Privacy policy
Last updated
The terms now say you must be 18 or older to buy, that your microphone may pick up other people in the room with you and that they should know, how far our liability goes, and that California law and courts apply. An Ask Pack’s asks no longer expire, including packs already bought, and a deletion request now refunds the asks left. Paid plans are sold only while our legal name and street address are shown on these pages and at checkout. The privacy policy now says we keep a record of what a card buyer agreed to at checkout, with the purchase record, and that a new subscriber gets the plan’s terms by Discord DM. The revision before this one, on November 14, 2026: The Free plan now has 20 asks a month (it had 50). The terms now cover the Ask Pack, asks bought by one person rather than a server: how its asks are used, that they expire after a year, and what a refund or a deletion request does to them. The privacy policy says what we keep about its buyer. When /juno join is typed in a text channel, Juno now also posts its notice, with the Hear me buttons, in that channel, and the notice mentions the people in the voice channel who haven’t answered (each at most once every 30 days). /hearme shows the same question as /juno optin. The terms now cover tips: a tip is optional, unlocks nothing and isn’t a charitable donation. The privacy policy says what a tip sends Stripe. The revision before this one, on November 11, 2026: Operational logs are now kept when Juno is updated. Before, every update deleted them. They still roll off at about 250 MB. The revision before this one, on November 10, 2026: Juno no longer keeps bets. The bet feature was removed, the stored bets were deleted, and these pages no longer mention them. When everyone in the voice channel has already pressed Hear me, Juno now opens with a short spoken line (that it is an AI, and that it hears people who pressed Hear me) instead of the full spoken notice. The chat notice with the buttons is posted on every join as before, and anyone without a yes still hears the full notice or gets a mention. The revision before this one, on November 9, 2026: Juno now hears only people who press Hear me. Before, it heard everyone it had told unless they opted out. A wake word that fails for someone no longer sends their speech to our transcription provider, and people who arrive later are no longer told by DM. It also says how to mute Juno’s voice for yourself. This revision also adds things the last one left out: three more cases where audio goes to our transcription provider (a follow-up straight after an answer, a slash command run from the voice channel, and a second pass on some Referee and Host speech), what the stream overlay shows, what we send Stripe, who is thanked for an Event Night, our private operator alerts, and how long usage counts are kept. It also says when a server’s data outlives removal, what /juno privacy leaves out, when background features can pause, and what a refund or card dispute ends. It also says the danger check doesn’t read pictures. The terms gain a route for copyright and other complaints about content.
The short version: Juno only hears people who said yes, in the voice channel it was invited to. It transcribes what they say, keeps audio and text in memory for up to ten minutes, and sends parts to Deepgram, Anthropic and OpenAI to answer. /juno optout takes a yes back.
- Audio stays off our disksHeld in memory for at most ten minutes, then deleted. Providers may hold what they are sent under their own terms.
- Heard only if you say yesPress Hear me once per server. /juno optout takes it back, in every channel of that server.
- Receipts kept 365 daysThe claim, the verdict and the sources, so they can be shared. Then deleted.
- We don’t train on itWe never train AI on your data, and we rely on our providers’ terms that they don’t either.
- Your micDiscord sends each person's audio to Juno separately. Juno subscribes only to people who said yes, so nobody else's is ever decoded.
- Heard on our serverThe wake word and local notes run on our own servers, and the notes last ten minutes at most. Audio can go out for transcription when someone says the name or a wake phrase, or while Juno is talking.
- When someone asksThe last minute of audio is transcribed so the request is heard right, and up to ten minutes of the text goes to the AI provider, so Juno knows what “that” is.
- Answer and receiptA short answer out loud; the claim, verdict and sources posted in chat.
- ForgottenWe delete audio and transcripts from memory within ten minutes and don't write them to disk. Providers may hold what they were sent under their own terms.
Who we are
Tetra Labs LLC, a California company (6296 Magnolia Ave #1100, Riverside, CA 92506) (“we”) runs Juno, a voice assistant for Discord voice channels, and this website. Questions or requests: support@intakenexus.com.
When Juno listens
- Only in a voice channel where someone ran
/juno join, and only until Juno leaves. It leaves when told to, about a minute after the last unmuted person goes, or after two hours of quiet. - On joining, Juno says out loud that it's an AI, that it only hears people who press Hear me, what happens to their speech, and how to take that back. When everyone in the channel has already pressed Hear me, it says only the first two. It posts the full notice in the channel's chat on every join with Hear me and Don't hear me buttons (and the same notice in the text channel where
/juno joinwas typed, if that was a different channel), changes its nickname to “Juno · AI listening”, and sets the channel status. If it can't do those things, it refuses to listen. - Juno hears you only if you said yes. Nobody is heard until that spoken notice has finished, and after it only people who pressed Hear me, then or on an earlier day in that server. Being in the channel, or staying after the notice, is not a yes.
- A yes covers the voice channels of that one server, for the wording of the notice you agreed to, for up to a year. When the wording changes or the year is up, Juno asks again. While your yes stands, Juno hears you whenever it is listening in a voice channel you are in, without asking each time; the channel status and nickname show when that is.
- People in the voice channel with no answer on record are mentioned by name in the notice when Juno joins, so Discord notifies them; someone who arrives later gets a mention in the channel's chat with the same buttons. Each person is mentioned at most once every 30 days, and nobody is heard unless they press Hear me. In a long session the chat notice is repeated every three hours.
- People who haven't said yes, and people who said no with Don't hear me or
/juno optout, aren't heard in any channel of that server. Juno doesn't subscribe to their audio, so it isn't decoded, stored or transcribed. Discord may still deliver the packets to our server, where they are discarded. - Juno's own voice goes to everyone in the channel, because Discord has no way for a bot to speak to only some people. If you'd rather not hear it, right-click (or tap) Juno in the voice channel and choose Mute; that affects only you.
- Each microphone is its own stream, so Juno hears the people who said yes and nobody else. It still hears their side of a conversation with you, and anything their microphone picks up, such as a voice in the same room.
Audio
- Each person's audio is decoded on our servers and kept in memory for at most ten minutes, then deleted. We don't write it to disk. Audio in memory is deleted sooner when Juno leaves the channel or when someone runs
/juno forget. - The wake word (“Juno”) is detected by software running on our servers, not by a third party.
- Local notes: by default, Juno transcribes what people say as they talk, by software on our own servers, for up to the last ten minutes. This step sends no audio off our servers, and the text is kept in memory only and deleted after ten minutes, like every transcript. A room goes without local notes when our servers are busy or when local transcription isn't on for that server.
/juno privacyshows whether local notes are on where you are. - In the default mode, audio goes to our outside transcription provider, Deepgram, in these cases:
- Someone says “Juno”, or one of the phrases “pull that up”, “pull it up”, “pull this up” or “fact check that” (a server can turn these phrases off). That person's request, plus up to the last minute of what everyone being heard in the channel said, is sent so the request is heard accurately.
- Juno has just finished an answer. For a few seconds the person who asked can follow up without saying the name, and what they say next is sent.
- Someone in the voice channel runs
/juno checkor/juno ask. Up to the last minute of what hasn't been transcribed yet is sent, so Juno knows what the request is about. - Juno is talking. Everyone being heard can then be streamed live to Deepgram, so a “stop” is caught straight away.
- Someone asks to be caught up, out loud or with
/juno catchmeup. Whatever hasn't been transcribed yet, up to the last ten minutes, is sent. In a room without local notes that can be all of it.
- If the wake-word software fails for someone, Juno can't hear its name from them until it is working again, and says so in the channel's chat. Their speech is not sent to Deepgram in its place.
- In Referee and Host modes, which a server has to switch on, what people say is transcribed in short batches every few seconds, with nobody asking, so Juno can follow the conversation. Only the stretches where someone is talking are sent, never the silence in between. Some of it may be transcribed on our own servers first. A stretch transcribed there is still sent to Deepgram when it sounds like a claim, a disagreement or a name, or when our own transcription isn't sure of it; the rest doesn't leave our servers.
- The display names of people in the channel, and the games they're playing where game awareness is on, are sent to Deepgram with the audio so names are transcribed correctly.
- If you attach a screenshot to
/juno checkor/juno ask, the image is sent to the AI model with your question. We don't keep a copy; Discord hosts the attachment. - We have opted out of Deepgram's model improvement program, so the audio we send is not used to train its models.
- We don't create voiceprints or recognise people by their voice. Discord tells us who is speaking.
Transcripts
Transcripts are kept in memory only, for at most ten minutes, and are used as context for Juno's answers. We don't write them to disk or to our logs. /juno forget deletes them early, and opting out removes your lines immediately.
Answers and fact-checks
To answer, Juno sends the request and up to the last ten minutes of the conversation's text (display names and what was said) to Anthropic, which provides the AI model, and the model may search the web using the question or claim. In Referee and Host modes, recent text also goes to Anthropic with nobody asking: to spot claims worth checking, to check them, and to find a line for a quiet room. The text Juno speaks is sent to OpenAI to generate its voice; your audio is not sent to OpenAI.
What those providers keep. We don't control what a provider keeps once it receives data. As their published terms read when we last checked: Anthropic deletes API data within 30 days, and can keep flagged content longer. OpenAI keeps Realtime API data for 30 days for abuse monitoring. Deepgram keeps usage logs for 90 days. Their API terms say they don't train their models on this data by default, and we rely on those terms; we can't check it ourselves.
Game awareness (off unless a server turns it on). With /juno settings games on, Juno reads the game each person in the voice channel is playing from their Discord activity status (only people who can be heard, never people who opted out), so a question like “how does this ability work?” is answered for the right game. It is read live when someone asks and sent with the request as above; it is never stored. People with activity status turned off show nothing.
If someone may be in danger
When what someone says to Juno suggests they might hurt themselves, Juno doesn't answer it as a question. It says, or posts with no name and no quote, a fixed line pointing to 988 in the US and local emergency services elsewhere. No AI model is called from that request and no receipt is made, the words aren't kept in the transcript, and the log entry for it says only that it happened in that server, not who or what was said. (Our routine log of someone saying “Juno”, with a hashed user ID, is written a moment earlier, like for any request.) To detect this the words must be transcribed first, so they may have reached our transcription provider. Juno checks for this with a fixed word list: it can miss things and it can misfire. The check reads words that are spoken or typed, not words inside a picture, so a screenshot attached to a command goes to the AI model as it is. Juno is not a crisis service, a therapist, a doctor or a lawyer, and nobody at Tetra Labs LLC is monitoring what it hears.
What we store
- Receipts: the claim or question, the verdict or answer, the sources, the display names and Discord user IDs of who said it and who asked, the server and channel IDs, the time, how confident Juno was, which AI model answered, and performance data (speed, cost). Deleted automatically after 365 days, when the bot is removed from the server, or earlier on request.
- Server settings, who said yes or no to being heard, and usage counts: so Juno behaves the way your server chose, hears only people who said yes, and stays within plan limits. A yes or a no is stored with your Discord user ID, the server, the notice version and the time. Deleted when the bot is removed from the server (a yes also lapses after a year), except usage counts (monthly totals per server, no names), which we keep with billing records for seven years.
- Notice log: that a person (as a hashed, not raw, user ID) was told about Juno, said yes or said no, in which server and channel, how, in which language, which version of the notice, and when. No content. It's our record that people were asked and what they answered, so it stays after
/juno forgetand after a server removes the bot. Deleted after 24 months, or earlier on request. - Free trial records: which Discord user started each server's First Night, kept for two years so a trial can't be claimed twice, and the Discord user IDs of people who passed the human check for it, kept for one year. The trial itself is recorded like a purchase, without the user ID.
- Purchases: the plan, the server it is for, the Discord user ID of whoever bought it, when it starts and ends, and the Stripe subscription or payment ID that links it to the payment. Kept for seven years after a plan ends, for tax and accounting records. Payment itself is taken by Stripe, Inc. on Stripe's own checkout page: Stripe collects your email address, your card details and, where sales tax applies, your billing address, under Stripe's privacy policy. We never see or store card numbers. We send Stripe the server ID and the buyer's Discord user ID with the payment, so the plan lands on the right server. An Ask Pack belongs to the person who bought it, not a server: we keep the buyer's Discord user ID with how many of its asks are left, and take one each time that person asks something in a server that is out of its own. For a card purchase we also keep a record that the buyer ticked the box agreeing to the terms and, for a subscription, to the monthly renewal: the words shown, the price and the time. It holds no Discord user ID and is kept with the purchase record. When a card subscription starts, Juno sends its buyer a Discord DM with the plan, the price, the renewal and how to cancel. Whoever buys an Event Night is thanked by display name, out loud and in the channel's chat. If a plan is bought inside Discord instead, Discord handles the payment and we store only the plan, the server, the buyer's Discord user ID and the dates. If you tip the developer, Stripe takes the tip the same way; a tip isn't tied to your Discord account, and we keep only its amount and Stripe's payment ID.
- Blocked accounts: a hashed user ID, when someone's data has been removed at their request or because they were under 13, so Juno doesn't hear them again.
- Operational logs: events such as “a request was answered”, with hashed (not raw) user IDs, timing and the length of what was said. No audio, no transcripts and no claim text. Logs roll off at a fixed size (about 250 MB), not after a fixed number of days. Updating Juno keeps them; they are gone when the machine running Juno is rebuilt.
- Operator alerts: when a plan is bought or something breaks, a message goes to a private Discord channel only we can read, with the server's name and ID and the plan, never the buyer. These stay until we delete them, and aren't removed automatically when a server removes Juno.
- Backups: the database is backed up daily on our servers, and an encrypted copy may be kept with a storage provider so a failed disk can't lose it. Backups are deleted once they are 14 days old, so anything deleted, including with
/juno forget, is normally gone from backups within about 14 days. If backups stop working, the last seven good ones are kept until they work again.
We don't use your audio, transcripts or receipts to train AI models. To improve Juno we only use statistics that can't be tied to any person, such as how fast answers were or how often verdicts were disputed.
Share pages
Each receipt has a share link. Anyone with the link can view it; the address is random and can't be guessed, and we ask search engines not to index it. Server leaderboard pages only open through links Juno posts in that server, and those links expire after 30 days. To dispute a receipt or ask for one to be taken down, use the link on the receipt or contact support@intakenexus.com. A receipt we take down stops showing within minutes. New cards posted in Discord are removed with it; older cards may have to be deleted by the server.
Rankings. Per-person leaderboards, streak call-outs and monthly awards are off unless a server's admins turn them on, and members are told in the channel when they do. They come from AI fact-checks, which can be wrong.
Stream overlay (Studio plan). A server manager can create a private link that shows receipt cards on a live stream as they happen: the claim or question, the verdict or answer with a short reason, how confident Juno is, the sources' titles and site names, and the display name of who said it. Nothing else from the channel is shown, and the link stops working if the server leaves the Studio plan. If your server uses it, the people in that voice channel should know they may appear on stream.
Who we share data with
The providers above (Deepgram, Anthropic, OpenAI), our hosting provider and backup storage provider, Stripe, which takes payments for paid plans and tips, Cloudflare, whose Turnstile check runs when someone takes the human check for a free trial and sees that person's browser and network details, and Discord, which delivers the audio and messages (and processes payments for plans bought inside Discord). These providers are in the United States, so your data may be processed there. We don't sell or share personal data for advertising, we don't give it to data brokers, and we don't show ads.
Your choices
- Hear me,
/hearmeand/juno optin: the button under Juno's notices is how you say yes. Either command, typed in any channel of the server, shows you the same words and the same button at any time. - Don't hear me and
/juno optout: Juno stops hearing you in that server immediately, and your audio and transcript lines in memory are removed. It doesn't change receipts already stored, or what was sent to a provider before you said no. /juno forget: wipes the audio and transcript Juno is holding for the channel./juno forget what: mealso takes your Discord ID and name off the stored receipts in that server that carry your ID (the verdicts stay, anonymous, so other people's stats still add up). It works by ID in one server at a time, so it misses other servers, rows that have only your name, and text that mentions you./juno export: sends you, by DM, a file of the stored receipts in that server that carry your Discord ID, and whether you've said yes or no to being heard there, with the same limits./juno privacy: shows whether you've said yes or no, the audio and transcript lines Juno is holding in memory about you in that server right now, and how many stored receipts carry your ID. It doesn't list the notice log, trial or purchase records, or what providers hold; ask us for those.- For anything else (deletion across every server, including anything the commands miss, corrections, questions about what we hold), contact support@intakenexus.com. We can remove your data across every server on request. Backups, Stripe's records and messages already posted in Discord can take longer or stay out of our reach, and we'll tell you which.
When a server removes Juno, that server's receipts, settings and everyone's yes or no are deleted, even if it happened while Juno was offline. One exception: if that server has a card subscription we couldn't cancel, we keep its data until the cancellation goes through, and try again each time Juno restarts. Purchase records, free trial records, usage counts and the notice log stay for the periods above.
Your rights
Depending on where you live (for example the EU, the UK or California), you may have the right to access, correct, delete or export your personal data, to object to how we use it, and to complain to your data protection authority. The commands above cover some of this; for the rest, contact support@intakenexus.com. We answer within 30 days and won't treat you differently for asking. We hear and transcribe you only with your consent, which you give by pressing Hear me and can withdraw at any time; withdrawing doesn't undo what was done before. We process the rest (receipts, settings, purchase records, logs) to provide the service your server asked for and to keep the records the law requires.
Reporting a problem
To report misuse of Juno, a wrong or harmful answer, or a privacy concern, contact support@intakenexus.com, or report the app through Discord. We review every report.
Age
You must be 18 or older to use Juno, or 13 to 17 with a parent's or guardian's permission. Juno isn't for anyone under 13, and server owners must not use it in servers meant for children. We don't verify ages; pressing Hear me confirms you meet this. To report someone under 13, contact support@intakenexus.com: we remove their data across every server and block the account.
Security
Audio and transcripts stay in memory, connections to our providers are encrypted, and share pages carry no tracking scripts or third-party content.
Changes
If we change how Juno handles data, we update this page and the date above before the change takes effect.