Choicewise Privacy Policy

Effective date: October 20, 2026 Last updated: October 20, 2026

1. Who We Are

Choicewise is owned and operated by Yangquan Xihetao Technology Co., Ltd. In this Privacy Policy, “Choicewise,” “we,” “us,” and “our” refer to that company.

2. Scope

This Policy explains how we process information when you use the Choicewise iOS app and related account, decision-support, subscription, support, safety, analytics, and privacy-request services.

Choicewise v1 is intended for the United States, Canada, Australia, New Zealand, and Singapore. Project-authored app chrome, product copy, legal materials, and support materials are English. User-entered and persisted content may use other languages. Ordinary AI final answers follow the language of the user's current question; a tied, ambiguous, or unsupported language signal falls back to English. The fixed crisis guidance described below remains project-authored English. Japan, South Korea, Hong Kong, Taiwan, Mainland China, and Europe/EEA are outside this v1 scope.

Choicewise does not operate an advertising program or a cross-app or cross-website tracking program. We do not describe disabled, removed, debug-only, or future services as current processing.

3. Information We Process

3.1 Account, profile, and authentication information

We process information needed to create, secure, and operate an account, including:

Sign in with Apple may send a name during initial authorization. The current account service does not save that name or use it as the profile nickname; it creates a generated display nickname instead. Apple email and account identifiers are retained for account operation.

Raw credentials and codes are handled only as needed for authentication and security. They should never be sent to Choicewise support.

For Sign in with Apple, the backend can exchange the authorization code and retain an Apple refresh token in encrypted form so it can revoke that authorization during account deletion. The token is not included in portable exports or sent to analytics or AI services. If a usable authorization is unavailable, you may need to sign in with Apple again before deletion can complete.

3.2 Device and visitor information

The app creates a pseudonymous visitor identifier on the device and may include it in unauthenticated requests to the Choicewise backend. The current application backend does not use or persist that visitor identifier as an account or analytics identity. Analytics requires a signed-in, consented session; the visitor identifier is not an anonymous analytics identity. The identifier can remain on the device after the app's local-data cleanup flow.

We also process device, app, network, and request information described in Sections 3.8 and 5.

3.3 Principles, plans, decisions, and other content

We process content you choose to create or submit, including:

This content may be sensitive depending on what you enter.

3.4 AI and safety information

Choicewise processes your questions, selected conversation history, active principles and plans, and AI responses to provide decision support. Workflow records may include tool results, checkpoints, and request metadata.

Choicewise does not provide mental-health assessment, diagnosis, treatment, or personalized psychological advice. For safety-related requests, it may show fixed guidance that suggests contacting someone you trust or a qualified professional, and local emergency services if there is immediate danger. Choicewise is not a crisis or emergency service.

We retain account-linked content-safety event types and risk levels to enforce safety boundaries. The dedicated safety log excludes raw triggering text; related messages, fixed replies, and workflow safety categories may be retained separately. These records describe content moderation, not an assessment of your health. Safety classifications and guidance interactions are excluded from analytics and advertising.

3.5 Subscription, purchase, entitlement, and usage information

For subscriptions and app access, we process product identifiers, an app account token, signed Apple transaction data while it is verified, hashed transaction or original-transaction identifiers, transaction environment and status, subscription period and status, entitlement records, quota counters, and usage records. Apple separately processes App Store purchase and subscription information under its own terms and privacy practices.

3.6 Reminders and notifications

When you configure a plan reminder, Choicewise may process plan and reminder identifiers, scheduled times, delivery status, error or provider metadata, and related timestamps. If remote notifications are used, the app and backend process an APNs device token, installation and account binding, token hash, protected sendable-token reference, authorization state, retry or unlink state, and delivery records. A scheduled reminder is not a guarantee that a notification will arrive, and Choicewise should not be used for time-critical or emergency reminders.

3.7 Privacy requests and exports

We process privacy-request type, status, timestamps, expiry metadata, continuation or recovery state, and a deterministic audit hash where needed to fulfill and audit a request.

Choicewise's portable export contains user-visible Principles and Plans. It does not include account or profile fields, conversations, decisions, feedback, consent, subscriptions, usage, commerce, push lifecycle, provider records, logs, caches, checkpoints, backups, identifiers, database relationships, or hidden internal controls. A temporary export file is cleaned after sharing or cancellation and through stale-artifact recovery. Backend export payloads are scheduled to expire after seven days and are removed by the cleanup task when it runs. Account deletion clears the export payload and its artifact hash; unlinked request records may remain. Files you save or share outside Choicewise are outside the app's cleanup controls.

3.8 Technical, diagnostic, and operational information

We process limited technical and operational information needed to run and protect the service, including:

Some of these systems may contain information from the categories above, including content fragments in workflow failure records. Choicewise does not intentionally put raw user or AI content into analytics events.

3.9 Analytics information

When analytics is enabled and the required consent is present, Choicewise collects limited product-analytics information in the following categories:

Amplitude processes the source IP and may derive coarse location from it. Choicewise does not request precise location for analytics.

Choicewise does not use analytics to collect advertising identifiers, GPS or precise location, credentials, raw principles, raw plans, raw questions, raw conversations, raw AI outputs, or free-form feedback text. It does not use arbitrary click, tap, gesture, text-entry, or generic interaction autocapture. Crisis classification or downgrade, crisis-resource interaction, and safety-section rendering are excluded from analytics. Analytics and source-IP-derived location are not used to select crisis or safety guidance.

3.10 Consent and cleanup state

