Privacy Policy
Effective date: 18 November 2026
This policy explains what personal data we process when you use Mailsignly at mailsignly.com, why we process it, on what legal basis and for how long. Mailsignly is a free email signature generator. Most features work without an account, but "no account" does not mean "no personal data", so we describe everything that actually reaches our server.
1. Controller
The controller of your personal data is: [TO BE COMPLETED: company details] ("we", "us" or "Mailsignly").
For any question about personal data, write to privacy@mailsignly.com. We have not appointed a data protection officer because we are not required to.
2. What data we process
2.1. Data that stays on your device
- Signature draft. What you type into the editor (name, job title, phone number, addresses, colours and so on) is saved in your browser's storage (localStorage) on your device so it survives a page reload. The draft is not sent to our server unless you save the signature to an account.
- "Send to computer" link. The hand-off link is created locally in your browser, and the signature data is placed in the URL after the # sign. Browsers do not send that part of the address to the server, so a signature shared this way does not reach us. Anyone who receives such a link can see what it contains.
2.2. Data we process on our server
- Account: email address, chosen language, account creation date and last sign-in.
- Sign-in tokens: when you request a sign-in link, we create a single-use token. We store only its SHA-256 hash (never the token itself), together with the email address, language, target page and the time it was created and used.
- Sessions: after you sign in we create a session. We store a hash of the session identifier, its creation and expiry dates, and your browser identifier (user-agent), which helps us spot suspicious sign-ins.
- Anonymous session: if you upload an image without an account, we assign a random identifier stored in the ms_anon cookie. We keep its hash and the dates it was created and last used. The identifier contains neither your name nor your email address.
- Uploaded images: logos, photos, banners and thumbnails you upload, and their metadata: type, dimensions, size, content hash, upload and last-use dates, and the link to your account or anonymous session. We re-encode images and strip embedded metadata (such as EXIF location data) in the process.
- Saved signatures: if you have an account and save a signature, we store its name and content, including the details you entered.
- IP address: used in rate-limit records (for example, how many sign-in links were requested from one address) and in server and network logs kept for security and troubleshooting.
We do not collect special categories of data, we do not run behavioural analytics and we do not show ads.
3. Purposes and legal bases
| Purpose | Data | Legal basis (GDPR) |
|---|---|---|
| Providing the service: sign-in, running your account, saving signatures, exporting and deleting data | email, language, tokens, sessions, signatures | Art. 6(1)(b) (performance of a contract, i.e. the Terms of Service) |
| Hosting images so that recipients of your emails can see the logo and photos in your signature | images and their metadata, anonymous session identifier | Art. 6(1)(b) |
| Security, rate limiting and abuse prevention (for example sign-in link spam or phishing) | IP address, user-agent, logs | Art. 6(1)(f) (legitimate interest in protecting the service and its users) |
| Meeting legal obligations, such as responding to authorities, handling complaints and accountability | data needed in the given case | Art. 6(1)(c) |
4. Cookies and browser storage
We use only cookies that are strictly necessary for the service:
| Name | Purpose | Duration |
|---|---|---|
| ms_sess | keeps you signed in; HttpOnly, Secure, SameSite=Lax cookie | 30 days |
| ms_anon | links images uploaded without an account to your browser | 30 days from when it is set (it is not extended when you use the service) |
| localStorage (draft) | keeps your signature draft on your device | until you clear your browser data |
We do not use analytics, marketing or third-party cookies. Because we only use storage that is strictly necessary to provide the service you ask for, no consent is required (Article 5(3) of the ePrivacy Directive), which is why there is no cookie banner. You can delete cookies and site data in your browser settings at any time; you will then be signed out and your draft will be lost.
5. Recipients and processors
We do not sell your data or share it for marketing. We use the following providers, who process data on our behalf under data processing agreements (Art. 28 GDPR):
- Netcup GmbH (Germany) – the server running the application, database and files. Data is stored in Germany.
- Cloudflare, Inc. – content delivery network, the tunnel connecting our server to the internet, and attack protection. Traffic to the site passes through Cloudflare, including IP addresses and uploaded images.
- Resend – delivery of sign-in link emails. Resend receives your email address and the message content.
We may also disclose data to public authorities where the law requires it.
Transfers outside the EEA
Cloudflare and Resend are based in the United States, so data may be transferred there. Transfers rely on the European Commission's adequacy decision for the EU-US Data Privacy Framework (to the extent the provider is certified) and, in addition, on the Commission's Standard Contractual Clauses. You can request a copy of these safeguards at privacy@mailsignly.com.
6. Images are public
An image in a signature must be reachable by the people who receive your emails, so every uploaded file gets a public address. Anyone who has that address can open the image without signing in. The address is hard to guess, but it is not secret: it is included in every email you send. Do not upload images that should not be public. Once you delete a file, its address stops working, although recipients' email programs may already have stored copies, which we cannot control.
7. How long we keep data
| Data | Retention period |
|---|---|
| Sign-in token | valid for 15 minutes and single-use; the record is deleted after [TO BE COMPLETED: clean-up period] |
| Session | 30 days or until you sign out |
| Files uploaded without an account and the anonymous session | files: about 13 months (400 days) after last use, then deleted automatically, so that images keep working in emails you have already sent. Create an account to keep them longer, or delete them yourself at any time. The anonymous session record (identifier hash and dates) is deleted automatically once it has no files left and has not been used for 30 days. |
| Account, saved signatures and account files | until the account is deleted; "Delete account" removes them immediately; backups are overwritten after [TO BE COMPLETED: backup rotation period] |
| Rate-limit records (IP address, email, time) | short-term, only for the duration of the rate-limit window |
| Server logs | [TO BE COMPLETED] |
We keep data longer only where the law requires it or where it is needed to establish, exercise or defend legal claims.
8. Your rights
Under the GDPR you have the right to:
- access your data and receive a copy;
- rectification of inaccurate data;
- erasure; you can delete your account and all related data yourself with the "Delete account" button, and individual files and signatures in your account panel;
- restriction of processing;
- data portability; your account panel lets you download an export of your data in JSON format;
- object to processing based on legitimate interest (Art. 6(1)(f));
- lodge a complaint with a supervisory authority, in particular in the EU country where you live or work. In Poland this is the President of the Personal Data Protection Office (Prezes UODO), ul. Stawki 2, 00-193 Warsaw. The lead authority depends on the controller's place of establishment: [TO BE COMPLETED].
To exercise your rights, write to privacy@mailsignly.com. We will reply without undue delay and within one month at the latest. For requests about account data, we may ask you to confirm that you own the account, for example by writing from the account's email address.
9. Profiling and automated decisions
We do not profile users and we do not make decisions based solely on automated processing that produce legal effects or similarly significantly affect them. Automatic rate limits only temporarily block an excessive number of requests.
10. Providing data is voluntary
Providing data is voluntary. Without an email address you cannot create an account, but you can still build and copy signatures. Without the ms_anon cookie you cannot upload images without an account. What goes into your signature is entirely up to you; include only what you want recipients to see. If you add other people's data (such as a colleague's photo), make sure you have a basis for doing so.
11. Security
We apply technical and organisational measures appropriate to the risk: encrypted HTTPS connections, storing tokens and session identifiers only as hashes, CSRF protection, rate limiting, validation and re-encoding of uploaded images, and regular backups.
12. Changes to this policy
We may update this policy, for example when the service's features, providers or applicable law change. The current version is published on this page with its effective date. We will notify account holders of material changes by email in advance.