Privacy Policy

1. Scope and App Overview

This policy applies to:

• Versai (package name: com.versaichat.app)

Versai is a mobile assistant that can use on-device sensors, location, Health Connect health data, and AI chat. The app may show ads and may offer in-app purchases / subscriptions through Google Play.

Core privacy principle: Health data, sensor readings, location, chat history, calorie/exercise records, and similar user content are not stored on our servers as a long-term user profile database. Our developer backend is primarily used for device identity (app user id), premium entitlement status, and server-side AI key management. Chats are stored on your device; for AI responses they may be sent to the AI provider you use depending on mode (your own API key or server-side AI).

2. Health Data — Health Connect

Versai may access health and fitness data through Android Health Connect. Under the Google Play User Data Policy, this section expressly discloses processing of health data.

What health data is accessed?

• Step count (Steps) — Health Connect READ_STEPS / StepsRecord read permission
• Walking / distance data (Distance) — Health Connect READ_DISTANCE / DistanceRecord read permission

The app does not currently request Health Connect read/write access to heart rate, sleep, blood pressure, body measurements, medical records, or other health record types. Only steps and distance read permissions are requested.

How is this data accessed / collected?

• Access is possible only after the user explicitly grants Health Connect permissions.
• Data is read on demand from the on-device Health Connect API for the date range requested by the user.
• If Health Connect is not installed or permission is denied, the related features do not work; the app does not read this data secretly.
• Versai does not run continuous background sync to scrape health data from third-party health apps; it reads when the user asks in chat or when the related tool is invoked.

How is health data used?

• Step and distance information is used to answer user questions such as “how many steps did I take today?” or “what is my walking distance?”
• Read values may be processed temporarily as tool output in the current chat context so the AI assistant can generate a response.
• Health data is not used for ad personalization, marketing profiling, credit scoring, sale, or independent data brokerage.
• Health data is not passed to advertising SDKs (for example AdMob) or purchase SDKs as health data.

Health data storage, sharing, and transfer

• Raw step/distance records read from Health Connect are not written to a permanent health database on our servers and are not archived by us.
• If you use your own API key (BYOK): chat text and any step/distance summary produced as tool output in that turn may go directly from the device to your chosen AI provider (for example an OpenAI-compatible endpoint). This transfer is solely to generate a response.
• If you use server-side AI / free trial / premium server AI mode: chat content (and, when needed for that turn, a text summary of tool results) may be sent through the developer backend to an AI provider to generate a response. The backend is not designed to store this content as a long-term “health file”; its purpose is key management and forwarding the completion request.
• Health data is not sold, rented, or shared with advertising networks.

User controls for health data

• You can revoke permissions at any time in Android / Health Connect settings.
• If permission is not granted, Versai does not use step or distance features.
• Uninstalling the app or clearing app data deletes Versai’s local records on the device; source data in Health Connect remains in Health Connect / the producing health app.

Health Connect Limited Use disclosure

The use of information received from Health Connect by Versai will adhere to the Health Connect Permissions policy, including the Limited Use requirements. Health Connect data is used only to provide or improve user-facing step and distance features; it is not used for advertising, is not sold, and is not transferred to third parties for any other purpose. Humans may read this data only with the user’s explicit consent, for security purposes, or to comply with applicable law.

3. Device Sensors and Local Fitness / Nutrition Records

Versai may take on-demand readings from hardware sensors on the phone through AI tools. These readings are not uploaded to a permanent cloud health archive.

• List of available sensors on the device
• Accelerometer readings
• Light sensor readings
• Short, optional readings from similar device sensors

If you create calorie entries, exercise sessions, nutrition goals, a fitness profile, or workout programs in the app, those records are stored by default in the local on-device database (Room). These local records are not automatically uploaded to our backend.

Note: If you type food/exercise information in chat or send a photo, that content may be sent along the selected AI path for a response (for example a calorie estimate). This is separate from Health Connect health data and does not create a permanent health file on our side.

4. Location Data

Versai may request approximate (ACCESS_COARSE_LOCATION) and/or precise (ACCESS_FINE_LOCATION) location permission for features such as “tell me where I am” and opening nearby places in Maps.

• How accessed: Android location services; only when the user grants permission.
• How used: answering location questions and optionally opening Maps searches.
• How stored: location is not uploaded to our servers for continuous background tracking; it is processed when the feature is used.
• Sharing: location is not provided to AdMob as a health/location profile for ad personalization. If you approve, the on-device Maps app may be opened.

5. Chat, Messages, Photos, and AI Processing

Versai processes chat prompts, messages, tool outputs, and optional images to generate AI responses.

On-device storage

• Chat history and conversations are kept in local on-device storage.
• Preferences, language, theme, selected AI provider, and similar settings are stored on device.
• API keys you enter (BYOK) are kept in encrypted preferences on the device; we do not collect these keys as a user account credential store on our side.

