Privacy Policy

Overview

TeenCue helps a parent or guardian understand how their teen or pre-teen uses supported AI chat services. A Chrome extension detects when a prompt is submitted on one of those services, and TeenCue records a classification of that prompt rather than the prompt itself.

This policy describes how the product works today. TeenCue is in active development, and this page will change as the product does.

The extension runs on the AI chat services TeenCue supports, and on the TeenCue website itself. On the TeenCue website it does one thing: let you connect a browser without copying a pairing code by hand. It reads no page content there, and nothing you do on teencue.com is classified or recorded as AI activity. TeenCue does not collect general browsing history, and the extension runs nowhere else.

TeenCue is not designed for secret monitoring. Your teen should know the extension is installed.

Information we collect

Parent account information:

• Your email address and the authentication details needed to sign you in, handled by our authentication provider.
• The date your account was created.

Subscription information, if you subscribe:

• A reference to your Stripe customer and subscription, which plan you chose, the subscription status, and the date the current billing period ends.
• No card number, expiry date or security code. Those are handled by Stripe and are never sent to TeenCue.

Child profiles that you create:

• A display name you choose. This can be a first name or a nickname, whatever you prefer.
• An optional age range.

Devices you connect:

• A device label, such as the browser and operating system reported when the device was paired.
• The version of the TeenCue extension.
• When the device was connected, when it was last seen, and whether it is currently active.
• A hashed form of the device authentication token.

AI activity records. When the extension detects a prompt submitted on a supported AI service, TeenCue stores a record containing:

• the AI provider, for example ChatGPT or Claude
• a usage category, for example school, coding, creative or personal advice
• a short topic label that is more specific than the category, such as "algebra_homework"
• a safety classification and a severity level from 0 to 3
• a confidence score for the classification
• the date and time the prompt was submitted
• which child profile and which connected device the record belongs to

Please read this part carefully. The short topic label is generated from the prompt, so it can indicate what a request was about. It is capped at 40 characters and is not the prompt text, but it is the one stored field derived from what your teen wrote. It is shown to you in the dashboard.

Transient prompt processing

To produce a classification, the text of the submitted prompt is sent from the TeenCue extension to the TeenCue classification service over an encrypted connection, and from there to our AI classification provider. The provider returns a structured result: category, topic label, safety classification, severity and confidence.

The TeenCue classification service is built so that:

• the prompt text is used only to produce that classification result
• the prompt text is never written to the TeenCue database, which has no column capable of holding it
• the prompt text is not written to TeenCue application logs

Once the classification result comes back, TeenCue keeps the result and discards the prompt text. We do not control every log that an infrastructure provider may keep about a network request, so we describe our own handling rather than making a guarantee about theirs.

Prompt text is handled automatically. It is not stored, it is not shown on any TeenCue screen or in any internal tool we have, and nobody at TeenCue reads it as part of running the service. There is no feature that would let us.

The third party that performs the classification processes the transmitted text under its own applicable terms and privacy policy. We describe our own handling above, and we do not make claims about theirs. See "Service providers" below.

What TeenCue does not store

TeenCue does not keep any of the following:

• raw prompt text
• AI assistant replies, or any conversation transcript
• a browsable archive of conversations
• page URLs, page titles or general browsing history
• keystrokes, screenshots, audio, video or location data
• raw device authentication tokens, which are stored only as a hash
• pairing codes in plain text

TeenCue does not offer parents a transcript archive. There is no feature anywhere in the product that reproduces what a teen typed.

How we use information

We use the information described above only to provide TeenCue and to keep it working and secure:

• show you a dashboard of AI usage for each child profile you created
• produce the Weekly Teen Brief and send it to your account email address, unless you have turned those emails off
• highlight classifications that may be worth a conversation with your teen
• operate, secure, debug and improve the service
• contact you about your account or about the service

We do not sell personal information. We do not use your information for advertising, and we do not transfer it to anyone for purposes unrelated to providing TeenCue. TeenCue does not train AI models on your data.

Service providers

TeenCue depends on a small number of third parties to function. These providers process information as necessary to provide their services, and under their own applicable terms and privacy policies:

• Supabase, for the database, parent authentication and backend services
• Anthropic, for classification of submitted prompt text
• Resend, for delivery of product email such as the Weekly Teen Brief
• Vercel, for hosting the TeenCue web application
• Stripe, for subscription payments

Payments are handled entirely by Stripe. Card numbers are entered on pages Stripe hosts and never reach TeenCue, so we do not receive or store a full card number. What we keep is a Stripe customer reference, a subscription reference, which plan you are on, the subscription status and when the current period ends. That is what tells us whether your subscription is active.

We may add or change providers as the product develops, and we will update this page when we do.

Data received through the Chrome extension