The app stores the current privacy-consent version and time. An authenticated consented session records the current version with the backend before a pseudonymous analytics identity is issued. Withdrawing consent prevents new analytics publication and clears or retires Choicewise-owned analytics identity and session state. Choicewise also keeps limited recovery state when local cleanup must be retried.

4. How We Receive Information

We receive or create information:

5. Why We Process Information

We process information to:

We do not use these categories for advertising or cross-app or cross-website tracking.

6. AI Processing and Zero Data Retention

Choicewise routes AI information through the Choicewise backend and a private LiteLLM gateway to OpenRouter, Inc., which routes requests to qualified third-party model providers. No OpenRouter plugin, web-search branch, MCP integration, or external tool is enabled in this route.

The app presents its privacy explanation and policy links before you choose Agree and Continue. This consent covers the AI processing described here and product analytics; there is no separate AI-only or analytics-only switch. If you choose Do Not Agree or withdraw consent in Privacy Center, the app returns to the privacy gate and does not start new AI requests. Withdrawal does not retract requests already sent or erase existing provider records.

For the current release, Choicewise uses controlled manual Zero Data Retention (ZDR) configuration. An authorized operator selects the exact model/provider endpoint, confirms that it supports ZDR, enables the applicable OpenRouter ZDR setting, and keeps each active primary and fallback route within that approved scope. A provider or model change requires the same manual qualification and disclosure-impact review.

Applicable data-processing terms govern this AI processing. Choicewise uses approved zero-retention model endpoints that do not retain prompts or responses or use them for training. These protections apply to the approved endpoints, not every provider service. OpenRouter may retain request metadata.

Choicewise does not publish or promise a fixed model name, model version, selection default, or fallback order. Route qualification is managed manually, and Choicewise does not promise automated validation or fallback enforcement. ZDR also does not erase Choicewise-owned caches, checkpoints, logs, backups, security records, or privacy-request obligations.

7. When Information Is Processed by Others

We use the following service and platform categories for the purposes described in this Policy:

Self-hosted LiteLLM, PostgreSQL, Redis, Nginx, and Prometheus are Choicewise-operated software components, not separate external legal entities. No separate external support or crash-reporting provider is currently represented.

Exact email-provider and infrastructure contracting entities, regions, retention terms, and subprocessors can depend on current operational configuration. We do not state unconfirmed details as facts.

8. International Processing

Choicewise and its providers may process information outside your country. Our current production backend and private AI gateway run in Singapore, with their local database and Redis storage on those servers. Amplitude uses the selected United States ingestion route. Our Azure email resources are configured with a United States data location. Microsoft explains that service data may transit or be processed in other geographies. Email, underlying AI providers, Apple, backup copies, and other service locations can differ; Singapore hosting does not mean all processing stays in Singapore. We use applicable contractual, technical, and organizational safeguards where required.

9. Retention

Choicewise uses the following retention positions:

Amplitude analytics is retained only as long as reasonably necessary for the product-analytics purposes described above; no fixed Amplitude event-retention period is promised.

After account deletion, minimal pseudonymous purchase-lineage and lifecycle records can remain to verify a later explicit restore and prevent duplicate or revoked purchase claims. Subscription-period usage aggregates preserve decisions already used and are pruned after their relevant period ends. These records do not contain the deleted account's personal content and are not described as anonymous or as legally required solely because they support restoration.

These are policy positions and configuration targets, not measured production retention guarantees. Current server access-log rotation keeps 14 daily rotated files, while the application and gateway container logs have no configured size or file-count rotation limit. The 90-day log target is therefore not a uniform enforced limit. Workflow-checkpoint cleanup, rolling backup cleanup, and the longer support and audit targets are not established as enforced controls. They do not mean every current system, provider, cache, log, checkpoint, or backup enforces the same period or can be immediately purged.

10. Your Choices and Privacy Requests

Depending on the available app and account functions, you can:

Delete Local Data clears selected Choicewise app caches, but the device visitor identifier and local consent record can remain. Account deletion removes or anonymizes the Choicewise-owned account graph and Choicewise-owned analytics identity, but it may not remove every Apple record, provider record, cache, log, checkpoint, or backup. Re-registering with the same email creates a new Choicewise account and does not restore the deleted account's data or identity. Unlinked privacy-request audit records and financial or transaction records can remain after deletion.

Choicewise targets a response to a verified access or export request within 30 calendar days and targets handling a verified account or data-deletion request within 30 calendar days. These are response and handling targets, not guarantees that every request completes within that period or that all providers and backups are purged.

To make a privacy request outside the available in-app controls, contact privacy@xihetao.com.

11. Tracking and App Privacy

Choicewise does not track users across other companies' apps or websites. Tracking is declared false, and the app declares no tracking domains. The collected-data categories are email address, user identifiers, device identifiers, coarse location, other user content, customer support, purchase history, product interaction, other diagnostic data, performance data, and other data such as consent and security records. Depending on the category, these support app functionality, product personalization, or analytics. The information is linked to an account or device; a pseudonymous identifier does not make it anonymous.

12. Children

Choicewise is intended for users who are at least 18 years old and is not directed to children under 18.

13. Security

Choicewise uses measures such as iOS Keychain storage for session credentials, password and code hashing, selected credential and rate-limit expiry controls, access controls, ownership validation, transaction rollback, and security and operational logging. No security measure is perfect, and we do not promise absolute security.

14. Changes to This Policy

We may update this Policy when our data, providers, purposes, retention, markets, rights features, or App Store disclosures change. We will keep the Policy at the stable URL above, update the Last Updated date, and re-present the consent version for material changes where renewed consent is required.

15. Contact

Privacy questions and requests may be sent to: