Private while you create
A draft is not available to hiring managers until you deliberately publish it.
Privacy and voice data
Your voice should stay in your control
Recording your voice is personal. This page explains what intro.id needs, what sharing an unlisted introduction really means, and which details still need to be agreed before a pilot.
Product explanation—not final legal terms. This page describes the intended MVP and current local prototype. Legal review, retention periods, provider terms and a privacy contact must be completed before real candidate data is collected.
At a glance
The practical version
Unlisted is not secret
Listeners need the published link and six-digit code. A recipient can still forward both.
You can change your mind
You can unpublish or permanently delete your introduction from your controls.
What we collect
To create an introduction, intro.id needs the information you enter and the recording you choose to make.
- Your name, professional headline and short context.
- Your audio recording and its duration.
- Your chosen contact email and optional professional link.
- Your publishing choice and the consent record associated with it.
- Basic technical information needed to operate and protect the service.
Current prototype behaviour
Profile details and draft audio are recoverable on this device. When you publish, profile information and the recording are stored in the connected Supabase project.
How it is used
We use this information to let you record, review, publish, share, manage and delete your introduction.
We do not intend to use your recording for personality analysis, emotion detection, candidate scoring, advertising, or training a general-purpose AI model.
Decision and legal review needed
Transcripts are deferred from the MVP. Before adding them, we must select a provider, confirm its processing and retention terms, and restore a reviewed text alternative for accessibility.
Who can access an unlisted introduction
While you are creating, only you should be able to access the draft through your candidate account. When you publish, anyone with both the unlisted link and listening code can view the profile context, play the audio and use the contact route you selected.
Think of an unlisted link and code like a CV sent by email.
It is not listed publicly by intro.id, but the recipient can copy or forward both. Do not include information in your recording that you would not want another hiring manager to hear.
How listening activity works
The intended MVP shows candidates aggregate signals such as total page opens and meaningful listens. It should not name individual listeners or show minute-by-minute behaviour.
The public listening page tells hiring managers that intro.id will not reveal whether or when a particular person listened.
Decision and legal review needed
We still need to define “meaningful listen,” choose the minimum analytics events required, set event-retention limits and confirm whether consent is required for those events.
Storage and retention
The planned MVP will store candidate records in Supabase Postgres and audio in a private Supabase Storage bucket. Published playback will use controlled access rather than making the storage bucket public.
Audio and account records should be kept only while they are needed to provide the service or meet an agreed legal obligation.
Decision and legal review needed
No retention period has been approved yet. Before a pilot, we must agree durations for active accounts, unpublished introductions, deleted records, backups, analytics events and failed uploads or transcription jobs.
Unpublish, correct or delete
Correct
Edit your profile context or replace the recording so the introduction represents you accurately.
Unpublish
Make the public page unavailable while retaining the introduction in your account.
Delete
Permanently remove the introduction, including its audio, subject to the final backup policy.
Current prototype behaviour
Unpublish and deletion controls propagate to the connected Supabase project and local device data wherever it is present.
Service providers
intro.id will need carefully selected providers to run the MVP. They should receive only the information needed for their part of the service and be bound by appropriate terms.
- Supabase
- Database, authentication and private audio storage.
- Transcription provider
- Not selected; transcription is deferred until after the MVP.
- Hosting, email, analytics and monitoring
- Not fully selected; each must be documented before pilot use.
Decision and legal review needed
The final privacy notice must name or clearly categorise subprocessors, explain international transfers where relevant, and link to an up-to-date provider list.
Questions and data requests
Candidates need a clear way to ask what data is held, correct it, request deletion, withdraw consent where applicable, or raise a concern.
Privacy contact not yet assigned
A monitored privacy email, responsible owner, response process and legally required rights language must be added before the pilot opens.
Until then, use the controls in the prototype to edit, unpublish or remove the introduction stored on your device.
Manage my introduction