Privacy Policy

What Cymora stores locally

Cymora stores session history, preferences, install-prompt dismissal, and similar product state in the browser or packaged app storage on the device. This lets the app remember sound-world settings, reduced-motion choices, recent reflections, and related shell state.

What Cymora does not require

Cymora does not require a user account, profile, or sign-in to use the core resonance loop. The current app does not include social sharing, public profiles, or cloud-synced session history.

Hosted web usage

If Cymora is used through a hosted website, the hosting provider and standard web infrastructure can process technical request data such as IP address, browser metadata, and requested URLs in ordinary server logs. Those logs are used for hosting, security, and reliability rather than a user account system.

Android and advertising readiness

Cymora's Android wrapper now includes Google Mobile Ads SDK support so a future release can enable restrained AdMob placements on non-session surfaces. If a release build includes that SDK, Google may process device identifiers and ad-related telemetry under Google's own policies. Any live Android release should keep active sessions, splash flow, and stage transitions free of ad interruptions.

Your controls

• Clear Recent sessions from within the app to remove local reflection history.
• Remove the app or clear site storage in the browser or Android settings to remove local preferences.
• Review the current Play listing and in-app disclosures before installing an ad-enabled Android release.

Changes

Cymora is still evolving. If the app later adds analytics, cloud sync, purchases, or live AdMob placements, this Privacy Policy and the Play Data Safety worksheet will be updated before that release ships.