KnowsYou.aiOpen beta
English
EnglishDeutschPolskiRomână
Start tracking free

Data, AI & security

See where your information goes and what each part does.

KnowsYou combines an application database, AI processing, private file storage and optional connected services. This page describes the current limited-preview flow without claiming perfect security or legal certification.

The short version

Store the record. Send only what a task needs.

Relevant conversation context reaches the AI provider. Voice, files, barcode lookups and connected data use separate, purpose-specific paths.

Data flow

Four paths are worth understanding.

The service does not process every input in exactly the same way.

Conversation and AI

The current message, selected history, active memories and relevant product context are sent to the configured agent provider—currently DeepSeek, with OpenRouter failover—so the agent can respond and use supported tools.

DeepSeek is based in China, which has no European adequacy decision. That transfer happens on every message and rests on your agreement to it; the Privacy Policy states what it covers.

Attachments take their own path, because the chat model reads only text. A photo or an uploaded document is first read by a vision or document model — one of the providers listed in the privacy notice — and what comes back is text, which then joins the conversation. Which provider handles which kind of attachment changes as models change.

Voice transcription

When you use voice input, the recording is sent through OpenRouter to OpenAI for transcription. Groq is used only if the primary request fails. The returned text becomes the message you can review and send.

Images and PDFs

PDFs are retained as uploaded. Images are processed and re-encoded before storage. A file attached to a message can be sent to the AI provider for that task.

Connected services & reference data

WHOOP data is imported only after authorization. Tokens stay on the server and do not enter conversation context. Barcode lookups use a local USDA and Open Food Facts product table first and may query Open Food Facts when a code is missing.

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.

AI provider boundary

KnowsYou does not claim that sending information to an AI provider is risk-free or that provider processing occurs only in your country. Do not submit sensitive information unless it is necessary for the workflow you choose.

Voice input

Voice audio is sent from the authenticated transcription route to a speech model at one of the providers listed in the privacy notice. If that call fails, the route can send the recording once more to an alternate. 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.

Barcode lookups and packaged-food data

A barcode lookup checks KnowsYou's local product table, which can contain packaged-food data from USDA FoodData Central and Open Food Facts. When both sources match the same normalized barcode, KnowsYou prefers the USDA Branded Foods entry. If a code is missing, the server can send the barcode digits to Open Food Facts and cache a returned match. That lookup does not include conversation text, account details or profile records.

If you send the scanned product in chat, the matched product snapshot becomes part of that message and can reach the AI provider as relevant context. Product matches and nutrition fields can be incomplete or wrong, so the composer shows the matched product for review before sending.

Packaged-food matches can use USDA FoodData Central Branded Foods, whose data are in the public domain and published under CC0 1.0. Contains information from Open Food Facts, which is made available under the Open Database License (ODbL).

WHOOP connection security

The WHOOP connection uses a random, expiring, one-time OAuth state bound to the KnowsYou session that started it. After the provider redirect, that same session must consume a second short-lived, one-time completion grant before the authorization code is exchanged. Only digests of the state and completion grant are stored; access and rotating refresh tokens are encrypted with AES-256-GCM. 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, disconnect WHOOP — and delete your account and everything in it yourself, from Settings 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.