Privacy policy
What we keep, and why.
Last updated 16 September 2026
TimsPro runs on the job experiences: a learner spends a workday inside a real role and comes out with evidence of what they can do. That evidence is personal, some of it belongs to minors, and some of it bears on hiring. This policy says what we collect, what we do with it, where it lives, how long, and how to have it removed. Where the product enforces a rule, we say so.
1. Who we are
TimsPro LLC, Florida, United States, operates the TimsPro service at app.timspro.io and this site. For a school, university or employer that uses TimsPro with its own learners or candidates, that organisation decides why the data is processed and TimsPro processes it on the organisation's behalf. For a person who signs in without an organisation, TimsPro is the responsible party. In both cases this policy applies, and questions go to [email protected].
2. What we collect
Identity
- Email address and name, from the sign-in provider you choose (an emailed one-time code, a Google account, or a Microsoft account). We never store a password: sign-in is handled by Microsoft Entra External ID, and the code or the provider's own login does the proving.
- An invitation record: who invited you, into which organisation, as which role, and when it was used. TimsPro is by invitation; nobody can create an account without one.
- A date of adulthood, never a birthdate. At registration we work out the date a learner becomes an adult and keep only that; the service needs to know whether someone is a minor, never how old they are.
Work
- What you write and do inside an experience: replies to colleagues, decisions at each moment of the day, and the deliverable you submit. Work in progress is saved as you go so a day can be paused and resumed.
- Results: the score, the recommendation, the moment-by-moment reasoning behind it, and the exact answer keys it was scored against, so a result can always be explained.
- Authored experiences, if you build them: the role, the day, the cast, the keys, and any source material you upload, such as a job description.
Use
- Usage records: when you signed in, which experience you opened, what was generated or scored, and the computing cost of the AI calls made on your behalf, attributed to you and your organisation. This is what lets an organisation see how the service is used and what it costs.
- Access records: who viewed a result, and when. These are written as it happens and are never deleted, so "did anyone see my work?" always has an answer.
- Technical logs from our hosting and edge providers: IP address, browser type, request time and outcome, kept for security and troubleshooting.
3. How we use it
- To run the experience: present the day, save your work, score it, and show the result to you and to the people entitled to see it.
- To let organisations manage their own people: invitations, roles, and usage.
- To keep the service secure and working: sign-in, abuse prevention, fault-finding.
- To improve the product, using aggregated or de-identified information. We do not sell personal information and we do not use it for advertising.
4. The AI, and what it sees
TimsPro uses a large language model (Claude, made by Anthropic) for two things: writing the day, from the role and source material an author provides, and scoring what a learner wrote against the answer keys the author wrote. Scoring happens on our servers, once, at the end of a day; the learner's browser cannot set a score. The model sees the text needed for the task at hand: the authored keys and the learner's own written responses. We do not send it a learner's name, email address or date of adulthood, and Anthropic does not use content sent through its business API to train its models.
A score is a judgement produced by software against keys written by people. It is evidence, not a verdict. Organisations that use results in hiring or grading are responsible for how they weigh them, and for the notices their own laws require about automated tools.
5. Who sees what
Access follows the organisation, which the product calls an account. A school, a university or an employer is an account, and TimsPro itself is one.
| Person | Sees |
|---|---|
| A learner | Their own work and results. |
| An author or instructor in an account | The account's experiences, and the results of the people who took them. |
| An account's administrator | The account's people, invitations, experiences, results and usage. Nothing of any other account. |
| TimsPro staff | Across accounts, for support and operation. Every view of a result is logged. |
Education work never reaches an employer by rule. A result from a school or university cannot be disclosed to an employer unless an adult, or a verified guardian for a minor, explicitly consents. That is a constraint the database enforces, not a promise in a document.
We share personal information only with the providers below, each under contract and only for the purpose stated. We disclose it otherwise only if the law requires it or to protect someone from harm, and we tell the affected organisation when we are allowed to.
| Provider | Purpose | Data |
|---|---|---|
| Microsoft Azure | Hosting, databases, monitoring | Everything in the service, in the East US 2 region |
| Microsoft Entra External ID | Sign-in | Email address, name, sign-in events |
| Google, Microsoft (optional) | Sign-in, if you choose that button | Your account's email address and name, from that provider to us |
| Anthropic | Writing and scoring days | Authored keys and a learner's written responses; no identity |
| Cloudflare | Network edge, protection against abuse | Request logs, IP address |
| Hostinger | This marketing site only | Request logs for timspro.io |
6. Students and minors
When a school or university uses TimsPro, student work and results are education records. The school controls them; TimsPro acts as the school's service provider under a written agreement, uses the records only to provide the service, and does not use student information for advertising or to build profiles for any purpose other than the service itself. A school may direct us to correct or delete a student's records at any time.
We do not knowingly create accounts for children under 13 except through a school that has authority to consent on a parent's behalf, and we do not ask a learner for more than a name and an email address. A parent or guardian who believes a child has been signed up outside that arrangement can write to [email protected] and we will remove the account.
For a minor, disclosure of a result to anyone outside the school requires a verified guardian's consent, and the minor gains control of that choice on the date they become an adult.
7. Where it is kept
The service runs in Microsoft Azure's East US 2 region, in the United States. Each organisation's work and results live in their own database that is not reachable from the internet; the application reaches it over a private network. This marketing site is served separately and holds no service data.
8. How long we keep it
| Record | Kept |
|---|---|
| Work in progress on a day | 30 days after the last save, then removed |
| Results in an organisation's database | 12 months, then removed |
| A learner's portable record of results | 5 years for work done at a school or university, 12 months otherwise |
| Access records (who viewed a result) | Not deleted |
| Usage records | As long as the organisation's account exists, for reporting |
| Technical logs | Typically 30 to 90 days, by provider |
Expiry is enforced by the service, not by a calendar reminder. Deletion on request happens sooner, below.
9. Your rights
Whatever the law where you live provides, we honour these for everyone:
- Access. Ask for a copy of the personal information we hold about you.
- Correction. Ask us to fix what is wrong.
- Erasure. Ask us to remove you. A deletion request removes a person's runs, results and identity in a single operation, and the record of who viewed a result survives without the name it pointed at.
- Portability. Ask for your results in a machine-readable form.
- Objection. Tell us to stop a use you object to, where the law allows.
Write to [email protected] from the address on your account. We answer within 30 days. If your organisation invited you, we may direct your request to it, since it decides on your records, and we will help it comply. We never treat a request as a reason to change how we serve you.
10. Security
- Every connection is encrypted in transit; the service refuses plain HTTP.
- There are no passwords to lose. Sign-in is by emailed code or a Google or Microsoft account, and the service admits only invited people.
- Sessions end: a Sign out control is on every page, thirty minutes without activity ends a session, and no session lasts more than a day.
- The databases are on a private network with no public address. Secrets are held in a managed vault, not in code or configuration files.
- Access by TimsPro staff is by named account and logged.
We are preparing the assurances schools ask for, including a SOC 2 report and an accessibility conformance report, and will say plainly what is and is not yet in place. If you believe you have found a security problem, write to [email protected]; we read those first.
11. Cookies and browser storage
The service keeps your sign-in session in your browser's local storage and remembers the last moment of activity, so idle sign-out works across tabs. Microsoft's sign-in page sets its own cookies to complete sign-in. Cloudflare sets a cookie used to tell people from automated traffic. Fonts on this site load from Google Fonts. There are no advertising cookies and no third-party analytics on the service.
12. Changes and contact
When this policy changes we update the date at the top and, for changes that matter, tell organisations directly before they take effect. Questions, requests and complaints: [email protected], or TimsPro LLC, Florida, United States. If you are not satisfied with our answer you may complain to the data protection authority where you live.