Questa pagina non è ancora tradotta; viene mostrata la versione inglese.
Privacy Policy
Last updated: 16 November 2026
2BEE FARM PTY LTD (ABN 57 697 830 461), which operates 2hives ("we", "us"), respects your privacy. This policy explains what personal information we collect, why, and how you can control it. We handle personal information in line with the Australian Privacy Principles (Privacy Act 1988). For visitors from the EU and UK, it also follows the GDPR.
1. What we collect
- Account details: your email address. If you sign in with Google, we also receive your Google account ID and verified email (no contacts or other Google data). If a sign-in method can't be linked because it already belongs to another account, we keep a support note of the two account numbers and the method (no email address) until either account is closed.
- Your programs: the prompts you write, the name you choose for the voice to call you and how to pronounce it (typed, or from a short recording of you saying it, which we keep only if you agree, turn into a pronunciation on our own servers, and delete whenever you ask), your chosen settings (voice, speed, length, background, ambience and similar), the scripts generated for you, and the audio we render.
- Listening activity: when and how much of each program or preview you play, how far you get, how long you listened to each beat range of the audio (worked out from the positions you listened to; the beat range describes the audio, not you), and whether you completed the headphone check. We use this to resume playback, show your listening history, and improve our programs. We also measure how playback performs on your device, such as how long it takes to start and whether it stalls or fails, together with your browser type and version but no personal details beyond what we already log, so that we can fix audio problems. These records are deleted after 30 days. We also keep, for each day you listen, the time zone your device reported (first and last) for 400 days, so that days are counted in your own time.
- Clicks and page views (first-party): which buttons and links are used and which pages are viewed, so we can see what works and fix what doesn't. Each record has the type of page (such as "/live/:id", with ids and everything after a "?" removed), the name of the control (a short internal name, never the words on it), where a link goes (only the website name for links to other sites), the section of the page, the version of a page being tested, your language and the time. It is linked to the anonymous browser ID the site already sets, or to your account when you are signed in. We never record anything you type, any text on the page or any email address, we use no new cookies, and nothing is shared with any other company. Records are kept for 90 days and then deleted. If your browser sends Do Not Track or Global Privacy Control, nothing is recorded, wherever you are. If you are in the EU or EEA, the UK or Switzerland, or we can't tell where you are, we record clicks and page views only after you press Accept in the cookie banner: until then nothing is stored against your browser ID, and Decline or no choice means none. Elsewhere, the banner's choices don't change this. Actions that belong to your account, such as signing up, checking out or playing a session, are still counted in totals, without your browser ID. If you accept cookies, three key actions (signing in, joining a live session or setting a reminder for it, and pressing Play on a course) are also sent to Google Analytics, as an event name and a page type only.
- Purchases: order details (product, price, date, promotion code or referral) and a Stripe reference. Card details are handled by Stripe and never reach us. For a business that buys paid partner packages, see "Paid packages" in the business accounts section.
- Referrals: your referral code, and who you referred or who referred you.
- Seniors Card discount (only if you claim it): your state, a one-way code made from your Seniors Card number (never the number or your name) and when you declared it. They are kept after you close your account so that one card cannot take the discount twice.
- Technical information: IP address, device and browser type, and server logs, used for security, fraud prevention and rate limiting.
- What our server itself records: separately from the page events above, our server keeps a log of what it served, so that we can run and secure the service and check that the page counts are complete. Each row has the time, the type of page or request (never the raw address, form values or search text), the status and how long it took, your language, device class, web or app and app version, the version of any page being tested, the campaign tags in the link you came by and, for audio we send you, when the first and last bytes went out and how many seconds of audio they cover (an estimate: your player downloads ahead of what you hear). Sign-in and account steps are logged as success or failure only, with no email address, code or token. It stores no IP address: it keeps only a short one-way tag made from the network part of your address (the first three numbers of an IPv4 address) and a secret that changes every day at midnight UTC, so tags cannot be linked from one day to the next or turned back into an address. Your account number is stored with a row only when you are signed in and have not switched off Usage analytics in your account. If Do Not Track or Global Privacy Control is on, nothing is stored (only an anonymous count). If you are in the EU or EEA, the UK or Switzerland, or we can't tell where you are, then until you press Accept in the cookie banner the rows carry no account number, browser ID or network tag. Rows are kept for 90 days and then deleted; daily totals without any identifier are kept. Rows tied to your account are in your data export and are deleted when you close your account.
- Your permission for AI features: before the first time you use a feature that sends what you type or say (as text) to our AI providers, we ask for your permission. We keep which version of the question you agreed to and when and, if you later switch the AI features off in your account, when. If you are not signed in, your answer is kept in a cookie for a year instead. If you say no, nothing is sent and the rest of 2hives keeps working.
- "Email me a link" (home page): if you type your email address into that box without an account, we keep the address, the time you chose and the page's language only until the email is sent (and delete it after three failed tries, or six hours after the chosen time). We use it for that one email and nothing else.
- Businesses that ask to be told when listings open in their country: if a business types its name, town, country and email address into the form for businesses that ask to be told when listings open in their country, we keep them, the page's language and a code that confirms the address. We send one confirmation email and, once it is confirmed, one email when partner listings open in that country. It is not tied to an account. An unconfirmed request is deleted after 7 days and a confirmed one 12 months after it was confirmed; write to info@2hives.com to remove it sooner.
- Venue accounts: if you register a venue we keep your account, the venue's name and type, its postcode or suburb, a contact name, and (if you give one) its website, and which version of the venue licence you accepted and when. We show the venue only totals ('fewer than 3' for one or two) of how many people scanned its card or joined through it. We never tell a venue who a person is. A person who joins through a venue's QR code has our usual account; we remember which venue's code they used so that venue can appear as their local partner, and you can remove that link in Settings.
- Sensitive information: what you type or say to write a session can touch on your health, beliefs or feelings (for example sleep, worry, grief or faith). You choose what to write. We use it only to write and deliver your session and to keep you safe (see "Interactive guided sessions" and "Practice log"), not for advertising, and we do not sell it.
- Crash reports (apps only): see Crash reports below.
- Cookies: strictly necessary cookies, plus Google Ads cookies only if you agree. See Cookies below.
- Your voice (only if you choose it): if you ask us to make a synthetic version of your own voice ("Your own voice"), we keep the recordings you make for it (short sentences you read aloud and a spoken consent sentence), the voice model made from them, quality and same-speaker check results, and a consent record (what you agreed to, when, the confirmation that you are 18 or older, and the country your connection came from). If you make your voice public, we also keep your public consent recording, the display name and description you choose, and ratings and reports from other users. If you tick the separate, optional "Help bring 2hives to my language" box, we also keep the sentence recordings you made for your voice and a record of that opt-in. If you upload a profile picture for your voice, we keep that picture (see Profile pictures). See Voice recordings below.
- Reading-session recordings (only if you sign in and join a reading session): your recordings of the sentences and of a spoken consent statement, the automatic check results for each recording, your progress through the script, and a consent record. We use them to train 2hives' synthetic guide voices and, if you choose, to list you as a reader on our Credits page. See Reading sessions below.
- Interactive guided sessions (only if you start one): what you say during the session (your microphone audio and its transcript), the guide's lines, your settings and guide, any safety flags, a written summary, and a recording of the session (the tones, the guide and, unless you choose "Don't keep my voice", your voice). If you choose not to save a session, none of this is kept after it ends, apart from a minimal record (see below). See Interactive sessions below.
- Ad clicks: if you arrive from one of our Google ads, on the website or (in Australia and New Zealand only) by installing our Android app from one, the click identifier Google adds to the link (gclid). We keep it with your account and orders so we can tell Google which ads led to a sign-up or purchase. See The Android app and the ad that brought you for the app.
- How you found us: we record which ad or link brought you here (the campaign tags in the link, such as utm_source, an ad click identifier, the first page you opened and the course it belongs to). If you are in the EU or EEA, the UK or Switzerland, or we can't tell where you are, we start recording this only after you press Accept in the cookie banner. We keep it with your browser's anonymous ID for 30 days and, if you sign up, with your account, to see which ads and links work (if you never accepted, there is nothing to attach). In a cookie only if you accept cookies. In the Android app this also includes the install referrer from Google Play (see The Android app and the ad that brought you).
2. Why we use it
We use your information:
- to provide the service (create, render and deliver your programs; sign you in; process payments; credit referrals);
- to communicate with you (sign-in links and codes, receipts, service messages and, if you agree, occasional emails about your programs and offers);
- to keep 2hives safe and working (security, fraud and abuse prevention, rate limits);
- to measure which of our ads and links bring people to 2hives (including, in Australia and New Zealand, the Android install referrer), to find and fix app crashes, and, if you ask for them, to send reminders;
- to improve our programs and pages, using aggregated listening statistics and counts of which pages and buttons are used.
3. Who we share it with
We use trusted service providers that process data on our behalf, and some that also use it for their own purposes:
| Provider | What for | Where |
|---|---|---|
| Stripe (the Stripe group, including Stripe Payments Australia Pty Ltd and Stripe, LLC in the United States) | Payments, fraud prevention, tax and legal compliance. Stripe acts for us as a processor and, for its own fraud-prevention and legal-compliance uses, as an independent controller under its own privacy policy. | Australia, the US and other countries where Stripe operates; transfers rely on Stripe's data-transfer terms (standard contractual clauses and, where applicable, the Data Privacy Framework) |
| Amazon Web Services (Amazon SES) | Sending email (our main sender), including your challenge emails and the offer email to a local business | Australia (Sydney) |
| Resend | Sending email when Amazon SES is unavailable | US |
| Anthropic | Generating your script from your prompt, and the next part of an interactive session from what you say (transcribed text only, never audio); checking shared intentions and the display name and description of a voice you publish (text only, never audio); reviewing pictures you upload for your voice or for an event (the image only); checking live-session chat messages and the text of chat voice messages (text only); answering your questions in a 2hives Assistant call (transcribed text only, never audio); drafting and checking the words of a local business's spoken line from its public website page (text only) | United States |
| Amazon Web Services (Amazon Bedrock) | A backup for the Anthropic tasks above, used only when our main connection to Anthropic is unavailable: the same text or images, never audio | Australia |
| Amazon Web Services (Amazon S3 and Amazon EC2, in our own AWS account) | Keeping a copy of our database in Amazon S3 (encrypted at rest by Amazon), encrypted backups of our files (we encrypt them before upload and keep the key), and a standby server that can run 2hives if our own computer fails | Australia (Sydney) |
| Backblaze, Inc. | A second, off-site copy of our database and files for disaster recovery. We encrypt it before upload and keep the key; Backblaze cannot read it | United States |
| Cloudflare | Website delivery and security | Global network |
| Cloudflare Turnstile | Checking that sign-ups, previews and sessions come from a person, not a bot | Global network |
| Only if you choose Google sign-in | Global | |
| Google Ads (Google LLC) | Measuring which of our ads lead to sign-ups, listening and purchases (conversion tracking) | US, global |
| Google Analytics (Google LLC) | Aggregated statistics on how the site is used: pages viewed, sign-ups, listening starts, purchases and a few key actions (an event name and page type only) | US, global |
| Meta Platforms (Meta Platforms Ireland Ltd / Meta Platforms, Inc.) | Measuring which of our Facebook and Instagram ads lead to sign-ups and purchases (Meta Pixel and Conversions API). Only if you accept cookies. For sign-ups and purchases, our server also sends Meta a one-way hashed (SHA-256) copy of your email address, Meta's own cookie ids (_fbp, _fbc), and the IP address and browser type (user agent) of the device you used, so Meta can match the event and count it only once alongside the pixel. The IP address and browser type go to Meta only, never to TikTok or Reddit. Meta discards the hashed email after matching. |
US, Ireland, global |
| TikTok (TikTok Pte. Ltd. / TikTok Technology Ltd, Ireland) | Measuring which of our TikTok ads lead to sign-ups and purchases (TikTok Pixel and Events API). Only if you accept cookies; hashed email as for Meta. | Singapore, Ireland, US, global |
| Reddit (Reddit, Inc.) | Measuring which of our Reddit ads lead to sign-ups and purchases (Reddit Pixel and Conversions API). Only if you accept cookies; hashed email as for Meta. | US, global |
| Microsoft Advertising (Microsoft Corporation) | Measuring which of our ads on Bing and Microsoft's network lead to sign-ups and purchases (UET tag). Only if you accept cookies. | US, global |
| Quora (Quora, Inc.) | Measuring which of our Quora ads lead to sign-ups and purchases (Quora Pixel). Only if you accept cookies. | US, global |
| Spotify (Spotify AB) | Measuring which of our Spotify ads lead to sign-ups and purchases (Spotify Pixel). Only if you accept cookies. | Sweden, US, global |
Your programs are rendered on our own servers in Australia.
- Website and apps. The advertising and analytics companies in the table (Google Ads, Google Analytics, Meta, TikTok, Reddit, Microsoft, Quora and Spotify) apply to our website (for most of them only after you accept cookies; see Cookies). The 2hives apps for iPhone and Android contain no advertising or analytics software from them and send them no events or pixels, wherever you are and whatever you chose on the website. The one thing that connects the Android app to Google Ads is the install referrer described in The Android app and the ad that brought you.
- Sleep partner (apps too). The one piece of partner advertising that also appears in the apps is the sleep partner line described under Your sleep partner.
- Some of these providers are outside Australia: the countries are in the "Where" column above (mainly the United States; Cloudflare works through a global network, and the advertising companies are global). We take reasonable steps to make sure they protect your information (APP 8). For people in the EU, the EEA, the UK and Switzerland, a transfer to a provider outside those places relies on the safeguards the provider offers (EU standard contractual clauses with the UK addendum, or the EU-US Data Privacy Framework where the provider is certified); the advertising companies receive data only if you press Accept in the cookie banner. You can ask us at info@2hives.com how a particular transfer is protected.
- We don't sell your personal information. We don't share your prompts or audio with other customers.
- Our AI providers receive only the text (or, where a section says so, the image) that each feature needs, and never your audio. Anthropic receives this content under its own consumer terms, not as our processor: it may keep it for a period, may use it to improve its models unless training is switched off, and may review items flagged for safety. We do not control what Anthropic does with it and cannot recall it once sent. Where Amazon Bedrock is used as the backup (Australia), Amazon's terms apply instead. You can switch AI features off at any time (see "AI features (optional)" below).
AI features (optional)
Features that write or check something with an AI provider (your session script, an interactive session, a shared intention, a picture or a message check, the 2hives Assistant) work only after you give your permission. Our basis is your consent, and explicit consent for anything you type or say that is health information. Anything you type or say may be sent to Anthropic as text (or, for pictures, as the image) so that the feature can work; section 3 explains what Anthropic does with it.
Pictures. A picture you upload (a profile picture, a team picture, or the picture for an event or a group) is sent to an outside AI to check that it is suitable to show only after a second, separate permission. We ask for it once, at the moment you first upload such a picture. If you say no, the picture is not uploaded and nothing is sent.
To withdraw: go to Account > AI features. You can switch all AI features off or only picture checking. New content then stops being sent at once. What was already sent cannot be recalled by us. Sessions you have already made stay in your library.
Cookies
Strictly necessary cookies are always on: your sign-in session (and, for up to 30 minutes after you ask for a sign-in link, a cookie that lets the same browser open it without a second tap), an anonymous visitor identifier that keeps unsaved programs private to your browser (and, outside the European Economic Area, the United Kingdom and Switzerland, remembers a sleep-partner link you opened before signing in), your language and cookie choices, a referral cookie for up to 30 days when you arrive through a referral link, the Google Ads click identifier for up to 90 days when you arrive from one of our ads, a cookie that lasts 24 hours after someone answers that they are under 18 (so the answer cannot be changed straight away), and a cookie that remembers for up to an hour that you confirmed you are an adult.
Google Ads and Google Analytics cookies are set only if you choose Accept in the cookie banner. We use Google's consent mode: until you accept, the Google tag stores nothing on your device and sends Google only cookieless signals (such as that a page was viewed or a purchase was made), without advertising or analytics identifiers. The events we send describe our products (a course, a price, an order number), never your name, email address or account. If you decline, nothing changes for you on 2hives. We remember your choice for 12 months, and you can change it at any time with Cookie settings at the bottom of every page. The Google tag is never loaded on your library or account pages.
Google's use of this data is described in How Google uses information from sites that use its services.
Other first-party cookies and browser storage. To test two versions of a page or a feature we may set a cookie holding a letter for the version you were shown (for example twh_hero, twh_fv, twh_imm; up to 12 months). In the EU, the EEA, the UK and Switzerland, and where we can't tell where you are, these are set only after you press Accept. We also set: a cookie that remembers your answer about AI features (12 months); a cookie that holds the name of a sign-up or purchase event, with no personal details, for up to an hour until the page that reports it has loaded; short-lived signed cookies for the sign-in steps (Google and Apple sign-in, security tokens on forms); and, only if you use the feature, a cookie for a guest's first name in a Listen together room (1 day), for a venue's tablet, or for a review link you were given. Your browser's own storage (local storage or IndexedDB) holds the random device identifier described under "Abuse prevention", your playback and headphone-check preferences, a note that you have already seen a banner or a first-session tip, and a small queue of usage events that could not be sent, which is kept for at most 30 days. Nothing in this paragraph is shared with an advertising company.
YouTube. The live channel page (/live) shows a still picture of our own. Only when you press play does your browser load the YouTube player (youtube-nocookie.com); YouTube (Google) then receives your IP address and its own cookies and terms apply.
Meta, TikTok, Reddit, Microsoft, Quora and Spotify advertising cookies and pixels load only after you choose Accept; until then nothing at all is sent to these companies, and if you decline, nothing ever is. They measure which ads lead to sign-ups and purchases; we send them product data (a course, a price, an order number) and, for sign-ups and purchases, the matching data listed in section 3, such as a hashed email address, never your name. Their cookies (for example _fbp, _fbc, _ttp, _rdt_uuid, _uetsid) last up to 13 months. Click identifiers from their ads (ttclid, rdt_cid, msclkid) are kept in our own cookies for 30 days and only sent to the matching company if you accept. You can change your choice at any time with Cookie settings.
The Android app and the ad that brought you
Status. This is not switched on yet: today the 2hives app sends us nothing from Google Play. We will switch it on only after this text is live and the Android app that does what follows is available in Google Play.
What we read. When you install the 2hives app from Google Play on Android, Google Play keeps a short piece of text called the install referrer: whatever was in the Play link you came from. If you came from one of our own ads or links, it holds campaign tags (such as utm_source) and an ad click identifier (for a Google ad, the gclid). The first time you open a newly installed app, 2hives reads that text, and only that text, from Google Play and sends it to us over an encrypted connection, together with the technical details every request to 2hives carries (your IP address, which we keep in server logs for up to 30 days, and the app version). We do not read your Google account, your advertising ID or any identifier of your phone. We keep only the campaign tags and click identifiers we recognise and discard anything else in the text. A click identifier identifies a click, and once you sign up it is linked to your account, so it is personal information.
Where. Only in Australia and New Zealand. The app first checks the country of your SIM card and mobile network on your phone. If it can't tell, or the country is any other, it reads nothing from Google Play and sends nothing. Our server checks the country of your connection as well, and stores nothing if the country is missing, unknown or any other. We do not do this in the European Union or EEA, the United Kingdom, Switzerland or anywhere else, because the app has no way to ask for your consent there.
When. Once: the first time you open the app after installing it (not when an existing app is updated). If the text can't be sent (for example you have no connection), the app tries again the next time you open it, at most three times in all, then stops.
Why. To measure which ad or link brought an install and, if you then sign up, which campaign led to the sign-up, so we can see which of our ads and links work.
What happens to it. We store the campaign tags the way we store the same details when you arrive on our website from an ad (see "How you found us" in section 1): with your browser's anonymous ID for 30 days and, if you sign up, with your account. If the text holds a Google ad click identifier, we keep it for 90 days and then delete it, and we upload it to Google Ads, with the type of event (such as "signed up") and its time, so that Google Ads can tell which of its ads led to a sign-up. Google can link that identifier to the ad click on your Google account. We do not send it to Meta, TikTok, Reddit, Microsoft or anyone else, and we send them nothing from the app.
What we do not do. We do not use your advertising ID, we add no advertising software to the app (the only Google code added for this is Google's Play Install Referrer library, which reads the text described above), and we do not follow you across other apps. You can ask us to delete what we hold about you (see section 5); we can't delete Google's own records, which you manage in your Google account.
Crash reports (apps only)
If the 2hives app for iPhone or Android crashes, it can send us one small technical report the next time you open it: the app version and build, the platform and operating system version, the kind of problem (such as a crash or a frozen app), the technical name of the error, up to 30 lines saying where in the code it happened, and the time. It does not include your name, email address, account, device identifier, cookies, the page you were on, any message text or anything you typed or listened to. We don't store your IP address with the report and use it only to limit how many reports can arrive per hour; like every request to 2hives, the request itself appears in our server logs for up to 30 days. Reports are not linked to your account, so closing your account does not delete them; they are deleted after 90 days. We use no crash-reporting service from another company, and we do not share the reports. We keep them for 90 days to find and fix bugs, and then delete them.
In Australia, New Zealand and elsewhere outside the EU, EEA, UK and Switzerland, this is on by default, and you can switch it off in the app under Account (Send anonymous crash reports). In the EU, EEA, UK and Switzerland (and where your country is reported as unknown) it is off until you switch it on there. If it is off, the app deletes the waiting report on your phone without sending it.
Voice recordings and voice models
A voice is sensitive personal information: it can identify you, much like biometric data. So we handle it with extra care:
- Only with your explicit opt-in, 18 or older. We make a voice model only when you ask for it, confirm you are 18 or older, tick the consent box, and read a consent sentence that includes your name. We check that every recording is the same person as the consent recording, and we use random sentences and a random phrase in each session so an old recording can't be replayed. You can only record live in your browser; we don't accept uploaded audio files.
- What we do with the recordings. We clean them up (trim silence, reduce background noise, even out the volume), transcribe them on our own servers to check that you read the sentence, and compare voice characteristics to confirm it is the same person. From the best recordings we make a voice model. We then test the model by having it read a few lines (including your name) and check that the result is clear and sounds like you. The recordings you made in a session are deleted once your voice is built or the session expires, unless you tick the "Help bring 2hives to my language" box (see below). The model's reference recording and your consent recording are kept with the model.
- Your own sessions. A private voice is used only for sessions you make. You choose whether it reads a whole session or only your personal lines.
- Community voices (only if you choose to publish). If you make your voice public, you give a separate consent (a checkbox and a second spoken sentence). Other 2hives users can then hear a short sample and choose your voice for their own sessions. Your public profile shows only the display name and description you choose, which need not be your real name, and never your account details. Every public voice is reviewed automatically before it is listed: text checks run first, then an AI service acting for us (Anthropic, see section 3) checks the display name and description and approves or rejects it straight away; anything it is unsure about goes to a person at 2hives. Only the display name and description are sent, never your audio. A person can still review a voice after reports from other users. You can unpublish or delete your voice at any time. After that, nobody can make new audio with it, but sessions other people already made with it stay playable for them. We keep a record of which sessions used your voice (session and order numbers and amounts), so a revenue share could be offered in the future. We don't pay voice owners at present.
- Watermark. Every line spoken in a cloned voice carries an inaudible watermark (AudioSeal) that identifies it as synthetic and lets us trace it to the session it was made for.
- Founder messages. Some messages from the founder on our site use an AI version of the founder's own voice, with his consent. They are labelled where you listen to them ("Gergo's voice, made with AI") and in the audio file itself.
- Not used for training unless you choose it: your voice model is used only to speak sessions, never to train or improve any AI model, by us or anyone else. Your own-voice recordings are not used for training either, unless you tick the separate "Help bring 2hives to my language" box (below). Not sold. All voice processing happens on our own servers in Australia; no voice audio is sent to any outside provider other than our encrypted backups (see Amazon Web Services and Backblaze in section 3).
- Help bring 2hives to my language (optional, only if you tick it). When you record your voice, a separate box asks whether we may also use your recordings to train 2hives voice models for your language. It is never ticked for you, and your voice works the same either way. If you tick it, we keep the sentence recordings you made for your voice after it is built, encrypted with a key unique to your account, and use them only to train 2hives voice models. They are never used to make a voice that sounds like you available to anyone, as a public voice or in our products. We record the opt-in with its time, a consent ID and the country your connection came from. You can withdraw at any time with Withdraw from training on your voice page; deleting your voice or closing your account also withdraws. We then delete the recordings immediately, and from backups within 90 days, and leave them out of every future training round. A model already trained with them can't "unlearn" them, so we stop using those model versions. If you don't tick the box, the recordings are deleted once your voice is built, as described above.
- Protected: recordings and models are stored encrypted with a key unique to your account, readable only by our voice and rendering services.
- Kept until you delete it. You can delete your voice at any time; closing your account deletes it too. Either way, we delete the recordings, the model and any audio cached from it immediately, and from backups within 90 days. Sessions already made with it, by you or by other users, stay with them.
- Your data export lists your voices, their languages, status and consent records (including any "Help bring 2hives to my language" opt-in), and your publications, ratings and reports. It does not include the audio itself.
Profile pictures
If you have a voice, a profile picture is shown next to it: in Community voices, in the voice picker and on your own "My voice" card.
- Your choice. If you don't choose a picture, we show a generated avatar (colours and the initials of your public display name). You can instead pick one of our abstract 2hives pictures, or upload your own.
- Uploading (optional). You can upload a JPG, PNG or WebP image of up to 5 MB. It is cropped square in your browser, and our server saves it again as a new image in two sizes. We remove all metadata, such as camera details, location (GPS) and colour profiles. The files get random names and are stored on our own servers in Australia.
- Review before others see it. Before anyone else sees an uploaded picture, an AI model acting for us (Anthropic's Claude, see section 3) checks it for nudity, violence, hate symbols, children, famous people or several people, logos or advertising, contact details, links or QR codes, offensive gestures, and disturbing images. Only the image is sent, never your name or account details. Until a picture is approved, or if it is rejected, others see your chosen 2hives picture or the generated avatar. If it is rejected, we show you a short reason. Other users can report a picture; after reports from 3 different people it is hidden until a moderator decides.
- Used only for this. We use your picture only to show it next to your voice. We never use it for anything else, and never to train any AI model.
- Removing it. You can remove your picture at any time in the "My voice" section of your account; we then delete the files immediately. Closing your account deletes it too. Your data export includes the picture itself.
Reading sessions for 2hives voices
Anyone with an account can read sentences aloud to help us build the synthetic guide voices used in 2hives sessions. This is separate from "Your own voice": recordings made for your own voice are used for training only if you tick that page's own, separate "Help bring 2hives to my language" box.
-
Only with your explicit consent, 18 or older. Before you start, you confirm that you are 18 or older, tick a consent box, and read a consent statement aloud that includes your name. We keep a record of what you agreed to and when:
- the statement and its transcript;
- a fingerprint (hash) of the recording;
- the time;
- the country your connection came from.
This consent is recorded separately from any other consent you have given us.
-
What we collect.
- Your recordings of the sentences and of the consent statement.
- The automatic check results for each recording (noise, loudness, length, and how closely an automatic transcript matched the sentence).
- Your progress through the script.
-
What we do with it.
- We use your recordings to train synthetic voices.
- 2hives may use those voices as guide voices in its products, including paid products (commercial use).
- The trained voice does not reproduce your recordings, but it may sound like you.
- We do not sell your recordings or share them with other companies.
- All recording, checking and training happens on our own servers in Australia.
-
Checked take by take. Reading is open to everyone who signs in. Every recording is checked automatically as you make it, and only recordings that pass the checks, or that you choose to keep after a check, are used. A person at 2hives can review a reader's recordings at any time, hold them back from training, or stop an account from reading if it is misused.
-
Thanks. Until 27 October 2026, accepted reading in one language earned 3 months of what was then called 2hives Plus at 30 minutes and 12 months in all at 60 minutes, once per person. Plus is no longer offered; listening is free for everyone. People with accepted reading on or before that date can still earn it until 26 gen 2027. To honour this we add up the length of your accepted recordings, and we keep a record of each grant with your account: the language, the minutes counted, the days given and when. So that the thanks is given only once per person, that record also holds a one-way code made from your email address (never the address itself). We keep that code until 26 gen 2028 so that we can answer any question about the thanks you were owed, and then delete it, even if your account stays open.
-
Credits page (only if you choose it). If you tick the separate, unticked box "List my name (or a name I choose) on the Credits page", we show that name there, publicly and worldwide, until you remove it; anyone can copy what is public. The box is separate from your recording consent, and you can untick it at any time. We list nobody without it.
-
Protected. Recordings are stored encrypted with a key unique to your account. Only our training process and you (to play back your own takes) can read them.
-
Withdrawing.
- You can withdraw at any time on the reading page, or by closing your account.
- We then delete all your recordings immediately, and from backups within 90 days.
- They are left out of every future training round.
- A voice that was already trained with them can't "unlearn" them. We stop using those versions and do not publish new ones made with your recordings.
- We keep the consent record (without audio) to show what you agreed to and when you withdrew.
- Thanks you already received stays with you.
-
Retention. Recordings are kept until you withdraw or close your account. The consent record is kept as long as we use, or could be asked about, a voice trained with your recordings.
-
Your data export includes your consent record, status and number of recordings. It does not include the audio.
Voice review
Where available, people who speak a language natively can help check how 2hives voices sound in it, through an invitation link or from their account.
- What we keep: your ratings (how natural a clip sounds, whether its words are pronounced well, which of two versions you prefer), the words you mark together with the sentence they appear in, an optional typed hint, and an optional short recording of you saying a word.
- Your recording (only if you agree): used only to correct how 2hives voices pronounce that word, never to make a voice that sounds like you.
- How your answers are used: to decide which voice versions we use and to fix how words are pronounced, that is, to improve 2hives voices.
- Who you are to us: if you join with an invitation link, your answers are linked only to a random code, not to a name, email address or account. If you join from your account, or sign in to be thanked, your answers are linked to your account.
- Thanks and credits: if you earned thanks days, we record each reward with your account. Your display name appears on our credits page only if you choose it, and you can remove it at any time.
- Deleting: you can delete everything you gave at any time with "Delete everything I gave" on the review page. Closing your account deletes it too. Your data export includes your answers, but not audio.
Language votes and helping
If a language you would like is not on 2hives yet, or its voice is still being made, you can say so and offer to help.
- A vote: we keep the language, the date, and a one-way code made from your email address (never the address itself), so the same person counts once. We also note whether you were signed in. Nothing else is stored with a vote.
- Offering to help: you need an account. We keep the language, what you offered (check the voice, read sentences aloud, or check the translation), and whether you said you speak the language natively. Translation checks you send (approve, or a suggested fix) are kept with your account. Reading sessions and voice review have their own sections above.
- Why: to count demand, to decide which languages to build next, and to thank you. The counts are seen by the 2hives team. When a language reaches our thresholds we only note it for the owners to decide; nothing is published automatically.
- Machine translation of the helper pages: when a language gets its first vote or helper, we may translate the text of the voice review, reading and language pages into it with an AI service acting for us. Only the page text is sent, never your data. These pages say they are machine translated and are kept out of search engines until a native speaker has checked them.
- "Not now" and "Tell me when the voice is live": if you dismiss the help card while signed in, we remember it on your account so it does not come back. If you tick "Tell me when the voice is live", we keep that request and send you one email when the voice is live; you can stop it with the link in that email or by unticking the box. A suppression or "stop emails" setting is always respected.
- Deleting: closing your account deletes your help sign-ups, translation checks, voice-live requests and your vote. Your data export includes them.
Interactive guided sessions
In an interactive session the guide listens to your answers. Because your voice can identify you, we handle it like the "Your own voice" recordings above:
- Only with your explicit consent, given on the consent screen before each session (18 or older, microphone, AI guide). You can choose Don't keep my voice: the recording then keeps only the guide and the tones.
- Saving is your choice. Before each session you choose whether to save this session to your library (off by default for the trial session, on by default for paid sessions). Not saved: nothing is recorded; your microphone audio is transcribed as you speak and not kept, and the transcript exists only in our server's memory during the session. Afterwards we keep only a minimal record: when it ran and for how long, its status, your guide and audio settings, how it was paid for, the cost of the AI calls and, if the safety check stopped it, the kind of concern and when (not your words). Saved: the recording, the transcript, your settings and a written summary are kept in your library, as described below.
- How it works: your microphone audio is transcribed on our own servers in Australia. Only the transcribed text (never the audio) is sent to Anthropic to write the next part, and to check for signs that you may need urgent help. Anthropic handles it under its own terms (see section 3); 2hives does not use it to train any model.
- Safety: if what you say suggests you may be in danger, the session stops, shows crisis lines, and the session is flagged so that our team can review it.
- Protected and yours: recordings are stored encrypted with a key for your account, readable only by you through your library. Delete a session there at any time; closing your account deletes all of them. Your data export includes each session's details, transcript and summary (not the audio).
- The trial session: to keep the one-time trial session (at no charge) to one per person, we keep a one-way hash of your email address (and of your Google account if you sign in with Google), also after you close your account, and for 30 days a one-way hash of your IP address and its network prefix.
Gifts
When you give a 2hives session or course, you tell us about the person you're giving it to:
- What we keep: their first name (and how to pronounce it), their email address if you ask us to email the gift, your personal message, the intention you wrote for their script, the guide and language you chose, and when to deliver it. We use these only to deliver the gift, show it on the gift page and personalise the session once it's opened.
- Please only give us details you are allowed to share. We email the recipient once, at the delivery time you choose (and never add them to marketing lists). If they don't open the gift, we don't contact them again.
- The gift link: anyone with the link can see the gift page (the first name, your message and the course) and open the gift, so share it only with the recipient. Gift pages are not shown in search engines.
- "Gift opened" note: if you ask for it, we email you when the gift is first opened; we don't tell you anything else about how the recipient uses 2hives.
- When it's opened, the session becomes part of the recipient's own account and this policy applies to them as a 2hives user. They can change the intention and the name in their session.
- Deletion: if the recipient closes their account, we remove their name, email address and your message from the gift record. If you close yours, gifts you paid for still work for their recipients; the order record is kept for tax purposes.
Live together sessions
Live together sessions are group listening sessions, free, every week:
- Listening: while you listen, your browser sends an anonymous signal every 20 seconds so we can show how many people are listening. It carries a random number made for that browser tab, not your account; we keep it in memory for under a minute and never store it.
- Reminders (only if you ask): we keep that you asked for a reminder for a session and email you a day before and 15 minutes before it starts. Every reminder has a link to stop them.
- Reflection wall (only if you post): to post you must be signed in and 18 or older. We keep your post, the name you chose to show (optional; it can be a nickname) and your account ID with it. Other visitors see only the post and that name, never your email or account. Posts are checked automatically before they appear: a post that suggests someone may be in danger is not shown, and we show the writer crisis lines; posts with health claims are held for a moderator; anyone can report a post. Our team can see and remove any post.
- Deletion: you can ask us to remove a post at any time (info@2hives.com); closing your account deletes your posts and reminders.
Shared intentions in live sessions
If you choose to share an intention during a live group session, we turn a voice recording into text on our servers and delete the recording straight away; we never store or replay your voice. The text is checked automatically (and may be checked by a moderator and an AI service acting for us) and, if it fits, read aloud anonymously by the session's synthetic guide voice to everyone listening. We show your city or country only if you ask us to. We keep the text with the session for 30 days for moderation and safety review, together with a link to your account so we can act on misuse; after 30 days both are deleted. If what you share suggests you may be in danger, we never read it aloud and we show you help lines for your country. You can export or delete this data from your account at any time.
Abuse prevention
Our service runs on our own computers, so we protect it from automated sign-ups. Signing up is not blocked because of your network: offices, universities and mobile networks share one address. Only an unusually large burst of attempts from one address can be paused for a while.
- Turnstile by Cloudflare: a privacy-friendly check that a person, not a bot, is signing up, making a preview or starting a session. Cloudflare processes it for us as a service provider.
- Device signal: a random identifier that 2hives makes up itself, in a first-party cookie and in your browser's local storage (in the apps, in the app's own web storage), so one device doesn't collect each offer many times. It is not your phone's advertising ID or hardware identifier, it is not shared with anyone, and it contains nothing about you.
- Network signal: we keep only a one-way hash of your IP address and its network prefix (for example 203.0.113.0/24), never the address itself, and we delete both after 30 days.
- Mailbox: we keep a one-way hash of your email address with dots and "+tags" removed, so one mailbox gets each offer only once. If these signals look unusual, an offer can start a little later while we check; your account works as usual in the meantime.
Live session chat
On a live together session page there is a short chat, open for 10 minutes before and 10 minutes after the session (never while it plays).
- To write you must be signed in, 18 or older, and choose a name to show (a nickname). Others see only that name and your message, never your email or account.
- Voice messages (only if you use them): your microphone records only while you hold the 🎙 button (or between two presses), for at most 30 seconds. We turn the recording into text on our own servers, even out its volume, remove any file details and keep it so others in the chat can play it.
- Automatic checks: every message, and the text of every voice message, is checked before anyone else sees it: first by our own filters, then by an AI service (Anthropic) that receives only the text of the message and the last few messages in the room, never your email, account or audio. A message may be held for a moderator or not shown. If a message suggests you may be in danger, we don't show it, we show you help lines, and our team is alerted.
- Never used for training: chat messages and voice messages are never used to train voices or AI models.
- Kept for 48 hours together with the result of the checks, then deleted. They are included when you export your data and deleted when you close your account.
Hosted groups
Signed-in members aged 18 or older can host a private group session (by invitation) or a public group event that anyone can find and join.
- What is public for a public event: the host name the host chooses, the event's title, description, date and time, and its language. The host's account and email are never shown.
- What the host sees: the names guests choose in the chat, and, for private groups, the email addresses the host typed in to send invitations. Never a guest's account or email otherwise.
- Invitations by email (private groups): we send the invitation and keep the address with the group so the host can see whom they invited; it is deleted with the group or when the host closes their account. We don't use it for anything else.
- Automatic checks: the host name, title, description and intention are checked automatically before a public event appears (first by our own filters, then by an AI service, Anthropic, text only), and an intention is turned into the session's words by our script writer. No person reviews a public event before it is published.
- Event picture (optional): a host can upload a JPEG, PNG or WebP image of up to 8 MB as the picture of a public or private event. Our server saves it again as a new image: all metadata, such as camera details and location (GPS), is removed, and it is cropped to a standard shape, resized and stored on our own servers in Australia, not at public file addresses. Before it is shown, an AI model acting for us (Anthropic, see section 3) checks the image for nudity, violence, hate symbols, children, famous people, logos and text; any text in it is read and checked against our content rules. Only the image is sent, never your name or account details. If the check can't run, the picture is not saved and the host is asked to try again later. No person reviews it first, but anyone can report it and our team can remove it. For a public event the picture is shown on the event page and in listings; for a private group, only to people who have the link. It is deleted when the host removes it, when the event is cancelled or when the account is deleted, and it is never used to train any AI model.
- Events without an uploaded picture show a picture that our own software draws from the event's title and description. No outside service is involved.
- Host's own voice: if a host chooses to use their own synthetic voice for an event, everyone who joins that event hears it.
- Chat in a group works as in every live session (see above), including the automatic checks and help for anyone in crisis. Reports go to the 2hives team, not to the host.
- Records: we keep each public event's details and the result of its checks while it is listed and for 12 months after it ends, and moderation records (reports, removals, suspensions and the reasons) for 12 months, to handle reports, repeat problems and requests from regulators.
Challenge listening
If you join the 2hives Guided Meditation Challenge, this is what we keep, and why:
- What we keep: against your account, the minutes you listened on each day of the challenge, so that we can tell whether you reached 10 minutes, and the hours of the day you listened, for a time-of-day view that only you see. We also keep, worked out from the positions you listened to, how long you listened to each beat range of the audio (delta, theta, alpha or beta; the beat range is the difference between the two tones in the audio, so it describes the audio and not you), by day and by session, so that we can show you your own numbers; only you see them, and your "Your month" share card shows them only if you tick that box. With it we keep your time zone, whether you chose to see your streak, calendar and badges, whether you chose the daily email, that you confirmed you are 18 or older, when you accepted the challenge rules, and when you ticked each email box (so that we can show that you agreed). When you join we also keep, once, where you came from: the campaign details in the link you used (utm source, medium, campaign and content, a referral code) and the website that sent you, so that we can see which of our own links and ads lead to sign-ups. This first-touch record is kept with your enrolment, is not shown to anyone but our admin pages in totals by source, and is never used to change what you are offered.
- Who sees it: only you. Your streak, calendar and badges are shown to you only if the box "Show me my streak, calendar and badges" is ticked. It is ticked when you join, and you can untick it at any time in your settings. The public counter and our admin pages show totals for everyone together, never one person. What a team captain sees, and what a public profile can show if you turn one on, is described in the sections below, and each is your choice.
- Sessions included with the challenge: while you take part you can play a set of ready-made sessions that come with the challenge. Nothing is made for you, and no script is written around your name.
- Emails: the daily email is sent only if you tick that box, and stops when you use the stop link in it, change the setting or leave. Both stop with the stop link. If you join before Day 1, the same box also lets us send one welcome email and one reminder the day before Day 1 (no daily emails before then). The finale invitation is part of the daily email. None of these is an offer.
- Leaving, export and deletion: if you leave the challenge we stop counting and stop the daily email. You can delete your challenge record at any time from your library ("Delete my challenge record"), without closing your account; closing your account deletes it too. Your account export includes your enrolments, when you agreed to each email, and your minutes for each day. The challenge rules are at Challenge rules.
Challenge teams
A team on 2hives can be enrolled in a Guided Meditation Challenge. This is what a team involves:
- Who sees what: the person who runs the team (the captain) sees who is in the team, by the name each member chose and never an email address, so they can remove someone. They also see totals for the whole team, only once at least five people have joined: the share who reached 10 minutes today (as a band: under 40%, 40 to 70% or over 70%), the team streak, total minutes (rounded to the nearest 10), how many joined the team's live session and the team's points (rounded to the nearest 5). A count of 1 or 2 is shown as "fewer than 3". We don't show a number for one person. The captain does not see what anyone listened to, for how long, or who was at a live session, whether a team member or a guest. Taking part is each person's choice.
- The captain and any organisation: the captain is a participant, not 2hives' customer or employer, and we do not act on their behalf. If the captain works for an organisation, the organisation receives nothing from us; it has only what the captain chooses to pass on. Teams are for adults (18 or over), and you confirm that when you start or join one.
- Team names: a team name is shown to the members of the team. If the captain also ticks the leaderboard and name boxes, it is shown to the public, and on members' public profiles. (An open team is different; see below.)
- Open teams (only if the captain chooses): if the captain makes a team open, anyone on the internet can see its page without signing in. It shows only the team's name, a description the captain wrote (200 characters at most), how many members it has and, once the team has at least five members, how many times it sat together and how many days were counted, and the time of its next team session. It never shows a member's name, picture, listening or attendance, and it asks search engines not to list it. The captain publishes the name and the description, so please keep the names of people and contact details out of both. We check them for links, contact details, offers and health claims, but not for names. If a page names or describes a person and that person (or anyone else) objects, use "Report this page" and we will hide the page and delete the words. In an open team the captain sees totals only, and a member appears to the captain as "Member 3" unless that member ticks "Show my name to the captain" (off by default, changeable at any time, and deleted when the member leaves the team or closes their account). If the captain makes the team private again, the page disappears at once and the members stay. To join from the page you sign in or create an account, confirm that you are 18 or older and tick the attendance notice, as for any team. A business can add its own partner code to the page link; it works like any other partner link. Every page has a "Report this page" link, which opens an email to info@2hives.com with the page address filled in. We look at every report and acknowledge it, may hide a page at once, and tell the captain why when we do; the captain can ask us to look again. We keep the report (including the email address of the person who sent it, if they gave one) and our decision for 12 months. We keep the open-team settings (open or private, the page address, the description) with the team and delete them when the team is deleted; the record of who chose to show their name goes when they leave or close their account; and a short record of when a captain opened a team (account number and time) is kept for 7 days to limit how often teams can be opened. Where the GDPR or UK GDPR applies, our basis for the page is the captain's request and our legitimate interest in a safe public page; you can object at info@2hives.com.
- Team picture: the captain or a co-captain can choose one of our generated pictures or upload an image or logo, after ticking that the team has the right to use it. Photos of people are not allowed. An uploaded picture is saved again on our own servers, which removes all hidden data such as camera details and location, and it is checked before it is shown (automatically; where an AI service checks it, Anthropic, see section 3, receives only the image, never a name or account). Anyone signed in can report it, and three reports hide it until a person decides. It is shown to the members of the team. It is shown to the public (on the leaderboard, the team card and members' public profiles) only if the captain also allows the team name to be public; otherwise a plain default picture is shown. The captain can remove or replace it at any time, which deletes the file at once. It is deleted with the team, is part of the captain's data export, and is never used to train any AI model.
- Business QR codes for teams: a business partner can share a team with a QR code. If you scan it we count the visit (a total per day, with no person) and keep in your browser a random code that links the visit to that business and team until the partner first-touch period ends. If you then sign up or join, we link your account to the business and team, only so that the business can see counts ("fewer than 3" if 1 or 2); the link is deleted 180 days after the event, when you leave or when you close your account, and is in your data export. In India nothing is counted until you give the separate consent.
- Inviting people from your own email: "Invite people" on the team page opens your own email app with a message ready to edit and send. 2hives does not send that message and does not see or keep the addresses you type.
- How long a team lasts: a team on 2hives has no end date. It stays until its members leave or nobody has used it for 12 months ("used" means someone opened the team page, joined a session or added to the team). After 11 months without use we show the captain a notice on the team page and send them an email. After 12 months the team is archived: its invite link stops working, its picture and voice messages are deleted, and its page becomes read-only. We delete the rest of an archived team's records 90 days later, unless the captain brings the team back before then.
- What we keep for a team: its name, picture and voice messages, who is in it (the name each member chose, the date they joined, who is the captain or a co-captain), which challenges the team is enrolled in, and the team's sessions. When you leave a team you are removed from its list at once.
- Several teams: you can be in up to five teams. In each challenge your days and your recorded live sessions count for one team of your choice. By default that is the team you joined the challenge through, and you can change it until joining for that challenge closes. We keep your choice for each challenge, and which of your teams you opened last, so the team pages show the right team.
- Attendance at live sessions: being in a team does not record anything about you. We record your attendance at live group sessions only while all of these are true: your team has been enrolled by its captain in a challenge that is running; you joined that challenge yourself; and you agreed to the attendance notice. A captain cannot enrol you or agree for you. If you do not agree, you can still be in the team and take part in the challenge; your live sessions just do not count for the team. You can leave the challenge or the team at any time, and we then delete what was recorded for you there. Outside a challenge your team's sessions are not recorded. Where the GDPR or UK GDPR applies, our basis is that it is needed to run the challenge you chose to join.
- Leaving: if you leave or are removed from a team, the attendance records kept for that team are deleted straight away. Attendance records are in any case deleted 120 days after the session and when you close your account.
- Handing a team over: a captain can hand a team over to another member. We keep the offer (both accounts and the date) until the member answers, the captain cancels it, one of them leaves, the team is archived, or 30 days have passed, whichever is first.
- What the captain sees: only team totals: from five members, a small count shows as "fewer than 3", shares as bands, points to the nearest 5 and minutes to the nearest 10. The captain never sees what anyone listened to or who attended a session, in any challenge.
- Guests at a team's session: a team can share a link to one of its scheduled sessions. If you are signed in, 18 or older and tick the notice on that page, you can join even if you are not in the team or in the challenge. We then keep, against your account and the team's number, a record of each session you attend as a guest: when you arrived and how long you listened. It adds a point for that team, and you can give points to one team a day. The captain sees only team totals, rounded or in bands, never who the guests were. The record is kept for 120 days and then deleted. You can delete it sooner with "Delete my guest records" (on the Team sessions page), or by closing your account.
- Calendar invites for your team's sessions: when the captain or a co-captain schedules, changes or cancels a team session, we email a calendar invite (an .ics file in your own language and time zone) to the captains and to the members who accepted the team notice. The invite names only you as the attendee, never another member, and we keep, against your account and the team, only which version of each series we sent you. Every invite has a "Stop calendar invites for this team" link, and the Team sessions page has the same switch; the record is deleted when you leave the team, with the team and when you close your account.
- Your team's own session: the captain or a co-captain can type a short theme (up to 300 characters) and ask for a session written around it, up to three for the whole challenge. We check the text for safety before anything is written (a text about self-harm or a health claim is refused and not kept), and send only that theme, never a name or an email address, to the outside AI service that writes the script (the text is processed in the United States or Australia). We keep the theme with the team so the captain can see it; it is part of the captain's data export and is deleted with the team. The recording is made once, is not public and can be played only by the team's members and the guests of its sessions.
- Leaderboard (only if the captain chooses): a team can appear on a public leaderboard, ranked by points per member among teams of a similar size (up to 5 members, 6 to 20, 21 to 50, 51 to 100, 101 to 200, 201 or more). The team name is shown only if the captain also allows it; otherwise it appears as "Team 3". For a team with fewer than 5 members only its place and name are shown: no points, no percentages and no member count. For a team with 5 or more members the points are rounded to the nearest 5.
Team voice messages
A captain or co-captain of a challenge team can record a short voice message for the team (at most 90 seconds), or make an AI version of their own voice if they have recorded one with "Your own voice"; an AI version is always labelled. Before the first message the captain agrees that the recording is shared with the team's members and kept until they delete it or the team ends (plus the period a finished team is kept, 12 months), and confirms they are 18 or older. Only signed-in members of that team can hear it: it is never public, never indexed and never in a share card. We make a transcript automatically on our own servers and check it; if it looks unsuitable the message is held for a person at 2hives, and three reports from members hide it until a person has looked. The audio, the transcript and the reports are deleted when the captain deletes the message, when the team is removed and when the captain's account is closed, and the captain's data export includes them. A member can ask to be e-mailed about a new message only while 2hives sends team email; otherwise the notice is in the app only. No message is used to train any model.
Company teams
A captain can upgrade a challenge team to a company team, paid for by a company. This is what that involves:
- What we keep: the payer's account (name and email), the company name and, if given, the company's ABN, the number of seats, the amount (GST included), the date, and the tax invoice we email to the payer. The card is handled by Stripe (see section 3); we never see it. Invoices are kept for 7 years for tax, even if the payer closes their account.
- What the company gets: a logo on the team page and a link to its website, which anyone signed in can report (three reports hide it until a person has looked; free teams cannot add a link), and an aggregate report from five members: participation in bands, never a figure for any person, and never who listened to what. The company does not see more than any other team's captain does.
- The website link: it is shown on the team page and, if the team name is public, on the leaderboard and the team card, with "nofollow", and is included in the captain's data export. It is deleted with the team. If you report a link, the report is deleted when you close your account.
Company pilots
Company pilots. If you start a team pilot for your company at 2hives.com/company, we keep your work email address, your company name, your country (from your connection), the date the pilot started, and the plan you choose, if any. We use them to run the pilot, to send you a short welcome, a weekly report with your team's totals, one email on day 10 with your team's numbers and the plans, and one email when the pilot ends, and to take payment if you choose a plan. The day 10 and end emails carry a link that stops them; the pilot is not affected. Where the GDPR or UK GDPR applies, our basis for the day 10 and end emails is our legitimate interest in telling the person who started a pilot what comes next; you can object at any time with that link or at info@2hives.com, and our basis for the rest is that it is needed to run the pilot you asked for. We do not sell this information or use it for other advertising. We keep it while the team exists and for 12 months after the pilot or the paid plan ends, except invoices and payment records, which we keep for 7 years.
"Tell me when plans open": if you are the pilot administrator and press this button on your team page, we keep your work email address with your team and send you one email when paid plans open in your country, and use the address for nothing else for this purpose. You can take yourself off with "Take me off the waitlist" on the team page or with the link in that email. We delete the request when we have sent the email, when you take yourself off, or 12 months after the pilot ends, whichever is first.
Milestones
A milestone is a run of days in a row, your first 100 minutes, 10 hours, a number of challenge days or a finished course. We work it out from the time you listen to full sessions, and we keep the milestone's name and the date you reached it. After a session we may offer you a card to share. Nothing is public unless you tap a share button. The card shows the milestone, and your profile name only if your public profile is on. If you tick "badges" on your public profile, your milestones show there. Your account export includes your milestones, and closing your account deletes them.
Challenge certificates
If you finish the Guided Meditation Challenge (25 or more counted days), you can make a certificate of completion. It is public only when you make it and share it. Its link can be opened by anyone who has it, and it is not listed in search engines. It shows the challenge name and dates and the issue date, and a name only if you choose to enter one (otherwise "A 2hives member"). You can withdraw it at any time, and the link stops working at once. If you add it to another service yourself, that service's own rules apply to what you add there. Your account export includes your certificates, and closing your account deletes them.
Practice log
After a session you can add an optional private note: how it was (one of three words) and a few lines of your own. We keep it with your account with the date, the session and the minutes you listened, and show it only to you, in your library. It is never shared, never sent to an AI service and never used to train voices or models. Our server checks the note's wording only to show you support lines privately if it sounds like you may be in danger; your note is always saved as you wrote it. It is kept until you delete it or close your account, and it is included when you export your data.
Feedback
When you are signed in, the Feedback form lets you send us an idea or tell us something is not working. We keep what you wrote exactly as you typed it, a cleaned-up copy for reading, the type you chose, the page you came from, your browser and device type, the app version, your language, the time and a reference number such as FB-12. We email a confirmation, and a short email when its status changes, only to your account's email address. An AI service from an outside provider reads each message to sort it, group it with similar ones and write a short English summary for our team; your text is processed in the United States for this, or in Australia when our backup provider (Amazon Web Services) is used. The AI cannot use any tools, files or accounts and sees only your message, without your name or email address. A message that sounds as if someone may be in danger is not sent to the model: you are shown support lines privately and a person reads it. Our team decides what happens next: nothing is built or sent because of your words alone. If we decide to act on an idea, our team writes a task in its own words and it is passed, without your message or your details, to our team and the software tools it uses to make the change. Please do not include passwords or health details. Feedback is kept for 2 years, or until you close your account if that comes first, it is included when you export your data, and you can ask us at info@2hives.com to delete it at any time. You can also attach one image (a screenshot or photo, up to 5 MB). We re-save it as a new, smaller picture, which removes location, camera and other hidden data, and we do not keep the original file. Only the 2hives team can see it. It is never sent to the AI service, and it is deleted together with your message (after 2 years, or when you close your account). Your data export lists the image's size and date.
Press requests
If you ask for a press pass on our Press page, we keep the name, news outlet, email address and link you give, the language of the page and the time. We use them only to reply to you and, if we approve the request, to send you access to our press materials. They are emailed to info@2hives.com and read by our team; we do not share them or use them for marketing. A request does not create an account and gives you no access by itself. We keep it for 12 months, or until you ask us to delete it by writing to info@2hives.com.
Ambassador applications
If you apply on our Ambassadors page, we keep the name, email address, social handles, main platform, audience size range, languages, country and link you give, the language of the page, the time, and the time you ticked the box confirming that you will label your posts. We use them only to reply to you and, if we approve the application, to send you a welcome email with your personal invite link. They are emailed to info@2hives.com and read by our team; we do not share them or use them for marketing. An application does not create an account and gives you no access by itself. We keep it for 12 months, or until you ask us to delete it by writing to info@2hives.com or you delete your account. It is included in your data export when your account uses the same email address.
10-minute help calls
If you ask for a help call on our getting-started page, we keep the first name, phone number, email address, preferred time of day and short note you give, and the time of your request. We use the phone number only to call you back, then delete it: when we close your request, and in any case 30 days after you made it, whatever happened. The note is deleted at the same time. Your request is emailed to info@2hives.com and read by our team; we do not share it, record the call or use it for marketing. We keep the rest (first name, email address, preferred time and a one-line note of how the call went) for 12 months, or until you ask us to delete it by writing to info@2hives.com or you delete your account. It is included in your data export when your account uses the same email address. These calls are for help using 2hives, not counselling.
Our phone line
If you call the 2hives phone number, an AI assistant answers, and it tells you so at the start. We do not record the call, and we keep no audio and no transcript. While you speak, our telephone provider, Twilio, and its speech services turn your words into text and turn the answer back into speech; we do not ask Twilio to record the call. The text of what you say is also sent to our AI provider, Anthropic (see section 3), so that the assistant can answer, so that it can note the topic and what a person should follow up, and so that we can check for signs that you may need urgent help. Only text is sent, never audio and never your phone number. Anthropic handles it under its own terms, not as our processor. We do not keep that text after the call: only what is listed here is kept.
What we keep from a call is a short record: the date and time, how long it lasted, the last three digits of your phone number, a few words on what you asked about, and a summary of at most five lines. The whole number is kept only as a keyed one-way code, used to stop one number calling over and over. If you give a name and an email address so that we can write back, we keep those too. We keep this record for 90 days, or delete it sooner if you write to info@2hives.com. We email the summary to info@2hives.com, where our team reads it, and we use the email address only to reply to you. If you ask for a person, or the assistant cannot help, we also leave a note for our sales team with that summary and the name and email address you gave (never a transcript); we delete the note after 90 days, or when you ask us to delete your call record. The AI assistant gives no health advice and does not itself make phone calls: a person at 2hives follows up by email, or by phone if you ask for a call.
If you say "stop" or ask us to stop texting you, we record your number as a keyed one-way code on our do-not-contact list, with the reason and no name, so that we never text it again. We keep that code until you ask us to remove it by writing to info@2hives.com, because deleting it would let us text you again by mistake.
If you call about a free mention for your business, we may recognise your number from a one-way code of it that we keep for up to 120 days (never the number itself). Only if you ask on the call, we send one text with your own link to the number you are calling from, and we record that you asked: the date, the reference of the call and the business's contact on our agreement record. We keep that record as evidence of your request, as described for sponsor agreements, and it is replaced by a one-way code if you ask us to erase your contact. You agree or say no on the web page, never on the call.
If you ask for a free team for your company, we use the company name and work email address you gave and confirmed to email that address a confirmation link. Nothing is created from the call: the free team is created only if the owner of that mailbox opens the link, and we also leave a note for our sales team. We keep the company name and address you gave for the link for up to 90 days if the link is not used.
Partner cards
Some sessions end with a card from a local business that has a free listing with 2hives. The card is labelled "Ad · from our partner". While some sessions are being prepared, before any audio, you may also see one line of text with a small logo, "Ad · Local partner: <business name>". That line is silent: it is never spoken, never shown during a session, and goes away when the audio starts. Neither the line nor the card is shown before or after a sleep session. A signed-in adult may see at most one line and one card a day. To choose a card near you we use the postcode or suburb you saved in your account or, if you saved none, the rough place your connection suggests (its country and, if your network provider's data gives it, a city, region or approximate point). This works in every country except Canada, China, India and South Korea, and in the European Economic Area, the United Kingdom, Switzerland and Liechtenstein, where we use only a place you typed. We use it once, in memory, to choose a card and check the distance. We never store it, write it to a log or put it in a cookie. We do not use it if your browser sends Do Not Track or Global Privacy Control, and then we use only a postcode you saved. You can turn partner cards off at any time. We keep a small record for each account, only to show at most one line and one card a day and never the same business twice in a row, and delete it after 48 hours unless you chose "Don't show me partners". We do not give any business your name, email, postcode, place, listening or a list of listeners. A business receives only totals, and a total of 1 or 2 is shown as "fewer than 3". We never play or show partner or sponsor lines to people using anonymous play or the ChatGPT app, and a coarse area (a suburb or postcode, or the location hint an assistant gives us) is used only once, in memory, to choose a local line and is never stored. We count a view when a line or a card has been on your screen for one second and a click when you press a card, with no third-party tool and no new cookie. When you press a card you leave 2hives, and the business's own privacy policy applies. You can save, change or remove your place, turn partner cards off, or report a line or a card, from the line, the card or your account page. Where the GDPR or UK GDPR applies, our basis for using a place you typed is your consent, which you withdraw by removing it. The sleep partner line described under Your sleep partner is separate: the daily limit above does not apply to it.
Businesses that bring you to 2hives
If you sign up through a business's QR code, link or code, we store which business that was on your account. We use it to credit that business and to check whether you became an active listener: you signed up, confirmed you are 18 or older, and listened for at least 10 minutes within 14 days. For that we use only your total minutes of listening, not which sessions you played. We never tell the business who you are, your email, your postcode or what you listened to. It receives only totals. If you do not want the business credited, do not enter a code, or press "Not this business" before you finish signing up, or ask us later at info@2hives.com. We keep the link between you and the business for 90 days after that month's count is final (and longer only while a dispute about the count is open), or until you delete your account, then keep only a total for each business and month. Where the GDPR or UK GDPR applies, our basis is our legitimate interest in running and auditing the partner programme honestly; you can object at any time at info@2hives.com. This business record is separate from the sleep partner record described under Your sleep partner, which has its own time limit.
Stopping the misuse of referrals
To stop people gaming the partner programme, we keep a one-way coded version of the network address you signed up from, with your sign-up record, only so that we can count how many sign-ups come from one connection and check them if there are many. We delete it when the month's count is final, at most 60 days after you sign up, and later only if a review or dispute about that month is still open. We describe it as coded, not anonymous: it is still personal information. Where the GDPR or UK GDPR applies, our basis is our legitimate interest in preventing fraud.
Your sleep partner
If you join 2hives through the invite link or QR code of a company that offers 2hives to its customers (a "sleep partner"), or you open that link while you are signed in and do not have a sleep partner yet, we store which company it was, the date, and that the link lasts 12 months from that day. The first link you use is the one that counts. This is a separate record from the credit described under "Businesses that bring you to 2hives", with its own time limit.
We then show "Ad · Your sleep partner: <company>", with the company's logo or name, on the home screen, on the website and in the apps. It is an advertisement and is labelled that way. Choose "Why am I seeing this?" on it to see this explanation.
If you open the link before you have signed in, we remember it until you sign up, using the anonymous visitor identifier described under Cookies. We do not do this in the European Economic Area, the United Kingdom or Switzerland; there the link counts only if you open it while signed in. If you press "Not this business" before you finish signing up, nothing is kept.
Hide stops us showing you that company and stops us counting you in its totals; we keep only a small record that you hid it, so it does not come back, until the 12 months end. Forget (Settings > Partners) deletes the record altogether.
The company never receives your name, your email address or what you listened to. It sees only totals for everyone who joined through its link: how many joined, how many listened for 10 minutes or more, and the minutes listened in total. The minutes are rounded, the figures are updated weekly, and a number under 5 is shown as "<5" (the minutes only appear when at least 5 people listened for 10 minutes or more).
We delete the record 12 months after the link (within 30 days after that), or at once when you use Forget or close your account. It is part of the data you can download. Only accounts confirmed as 18 or older are included.
Where the GDPR or UK GDPR applies, our basis is our legitimate interest in offering partner companies a way to reach people who came to 2hives through them, balanced by your control: you can object at any time by choosing Hide or Forget, or at info@2hives.com, and you can complain to your data protection authority.
Spoken line and card offer
For some businesses in Australia we prepare one short spoken line and a partner card, both at no charge to the business, and send one email with a personal link, and one short reminder 30 days later only if the business has not answered, said no thanks or unsubscribed. We take the business name, what it does, where it is, its website and an email address from the business's own public website, and we record the page where we found the email address. We write only to an address the business has published for people to contact it, and not where the site asks not to be sent promotional email. To draft the line, a text service run by Anthropic reads the business name, its place and the text of its public website page; it handles that under its own terms, not as our processor, and has no Australian region. Amazon SES (Sydney) sends the email, our own computers make the audio, and Cloudflare carries our web traffic through servers around the world, so some of the details may be handled outside Australia.
Nothing is played or shown to listeners unless the business says yes: on its personal page, or, in Australia, by joining as a local partner, where the joining page says a short spoken ad may play. We then email the business the exact words and a link to hear them, and the ad does not play until at least 24 hours after that email is sent. If the business says yes, the line is played, labelled "Ad", to signed-in adult listeners before a session starts (never in a sleep session), and the card is public: a signed-in adult listener in a place where we run these ads can see it, labelled "Ad", once it has passed our check. The business can withdraw both on that page at any time, say no thanks there, or use the unsubscribe link in the email. It can ask us at info@2hives.com to see or correct its details, to tell it where we found them, or to remove them. We keep a record of its answer, with the date and the version of the wording it saw, as described for sponsor agreements. If the business has not answered, about 120 days after we prepare the offer we switch its link off and erase what the offer contained: the line, its audio, the place details and any listing we made for it (unless the business has since used that listing). We keep a record of where we found the email address and why we wrote to it, linked to the address only by a one-way code, and our mailing records: the list the address came from and a log of the emails we sent to it, and, if the business unsubscribes or asks us to stop, its place on our do-not-contact list, so that we can show why we wrote and never write again. Copies in our backups (up to about 3 months) and with the providers named above, including the text service that drafted the line, are held under their own schedules.
Business accounts
This section is for people who join 2hives as a local partner or help manage a partner business. It sits on top of the rest of this policy, and the partner terms explain the programme.
What we keep. When you apply, we keep the business's legal and trading name, its ABN or tax number, country, the contact name and email address you give, its website, the postcodes or suburbs and languages it serves, the time you agreed to the partner terms and which version, and the campaign or QR card that brought you to the sign-up page (remembered in a cookie for up to 90 days). For each team member we keep the email address, the role (owner, editor or viewer) and when they joined. We keep the partner card and every change to it, any picture you upload (re-encoded without camera data), your requests for a hosted session, and a log of who changed what and when. If you ask for printed postcards, we also keep the delivery address you give, only to post them; we delete it 90 days after they are sent or the request is refused.
Listings we prepare. For some businesses we prepare a listing before they have asked, using only details the business has published itself (its name, area, website and a public email address or phone number). We prepare it but do not show it to listeners unless the business says yes to the spoken line and card described under "Spoken line and card offer". It carries a claim code that we keep only as a one-way hash; the plain code appears on the printed card only and is deleted from our systems once the card has been made. A listing nobody claims is deleted 90 days after its code expires.
When you join with your email. We keep the version and time of the partner terms you accepted, a one-way hash of the text shown on the button, and a one-way coded version of your network address, as the record of that acceptance. The confirmation link we email you is single use and expires.
How we use it. To run the programme: to check your application, to show the card once it is approved, to give you totals, to schedule a hosted session, and to send service email (that we received your application, our decisions and the reason, team invitations, ownership checks, and, only if you switch it on, a monthly summary). Apart from the one offer email and the one reminder described under "Spoken line and card offer", and the two service emails about a spoken ad that starts on joining (the exact words before it first plays, and a note that it is live), we send no marketing from this area. To confirm that you control a business we may email a link to an address at your website's domain, or a code to an email address published on your website; we keep only a one-way hash of the link or code, for 30 days.
Who sees what. Listeners see only the approved card (name, one line, picture and link). Your team sees the team list and the business's details. We never give anyone your name or email, or a list of listeners: a partner receives only totals, and any total of 1 or 2 is shown as "fewer than 3". Each month we email the business's contact address a report of totals; it is a service message and carries an unsubscribe link.
Paid packages. If a business buys optional paid packages (businesses only), we keep, for the person who buys and for the business: the terms version accepted, the time, the user account, the quantity and price, the confirmations given (including that the purchase is for a business) and the wording shown; the business's tax or registration number (in full in the business details, masked in the acceptance record), its type and the result of checking it with the official register (ABN Lookup for Australia, VIES for the EU and equivalent registers; the number is sent to that register for the check); the billing country (and, for the United States, the billing state), the country the card was issued in and the country the connection came from; the result of our sanctions and Australian-presence checks; invoices and credit notes with Stripe's reference numbers; and the dates of any change or cancellation. Stripe collects the billing address and any tax number entered at checkout and gives us the country and the number; Stripe keeps the rest. When a business buys, and weekly after that, we compare the business and contact names with the sanctions lists of Australia (DFAT), the European Union, the United Kingdom and the United States (OFAC); a possible match pauses the purchase until a person at 2hives decides. We do this to follow sanctions, tax and consumer law and to prevent fraud. Where the GDPR applies, our legal bases are the contract with the business, a legal obligation, and our legitimate interest in preventing fraud and in checking that a customer is a business. We keep the acceptance record and invoices for 7 years from the purchase for tax and contract record keeping, even if the business or the account is deleted. We do not use Stripe Tax or any merchant-of-record service for these sales.
Your choices. An owner can download the business's data and delete the business at any time; the card, team list, requests and totals are deleted with it. A member can leave a team. If you close your own account you leave every business, and your name is removed from the activity log; if you were the only owner, the business is paused (not deleted) until another owner is added or you ask us to delete it. Where the GDPR applies, our basis is the partner agreement with the business, and your consent for the monthly summary. Deleting the business does not delete the records of a paid package that we must keep (see Paid packages).
The 2hives Assistant
If you start a call with the 2hives Assistant, your microphone audio is sent to our server while the call is open, and our own server turns it into text. The Assistant is an AI: the text of what you say goes to our AI provider (see "Who we share it with") to write its answer, which our server then speaks back to you. Your audio is never sent to the AI provider and is never stored.
We do not keep a recording or a transcript of the call. When the call ends, what was said is gone. We keep only anonymous daily totals (how many calls, how many minutes, how many were passed on to a person or stopped for safety, and the general topics asked about), with nothing that identifies you.
To stop the service being misused, we limit how many calls can be made each day. For this we set a strictly necessary cookie holding a random identifier for your device (kept for up to 12 months), and we count calls per network address for a day. Neither is linked to your account or used for anything else.
If you ask for a person, the Assistant can open the help-call form with your question filled in; nothing is sent until you submit that form (see "10-minute help calls"). If what you say suggests you may be at risk, the call stops and we show crisis support numbers. The Assistant helps with using 2hives; it is not counselling or medical advice.
Playing and keeping your progress in an AI assistant
Anonymous play. When you play a 2hives session through an AI assistant without signing in, and without choosing to keep your progress, we do not create an account for you and we keep no record about you or your conversation. We do not keep your IP address, device details, location or what you said to the assistant together with anything about you. We keep only totals, for example how many times a session was played in a language and country in a day, and how often a session was rated; a star rating is stored without any identifier. If you ask for a personal session made from a menu of choices, we keep the request (kind, length, voice, language) for 7 days with no identifier, and no one can tell who asked. If you ask for a venue or group near you, the assistant may send us a city or region. We use it once to find the nearest ones and do not keep it. Links from an assistant. The links we give an assistant to show you carry a source tag, so that we can count visits for each assistant: the parameters src, source, utm_source (the assistant, for example chatgpt, claude-directory or copilot), utm_medium and utm_campaign (which tool gave the link). The tag is the same for everyone and holds no personal data. A link to a live conversation also carries a short-lived code, made from a value that stands for you in the assistant, so that 2hives.com can check the request came from there; it expires in minutes, and you still sign in on 2hives.com before anything is linked to you. What 2hives.com keeps when you open a link, including how you found us if you later sign up, is described under "How you found us" in section 1 and follows the consent rules stated there. Your assistant is a separate service and may add its own tracking to links. Your assistant (for example ChatGPT, Claude, Copilot or Gemini) is a separate service with its own privacy policy; it holds what you say to it. Like every website, the networks and servers that carry the request to us handle technical data such as your IP address to deliver it: our server logs, which include it, are deleted after 30 days, and our page log keeps only a one-way tag made from the network part of the address, which changes every day, for 90 days (see "What our server itself records"). We do not use any of it to identify you or to show you advertising. We never play sponsor messages in anonymous play or in the ChatGPT app, and we never use personal data for them beyond a coarse area that is not stored. Anonymous play is open to everyone aged 13 and over. If you are under 13, please do not use 2hives; if we learn that someone under 13 has used it, there is nothing to delete because we hold no personal data from anonymous play. Where an assistant offers features for adults (personal sessions in your own words, live conversations, teams, anything paid or sponsored), they open only after you confirm that you are 18 or over, and you sign in on 2hives.com for the rest. Questions: info@2hives.com.
Keeping your progress in an AI assistant
You can listen to 2hives in an AI assistant without signing in, and nothing is kept about you. Not every assistant offers to keep your progress; the ChatGPT app does not at present. If you tap "Yes, keep my progress" and the assistant lets us recognise you, we keep a progress record for you: the sessions you played, your badges, streaks and challenge days, the sessions you saved, and your settings. We do not keep your name, email address, IP address, location, or anything you say to the assistant. The record is tied to a code that we make from an identifier the assistant gives us; the code is not your name, but we can still recognise you by it, so we treat the record as personal information. We use it only to show you your progress and to keep your streak. We do not sell it, use it for advertising, or share it with sponsors. We delete it 6 months after you last use it, and sooner if you ask. The entries for single plays are deleted after 90 days (we keep the counts), and a record we delete leaves our backup copies within about 3 months. To see or delete it, ask the 2hives assistant for "my 2hives data" or press "Delete my 2hives data". You can also link it to your 2hives app account with a code from the app; then it is part of your account. Deleting a chat in the assistant does not delete the record; use the delete button. If you cannot reach the assistant account you used, we cannot find your record; it is deleted automatically after 6 months without use. Your assistant keeps its own records and has its own privacy policy.
Keeping your progress is your choice, and anyone aged 15 or over may choose it here. If you are 13 or 14, you can keep your progress only on 2hives.com, with a parent's agreement (section 7); anonymous play stays open to you. 2hives is not for children under 13. We count the days you listened and show them kindly: we never tell you that you "lost" anything and we never message you to come back. We do not use your record to choose what you see or to show you advertising, and we never use it to guess anything about your health or feelings. If you tell us, or we learn, that you are under 15, we stop keeping your record and delete it. If you do not tap, we keep nothing about you. Features that need an adult (personal sessions you describe in your own words, live conversations, teams, anything paid or sponsored) are for people aged 18 and over. In India, Brazil and South Korea, the button reads "I am 18 or over, keep my progress" and keeping your progress there is for people who say they are 18 or over.
In short (UK): We keep a small progress record only if you say yes. You can delete it whenever you like.
Emails you send us
When you write to info@2hives.com, our team reads your email in a shared mailbox. We keep the sender's name and email address, the subject, the time, the text of the message (stored encrypted), the names and sizes of any attachments (we never open attachments) and our reply. We use them only to answer you, to keep a record of what we told you, and to meet legal duties such as answering a privacy request on time. An AI service from an outside provider may read the text of an email to sort it and to suggest a reply for our team to check; your text is processed in the United States for this. The AI cannot use any tools, files or accounts, and nothing is sent to you until a person has approved it. We keep these emails for 12 months, or until you ask us at info@2hives.com to delete them.
4. How long we keep it
Backups. We keep encrypted backups so that 2hives can be restored after a failure (see Amazon Web Services and Backblaze in section 3). They expire on a schedule: the database copy and file backups after up to about 9 weeks (daily copies for 30 days, then weekly copies for 8 weeks), and the off-site copy after up to about 13 weeks (the same schedule plus a 30-day lock against deletion). When we say below that something is deleted "from backups", the copy leaves our backups as they expire, within about 3 months (at most 95 days) after you delete it.
| Data | Kept for |
|---|---|
| Live session chat messages, voice messages and the results of their checks | 48 hours |
| Progress record kept in an AI assistant (only if you tap "Yes, keep my progress"): the sessions you played, badges, streaks, saved sessions and settings | 6 months after you last use it, or at once if you delete it; entries for single plays 90 days; backup copies within about 3 months (at most 95 days) |
| Public hosted events (details and the results of their checks) | While listed, then 12 months after the event |
| Event pictures you upload | Until you remove them, the event is cancelled or you close your account |
| Hosting moderation records (reports, removals, suspensions) | 12 months; suspensions for as long as they last plus 12 months |
| Account, programs, scripts and audio | Until you delete them or close your account |
| Raw listening events | 90 days (aggregated statistics without personal identifiers may be kept longer) |
| Time you listened to each beat range, by day (only you see it) | 120 days, or until you close your account |
| Time you listened to each beat range, in each session | With the session's listening record, until you close your account |
| Clicks and page views (first-party) | 90 days |
| What our server records (page opens, audio delivered, sign-in steps), with a one-way daily network tag | 90 days; daily totals without identifiers are kept |
| Your answer about AI features | Until you close your account (in a cookie, 12 months) |
| "Email me a link" address | Until the email is sent; at most 6 hours after the chosen time |
| Business interest form (name, town, country, email address) | 7 days if not confirmed; 12 months after it was confirmed |
| Order records | As required by tax law, usually 5 to 7 years |
| Server logs | Up to 30 days |
| Google Ads click identifier (website) | 90 days in your browser; with an order or account, as long as that record |
| Install referrer from Google Play (Android app; Australia and New Zealand only): campaign tags | 30 days with the browser's anonymous ID; with your account if you sign up, as long as the account |
| Install referrer from Google Play: Google Ads click identifier | 90 days, then deleted |
| Crash reports (apps) | 90 days |
| Parent request and agreement for a 13 or 14 year old: the parent's email address (until they decide, or 7 days), then a record of the hash of that address, the time, the terms version and the method | The address: until the parent decides or 7 days; the record of an agreement or withdrawal: while the account exists and up to 3 years after it is deleted; of a declined or unanswered request: 30 days |
| Under-18 lock-out (cookie, and one-way hashes of the email address, the account and the network address) | Used for 24 hours (7 and 30 days for a repeated answer); the repeat count is kept 180 days, then cleared |
| Voice recordings and voice models (if you opt in) | Until you delete them or close your account; deleted within 30 days. Recordings from an unfinished or failed attempt: deleted when the attempt ends (at most 2 hours) |
| Own-voice recordings kept for training (only if you tick "Help bring 2hives to my language") | Until you withdraw, delete the voice or close your account; deleted from backups within 90 days. The opt-in record: as long as we use, or could be asked about, a model trained with them |
| Profile pictures for your voice (if you upload one) | Until you remove it or close your account |
| Record of sessions made with a public voice (ids and amounts) | As long as the related order records |
| Reading-session recordings | Until you withdraw or close your account; deleted from backups within 90 days. Consent records: as long as we use, or could be asked about, a voice trained with them. |
| Reading thanks records (earned by reading) | The grant record: as long as your account exists. The one-way email code with the stage, language, minutes and days: until 26 gen 2028, then deleted, also if your account stays open. |
| Voice review answers, hints and recordings | Until you delete them on the review page or close your account |
| Recording of you saying your name, and the pronunciation made from it | Until you delete it or close your account |
| Interactive session recordings, transcripts and summaries | Until you delete them or close your account |
| Interactive sessions you don't save | Nothing of what you said; the minimal session record until you close your account |
| Trial-session record (one-way hashes) | Email and Google hashes: kept so the trial session stays one per person; IP hashes: 30 days |
| Gift details (recipient's name, email address, message) | Until the gift is opened and for as long as the gift record exists after that; removed when the recipient closes their account. Unopened gifts: until 12 months after they expire (3 years after purchase) |
| Live session reminders and reflection-wall posts | Until you remove them or close your account |
| "Listening now" signals | Under a minute, in memory only |
| Challenge minutes by day, settings, the times you agreed to the rules and to each email, and where you came from when you joined (campaign details in the link and the referring website) (only if you join) | Until you delete your challenge record or close your account |
| Hours of the day you listened (only if you join; only you see them) | 90 days after the edition ends (or after you leave), or until you delete your challenge record or close your account |
| Open team page settings and description | Until the team is deleted |
| "Show my name to the captain" choice (open teams) | Until you leave the team or close your account |
| Record of a captain opening a team (rate limit) | 7 days |
| Live-session record for a challenge team (members, and guests of a team's session) | 120 days after the session, or until you leave the team (members), ask us to delete it (guests) or close your account |
| Team picture (challenge team) | until the captain removes or replaces it, or the team is deleted |
| Company team payments and tax invoices | 7 years (tax law), even if you close your account |
| Paid partner package acceptance records, invoices and credit records | 7 years from the purchase (tax and contract record keeping), even if the business or account is deleted |
| Company team website link and company record | Until the captain removes it, or the team is deleted |
| Milestones (computed from your listening) | Until you close your account |
| Challenge certificate (only if you make one) | Until you withdraw it or close your account |
| Feedback messages (what you wrote, an optional image, the AI-written summary, emails about it) | 2 years, or until you close your account |
| Press pass requests (name, outlet, email address, link) | 12 months |
| Ambassador applications (name, email address, handles, platform, audience range, languages, country, link) | 12 months |
| Help call requests (first name, email address, preferred time, outcome; the phone number and note are deleted when the request is closed and within 30 days at most) | 12 months |
| Phone line call record (date, length, last three digits of the number, topic, summary, and the name and email address if you gave them), and the sales note made from it if you asked for a person | 90 days |
| Phone line business recognition code (a one-way code of a prospect's phone number, not the number) | 120 days, or until the business says no |
| Phone line do-not-contact code (a keyed one-way code of a number whose owner said stop, with the reason, no name) | Until you ask us to remove it |
| Phone line consent record (that you asked on the call for a text with your link: date, call reference, the business's contact) | As long as the agreement it belongs to can be questioned; erasure replaces the contact with a one-way code |
| Partner line and card record (last line and card shown and day, and whether you turned cards off) | 48 hours, or until you turn cards back on |
| The business whose QR code or code you used | 90 days after the month's count is final (longer only during a dispute), or until you delete your account; then only a total |
| Network-address code for the sign-up limit | Until the month's count is final, at most 60 days (longer only while a review or dispute about that month is open) |
| Your saved postcode or suburb, if you saved one | Until you remove it or delete your account |
| Sleep partner record (company, date, expiry, whether you hid it) | 12 months from the link, then deleted within 30 days; at once if you use Forget or close your account |
| Sleep-partner link opened before sign-up (company, date, against the anonymous visitor identifier; not stored in the EEA, UK or Switzerland) | Until you sign up (then it moves to your account record) or 12 months, whichever is first |
| Sleep-partner events (joined, hid; account and company) | 90 days, and at once when you use Forget |
| Business account (details, team, card and its changes, requests, activity log); the delivery address for printed postcards is deleted 90 days after they are sent or refused | Until the business is deleted; a draft listing nobody claimed is deleted 90 days after its claim code expires |
| Ownership-check records (a one-way hash of the link or code we sent) | 30 days |
| Emails sent to info@2hives.com (sender, subject, text, our reply) | 12 months |
| Shared intentions (text and account link) | 30 days after the session |
| Ad platform cookies (Meta, TikTok, Reddit, Microsoft, Quora, Spotify), after you accept | up to 13 months in your browser; their click identifiers in our cookies: 30 days |
| IP address and browser type kept to match a sign-up or purchase with Meta (only if you accept cookies) | Until the event is sent, and at most 30 days |
5. Your choices and rights
- Access and export: download a copy of your data from your account page.
- Correction: update your details from your account page, or ask us.
- Deletion: you can delete your account yourself, at any time, in the app or on the website. Sign in, open Account, then Your data, then Delete my account, and type the word shown. The same page is at https://2hives.com/account on the web. A page that explains what is deleted and what is kept, and needs no sign-in, is at https://2hives.com/delete-account. If you can't sign in, or don't have the app, write to info@2hives.com from the email address of your account with the subject "Delete my account"; we delete the account and reply within 30 days. We delete your programs, scripts, audio and listening history, except what we must keep by law or for safety (order records without your email address, one-way codes that stop a one-time offer being claimed twice, a voice-consent record without audio, and a note that an account was blocked for misuse; the page above lists them). Copies in backups expire within 90 days (section 4).
- Marketing emails: every marketing email has an unsubscribe link (Spam Act 2003). Service emails, such as sign-in links and receipts, are necessary for the service.
- Decisions made by a computer program: a program, without a person, makes these decisions that can affect you. (1) Whether an age answer lets an account be created; it uses the birth year you give, a cookie and one-way hashes of your email address or account number. (2) Whether a chat or voice message, post, shared intention, display name, description, picture or team text is shown, held for a person or hidden; it uses what you wrote or uploaded, and some of these checks are made by an AI service (Anthropic). (3) Whether a session or chat is stopped and help lines are shown because what you said suggests that you may be in danger or are under 18; it uses the transcribed text. (4) Whether sign-ups, previews or offers from one connection are slowed or paused; it uses a one-way hash of your network address, your device signal and the result of the bot check. (5) Whether a recording passes our quality checks so that it can be used; it uses noise, loudness, length and how closely an automatic transcript matched the sentence. You can ask a person at 2hives to review any of these decisions at info@2hives.com.
- EU and UK users: you may also object to or restrict processing, ask for your data in a portable form (the export above), withdraw any consent you gave (without affecting what happened before), and complain to your local data protection authority. The legal bases, our EU representative and the rules for transfers are in For users in the EU, EEA and UK.
6. Security
We use encryption in transit (HTTPS), hashed session tokens, restricted and sandboxed services, and least-privilege access. No system is perfectly secure; if a data breach is likely to cause you serious harm, we will notify you and the OAIC as required by the Notifiable Data Breaches scheme.
7. Children
Anyone can listen to 2hives without an account, and then we do not keep a profile or account for you (the technical information described in section 1 still applies). An account is for people aged 15 and over (see our Terms); a person aged 13 or 14 may keep one only with the agreement of a parent or guardian. We do not knowingly keep an account of anyone under 13, or of anyone under 15 without that agreement. Personal sessions in your own words, live conversations and group sessions, teams, business and sponsor pages, paid plans, sending feedback and sharing a moment are for adults (18 and over). The first time you open one of these features, we ask you once to confirm that you are 18 or over, with your birth year. Where we detect that you are in India, Brazil or South Korea, and in the 2hives apps, we ask when you sign in, and you must be 18 or over (19 in South Korea) to have an account there. We do not keep your birth year: we keep only the date you confirmed, your age band (for example 25-34) and how you confirmed it. If the birth year you choose when we ask the question makes you under 13, we close the account and delete it straight away, and keep only the lock described below, which stops the same browser trying again; there is no way for a parent to agree. If it makes you 13 or 14, we ask you, there and then, for the email address of a parent or guardian and send that address one message with a link to agree and a link to decline. Your account stays for up to 7 days while they decide, with the adult features closed, and with no ads, marketing emails or push messages. We use the address only to send that message and one confirmation, and delete it when they decide or after 7 days. The parent gives their birth year once so that we can check that they are an adult; we do not keep it. If the only parent we asked declines, or no parent answers within 7 days, we delete the account with the same full deletion as the delete button on your account page; the same happens if they later withdraw their agreement, which they can do at any time from the link in the confirmation message. If the parent agrees, we keep a record of it: a scrambled (hashed) copy of the parent's email address, the time, the version of our terms and that the agreement was given by email. We keep that record while the account exists and for up to 3 years after it is deleted (30 days for a declined or unanswered request, with only a note that a request was declined), without your name or email address. If we learn in another way that an account belongs to someone under 15 and no parent has agreed, we suspend it and, once a person has checked it, delete it within 7 days. If someone under 18 has confirmed that they are an adult, we close the adult features for the account. Parents or guardians can write to info@2hives.com.
If someone answers that they are under 18 when we ask the question, the adult features stay closed on that account and a person at 2hives looks at it. Where the question is asked at sign-up, we do not create an account and we do not keep or send an email address; where it is asked later, the account stays for listening, progress and settings. If you tell us you are under 18, or we find that you are, we do not use your information for personalised advertising, and we use only what is needed to run your account. To stop the answer being changed straight away (for example by trying another birth date), we keep for 24 hours (7 days if the same account or email address says it is under 18 again after the lock ended, and 30 days the third time) a signed cookie in that browser and, if an email address is known (typed in, or from your Google or Apple sign-in), a salted one-way hash of that address (in lower case and without any "+tag"), with a counter and a time; if you were signed in, a one-way hash of your account number in the same way. The hash cannot be turned back into the address, and we do not keep the address itself. We use your IP address only to count how many under-18 answers come from one network, as a one-way hash with a counter and a time, for 24 hours, to slow down abuse; it never decides anything about your age and never locks anyone out on its own. Only if one network produces an unusually large number of such answers in a day (more than 200) is sign-up from it paused for a while, with a "try again later" message. For the repeat counter we keep the one-way hash and a count for 180 days. Nothing else is kept.
In interactive guided sessions and in the chat, an automated check looks for clear statements that you are under 18 (for example "I am 12"). If it finds one, the session ends gently, we show help lines for young people, and a person reviews the account; its adult-only features are paused meanwhile. The text of the statement is not stored with the flag.
Advertising cookies and pixels, and the sign-up and purchase events we send to advertising companies, are not loaded or sent for people who tell us they are under 18, and are sent only for accounts that have passed the adult check.
The challenge, challenge teams and public profiles are for adults (18 or over) only.
In an AI assistant, anonymous play is open to people aged 13 and over and keeping your progress to people aged 15 and over; see Playing and keeping your progress in an AI assistant.
8. Complaints and contact
Email info@2hives.com with any question or complaint; we aim to reply within 30 days. If you aren't satisfied, you can contact the Office of the Australian Information Commissioner (oaic.gov.au).
2BEE FARM PTY LTD (which operates 2hives) · ABN 57 697 830 461 · info@2hives.com
For users in India: see Privacy: for users in India. Where it differs from this policy (for example how long we keep partner-link records, and your rights and our grievance contact under the Digital Personal Data Protection Act 2023), that page applies to you.
For users in the EU, EEA and UK
This section adds to the rest of this policy for people in the European Union, the EEA and the United Kingdom (GDPR and UK GDPR). The controller is 2BEE FARM PTY LTD (ABN 57 697 830 461), Melbourne, Victoria, Australia, info@2hives.com. We have not appointed a data protection officer; write to info@2hives.com.
- Our representative in the European Union (GDPR Article 27): Sándor Bácskai, Jerney utca 47, fsz. 2., 1148 Budapest, Hungary, eu-rep@2hives.com. You and data protection authorities can write to the representative as well as to us, in Hungarian or English; we will answer in your language.
- Why we may use your data (legal basis):
| What | Basis |
|---|---|
| Your account, programs, sessions, orders and delivering what you ask for | Contract (Art 6(1)(b)) |
| Sending your text to our AI providers to write your session | Contract, and your permission for AI features (Art 6(1)(a)) |
| Voice recordings, voice models, reading sessions, voice review, interactive-session voice, the training options and your recording of your name | Your explicit consent (Art 6(1)(a)), which you can withdraw at any time |
| Cookie-banner choices: advertising and analytics cookies and pixels, first-party page and click records, page tests, crash reports, the first-touch record of how you found us | Your consent (Art 6(1)(a)); nothing is stored before you press Accept |
| Marketing emails, saved postcode for partner cards, public profile, credits listing | Your consent |
| Security, fraud and abuse prevention, rate limits, the under-18 lock-out, the server records, moderation of chat, posts and public events, the partner programme's honesty checks | Our legitimate interests in keeping 2hives safe, fair and working (Art 6(1)(f)); you can object |
| Order and tax records | Legal obligation (Art 6(1)(c)) |
| Saving what we must for a legal claim | Legitimate interests |
- If you do not give data: you can use 2hives without giving anything that is optional; we need an email address and an adult confirmation to make an account.
- Transfers: 2hives is run from Australia, which does not have an EU adequacy decision. Where you give us your data directly, it is stored in Australia, and the voice recordings you record in the browser are processed on our own servers there. Our providers outside the EU and UK are listed in section 3 with the safeguards that apply.
- Automated decisions: see section 5. None of them has a legal effect on you beyond stopping a sign-up or hiding content, and you can ask a person to review each one.
- Complaints: you can complain to your local data protection authority, for example in the UK the Information Commissioner's Office (ico.org.uk).
For users in the Republic of Korea
This section adds to the rest of this policy for people in South Korea, under the Personal Information Protection Act (PIPA). If it differs from another section, this section applies to you.
- Who is responsible: 2BEE FARM PTY LTD (ABN 57 697 830 461), which operates 2hives, Melbourne, Victoria, Australia. The person responsible for personal information (privacy officer) is Gergo Bacskai, director: info@2hives.com.
- Age: you must be 19 or older to create an account in Korea, and we ask your birth year when you sign in. We do not knowingly collect personal information from anyone under 19 there.
- What and why: the items in section 1 (for example your email address, your programs and your listening records), for the purposes in section 2 (providing the service, contacting you, keeping 2hives safe, improving it). We ask for your consent where the law requires it, and you can withdraw it at any time; the sign-up and cookie choices say what each one covers. Marketing emails and advertising measurement are separate choices.
- How long we keep it: as shown in the table in section 4. When the purpose is met, or you close your account, we delete the data, except what the law requires us to keep (for example order records).
- Your rights: you can ask to see, correct, delete or restrict the use of your personal information, and withdraw your consent, from your account page or by writing to info@2hives.com. We answer within 10 days. You can also act through a representative.
- Sending your information overseas, and who handles it: 2hives is run from Australia, so your information is transferred to and stored in Australia. Some providers named in section 3 process it in the United States and other countries (see the "Where" column there for each). What is transferred is the information needed for each provider's purpose (for example your email address to send you mail, or the text of your prompt to write your script). It is transferred over encrypted connections when you use the service, and kept for the time in section 4. You can refuse a transfer that depends on your consent, but then we may not be able to give you the service. The contact for questions about a transfer is info@2hives.com.
- Security: see section 6.
- Complaints: write to info@2hives.com first. You can also contact the Personal Information Protection Commission (PIPC, pipc.go.kr), the Personal Information Infringement Report Center run by KISA (privacy.kisa.or.kr, 118) or the Personal Information Dispute Mediation Committee (kopico.go.kr, 1833-6972).
For users in Brazil
This section adds to the rest of this policy for people in Brazil, under the Lei Geral de Proteção de Dados (LGPD, Law 13,709/2018). If it differs from another section, this section applies to you.
- Who is responsible: 2BEE FARM PTY LTD (ABN 57 697 830 461), which operates 2hives, Melbourne, Victoria, Australia.
- Our data-protection contact (encarregado): the privacy contact of 2BEE FARM PTY LTD, info@2hives.com. Write to it in Portuguese or English to use your rights under the LGPD (to confirm that we process your data, to see, correct, delete or move it, to withdraw your consent, and to ask who we share it with) or with any question about this policy.
- Age: you must be 18 or over to have an account in Brazil (section 7).
- Complaints: write to info@2hives.com first. You can also complain to the Brazilian data protection authority, the Autoridade Nacional de Proteção de Dados (ANPD, gov.br/anpd).
9. What changed
On 16 November 2026:
- We added to Playing and keeping your progress in an AI assistant that the links we give an assistant carry a source tag (
src,source,utm_source,utm_medium,utm_campaign) naming the assistant, so that we can count visits for each assistant; the tag holds no personal data, and a link to a live conversation also carries a short-lived one-time code.
On 12 November 2026:
- Section 7: an account is now for people aged 15 and over; a person aged 13 or 14 may keep one only if a parent or guardian agrees by email (the parent's address is used for that one message and deleted when they decide or after 7 days); without that agreement the account is deleted. Listening needs no account.
- New section For users in Brazil names our data-protection contact (encarregado), info@2hives.com.
- We made Playing and keeping your progress in an AI assistant more exact: our server logs, which include your IP address, are deleted after 30 days, our page log keeps only a one-way daily tag of the network part for 90 days, a personal session you ask for from a menu is kept for 7 days without any identifier, and a star rating is kept without any identifier. We said that not every assistant offers to keep your progress.
On 11 November 2026:
- 2hives is now for people aged 13 and over. Listening and keeping your progress are open to everyone 13 and over; personal sessions in your own words, live conversations, teams and anything paid or sponsored are for adults (18+) (section 7 and the Terms). We ask for your birth year when you first open a feature for adults, not at sign-in (India, Brazil, South Korea and the 2hives apps: at sign-up).
- We added Playing and keeping your progress in an AI assistant: anonymous play keeps nothing about you; if you tap "Yes, keep my progress", a pseudonymous progress record is kept for 6 months after you last use it, with 90-day play entries and 35-day backups, and a delete button. We said that the networks that carry a request briefly handle your IP address, and that we never play sponsor lines in anonymous play or in the ChatGPT app.
- We added the progress record to the table in section 4, and a sentence to Partner cards about assistants and the coarse area.
- Section 7 now sets the age at 13 (18 in India and Brazil, 19 in South Korea); under-13 stays closed, and the adult features stay for adults, with a one-time age confirmation the first time you open one.
On 5 November 2026:
- We added Your sleep partner: the company whose invite link or QR code you used can be shown to you as a labelled ad, what we store, how to Hide or Forget it, the totals the company sees, and how long we keep it. Cookies, Partner cards, Website and apps and section 4 were updated to match.
On 3 November 2026:
- We described what we keep when a business buys optional paid partner packages, who else receives it (Stripe, as our processor and for its own purposes as an independent controller; the official business registers; the sanctions lists), the weekly sanctions check and how long the records are kept (business accounts section, section 3 and section 4). On 31 October 2026:
- We added The Android app and the ad that brought you: the Google Play install referrer, Australia and New Zealand only, and how long the ad click identifier is kept (90 days).
- We added Crash reports for the apps.
- Section 5 now names where to delete your account (in the app and at 2hives.com/delete-account).
- Section 3 now says that the advertising and analytics companies apply to the website, not to the apps.
- Section 7 now describes what the under-18 lock-out keeps: a cookie and one-way hashes of the email address (or account), no longer a code made from your network address and browser type. The network address is used only to count attempts.
- We described the device signal more exactly (section on abuse prevention).
- We added what our server records (page opens, audio delivered, sign-in steps), your permission for AI features, the "Email me a link" box and the business interest form (section 1), and the page-test cookies and browser storage (Cookies).
- We named the backup and standby copies held with Amazon Web Services (Sydney) and Backblaze (United States), and corrected the backup time to at most 90 days (sections 3 and 4).
- We added the list of decisions made by a computer program (section 5), a section for users in the EU, EEA and UK with our EU representative and the legal bases, and the higher age in South Korea (section 7).
- We removed the statement that our AI provider does not use prompts for training under its commercial terms, and now say that its own terms apply.
- We said exactly how Anthropic handles what we send (its own consumer terms, not as our processor), and added a section on the optional AI features and how to switch them off (sections 3 and "AI features (optional)").
- The postal address of 2BEE FARM PTY LTD is now one value used on every legal page.
On 27 October 2026:
- We no longer describe trials or prices, because 2hives is free to use; the data we keep is the same.
- Reading sessions, voice review and session review no longer earn this thanks. People with progress on or before 27 October 2026 can keep earning it until 26 gen 2027. We now delete the one-way email code of the reading-thanks records on 26 gen 2028.
- Being listed on the Credits page is a separate opt-in.
- We added a short note on automated checks (section 5).
- 2hives is for people aged 18 and over only; the parent-permission wording is gone (section 7). We ask for your birth year at sign-up and keep only that you are an adult and an age band. We describe the under-18 lock-out, the automated under-18 check in sessions and chat, and that advertising pixels are not used for people under 18.