Your development data.
This notice describes the current product preview and workspace design. The organisation operating a connected workspace determines the purpose, access arrangements and retention period for its team’s data.
The illustrative preview
The public preview uses fictional people, engagements and feedback. Changes are stored in this browser’s local storage. Use fictional information only. You can remove your changes using “Reset demo” in the workspace tab or by clearing this site’s browser storage.
A connected workspace
With Supabase configured, Talentonics stores account email addresses, team rosters, assessment observations, calibration decisions, coaching priorities and checkpoint evidence in Supabase PostgreSQL. Talentonics manages sign-in and database sessions using Auth.js and Prisma. Resend delivers requested sign-in links; Google verifies identity when you choose Google sign-in. The application runs on Vercel. Sign-in cookies are essential for accessing your private workspace and expire after 30 days; signing out removes your current session.
Visibility of feedback
While a cycle collects feedback, reviewers can see their own submissions. Workspace managers can see other perspectives after collection closes. After release, an assessed team member can see their own results and plans. Managers in this version have access across their workspace; separate teams requiring separate manager boundaries should use separate workspaces.
Purpose and context
Use observations relevant to agreed work expectations. Avoid recording health information or other sensitive personal details in free text. Ratings and calibration are human decisions, and the current version does not send observations to an AI provider.
Export, corrections and removal
Signed-in participants can export the records visible to their account. For a correction, access question or deletion request, contact the manager or administrator who invited you to the workspace. Administrators must agree a retention period and an operational process for these requests before collecting real employee information. The initial version preserves original submissions and appends later decisions; a correction workflow and automated retention controls are still to be implemented.
Before using a live pilot
The operator must provide its own controller identity, contact details, applicable terms and complete privacy notice. Live access policies and data handling must be reviewed and tested with the connected environment before employee records are collected.