vynt://legal/privacy
Privacy policy
A plain description of what VYNT stores and what it never exposes. This summary is provided for clarity and is not legal advice.
Data we store
Your account email, plan and subscription state; the sources you connect; the content and metadata you submit for indexing; derived topics, entities and index components; provenance hashes; API usage records; and an audit log of actions taken in your workspace.
Content you submit
Content is processed to derive structured metadata. Derived metadata and hashes are retained with your workspace. You can delete indexed items, which removes the derived records from your workspace.
What is publicly readable
Provenance records are publicly readable by hash or record ID. They contain hashes, source, version, timestamps and status — not content, not metadata values, and no personal data.
Public anchoring
Anchoring a provenance hash to a public network is optional and off by default. Only the provenance hash is ever anchored. Personal data is never written to an immutable public network.
Credentials and keys
API keys are stored as hashes with a short non-secret prefix. Full keys are shown once at creation and cannot be retrieved afterwards. Payment card details are never stored by VYNT.
Processors
We use infrastructure providers for hosting and database services, a language-model provider for semantic analysis, and a payment processor for billing. Content sent for analysis is not used to train models.
Your controls
You can delete indexed items, revoke API keys, disconnect sources, export your audit log and delete your account. Deleting your account removes your workspace data.
Have a question about data handling? Use the contact page and we'll answer specifically.