Scope and roles
This notice covers the public website, Discord installation flow, meeting capture service, transcript commands, and pilot support activity.
The organization that installs Toki controls why its meeting information is processed and who may access it. The pilot operator processes that information to provide Toki.
Information processed
Installation information. Discord user and server identifiers, workspace membership, role and capability information, configured voice and text destinations, and OAuth installation state.
Meeting information. Meeting state, Discord speaker identifiers and display snapshots, finalized transcript text, timestamps, confidence, transcript gaps, and provider metadata.
Operational information. Request IDs, dependency health, error categories, bounded audit events, and configuration or deletion activity.
Raw audio
Toki does not persist raw meeting audio. Voice frames exist transiently in memory while they are decoded and sent to the configured speech-to-text provider, then they are discarded.
A meeting transcript is durable text and should still be treated as sensitive company information.
How information is used
- Install and bind Toki to an authorized Discord server.
- Enforce meeting lifecycle, workspace, source, and destination boundaries.
- Produce and return authorized speaker-attributed transcript pages.
- Maintain reliability, prevent abuse, investigate failures, and support the private beta.
Providers and disclosure
Discord supplies identity and voice transport. Deepgram is the configured streaming speech-to-text provider. Infrastructure providers may process encrypted service traffic and durable application data as needed to operate the pilot.
Information is not sold. Workspace information is not made public by this website.
Retention and deletion
The approved V1 policy targets a configurable 30-day default for meeting content and 12 months for minimal action receipts and audits. Automated retention and deletion enforcement is a later roadmap item and must not be assumed active during the current capture beta.
Until that workflow ships, pilot operators and workspace owners must coordinate deletion through the established private support channel.
Participant choices
Meeting participants should contact the organization that invited Toki because that organization controls the meeting record. Depending on location, a participant may have rights to access, correct, restrict, export, or delete personal information.
Identity and authority may need to be verified before a request is completed.