How we handle your day

Privacy Policy

v1.3.0Effective October 25, 2026

Chimesong is an independent project by Esharive Joshua Akpevweoghene, based in Delta State, Nigeria, and is publicly live at chimesong.app. This page describes the online-only service and its current handling of personal data. Provider arrangements, processing practices, and operational retention remain subject to ongoing review.

What Chimesong is

You describe your day. Claude by Anthropic provides a score and reflection, except when a safety response is needed. You can use Chimesong with an account or as a guest (see Using Chimesong as a guest). Entries are private by default. Sharing is an explicit choice, subject to moderation (see Sharing and moderation). Shared posts use a pseudonym and are visible to other signed-in users; the Feed requires an account. Chimesong is a reflection app, not a mental-health service.

What we collect

Account basics: email, profile settings, and a generated pseudonym. Supabase Auth processes passwords and manages sessions.
Entries: day text, scores, and AI reflections, stored with your account so you can revisit them. With an account, Chimesong also stores the short factors it notes from your entries (for your Trend and patterns) and the questions you ask Ask Chimesong together with their answers.
Interactions: shared posts, comments, reactions, ratings, reports, appeals, moderation results, and game progress.
Preferences: theme, sensory choices, timezone, AI persona, and consent choices.
Security records: hashed IP/browser information for consent evidence, browser/region-derived security fingerprints, login events, and audit events. These are security identifiers, not advertising profiles. Hashing does not necessarily make a record anonymous.
Optional analytics: only with valid analytics consent, PostHog EU Cloud receives coarse page visits and selected occurrence-only events about signup, reflection, History, and voluntary Public Echo sharing. PostHog-generated pseudonymous browser and session identifiers support cross-session analysis and visit counts. Chimesong does not intentionally send entry text, other user-generated content, email addresses, or Chimesong account IDs to PostHog. Browser performance measurements may still be sent to Chimesong's own telemetry endpoint, which acknowledges and discards them.

We do not sell your entries or use advertising trackers. Browser timezone, request-region information, and security processing should not be mistaken for a promise that no technical identifiers are processed.

Using Chimesong as a guest

You can write about your day and receive a Chime without an account (Local Mode).

Where your entries live: a guest's entries and Chimes are saved only in your browser's storage on that device. Chimesong does not store guest entry text in its database. Clearing this site's data in your browser deletes that history, and Chimesong cannot recover it.
What is sent to produce a Chime: the text you submit goes through the same AI and safety checks as an account entry, which means it is sent to Anthropic under the terms described in Providers and transfers. The result is returned to your browser, not kept by Chimesong.
Fair-use limits: to keep the free guest allowance fair, Chimesong sets an essential, HTTP-only cookie (cs-local-ai, lasting up to 7 days) holding a random device token. The server stores only keyed hashes derived from that token and from your network IP address, plus operation details such as the time and outcome. It never stores your writing for this purpose.
Offline writing stays in your browser. It is sent for a Chime only if it is later rated.
Creating an account later does not upload your guest history automatically.

The Feed, sharing to Public Echo, your Trend, patterns, and Ask Chimesong require an account.

Sharing and moderation

Sharing to Public Echo is always your choice. Before a post or comment is published, Chimesong checks it:

Safety checks: the public text of a post (and any caption) is checked by Anthropic for crisis signals, and posts and comments are checked by Anthropic against the Community Guidelines. If a check finds a problem, the post or comment is not published and you are told why; your private entry is not affected. If a check cannot run, nothing is published and you can try again.
Identifying details: before you share a post, Chimesong scans its text for details that could identify you or someone you mention, using pattern matching and AI, and warns you. This warning does not block sharing; if you choose to share anyway, the kinds of detail detected may be logged, without the text.
What is stored: a published post keeps a snapshot of the public text, its score and reflection, the card style you chose, and your pseudonym. Reports, moderation decisions, and appeals are stored with your account's interaction records.
Reports and appeals: signed-in users can report posts and comments. Reports are queued for review by the operator, and each moderation action is recorded in the security audit log. You can appeal a moderation decision from Settings.

