1. Introduction
AVI Health («we», «our», «us», the «Company») provides the AVI Health mobile application (the «App»), which connects to a Bluetooth wearable device and/or your phone’s health platform (Android Health Connect / Apple Health) to help you and, optionally, your family members monitor health and wellbeing.
This Privacy Policy explains, in line with the EU General Data Protection Regulation (GDPR) and equivalent laws, what personal data we collect, why, on what legal basis, how long we keep it, who we share it with, and what rights you have. It applies to everyone who uses the App.
By creating an account or using the App you acknowledge this Policy. Where we rely on your consent (e.g. for health data or location sharing), you may withdraw it at any time as described in Section 13.
2. Who Is the Data Controller
AVI Health OÜ is the data controller responsible for your personal data processed through the App.
Registry code: 17534088
VAT identification number: EE102998311
EMTAK (business activity) code: 62901
Website: https://avihealthai.com
Contact: info@avihealthai.com
Privacy Contact: Sergei Tolbuzov — info@avihealthai.com
Data Protection Officer (DPO): AVI Health OÜ is not currently required to appoint a Data Protection Officer under GDPR Art. 37. If the scale or nature of our processing changes such that a DPO becomes mandatory, we will update this Policy and publish the DPO’s contact details.
We have data processing agreements (DPAs), or rely on the equivalent standard contractual terms, with each processor listed in Section 6 to ensure they process your data only on our documented instructions.
3. Information We Collect
3.1 Account & Identity Data
- Email address, username, display name, phone number, region
- Authentication method (email/password or Google Sign-In)
- Firebase Cloud Messaging (FCM) push token and device platform (Android/iOS)
- Online/last-seen status (used for the in-app messenger)
- Profile picture, if you choose to set one (Section 3.10)
3.2 Profile Data
Biological sex, date of birth, height, weight, disability status
These are collected during onboarding to personalise health tracking. Depending on account type, this information is stored either locally on your device or synced to our servers (see Section 8).
3.3 Health & Fitness Data (Special Category Data — GDPR Art. 9)
Collected from your connected Bluetooth wearable and/or Android Health Connect / Apple HealthKit:
- Step count, calories, distance
- Heart rate
- Blood oxygen (SpO2)
- Body temperature
- Sleep duration
- Stress level
- Weight and other wellness-module entries available in the App
This data is processed as special category health data. We only process it with your explicit consent, given by enabling the relevant tracking feature or pairing a device. You can withdraw consent at any time by disabling the feature, revoking Health Connect/HealthKit permissions, unpairing your device, or deleting your account.
Most of this data is stored locally on your device. A subset (steps, calories, heart rate, SpO2, body temperature, sleep, stress) is transmitted, only on request, through our servers when you or a connected family member or friend use the location/health-sharing, «Ask About Family», or «Ask About Friends» features described below — see Sections 3.5 and 5.2.
We never use health or fitness data obtained via your wearable, Android Health Connect, or Apple HealthKit for advertising, marketing, or data mining, and we never share it with data brokers or advertising networks. This commitment applies to all health data described in this Policy, not only the California-specific notice in Section 15.
3.4 Temperature Alerts
If your temperature reading crosses a configured threshold, we store an alert record (temperature value, threshold, your name, timestamp, acknowledgement status) so it can be pushed to your connected mutual friends (Section 3.7) — not to every user of the App.
3.5 Location Data
With your permission, we access your device’s GPS location to support the family and friends map feature. Location (and the health metrics in Section 3.3) is only transmitted on demand, when you or a connected family member or mutual friend requests it. It is relayed through our servers to the requesting device via push notification and is not stored — the underlying database record is deleted automatically within seconds, whether or not the request succeeds, and cannot be read back by any client. We do not keep a location history on our servers.
When a live request succeeds, the requesting device saves that one location point locally on that device only, overwriting any previous point held for the same family member or friend. This lets the App show a «last seen» position, clearly labelled as such and never presented as a live location, if a later request goes unanswered — for example because the other person’s device is offline, or because your own device has no network connection at all. This local snapshot is never transmitted to or stored on our servers, persists on your device until it is overwritten by a newer position for that same person, and is removed if you sign out, delete the App, or clear its data.
To know whose last-known position to show even when your device is completely offline, the App also keeps a small local list of your connected family members’ and friends’ names and relationship type — the same connections already described in Section 3.7 — cached on your device. This local list is never transmitted to or stored on our servers, and is removed if you sign out, delete the App, or clear its data.
The map’s contact card also lets you call a connected family member or friend directly: the App reads their stored mobile phone number (Section 3.1) and opens your phone’s dialer with it pre-filled — you place the call yourself; the App never dials automatically. Your mobile phone number is therefore visible to the family members and friends you are connected with so they can reach you. A separate «Call Emergency» button simply opens your dialer with your region’s public emergency number and involves no personal data.
3.6 Messages & Communications
- In-app chat: message text is relayed through our servers only long enough to deliver it via push notification, after which the server-side record is deleted. The message itself is stored only locally on your and the recipient’s devices. A short preview of the most recent message per conversation, and unread-message counts, are kept server-side to power the chat list.
- Support requests: category, subject, and message text you submit through in-app support, together with your email, name, and account ID, are sent to our support inbox by email.
- AI Assistant conversations: see Section 5.2.
3.7 Friend Connections
The App lets you send another user a friend request from a chat; if they accept, we store that connection (both users’ IDs, display names/usernames, and the request’s pending/accepted status and timestamps) so the App can show you to each other on the family map, include each other as recipients for temperature alerts (Sections 3.4–3.5), and enable the AI Assistant’s «Ask About Friends» scenario between you (Section 5.2). Either person can remove the connection at any time, which deletes the record and immediately stops all three. This data is created only when you take an explicit action (sending or accepting a request) — we do not infer or suggest connections.
3.8 Subscription Data
Plan, billing period, activation/renewal/expiry dates, and auto-renew status for paid subscription tiers.
3.9 Technical Data
Device type, operating system, app version, Bluetooth pairing information needed to operate your wearable device, and standard server-side technical/security logs (IP address, request timestamps, basic error logs) generated automatically by our cloud infrastructure. We process technical and security logs under our legitimate interest in maintaining the security, stability, and integrity of the App (GDPR Art. 6(1)(f)).
3.10 Profile Picture
Setting a profile picture is optional. When you choose one, the App opens your device’s own system photo picker (the Photos picker on iOS, the Android photo picker on Android). The App receives only the single image you select — it is never granted access to the rest of your photo library, and it does not read, index, or scan your other photos. You then crop the image on your device, and only the cropped result is uploaded to our cloud storage and linked to your account.
Your profile picture is visible to other signed-in users of the App, in the same way your username and display name are: it appears beside you in chats, on the family and friends map, and in user search results. Only you can change or remove it, from the same Settings screen.
We keep one picture per account. Setting a new one replaces the previous file, and we retain no history of earlier pictures. If you remove your picture, the stored image is deleted from our cloud storage at that point and the App goes back to showing your name initial. The image is also deleted if you delete your account (Section 8).
If you signed in with Google and have not set your own picture, the App displays the Google account photo described in Section 6; in that case we store the link to that image rather than a copy of it.
We do not analyse profile pictures. They are not used for face recognition, biometric identification or template extraction, or any form of profiling.
3.11 What We Do Not Collect
We do not use cookies, and we do not integrate any dedicated analytics or crash-reporting SDK. We do not use any of the data described in this Policy — including the technical/security logs in Section 3.9 — for advertising, behavioural profiling, or data mining.
4. Legal Bases for Processing (GDPR Art. 6 & 9)
| Purpose | Legal basis |
|---|---|
| Creating and operating your account | Performance of a contract (Art. 6(1)(b)) |
| Health, location, and wearable data | Your explicit consent (Art. 6(1)(a) and Art. 9(2)(a)) |
| AI Assistant processing, including «Ask About Family» and «Ask About Friends» (Section 5.2) | Your separate, explicit consent given before first use of the feature (Art. 6(1)(a), Art. 9(2)(a)) — additional to, and distinct from, the consent given for wearable tracking itself |
| Emergency and temperature alerts | Consent, and vital interests (Art. 9(2)(c)) only in a genuine, narrowly-defined emergency where you cannot otherwise be reached |
| Push notifications (health, temperature, and family alerts) | Legitimate interest (Art. 6(1)(f)) in delivering the feature you enabled, alongside the consent already given for the underlying data |
| Chat list previews and unread-message counts | Legitimate interest (Art. 6(1)(f)) in operating the messenger feature |
| Friend connections (sending/accepting a friend request) | Your explicit consent, given by sending or accepting the request (Art. 6(1)(a)) |
| Profile picture (Section 3.10) | Your explicit consent, given by choosing and uploading an image (Art. 6(1)(a)) |
| Security, fraud prevention, technical/security logs, service integrity | Legitimate interest (Art. 6(1)(f)) |
| Responding to legal requests | Legal obligation (Art. 6(1)(c)) |
You may withdraw consent at any time; this does not affect the lawfulness of processing carried out before withdrawal, and may limit which features remain available to you.
5. How We Use Your Information
- Operate your account and authenticate you
- Deliver the health-tracking, temperature-alert, and family location-sharing features you enable
- Power the AI health assistant (Section 5.2)
- Deliver push and in-app notifications
- Process subscription billing and renewals
- Respond to support requests
- Maintain the security and integrity of the App
- Comply with legal obligations
5.1 No Automated Decision-Making or Profiling
The App does not make automated decisions about you that produce legal or similarly significant effects (GDPR Art. 22), and we do not profile users. Should this change, you would have the right to object under Art. 21 GDPR. The App is not a medical device: it does not diagnose conditions or make treatment decisions. Any AI-generated content is informational only and is not reviewed by a human before being shown to you.
HIPAA (United States): AVI Health OÜ is not a HIPAA covered entity or business associate. The App is not intended for use by healthcare providers, and we do not process protected health information (PHI) as defined under HIPAA. If future features involve interaction with healthcare providers or PHI, we will update this Policy and comply with applicable HIPAA requirements.
We do not use automated decision-making or profiling as defined under CPRA, VCDPA, CPA, CTDPA, or UCPA. If this changes in the future, you will have the right to opt out under applicable U.S. state privacy laws.
5.2 AI Health Assistant
Before you use the AI assistant for the first time, we ask for your separate, explicit consent to send your messages — and, depending on the scenario, a snapshot of your own recent health metrics — to Google’s Generative AI service (Gemini) to generate a response. This consent is additional to, and distinct from, the consent you gave for wearable/health tracking itself (Section 3.3), because it involves transmitting your data to a further third-party processor. We process this data under Google’s enterprise API terms, under which Google does not use your prompts or health context to train its general-purpose models. This is processed in real time to produce your answer and is not additionally stored by us.
Your conversations with the AI assistant are saved locally on your device so you can revisit and continue them later; they are not stored on our servers beyond the real-time processing described above. You can rename or delete individual conversations at any time from within the App.
If you use the «Ask About Family» or «Ask About Friends» scenario, the same health-metric fields (steps, calories, heart rate, SpO2, body temperature, sleep, stress) belonging to a connected family member or friend are relayed to you on demand (Section 3.5) and included in the prompt sent to Gemini so the assistant can answer questions about that person. This involves a second person’s special-category health data: the ability to ask about them exists because you accepted a friend request from each other, or — for family — because you are both active members of the same family subscription plan; no further separate opt-in step is required beyond that. Location coordinates are never included in this prompt. Both scenarios re-check this connection every time you send a message, including when you reopen a saved conversation, so removing a friend or a family plan lapsing immediately stops that person’s data from being used this way — even in an old conversation that discussed them before the connection ended.
6. Sharing Your Information
We do not sell your personal data. We share data only with the following processors, strictly to operate the App:
| Recipient | What they process | Purpose |
|---|---|---|
| Google Firebase / Google Cloud | Account data, your profile picture if you set one, health metrics you enable, messages in transit, friend connections, notifications, technical/security logs | Authentication, database, file storage, cloud functions, push notifications, security |
| Google Sign-In | Name, email, profile photo (if you sign in with Google) | Authentication |
| Google Generative AI (Gemini) | Your messages and the health context described in Section 5.2, under Google’s enterprise API terms | Generating AI assistant responses |
| Resend (email delivery) | Your email address and message content, for welcome emails and support requests | Transactional email delivery |
| Android Health Connect / Apple HealthKit | Health metrics available on your device | Merging platform health data with wearable data, at your permission |
| Emergency contacts you configure | Notified in an emergency escalation | Emergency response |
| Law enforcement or regulators | As required by law | Legal compliance |
We do not share data with wearable device manufacturers beyond what is required for the Bluetooth pairing protocol itself; we have no visibility into, and do not control, any data the device firmware itself may transmit to its manufacturer.
7. International Data Transfers
Our processors (principally Google) operate global infrastructure, so your data may be processed outside your country of residence, including in the United States. Where this involves a transfer out of the EU/EEA, we rely on the safeguards our processors provide — currently the EU-U.S. Data Privacy Framework (DPF) and/or Standard Contractual Clauses (SCCs) — to ensure your data continues to receive an equivalent level of protection.
A note on the current status of the DPF. The legal foundation of the DPF has come under renewed scrutiny following a June 2026 U.S. Supreme Court ruling that privacy advocates argue undermines the independence of the U.S. oversight bodies the DPF relies on, and a further legal challenge before the Court of Justice of the EU has been announced. As of the date of this Policy, the European Commission’s adequacy decision underpinning the DPF remains in force and has not been suspended or withdrawn. We require our processors to also maintain Standard Contractual Clauses as a fallback transfer mechanism, so your data continues to be lawfully protected even if the status of the DPF changes, and we monitor developments in this area.
UK users: the same categories of safeguard apply under the UK GDPR, via the UK’s International Data Transfer Addendum and/or the UK extension to the EU-U.S. Data Privacy Framework.
Other jurisdictions: if you access the App from a country with its own data protection law (for example Brazil’s LGPD or Canada’s PIPEDA), we process your data under the principles set out in this Policy and aim to meet the requirements of the applicable local law.
8. Data Retention
- Account & profile data: retained while your account is active; deleted, along with your Firebase Authentication record, when you delete your account.
- Profile picture: retained while your account is active, and replaced rather than accumulated each time you set a new one; the stored image is deleted from our cloud storage as soon as you remove it, and in any case when you delete your account.
- Chat messages: deleted from our servers immediately after delivery; only a short last-message preview and unread counts persist server-side while a conversation exists.
- Location and health-sharing relay requests: deleted automatically within seconds of being handled, whether or not delivery succeeds.
- Temperature alerts: retained while your account is active, for your alert history.
- Friend connections: retained until either person removes the connection or deletes their account, whichever happens first.
- Support messages: retained in our support mailbox for as long as needed to resolve your request.
- Technical/security logs (IP addresses, error and access logs): retained for a limited period necessary for security, abuse-prevention, and debugging purposes, then automatically deleted or anonymised in line with our cloud infrastructure provider’s log-retention settings.
- Backups: our production databases are backed up for disaster-recovery purposes. Backup copies are retained only for a limited rotation period and are not used to circumvent a deletion request — once a backup cycles out, the deleted data is gone from it too. Backup copies are maintained under our legitimate interest in ensuring service continuity, security, and resilience of our systems (GDPR Art. 6(1)(f)).
- Locally-stored data (most health metrics, full message history, AI assistant conversations): stays on your device until you delete the App, clear its data, or delete the individual item in-app.
- Local last-known location cache: the one location point saved on your own device for each connected family member or friend (Section 3.5) is retained until it is overwritten by a newer position for that person, or until you sign out, delete the App, or clear its data.
- Local family/friend roster cache: the names and relationship type of your connected friends (Section 3.7), cached on your device so the last-known location feature keeps working offline (Section 3.5), is discarded when you sign out, delete the App, or clear its data.
9. Children’s Privacy
The App is intended for use by individuals aged 16 or older creating their own account; if you are 16–17, a parent or guardian must consent. We do not knowingly collect personal data directly from a child through self-registration.
COPPA (United States): we do not knowingly collect personal data from children under 13. If we learn that we have inadvertently collected personal data from a child under 13, we will delete it as soon as possible.
If you believe a child’s data has been collected by the App, contact us at info@avihealthai.com and we will investigate and delete it as appropriate.
10. Data Security
- Data in transit to our servers is encrypted (TLS), and our cloud infrastructure (Google Firebase — Firestore for database records and Cloud Storage for profile pictures) encrypts data at rest.
- Server-side access to account data is restricted to what our Cloud Functions need to operate each feature; security rules prevent other users from reading your data directly, and the location/health-sharing relay is structured so it cannot be read by any client, only delivered via push notification.
- Data stored locally on your device relies on your device operating system’s standard app-sandboxing protections.
- No system is completely secure; we cannot guarantee absolute security of information transmitted to the App.
11. Data Protection Impact Assessment
Because the App processes health data at scale, we treat a Data Protection Impact Assessment (DPIA) under GDPR Art. 35 as a standard part of designing any feature that involves significant processing of special category data, and we review completed DPIAs periodically as the App evolves.
12. Your Rights
Subject to applicable law (including GDPR Articles 15–21), you have the right to:
- Access the personal data we hold about you
- Rectify inaccurate or incomplete data
- Erase your data («right to be forgotten»), including via the in-app account deletion feature, which removes your Firestore profile and Firebase Authentication record
- Restrict or object to processing, including any future profiling (Section 5.1)
- Data portability — receive, in a structured, machine-readable format, the data you provided to us directly (e.g. the profile and health data you entered or synced)
- Withdraw consent at any time where processing is based on consent (Section 4), without affecting the lawfulness of prior processing
- Lodge a complaint with the data protection supervisory authority in your country of residence, place of work, or where an alleged infringement occurred
To exercise any of these rights, contact us at info@avihealthai.com. We will respond within one month of receiving your request; for complex or numerous requests this may be extended by a further two months, in which case we will explain why. California and other U.S. state-specific response timeframes are set out in Sections 15–16.
Identity verification: before responding to a rights request, we may need to verify your identity. Verification may include confirming access to the email address associated with your account or requesting limited additional information strictly necessary to confirm your identity. We will not use verification information for any purpose other than responding to your request.
Where a user has died, requests concerning their data may be made by their legal heir or estate representative and will be handled in accordance with the law of the deceased’s country of residence.
13. Managing Your Consent
You can withdraw consent for specific processing at any time:
- Health tracking: unpair your wearable device and/or revoke Health Connect/HealthKit permissions in your device settings
- Location sharing: revoke location permission in your device settings — note that a family member or friend’s device may still hold a locally-cached «last seen» position for you, sent before you revoked permission, until a newer position overwrites it or that device’s data is cleared (Section 3.5)
- Friend connections: remove a friend from within the App at any time, which stops map visibility, alert-sharing, and AI Assistant access to their data (Section 5.2) with that person, and deletes the connection record
- AI Assistant: simply stop using the assistant; no health context is sent unless you initiate a conversation
- Account deletion: removes your server-side data as described in Section 8
- Sign out: also clears the local family/friend roster and any cached last-known location snapshots (Section 3.5) from that device
14. Cookies and Tracking
The App does not use browser cookies and does not integrate any analytics or crash-reporting SDK.
15. California Privacy Notice (CCPA/CPRA)
If you are a California resident, the California Consumer Privacy Act, as amended by the CPRA, gives you the rights summarized below. This section serves as our notice at collection.
Categories of personal information we collect: identifiers (email, phone, device IDs, IP address); characteristics of protected classifications (biological sex, disability status); commercial information (subscription and billing data); geolocation data; your friend connections (Section 3.7); visual information (your profile picture, if you set one — Section 3.10); internet or other electronic network activity information (basic technical/security logs described in Section 3.9, collected only for security and service-operation purposes, not analytics or advertising); and sensitive personal information — specifically health data and precise location, as described in Section 3. We do not collect professional/employment information.
Purpose and retention: each category is collected for the purposes in Section 5 and retained per Section 8.
Sensitive personal information: we use health data and location only to provide the features you enable; we do not use them to infer characteristics about you or for cross-context behavioral advertising.
Sale/sharing: we do not sell personal information, and we do not «share» it (as CPRA defines that term) for cross-context behavioral advertising, so no «Do Not Sell or Share My Personal Information» opt-out link is required.
Your rights: to know and access, delete, correct, and limit the use of sensitive personal information, and to not be discriminated against for exercising these rights. Exercise them by emailing info@avihealthai.com; we will verify your identity before responding.
Response timing: we will respond to verifiable consumer requests within 45 days of receipt, extendable once by a further 45 days where reasonably necessary; we will notify you if an extension applies.
16. Other U.S. State Privacy Laws
If you reside in Virginia, Colorado, Connecticut, Utah, or another U.S. state with a comprehensive privacy law (e.g. VCDPA, CPA, CTDPA, UCPA), you have similar rights to access, correct, delete, and obtain a copy of your personal data, and to opt out of targeted advertising and profiling — which, as noted in Section 5.1, we do not perform. Contact info@avihealthai.com to exercise these rights.
Washington and Nevada consumer health data laws: Washington’s My Health My Data Act and Nevada’s consumer health data law regulate «consumer health data» — a broad category that includes fitness, wellness, and biometric data like the App collects — separately from, and more strictly than, general state privacy laws. They include rights to know, delete, and withdraw consent specific to health data, a ban on geofencing around healthcare facilities, and, in Washington, a private right of action for violations. Where these laws apply to you, we provide the disclosures and rights they require through a separate, standalone Consumer Health Data Privacy Policy, linked from our homepage and in the App, in addition to this Policy.
17. Data Breach Notification
If a security incident results in unauthorized access to your personal data, we will notify affected users and, where required, the relevant supervisory authority or regulator without undue delay, in accordance with GDPR Art. 33–34 and applicable U.S. state breach notification laws.
18. Changes to This Policy
We may update this Privacy Policy to reflect changes in the App or applicable law. We will notify you of material changes via the App or by email. Continued use of the App after changes take effect constitutes acceptance of the updated Policy.
19. Contact Us
AVI Health OÜ
Email: info@avihealthai.com
Website: https://avihealthai.com
For data protection rights requests or complaints about how we handle your personal data, use the same address; you may also contact your local data protection supervisory authority.