TeenCue’s use of information received through the TeenCue Chrome extension complies with the Chrome Web Store User Data Policy, including the Limited Use requirements.

In practice that means the information the extension handles is used only to provide the features described on this page, and for the security and operational work needed to keep them running. Specifically:

• We do not sell it, and we do not transfer it to anyone for any purpose unrelated to providing TeenCue.
• We do not use it for advertising, and we do not use it to build an advertising profile.
• We do not use it to determine creditworthiness or for lending purposes.
• We do not allow people to read it, except where you ask us to, where the law requires it, or where it is needed for a security investigation. Prompt text is not readable by us in any case: it is not stored, and no TeenCue screen or internal tool displays it.

Cookies and referral links

TeenCue sets only first-party cookies, meaning cookies readable by teencue.com and nothing else. There are no third-party advertising cookies, no tracking pixels, no analytics scripts and no cross-site tracking anywhere in the web app or the extension.

Sign-in cookies:

• Set by our authentication provider when you sign in, and needed to keep you signed in. Signing out clears them. Without them the product cannot work at all, so there is nothing to consent to or switch off.

Referral cookies. Some people find TeenCue through a creator who recommends it and is paid a share of what customers they refer pay us. If you arrive through a link containing a "ref" value, we set two cookies for 30 days:

• The creator code from the link, so we know who to credit if you later create an account.
• A random identifier with no meaning outside TeenCue, used only to count that a link was opened. It is not linked to your name, your email or anything you do elsewhere.

Both cookies are marked HttpOnly, so page scripts cannot read them. On the server we store a record that the link was opened, holding the creator, that random identifier and the time. We do not store your IP address, your browser user agent, the page you came from or any browsing history alongside it.

So that one source cannot flood a creator’s click count, we do count how many recent requests have come from the network address a request arrives from. That address is turned into a one way fingerprint before anything is written down, it is never stored next to the click record or anywhere else, and the counts are deleted within days.

If you go on to create a TeenCue account, we store a record linking your account to that creator, so their commission can be calculated. Once your first payment is made, that link is fixed and cannot be moved.

A creator is never shown who you are. They see counts, and the amounts they have earned. They cannot see your email address, your child profiles, your AI activity records, or anything else about your account.

Clearing your cookies before creating an account means no creator is credited. Clearing them afterwards changes nothing, because the link is held against the account rather than in your browser.

Retention and deletion

We want to be straightforward about what the product can and cannot do today.

• Classification records stay attached to a child profile until they are deleted. TeenCue does not currently expire them automatically after a set period.
• Removing a device from your dashboard revokes that device straight away and stops any further activity being recorded from it. Revoking a device is not deletion. Records already collected from that device remain.
• TeenCue does not yet provide a button that deletes a child profile or an account from inside the product. Deletion is currently handled manually by a person.

To have your account and its data deleted, email support@teencue.com from the address on your account, or use the deletion request button on your Account page. We handle these by hand, so we are not setting a turnaround time we cannot yet stand behind.

Deleting data from the live service does not instantly remove it from routine infrastructure backups held by our providers. Those copies age out on schedules set by those providers, which we do not control, so we will not invent a date for it here.

Security

Measures currently in place include:

• data encrypted in transit using HTTPS
• database access rules so that a parent account can read only its own family records
• device tokens stored only as hashes, and short lived pairing codes that are never stored in plain text
• service credentials such as API keys held server side, never shipped inside the browser extension

No service can promise perfect security, and we do not. We cannot guarantee that unauthorized access will never happen.

Children's data and parental responsibility

TeenCue is designed for parents and guardians managing devices used by minors in their care. The parent or guardian is the account holder. Children and teens do not have TeenCue accounts and do not sign in.

TeenCue is not built for covert surveillance. Set it up with your teen present. Pairing a device is a step the two of you complete together, and the extension stays visible in their browser.

You are responsible for confirming that you have the authority to monitor the device you connect, and for following the laws that apply where you and your family live.

This policy does not make a claim of compliance with any specific privacy law or framework. It describes what the product does so that you can decide whether it is appropriate for your family.

Your choices

• View every classification record TeenCue holds for a child from your dashboard.
• Remove a connected device at any time to stop collection from that device.
• Uninstall the Chrome extension to stop collection entirely.
• Turn Weekly Teen Brief emails off, or back on, from your Account page. The setting takes effect for every later scheduled brief.
• Email support@teencue.com to request access to, correction of, or deletion of your data.
• Clear your browser cookies before creating an account if you do not want a creator credited for your referral.

Changes to this policy

We may update this policy as TeenCue changes. When we do, we will revise the date shown at the top of this page. If you keep using TeenCue after an update, the updated policy applies to your use of the service.

Contact

For any question about this policy, or to make a request about your data, contact TeenCue at support@teencue.com.