What we collect, and what we do with it

This website

This site loads no analytics, no advertising scripts and no third-party embeds. It sets no cookies and stores nothing in your browser beyond the currency you pick on the pricing page, which stays on your device. Fonts are served from this domain, not from a font service. That is why there is no cookie banner: there is nothing to consent to.

The support request form

If you submit the support request form, we receive what you typed: your name, work email, company, what you are after, and your answers about what you are building and what human data you need, plus any optional fields you chose to fill in. We also record the time of the submission, your browser's user-agent string, the page that referred you, and a salted one-way hash of your IP address used only to rate-limit the form. The IP address itself is not stored.

We use this to arrange setup, understand your use case, and reply to you. We do not sell it, share it with third parties for their own purposes, or add you to a marketing list.

Website campaign chat

The campaign chat at app.tellseed.com stores your draft, its questions and a bounded conversation on our server. An essential cookie connects this browser to the draft for up to 24 hours. Examples, manual edits, style presets, previews and statistics run without sending content to a model provider. The chat shows whether AI is available. When enabled, sending a chat message sends that message, your current draft and the recent conversation to OpenAI to generate a reply or proposed edits. Contributor answers and account credentials are not included. Avoid confidential information in the chat.

Pasting a website address, or choosing Website, asks our server to read its public page and a limited number of linked style and logo files. We keep the detected name, description, colours and usable logo with your draft. This import uses no AI calls. If you then use AI chat, the extracted business description and style are included as context; logo bytes are not sent to OpenAI. The websites we request can see our server's visit. Imported draft assets follow the draft and trial retention periods below.

We request that responses are not stored as retrievable API objects. This does not mean zero provider retention: OpenAI may retain abuse-monitoring logs containing prompts and replies for up to 30 days, with exceptions described in itsAPI data controls. API data is not used to train OpenAI models by default. Provider processing may occur outside the EU.

Registering and verifying your email lets you save the draft to your workspace. Publishing a website trial starts its 24-hour collection window. The retention rules below apply to these trials separately from existing Free campaigns and campaigns made through your connected agent.

A hosted workspace

To start a free workspace, you verify your email. We store your email and a hash of a single-use verification token; links expire after 20 minutes. Used proofs are removed on verification and expired proofs are cleared when another signup is requested. Hashed rate-limit identifiers help prevent abuse. Signing in sets an essential browser session cookie for up to 30 days. A separate essential cookie lets you copy your agent connection during that session; the installed agent key remains valid until you replace or revoke it. We store only hashes of these keys on the server. Your email is not added to a marketing list.

If you run a hosted workspace, we hold what you build and what your contributors type: campaigns, the situations in them, the answers, the review decisions, exports, and the brand images you upload. We hold your name and contact email so we can reach you, and a subscription reference if you are on a paid plan.

Your workspace includes an optional question about where you heard about Tellseed. If you answer, we store the category you select and when you saved it with that workspace. We use aggregate counts to understand which sources lead to campaign creation, publication, answers and reviewed exports. This is a self-reported source, not browsing-history tracking. No tracking cookie, page-view event or third-party analytics script is added. You can change your answer or remove it by saving the blank option in your workspace.

All of it lives on a single server we rent in Falkenstein, Germany, inside the EU, backed up nightly to the same server. Encrypted recovery bundles are also created every six hours, uploaded to an operator-controlled Backblaze B2 bucket in the EU, and downloaded to an operator-controlled computer for recovery verification. You are the controller of your contributors' answers; we are your processor, and we act on your instructions.

If you configure automations, we store each key's hash, permissions, campaign scope, expiry and last-use time. Webhook destinations and their signing secrets are stored so we can send signed events to the endpoints you choose. Events contain identifiers and version references, not answer text or contact details. Delivery history is kept for seven days from the event. An integration with results access can retrieve answers, including any optional contact details you collected, or download exports. You choose that access and are responsible for your destination's processing and retention. Disable destinations and revoke keys in your workspace.

Answering on a Tellseed page

If somebody sends you a link to answer questions on a page Tellseed serves, that page keeps what you type, exactly as typed, for the owner of that campaign. It does not ask who you are. You are a random cookie and the hash of it; there is no account, no email address and no login.

Some pages ask what to call you. If you type a name, it is stored with your answers so the owner knows who to thank. It is shown to the owner and to anyone they give a read-only link to. It is never shown to the people reviewing answers, and it never enters a training set. If you want it removed, tell the owner of the campaign, or write to us and say which campaign: the name is erased from every answer you gave, and the answers themselves are untouched.

When we look

Running a hosted service means occasionally needing to see what you see: you report that an export is wrong, or that a page will not load, and we have to look at the campaign rather than guess at it.

We do this only to answer something you asked us about, or to investigate a fault we can see from our side. If we ever need to look for another reason, we will ask you first.

Who else touches it

Each is a processor acting on our instructions, except Paddle: they are the seller of record for a paid plan, so they are a controller of your billing details in their own right and have their own privacy notice. We never see your card number.

How long we keep it

• Workspace requests for up to 12 months after submission, so we can follow up on setup. Requests submitted during the private beta are retained for up to 12 months after the beta ended on 8 September 2026. Rate-limiting records are deleted within an hour; submissions caught by the spam checks are deleted after 30 days.
• Existing Free campaigns, campaigns created through your connected agent, and purchased campaigns and answers until you delete them or ask us to delete the workspace. Cancelling a paid plan does not put previously purchased campaign data into trial cleanup.
• Website chat drafts and unpaid trials: anonymous drafts expire after 24 hours. Saved but unpublished trial campaigns become eligible for deletion seven days after saving. Published unpaid trials become eligible seven days after their 24-hour collection window ends. Scheduled cleanup removes their content and answers, while retaining a content-free audit event and the record that the workspace used its trial. Payment must be confirmed before cleanup; deleted answers cannot be recreated by a later payment. Encrypted recovery copies follow a separate 30-day backup retention schedule.
• Contributor visit state, the cookie-sized record of which situations you have already seen, is derived and rebuildable, and is purged on a timer.

Your data

You can ask us for a copy of what you sent, ask us to correct it, or ask us to delete it. Write to hello@tellseed.com and say so. We will action it and confirm. If you are a contributor rather than an owner, tell us which campaign, and we will pass it on or act on it ourselves depending on what you are asking for.

Tellseed is early. If what we collect changes, this page changes with it before the change takes effect.