Hearest (相癒) Privacy Policy
Last updated 2026-11-18 · Covers the Hearest app for Android and iOS and the website towntown.us
Hearest is run by TownTown Inc. (小鎮 TownTown — "we", "us"). This policy explains what we collect, why, who processes it, how long we keep it, and what you can ask us to do. Contact (also our personal data protection contact, for questions and requests about your personal data): tobewithblue@towntown.us. This policy is also available in Traditional Chinese and in Malay: 繁體中文, Bahasa Melayu.
Hearest is a self-care journaling app. It is not a medical service and does not diagnose or treat any condition. If you are in crisis or thinking about harming yourself, contact your local emergency number or a crisis line right away (Taiwan: 1925 Lifeline of the Mind, 24 hours; Singapore: Samaritans of Singapore 1767, 24 hours; Malaysia: Befrienders Kuala Lumpur 03-7627 2929, 24 hours).
1. What we collect in the app
Your account. You sign in with Google or with Apple. Through Firebase Authentication we receive your email address (if you sign in with Apple and choose to hide your email, this is the forwarding address Apple gives us) and the account ID Firebase Authentication gives you in Hearest, which we also store with your Hearest profile on our servers. Each request the app sends to our servers' API carries a sign-in token from Firebase (pictures and other files the app downloads are fetched without it), which, if you sign in with Google, also contains your Google account's name and profile-photo link; our servers use it to confirm that the request comes from you, and their logs may record details of the request. If you sign in with Google, Firebase keeps your Google account's name and profile photo; if you sign in with Apple, we ask Apple only for your email address, not your name. We never receive your Google or Apple password. If your Google and Apple accounts use the same email address, then when you sign in with the second one, the app asks you to sign in once with the one you used first; after that, both open the same Hearest account. You choose a nickname and one of our preset avatars, and you can set your language, region, music and sound preferences.
What you write and choose. We store what you create so the app can show it back to you:
- seeds — what you write about a worry, its category (for example health or relationships), how you feel, the tree you pick, who can see it, reminder times, and the AI's reflections on it; older seeds also still hold the comments and replies left on them in earlier versions of the app;
- guided reflections — your conversation with the AI guide, and the rating and feedback you give at the end;
- the Treehole — the letters and replies you write, drafts, your Treehole nickname and mood animal, and the matching preferences you set, such as topics you care about;
- Hearest Friends — friend requests, friendships and the nicknames you give friends. An invite QR code or link contains your account ID. If someone opens it in a web browser, the page that passes it on to the app or the app store is hosted by Zeabur, which receives the link, including your account ID, with ordinary request details.
Much of this is about your feelings and well-being, and we treat it as sensitive information.
Collected automatically.
- A notification token, so we can send you notifications. To deliver a notification, Google (Firebase Cloud Messaging) and Apple also handle the details needed to open it — for example account IDs (a friend's, or a letter writer's), a friend's nickname and avatar, the IDs of seeds, letters and drafts, and a letter's score.
- App-integrity checks (Google Play Integrity on Android, Apple App Attest on iOS): only earlier app versions run them, when you delete or restore your account and on requests to the AI guide; the current version does not.
- An ID for this installation of the app, which Google receives when the app downloads its current settings (Firebase Remote Config).
- On iPhone, to tell whether you are offline or our servers are down, the app loads a small test page from Apple (captive.apple.com), so Apple receives your IP address and ordinary request details.
- Like any app that uses the internet, your IP address and basic request details reach the servers that answer each request — our servers at AWS and Google, and the other providers in section 5 — which may keep them in their logs.
- Crash reports (Firebase Crashlytics): device model, operating system, app version, technical details of the crash and an ID for this installation of the app, which groups reports from the same installation. We don't attach your account to them. On Android, when signing in with Google or Apple fails or is cancelled, the app also sends Crashlytics a short report of what went wrong — the kind of failure, whether the account picker appeared, and the Google Play services version — so we can fix sign-in problems.
- On Android only, Google Analytics for Firebase records standard app-usage events with a separate analytics ID for this installation of the app (the app-instance ID), and estimates your approximate location (for example your city) from your IP address. We use it only to see how the app is used — never for advertising — and we don't collect your device's advertising ID.
- On Android, the QR code scanner is Google's ML Kit. When you open it, ML Kit sends Google technical information — your device model and system version, the app version, identifiers for your device and this installation of the app, and how the scanner performed — which Google uses under its own privacy policy to maintain the scanner and detect abuse. The camera image itself stays on your phone.
- On Android, if you install the app from a friend's invite link, Google Play keeps the link's invite details — which include your friend's account ID — and the app reads them once after installing to connect the invite.
Bug reports. When something goes wrong and you agree to send a report, we receive the note you type, recent app logs with message contents removed, technical details of what went wrong (these can include the IDs of the records involved — for example a Treehole conversation's ID, which can contain the other person's account ID), your device model and software versions, and your account ID. The app also sends such a report automatically, without asking, when it finds duplicated Treehole letters, so that we can fix the cause.
Reporting what the AI wrote. If you long-press something the AI wrote and choose to report it, we receive that text — and, for a reply from the AI guide, the message you sent just before it — together with any note you add, your device model and software versions, your account ID, and the IDs that tell us which seed and conversation the text belongs to (on a friend's seed, that seed's ID). We read these reports to improve what the AI writes, and keep them like bug reports: until you ask us to delete them, also after you delete your account. We don't reply to reports, and the reported text stays in the app.
Reporting and blocking Treehole letters. If you report a Treehole letter, we receive the letters that person wrote to you in that conversation, their account ID, the ID of the conversation (or of the letter, if you haven't accepted it yet), any note you add, your device model and software versions, and your account ID. We review every report within 24 hours; when a letter breaks our rules, we remove it and disable the writer's account. We keep reports like bug reports: until you ask us to delete them, also after you delete your account. We don't reply to reports. If you block someone, your phone hides their letters right away and sends us your account ID and theirs. Once we have accepted the block, we stop matching the two of you, and neither of you can send the other a letter; letters still waiting between you will no longer reach the other person — they are passed on to someone else, sent back to the person who wrote them, removed, or kept back and never sent. We keep the block — both account IDs and when it was made — even if one of you later deletes their account, and it can't be undone yet. The other person isn't told. Until we accept it, your phone keeps the block and sends it again; if we never accept it, it works only on your phone.
Feedback and emails. The feedback form in Settings is a Google Form: Google Forms stores what you enter there, including your email address and nickname. If you email us, the message stays in our mailbox (Gmail, in our Google Workspace).
What we don't collect. The app never asks for your device's location; the only location information is the approximate one Google Analytics estimates on Android, described above. The app doesn't access your contacts, the photos on your phone or your microphone, and it never asks for your phone number, birthday or legal name. If you type details like these into something you write — a seed, a letter, a bug report, the feedback form or an email — they are stored and sent along with that text. The camera is used only to scan friend QR codes, and the image never leaves your phone. We show no ads and don't track you across other companies' apps or websites.
What you must provide. To sign up and sign in you must provide a Google or Apple account (from which we receive your email address) and a nickname; without them you can't use Hearest. AI replies need what you write; if you don't write it, you get no AI reply. Everything else, such as Treehole letters, friend invites, bug reports and feedback, is up to you; if you don't provide it, you just can't use that feature.
2. How we use it
- To run the app: keep your forest, deliver and match Treehole letters, connect friends, remind you, send notifications and keep your data in sync.
- For the AI features described in section 3.
- To keep Hearest safe and working: check app integrity, fix crashes, investigate bug reports and act on reported Treehole letters.
- To improve Hearest: see how the app is used (analytics on Android) and, from the rating you give at the end of a guided reflection, whether the AI guide helps.
We don't sell your information and we don't use it for advertising.
Legal bases (EEA and UK). We process your information to provide the service you signed up for (contract); to keep it secure and fix problems (including the automatic reports about duplicated Treehole letters) and to understand how the app is used through analytics on Android (legitimate interests); and — for the bug reports and reports of AI-written text you choose to send, for information about your health, and on the website for reader analytics and the newsletter — with your consent.
3. AI features
When you plant a seed or talk with the AI guide, what you write, with your language and region, is sent from our servers to OpenAI, which writes the reflection or reply. This can happen while you are still writing a seed and when a reminder is due. Before you sign in, the app shows you this policy and asks you to agree to it, and you can't sign in without agreeing. You can withdraw this agreement at any time by writing to tobewithblue@towntown.us. AI replies are at the core of Hearest, so once you withdraw we can no longer provide the service: we will first write back to explain this, then stop processing your information and delete your account for you, which from then on works as if you had deleted it in the app (section 6). You can also delete your account in the app yourself. We don't attach your email address or other account details to it; anything you write yourself, including any names or contact details in it, is sent as you wrote it. OpenAI may keep any of these requests for up to 30 days to detect abuse, under its own policy.
Conversations with the AI guide. To stay consistent from one conversation to the next, the guide builds a memory in our database at Amazon Web Services (Japan; earlier app versions built it in our database at Google — Firestore, in the United States, or in Taiwan for some versions released in October 2026, including Android 1.0.1 — and that memory is still kept there, but the current app starts a new one): a summary of each conversation and a profile of what comes up for you — recurring themes, what matters to you, health-related things you mention such as a diagnosis or treatment, and the approaches that help or that you would rather avoid. It also automatically assesses each message you send for signs of risk, such as hopelessness or thoughts of self-harm: it records the kinds of risk it sees, an overall risk level, how confident it is, and a one- or two-sentence explanation. These assessments are kept for safety review and to check the guide's quality. They do not change the reply to the message assessed, but they can make the guide's later replies more careful, for example by offering crisis resources. To choose how to respond, the guide also judges your state in each message — for example how intense your feelings seem, how ready you are for a suggestion, how much you can take in, and patterns such as rumination, hopelessness or self-criticism — and keeps that judgment, the approach it chose and a short explanation with the conversation. With earlier app versions, OpenAI also keeps a copy of every request we send it for the guide and of its reply — including your conversation and the memory built from it — in our OpenAI account, where the people who run Hearest can look at them to find and fix problems with the guide. When a conversation ends, we also save it with your seed on our servers at Amazon Web Services (Japan): the whole conversation, its closing summary, and the feedback and score you give it.
Seeds. OpenAI also keeps the requests about your seeds, and its replies, in our OpenAI account, for the period OpenAI sets.
AI replies can be wrong and are not professional advice.
4. What other people can see
- A Treehole letter is delivered to another Hearest user with your Treehole nickname, your mood animal and the kind of support you chose for it (for example, just to be listened to, or to find a way through together) . The app doesn't show them your email address or account details, but their app does receive your account ID with the letter and keeps it hidden. They can reply, and they can forward it to other users. If the person who receives a new letter doesn't accept it within 24 hours, we remind them once before the time is up and then pass the letter to another user automatically; when everyone who could receive it has had it and nobody accepted it, the letter comes back to you and we keep it for you (section 6).
- Seeds you set to "Hearest Friends" or "Public" can be seen by your friends or by visitors to your forest. Seeds set to "Just me" are not shown to anyone else in the app. However, when a friend opens your forest, their app currently downloads all your seeds, including those set to "Just me", and hides those on their phone.
- Comments and replies that you or your friends left on seeds in earlier versions of the app are still kept with those seeds, with each writer's account ID, nickname and avatar, and are sent to the app of anyone who opens that forest — the seed's owner and their friends.
- Friends and people you invite see your nickname and avatar.
5. Who processes your information, and where
These companies process your information to provide their service to us:
- Amazon Web Services — our servers and databases, and the account-deletion email — Japan;
- Google (Firebase, Google Cloud and ML Kit) — sign-in, notifications, crash reports, app-integrity checks, configuration, analytics and the QR code scanner on Android, and part of our servers. Our Cloud Functions run in Taiwan and the United States, and our Firestore database in the United States (some app versions released in October 2026, including Android 1.0.1, used Cloud Functions and a Firestore database in Taiwan, and the data they stored is still kept there); the other Firebase services run on Google's infrastructure worldwide;
- Google Workspace (Gmail) — our email, tobewithblue@towntown.us;
- Google Forms — the feedback form. This is a Google consumer service, which Google provides under its own terms and privacy policy;
- OpenAI — AI replies and reflections, and the copies of AI requests described in section 3 — United States;
- Zeabur — the web page behind invite links;
- Cloudflare — the website and, if you agree, its reader analytics;
- Mailchimp (Intuit) — the website newsletter — United States;
- Apple — Sign in with Apple, if you use it;
- Apple and Google Play — notification delivery and app-integrity checks on their platforms, and on iPhone the connection check described in section 1; on Android, Google Play also passes the details of an invite link (including the inviting friend's account ID) to the app.
Your information may therefore be stored and processed outside your country, for example by Amazon Web Services in Japan, by OpenAI in the United States and in Google's facilities in many places. We send it there on these grounds: Amazon Web Services, Google (Firebase and Google Cloud) and OpenAI have committed, in their data processing terms with us, to protect it and to process it only on our instructions; and sending it to each company listed above is necessary to provide the service you asked for, for example sending what you write to OpenAI to write a reply. Apart from what you choose to share with other Hearest users (section 4), we share information beyond these providers only when the law requires it, or to protect someone's life or safety.
6. How long we keep it
- Your account and content: for as long as your account exists.
- Removing a friend: the letters and other exchanges between the two of you disappear from both apps, but we keep them without a time limit, and they come back if you become friends again.
- Deleting your account: in the app, you confirm on a screen that shows the recovery period (currently 30 days). Signing in during that period restores your account. When it ends, we permanently delete from our servers' databases your profile, your seeds, and your Treehole letters that nobody accepted and that came back to you; backups we have made may still hold copies. The following are currently not deleted with your account. Letters you exchanged with other people stay in their mailboxes. Your own Treehole letters, replies and drafts, your friend requests and records left by features of earlier app versions are not deleted either; if you sign up again with the same Google or Apple account, they come back. If you used version 1.0.0 or 1.0.1 of the Android app, what you stored with it on our servers stays where that version stored it: the current app does not show it, and deleting your account in the current app does not delete it; email us and we will delete it. Messages still waiting in our delivery queues when your account is deleted, such as notifications and letters sent from older versions of the app, are not removed with it and are kept for a few days. Your language and region setting, your bug reports, your sign-in record (Firebase Authentication keeps your account ID, the ID of the Google or Apple account you signed in with, your email address and, if you signed in with Google, your name and profile-photo link) and, if you have used the guided reflection, the records the AI guide keeps in our databases (at Amazon Web Services, and at Google for earlier app versions) and the saved copies of your finished conversations on our Amazon Web Services servers (section 3) are not deleted with your account; email us and we will delete them. If you signed in with Apple, the app asks you to confirm with Apple once more when you delete your account, and asks Apple to stop Hearest's use of your Apple ID; if that step fails, your account is still deleted, and you can remove Hearest yourself in your Apple ID settings.
- Treehole letters that nobody accepted and that came back to you, with the account IDs of everyone who received them: until you take the letter back, the daily retry you can ask for delivers it to someone else, or you delete your account — there is no time limit.
- Bug reports: until you ask us to delete them. They have no automatic expiry date and are not removed when you delete your account.
- Crash reports: 90 days (Firebase Crashlytics).
- The installation ID Google receives when the app downloads its settings (Firebase Remote Config): for the period Google sets.
- Notification delivery (Google's Firebase Cloud Messaging and Apple's push service): the ID Google uses to reach this installation is kept until we ask Google to delete it, and a notification that cannot be delivered right away waits for a limited time; Google and Apple set those periods.
- A friend's invite read through Google Play when installing on Android (including that friend's account ID): Google Play offers it to the app for 90 days after installing, and reinstalling resets it; how long Google keeps it beyond that is Google's to set.
- Usage analytics on Android (Google Analytics for Firebase): kept for the period set in our Google Analytics settings.
- Copies OpenAI keeps for abuse monitoring: up to 30 days.
- Copies of AI requests and replies, for the AI guide in earlier app versions and for your seeds, that OpenAI keeps in our account (section 3): for the period OpenAI sets.
- The AI guide's records and memory in the current app: deleted automatically 180 days after they were last written; while you keep talking with the guide, the parts it still uses are kept longer. They are not deleted when you delete your account; email us and we will delete them.
- Feedback-form answers and emails you send us: until you ask us to delete them.
- Information stored on your phone stays until you uninstall the app, or until an app update moves the app to a different service environment: the first time the updated app opens, it signs you out and deletes your account information from your phone. On iPhone, your sign-in stays in the system keychain after you uninstall the app until you reinstall it and open it, which signs you out; logging out before you uninstall removes it. If you back up your iPhone to iCloud or a computer, the backup includes the app's data on your phone.
7. Your choices and rights
- In the app you can edit your nickname and avatar, choose who sees each seed, archive seeds, remove friends and delete your account.
- Write to tobewithblue@towntown.us to get a copy of your information (including how we used it and to whom we gave it in the past year), correct it, delete specific items, object to or restrict a use, or withdraw a consent (for what happens when you withdraw the agreement in section 3, see section 3). We reply within 21 days; if we cannot finish within 21 days, we tell you within that time why, and when we expect to finish. We cannot yet find and delete the copies of AI requests OpenAI keeps in our account one by one.
- You can turn notifications off in your phone's settings.
- If you have concerns about how we handle your personal data, you can also complain to a supervisory authority: in Singapore, the Personal Data Protection Commission (PDPC); in Malaysia, the Personal Data Protection Commissioner (Pesuruhjaya Perlindungan Data Peribadi); in the EEA or the UK, your data protection authority.
8. Children
Hearest is for people aged 13 and over; if you live in Malaysia, you must be 18 or over. We don't knowingly collect information from children under 13, or, in Malaysia, from anyone under 18. If you believe such a person is using Hearest, email us and we will delete the account.
9. Security
Everything the app sends to our servers is encrypted in transit (HTTPS). Bug reports waiting to be sent are encrypted on your phone. No system is perfectly secure; if a breach affects you, we will tell you as the law requires.
10. The website
Like any website, towntown.us receives your IP address and ordinary request details with every visit: they reach Cloudflare, which hosts the site, and on pages that list crisis lines we use the country Cloudflare works out from your IP address to show the lines for your region, without storing it; Cloudflare may keep request details in its own logs. The site also counts how many times each article is opened — a count that records nothing about you — and, only if you agree in its banner, keeps a visitor ID and your reading activity (which articles, how far, how long, the referring site, country and city, device type, browser, operating system and window size) for 12 months, stored with Cloudflare. The site sets up to three cookies of its own: ha_consent remembers your choice for 6 months; only after you agree, ha_vid holds the visitor ID for 13 months and ha_sid marks the current visit until you close the browser. You can withdraw at any time on towntown.us/privacy/, which also deletes the records kept for that browser; the site has no accounts, so it cannot find records from another browser or device — withdraw there too. If you subscribe to the newsletter, your email address is stored with Mailchimp (United States) until you unsubscribe.
11. Changes
We will publish updates on this page with a new date. If a change materially affects how we use information you have already given us, we will tell you in the app or by email before it takes effect.
12. Contact
TownTown Inc. (小鎮 TownTown) · tobewithblue@towntown.us (personal data protection contact)