Privacy Policy

esigna (“we”, “us”, or “our”) lets you make professional email signatures for free and offers an optional paid plan. You can use it with or without an account. This Privacy Policy explains what information we collect, how we use it, and the choices you have.

Questions: support@esigna.app.

You can make and copy a signature without signing up. While you do:

• Your draft stays in your browser. The details you type and the images you add are stored on your device, in your browser’s own storage. We do not receive them unless you do one of the things below, or use esigna in ChatGPT (see the next section). Clearing your browser’s site data, or choosing “Clear from this browser” in the editor, removes them, and we cannot recover them.
• Images you copy into an email are hosted by us. An email client can only show an image from a web address, so when you copy your signature as HTML (or add an image to it), we upload that image, resized for email, and publish it at a long, unguessable public address. Anyone who receives an email with your signature can see it.
• Your photo is dressed on our server. To show your photo dressed for a Season, or cut out for Portrait, the editor sends it to esigna’s own server, which sends the picture back and keeps nothing. The Santa hat tool sends a smaller copy of your photo the same way, only to find where your head is, and keeps nothing either. It is not sent to anyone else or used to train anything.
• A cookie groups those images. The first time you host an image without an account we set a cookie (esigna_guest) holding a random identifier, so images from the same browser are stored together and abuse can be traced and removed. It is not used for advertising or to follow you across other sites.

If you later create an account and save your draft, it moves from your browser into your account and the browser copy is removed.

You can also design a signature with esigna’s app in ChatGPT. It works without an esigna account. While you do:

• ChatGPT sends us what it asks esigna to do. When ChatGPT uses esigna’s tools, it sends us the details for your signature (such as your name, title, company, contact details and links), the design, and any image you attach for it. We receive what those requests contain, not the rest of your conversation. ChatGPT also adds your language and approximate location to each request; we do not use or keep them.
• Your signature is kept as a draft. So ChatGPT and the esigna Editor inside it can work on the same signature, we keep it on our server under a long, unguessable identifier, with its recent changes so you can undo them. Designs prepared for you to choose from are kept the same way, including any ChatGPT checked but did not show. A draft can no longer be opened 30 days after its last change, and is then deleted.
• Images are hosted for email. A photo, logo or other image you add is published at a long, unguessable public address, as described above, so anyone who receives an email with your signature can see it.
• ChatGPT sees your signature. What esigna returns to ChatGPT (the signature, a review of its design, and the changes you make in the esigna Editor there) goes to OpenAI so ChatGPT can help you. OpenAI handles it under its own privacy policy.
• An anonymous identifier limits abuse. ChatGPT gives each request an anonymous identifier for the person making it. We use it, or the request’s IP address, only to limit how often images can be hosted, drafts started and designs kept, and we do not keep it with your draft.

We count what gets used in ChatGPT the way we count it on esigna, as described below: which of esigna’s tools ChatGPT uses and whether each worked, and what is done in the esigna Editor there, such as choosing a template or copying your signature. These counts never hold the details you give, the anonymous identifier above or your draft’s identifier, and esigna’s pages inside ChatGPT do not count page views.

This feature needs an account. A free account can use it once and the Signature plan as often as you like, so we record when a free account uses it. When you paste a signature you already have to fill in your details, its text and links go to our server and to TypeSafe, which sorts them into your name, title and contact details. We do not store the paste. TypeSafe does not use it to train its models and keeps it only as long as its own privacy policy allows. Images in the paste are never sent, and nothing leaves your browser until you paste.

Making your own Brand Kit needs the Brand Kit plan. When you type a website, our server visits that site’s public pages, as a browser would, and reads its logo, colors, fonts, name and the contact details it publishes. When you start from one of your Signatures, we read its details, logo and photo. Only make a Kit for a brand that is yours or that you have permission to use.

• Kept with your account. What was read, the pictures, and the choices you make are kept until you delete the Kit, so you can come back to it. Only your account can open it.
• Photos are processed on our server. A photo you add, or the one in your Signature, is cut out from its background on esigna’s own server to place you on your covers and video call background. It is not sent to anyone else or used to train anything.
• Sample Kits are made from invented companies and people, and anyone can open them.

To learn what to improve, we count what people do in esigna: for example, how many open the editor, which template they choose, whether they copy their signature and into which email app, and whether they open checkout. We use PostHog for this, and it runs without cookies or browser storage.