Why we process it

Account and entry processing provides the service you request. Signup records acceptance of the Terms and Privacy Policy, and the application checks required consent before scoring. Security, moderation, and audit records support abuse prevention and accountability. Optional analytics has a separate, withdrawable choice.

The operator is responsible for confirming the applicable lawful bases and deployed processing arrangements. Accepting a notice is not a blanket waiver of privacy rights.

Providers and transfers

Supabase supplies database and authentication functionality. The operator is responsible for confirming the production hosting region, backup schedule, and deployed encryption configuration.
Anthropic receives entry text needed for AI processing. A stateless scoring request does not mean zero retention. Its published API policy describes deletion of inputs and outputs within 30 days by default, with exceptions for certain services, agreements, safety enforcement, and law. Chimesong does not claim a zero-data-retention agreement. See Anthropic's retention policy.
PostHog is an external processor for optional product and web analytics on its EU Cloud. It receives analytics events only after valid consent; the browser's network request necessarily exposes technical connection information, including the network IP address, to the provider. Chimesong disables GeoIP enrichment in event configuration. The PostHog project-level setting to discard raw client IP data must be enabled before production analytics is activated; disabling GeoIP enrichment alone does not discard that data.
Web hosting, payment activation, processor agreements, and international-transfer arrangements require deployment review. A planned provider is not represented here as an active or verified production arrangement.

Infrastructure providers may separately process request and security logs. Their deployed settings and terms require ongoing operational review.

Current retention and deletion behavior

Entries remain until you delete them or delete your account. The application does not currently enforce an automatic five-year entry expiry.
Deleting an entry removes its associated public post and dependent interactions through the existing deletion rules.
No automatic 90-day moderation purge or two-year report purge is implemented. Those earlier schedules were inaccurate and are not promises of the current release.
Consent records linked to a profile are deleted with that profile; they are not retained for an additional year by the current schema.
Account deletion removes the account, profile, owned entries, posts, and dependent user records through application deletion and database cascades.
Security audit records can remain after account deletion with the actor's profile link cleared. Event details, target identifiers, or hashes may remain. They are not all included in the self-service export and are not necessarily anonymous. No automatic audit-record expiry is currently implemented.
Provider logs and backups are separate from live application deletion. No fixed 35-day backup expiry has been verified for public deployment.

The operator is responsible for the operational retention, backup, and residual security-record handling. This page does not invent a schedule that the application cannot enforce.

Your choices and rights

Use Settings to download the available account-data JSON export or delete your account. Use History to delete entries. The export covers supported account, entry, and interaction records, not every operational or provider log.

For access, correction, erasure, portability, or an objection to processing, contact klarkkrampus@gmail.com. Applicable rights and response obligations depend on your jurisdiction. You may contact the Nigeria Data Protection Commission (NDPC) or your local supervisory authority.

Manage cookies is available in the landing footer, legal pages, and Settings. Optional analytics is off without valid consent. Withdrawal stops subsequent analytics sends and resets the PostHog browser identity and storage where supported; it cannot retract a request already sent. A browser Global Privacy Control signal overrides prior analytics consent. Essential authentication and security cookies do not depend on optional analytics.

Age and safety

Signup includes an age-eligibility acknowledgement. It is not independent age verification. If you believe an ineligible child has an account, contact klarkkrampus@gmail.com. Do not put identifying details about children or other people into shared entries.

AI output is not medical advice or a clinical assessment. Crisis guidance is available at /safety; this application is not an emergency service.

Cookies and browser storage

The Cookie Policy describes session and request-security cookies, saved sensory settings, local game state, and optional telemetry. Clearing cookies does not necessarily clear localStorage; your browser offers separate site-data controls.

Changes and contact

Material notice changes update the version above and the Changelog. The application uses versioned consent records for required policy acceptance. Questions reach klarkkrampus@gmail.com.