Effective 13 October 2026. What we store, why, who processes it, and how to get it out.
Website and account data (your name, email, workspace settings, usage of the dashboard) is data we control. Customer Data (your subscribers' records, cancel sessions, offers, emails we send on your behalf) is data you control and we process as your service provider under our terms and, where applicable, a data-processing agreement.
Account details, the configuration you enter, server logs with IP addresses for security and rate limiting, and an audit trail of actions taken in your workspace, including sign-ins and failed sign-ins with their IP address (kept for the audit log’s retention period). The dashboard uses no third-party analytics or advertising pixels, and no analytics or error-tracking service receives your data.
What you connect and send. From your billing: who each customer is (email address and name), their plan, price, seats, status, trial and invoices. From your app: the customer's id, the language they were shown and the one their browser asks for, the events you send, and, for identified customers, page views with the page path and title (set data-pageviews="off" on the widget script to stop them). With each cancel attempt, the region it came from (country, and state in the US, from the hosting platform's location lookup) to apply cancellation rules, the reason picked and what the customer wrote (minimised), and the outcomes of offers. You choose which fields and events to send. When you sign subscriber identity with your widget secret, the widget accepts only a display name from the browser and everything else must come from your server; without signed identity it will also accept a plan label and custom attributes from the page, and those can affect targeting, so sign identity in production.
In short: typing an address on trytenure.co makes Tenure read that site's public home page once; nothing is linked to you, and the count of reads from your IP address is kept one hour. In detail: on trytenure.co, the site field can show a sample cancel screen before making an account. Preview cancel screen keeps you on the page; Draft my plan opens free account setup. The preview uses the site's look when we can read it, or Tenure's default look when we cannot. Tenure's servers then read that site's public home page (and a sign-in page it links to, for its look) with their stylesheets, under the same rules as setup's read, and send back only the look, the site's name and the address of its logo. No Firecrawl, no AI model and no account are involved. The read is kept in server memory and by the hosting CDN for up to 6 hours (10 minutes when the site couldn't be read), so the same site isn't read again; if you then sign up with that site, setup may reuse it. Your IP address (for IPv6, its /64 network) is used only to count how many sites you have us read, up to 6 an hour: the count is kept for that hour and isn't linked to an account or to the site you typed. Your browser loads the site's logo directly from that site.
Tenure is hosted on Vercel with a Supabase Postgres database (see International transfers). Each subprocessor above is on Tenure's own account. The services you connect (Stripe or Chargebee for billing, and your own Resend for customer email) are yours: Tenure sends them what billing changes and email delivery need, with your credentials; with your own billing, that billing data goes, signed, to your own billing service or backend instead. Tenure doesn't train models on your customers' data. TypeSafe and OpenAI process what they receive under their API terms; whether those terms allow training, and how long they keep inputs, isn't yet confirmed for Tenure's accounts, so ask us before sending customer text. No analytics or error-tracking service receives your data.
TypeSafe (typesafe.ai)
OpenAI
Firecrawl (firecrawl.dev)
Resend (Tenure's own account)
Vercel
Supabase
Cancel sessions are kept for as long as your workspace exists so Results can report outcomes over time. Customers' typed words are kept, minimised, for 180 days. The churn report's history of your past cancellations is deleted 25 months after each subscription ended, and the comments customers typed when cancelling in Stripe's customer portal are kept, minimised, for at most 180 days. Audit events are kept for the retention period set on your workspace (365 days by default, or forever if you set it to 0) and are purged nightly past that age. Webhook delivery payloads are removed after 90 days. You can erase any individual customer with all their sessions from the dashboard ("Erase customer" on the customer page); erasure also removes their references from the audit log. The data-subject API exports a customer's data; it does not erase. Deleting your workspace removes all of it at once; copies in the database provider's backups remain until those backups expire. Password-reset and invite tokens expire automatically.
Passwords are hashed with bcrypt; API keys are stored as hashes; session cookies are encrypted and HttpOnly; connected secrets are encrypted at rest; outbound webhooks are signed; widget identity can be signed with a per-workspace secret; billing changes need an explicit acceptance and are never applied twice. Report vulnerabilities to security@trytenure.co.
Workspace owners and admins can export their workspace, and owners can delete it. Account holders can leave a workspace at any time (an owner first hands ownership to someone else); leaving their last workspace deletes their Tenure sign-in. For Customer Data, requests from your subscribers should be directed to you as controller; the data-subject endpoint lets you fulfil access requests in seconds, and erasure requests are fulfilled from the dashboard.
OpenAI drafts your plan and customer wording from your site, turns changes you describe in words into proposed changes to your offers, suggests a tone of voice, drafts your check-in sentences and translates customer wording, each with only the fields that task needs and nothing about your customers. A check-in shows each customer's numbers in sentences you approved; Tenure fills the numbers in itself. The one time a customer's words go to OpenAI is when you click Draft an answer beside their unanswered question in Help cards: that question, with names, email addresses, links, phone numbers and long numbers removed, goes with your docs, and never while “What they write” is switched off. Feedback grouping uses TypeSafe. Standard setup templates, eligibility checks and recorded outcome explanations run in code. Tenure doesn't train models on your customers' data. TypeSafe and OpenAI process what they receive under their API terms; whether those terms allow training, and how long they keep inputs, isn't yet confirmed for Tenure's accounts, so ask us before sending customer text. You can disable “What they write” in Settings › Customer data and privacy; this stops customer-text processing, not all model processing.
The hosted service stores your data in the United States: the application runs on Vercel (Portland, Oregon) and the database on Supabase (US West, Oregon). Data is transferred to the subprocessors described above as needed for the features you use.
Privacy questions: privacy@trytenure.co. Security issues: security@trytenure.co.