• What an event holds. The page and the action, how far down the page you scrolled, the template, which kinds of detail a signature has (such as a photo, a logo or a LinkedIn link, but not what they say), the choices you made in a free tool (such as an icon style or a handwriting style), your browser and device type, the site that sent you, and your approximate country.
• What it never holds.Anything you type or paste: your name, email address, phone number, links, address, or the signature itself. The free tools work in your browser, and the images, names and drawings you use in them are never sent to us, apart from the Santa hat tool’s photo above, which is read and thrown away. Page titles and the ids in share and signature addresses are removed before an event is sent.
• How visitors are counted. PostHog combines your IP address and browser details with a value that changes every day to make an anonymous code, then discards the IP address. The same visitor gets a new code the next day, and the events are never linked to your account.
• When a page stops working, the event holds the kind of error, not what it says, and whether your browser was translating the page.
• Purchases are counted by payment (that one was made, and for how much) without who made it.
• In ChatGPT, the calls ChatGPT makes to esigna’s tools are counted, each on its own: which tool, whether it worked, the template it drew from, and whether it came from OpenAI’s servers. Not who made it, their location, or anything else it was sent.

An account with the Signature plan can share one of its signatures as a team link, so each person on a team adds their own details to the same design and copies their own signature, with no account.

• What you add is kept with the team’s account. The details and photo you add on a team link are stored with the account of whoever shared it. They can see them, change the link and remove you. You can change your details from your own link, which your browser remembers. The page shows the first name of whoever shared it.
• Being removed. Ask whoever shared the link, or contact us, and your details and photo are deleted. A signature you already pasted into your email keeps working.
• Sharing a link. Anyone with a team link can add their details while it is on, so send it only to your team. You can turn it off or replace it at any time.

An account can upload its company's font, so its name and company are drawn in it in every inbox.

• The file stays with esigna. Font files you upload are stored privately with your account. Only our server opens them, to draw the pictures of your name and company. We never serve, share or show the file to anyone, teammates on your team links included, and use it for nothing else.
• The pictures are public. When you copy a signature set in your font, the pictures of your name and company are kept at public web addresses, like every image in a signature, so email apps can show them. They are pictures of those words, not the font.
• Removing it. Remove a file, or the whole font, from the font dialog in the Editor at any time, and the files are deleted. Deleting your account deletes them too. Signatures you already pasted keep their pictures.

Depending on how you use esigna, we may process:

• Account information: name, email address, and authentication details provided through our sign-in provider (Clerk), including when you use Google or email-based sign-in.
• Signatures you save: the details in a signature saved to your account (such as name, title, company, contact links and design choices), and the headshot or logo you save with it.
• Team signatures: the details and photo someone adds on a team link, kept with the account that shared it, as described above.
• Brand Kits: what was read from the website or Signature a Kit was made from, its logo and photos, and the choices you make, kept with your account until you delete the Kit.
• Signatures you paste: the text and links of a signature you paste to fill in your details, read when you paste it (or, if you paste before you have an account, once you’ve made one) and not stored.
• ChatGPT drafts: the details, design and images of a signature you make with esigna in ChatGPT, kept as described above.
• Hosted email images: the images described above, published so your signature displays in email clients, whether or not you have an account.
• Share pages: the image and name of a signature you choose to publish as a share link.
• iPhone pages: when you choose iPhone in the Copy window, your signature as Copy signature makes it, kept at a long, unguessable address so the code there can open it on your phone, ready to copy.
• Earlier AI caricatures: esigna no longer generates them. If you made one before September 2026, the generated images stay stored with your account, so signatures using them keep working, until you remove them or ask us to delete them.
• Feedback and Teams requests: what you write in the feedback or Teams form, the email address you give for a reply, and the page, browser and signature design it was sent from, so we can read and answer it.
• Purchases: for the Signature plan, the Brand Kit plan and earlier credit packs, we keep the account, product, payment and reversal identifiers needed to grant access, handle refunds and disputes, and meet legal obligations. Card payments are processed by Dodo Payments; we never store card numbers.
• Usage and technical data: logs such as IP address, device and browser information, and the anonymous product events described above, needed to operate, secure and improve the service, including rate limiting to prevent abuse.

