Privacy Policy

This policy explains how Vivary LLC ("Vivary," "we," "our," or "us") collects, uses, and protects your information across everything we make: this website and the Vivary iOS beta waitlist, and the Vivary iOS app. Sections 1 through 8 cover the website and waitlist. Section 9 covers the app, and is the one to read if you use Vivary on your phone.

1. Information we collect

Information you give us

• Email address. When you request a beta invite, we collect the email address you enter so we can send you a TestFlight invite and beta-related updates.

Information collected automatically

• Anti-abuse data. When you submit the sign-up form, we record a one-way hashed (salted) version of your IP address, your browser's user-agent string, and a timestamp. We use these only to prevent spam and abuse of the form. We do not store your raw IP address.
• Aggregate analytics. We use a privacy-first analytics service (see Section 4) that reports aggregate metrics like page views and referrers. It does not use cookies and does not identify you.

What we do not collect

• No accounts, passwords, or profiles on this website.
• No advertising or cross-site tracking cookies.
• We do not sell or rent your information, and we do not build advertising profiles.

2. How we use your information

• To send you a TestFlight beta invite when the next wave opens, and occasional updates about the beta.
• To protect the sign-up form from bots and abuse.
• To understand aggregate traffic so we can improve the site.

3. How we share information

We do not sell, rent, or trade your personal information. We share it only with the service providers that host and protect this site and run the app's cloud features (Section 4), and only as needed to operate them; if required by law; or in connection with a business transfer, in which case we will notify you. Providers are bound to protect your data.

4. Third-party services

This website

This site runs entirely on Cloudflare. We use the following:

Cloudflare Turnstile. To keep the sign-up form free of automated abuse, we use Cloudflare Turnstile, which runs invisibly. Turnstile may collect information about your interaction with our site, such as your IP address, browser and device characteristics, and challenge-solving telemetry, to tell humans from bots. Cloudflare processes that information as described in the Cloudflare Turnstile Privacy Policy Addendum and Cloudflare's Privacy Policy. Turnstile does not use this information for cross-site tracking or advertising.

Cloudflare Web Analytics. This service is cookieless, does not fingerprint individuals, and does not collect personal data. It gives us aggregate counts only.

The iOS app

These providers are involved only in the app's cloud features, described in Section 9. When a feature runs on your device — which is most of them — none of these services see anything.

5. Data retention

Website

• Waitlist email: kept until the Vivary beta program ends or you ask us to remove it, whichever comes first, then deleted.
• Anti-abuse data (hashed IP, user-agent): kept only as long as needed to prevent abuse, then deleted.

iOS app

• Cloud requests (photos you send for analysis, questions you ask Ken and their context): not retained. They are processed to answer the request. Vivary keeps no copy, and our OpenRouter account is set to zero data retention.
• Account (the pseudonymous Apple identifier and, if you shared it, your email): kept until you delete your account.
• Contributions (only if you turned them on): kept as long as they are useful for training and evaluating Vivary's models, or until you request deletion, whichever comes first.

6. Data security

All traffic is encrypted in transit (TLS/HTTPS). Sign-up data is stored on Cloudflare's infrastructure with access limited to what is needed to operate the waitlist, and IP addresses are hashed rather than stored in the clear. In the app, sign-in tokens are stored in your device's Keychain and server-side session tokens are stored hashed. No method of transmission or storage is perfectly secure, but we take commercially reasonable steps to protect your data.

7. Your rights

You may ask us to access, correct, delete, or export your personal information, or to withdraw consent, at any time. To do so, email privacy@vivary.app and we will respond within 30 days. Removing your email from the waitlist is as simple as asking. In the app, you can delete your account and its cloud records yourself at any time, without contacting us — see Section 9.

European Economic Area / UK (GDPR)

The data controller is Vivary LLC (privacy@vivary.app). We process your waitlist email based on your consent (which you may withdraw anytime) and process anti-abuse data based on our legitimate interest in keeping the form secure. In the app, we process cloud requests and contributions based on your consent — each is a separate choice you can withdraw in Settings — and process account and usage-metering data as necessary to perform our contract with you and on our legitimate interest in preventing abuse of free cloud requests. You may also restrict or object to processing and lodge a complaint with your local Data Protection Authority. Where data is transferred outside the EEA/UK, appropriate safeguards (such as Standard Contractual Clauses) apply.

California (CCPA/CPRA)

You have the right to know, delete, and correct the personal information we hold (categories: identifiers such as email, a pseudonymous account identifier, a random device identifier and hashed IP; photos and the plant-care content you send to cloud features; and approximate location if you turned region sharing on). We do not sell or share your personal information, and we will not discriminate against you for exercising your rights. To make a request, email privacy@vivary.app.

India (DPDP)

The data fiduciary is Vivary LLC. We process your data for the purposes in Sections 2 and 9 with your consent, and you may access, correct, or erase your data or file a grievance by emailing privacy@vivary.app.

8. Children's privacy

This site, the Vivary beta, and the Vivary app are not directed to children under 16, and we do not knowingly collect personal information from them. If you believe a child has given us their information, email privacy@vivary.app and we will delete it.

9. The Vivary iOS app

What stays on your device

