Privacy Policy
This Privacy Policy describes Our policies and procedures on the collection, use and disclosure of Your information when You use I Ching Dialogue and tells You about Your privacy rights and how the law may protect You.
We process Personal Data needed to provide and secure the Service as described below. Optional product analytics is disabled unless You expressly allow it in the Application.
Interpretation and Definitions
Interpretation
The words of which the initial letter is capitalized have meanings defined under the following conditions. The following definitions shall have the same meaning regardless of whether they appear in singular or in plural.
Definitions
For the purposes of this Privacy Policy:
- Application refers to I Ching Dialogue, the mobile software program provided by the Company.
- Company (referred to as either "the Company", "We", "Us" or "Our") refers to Asana AI, LLC.
- Device means any device that can access the Service such as a computer, a cellphone, or a digital tablet.
- Personal Data means any information that relates to an identified or identifiable individual.
- Service refers to the Application and related backend services used to generate readings, diagnostics, and live interpretations.
- Service Provider means any natural or legal person who processes data on behalf of the Company. It refers to third parties that help host, secure, operate, or support the Service.
- Usage Data refers to data collected automatically, either generated by the use of the Service or from the Service infrastructure itself.
- Website refers to the public project page at https://podlesnyy.github.io/iching-oracle-public/.
- You means the individual accessing or using the Service, or the company, or other legal entity on behalf of which such individual is accessing or using the Service, as applicable.
Collecting and Using Your Personal Data
Types of Data Collected
Personal Data
While using Our Service, We may collect certain information that can be used to operate, secure, and improve the Service. This information may include:
- the question text You submit for a reading;
- the selected locale and reading method;
- line values, if they are used by the selected reading method;
- a locally generated device identifier used to maintain an anonymous device session;
- a Google Sign-In account identifier for paid In-depth purchases, restore, and access checks. We do not store Your Google email address, name, profile photo, or the raw Google account subject in ordinary backend records;
- a Sign in with Apple account identifier for paid In-depth purchases, restore, and access checks. The Application does not request Your Apple email address or name, and We do not store the raw Apple account subject in ordinary backend records;
- contact details and any information You voluntarily provide if You contact Us.
Information Collected while Using the Application
To provide features of the Application, the app may store or process the following information on Your Device:
- saved readings and local journal history;
- application settings such as language, runtime mode, base URL, ambient audio preference, product analytics consent state, OpenAI processing consent state, and onboarding state;
- technical metadata required to render readings and support diagnostics;
- a paid-access account session token if You sign in with Google or Apple for In-depth access.
The current release scope does not request access to Your contacts, camera, microphone, or precise location.
OpenAI Processing Choice
On iOS, before the first new In-depth interpretation, In-depth version of a Standard reading, or Follow-up request is sent, the Application asks You to allow processing by OpenAI. I Ching Dialogue sends the data through Our backend to OpenAI only for the purpose of generating the In-depth interpretation or Follow-up answer You requested.
The disclosed data categories are Your question; response language; selected line-building method; the six line values submitted by the Application and the six resolved line values; and hexagram and changing-line texts. Follow-up also includes prior questions and interpretations, primary and relating hexagram numbers, changing-line indexes, and pseudonymous technical reading identifiers that link the request to earlier readings. Standard readings remain on Your Device and remain available if You choose Not now. Before You allow processing, the iOS client does not send the protected request, create the backend interpretation job, or use an In-depth reading.
Before a new purchase, the Application shows this choice after You select the purchase but before Sign in with Apple and App Store confirmation. Restoring an earlier purchase does not require this choice; if needed, the Application asks before the next new In-depth or Follow-up request. You can review or withdraw this choice in the About section of iOS Settings, which does not provide a preselected control or grant permission outside a new action. Withdrawal blocks future new protected requests, but cannot recall a request already sent or delete data already processed by Our backend or OpenAI. Settings cannot enable processing. Android currently does not provide this separate provider-specific control: after Your intentional In-depth or Follow-up action and any required access step, Android sends the necessary data through Our backend to OpenAI as described in this Policy.
Usage Data
The Application and backend process limited technical Usage Data needed to provide, secure, and troubleshoot the Service. Optional Firebase Analytics data is handled under the separate choice described below.
Usage Data may include technical information such as Your Device's IP address when communicating with the backend, app version, request timestamps, latency metrics, mobile platform details, an anonymous installation or session identifier, safe error codes, and similar operational data.
The current Android and iOS Application targets do not include Firebase Crashlytics and do not send crash, ANR, or handled-exception reports to Firebase Crashlytics. The mobile operating system and app store may separately provide crash or stability information under their own settings and privacy terms.
Android and iOS public-store builds may use Firebase Analytics only after You expressly enable optional app-usage sharing. Collection is off before that choice and remains off if You continue without sharing. Your choice does not affect readings, paid access, purchases, or restore. You can change the choice at any time in the About section of Settings. Disabling sharing stops new manual product events and asks the Analytics SDK to deny Analytics storage and advertising-related consent categories, stop collection, and reset its local analytics data. On the first later opt-in, the Application keeps collection disabled while it denies all Analytics consent categories and clears local Analytics data that may remain from an earlier Application version. It then grants only Analytics storage and enables collection. Advertising storage, advertising user data, and ad personalization remain denied.
Manual Firebase Analytics events are limited to allowlisted product events and allowlisted parameters such as source, reading type, method, submit mode, entitlement state, product type, safe error code, HTTP status, and locale. We do not add question text, answer text, follow-up text, lineage, raw reading identifiers, Support ID or short support code, purchase token or hash, order ID, purchase region, test purchase flag, purchase completion time, backend response body, AI provider payload, file path, free-form exception message, email, account identifier, or a developer-supplied user identifier to these events. Firebase Analytics automatically assigns an app-instance identifier and may collect general device information, language, and approximate location derived during network collection. This app-instance identifier is specific to the app installation and is not Your account ID or an advertising identifier. We do not call Firebase Analytics setUserId and do not set Analytics user properties with Support ID, account, or purchase/order data.
After permission, Firebase Analytics may also record SDK-generated app lifecycle events, including first open, app update, OS update, session start, and user engagement. Automatic screen reporting is disabled. The iOS target does not call the StoreKit 2 transaction logging API, and its minimal Analytics dependency omits the identity-support and on-device ads-conversion components.
Optional Analytics is used only to understand app use and improve flows, usability, and product quality. We do not use this data for advertising or personalization and do not sell it. Questions, interpretations, Journal or Follow-up text, line values, account, support or purchase identifiers, crash reports, and diagnostic payloads are not included in optional product Analytics.
When the Application is in live mode, the backend may create a safe audit record for operational and diagnostic purposes. That record is designed not to store the raw user question in the PostgreSQL audit table.
Use of Your Personal Data
The Company may use Personal Data for the following purposes:
- To provide and maintain the Service: to generate readings, return interpretation results, and keep the Application functioning.
- To manage anonymous device sessions: to associate requests with a locally generated device identifier without requiring an in-app account.
- To manage paid access: to verify Google Sign-In or Sign in with Apple for paid In-depth access, link Google Play or App Store purchases to an account-level entitlement, restore eligible purchases after reinstall or clear data, sign You out, and process account deletion requests.
- To provide live interpretation: when live mode is enabled, to send the required reading context through Our backend to the configured AI provider.
- To support diagnostics and security: to monitor service health, investigate failures, prevent abuse, and maintain infrastructure reliability.
- To validate in-app purchases and subscriptions: to confirm Google Play or App Store purchase state, update access to paid in-depth readings, and restore purchases when You request it.
- To manage Your requests: to respond if You contact Us.
- To comply with legal obligations: where retention or disclosure is required by applicable law.
Service Providers and Third Parties
We may share relevant Personal Data with Service Providers to operate the Service. Depending on runtime mode and deployment configuration, these providers may include:
- hosting and infrastructure providers, including DigitalOcean;
- AI processing providers used by Our backend to generate live interpretations, including OpenAI when enabled;
- Google Play services used to process in-app purchases and subscriptions and to verify purchase state through the Google Play Developer API;
- Google Sign-In services used only to verify the Google account selected for paid In-depth purchase, restore, and access checks;
- Apple services used for Sign in with Apple, App Store purchases and subscriptions, and App Store transaction validation;
- Firebase Analytics, used on eligible Android and iOS public-store builds for allowlisted product events only after You expressly enable optional app-usage sharing;
- development and operational tooling strictly needed to secure, monitor, or maintain the Service.
In-app purchases and subscriptions are processed by Google Play on Android and by the App Store on iOS. The Application and Our backend may receive purchase identifiers such as product ID, purchase type, order ID, purchase token, transaction ID, and original transaction ID for validation and restore. We do not store the full Google Play purchase token or signed App Store transaction in ordinary backend records; We store minimized identifiers and validation data for entitlement, audit, and fraud-prevention purposes.
Google Sign-In for paid access sends a Google ID token from the Application to Our backend. The backend verifies the token with Google, stores a keyed hash of the stable Google subject, creates an internal account identifier, and stores only a hash of the account session token. We do not use Your Google email address as a billing key.
Sign in with Apple for paid access sends an Apple identity token from the Application to Our backend. The backend verifies the token with Apple, stores a keyed hash of the stable Apple subject, creates an internal account identifier, and stores only a hash of the account session token. The Application does not request Your Apple email address or name.
We do not use advertising SDKs, contact-book integrations, or developer-supplied Firebase Analytics User-ID values in the current release scope.
Retention of Your Personal Data
The Company will retain Your Personal Data only for as long as it is needed for the purposes described in this Privacy Policy, unless a longer retention period is required or permitted by law.
- local reading history and application settings remain on Your Device until You clear app data, remove entries, or uninstall the Application;
- operational, entitlement, and purchase-validation records may be retained on the backend for security, troubleshooting, purchase restore, fraud prevention, and service reliability;
- account identity records for paid access are retained while the account is active. Account deletion removes the Google or Apple identity link, revokes active account sessions, scrubs linked account, installation, reading, and request identifiers, and prevents future use of the old account identifier. For an Apple account, the backend also attempts to revoke the Apple credential. That revocation may finish asynchronously or fail after bounded retries while local account deletion still completes;
- backend LLM exchange logs that may include reading questions, generated answers, and AI provider request/response payloads are retained for a limited operational window. After account deletion, these payloads may remain without the scrubbed account and installation links for up to the default 30-day production retention window, after which a scheduled backend job deletes older records;
- purchase, billing ledger, grant, usage, refund, and chargeback history may be retained under a replacement pseudonymous billing reference for purchase restore, accounting, fraud prevention, and legal obligations;
- Firebase Analytics app-instance data and allowlisted product events are retained by Firebase according to the provider's service settings only after optional app-usage sharing has been enabled. Disabling sharing stops new collection but does not by itself delete data already processed by the provider;
- where feasible, server-side audit data is minimized and excludes the raw question text.
Transfer of Your Personal Data
Your information may be processed in countries other than Your own, including where Our infrastructure or Service Providers operate. By using the Service, You understand that data may be transferred and processed outside Your jurisdiction.
Delete Your Personal Data
You may delete local Journal entries from the Application. Clearing app data where the platform provides that action, or uninstalling the Application, also deletes locally stored data. You may contact Us to request access to, correction of, or deletion of Personal Data that You have provided to Us, subject to legal and operational constraints.
If You used Google Sign-In or Sign in with Apple for paid In-depth access, the Application may also provide an account deletion action. It removes the account identity link and sessions and scrubs related identifiers. Questions, generated answers, and AI provider payloads may remain without those links for up to 30 days. Pseudonymized purchase and billing history may be retained where necessary to verify purchases, handle refunds or chargebacks, prevent abuse, or comply with law. Deleting an account does not delete the local Journal and does not cancel an App Store or Google Play subscription; You must cancel an active subscription in the applicable store.
Until the Service confirms account sign-out, the Application may keep the prior account session in protected on-device storage solely to retry revoking that same server session at app launch or when You retry. It is not exposed as an active account session, and new account sign-in, purchases, restores, and paid readings remain blocked until sign-out is confirmed.
Until the Service confirms an account deletion result, the Application may keep the original deletion request in protected on-device storage and resend that same request at app launch or when You retry. The Application does not expose this data as an active account session and clears it after a confirmed result or when the protected request can no longer be used. A later Sign in with Apple action is ordinary authentication: it may open the selected existing account or create a new account if none exists. It does not check or confirm deletion of the previous account or any other Apple ID.
Cached paid-access status and queued paid-reading jobs use a keyed opaque account-owner value in application preferences instead of the raw internal account identifier. The separate key and any recovery identity needed to finish local cleanup are kept in device-only protected storage. A recovery identity is removed after cleanup before the Application permits replacement account sign-in.
Disclosure of Your Personal Data
Business Transactions
If the Company is involved in a merger, acquisition, asset sale, or similar transaction, Your Personal Data may be transferred as part of that transaction.
Law Enforcement
Under certain circumstances, the Company may be required to disclose Your Personal Data if required to do so by law or in response to valid requests by public authorities.
Other Legal Requirements
The Company may disclose Your Personal Data in the good faith belief that such action is necessary to comply with a legal obligation, protect and defend rights or property, investigate possible wrongdoing, protect the personal safety of users or the public, or protect against legal liability.
Security of Your Personal Data
We use reasonable technical and organizational measures intended to protect Your Personal Data. However, no method of transmission over the Internet or method of electronic storage is completely secure, and We cannot guarantee absolute security.
Your Privacy Rights
Depending on Your location, You may have rights to access, correct, delete, restrict, or object to certain uses of Your Personal Data, and to request a copy of the data We hold about You.
If You are a resident of California, We do not sell personal information as that term is commonly understood. If applicable law grants You specific privacy rights, You may exercise them by contacting Us.
Children's Privacy
Our Service is not directed to anyone under the age of 13. We do not knowingly collect personally identifiable information from anyone under the age of 13. If You are a parent or guardian and You are aware that Your child has provided Us with Personal Data, please contact Us.
Links to Other Websites
Our Service may contain links to other websites that are not operated by Us. If You click on a third-party link, You will be directed to that third party's site. We strongly advise You to review the Privacy Policy of every site You visit.
Changes to this Privacy Policy
We may update Our Privacy Policy from time to time. We will notify You of any changes by posting the new Privacy Policy on this page and updating the "Last updated" date at the top of this Privacy Policy.
You are advised to review this Privacy Policy periodically for any changes. Changes to this Privacy Policy are effective when they are posted on this page.
Contact Us
For privacy questions, access requests, or deletion requests, You can contact Us:
- by email: support@anyposeai.com
- through the public project page: https://podlesnyy.github.io/iching-oracle-public/