We use the information above to:

• Provide, maintain and improve the signature editor
• Host the images your signatures need to display in email
• Authenticate you and keep your account secure
• Save signatures to your account and show them on any device
• Grant paid access and handle refunds or disputes
• Detect abuse, prevent fraud, enforce rate limits and our Terms
• Respond to support requests and send service-related notices
• Email you occasional product news, such as what’s new in your plan. Every one has an unsubscribe link
• Comply with law and protect our legal rights

We share information with service providers who help us run esigna:

• Authentication (Clerk)
• Database and file storage for accounts, team links, Brand Kits and feedback (Supabase)
• Sending email, such as welcome emails, product news and feedback to our inbox (Resend)
• Hosting, image storage and security (Vercel)
• Product analytics, without cookies (PostHog)
• Reading a signature you paste into its details (TypeSafe)
• Payments for the Signature plan, the Brand Kit plan and earlier credit packs (Dodo Payments)

When you use esigna in ChatGPT, what it returns to ChatGPT goes to OpenAI, as described above. Images you host for email, and share pages you publish, are public by design. We may also disclose information if required by law, to protect rights and safety, or in connection with a business transfer. We do not sell your personal information.

We only use the cookies and browser storage esigna needs to work, which is why there is no cookie banner to click through:

• Signing in. Clerk sets cookies on esigna’s own domain and its sign-in domain to know whether you are signed in and to keep you signed in. They are set on your first visit, signed in or not. Cloudflare, which protects that sign-in service, adds security cookies to it.
• The guest cookie described above, set only when you host an image without an account.
• Your last product. With an account, a cookie remembers whether you last used Signatures or the Brand Kit, so signing in opens it again.
• Your language.If you choose a language with the Editor’s language switch, or open the Editor from one of our pages in French, a cookie remembers that language for a year. Without it, the Editor follows your browser’s language.
• Browser storage for your draft and its images, a signature you paste before making an account (only until your account reads it, at most 15 minutes), a note that you opened checkout in that tab, so coming back without paying can ask what stopped you (at most 2 hours), and your theme and preview preferences.

PostHog counts page views and what gets used, without cookies and without following you to other sites. We do not use advertising or cross-site tracking cookies.

Videos.Some guides play a video in YouTube’s player, from youtube-nocookie.com, its privacy-enhanced mode. The player loads as you scroll near it, so YouTube receives your IP address and that the video is on esigna, and it may store information in your browser. That is covered by Google’s privacy policy, not this one.

• A draft kept in your browser stays there until you clear it, clear your browser’s site data, or save it to an account.
• A ChatGPT draft is deleted 30 days after its last change, as are designs prepared for you to choose from, including any ChatGPT checked but did not show.
• Hosted email images are kept for as long as the service runs, because deleting one would break every signature already using it. You can ask us to remove specific images.
• An iPhone page stops opening 24 hours after it is made and is deleted within the following day. The images it shows are hosted email images, kept as above.
• Account and signature records are kept while your account is active and as needed to operate the service; you can request deletion at any time.
• Details added on a team link are kept until the person is removed, the signature the link shares is deleted, or the account that shared it is.
• Font files you upload are kept until you remove them or delete your account.
• Feedback and Teams requests are kept so we can answer them and improve the service; you can ask us to delete one.
• Purchase records are kept as long as tax, accounting and dispute rules require.

• Use the editor without an account, and clear your draft from the editor’s menu whenever you like
• Update profile details through your account and sign-in provider
• Edit or delete signatures saved to your account
• Unsubscribe from product news with the link in any of those emails, or by writing to us. Your account and service emails are not affected
• Contact support@esigna.app to access, correct or delete your data, or to have hosted images removed

We use safeguards appropriate to a hosted web app, including encrypted transport (HTTPS) and access controls on our systems. No method of transmission or storage is 100% secure. Anything saved only in your browser is as safe as the device it is on.

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

We may process information in the United States and other countries where we or our providers operate. If you use esigna from another region, you understand your information may be transferred to and processed in those locations.

We may update this Privacy Policy from time to time. We will change the “Last updated” date at the top of this page when we do. Continued use of esigna after changes means you accept the updated policy.

For privacy questions, email support@esigna.app. Related documents: Terms of Service and Refund Policy.