Security & Data Handling

What we collect, where it lives, who can see it, and how to get it gone.

A short, plain-language summary of how getconstellation.ai handles data: what the demo form and the extension touch, where it's stored, when it goes away, how to ask for it back, who can read it, and how to reach a human about a security concern. Last updated 2026-08-04.

Data we collect and crawl

The form fields — and nothing the extension hasn't seen.

The only personal information getconstellation.ai itself collects is what you type into the Request a demo form on the home page: your name, your work email address, and your company name. Full details on those three fields — validation, character caps, and what's deliberately not asked — live on the privacy page.

The ConstellationOS browser extension does not run in the background and does not crawl pages you haven't opened. It only ever touches the page currently active in the user's tab, at the moment the user explicitly invokes it. There is no site-wide crawl, no off-tab scraping, no continuous-visited-pages index, and no analytics endpoint on the extension side. Pages the user has not opened in their browser are never read, never fetched, and never sent to any server.

Where it is stored

Postgres over TLS — and the browser for everything else.

When you submit the demo form, the three fields are written to a single row in the leads table in a Postgres database hosted on Neon. The database is reachable only over TLS, and the server authenticates with the standard Postgres credentials configured for this app — there is no public read or write endpoint.

The extension itself does not upload page contents to a server. Working data — the page text the user is currently viewing, in-flight summaries, model context — stays in the user's browser session for the duration of that session and is cleared when the session ends. There is no third-party data warehouse, no shadow log store, and no separate analytics backend receiving extension activity.

Retention

Leads purged within 90 days. Extension data lives only as long as the tab.

Submitted leads sit in the leads table until a teammate replays them through the internal /leads/queue endpoint or the row is deleted directly. Each lead is reviewed and purged within 90 days of submission, or sooner if you ask us to delete it.

Extension-side working data is cleared on session end — closing the tab, ending the chat, or revoking the extension's permissions all drop whatever was held in memory. Database backups follow Neon's defaults for the project; if you want any row removed before the normal retention window, contact us using the channel below and we'll delete it immediately.

Deletion on request

One channel, a 30-day ceiling, and nothing to delete that isn't yours.

Send any deletion request to the security contact below and we'll remove the relevant row from leads within 30 days of the request — typically much sooner, usually the same business day.

There is no extension-side data to delete on your behalf — because nothing the extension reads leaves the user's browser unless the user explicitly exports it. If you exported a transcript or summary and saved it on your own machine, that's your copy to handle locally; we don't hold a copy of it on any server.

Access controls

A named internal team, behind authenticated Postgres credentials.

Access to the leads table is limited to a named internal team that operates Constellation. Credentials are the standard DATABASE_URL Postgres role configured for this app; there is no anonymous read endpoint, no public SQL gateway, and no client-side token that can be lifted from a browser and replayed.

The /leads/queue companion endpoint that lists queued leads is operator-only by design — it has no authentication on the wire today because it lives behind the network boundary of the deployment and exists only so queued leads can be replayed once the sending domain is verified. There is no third-party access to submitted data; it is not sold, shared, licensed, or exposed to advertising, analytics, or social platforms in any form.

Security contact

A single channel for security issues and disclosure questions.

Report a vulnerability, ask a question about this page, or flag anything that looks off — security@getconstellation.ai is the address. For now this is a placeholder: while the getconstellation.ai sending domain is still being verified, mail forwarding needs to be wired up at the registrar before this address is live. Until then, reach Constellation directly at the contact listed on the about page and your message will be routed the same way.