Privacy Policy

What we collect

SignScribe is designed so that your signature — drawn, typed, or uploaded — is created and rendered entirely within your own browser. We do not upload, transmit, or store the images or text you create using our tools.

Analytics

We may use privacy-respecting, aggregate analytics to understand overall site traffic (such as which pages are visited). This does not include the content of anything you draw, type, or upload.

Third-party fonts

The type-signature tool loads script fonts from Google Fonts. Loading these fonts may involve a request to Google's servers, subject to Google's own privacy policy.

Cookies

SignScribe does not use cookies to track you across sites or to store your signature data.

Legal basis and international visitors

For visitors in the European Economic Area, our minimal, aggregate analytics use is generally handled under a legitimate-interest basis for understanding site performance, since it does not involve identifying individual visitors or processing sensitive personal data. Because signature content never reaches our servers regardless of where you're located, there's no cross-border data transfer question to address for that content specifically — it simply stays on your device.

Children's privacy

SignScribe is not directed at children under 13, and we do not knowingly collect personal information from children.

How the "no server" claim actually works

It's an easy claim to make and a harder one to prove, so here's the specific mechanism. All three tools — draw, type, and upload — run using JavaScript that executes entirely inside your browser tab. The draw tool uses the HTML5 Canvas API to capture and render your strokes locally. The type tool loads a font file and renders your typed text into an image, again entirely on your device. The upload tool reads the photo you select using your browser's built-in file APIs and processes background removal using code that runs on your device's own processor, not on a remote server. In each case, when you click "download," the resulting image is generated and saved directly from your browser's memory. There is no upload step in the code, because there's no server endpoint built to receive one. If you're comfortable with browser developer tools, you can verify this yourself: open the Network tab before using any of the tools, and you'll see no outgoing request carrying your signature data.

What data does reach a server, and why

Two categories of data do involve a request to somewhere outside your device, and we want to be specific about both rather than lumping them into a vague "we don't collect data" statement. First, loading the site itself and its script fonts involves standard web requests to our hosting provider and to Google Fonts — this is true of virtually every website and doesn't include anything you type, draw, or upload. Second, if we use aggregate analytics to understand traffic patterns, that data is limited to things like which pages were visited and roughly when, not the content of your signature.

Your rights over your own data

Because your signature content itself is never transmitted or stored by us, there's nothing on our end to request access to, correct, or delete in relation to what you draw, type, or upload — it exists only in your browser's memory during your visit and in the file you download to your own device. If you've contacted us by email, you're welcome to request that we delete that message and any attachments from our inbox; see the contact page for details on how to reach us.

Data retention

Since signature content is never stored on our servers in the first place, there is no retention period to describe for it — it simply doesn't exist outside your own browser session and downloaded file. Any aggregate, non-identifying analytics data we collect about site traffic is retained only as long as needed to understand usage trends, and is not tied to any individual visitor's signature activity.

Security practices

The site is served exclusively over HTTPS, encrypting the connection between your browser and our hosting provider for the page content itself. Because signature data never leaves your device, there's no separate "signature database" that could be breached — the strongest security guarantee here is architectural rather than something enforced after the fact by access controls or encryption of stored data.

Comparing this to account-based tools

Many e-signature and document platforms are built around a different model: your signature is stored in an account so it can be reused across future documents, and the platform keeps a full history of everything you've signed for audit purposes. That's a genuinely useful trade-off for some use cases — a business tracking dozens of contracts, for instance — but it necessarily means storing signature and document data on the platform's servers. SignScribe intentionally trades that reuse-and-history convenience for a simpler guarantee: nothing about what you draw, type, or upload is ever stored anywhere but your own device. Which model is "better" depends entirely on what you're trying to do; for a one-off signature image, we think the simpler model is the right one.

Changes to this policy

We may update this policy occasionally, most often to reflect a new feature or a change in which third-party services (like font providers) the site relies on. Material changes will update the "last updated" date at the top of this page. Continued use of the site after changes constitutes acceptance of the updated policy.

Contact

Questions about this policy can be sent via our contact page.