DisceraDiscera
TermsPrivacyBlogOpen app

Discera Privacy Policy

Effective November 10, 2026

Discera (“Discera,” “we,” “us”) is a task-routing tool: you type a request, Discera decides which AI model should handle it, sends it there, and shows you the result. This page explains what data that involves, where it goes, and what we do and don’t keep.

Accounts are optional

You don’t need an account to use Discera. Access to the app itself is controlled by a shared access code, not a login. Separately, Discera offers an optional sign-in (with Google, or with an email address and a password, or via a one-time sign-in link). If you sign in, Discera syncs your saved chats — titles and full message content — to your account so they’re available on any device you sign into, not just the one you started on. Signing in doesn’t unlock any other extra features or change what you can do in the app, and if you never sign in, nothing in this section applies to you: your chats aren’t saved to any account (see “What stays on your device” below), and the identifiers described below (device ID, IP) remain device- and network-level, not tied to a name or email.

What we collect, and why

  • What you type. The text (and, for image generation, the resulting image) of each task you submit is sent to the AI provider best suited to handle it, so it can generate a response. Because Discera keeps your full conversation in context, each request sends the earlier messages in that chat along with your new one — not just the latest message. See “Third-party AI providers” below for who that is and on what terms.
  • A device ID. On first visit, your browser generates a random identifier and stores it in your browser’s local storage. It’s sent with each request so we can enforce rate limits and, if necessary, suspend access for a specific device that’s abusing the service. It is not a name, email, or advertising identifier, and we cannot use it to identify you personally.
  • IP address. Every request to our servers carries an IP address, as with any web request. We use it for the same rate-limiting and abuse-prevention purposes as the device ID, and as a secondary signal for it (device IDs can be cleared by clearing browser storage; IP is a harder-to-evade backstop, though not foolproof either — it changes with the network).
  • Request metadata. When a task is actually dispatched to a model (not just a page visit), we log the device ID, IP, and a timestamp, and keep a running count per device, so the admin view can show usage and apply bans. Page visits are counted separately, in aggregate only — see “Visit counts” below.
  • Visit counts. When a page on discera.chat loads, we record three things: the page’s path (for example, /blog), the hostname of the site that linked you here, if any (for example, google.com), and whether the device looks like a phone or a computer. The record contains no IP address, no device ID, and nothing tying it to an account or a chat, and it can’t be looked up per-visitor through the site. We count visits in our own database (Supabase) rather than sending them to a third-party analytics company, and we use the counts to understand which pages people actually read.
  • Your email address — only if you choose to sign in. If you use the optional sign-in, you sign in with Google, or enter an email address and either set a password or have a one-time sign-in link sent to it (via Supabase, described below). Passwords are handled by Supabase only — we never see or store them. We don’t ask for your name or any other profile information.
  • Your email address — if you join the waitlist. Discera has a waitlist for people who want launch updates. If you join it, you give us your email address, which we store in our database (via Supabase, described below) and use to send you a confirmation and, later, launch-related updates. We send those emails through Resend, our email delivery provider, which processes your address to deliver the messages. Joining the waitlist is optional and separate from the sign-in above.

We do not collect names, phone numbers, or payment information, because Discera doesn’t currently ask for any of them. We do collect an email address, but only from someone who deliberately chooses to use the optional sign-in or join the waitlist — neither is required to use the app.

What stays on your device

The access code you enter is saved in your browser’s local storage and sent with each request so our servers can verify it, but we don’t store it on our servers. Your saved chats and chat titles work the same way by default — they’re kept in your browser’s local storage and are not stored in our database — unless you sign in. If you sign in, your chats are also synced to Discera’s database (via Supabase) so they follow your account across devices; see “Hosting infrastructure” below for where that’s stored and who can access it. One thing this doesn’t mean: when you send a message, it still passes through our servers and on to the AI provider to generate your answer, as described under “What you type” above — it’s processed, just not saved to an account. If you never sign in, clearing your browser’s site data for Discera deletes your chats permanently, because there’s no copy saved anywhere else.

Cookies

Discera does not use cookies. The device ID, your saved chats, and (if you sign in) your sign-in session use browser local storage instead, which isn’t sent to us automatically the way a cookie is — it’s only included when the app or Supabase’s own client library explicitly attaches it to a request.

