Privacy, by structure.

01What this policy covers

This policy covers sigquill.com(the marketing website you’re reading now) and app.sigquill.com (the signature builder). Both are static front-end applications — there is no tracking code embedded in the pages themselves. A small backend service we operate handles the few moments Sigquill talks to a server: rendering or previewing your signature, an optional donation, and support requests. Each of those is described below.

Sigquill is operated as a sole proprietorship. We are the data controller for the limited information described here. Questions go to support@sigquill.com.

02Cookies & tracking

This marketing website sets no cookies of any kind— no analytics cookies, no advertising cookies, no “consent” cookies, because there is nothing to consent to. We don’t load third-party fonts, embedded social widgets, or tag managers.

The builder, app.sigquill.com, sets no cookies either. There’s no account to log into and no session to remember you by. Whatever you’ve built is saved locally in your own browser (see “Your signature content” below). The text of your signature is sent to our servers only when you explicitly ask for a preview or a rendered signature, or choose to donate or contact support. Images are the one thing that leaves earlier: a logo or headshot is uploaded as soon as you add it, so it can be hosted for email, and if you’ve already filled in your email address it is sent along with that upload — used once to derive the tag described under “How long we keep things”, then discarded.

03Analytics on this site

Sigquill uses Cloudflare Web Analytics to understand which pages visitors land on and how the site is performing overall. The service is cookieless. It does not set any cookies in your browser, does not store your IP address, does not assign you a persistent identifier, and does not share data with advertising networks or third parties.

Cloudflare processes aggregated visit data on Sigquill’s behalf as a data processor under a standard Data Processing Addendum. Because the measurement is instrumented at the network edge, there is no third-party analytics script running inside these pages and no request from your browser to a separate tracking server.

04Search engines

We use Google Search Console and Bing Webmaster Toolsto see how Sigquill’s pages rank in search and whether they’re indexed correctly. These tools report each search engine’s own data — impressions, ranking position, crawl status — about their search results. They are not given your browsing activity on this site, and they are not processors of your visit data. We mention them here for transparency, not because they observe you.

05What we collect if you donate

Sigquill is free, start to finish — no account, no paywall, nothing held back. An in-app panel lets you optionally support hosting costs with a small one-time donation through PayPal. Donating is voluntary and doesn’t unlock anything; everything is already available without it. If you choose to donate, we ask PayPal to collect:

• The donation amount you pick (one of a few fixed amounts) and the email address you enter at PayPal, used only to send a thank-you receipt.
• Optionally, your name, if you choose to add one, used only to personalize that thank-you email.

We don’t keep a copy of any of it. Once PayPal confirms the payment, we send a one-time thank-you email through Resendand record nothing about the transaction ourselves — PayPal is the sole holder of your donation’s details. Payment is processed entirely by PayPal; your card number, CVV, and bank details are entered on PayPal’s surface and are never sent to, seen by, or stored by Sigquill.

06Your signature content

You can open the builder, choose a template, and edit your details — no account, no payment, nothing to unlock. While you’re working, your draft (the name, title, contact details, links, and any logo or headshot you add) is saved only in your own browser’s local storage. It never touches our servers on its own, and it’s yours to clear at any time.

When you preview, copy, or download your finished signature, the builder sends those details — including any logo or headshot — to our backend for exactly one request. That request renders the HTML and the text of your signature is discarded immediately: nothing about your signature is written to a database, before, during, or after that request. Images are the exception — they are uploaded to our object storage (Cloudflare R2) so that email clients can load them, and are kept for as long as described under “How long we keep things” below. If you’ve filled in your email address, it is sent along with that upload for one purpose only — to compute the one-way tag described below, so we can find your images again if you ask us to delete them. The address is used for that calculation and then discarded; it is never stored or logged. We don’t have, and never ask for, access to your mailbox, contacts, or any connected account.

07Who processes data on our behalf

We keep the stack deliberately small. These are the only services that touch any data related to your use of Sigquill:

We do not sell, rent, or trade your information, and we don’t share it with anyone beyond the providers above that are necessary to deliver the product.

08How long we keep things

• Aggregate analytics are retained by Cloudflare on a rolling window (currently around six months) and contain no personal data.
• Your signature’s textis never stored on our servers, so there’s nothing here to retain or delete — closing the tab, or clearing your browser’s local storage, is the same as deleting it.
• Images you upload(a logo or headshot) are stored so they display in email. The stored file’s name is built from two parts: a hash of the file itself, and — if you’d filled in your email address in the builder before uploading — a one-way tag derived from that address. The address itself is never stored: not in the file name, not alongside the file, and we never write it to a log. The tag is computed with a secret key that only we hold, so it can’t be worked backwards into an email address by anyone who sees it, and its only purpose is to let us find your images if you ask us to delete them. It is part of the image’s public web address, so it does travel inside every signature you send — and it is the same tag on all of your images, which is precisely what lets us find them together. If you uploaded an image before filling in your address, it carries no tag — we won’t be able to find it by address, so send us the image’s link instead. Separately, we prune old images: any image whose last recorded fetch — or, if it has never been fetched, its upload date — is more than 18 months old is deleted. That is a proxy for “nobody is using this any more” rather than a precise measure, and it’s a housekeeping job we run, not a scheduled one, so the exact timing varies.
• Donationsleave no record with us. PayPal retains its own transaction history under its own policy; we don’t hold a copy.
• Abuse-prevention counters— to enforce rate limits we hand Cloudflare’s rate limiter a one-way hash of your IP address as a counting key. The address itself is never stored or logged, and the counters run in short windows of a few seconds, so nothing lingers.

09Your rights & choices

Depending on where you live, you may have the right to access, correct, or delete the personal data we hold about you, and to object to or restrict certain processing. Because we write nothing about your signature to a database, most of these requests are quick to honor — there is usually nothing on our side to find. The exception is any logo or headshot you uploaded: those we do hold, and we can delete them on request. Tell us the email address you used in the builder and we’ll remove every image tagged with it; for anything uploaded before you entered that address, send us the image’s link instead and we’ll delete it that way.

To make a request, email support@sigquill.com. We’ll respond within a reasonable timeframe. If your request concerns a donation, PayPal — not Sigquill — is the party holding the transaction record; we’re happy to help you get in touch with them.

10Where your data is processed

Our providers (PayPal, Resend, Cloudflare) may process data on servers in the United States, the European Union, or other regions, under their own terms and safeguards. By using Sigquill — including if you choose to donate — you understand that the limited data described above may be processed in those locations to deliver the product to you.

11Changes & contact

If we change this policy, we’ll update the “Last updated” date above. Material changes to how we handle data will be reflected here before they take effect. We keep the substance stable on purpose — the privacy posture is structural, not a knob we expect to turn.

Questions, requests, or concerns: support@sigquill.com.