Privacy and private memory

When remote knowledge retrieval is enabled, search queries may include your current question and chart terms used to find references. With OpenRouter, these queries are processed by OpenRouter and its model provider. This step does not upload your complete private history, private memory vectors, passwords, or personal model key. Processing and retention are subject to the relevant providers’ policies.

Supabase Auth handles email registration, verification, sign-in and password recovery. Passwords are not stored in the app’s business database. Authentication cookies are HttpOnly.

People, charts and conversations are saved encrypted in the app’s separate PostgreSQL database only when you enable private storage. Sending saved history to a model provider needs separate permission. A chart and the current conversation are sent to the provider when you request an AI answer.

Turning storage off stops saving and recall. Permanent deletion destroys private-data keys and keeps minimal revocation records to prevent deleted data from reopening. Backups may contain encrypted data; recovery must replay revocations before allowing access. Deleting app data does not automatically delete your Supabase Auth user.

Your own model key stays in this tab’s session and is cleared on sign-out or account switch. Registration does not subscribe you to marketing. Research and training require separate consent.

Use Account to manage consent, export and delete data. Keep downloaded files private.