Trust & privacy
Your documents. Your data. Your control.
Recitare is built privacy-first: encrypted storage, automatic PII redaction, no AI training on your content, and delete-anytime control.
Six protections
How Recitare protects your work
Built into every interaction, not switched on by request.
- PII Privacy Shield
- Recitare automatically scans for sensitive data (Social Security and National Insurance numbers, phone numbers in US, UK and international formats, email addresses, credit cards, IBANs, street addresses and postcodes) and replaces it with [PROTECTED] placeholders before your text is sent for AI analysis: questions, summaries, and study guides. For documents about other people, optional Name Protection hides personal names too. Text sent for speech synthesis is spoken exactly as written, so it is protected by our providers' no-training terms rather than redaction.
- No AI model training
- Your documents are not used to train Google Gemini, Anthropic Claude, or any other AI model. Their API terms prohibit training on submitted data. For repeat questions on the same document, text may be briefly cached by the AI provider (up to about 30 minutes) to speed up responses, then discarded.
- Encrypted in transit and at rest
- All data transmitted between your browser and our servers uses TLS 1.2+ encryption. Documents stored in our database are encrypted at rest. Your content travels through secure channels at every step.
- Your activity, visible to you
- You can review a history of the AI actions run on your documents: what ran, when, and with which model, any time from your account. Built so you can verify what ran, not so we can watch you.
- Your data, your control
- Delete any document, summary, or your entire account at any time. Deleted items enter a 30-day recovery window, then are permanently erased: documents, cached audio, and AI outputs alike. Your subscription, your data, your rules.
- Verified AI outputs
- Recitare cites specific page numbers when generating summaries and study guides. Every claim links back to your source document, so you can verify the work rather than take it on trust.
For interviews and participant data
Name Protection
Pattern matching can recognise a phone number. It cannot recognise a name. For transcripts and other documents about real people, tick Protect names in this document when you upload, or switch it on later from the Study tools menu in the reader.
Names are picked out in your browser, not on our servers
A small language model runs inside your browser and picks out the personal names. Your document is not sent anywhere for this step. The model is downloaded once from Hugging Face, then kept in your browser.
AI analysis sees tokens, not names
Before a question, summary, study guide or library search goes to our AI providers, each name is swapped for a neutral token such as [PERSON_3fa9c1b20d4e].
You still see the real names
The swap happens on our server, at the single point where text leaves for an AI provider, and the names are put back before the answer reaches you. The list of names is stored with your document, which already contains them, and is deleted with it.
What it does not cover
- Read-aloud.
- Speech synthesis has to receive the text as written, so names are spoken. That text is covered by our providers' no-training terms instead.
- Pictures.
- A Snap sends an image of the area you select, and text inside an image cannot be swapped out. Recitare asks before the first Snap on a protected document.
- Your stored document.
- It is kept encrypted with the names intact, so that you can read it. You can delete it at any time.
- Missed names.
- Detection is tuned for English and can miss unusual names or spellings. Treat it as a safeguard alongside your ethics approval, not as a substitute for anonymising data your protocol requires you to anonymise.
- A short wait at the start.
- Until the names have been found, usually a minute or two after upload, Recitare pauses AI features on all your documents rather than run anything unprotected. Scanned pages of a protected upload are read on your device instead of by a cloud model, which is slower, and figure descriptions are skipped.
- Switching it on later.
- Protection starts from that moment. Anything the document already sent for AI analysis cannot be recalled.
Who processes your text
Three providers, named.
Every AI provider we work with is held to the same terms: your content is processed for you, and not used to train their models.
- We do not sell your data.
- AI providers do not train on your content.
- Automatic PII redaction runs before AI analysis, and optional Name Protection hides personal names too.
- You can export or delete your data at any time.
| Provider | Purpose | Data policy |
|---|---|---|
| Google Gemini | Document analysis, summaries, study guides, questions | Not used to train models |
| Inworld | Text-to-speech on every plan | Real-time synthesis, not used for training |
| Anthropic Claude | Image and diagram analysis | Not used to train models |
Questions
Privacy, answered straight.
Where are my documents stored?
Documents are stored in our encrypted database hosted on Turso (SQLite). They are encrypted at rest and in transit. You can delete any document at any time from your account.
Does Recitare train AI models on my documents?
No. Your documents are not used to train Google Gemini, Anthropic Claude, or any other AI model; their API terms prohibit it. Text may be briefly cached by the provider (up to about 30 minutes) to make repeat questions on the same document faster, then discarded.
What personal information does Recitare redact?
Before your text is sent for AI analysis (questions, summaries, study guides), Recitare automatically scans for and replaces Social Security numbers, UK National Insurance numbers, labelled NHS numbers, phone numbers (US, UK and international formats), email addresses, credit card numbers, IBANs, street addresses, UK postcodes within an address, and dates of birth with [PROTECTED] placeholders. Pattern matching cannot recognise a person's name, which is what Name Protection is for (see the next question). Text sent for speech synthesis is spoken exactly as written, so it is protected by our providers' no-training terms rather than redaction.
How does Name Protection work, and what does it not cover?
Tick “Protect names in this document” when you upload, or switch it on later from the Study tools menu in the reader. A small language model then runs inside your browser and finds the personal names; your document is not sent anywhere for that step. The list is saved with your document, and from then on each name is swapped for a neutral token on our server before a question, summary, study guide or library search goes to our AI providers, and swapped back before the answer reaches you. Until the names have been found, usually a minute or two, Recitare pauses AI features on all your documents rather than run anything unprotected. What it does not cover: read-aloud still speaks the names, because speech synthesis needs the text as written; a Snap sends a picture, and text inside a picture cannot be swapped out, so Recitare asks before the first Snap on a protected document; and your stored document keeps its names so that you can read it. Detection is tuned for English and can miss unusual names, so treat it as a safeguard alongside your ethics approval, not as a substitute for anonymising data your protocol requires you to anonymise. Switching it on later cannot recall anything already sent.
Can I upload interview transcripts or other participant data?
That decision belongs to your ethics approval, not to us. Your ethics committee or data-management plan determines whether participant data may be processed by a cloud service. What we can do is hand you the exact processing chain to take to them: your text is stored encrypted on Turso, processed only by the AI providers named above (Google Gemini, Anthropic Claude, Inworld) under terms that prohibit training on your data, scanned by our automatic redaction before AI analysis (with optional Name Protection, which finds personal names on your own device and hides them from AI analysis), and permanently deletable by you at any time. If your protocol needs more detail, email support@recitare.app before uploading. We are happy to answer your data-protection office's questions directly.
Can I see what the AI has accessed?
Yes. Every AI interaction is recorded in an activity log with timestamps, model versions, and content hashes. You can review your complete activity history from your account at any time.
What happens when I delete my account?
Delete your account from Account, then Security. It is deactivated immediately, your subscription is canceled at once, and everything (all documents and their original files, cached audio, summaries, chat history, bookmarks, API tokens, and activity logs) is permanently erased within 30 days. Sign back in within 30 days to cancel and restore everything. Payment records are held by Stripe for legal compliance. One thing we keep: anonymous feature-usage counts (for example, how many times an export button was clicked) with no name, email, documents, or content attached. Once your account is erased, these can no longer be linked to you.
Is my data shared with third parties?
No. We do not sell, share, or provide your data to any third party. The only external services that process your text are the AI providers listed above (Google Gemini, Anthropic Claude, Inworld), under API terms that prohibit training on your data.
What is my Reading Record and what does it store?
As you listen, Recitare quietly keeps a per-paper reading record: which passages you listened to, where you stopped, figures you snapped, and questions you asked, plus an AI-generated capsule (title, one-line summary, key terms). It exists so the app can do useful things for you: resume exactly where you left off, show what each paper was about in your library, and send you an optional next-day recap with a quick recall prompt. It is visible to you in your library, never shared, and never used to train AI models. Recap emails have a one-click unsubscribe. When you delete a document (or your account), its reading record and all its events are permanently erased with it in the same 30-day purge.
How are AI-generated outputs verified?
Recitare cites specific page numbers (for example, [Page 3]) when generating summaries and study guides. Every claim links back to your source document so you can verify the output against the original text.
How does Recitare keep the AI from hallucinating?
Several layers work together. Listening is verbatim: Recitare reads the exact words in your document, so playback cannot invent anything. For answers, summaries, and study guides, the AI works only from the document you uploaded, not the open web, so responses stay grounded in your source. Every specific claim cites its page (for example, [Page 3]) so you can check it against the original, and the AI is instructed to say when something is not in the document rather than guess. Each answer also carries a confidence indicator, computed from grounding signals such as hedging and coverage, that flags responses worth double-checking. No AI is perfect, so we make outputs traceable and checkable rather than ask you to take them on faith.
What encryption does Recitare use?
All data transmitted between your browser and our servers uses TLS 1.2+ encryption. Documents stored in our database are encrypted at rest. Generated audio is cached securely so replays are instant, and is removed when you delete the document.
Questions about security?
We are happy to walk you or your data-protection office through the architecture and data handling.