Legal

Privacy policy

What Temply collects about you, why, who else handles it, and how to see it, take it or delete it.

Last updated 25 September 2026 · Terms of service

1. Who is responsible

Temply runs Temply and is the controller of the personal data described here. Reach us at hello@temply.app.

2. What we collect

  • Account. Your name, email address and profile picture from the sign-in provider you choose, and the workspaces you belong to. Held by Clerk on our behalf.
  • What you build. Templates, brands, uploaded images, the sample data you type into the preview, and the version history of each template.
  • Billing. Your plan, your Stripe customer and subscription ids, the number of seats and template packs, and your monthly API call counts. Stripe processes the payments and stores your card details, which go to it directly and never reach us.
  • API use. Which key was used, when, and a monthly count per workspace — enough to enforce the plan, not the content of your calls. The data you pass to render a template is used for that render and not stored.
  • Test sends. When you send a test email from the editor, the address you send it to and the rendered email pass through Resend.
  • Contact form. The name, email and message you submit, kept so we can answer.
  • Errors. When something breaks, the error, the page it happened on and the browser version go to Sentry. Not the contents of your editor.

We do not run advertising or analytics trackers. There is no cookie banner because the only cookies are the ones that keep you signed in; your theme choice lives in your own browser’s storage.

3. Why, and on what basis

  • To run the service you signed up for — storing your work, rendering it, serving your API calls, billing your plan. This is performance of our contract with you.
  • To keep the service safe — rate limits, abuse prevention, error monitoring. This is our legitimate interest in running a working product, balanced against yours.
  • To answer when you write to us. Legitimate interest, and yours too.
  • To meet legal obligations such as tax records for payments.

We send email about your account (receipts, a change to these terms, a security notice). We do not send marketing email.

4. Who else handles it

These services process data for us, each for one job:

  • Clerk — sign-in, accounts and team membership.
  • Stripe — checkout, payments, invoices and storing your card details, as our payment processor; card details never reach us.
  • Resend — the email we send: test sends from the editor and contact-form delivery.
  • ImageKit — storing the images you upload for your templates.
  • Sentry — error reports when something in the product breaks.

Plus the hosting provider the application and its database run on. Some of these are outside the UK and EU; where they are, transfers rest on standard contractual clauses or an adequacy decision. We do not sell personal data and do not share it with anyone else, except where the law requires.

5. How long we keep it

  • Your work: for as long as your workspace exists. Deleting a template deletes it and its history; deleting the workspace deletes everything in it, cancels the subscription, and removes the images from the image host.
  • Account data: until you delete your account, which you can do from Settings.
  • Billing records: as long as tax law requires, typically six years.
  • Error reports: 90 days.
  • Contact messages: until answered and no longer needed, at most a year.

6. Your rights

You can see and change your account details in Settings, and take your templates out at any time — the HTML view of every template has a download. You can delete templates, brands, images, keys, workspaces and your account yourself.

Where the law gives you rights to access, correct, erase, restrict or port your data, or to object to processing, write to hello@temply.app and we will act within a month. If you think we have handled your data wrongly you can complain to your data-protection authority.

7. Security

Everything travels over HTTPS. API keys are stored as hashes and shown once. Sessions are managed by Clerk. The database is backed up off the host. No system is perfectly secure; if we learn of a breach affecting you, we will tell you without undue delay.

8. Changes

We will update this policy when the product or the law changes. The date at the top is the date of the current version; for a change that materially affects you we will say so by email or in the product.