TOKENVIVE · PRIVACY POLICY
Privacy Policy
Updated: November 1, 2026
Scope
This policy applies to the TokenVive iPhone app, Apple Watch app, Home Screen widgets, watch complications, and tokenvive.app website. It explains how personal information is handled and your rights.
TokenVive stores AI sign-in credentials, usage limits and available usage history, health inputs, body energy, manually logged sleep, break records, and reminder settings primarily in local storage on your iPhone, paired Apple Watch, and the devices used by their widgets and complications. Your device connects directly to your selected AI provider for sign-in and usage checks; body energy is calculated on device. These features do not automatically upload AI credentials, usage history, or health records to TokenVive servers.
To verify Pro access, restore purchases, and preserve trial and invitation benefits, the app connects to online services to process necessary App Store verification information and membership records. Feedback or support emails you choose to send are also used to handle your request. The scope, purposes, and storage of this information are described below.
Age requirement and minors
TokenVive and its companion services are intended for users aged 13 or older who also meet the applicable minimum age in their region. Users below the local age of majority must use the service with the consent and guidance of a parent or other guardian. We do not knowingly collect personal information from users below this minimum age. Users or guardians who discover or suspect collection of information from a user below the minimum age, or processing without legally required guardian consent, can contact the developer using the email in this policy. Include only a description of the issue and necessary contact information. Do not send identity documents, account credentials or complete health records. After verification, we will stop the relevant processing, delete personal information under our control as required by law, and explain the outcome to the person who reported the issue. Users can manage on-device data through the app and system controls. Original Apple Health records remain under their control through Apple Health.
Apple Health and body energy
Health records are sensitive personal information. With system permission on the relevant device, the app reads available sleep, heart rate, resting heart rate, heart rate variability, respiratory rate, steps, active energy, workouts, stand duration, stand hours, and mindfulness records to display trends, build a personal baseline, and estimate body energy. Denying or withdrawing health permission does not affect AI account features; related health displays and reminders may become unavailable.
Phone and Apple Watch read health records separately and supplement one another's inputs through Apple's paired-device communication. Input caches stay on device and can be used for background calculations after the first unlock. Only the phone calculates body energy. Results and necessary trend and metric summaries sync to the watch; phone widgets and watch complications read local shared caches. Manually logged sleep, no-sleep confirmations, and rest records stay on device to refine estimates. The app does not write to Apple Health.
These health records are not sent to TokenVive servers or AI platforms, or used for advertising, marketing, research partnerships, or generative AI. Widgets and notifications may display health readings visible to others who can see your screen. Body energy is for everyday awareness, not medical diagnosis or emergency monitoring.
After you first explicitly connect Apple Health and grant system permission, the app may read necessary health records and perform a limited amount of local preparation while in the foreground to reduce the initial wait. While your Pro status is unconfirmed, preparation results stay internal to the device and are not used for normal health results in the app, widgets, the watch, or service reminders. The relevant displays update after valid access is verified and the necessary inputs are ready. This preparation does not result in indefinite background health updates once the absence of valid access is confirmed.
AI sign-in & usage checks
You authorize access on the official website of your chosen provider: OpenAI for Codex, Anthropic for Claude Code, Cursor, GitHub for GitHub Copilot, xAI for Grok, Google for Antigravity, or Meta for Muse. TokenVive does not receive your sign-in password. Your device handles the temporary codes, access tokens, session credentials, and credentials for refreshing sign-in supplied by the provider. Requests to sign in, identify your account, and retrieve usage limits and available usage summaries go directly to that provider. The provider may receive your IP address, request time, client identifier, and authorization information.
Your iPhone handles sign-in and session refresh. Credentials for refreshing sign-in stay in your iPhone’s Keychain. A copy of access credentials is sent to your paired watch. Your iPhone, watch, and usage widgets can check usage directly and sync the latest successful result. Widgets use the shared Keychain on their own device. Watch credentials may be access tokens or provider session credentials; the provider determines their permissions. Removing refresh credentials does not make provider access read-only.
The shared container on your device stores account identifiers, custom names, necessary routing information, usage limits, reset times, available usage summaries, and update status. Your device retrieves available Codex message counts and token history, as well as Cursor token history, and summarizes them by date without saving conversation text. Coverage depends on the data the provider supplies and your account permissions. TokenVive does not actively read or save conversation text, or use these credentials to send generative AI requests.
Membership identity, trials, and purchase verification
TokenVive links your Pro access using verification information provided by the App Store. You do not need to provide TokenVive with a separate account password, phone number, or sign-in email. Your device sends the necessary signed App Store proof and device verification identifier over an encrypted connection to the membership service for verification. The service maps the verified App Store identity to a membership ID using a derived reference that does not directly reveal the original identifier. This supports checking existing access after reinstalling or changing devices and prevents duplicate one-time trials and invitation rewards.
Our membership service stores your membership ID, invitation code, one-time trial grant time, gift and invitation records, remaining trial time, purchase and validity records, necessary renewal status, and access adjustment records. To verify and restore purchases, confirm renewal or refund status, and maintain Pro access, Apple, the membership service, and entrusted providers of purchase verification and membership services process the necessary membership identifiers and purchase records. The purchase verification service also receives device identifiers (such as IDFV) to provide purchase verification and membership services. These activities do not require your AI credentials, conversation text, or health records. Apple handles payment and account authentication; TokenVive does not receive your Apple Account password or bank card information.
Purposes, sharing, and infrastructure
The data above supports account queries, paired-device sync, health displays, and reminders that users enable. TokenVive does not sell personal information, share it for cross-context behavioral advertising, integrate advertising or cross-site tracking SDKs, or use health data for advertising.
AI platforms process direct requests under their own terms and privacy policies. Direct connection does not mean offline operation or no third-party server processing. Some platform infrastructure may be outside your country or region. Consider your chosen provider's privacy information before connecting. Health data is not included in usage requests to these platforms.
The website uses AWS US West (Oregon) infrastructure and Google Cloud DNS. When you visit the website, network providers may process technical information such as IP addresses and request times for connectivity, operation, and security. AI data queries go directly to your selected provider; membership identity and access verification separately require a connection to the membership service.
Notifications, motion, and screen content
When you enable notifications, TokenVive creates local reminders and daily summaries using the usage data, energy estimates, break records, and reminder settings saved on your device. These records are not uploaded to a push notification server, and AI models do not generate the summaries. You control notification permission, sounds, quiet hours, and whether details are hidden. Reminder settings sync between paired devices. Details are hidden by default. If you turn off Hide notification details, notifications may show account names, usage information, or health readings. Change this in Settings → Notifications → Delivery, or turn off notifications or previews in your device’s Settings. This setting only hides notification details; it does not hide content in the app, Home Screen widgets, or watch faces.
With Motion & Fitness permission, Apple Watch stand reminders use movement and stationary activity to estimate how long you have been inactive. Data and reminder state are processed and stored on the watch. This does not precisely detect whether you are sitting. Turn off stand reminders in TokenVive’s notification settings and manage Motion & Fitness permission in your device’s Settings. Stopping and clearing health data removes related health notifications and summaries; you manage AI usage alerts separately. System permissions for health, notifications, and motion are not automatically revoked by this action.
Third-party processing and responsibility
Independent third-party websites, accounts, and services process personal information under their own applicable terms and privacy policies. We cannot control their independent processing. To the extent permitted by applicable law, we are not liable for disclosure, loss, or misuse caused entirely by their independent processing and not by our breach of this policy or legal duties.
We remain legally responsible for protecting personal information that we entrust to third parties to provide the Service, and manage the scope and security requirements of that processing. The preceding limitation does not exclude our own legal duties or responsibility for entrusted processing.
Business transfers
If a merger, acquisition, or business transfer requires transferring personal information, we will notify users of the recipient and relevant matters as required by law and require the recipient to continue applicable data protection duties. Transfers are limited to information necessary for the relevant business. A business transfer alone does not expand processing purposes. Material changes to purposes or methods will follow legally required notice and consent procedures.
Such transfers cover only information that we actually control. They do not mean that we hold or can remotely retrieve AI credentials, usage history, or health records stored on your devices.
Website tracking and support email
The website has no advertising or analytics tracking scripts, sets no tracking cookies itself, and embeds no third-party tools for ongoing tracking across websites or online services. The website provides separate language URLs and does not store a language preference. The website does not currently adjust processing in response to browser Do Not Track (DNT) signals. It performs no such cross-site tracking or advertising sharing regardless of those signals.
When users email the developer, the developer receives their email address and voluntarily supplied content to handle the request. Do not include passwords, authorization codes, access tokens, complete health records, or other unnecessary sensitive information.
Retention, disconnection, and deletion
While an account is connected, your device keeps the credentials and connection data needed to check usage. To disconnect, open the account’s menu in Settings → AI accounts. The device stops checking that account and removes its saved credentials from Keychain and its current usage data. Your watch removes its credentials and usage data after receiving and processing the disconnection update. An offline watch or background restrictions may delay this; an offline watch may continue checking usage until it receives the update. Disconnection markers, account names, and necessary state remain to prevent older sync messages from restoring the account.
Disconnecting in TokenVive does not close the provider account or automatically revoke the provider’s authorization. To fully revoke access, also remove the relevant sessions, authorizations, or tokens using the provider’s security settings. The provider’s own data retention and deletion rules still apply.
After you confirm Stop and clear both devices in Settings → Apple Health → Health metrics on iPhone or in Watch settings, this device stops reading health data and clears health inputs, body energy and history, manual sleep and no-sleep entries, rest records, related summaries and health notifications from TokenVive. AI accounts, usage alerts, membership and trial or invitation eligibility are kept. A clear request for an offline paired device remains pending until that device receives it, clears its data and acknowledges completion. The app does not report both devices cleared before that acknowledgement. Older sync messages cannot restore deleted records. Widget displays may change later when the system refreshes them.
Original Apple Health records and system permissions are kept. You may explicitly reconnect on iPhone to read records still in Apple Health under existing permissions and rebuild calculations. Deleted manual sleep and rest records are not restored from old paired caches. Manage system health permissions separately on each device. Membership expiry only stops updates and keeps history; it does not trigger this clear operation.
Uninstalling TokenVive does not revoke provider access, cancel subscriptions, or guarantee deletion from shared Keychain, other extensions, or system backups. We retain website technical logs and support emails only as needed to respond to requests, maintain security, or meet legal obligations, then delete or de-identify them. To request deletion of information under our control, email the address in this policy. The developer cannot remotely clear data stored on your devices. System and third-party retention rules apply separately.
The membership service retains membership IDs, one-time trial markers, gift and invitation records, and purchase and access adjustment records for as long as necessary to provide and restore access, prevent duplicate grants, handle disputes, or meet legal obligations. Uninstalling the app, disconnecting an AI account, or clearing health data does not delete these membership records or reset one-time trial eligibility. You can send a data request to the email in this policy. Records that must legally be retained are handled as required, and we explain what cannot be deleted immediately and why. Feedback and support content is retained only as necessary to handle issues and meet necessary obligations, then deleted or de-identified.
Feedback you choose to submit
When you tap Submit in Settings → Feedback, the app automatically includes your own referral code (marked as unavailable if it cannot be retrieved) and sends your optional contact email, the feedback category, your description, the images you selected, and a random identifier used to recognize the same submission. The code helps locate the issue; it is not a sign-in credential. Submitting a code does not automatically change Pro access. A contact email is optional and is used only to contact you about this feedback. The app does not automatically attach AI credentials, health records, or complete diagnostic information for this purpose.
Selected images are resized and re-encoded on your device before upload. Hide account information first, and do not submit passwords, authorization codes, access tokens, identity documents, or health records. Feedback is stored by the support service to review, handle, and respond to issues, subject to this policy’s retention and deletion rules. If you contact us by email, we receive your sender address and the content you choose to provide.
Choices and privacy rights
Connecting AI accounts and reading health data are optional and require user authorization. Data may be unavailable without relevant permission. Contact the email in this policy to learn the categories, sources, purposes, and recipient categories of personal information we process; request access, copies, correction, or deletion of identifiable personal information under our control; or make other requests under applicable privacy law.
We may verify identity to handle requests, asking only for necessary information. Do not provide passwords or credentials. We respond within legally required time limits. If a request cannot be fulfilled, we will explain why and the applicable next steps. We do not discriminate against users exercising privacy rights. Withdrawing permission needed for a feature may make that feature unavailable.
Security
External sign-in and usage requests use HTTPS. Antigravity also uses a localhost callback on your device to receive authorization codes; this does not upload data to an external service. Sign-in credentials are stored in system Keychain items that are accessible after the first unlock and restricted to that device. Credentials for refreshing sign-in are not sent to your watch. The shared container on your device stores account metadata, saved usage data, and cached health inputs needed by TokenVive and its extensions. This storage should not be understood as end-to-end encryption with keys that only you can access.
TokenVive does not actively upload health data to the cloud. Device or system backups may retain information under their own rules; on-device processing does not mean every backup is excluded. No method of transmission or storage is completely secure. We will meet applicable security and incident-response obligations. Keep your device secure and never send authorization codes or access credentials to support staff.
Policy updates and contact
We may update this policy as features and personal information processing change, indicating the update date. Material changes to processing or user rights will be communicated before implementation through in-app notices, prominent page notices, or other appropriate means. Where legally required, separate consent will be obtained before the processing starts; continued use does not replace that consent.
Send privacy questions, data requests, and other support inquiries to the TokenVive developer at hakumataczyy@163.com.