Privacy Policy

1. Who is responsible for your data

In short: The company behind FairSign is the data controller. One email reaches us.

FairSign is operated by [TODO: COMPANY_LEGAL_NAME], registered in [TODO: JURISDICTION], which is the data controller for the processing described here (GDPR terms). For anything privacy-related, write to [TODO: CONTACT_EMAIL] — a person reads it, not a ticket bot.

2. The honest headline: two modes, two very different data flows

In short: Self-signing: your file never leaves your device — we couldn't look at it if we wanted to. Sending for signature: the file goes through our servers, encrypted, EU-hosted, deleted after 30 days.

Most e-signature privacy policies blur this. We won’t:

• Self-signing — zero upload. When you sign your own PDF, the file is opened, filled, and signed entirely in your browser. It is never uploaded, we never receive it, we keep no copy, and no record of its content exists on our side.
• Sending for signature — encrypted, temporary, EU. When you send a document to other people, we have to store and deliver it. The file is encrypted in transit (TLS) and at rest (AES-256), stored in the EU, kept for 30 days after the request completes, then deleted automatically. You can also delete it manually at any time before that.

We deliberately do not claim “your files never leave your device” across the whole product — that is only true for self-signing, and precise claims are the point of this page.

3. What we collect, and why

In short: An email address to run your account, envelope metadata to run signature requests, and signing events (IP, device, timestamps) because they are the audit trail.

• Account data — your email address (that’s the whole login) and your plan. Legal basis: performing our contract with you.
• Documents sent for signature — the file itself plus envelope details (recipients, field placements, status). Legal basis: performing our contract.
• Signing events — when a recipient opens, views, consents, signs, or declines, we record the timestamp, IP address, and browser user-agent. These events are the tamper-evident audit trail that gives the signature its evidentiary value. Legal basis: performing the contract and our legitimate interest in producing reliable signature records.
• Waitlist and support email — if you join the waitlist or write to us, we keep the message and address to reply and to send the one launch email we promised. Legal basis: consent; unsubscribe or ask us to delete it any time.

That’s the list. No behavioral profiles, no data brokers, and no analytics cookies today — see the Cookie Policy.

4. What we never do with your data

In short: No selling, no ads, no reading your documents.

• We never sell personal data. To anyone. In any form.
• We show no ads and share nothing with ad networks.
• We don’t read the documents you send; they are processed only to deliver, sign, and archive them as you asked.

5. Where your data lives, and who helps us process it

In short: EU-hosted storage and a short, named list of processors.

Documents and account data are stored in the EU region of our hosting provider. We use a small number of processors under data-processing agreements:

• Supabase — database, authentication, and encrypted file storage (EU region).
• Paddle — payments, as merchant of record. Paddle receives your billing details; we never see your card number.
• Email delivery provider — [TODO: ESP_NAME — confirm before launch] — sends signature-request and account emails on our behalf.

If a processor is outside the EU/EEA, transfers rely on an adequacy decision or EU Standard Contractual Clauses [TODO: TRANSFER_MECHANISM — confirm with counsel].

6. How long we keep things

In short: Files sent for signature: 30 days after completion, then gone. Audit records of completed signatures: kept, because all parties rely on them. Everything else: until you delete it.

• Self-signed files — never stored. Nothing to retain.
• Files sent for signature — deleted automatically 30 days after the request completes (every party receives the final signed copy by email at completion). You can delete the stored file manually at any time before that.
• Audit records of completed signature requests — retained for [TODO: RETENTION_PERIOD — set by counsel]; see section 7 for why.
• Account data, templates, unfinished requests — kept while your account exists; deleted when you delete them or your account.
• Waitlist emails — until launch plus a short wind-down, or the moment you unsubscribe.

7. Where the right to deletion ends: signed documents

In short: Deleting your account can't erase the record of a contract other people signed with you.

Deleting your account removes your profile, your templates, and any signature requests still in progress. Completed signature requests are shared between every party who signed: the final document and its audit record are what lets each of them prove what was agreed. So those records are not destroyed because one party deletes their account — this is the legal-retention exception recognized by the GDPR (Art. 17(3)), and we state it here so it never surprises anyone. The retention period is [TODO: RETENTION_PERIOD — set by counsel].

8. Your rights

In short: Access, correct, export, delete, restrict, object — one email, no forms, no fee.

Under the GDPR (and similar laws) you can ask us at any time to:

• tell you what data we hold about you (access);
• correct it (rectification);
• hand it over in a portable format (data portability);
• delete it (erasure — with the single exception described in section 7);
• restrict or object to specific processing;
• withdraw consent for anything based on consent (e.g. the waitlist).

Email [TODO: CONTACT_EMAIL] and we’ll answer within a month. You can also complain to your local data-protection authority — we’d appreciate the chance to fix things first, but you don’t owe us that.

9. Cookies

In short: Essential cookies only. The full, honest list is one click away.

FairSign sets only cookies the service needs to work (login session, language, theme, signer access verification) and runs no analytics or advertising cookies. Every cookie we set is listed, with its purpose and lifetime, in the Cookie Policy.

10. Security

In short: Encryption in transit and at rest, EU storage, access-coded documents, and honest disclosure if anything ever goes wrong.

Documents sent for signature are encrypted with TLS in transit and AES-256 at rest. Signing links are unguessable tokens that expire after 30 days, and senders can require an access code on top. Should a breach ever affect your data, we will notify you and the supervisory authority as the GDPR requires — plainly, not buried in a status page.

11. Children

In short: FairSign is not for children.

FairSign is a contract tool and not directed at children under 16. We don’t knowingly collect their data; if you believe a child has used the service, contact us and we’ll delete the account.

12. Changes to this policy

In short: Material changes are emailed to you before they apply.

If we change this policy in any way that matters — new data, new purpose, new processor — we’ll email account holders before the change takes effect and update the date at the top. We will never quietly downgrade the promises in section 2.