Privacy & data retention

Service-specific reference. This page covers Chat, Mobile, Platform and the managed API. Only Platform and the managed API are under maintenance. These descriptions do not cover locally downloaded weights or Code CLI direct/BYOK use. For binding current terms, consult the SimpleDirect Privacy Policy and Terms . Code mode details are documented in the CLI privacy reference .

Vinci’s data handling depends on the feature. New web accounts sync new chats by default; existing accounts keep their sync setting. Saved history, account memory, retrieval documents and public shares have separate storage and controls.

API processing and local browser history

API. Usage and billing records keep only metadata — model, token counts, status and timestamps — not message content.
Demo (no account). A small signed counter enforces the message limit. Guest history and local memories can be saved in that browser and included in requests; signing in does not import guest history into your account.
Earlier local web chats. These stay in Archived on that device and will not be uploaded by sync. Archiving does not remove copies from earlier sync use.

What is stored

These features exist to keep data for you, so they store it. Their storage location and controls differ by feature, product and sign-in state:

Memories in Vinci Chat web. When you’re signed in, saved memories are stored with your account, independently of conversation sync. In the no-account web demo, memories are kept locally in that browser and may be included with chat requests. Signed-in web memory is on by default. With memory on, Vinci may save facts from your chats; manage them in Account > Memory & skills. Browser memories move to your account only through the explicit move action. Other products or versions can differ.
Custom instructions in Vinci Chat web. These are saved in your browser and included in chat requests to guide replies. They are not saved as account settings.
Skills. Reusable skills are separate from custom instructions, with their own storage and controls. Check the guidance for the product and version you use.
Uploaded documents. Documents you upload for retrieval are stored, scoped to your account, and deleted when you delete them.
Shared artifacts. If you create a shareable link to an artifact, that artifact is stored and reachable via the link until you revoke it.
Synced conversations. New web accounts sync new chats by default. Existing sync-off accounts can turn on Sync new chats in Account > Data & privacy. Synced chats use SSE-S3 encryption at rest in ca-central-1; the service can read them. Earlier local browser chats in Archived are not uploaded by sync. When you have synced copies, Delete synced copies appears under Account > Data & privacy, whether sync is on or off. Deleting them does not change that setting or chats on this device. Turning sync off also deletes synced copies. Cloud deletion cannot be undone.
Mobile 1.0.10. It reads the same account-level sync setting and, when it is on, uploads that account’s local chats from the phone. Accounts created in Mobile choose On this device or Synced under Where should your chats live?; sync stays off unless Synced is chosen.

Where it runs

Model inference runs on DeepInfra or Fireworks, depending on the class. Your messages are sent to that provider to generate a reply.
Account data (email, hashed keys, usage and credit balances), synced conversations, and uploaded documents are stored in Canada (Montréal, ca-central-1).
Web search is served primarily through Canadian infrastructure, with a US provider as a fallback.
Email delivery and optional product analytics are handled by US services (SendGrid and PostHog); analytics is off unless you enable it, and never includes message content.

Your account & keys

API keys are stored only as a hash; the secret is shown once. Rotate or revoke anytime — a revoked key stops working immediately.
Email verification and password reset protect account access. New accounts may be asked to verify their email before using Vinci.
We collect the minimum needed to run the service.

This page describes how the product is built. For binding legal terms, see the SimpleDirect terms of service and privacy policy.