Privacy Policy
What Sourceteller collects, why, who else touches it, and how to get rid of it.
Last updated 14 September 2026
Who operates Sourceteller
Sourceteller, the operator of sourceteller.com, is the data controller for the data described in this policy. Contact: support@sourceteller.com .
That address is also the contact for anything in this policy — access requests, deletion, corrections, or a complaint. There is no separate privacy desk; the person who built the system answers it.
Two kinds of data, kept apart
Your account data is what you give us to have an account at all: your email address, your name if you provide one, your workspace name and settings, and a record of what you bought.
Your workspace content is what you put into the product — the documents you upload, the websites you ask us to read, the questions asked of your assistant and the answers it gives. This is yours. We process it to run the service you are paying for and for nothing else.
What we collect
Account and billing
- Email address and sign-in credentials, handled by Firebase Authentication
- Workspace name and settings
- How you found us — the campaign link or referring site of your first and last visit before signing up
- Purchase records — what was bought, when, and the payment reference. We never see or store your card details. Payments go through Creem, who act as merchant of record; your card is handled on their systems, not ours.
Workspace content
- Documents you upload, and the text extracted from them
- Content from websites you ask us to crawl
- Conversations — questions, answers, and which sources were cited
- Usage counts, so the credit and parse-page meters work
Voice and phone calls
If you enable voice or a phone line, we store the caller's phone number and the text of the conversation, so the call appears in your workspace's history alongside chat. Call audio is never recorded or retained — speech is converted to text as the call happens and the audio is discarded.
Callers to your phone line are usually your customers rather than ours. You are responsible for telling them their call is answered by an automated assistant and that a transcript is kept, as your local law requires.
Technical logs
Ordinary server logs — IP address, timestamp, which endpoint was called, whether it succeeded. Used to keep the service running and to investigate abuse. Not used to build a profile of you.
We run no advertising, no third-party analytics trackers, and no cross-site tracking of any kind. There are no advertising cookies. The only cookies and browser storage we use are the ones that keep you signed in and remember your interface preferences.
Your content is never used to train models
Your documents, questions and answers are never used to train any AI model — not ours, not a provider's. We do not sell your data, rent it, or share it for advertising. The AI providers we use are contractually barred from training on data sent through their APIs.
Every workspace's search index is separate, keyed to a fixed internal identifier. There is no shared pool of documents across customers.
Who else processes it
Running the service means some data passes through other companies. This is the full list. Each one sees only what its job requires.
| Provider | What it does | What it sees |
|---|---|---|
| OpenAI | Generates answers, creates search embeddings | Document passages and questions, at the moment of answering |
| Qdrant Cloud | Stores the search index | Document passages and their embeddings |
| Google Firebase | Sign-in, and the database behind workspaces | Account details, settings, conversations, usage |
| Railway | Runs the application servers | Data in transit while a request is being served |
| Daily.co | Carries voice and phone-call audio | Live call audio and the caller's number. Nothing retained by us |
| Speechmatics | Converts speech to text | Call audio as it is spoken |
| Cartesia | Converts the answer back to speech | The text being spoken aloud |
| Resend | Sends service email | Your email address and the message |
| Creem | Processes payments as merchant of record | Your billing details and payment. Never passed to us |
We update this list when it changes. If a provider is added that materially changes how your data is handled, we will say so before it takes effect.
Where it is stored
Primarily in the United States, on the cloud services listed above. We run no servers of our own. Because our providers operate globally, data may be processed in other countries; each is bound by its own contract to protect it.
Data is encrypted in transit using TLS, and encrypted at rest by the providers holding it.
How long we keep it
Until you delete it. Your documents, conversations and settings stay for as long as your workspace exists. We do not expire or purge content on a schedule.
Delete a document and it goes, along with everything indexed from it. Delete your account and everything goes — the process is described on our account deletion page.
Two exceptions, both narrow. Payment records are kept for up to seven years where tax and accounting law requires it; they contain the transaction and billing name only, never your documents or conversations. And encrypted backups may hold residual copies for up to thirty days before being overwritten on their normal rotation.
Your rights
You can, at any time:
- See what we hold — most of it is visible in your console; email us for the rest
- Correct it — account and workspace details are editable in settings
- Delete it — individual documents and conversations, or the whole account
- Object — tell us to stop processing, understanding that this usually means closing the account
Email support@sourceteller.com from the address on the account. We respond within one business day and complete requests within thirty days.
Where your assistant answers questions from your own customers, you are the controller of that data and we process it on your behalf under these terms.
Children
Sourceteller is a business product and is not directed at children. We do not knowingly collect data from anyone under 16. If you believe a child's data has reached us, email us and we will remove it.
Changes to this policy
We will post the new version here with a new date, and email account owners before anything material takes effect. Continuing to use the service after that means accepting the change.