Veni Privacy Policy

Effective Date: August 31, 2026
Last Updated: October 22, 2026

Carlos Navas, an individual doing business as Veni ("Veni," "we," "us," or "our") built Veni (the "App") to help you collect your own lab results and medical documents in one place and track what's in them over time. This Privacy Policy explains what information we collect, why, how we use and share it, and the choices and rights you have — including the specific disclosures required for consumer health data under Washington's My Health My Data Act and similar state laws.

If you do not agree with this Policy, please do not use the App.

A note on how this document was prepared: this Privacy Policy — including Section 11 below — was drafted with the help of AI tools and reviewed by Veni's founder, not by a licensed attorney. We've made a good-faith effort to get the substance right and keep it updated as gaps are found, but AI-assisted drafting can miss things a qualified reviewer wouldn't, so please don't treat this as a substitute for your own independent legal advice. Section 11 in particular hasn't been reviewed by an attorney at all. If you spot something that looks wrong or incomplete, contact us using the details in Section 13.

1. Notice at Collection: Consumer Health Data

Several U.S. states (Washington, Nevada, Connecticut, and others) now regulate "consumer health data" separately from general personal information, whether or not a company is a HIPAA-covered entity. Veni is not a HIPAA-covered entity or a healthcare provider — HIPAA generally applies to doctors, insurers, and clearinghouses, not to a consumer app like this one. We are choosing to apply health-data-grade protections anyway, because that's what the information in this App deserves.

Categories of consumer health data we collect:

Why we collect it: solely to provide the App's core function — importing, organizing, extracting, and displaying your own health documents and the trends within them back to you.

Sources: directly from you (the files you choose to import) and, if you connect it, from your Google Drive account (read-only, and only the files you explicitly select).

Categories of consumer health data we share, and with whom: we share the minimum necessary with the service providers listed in Section 4 ("Service Providers") strictly so they can perform services on our behalf (e.g., cloud hosting, document processing to extract metrics). We do not sell consumer health data. We do not share consumer health data with advertisers, data brokers, or anyone for advertising purposes, ever.

Your rights and how to exercise them: see Section 6. You can also reach us directly at cenavas17@gmail.com.

Consistent with Washington's My Health My Data Act, we do not use geofencing around healthcare facilities to target ads, collect location data, or send notifications, and we have no plans to.

2. Information We Collect

2.1 Account information

When you sign in, we receive your name, email address, and a stable account identifier from whichever provider you choose:

• Sign in with Apple — Apple may share your name and either your real email or a private relay address, per your choice.
• Sign in with Google — Google shares your name, email, and profile identifier. If you also connect Google Drive to import files, this includes a read-only authorization scope limited to files you pick — we cannot browse, list, or access your Drive beyond what you explicitly select through Google's picker.

We use Firebase Authentication (a Google Cloud service) to manage the resulting session; your account is identified in our systems by the Firebase-issued identifier, not by a password we ever see or store.

2.2 Health documents and extracted data

The PDFs and other documents you import, plus the biomarker data (name, value, unit, reference range, date) our extraction process reads out of them. This is the core content of the App and the data described in Section 1.

2.3 Patient profiles

If you track more than one person (e.g., yourself and a family member), we store the name you give each patient profile and which documents/metrics you've assigned to them. We do not require or request separate identity verification for people other than the account holder.

2.4 Subscription and purchase information

We use RevenueCat and Apple's App Store/StoreKit to manage subscriptions. We receive your subscription tier (Free or Premium), renewal status, and purchase history from these providers. We do not receive or store your payment card details — those are handled entirely by Apple.

2.5 Usage and diagnostic information

To enforce fair-use import limits and to prevent abuse of our backend, we track how many documents you've imported in a given period, tied to your account identifier. We use Firebase App Check to verify that requests to our backend come from a genuine, unmodified copy of the App, rather than an automated script.

