See where your information goes and what each part does.

Account and application records

Account, profile, conversation and structured wellness records are stored in PostgreSQL. The service uses authenticated profile context when it reads or writes data; the model does not choose which profile an action belongs to.

Sign-in supports email and password. Google sign-in is available only when that provider is configured. Session information is used to keep the account authenticated across supported clients.

What reaches the AI provider

An agent request can include the current message, a recent conversation window, a derived conversation summary, active memories and a structured snapshot of relevant records. Current-turn images or PDFs can also be included when the task requires the attachment.

The provider returns text or proposed tool calls. Application code validates and executes supported tools using the authenticated profile. Agent runs, context references and tool calls are recorded so actions can be inspected.

Voice input

Voice audio is sent from the authenticated transcription route to Groq. A saved preferred language can be passed as a transcription hint. KnowsYou receives the resulting text; the transcription route does not create a permanent application record of the audio itself.

The transcription provider can process the audio under its own service terms. Read the text before sending it because names, amounts and treatment terms can be transcribed incorrectly.

Files and object storage

Uploaded files are currently stored in a private DigitalOcean Spaces bucket in Frankfurt, Germany. The bucket is not configured as a public CDN. Retrieval requires an authenticated account check followed by a short-lived signed URL.

Supported images are resized and re-encoded as JPEG or PNG before storage. Supported PDFs are validated and retained as uploaded. File metadata, such as the safe display name, type, size and ownership, is stored in the application database.

WHOOP connection security

The WHOOP connection uses a random, expiring, one-time OAuth state whose digest is stored server-side. Access and rotating refresh tokens are encrypted with AES-256-GCM before storage. Tokens are never returned to the web or mobile client and never enter agent context.

WHOOP webhooks require a timestamped HMAC signature and reject stale replay attempts. Disconnecting revokes access when possible, removes local connection credentials and stops future syncs. Imported history is a separate product record and remains until deleted.

Conversation history and memory

The raw conversation timeline, cumulative summaries and curated memories are separate records. Only active, relevant memories are selected for future context. Low-confidence candidates and memories marked deleted are excluded.

Asking the agent to forget a memory currently soft-deletes that curated memory for future use. The audit record and underlying source conversation are not immediately erased. See Privacy for the retention and deletion boundary.

Current safeguards—and their limits

Implementation-backed safeguards include:

• HTTPS for deployed web traffic;
• authenticated, profile-scoped reads and writes for user records;
• a private file bucket with time-limited signed retrieval links;
• encrypted WHOOP credentials and signed webhook validation;
• server-side secrets that are not returned to clients; and
• audit records for agent runs, context references and tool actions.

These controls do not amount to a promise of absolute security, uninterrupted availability, a particular certification or compliance with every jurisdiction. The preview does not make a public backup or recovery-time guarantee.

Controls and requests

You can review and correct records, manage notifications and disconnect WHOOP in the application. Account-data requests can be sent to privacy@knowsyou.ai. Identity verification may be required.

This page describes the implementation; the corresponding privacy and contractual statements need market-specific legal review before commercial launch. Read the privacy notice and terms for the current preview scope.