Skip to content
freedocumentsigner.
How it worksBuy creditsPrivacy, first
Sign a document
CLEAR WORDS. NO SMALL PRINT.

Your files are your business.

Here is exactly what stays on your device, what we process, and why.

Last updated: 19 September 2026

Signing and downloading happen in your browser. If you separately choose Email me a copy, the signed PDF is uploaded to our server and sent through Brevo to your verified account email. That optional step requires your explicit consent.

1. Who is responsible

Free Document Signer
Operated from Camelon, Falkirk, Scotland, United Kingdom
Contact: support@freedocumentsigner.com

The operator is the controller for the limited personal information described below. This policy covers this website and its credit service, not independent websites you visit, including Stripe Checkout.

2. What happens to your document

PDFs, signatures, typed text, initials, and dates are held in browser memory while you edit. They are not intentionally persisted to browser storage, logged, sent to an analytics service, or used to train models. Refreshing or closing the tab ends the session. Your downloaded files remain wherever you save them, including any cloud folder you choose. Browser extensions, operating-system memory, and your device’s backup settings are outside our control.

We cannot retrieve or restore a document for you. Do not attach documents or signatures to a support request. We do not claim that this service removes malware or hidden content from PDFs.

3. Information we do process

  • Accounts and credits: your preferred display name, email address, Supabase Auth user ID, verification status, authentication/session records, a one-way hash of the normalized email to prevent repeat free-credit grants, account creation time, terms acknowledgement, and remaining credit count. Supabase Auth verifies your email at signup. Passwords are transmitted securely to Supabase Auth, which stores password hashes; the application does not store or intentionally log plaintext passwords. Email codes remain available for account recovery. Secure HTTP-only session cookies keep you signed in.
  • Exports: a random request ID and timestamp associated with your account, to deduct a credit once and prevent a retry being charged twice. The ID contains no document data.
  • Purchases: Stripe Checkout session ID, account identity, pack size, amount, and payment timestamp. We provide your verified account email to Stripe Checkout. Stripe handles receipts according to the payment and receipt configuration and processes payment and billing information, including contact information it asks for; we do not receive or store card numbers in this application. After a verified, fulfilled purchase, we use Brevo to send an account credit confirmation to your verified account email. It includes your preferred display name when available, credits added, amount paid and a purchase reference, but no PDF or signature. We retain delivery status, attempt timestamps, deduplication identifiers and any provider message reference with the purchase record to manage delivery and prevent duplicate confirmations.
  • Security: the hosting provider processes ordinary connection information such as IP addresses and request details. Our abuse limiter uses a keyed hash of the connecting IP and an hourly time window. It is not a document identifier or device fingerprint.
  • Support: information you choose to send us by email.

Optional email delivery

When requested, we process the signed PDF and your verified recipient email to fulfil that request. The attachment passes through server memory and Brevo; the application does not write it to its database or document storage and does not intentionally log it. Brevo and receiving email services may process or retain the resulting email and attachment according to their own policies. We cannot promise immediate deletion from those systems. The email copy remains in your mailbox until you manage it there. Do not use email delivery for documents you do not want processed by an email provider. You may withdraw consent before submitting; an email already sent cannot be recalled by us.

See Brevo’s privacy policy. Our lawful basis for this optional document transmission is your consent. Transactional signup and sign-in messages are needed to provide account access; they are not marketing.

4. Purposes and legal bases

We process accounts, credit balances, and payment records to provide the service and carry out our contract with you. We process limited security information under our legitimate interests in preventing fraud and maintaining the service. Records required by tax or accounting law are retained under legal obligations. Optional Google Analytics measurement is based on your consent, which you can withdraw through Analytics settings. Optional advertising uses its separate consent arrangements.

5. Providers and international processing

Vercel hosts the website and API. Supabase provides authentication and the credits database. Stripe handles payments. Brevo handles optional document emails and account credit purchase confirmations. Each processes information needed to perform its role. Provider policies and applicable agreements describe their processing. The operator is responsible for selecting appropriate service settings and maintaining any required processor agreements and safeguards for international transfers. Signing and downloading remain local. If you request email delivery, Vercel and Brevo process the completed PDF to send your copy.

Read Vercel’s privacy notice, Supabase’s privacy notice, and Stripe’s privacy notice for their own processing.

6. Retention

Session cookies follow Supabase session configuration and can refresh while you use the service. Signing out clears this browser’s session. The free-allowance email hash is retained to prevent duplicate grants, including after account deletion, subject to applicable rights and retention review. Credit records remain while needed to make non-expiring credits available. Export request IDs are retained with the credit account for retry protection and dispute handling. Abuse-limiter buckets expire from the active table after 24 hours, with cleanup on the next request. Provider logs and backups follow their configured retention periods; deletion may take longer to reach backups. Payment records needed for UK accounting are normally retained for six years after the relevant accounting period, subject to the operator’s applicable obligations. Support correspondence is normally deleted within 12 months of resolution unless an ongoing dispute or legal obligation requires longer.

7. Cookies, analytics, and advertising

We use Google Analytics 4 to understand visits to public information pages, only after you accept optional analytics. Google may process usage, device, browser and page-interaction information, cookie identifiers and connection information when analytics requests reach its services. This is not anonymous measurement. We disable Google signals and advertising personalisation in this integration; advertising consent remains denied for this analytics tag.

We send predefined public-page addresses and labels. We suppress referrer values and strip URL queries and fragments from measurement. The Google tag runs in a separate empty document rather than the signing interface. We do not measure account, signup, sign-in, editor or checkout pages, and do not send PDFs, filenames, signatures, initials, document text, email addresses, display names, passwords, account IDs or payment identifiers to Google Analytics. No custom signup, export or purchase events are sent.

Before acceptance, analytics stays off. Use Analytics settings on any page to accept or reject it; rejection stops future measurement and clears this integration’s analytics cookies. Your choice is stored locally for up to 180 days. Withdrawal does not erase information Google already received. Google’s handling and retention of measurement data depend on its policies and the Analytics property settings. See Google’s privacy policy and how Google uses information from partner sites.

Advertising is currently disabled. No advertising or consent-platform scripts are loaded.

We do not use session replay. Aggregate counts of exports and purchases can be calculated from service records without inspecting documents. Ad components are mounted only on the FAQ and how-it-works pages. When advertising is enabled, scripts previously loaded on those pages may remain in the browser during navigation without a full page reload. PDF code and fonts are served from this site. Read our cookie policy.

8. Your choices and rights

Depending on applicable law, you may request access, correction, deletion, restriction, portability, or object to processing based on legitimate interests. Contact the operator using the details above. We may ask you to demonstrate control of your account; we do not need your PDF or your sign-in code by email. Deleting an account can permanently remove access to unspent credits. Some accounting information may need to be retained even after deletion.

You can block or delete cookies, but the credit service may stop working. Sign in again with the same email after clearing browser data. Depending on the laws that apply to you, you may lodge a complaint with the relevant data protection or privacy authority in your country or region. For UK-related complaints, this may be the Information Commissioner’s Office (ICO). We do not sell document content or personal information.

9. Changes and contact

We will update this page if our processing changes. Material changes requiring consent will not be applied merely by changing this notice. Use the contact details above for questions or privacy requests.

freedocumentsigner.

A little less paperwork. A little more life.

Signing stays on your device
How it worksBuy creditsFAQsSign Google Docs as PDFPrivacy policyTerms of useCookie policyContactMy accountInstagramThreads

© 2026 Free Document Signer · Made for your everyday paperwork.