To tell you when documents you imported are ready, we store a push notification token for each device you use the App on, tied to your account identifier. Notifications say only that your documents are ready (or that some need your attention) — never which documents, or anything in them.

We use Firebase Crashlytics to learn about app crashes so we can fix them; it collects a crash log describing what the App was doing when it failed, not tied to your account identity. We do not use any analytics or advertising SDK — Firebase Analytics is explicitly disabled in our configuration, and no advertising SDK is integrated into the App.

3. How We Use Information

We use the information above only to:

1. Provide the App's core functionality — importing, storing, extracting, organizing, and displaying your health documents and metrics.
2. Authenticate you and keep your account secure.
3. Enforce the import limits attached to your subscription tier and process purchases/renewals.
4. Detect, investigate, and prevent fraud, abuse, or security incidents.
5. Provide customer support when you contact us.
6. Comply with legal obligations.

We do not use your health data to train general-purpose AI models, and we do not use it for advertising, marketing profiling, or targeted ads of any kind — we don't run ads in the first place.

4. How We Share Information — Service Providers

We share the minimum information necessary with the following categories of service providers, each acting on our behalf under its own confidentiality and security obligations. We do not permit any of them to use your data for their own independent purposes.

We do not sell your personal information or consumer health data. We do not share it with data brokers. We do not disclose it to advertisers.

We may disclose information if required to by law, subpoena, or other legal process, or if we believe in good faith it's necessary to protect the rights, property, or safety of Veni, our users, or the public — and, where legally permitted, we will attempt to notify you first.

If Veni is involved in a merger, acquisition, or asset sale, your information may be transferred as part of that transaction, subject to this Policy's commitments continuing to apply or you being notified of any change.

5. Data Security

• Data in transit between the App and our backend is encrypted (TLS/HTTPS).
• Backend access is gated by Firebase Authentication and Firebase App Check, which verifies requests originate from a genuine copy of the App.
• Your imported documents, extracted metrics, and patient profiles are stored on your device (via Apple's SwiftData framework), and synced across your own devices through your private iCloud account (Apple's CloudKit service) so your history survives a lost or reset device. This iCloud sync is between your devices and Apple's infrastructure directly — Veni's own servers never see or store this data.
• When you import a document, our servers keep it only until it has been processed — usually under a minute — and delete it right after; anything left over is deleted automatically within 24 hours. The values extracted from it are then encrypted with a key that exists only on the device you imported from (P-256 key agreement and AES-256-GCM), and kept in that form — which our servers cannot read — until that device retrieves them, then deleted; anything not retrieved is deleted within 24 hours. This is what lets imports finish while the App is closed.
• Apart from that, our backend keeps a few small records tied to your account: your import count (to enforce fair-use limits), your subscription tier, and a notification token for each of your devices — none of them contains your health data itself.
• Access to backend infrastructure is limited to personnel who need it to operate the service.

No method of transmission or storage is 100% secure, and we cannot guarantee absolute security. If we experience a breach affecting your consumer health data, we will notify you and any applicable regulators as required by law.

6. Your Privacy Rights

Regardless of where you live, we extend the following rights to all Veni users:

• Right to know / access — what data we hold about you and how we use and share it.
• Right to correct — inaccurate metrics can be fixed via the App's conflict-resolution tools, or by re-importing the source document; other inaccuracies, contact us.
• Right to delete — see below.
• Right to data portability — export your extracted metrics as a PDF report directly from the App at any time.
• Right to opt out of sale/sharing — not applicable; we don't sell or share your data for cross-context advertising in the first place.
• Right to non-discrimination — we will not deny you service, charge you a different price, or provide a different level of service because you exercised any of these rights.
• Right to appeal — if we deny a rights request, you may appeal by replying to our denial email; if we uphold the denial, we'll explain how to escalate to your state Attorney General (for Washington residents) or applicable regulator.

How to exercise these rights:

• In the App: Profile → Account → Delete Account… immediately and permanently deletes every patient, document, and health metric stored on your device; deletes the server-side records described in Section 5 (your import-quota and subscription-tier records, your devices' notification tokens, and any document or encrypted result still waiting to be processed or retrieved); deletes the sign-in account itself; and signs you out. This one step removes your data completely, both on-device and on our servers.
• By email:cenavas17@gmail.com — for any request the in-app tool doesn't cover, or if you no longer have access to the App.

We will verify your identity (typically via the email associated with your account) before fulfilling a request, and will respond within the timeframe required by applicable law (generally 45 days, with one possible 45-day extension for complex requests).

7. Data Retention

Documents you import are held on our servers only until they've been processed, and their encrypted results only until your device retrieves them — each for at most 24 hours (Section 5). Everything else stored on your device and in your iCloud account stays there until you delete it.

We retain your account and health data for as long as your account is active. If you delete your account, we remove the data described in Section 6 immediately upon your request; certain minimal records (e.g., billing history required for tax/accounting purposes, or records of a rights request itself) may be retained for the period required by law, then deleted.

8. Medical Disclaimer

Veni is not a medical device, and it does not provide medical advice, diagnosis, or treatment. The App is an organizational and informational tool. Document extraction is performed by an automated AI process and can contain errors — misread values, wrong units, or misattributed dates. Always verify an extracted value against the original document (available in the App's built-in viewer) and consult a licensed healthcare professional before making any medical decision. Do not use the App for medical emergencies — call your local emergency number instead. See the Terms of Service for the full disclaimer.

9. Children's Privacy

Veni requires account holders to be at least 18 years old (see the Terms of Service, Section 1). We do not knowingly allow anyone under 18 to create an account or interact with the App directly, and the App is not directed to children.

An adult account holder may create and manage a patient profile for a minor dependent (e.g., their own child) as part of tracking their family's health information. In that case, the information in that profile is entered and controlled entirely by the adult account holder — we do not collect it directly from the minor.

If we learn that someone under 18 has created their own account, we will delete it. If you believe a child has provided us with personal information directly, contact us at cenavas17@gmail.com and we will delete it.

10. Where We Operate

Veni is currently offered in the United States (including Puerto Rico), Canada, Brazil, Japan, and Spanish-speaking Latin America: Mexico, Guatemala, Honduras, El Salvador, Nicaragua, Costa Rica, Panama, Colombia, Venezuela, Ecuador, Peru, Bolivia, Paraguay, Chile, Argentina, Uruguay, and the Dominican Republic. Veni is not currently offered in the European Union, the United Kingdom, Switzerland, or Taiwan/Hong Kong. Your information is processed on servers located in the United States (Google Cloud's us-central1 region, via Firebase). By using the App, you consent to this transfer and processing — Japan-based users see an additional in-app cross-border transfer disclosure before their first import; see Section 11.2.

11. Additional Disclosures for the EU/EEA, UK, Switzerland, Japan, and Taiwan/Hong Kong

Veni is not currently offered in most of the regions covered by this section (see Section 10) — the exception is Japan, where the App is offered and Section 11.2 is already in effect. For the EU/EEA, the UK, Switzerland, and Taiwan/Hong Kong, this section describes the additional protections that will apply once Veni becomes available there, so that the commitments below are already in place before that expansion happens rather than being added afterward.

11.1 European Union/EEA, United Kingdom, and Switzerland

Once the App is offered in the EU/EEA, the UK, or Switzerland, the following applies under the General Data Protection Regulation ("GDPR"), the UK GDPR, and Switzerland's Federal Act on Data Protection ("FADP"):

• Controller. Carlos Navas, doing business as Veni (Section 13), is the controller of your personal data.
• EU/UK representative. Because Veni is not established in the EU/EEA or UK, Article 27 GDPR and Article 27 UK GDPR require us to designate a representative there before offering the App to individuals in that region. We will appoint one before launch and publish their contact details in this section at that time.
• Legal bases for processing. Account and authentication information (Section 2.1) is processed under Article 6(1)(b) GDPR, as necessary to provide the App under our contract with you. The health data described in Section 1 — documents, extracted metrics, and patient profiles — is "special category data" under Article 9 GDPR, and we process it on the basis of your explicit consent (Article 9(2)(a)), given when you import a document or add a patient profile; you may withdraw this consent at any time by deleting the relevant item or your account (Section 6), which does not affect the lawfulness of processing before withdrawal. Usage information (Section 2.5) is processed under our legitimate interest in preventing abuse of the App (Article 6(1)(f)).
• International transfers. Your data would continue to be processed in the United States (Section 10). Before offering the App in these regions, we will put a recognized transfer mechanism in place with each service provider named in Section 4 — the European Commission's Standard Contractual Clauses, the UK's International Data Transfer Addendum, or the Swiss-adapted equivalent, as applicable.
• Your rights. In addition to the rights in Section 6, you will have the right to lodge a complaint with your local supervisory authority — in the EU, the authority of your habitual residence, place of work, or place of the alleged infringement; in the UK, the Information Commissioner's Office; in Switzerland, the Federal Data Protection and Information Commissioner — and the right to object to processing carried out on the basis of our legitimate interests.

11.2 Japan

The App is offered in Japan, so the following applies under the Act on the Protection of Personal Information ("APPI"):

• Purpose of use. Section 3 states each purpose for which we use your personal information. We will not use it beyond those stated purposes without first obtaining your consent, as APPI requires.
• Special care-required personal information. The health data described in Section 1 is "special care-required personal information" under APPI Article 2(3). We obtain your consent before acquiring it, which you give by choosing to import a document or add a patient profile.
• Cross-border transfer. Because your information is processed in the United States (Section 10), providing it to our U.S.-based service providers (Section 4) is a transfer to a third party in a foreign country under APPI Article 28. Before your first import, the App shows an in-app screen disclosing that your data is transferred to and processed in the United States, describing the receiving country's data protection measures (Section 5), and requiring you to affirmatively agree before the transfer takes place. You can review this disclosure again at any time from Profile → Settings → International Data Transfer.
• Your rights. You will be able to request disclosure, correction, addition, deletion, or suspension of use of your personal information, and suspension of its provision to third parties, by contacting us as described in Section 13. We will respond within the timeframe APPI requires.

11.3 Taiwan and Hong Kong

Once the App is offered in Taiwan or Hong Kong, the following applies under Taiwan's Personal Data Protection Act ("PDPA") and Hong Kong's Personal Data (Privacy) Ordinance ("PDPO"):

• Notice at collection. Consistent with Taiwan PDPA Article 8 and Hong Kong PDPO Data Protection Principle 1, Sections 1–2 already state who collects your data, the purpose of collection (Section 3), the categories collected, and your rights and how to exercise them (Section 6). You may decline to provide any information described in those sections; doing so may mean the App's core features are unavailable to you.
• Accuracy, retention, and use. Sections 5 and 7 describe how we secure and retain your data, and Section 3 describes how we use it — limited to the purposes stated there, consistent with PDPA Article 5 and PDPO Data Protection Principles 2 and 3.
• Your rights. In addition to Section 6, you will have the right to request access to and correction of your personal data under Taiwan PDPA Articles 3 and 10, and Hong Kong PDPO Data Protection Principle 6. Contact us as described in Section 13.

12. Changes to This Policy

We may update this Policy from time to time. If we make a material change, we'll notify you in the App or by email before it takes effect, and update the "Last Updated" date above. Continuing to use the App after a change takes effect means you accept the updated Policy.

13. Contact Us

Carlos Navas, an individual doing business as Veni
Avenida Roosevelt, Edificio Sea Garden, Torre 1, Maldonado, Uruguay, ZC 20001
Email: cenavas17@gmail.com

Washington residents may also contact the Washington State Attorney General's office regarding consumer health data concerns.