Vivary is built on-device-first. Plant identification runs on your iPhone using local machine-learning models. Your plant collection, photos, journal entries, care schedules, and reminders are stored only on your device — Vivary keeps no server copy of your collection, and there is no cloud sync. (If you back up your device with iCloud or your computer, those backups are governed by Apple's terms, not ours.) Care reminders are scheduled locally on your device.

The app contains no advertising, no third-party analytics or tracking SDKs, and does not access the advertising identifier (IDFA).

Choosing cloud features

A few features go beyond what runs on your phone: bigger questions for Ken, plant health checks, and taking a closer look at an uncommon plant. Before any of those send anything, Vivary asks your permission once and tells you what is sent, who receives it, and how it is handled. You can change the answer at any time in Settings.

Declining keeps everything on-device: identification, your collection, journal, care, and reminders keep working. If we ever materially change what is sent, who receives it, or how it is handled, the app asks again rather than relying on your earlier answer.

Looking up a plant's care information or its toxicity is never behind this permission.

Photos you send for cloud analysis

When you ask for a plant health check, or ask Vivary to take a closer look at a plant the on-device model isn't confident about, the app sends that photo to Vivary's servers, hosted on Fly.io. From there Vivary's own identification models run on Modal, and the interpretation is generated by Google's Gemini model, reached through OpenRouter. If you have enabled optional region sharing, an approximate region (like "Oregon, US") is included to improve the answer — never your precise location.

Photos sent this way are processed to answer your request and are not stored. Vivary keeps no copy, and our OpenRouter account is set to zero data retention and opted out of model training, so requests are not stored or used to train models there. The only photos used to improve Vivary's models are the ones you explicitly opt in to sharing (see "Contributions" below).

Ken, the plant assistant

Questions to Ken are answered on your device when possible. When a question needs cloud AI, the app sends your question along with the context needed to answer it — through Vivary's servers (Fly.io) to OpenRouter, where Google's Gemini model generates the answer.

That context is: the question you ask; and, when you ask about your collection, the plants you have saved (their names and how sure the identification was), their light, watering and garden-bed details, recent care, journal notes related to your question, and health-check results including open and resolved issues and past treatments; plus your display name if you set one in the app.

This context is used only to answer your question. Vivary keeps no copy, and under our zero-data-retention, no-training configuration with OpenRouter it is not retained there or used to train models.

Accounts and the free tier

You do not need an account to use Vivary. The core app — identification, your collection, journal, and care — works without one. Free cloud requests are metered by a random identifier created on your device, which is not tied to your identity.

If you sign in with Apple to use extended cloud features, we receive the pseudonymous user identifier Apple generates for Vivary and, only if you choose to share it, your email address (Apple's Hide My Email is fully supported). We never see your password. Apple's sign-in sheet offers to share your name; Vivary does not read or store it. Sign-in tokens are stored in your device's Keychain, and server-side session tokens are stored hashed.

Deleting your account

You can delete your account at any time in the app: Settings → your account → Delete account. This permanently deletes your account and cloud records from our servers and removes your plants, journal, and photos from the device. You can also request deletion by emailing privacy@vivary.app.

Contributions — off by default

You can optionally help improve Vivary's identification and disease models by sharing anonymized examples. This is off by default and asks for your explicit consent first. It is a separate choice from the cloud-features permission above; turning on cloud features never turns on contributions.

If you turn it on, a contribution includes: the plant photo from an identification or health check, the species you confirmed, and — for health issues — the condition, treatment, and outcome. If you separately enabled region sharing, an approximate region is included.

What a contribution never includes: your account, name, or email; your precise location; your journal text. (Journal notes can reach the cloud only as part of a question you ask Ken — see "Ken, the plant assistant" above — never through contributions.) Photo metadata (location and camera data) is stripped before anything is shared, and if you typed an issue description yourself, an on-device model rewrites it as a generic label first, or it is left out entirely. Each contribution is tagged with a random identifier, not with you. You can turn contributions off at any time and request deletion of past contributions at privacy@vivary.app.

Weather

If you set up garden beds, Vivary fetches local weather through Apple Weather (WeatherKit) to adjust watering guidance. Your garden's approximate location is sent to Apple's Weather service for this purpose, under Apple's privacy policy. Vivary's servers are not involved.

Beta (TestFlight) builds

Beta builds distributed through TestFlight handle your data exactly like the App Store version described above — they contain no additional automatic data collection. If something goes wrong during the beta, you can send us feedback (including screenshots you choose to attach) through TestFlight itself. Apple's TestFlight additionally shares crash logs and usage statistics with us under the TestFlight terms you accept when joining a beta.

Your rights in the app

Everything in Section 7 — access, correction, deletion, export, and the GDPR, CCPA/CPRA and DPDP provisions — applies equally to data from the iOS app. Contact privacy@vivary.app.

10. Changes to this policy

We may update this policy. When we make significant changes, we will update the "Last updated" date above and, where appropriate, notify waitlist subscribers by email. If a change materially affects what the app sends to cloud features, the app asks for your permission again rather than relying on your earlier answer. The current version always lives at vivary.app/privacy, and the app links to this page directly from its settings, so you are always reading the current version.

11. Contact

Vivary LLC
Email: privacy@vivary.app
Web: vivary.app