Stringalize

Privacy notice

Last updated:

This notice explains what personal data Stringalize collects, why, and what you can do about it. It is given under Regulation (EU) 2016/679, the General Data Protection Regulation ("GDPR").

Who is responsible for your data

The data controller is:

Claudio Barbera
Via Mirga 23C, 91011 Alcamo (TP), Italy
VAT number (Partita IVA): 07255050820
Email: barbera.claudio@gmail.com

Write to that address for anything concerning your personal data.

What we collect, and why

DataWhy we need itLegal basis
Account details: your name, email address and password. The password is stored only as an irreversible hash. To create your account, let you sign in, and send you service emails such as password resets and invitations. Performing the contract with you (Art. 6(1)(b) GDPR)
Team membership: the teams you belong to, your role, and the projects and languages you may work on. To give each person the right access. Performing the contract
Activity records: which changes you made to projects, strings and translations, and when. To show a history of changes to your team, and to make deleted content recoverable. Performing the contract
Invitations: the email address of a person a team invites. To send the invitation and let that person join. Legitimate interest of the inviting team and ours in providing the service (Art. 6(1)(f))
Session and technical data: for each sign-in, your IP address and the browser you used; server logs of requests. To keep you signed in, protect accounts, limit abuse and diagnose faults. Legitimate interest in running a secure service (Art. 6(1)(f))
Visit statistics on the public pages: page viewed, referring site, browser, device type and country. No cookie is set and you are not followed across sites or visits. To understand which pages are useful. Legitimate interest in improving the site (Art. 6(1)(f))

We do not sell personal data, show advertising or build profiles of you. We do not make decisions about you by automated means.

Providing your name, email address and a password is necessary to have an account. Without them we cannot offer the service.

The content you put into Stringalize

The strings and translations your team stores are yours. If that content contains personal data, your team decides why and how it is processed and remains its controller; we process it only to provide the service, as a processor on your behalf. A data processing agreement is available on request.

Cookies

Stringalize uses a single cookie.

NamePurposeDuration
session_id Keeps you signed in. It is set when you sign in or create an account, and is readable only by our server. Until you sign out

This cookie is strictly necessary for the service you asked for, so it does not require your consent and there is no cookie banner. There are no advertising, profiling or third-party cookies. Visit statistics are collected without cookies, and browsers that send a "Do Not Track" signal are not counted.

Who receives your data

We use a small number of suppliers, who process data on our instructions:

Visit statistics are processed on our own server and are not shared with anyone. We disclose data to authorities only where the law requires it.

How long we keep it

Your rights

Under the GDPR you may at any time:

To exercise any of these, write to barbera.claudio@gmail.com. We reply within one month. You also have the right to lodge a complaint with the Italian data protection authority, the Garante per la protezione dei dati personali, or with the authority of the country where you live.

Security

Connections to Stringalize are encrypted. Passwords and API keys are stored as hashes rather than in readable form, with the exception of each project's read-only export key, which is kept readable so that it can be shown to you again. Access to the server is restricted.

Age

Stringalize is a tool for professional use and is not intended for anyone under 16.

Changes to this notice

If this notice changes in a way that matters, we will say so on this page and, where appropriate, by email. The date at the top shows when it was last revised.