Third-party AI providers

Depending on what a task needs, Discera sends it to one of the following providers to generate the actual response. Each is a separate company with its own privacy practices, and each processes what you submit under its own terms, not ours:

  • Anthropic (Claude) — text and reasoning tasks.
  • OpenAI (GPT, GPT Image) — text and image-generation tasks.
  • Perplexity (Sonar) — tasks that need live web search.

We route to whichever of these is live and appropriate for your task; the result you see in Discera tells you which one handled it. We don’t control, and aren’t responsible for, how these providers individually handle the data once it reaches them — review their own privacy policies if you want specifics on retention or model-training use on their end.

Hosting infrastructure

Discera is hosted on Netlify, including the rate-limit counters, device logs, and ban list described above, which are stored in Netlify’s data store (Netlify Blobs) rather than a separate database we operate. Netlify processes this as our infrastructure provider.

The optional sign-in is handled by Supabase, a separate infrastructure provider. If you sign in, your email address and sign-in activity (when you signed in, session tokens) are stored in Supabase’s systems on our behalf, under Supabase’s own security practices. If you sign in, your synced chats — titles and message content — are also stored in Supabase, in a database table restricted so that your account can only ever read or write its own chats (enforced at the database level, not just in the app code, and independently verified). We don’t copy your email or chat content into Netlify Blobs or connect them to your device ID or IP-based usage records — the two systems are separate today.

Waitlist email addresses are also stored in Supabase, in a separate table from accounts and chats. When you join the waitlist, the confirmation email — and any later launch updates — are sent through Resend, our email delivery provider. Resend processes your email address solely to deliver those messages, under its own privacy practices.

Feedback form

Discera links to an optional feedback form hosted by Google Forms. If you choose to submit feedback there, what you type is collected and stored by Google under Google’s own privacy policy, not ours — we see the responses, but Google is the one processing and storing them. Using the form is entirely optional.

How long we keep things

Device and IP records used for rate-limiting and abuse prevention are kept until manually cleared by an administrator — there is currently no automatic expiry. Ban records persist until an administrator removes them. If you sign in, your email address and any chats you’ve synced are kept in Supabase until you ask us to delete them (see “Your choices” below) — there’s no self-service account or chat deletion yet, aside from deleting individual chats from within the app, which removes them from Supabase immediately. Waitlist email addresses are kept until you ask us to remove you from the waitlist, or until the waitlist itself is retired. We periodically review this and may add automatic expiration or further self-service deletion in the future.

Who can see admin data

The device log and ban list are visible only through a separate admin credential, distinct from the regular access code, held by the people operating Discera. It is not exposed to regular users of the app.

If you sign in, your synced chats are protected so that no other user can ever see them — but the people operating Discera have database-level access and can technically read them, for example to investigate abuse or help with a support request. We don’t read chats routinely.

Children’s privacy

Discera is not directed at children under 13, and we don’t knowingly collect data from them. If you believe a child has used Discera and you’d like the associated device/IP records removed, contact us at the address below.

Your choices

Clearing your browser’s site data removes your device ID, locally-cached chats, and local sign-in session immediately. If you’re signed in, deleting a chat from within the app removes it from Supabase right away, not just locally. Signing out (from the app sidebar) clears your chats from that browser’s local cache — nothing is lost, since they’re still safely in your account, and signing back in (on that device or any other) pulls them straight back down. To request removal of server-side records tied to a specific device ID or IP (for example, if you believe you were banned in error, or want abuse-prevention records about your device deleted), to delete an account you signed in with (removing your email address and all synced chats from Supabase), or to be removed from the waitlist (deleting your email address from it), email us and we’ll act on it directly — there’s no self-service full-account deletion button yet.

Changes to this policy

If how Discera handles data changes in a material way, we’ll update this page and change the “last updated” date above. We don’t currently email individual users about policy changes, including anyone who has signed in — check this page directly for the latest version.

Contact

Questions, deletion requests, or anything else related to this policy: support@discera.chat.

This policy describes Discera’s practices as of the date above and isn’t a substitute for legal advice. If you operate Discera commercially and need this reviewed for a specific jurisdiction or regulatory regime (GDPR, CCPA, etc.), have a lawyer look it over.