Your own API key (BYOK) mode

In this mode, chat content travels between your device and the AI platform you configured. The developer backend does not insert a permanent storage layer for your chat content; processing is subject to the privacy policy of your chosen AI provider.

Server-side AI / free trial / premium server AI

In these modes, a chat request may be forwarded through the developer backend to an AI provider to generate a response. The backend’s primary role is verifying entitlements/quotas with the device identity, managing server AI keys, and forwarding the completion request. We do not intend to keep your chat history as a long-term user content archive. Message content is still processed at the moment of transmission.

Chat contents are not sold matched to your personal identity (name, email account, etc.).

6. Data Kept on the Developer Backend

Backend data is intentionally limited. It typically includes:

• Device / app user identity (X-User-Id; a stable id derived from the device)
• Premium / subscription entitlement status, product info, expiry timestamps
• Free message quota / usage counters
• API keys and configuration needed for server-side AI (keys managed by the developer)

The backend is not used to permanently store your raw Health Connect step/distance data, sensor time series, location history, or local calorie/exercise database. The backend is focused on “device key and AI keys / entitlement management.”

7. Advertising (Google AdMob)

In free use, Versai may show ads (for example interstitial ads) via Google AdMob. In that context, advertising ID (AD_ID) and technical data needed for ad delivery may be processed by Google advertising services.

• Purpose: fund the app and show ads in free use
• Typical data processed: advertising ID, device/app technical info, ad interactions
• Health Connect health data is not sent to the ad SDK
• After a premium purchase, the ad experience may change / be removed

For Google ads and privacy practices: https://policies.google.com/privacy and https://support.google.com/admob/answer/6128543

8. In-App Purchases and Subscriptions

Versai may offer premium subscriptions / in-app purchases through Google Play Billing and RevenueCat.

• Data processed: purchase status, subscription product id, renewal / expiry info, RevenueCat customer info, technical verification data tied to Play purchase receipts
• Purpose: unlock premium features, prevent fraudulent subscriptions, sync entitlement between device and backend
• Payment card details are not stored on our servers; Google Play processes payment
• Device identity and subscription status may be shared with the backend for purchase verification

9. Other Permissions and Technical Data

• Internet access: required for AI, ads, purchase verification, and configuration
• Notification permission (POST_NOTIFICATIONS): to show notifications when granted
• Foreground service (data sync): local operation for assistant or background sync work
• Firebase Remote Config: remote configuration / feature flags (does not collect a personal health archive)
• Limited technical data such as crash/error info, device model, and OS version may be processed for performance and reliability

Versai does not use call log (CALL_LOG) or SMS read/write permissions. Those features have been removed from the project.

10. Purposes of Data Use (Summary)

• Provide assistant features (chat, tools, sensors, location, steps/distance)
• Run local fitness / nutrition tools on device
• Verify premium entitlements and manage free quotas
• Show ads (free use)
• Maintain performance, fix errors, and comply with legal / store requirements

We do not sell your data for email marketing. We do not sell health data to advertisers or data brokers.

11. Third-Party Services

Key providers and privacy links:

• Google / Google Play — distribution, billing, Health Connect ecosystem, location services
  Privacy: policies.google.com/privacy
• Google AdMob — ad serving
  Privacy: policies.google.com/privacy · AdMob privacy
• RevenueCat — subscription / purchase management
  Privacy: revenuecat.com/privacy
• Android Health Connect — reading steps and distance health data
  Privacy: Health Connect
• AI providers (depending on user or server configuration) — chat completion; the selected provider’s own privacy policy applies
  Privacy: openai.com/privacy
• Firebase (Google) — Remote Config / configuration
  Privacy: firebase.google.com/support/privacy

12. Data Security

We use encrypted on-device storage for API keys and sensitive preferences. HTTPS is used for network communication. No system is 100% secure; managing your device lock and app permissions remains your responsibility.

13. Children's Privacy

Versai is intended for users aged 13 and over. We do not knowingly collect personal data or health data from children under 13. If a parent believes a child has provided data, contact us at myversaiapp@gmail.com.

14. Data Retention and Data Deletion Rights (Data Deletion)

Local data

Chat history, settings, local calorie/exercise records, and similar data live on your device. You can delete them with in-app clear options, by uninstalling the app, or by clearing app data/cache in device settings.

Health Connect data

Source step/distance data in Health Connect is not kept on Versai’s servers. Revoking permission cuts access. To delete source health data, use Health Connect or the app that produced the data.

15. Changes

This policy may be updated. Material changes will be posted on this page with a new “Last updated” date. Continued use of the app means you accept the updated policy.

16. Contact

For questions about this privacy policy, health data processing, or Versai, contact us by email: