No AI training
We do not train or fine-tune AI models on your data.
What we keep, why we need it, and how you stay in control.
Last updated:
We do not train or fine-tune AI models on your data.
View saved practice in your account and request a full data copy.
Ask us to delete your account and personal information.
Rehearse My Conversation provides AI conversation practice and feedback. This notice explains how we handle personal information when you use the service or contact us.
For privacy questions or to exercise your rights, use our privacy contact form.
We use your information to run your account, provide the practice you ask for, generate feedback, save your history, process payments, respond to messages, and keep the service secure and working. We do not sell your personal information or use your practice content for advertising.
We do not use your data to train or fine-tune AI models. Using an AI model to respond to your conversation or produce feedback is part of delivering your practice; it does not mean we train that model on your data.
When you ask AI to create a briefing, your notes and extracted reference documents are sent to Ollama Cloud. If you provide a public link, its URL is sent to Ollama’s web search and page-reading services; personal notes and uploaded documents are not used as web search queries. The retrieved text helps generate an editable draft and can be included as a practice reference.
Conversation content is sent to Google Gemini for live practice. Your transcript and briefing are sent to Ollama Cloud for conversation review and feedback, together with limited camera samples when you enable visual feedback. These providers process the content needed to deliver those features.
Google’s paid-service terms say prompts and responses are not used to improve its products; its unpaid-service terms differ outside the UK, EEA and Switzerland. Ollama’s privacy policy says cloud prompts and responses are processed transiently and are not used for training. Provider handling follows the terms applicable to the service and account used.
You can see your account details in Account settings, your saved transcripts and feedback in My sessions, and your plan and payment information in Billing. The table below explains the other records involved.
| Information | Purpose and retention |
|---|---|
| Account and sign-in | Name, email, account identifier, sign-in providers, verification status and account timestamps. Firebase handles authentication credentials. We retain your account records so you can sign in and manage your account. |
| Saved scenario briefings | Your latest situation, practice focus, custom practice name, AI drafting notes, reference link and extracted document text are saved privately to your account for each scenario. They are restored for future setup, including on another device. Updates replace that scenario’s latest draft; there is no automatic expiry. Original uploaded files and camera samples are not stored with these drafts. |
| Saved practice | Conversation transcripts, feedback, scores, scenario and partner choices, difficulty, language, duration and session timestamps. These are retained for your session history and progress until deletion is requested; there is currently no automatic expiry for saved sessions. |
| Billing and allowance | Payment and subscription references, plan, billing periods, payment status, practice usage and remaining allowance. Stripe processes card details; we do not store your full card number or security code. Records support your purchases, service allowance, accounting and payment disputes. |
| Messages you send us | Contact details, enquiries, privacy requests and product feedback, including optional company details, rating or session reference. Copies and delivery status are retained in our support records and email inbox to respond and follow up. |
| Activity and technical records | Practice visits and selections, random visit/session identifiers, session duration, end reason and completed transcript text are also written to operational logs. Hosting and service providers may process IP addresses, request information and error/security logs. These help diagnose failures and protect the service. |
| Optional website analytics and advertising | If you accept the relevant cookies, Google Analytics measures public website visits and approximate countries derived from IP addresses. Meta Pixel measures public marketing-page visits for advertising. These services use browser identifiers and device/network information. The cookie details below explain the providers, choices and durations. |
| Briefings, documents, microphone and camera | Context, instructions and extracted document text are processed for your practice and feedback. Microphone audio and optional camera frames are sent to Gemini. Limited camera samples may be sent to Ollama for visual feedback. We do not save raw audio/video recordings, camera samples or uploaded document originals in your session history. Transcripts and reports may include information from them. |
Account, session, support and billing records do not currently have a single fixed automatic deletion period. We keep them for the purposes above, subject to your deletion rights. Operational logs, backups and payment-provider records follow the relevant provider’s retention settings and legal requirements. Ask us for the retention details for your records.
To prevent repeated free trials, we keep keyed hashes of verified email addresses, Google or Apple account identifiers, and a random browser identifier for up to 365 days. These records are held separately from your account, so deleting and recreating an account does not reset free-trial eligibility. We keep network and request-rate records for up to 24 hours. These identifiers remain personal information where they can be linked to you; they are not used for advertising. Expired records are removed by a scheduled cleanup. Contact us if you believe a limit has affected you incorrectly or to exercise your privacy rights.
You can request a copy of all personal information we retain about you, including support, usage and identifiable operational records that are not displayed in your account. Passwords, security secrets and other people’s information are excluded or redacted where necessary.
Saved transcripts and feedback are currently held in private Backblaze storage in its EU Central region in Amsterdam, the Netherlands. Account details and session metadata are stored using Firebase/Firestore. Authentication, AI processing, payments, hosting and email use provider-operated systems, which may process information outside the UK.
Our providers include Google Firebase and Gemini, Backblaze, Ollama Cloud, Stripe, and our hosting and email providers. With your cookie permission, Google Analytics and Meta also receive the website tracking information described below. We share the information necessary for their role. Authorised operators may access records for support, security, administration and privacy requests. We may also disclose information where required by law or to protect legal rights.
Some providers may process information outside the UK. Where UK data protection law requires safeguards for those transfers, appropriate contractual or other legally recognised safeguards are required. Contact us for details of the providers, locations and transfer arrangements relevant to your data.
Account data is accessed through authenticated requests, connections use HTTPS in production, and saved transcript and feedback storage is private and encrypted. Access is restricted to the people and systems that need it.
We rely on performance of our contract with you for accounts, practice, feedback, saved history and purchased services. Our legitimate interests in operating a reliable, secure service support troubleshooting, abuse prevention and handling support messages, subject to your interests and rights. Legal obligations cover records and disclosures required by law. Optional website analytics and advertising tracking rely on your consent, which you can withdraw in Cookie settings.
You choose whether to enable your microphone or camera and what material to share. You can turn these features off and use text practice. Browser permission controls device access. Where processing requires consent under applicable law, you can withdraw that consent without affecting earlier lawful processing.
Do not upload information you are not entitled to share. Avoid unnecessary sensitive personal information about yourself or anyone else. If we cannot process the account or practice information needed for a feature, that feature may not work.
You can request access to your information or request deletion at any time. Use the buttons below or our privacy contact form. You do not need an active paid plan to make a request.
Include the email address linked to your account and describe what you need. We may ask for reasonable verification before disclosing or deleting information. Sending a request does not immediately delete your account. We will explain the scope, any necessary identity checks and the outcome.
We normally respond within one month, subject to the rules on identity verification and permitted extensions for complex or multiple requests. Requests are normally free. If an extension, charge or refusal is permitted by law, we will explain why.
A deletion request covers the personal information we hold about you, including saved sessions, scenario briefings and their reference text, support records and identifiable logs. We may retain limited information where necessary for legal obligations, security or legal claims, and will explain any exception. Copies in backups or retained object versions are addressed as part of deletion; deletion from the account screen alone would not remove every copy.
Depending on the circumstances, you may also request correction, restriction, portability or object to processing based on legitimate interests. Feedback is a practice aid; we do not use it to make automated decisions with legal or similarly significant effects about you.
You may complain to the UK Information Commissioner’s Office (ICO) or your local data protection authority. You can contact us first, but you do not have to.