Privacy and Metrics
What AIForj collects and what it never collects
AIForj is built around a local-first idea: your sessions, mood shifts, and guided-tool history should help you without becoming a pile of sensitive content sent to a remote analytics vendor by default.
This page explains the plain-English version of that promise. If you want the broader product-safety framing, read How AIForj stays safe.
Privacy guide integrity
Clinical review
Last reviewed
April 16, 2026
Built for emotional first aid, not diagnosis or crisis care. Read the editorial policy to see how AIForj writes, reviews, and updates content.
Anonymous metrics preference
Default is off for sensitive tool usage. When enabled, AIForj sends only whitelisted anonymous counters and buckets to AIForj’s first-party metrics endpoint.
Public marketing page views may be counted without cookies or identity. Sensitive tool events require this opt-in.
What stays on your device by default
- your mood ratings and mood-shift history
- session history used for “For You, right now” recommendations
- written responses you enter inside techniques and interventions
- Talk to Forj typed messages and local companion memory, unless a feature clearly says otherwise
- garden progress data and local streaks
- your anonymous-metrics preference itself
Voice input depends on your browser and device. Some browsers process speech through their own speech services. AIForj does not store voice audio or transcripts on its server.
What can be shared only if you opt in
Public marketing pages can send aggregate page-view counters without cookies, user identity, raw URLs, or free-text. Sensitive tool usage requires the anonymous metrics opt-in. If you turn it on, AIForj can send a small set of whitelisted counters to a first-party AIForj endpoint:
- whether a tool was started
- whether a tool was completed
- a duration bucket such as “2 to 5 minutes”
- a mood-shift bucket such as “up 1” or “up 2 plus” when a measured intervention has both ratings
- safe share-card counts and share-link opens
- checkout starts and successes by plan type only
- a short rotating anonymous client id that refreshes regularly
The goal is to understand which tools get used and which kinds of shifts are happening, without sending session content or building identity profiles.
What AIForj never sends as anonymous metrics
- free-text responses from techniques or interventions
- audio, voice transcripts, or message bodies
- names, phone numbers, email addresses, or gift-note text
- provider-search details or anything meant for crisis support
- full raw mood histories as a default background feed
- IP addresses or raw browser user-agent strings
Payments, gifts, and share links
Payments are handled by Stripe. AIForj stores only what is needed for checkout, entitlement, invite, and redeem flows: plan type, Stripe session/customer/subscription identifiers when needed, gift or family invite codes, activation status, and expiration status. Emotional content is not attached to Stripe metadata.
Calm Card share links use a minimal token with card type, tool slug or blueprint archetype, optional sender first name, and optional short non-sensitive message. They do not include journal text, chat text, raw mood scores, crisis status, provider searches, or full histories.
Why this is structured so narrowly
Mental-health-adjacent products lose trust quickly when they treat vulnerable moments like ad-tech fuel. AIForj is trying to do the opposite: keep emotional first aid useful, fast, and measurable without turning the underlying session content into a broad analytics stream.
If the product can learn enough from counts and buckets, it should not demand more than that.