Personal information governance policy
OralReady · Houssem Ben Salem
Version 1.0 · Approved on November 8, 2026 by Owner, person in charge of the protection of personal information · Effective November 8, 2026
This policy describes how we govern personal information through its whole life cycle: collection, use, communication, retention and destruction. It fits our size: a sole proprietorship with no employees and no user accounts. Our Privacy policy explains what information we collect and why.
1. Scope
This policy applies to all personal information we hold for OralReady, or that our service providers process for us. That is the information of people who practise, buy a pass or write to us.
2. Roles and responsibilities
| Role | Who | Responsibilities |
|---|---|---|
| Person in charge of the protection of personal information | The operator (Owner), who has the highest authority in the business | Approve this policy and make sure it is applied. Answer access, correction and portability requests. Handle complaints and review requests. Manage incidents and keep the register. Carry out privacy impact assessments. Choose providers and sign the written agreements. This role can be delegated in writing. |
| Access to personal information | The operator only | No one else in the business has access. |
| Service providers | Cloudflare (hosting, server, temporary storage, audience measurement); OpenAI (transcription); Anthropic (grading); Stripe (payment, and an independent controller for its own purposes); Zoho Mail (email) | Process the information only for the task given, under a written agreement. Protect its confidentiality. Not keep it after the mandate ends. Notify us of an incident. |
| People who use the service | You | You control the data kept in your browser (consent, history, access code) and can delete it. |
What we do at each stage
| Stage | What we do |
|---|---|
| Collection | We collect only what we need. Before the first recording, we ask for express consent, separate from the terms of use. No profiling function is on by default: the estimate starts only after a click on "Get my estimate". Before each mock, we remind people not to give their name, their department or details about other people. |
| Use | We use the information only for the stated purposes. We train no AI model on your answers. We won't add a feature that keeps transcripts to improve the service without separate consent and a documented anonymization method. |
| Communication | We communicate information only to the named providers, under a written agreement. Before any communication outside Québec, we carry out a privacy impact assessment (section 8). We sell no information. |
| Retention | We follow the schedule in section 3. The most protective settings apply by default, for example history kept for the session only. |
| Destruction | Deletion is automatic where possible (scheduled expiry). Otherwise, we destroy the information as set out in section 3. We anonymize information only under the criteria set by regulation, and for serious and legitimate purposes. Otherwise, we destroy it. |
3. Retention and destruction schedule
| Information | Where | Minimum | Maximum | How it is destroyed |
|---|---|---|---|---|
| Raw audio | Server memory, then the transcription provider | 0 | Us: 0 (never saved). OpenAI: no retention. | Never written to disk, storage or logs; checked by code review |
| Transcripts | Server memory, then Anthropic; your browser | 0 | Our server: none. Anthropic: 30 days. | Returned to the browser only; deleted by Anthropic |
| Result (estimated level and feedback) | Cloudflare KV | 0 | 1 hour | Automatic expiry (3,600 seconds at most) |
| Result history | Your browser | 0 | Last 10 mocks; session only, unless you choose to keep it | "Delete my history" button; end of session |
| Hashed IP address (changing key) | Cloudflare KV | 0 | 48 hours | Automatic expiry (172,800 seconds at most); key changed at least every 48 hours |
| Technical counters (pass, recordings, limits) | Cloudflare KV | 0 | 48 hours. For a pass: paid mocks, 8 days after the first; refund status, 24 hours or, if it is refunded, until it would have ended; turned off, 90 days. | Automatic expiry |
| Server logs | Cloudflare | 0 | Not stored; nothing from answers, no name, email or IP address, no link to a payment | A coding rule that bans writing personal information to logs |
| Pass and access code | Your browser; the code is also on the Stripe invoice | Length of the pass | End of the pass (invoice: like payment records) | The pass holds only an ID, an end date and a signature. You can remove it at any time. |
| Consent | Your browser | Until withdrawn | Until withdrawn | "Withdraw my consent" button |
| Payment records | Stripe; our monthly exports, kept in Canada | 6 years after the end of the tax year (tax requirement) | 6 years plus 1 year | Yearly deletion of expired exports. Stripe applies its own policy. |
| Access-request, complaint and support emails | Mailbox | Until the file is closed | 24 months after closing | Automatic deletion rule in the mailbox |
| Incident register | Operator | 5 years (Québec), which covers the 24 months federal law requires | 5 years | Entries older than 5 years deleted |
4. Access, correction and portability requests
- The request is made in writing to the person in charge, at [email protected] or 2000, rue Saint-Marc, app. 905, Montréal (Québec) H3H 2N9.
- The person in charge checks the requester's identity without asking for more than needed.
- They look for the information at Stripe (using the purchase email), in the mailbox and on the server, which holds data only for short periods. They provide it in a structured, commonly used format.
- They answer in writing within 30 days of receipt. If there is no answer by then, the law treats the request as refused, and the requester can apply to the Commission d'accès à l'information.
- They log each request: date, type, date of the answer.
- They adapt how access is given for people with disabilities.
5. Review of an automated estimate
- Anyone can submit comments on an estimate and ask for a review by a person, with the "Ask for a review" button or by email.
- The person in charge looks at the information provided (for example, the printed report), the criteria and the estimate. They correct the information used if needed, for example a transcription error.
- They answer within 30 days, with the reasons and main factors behind the estimate.
- Reviews are free.
6. Complaint handling
- Make a complaint. Write to [email protected] (subject: "Complaint") or by mail to 2000, rue Saint-Marc, app. 905, Montréal (Québec) H3H 2N9, to the attention of the person in charge of the protection of personal information. Describe the problem and what you would like.
- Acknowledgement. We acknowledge receipt within 5 business days, with a file number.
- Review. The person in charge looks into the complaint and may ask you questions.
- Answer. We send you a written answer, with reasons, within 30 days of receiving the complaint.
- Recourse. If our answer doesn't satisfy you, you can contact the Commission d'accès à l'information du Québec (www.cai.gouv.qc.ca) or the Office of the Privacy Commissioner of Canada (www.priv.gc.ca).
Complaints are handled free of charge. We keep the file for 24 months after closing it.
7. Confidentiality incidents
A confidentiality incident is, for example, unauthorized access to personal information, or its loss. This is what we do:
- Reduce the risk. As soon as we have reason to believe an incident happened, we take reasonable steps to reduce the risk of injury and prevent it from happening again.
- Assess the risk. We consider how sensitive the information is, the possible consequences, and how likely it is to be misused.
- Notify. If the risk of injury is serious, we promptly notify the Commission d'accès à l'information and the people concerned. If the incident creates a real risk of significant harm under federal law, we report it to the Office of the Privacy Commissioner of Canada and notify the people concerned.
- Record. We record every incident in the register, even if it creates no serious risk: description, circumstances, dates, number of people affected, risk assessment, notices sent and steps taken. We keep each entry for 5 years.
- Providers. Our providers must notify us of an incident: OpenAI and Cloudflare without undue delay.
8. Privacy impact assessments (PIAs)
When. We carry out a PIA:
- before launch;
- before acquiring, developing or overhauling a system that handles personal information;
- before communicating personal information outside Québec, or entrusting it to a provider outside Québec;
- before any change of provider or model, for example a new transcription model.
How. We follow the report template of the Commission d'accès à l'information, scaled to our size. For each provider, the PIA describes:
- the information, the purpose, the location and the retention period;
- use for training AI models;
- the written agreement (version and date);
- the legal framework of the destination country, including access by authorities;
- the protection measures, the residual risk and the decision.
It also documents:
- why the biometric rules don't apply: we identify no one by voice and create no voiceprint database;
- why we treat spoken answers as sensitive information;
- the limits of the agreements, which mention neither Québec nor Canada.
We communicate information outside Québec only if the PIA concludes it will be adequately protected, and under a written agreement that reflects it. The person in charge approves and dates each PIA. Current version: 1.0, November 8, 2026.
9. Written agreements with our providers
| Provider | Agreement | Version |
|---|---|---|
| OpenAI | Data Processing Addendum, part of the services agreement | Effective January 1, 2026 |
| Anthropic | Commercial Terms, which incorporate the data processing addendum by reference | Effective June 17, 2025 |
| Cloudflare | Customer DPA, version 6.4, part of the Main Agreement | Effective April 3, 2026 |
| Stripe | Services Agreement and privacy policy | 2026-09-28 |
| Zoho Mail | Terms of Service + Privacy Policy | 2022-03-02 + 2025-12-22 |
We review these agreements at each PIA.
10. Review of this policy
The person in charge reviews this policy every year and before any change of provider or model. Each version is approved, dated and published on this page.
| Version | Approval date | Changes |
|---|---|---|
| 1.0 | November 8, 2026 | First version |