Privacy Policy

Last updated: September 25, 2026

EmailSendoff is an independent online tool for creating email signatures. This policy describes what the editor and purchase-recovery flow handle. We do not require an account.

Questions or privacy requests: taylormakegames@gmail.com. The operator of EmailSendoff is responsible for this service.

Information You Enter

Your name, job title, company, contact details, social profile names, image URL, and design choices are used in your browser to build the signature. The editor does not send these signature details to our server. Copying a signature places the generated content on your clipboard.

Optional draft saving is off until you choose “Allow draft saving.” If enabled, the editor stores the draft in this browser’s local storage. Use “Clear saved draft” in the menu or your browser’s site-data controls to remove it. If you decline, the draft is not saved between visits.

If you use a remote image URL, your browser requests that image from its host. The host may receive ordinary connection information such as your IP address. The URL may also appear in the signature you copy.

Purchases and Recovery

Stripe hosts checkout and processes payment details. We do not receive or store your full card number. Our server receives the Checkout Session information needed to verify a Premium purchase.

If you request purchase recovery, we use the email address you enter to search Stripe Checkout Sessions for a completed, paid Premium purchase. If one is found, Resend delivers an email containing a one-time recovery link that expires after 15 minutes. We do not create a customer account or keep a separate purchase database.

Cookies and Device Storage

• Premium access cookie: a signed, first-party, HttpOnly, Secure, SameSite=Lax cookie set after a purchase is verified. It remembers the Premium unlock on that browser for up to ten years. It contains an entitlement and expiry, not your signature details.
• Draft preference cookie: records whether you allow or decline local draft saving, for up to one year. It is used only to remember that choice.
• Draft local storage: stores signature fields only if you opt in. It remains in the browser until you clear it or clear this site’s browser data.

We do not use advertising cookies or cross-site ad tracking. Basic analytics are configured without analytics cookies. The purchase cookie is required for the Premium access feature; draft saving is optional.

Service Providers and External Resources

We use Netlify to host the site and run its server functions, Stripe for checkout and payment verification, Resend to deliver requested recovery emails, and PostHog for basic site analytics. The editor also loads styling and fonts from Tailwind’s CDN and Google Fonts. Its sample avatar is hosted by Unsplash. These providers may receive technical information when your browser or a server function connects to them, and handle it under their own privacy terms.

Analytics, Sale, and Retention

We use PostHog to understand basic site usage, such as page visits, selected signature theme, and whether the copy button is used. We configure analytics without session replay, autocaptured clicks, form capture, advertising pixels, analytics cookies, or cross-site ad tracking. Analytics events do not include the personal details entered into your signature, such as your name, email address, phone number, company, image URL, social profile names, or generated signature content.

We do not sell personal information. Netlify, Stripe, Resend, PostHog, and external asset hosts may process technical or transaction information needed to provide their services. We do not keep signature drafts on our servers. Stripe and Resend retain information according to their policies and legal obligations.

Your Choices

You can decline draft saving, clear a saved draft from the editor menu, or remove site data in your browser. You may also contact us to ask about access, correction, or deletion requests that apply where you live. Some payment or transaction records may need to be retained by Stripe or as required by law.

Security and Changes

We use server-side payment verification and signed access tokens, but no online service can promise perfect security. We may update this policy when the service changes. The latest version will be posted here with its updated date.