Current edition: Android · Adults 18+ · Free · General wellness only
1. Who this policy covers
This policy describes information handled by Vitalsio: Health Tracker, its Android application, this website, and developer support. “We” means the Vitalsio developer. Contact us at leelovesepg@gmail.com. This policy describes the current free, non-commercial edition.
Vitalsio is intended for adults aged 18 or older. It supports general wellness; it is not a medical device. We do not knowingly offer the service to children. Contact us if you believe a child has submitted personal information.
2. Camera processing and face information
A scan starts when you initiate it and grant camera access. The Android front camera supplies temporary frames for face positioning, signal quality checks, and pulse-related optical processing. This is not an identity-verification or face-recognition service.
The current scan-analysis requests do not contain face photographs or raw video. Scan camera frames are not retained as a photo collection or uploaded by that analysis flow. Temporary camera processing is separate from any image you deliberately attach to AI chat.
Device camera permission can be revoked in Android Settings. Without it, camera-guided scans cannot operate. Previously saved records can still be accessed.
3. Profile, records, and local storage
Information you enter may include age, sex selection, height, weight, waist measurements, units, and language preferences. Saved records may contain pulse-related results, derived body metrics, wellness estimates, timestamps, calculation sources, manual entries, and generated explanations.
The profile, records, and app preferences are stored locally on your device. Anonymous device credentials used for AI requests are stored using Android KeyStore-backed protection. A personal account is not required for core record keeping. Reinstalling or moving devices does not provide an automatic account-based recovery service.
Where you authorize an available Android health-platform integration, its permissions and data categories are governed by the permission screen. You can review those permissions in Android settings. Data you choose to include in AI requests follows the rules below.
4. Optional AI features and the information sent
AI functions send information over HTTPS to the Vitalsio gateway, which forwards necessary content to OpenAI for processing. Anonymous device credentials separate service requests; they are not your name or email address.
- Scan estimates and explanations: selected profile fields, structured recorded values, sources, units, and relevant report context. The current flow does not send scan face photos or video.
- Weekly reports: the selected period, summarized records, metric provenance, and comparison context needed to produce the requested summary.
- Chat: your messages and conversation context, pictures you actively attach, and health context when you enable its inclusion. Do not include information about another person without their permission.
AI features are optional. Their controls and consent choices determine future processing. Turning a feature off does not retrieve requests already transmitted. If you upload an image, the image itself may disclose faces, documents, or other sensitive details; choose its content carefully.
5. Providers, purposes, and disclosures
We use information to provide requested features, manage asynchronous reports, protect the service, respond to support requests, and satisfy applicable legal requirements. Hosting and network infrastructure can process technical request information needed to deliver and secure the service, such as IP address, time, and error information.
OpenAI processes submitted content as an AI service provider. Requests use the Responses API with store=false; this is not a promise of zero provider retention. Provider abuse-monitoring rules and any account-specific controls may still apply. See OpenAI’s data controls documentation.
We do not sell your face or health information or use it for advertising targeting. The current non-commercial edition does not initialize product analytics, attribution reporting, or Google Play billing. We may disclose information where required by applicable law or necessary to address abuse or protect rights.
Providers may process data outside your country. Processing locations and applicable protections depend on the infrastructure and provider configuration. We do not claim that all processing occurs in your country or specify an unverified hosting region.
6. Retention by feature
| Information | Current handling |
|---|---|
| Local profile and records | Kept on the device until removed through app controls or local app data removal. |
| Scan-analysis input | Not written to the gateway database as a stored scan request. Upstream processing has separate provider rules. |
| Weekly task input | Held while queued or running; cleared on completion or termination. Queued tasks older than 24 hours expire and their input is cleared. |
| Weekly report result | Retained by the service for up to 30 days. Non-content task and idempotency metadata may remain to prevent duplicate processing. |
| Chat replay text | Short-lived replay storage, configured by default for 15 minutes; no long-term chat archive is provided by the service. |
| Pictures attached to chat | Expire after 2 hours and are removed through service cleanup; deletion is also requested when you clear or leave the conversation. Connectivity and cleanup timing can affect removal. |
| Support correspondence | Kept as needed to respond and document the request, or meet a legal obligation. |
Retention expiry ends service availability; it is not a guarantee of instantaneous physical erasure from every storage layer. Our application logs are designed not to contain health request bodies, images, or secret credentials. Infrastructure and provider logs follow their own operational retention controls.
7. Your controls and deletion requests
Use Settings in Vitalsio to manage local information and request deletion of linked service data. These are distinct storage locations. Server deletion requires internet access and the device’s current service credential. If the request fails, the app retains the credential for retry and must not be understood to have completed server deletion.
The service deletion endpoint removes the current device identity’s tasks, results, chat replay entries, and uploaded chat pictures, and revokes its credential. Uninstalling alone does not notify the server, revoke remote records, or remove information already processed by a provider. We cannot withdraw completed upstream AI requests through this deletion endpoint.
For help, email leelovesepg@gmail.com. Depending on your location, you may have rights to access, correct, delete, restrict, object to processing, withdraw consent, or complain to a data-protection authority. We may need proportionate information to verify a request. Because we do not operate a named user account, we may be unable to locate device-only information or link an email to an anonymous device record.
8. Website visits and email support
This website does not include an advertising tracker, analytics SDK, account form, or newsletter database. Its scripts operate the navigation menu and do not submit health information. Our hosting infrastructure receives website requests and may keep standard access and security logs, including IP address, request time, requested page, and browser information, to deliver and protect the website.
Following an email link opens your chosen mail application. Sending a message shares your address, message, and any attachments with our support mailbox and email providers. Please omit unnecessary health details, identity documents, and payment information.
9. Security and future changes
We use data minimization, encrypted network transport, access controls, and device credential protection to reduce risk. No application, device, network, or storage system can guarantee complete security. Protect your phone and its backups, and avoid sending information through channels you do not trust.
Material changes to features or data practices will require corresponding updates to this policy and additional notices where required. The date above identifies this version. The app’s actual permission and consent prompts remain relevant to the specific action you request.