Privacy Policy
Updated September 10, 2026
Balmly helps you write a message of encouragement for someone else. This policy explains what information Balmly handles, where it goes, and who processes it. Balmly has no account or login system: it does not ask for your name, email address, or any other personal identifier, and it does not build a profile of you.
Balmly is not a medical, counseling, or crisis service. It is an automated tool for creative writing and faith-based encouragement. It does not monitor your activity, cannot guarantee detection of any risk, and does not contact emergency services. If you or someone else is in immediate danger, call 911, or call or text 988 (the Suicide & Crisis Lifeline) in the US.
What you type into the app
To create a message, you describe another person's situation and may enter that person's name and their relationship to you. When you ask Balmly to check or generate a message, this text is sent over an encrypted connection to Balmly's backend for that request only. It is never written to any database — not on Balmly's servers, and not by Balmly anywhere else. Once the request is complete, Balmly does not retain the description or the names.
Balmly's server logs record only technical metadata about each request: the message category, the internal safety-check flags, response time, and status codes. The free-text description and any names you entered are not included in these logs.
Processing by Anthropic (Claude)
The situation description is sent to Anthropic's Claude API as part of checking and generating your message. Anthropic acts as a data processor for this step, and its own API data-handling policies apply, separately from this policy. See Anthropic's Privacy Policy.
The anonymous app identifier and your credit balance
The first time you use Balmly, the app generates a random identifier (a UUID) on your device and stores it in the operating system's secure storage. This identifier is anonymous: no name, email, or other personal detail is attached to it.
Your remaining credit balance is stored on Balmly's backend (a Cloudflare D1 database), keyed to that anonymous identifier. Storing the balance server-side is necessary so that credits you have purchased survive across app sessions and cannot be altered from the device. No other information is stored against the identifier.
Purchases
In-app purchases and receipt validation are handled by RevenueCat and by the App Store. Your payment card details never pass through Balmly or its servers. After a successful purchase, RevenueCat sends a notification to Balmly's backend so that your credit balance can be updated. RevenueCat is a separate data processor with its own privacy practices — see RevenueCat's Privacy Policy.
What Balmly does not do
- No analytics or usage-tracking SDKs.
- No advertising and no third-party ad or tracking networks.
- No selling or sharing of personal information.
- No real-time monitoring of your activity or the content you write.
- No persistent identifier for you beyond the anonymous app identifier described above.
Data processors
- Anthropic — runs the Claude API that checks and generates message text.
- RevenueCat — processes in-app purchases and validates receipts.
- Apple — processes payments through the App Store.
- Cloudflare — hosts Balmly's backend and the database holding anonymous credit balances.
Children
Balmly is not directed to children and does not knowingly collect personal information from children.
Availability
Balmly is intended for use only within the United States.
Changes to this policy
If this policy is updated, the date at the top of the page will change accordingly.
Contact
Questions about privacy, or requests relating to your data: pekka.huuskonen@gmail.com. Because Balmly does not store your name or email, a deletion request can only be matched to your data if you are able to provide your anonymous app identifier.