Last updated: October 2026.
Trust & Data
This page states how Curriculo Inc. handles data in product demonstrations. It applies to every environment we run: production, demo, staging, preview, developer machines, and CI.
The rule
No real candidate data in any demo environment. Synthetic or fixture data only. Our public demo surface stays behind the signed-out redirect unless a later ruling re-enables it.
That rule does not depend on whether a demo page is public today. It applies the moment demo data exists anywhere.
What counts as real candidate data
Any data that identifies, or could identify, a real person or a real customer record:
- names, email addresses, phone numbers, postal addresses, or profile links of real candidates or applicants;
- real resumes, cover letters, interview notes, or screening transcripts;
- real customer or organisation names, job titles, or mailbox content;
- production exports, database dumps, screenshots of production screens, or pseudonymised copies that still carry a re-identification key.
Fixture data means records written by hand or generated deterministically with no provenance from a real person: reserved documentation domains such as example.com, reserved phone ranges, invented names, and an explicit seed marker.
How our demo works today
The unauthenticated demo application shell was removed in 2026 after real candidate data was exposed on a public demo page. Demo URLs at ats.curriculo.me now redirect to the sign-in page, before any routing rule can serve them as customer pages. The removed routes, mock data, and demo providers are pinned by automated tests so they cannot be reintroduced silently.
If we bring a demo back
A future ruling may re-enable a demonstration surface. If that happens, all of the following apply before it ships:
- demo records are checked in as a static fixture and generated by a checked-in script with a fixed seed, so reruns are byte-identical;
- the demo page imports only the fixture and local components, with no API client, no data hooks, and no network calls;
- automated tests pin the page isolation and the fixture hygiene;
- every other retired demo path still redirects to sign-in;
- no value in the fixture is derived from production data. Pseudonymised production data is not a substitute for synthetic data.
How we enforce it
Pull requests that touch demo pages, demo fixtures, or demo routing must cite the rule. Automated guard suites run in CI, and a failing guard blocks the change. Copying production data into any non-production environment is prohibited, which extends our existing environment-segregation control.
Changing this policy
Only a new documented ruling revisits this policy. A later decision to allow real data in a demo would be that new ruling, recorded and reviewed on its own, rather than an exception applied quietly to an existing page.
Questions
Contact [email protected] with the subject line "Demo Data Policy".