Privacy Policy
Last updated 16 October 2026
This is a draft under legal review. It describes what Sesavu actually does with data today. It deliberately does not claim capabilities the product does not yet have. A counsel-reviewed policy will replace this before any paid launch.
What we collect today
Sesavu has accounts, and data you save is stored on our servers. In practice:
- Account details. When you sign up we store your email address and a hashed password, and we set a session cookie so you stay signed in. We never store your password in readable form.
- References you save. When you save a reference, we store what you provide — a source URL, any title, notes, and (for direct image URLs) a copy of the image — in our hosted Postgres database, linked to your account, so it is there when you sign in again.
- Product analytics. If you accept analytics in the consent banner, we send usage events to PostHog. These events carry an account identifier and coarse properties such as the kind of reference saved; they never carry your email address, note text, page content, or the URLs you save. Declining means no events are sent.
- Standard request logs. Like most web apps, the hosting layer may record basic technical request information.
Who else processes your data
- Hosting and database providers, which run the app and store your library.
- PostHog, for product analytics, only if you consent.
- An AI provider you choose. Optional AI is off until you choose Google Gemini or Anthropic, review that provider’s disclosure, consent, and supply a separate provider API key. Google Gemini vision receives thumbnail image bytes, MIME type and annotation instructions. Anthropic brief generation may receive collection context, reference identifiers, kinds, titles, ratings, tags, palettes, style descriptions and extracted text. The in-product disclosure names the exact categories before the first provider request.
Your API account, quota, billing and contract remain between you and the provider; Sesavu does not supply or pay for that provider relationship. We store the API key encrypted and use it only for the provider operation you consented to. The provider’s own processing and retention terms apply. You can revoke a key or withdraw consent for one provider without deleting results already returned or anything you wrote yourself.
Paid plans are not live, so no payment processor holds your data yet. If we add other processors — email, for example — this policy will name each one and what it receives before we start. We will not silently start sharing your data with a third party.
AI agent connections
An agent can access your references and collections, including private ones, only after you approve a connection or create and share a personal token. Access applies to your library, rather than just the collection you are viewing. Read-only access lets the agent search and read references, collections and available design briefs, including reference content and images. Read and save access also lets it save references, create collections and add references to collections. There is no delete tool.
Agent sign-in tokens issued through OAuth and personal tokens are stored as hashes, not readable token values. OAuth access tokens expire after 15 minutes. If you approve offline access, refresh tokens rotate after use and expire after 30 days, with a maximum connection lifetime of 90 days before you must sign in again. Authorization codes expire after one minute.
Content an agent reads is shared with that agent's AI provider under the provider's own terms, including its processing and retention terms. Only connect a provider you trust with the private content in your library.
To disconnect, open Sesavu, go to Agents and disconnect the connection or personal token. This stops future access through that credential. It does not remove content the provider has already received.
Sesavu records usage events for agent tool calls and OAuth actions such as consent, token refresh and revocation. These events include tool names, timestamps, connection identifiers and operation results or counts where applicable. They do not include token values.
Captured third-party content
Sesavu lets you capture images and text from other websites. Be careful not to save sensitive on-screen content (for example, pages behind a login such as banking or email). Saved references are private by default; a reference only becomes visible to others if you explicitly publish it.
Your choices
- You can delete a saved reference from the app.
- You can request an export of your library, and you can request deletion of your account and its data.
- Those controls are not yet exposed on every screen in the app. Until they are, contact us and we will run the export or deletion for you.
Children
Sesavu is not directed to children under 13, and we do not knowingly collect their data.
Changes
As the product adds or changes features, this policy will be updated to describe them accurately, with the "last updated" date changed above.
Contact
Privacy questions can be sent to akash@Chaitonix.com.
