Your health data stays yours.

Who we are

Valeska is a personal chronic-care companion app published byPhoenixCKK LLC ("PhoenixCKK," "we," "us"). This policy applies to the Valeska app and this website. Valeska is available on iPhone and iPad, and on Android through Google Play. Platform-specific sections below apply only to the version and features you use. By using Valeska, you agree to the practices described here.

Our regulatory status

Valeska is a personal health-informatics tool. It helps you organize the data you enter and surfaces observational patterns from it.

• Valeska is not a medical device and does not diagnose, treat, cure, or prevent any medical condition. It does not provide medical advice. Always consult a qualified clinician.
• PhoenixCKK is not a HIPAA-covered entity and does not act as a HIPAA "business associate." We are a consumer software company.
• Even though HIPAA doesn't apply to us, we built Valeska's data handling to a high standard anyway, and we comply with the consumer-health-privacy laws that do apply (see Your rights and Health breach notification).

What we collect

• Account information, your name and email address, received from your sign-in provider (Sign in with Apple, or Sign in with Google) when you create an account.
• Health information you enter, symptoms, medications, conditions, nutrition, water, mood, cycle data, questions for your doctor, severity ratings, notes, and the dates and times you log.
• Voice transcripts, when you use voice input. Valeska does not store raw audio or send it to PhoenixCKK. On Android, the operating system's speech provider processes dictation according to your device and provider settings; you review the transcript before anything is saved.
• Apple Health data, only if you opt in on iPhone or iPad: vitals, activity, weight, sleep, and cycle data. If you separately enable write access, Valeska can write entries you log yourself back to Apple Health (see Apple Health below).
• Health Connect data, only if you opt in on Android: heart rate and resting heart rate, blood pressure, blood oxygen, blood glucose, respiratory rate, weight, steps, active calories, and sleep sessions and stages. You may separately allow up to 90 days of this history or enable write-only Water access. Valeska does not request reproductive or cycle data, body temperature, or Water read access from Health Connect (see Health Connect below).
• Clinical health records, only if you separately opt in on iPhone: laboratory results and medication records from Apple Health. Laboratory results stay encrypted on your device only. Android 1.0 does not request Health Connect Medical Records permissions or import personal health records (see Clinical health records below).
• Documents you add, photos or scans of insurance cards, IDs, and medical records you choose to store in the app, plus the text the app extracts from them to fill in fields for you.
• Symptom photos you add, if you choose to attach a photo to a symptom. These photos stay on that device, are excluded from Android backup and device transfer, and are never synced to Valeska. They are included in a local data export only when you turn on that export option.
• Optional profile details, date of birth and gender, if you choose to add them. These stay on your device only, they are never uploaded, even with cloud sync turned on.
• Optional approximate location on iPhone and iPad, only if you turn on Weather insights. Valeska sends a reduced-accuracy device location, or approximate coordinates derived from your device-local postal code, to Apple Weather through WeatherKit to retrieve local weather. Valeska does not store or sync the coordinates. Android 1.0 has no Weather insights and requests no location permission.
• Feature-usage and reliability events, after you sign in, Valeska records privacy-bounded events such as which feature or developer-labeled control was used, broad speed and repeat-tap buckets, action-failure categories, paywall, trial, and purchase outcomes, and retention-prompt choices. These events include the event time, platform, and app build, but never health content, free text, prices, raw error messages, or a device identifier in the first-party event. They are sent to PhoenixCKK through Supabase whether or not health-data cloud backup is enabled and are deleted from your device after the server accepts or rejects them.
• Android ML Kit diagnostics, the Android app uses Google ML Kit for barcode and document scanning, text recognition, language identification and translation, and on-device generative AI. Google states that these SDKs collect device and app information, user, device, or per-installation identifiers, performance metrics, API configuration, input and output sizes, feature events, error codes, and configured or identified languages for diagnostics and usage analytics. Barcode auto-zoom also reports a per-scan session identifier, zoom changes, and candidate bounding-box coordinates. Google states this data is encrypted in transit and is not shared with third parties. Google's disclosure lists sizes, configuration, events, and errors rather than scanned images, recognized text, prompts, or model output.
• Reference-lookup requests, when you search for or scan a food, beverage, or medication, Valeska sends the search term, barcode, or drug identifier needed for the lookup to the reference provider named below. These requests do not include your Valeska account identity or health journal.
• Crash & performance diagnostics on Apple platforms, to keep the app stable, the iPhone and iPad app collects crash reports and basic performance data through Sentry. These use a pseudonymous identifier and contain no health data. The current Android release does not include the Sentry SDK or another third-party crash-reporting SDK.

What we do not collect

• Biometric identifiers, fingerprints, or facial-recognition data
• Your precise location
• Your contacts, or photos and files you have not explicitly chosen to add as a document or symptom photo
• Cross-app or cross-website tracking
• Advertising identifiers, or any data used for advertising

How we use your information

Your information is used solely to:

• Provide the Valeska service to you
• Sync your data across your devices while paid cloud backup is active
• Generate the visit-prep summaries you share with your doctor
• Look up reference information (drug and food data) you request
• On iPhone and iPad, match local weather days with symptom days when you enable Weather insights
• Understand which features are used, so we can improve them
• Diagnose crashes and keep the Apple-platform app reliable

We do not use your health data for advertising, marketing, profiling, data mining, or to train AI models, and we never sell it.

How cloud backup works

Valeska works fully offline. A Free account does not upload its own health journal for cloud backup. When Pro or Family access becomes active, cloud backup is on by default for the signed-in account so eligible data can be restored on another device. You can turn it off at any time in Settings.

While backup is on, eligible data is stored onSupabase infrastructure (hosted in the United States) under our control, encrypted in transit and at rest, and protected by per-user access controls. The categories this policy identifies as device-only, including imported laboratory results and symptom photos, are never uploaded. Turning backup off stops future backup and sync of your own data; it does not erase a copy already stored on our servers. That copy is kept while your account exists and is removed when you delete your account. Data another person shares with you may still be transported as part of that care connection even when backup of your own data is off.

Who has access

Your health data is private to you.

• We do not sell, rent, or share your information with third parties for marketing.
• We do not share your data with insurance companies, employers, data brokers, or advertisers.
• Google ML Kit, on Android, receives the diagnostic and usage data described above. Google states that it is encrypted in transit and is not shared with third parties.
• We do not use your data to train AI models.
• Caregivers you invite see only the specific categories of data you grant them, behind an NDA gate. You can change or revoke their access at any time, which removes the shared data from their device.

Dependent profiles and families

Valeska supports profiles for dependents, for example, a parent or legal guardian managing a child's chronic illness, or an adult managing care for a family member. Dependent profiles are created and controlled entirely by the adult account holder:

• All data in a dependent profile is entered by you, or by a caregiver you've invited, the app does not interact with or collect data directly from the dependent.
• Sharing is controlled per profile: a caregiver you invite to one profile sees nothing from your others, and you can revoke access at any time.
• Deleting a dependent profile, or your account, permanently removes that data (see How long we keep it).

Subscriptions and payments

Valeska's paid tiers (Pro and Family) are billed through Apple on iOS and through Google Play on Android. The app store processes the payment, we never see or store your card details. We receive and keep only your subscription status (which tier is active) so the app can unlock your features.

Third-party services we rely on

We keep third parties to a minimum, and we never send them data that identifies you alongside your health information:

• Apple, Sign in with Apple (name + email), Apple Health (if you opt in), Apple Weather through WeatherKit for optional iPhone and iPad Weather insights, and on-device AI (see below). WeatherKit receives the approximate location needed to return local weather; Valeska does not store or sync those coordinates.
• Google, Sign in with Google (name + email), Google Play billing on Android, on-device AI through Android's AICore and ML Kit, ML Kit scanning, text, language, translation, and diagnostic services, and the Android system speech provider when you choose voice dictation. AICore generation runs on your phone, so no health data is sent to Google for generative AI. ML Kit receives the diagnostic and usage data described above. Speech-provider handling depends on your device and provider settings; Valeska does not retain the audio or send it to PhoenixCKK.
• Supabase (US-hosted), stores eligible data while your paid cloud backup is active and transports data through care connections you accept.
• Sentry, used by the iPhone and iPad app for crash and performance diagnostics with a pseudonymous identifier and no health data. The current Android release does not include Sentry.
• Open Food Facts and USDA FoodData Central, when you search for or scan a food or beverage, we send the search term or barcode needed to look up product nutrition. We do not send anything that identifies you.
• U.S. government health databases (NIH / National Library of Medicine RxNorm & RxTerms, and the FDA's openFDA / DailyMed), when you search for or add a medication or run an interaction check, we send the drug search term or identifier needed for the lookup. We do not send your name, account, or any data identifying you.

Apple Health (HealthKit)

If you enable HealthKit in Settings, Valeska readshealth data to display trends and include them in the visit-prep summaries you choose to share. If you separately enablewrite access, Valeska can also write entries you log yourself back to Apple Health, water intake, period and spotting days, cervical mucus, and sexual activity, so your Apple Health record stays complete. We only ever write what you logged. With HealthKit data, we do not:

• Share HealthKit data with advertisers, data brokers, or any third party
• Use HealthKit data for marketing or advertising
• Sell HealthKit data
• Use HealthKit data to train machine-learning models

You can turn HealthKit off any time in Settings → Apple Health, or revoke access on your iPhone or iPad inSettings → Privacy & Security → Health → Valeska.

Clinical records you connect from your providers (lab results and medication records) are handled separately, seeClinical health records below.

Clinical health records

On iPhone, Apple Health can hold clinical records from providers you have connected. With your separate, explicit permission, Valeska can read laboratory results and medication records. You can skip this entirely. Android 1.0 does not request Health Connect Medical Records permissions and does not import personal health records.

Lab results stay on your device. Any lab result you import is:

• Stored only on your device, in the encrypted database, and never uploaded to our servers, even when cloud sync is on
• Never visible to caregivers you've invited
• Never fed to the on-device AI, it does not see your lab values
• Included only in your own data export, for your eyes

Medication records require your choice. On iPhone, you choose what to import. Once saved, the medication follows the same rules as one you add by hand: it syncs while paid cloud backup is active (on by default for Pro and Family unless you turn it off), and a caregiver can see it only if you grant that profile Medication access.

Whatever you import, we never:

• Use clinical records for advertising or marketing
• Sell them, or share them with any third party
• Use them to train AI models

You can remove imported laboratory results in Settings and edit or delete an imported medication from your medication list. Deleting your account or profile removes the local records too.

Health Connect (Android)

On Android, if you enable Health Connect, Valeska readsheart rate and resting heart rate, blood pressure, blood oxygen, blood glucose, respiratory rate, weight, steps, active calories, and sleep sessions and stages to display trends and include them in the visit-prep summaries you choose to share. You may separately allow up to 90 days of this ordinary history. A separate, write-only Water permission lets Valeska write only water entries you log, restore, or re-log for your own profile. Valeska never reads Water and does not request reproductive or cycle data or body temperature from Health Connect on Android. With Health Connect data, we do not:

• Share it with advertisers, data brokers, or any third party
• Use it for marketing or advertising
• Sell it
• Use it to train machine-learning models

You can turn Health Connect off any time in Settings inside Valeska, or revoke access in the Health Connect app underApp permissions → Valeska.

Android 1.0 does not request the separate Health Connect Medical Records permissions and does not import laboratory results or provider medication records.

On-device AI

Valeska's AI runs on your device, Apple's on-device foundation models on iOS, and Android's on-device models (through AICore / Gemini Nano) on Android. Pattern detection and the language-model narration that explains your insights happen entirely on your device. Health data and saved transcripts are not sent to an external generative-AI service, not to us, OpenAI, Google, Anthropic, or anyone else. Voice dictation is handled separately by the operating system speech provider as described above. On Android, AICore performs generation locally on your phone, so your health data is not sent to Google for generative AI.

Clinical records get extra distance from the AI: imported lab results are never included in what the on-device AI reads, so it never sees your lab values.

How long we keep it

Data you sync is kept for as long as your account exists. When you delete your account:

• Your data is permanently removed from our servers within 30 days.
• Locally cached data is deleted from your device immediately.

You can delete your account from inside the app, or request deletion without signing in from our account-deletion page.

Your rights

• Access, your data is visible to you in the app at any time.
• Export, from Settings as a data file or spreadsheet, or through the visit-prep share function. Symptom photos are included only when you turn on the separate photo option for that export.
• Delete, delete your account and all data from Settings, or via our account-deletion page without signing in.
• Correct, by editing any entry in the app.
• Withdraw consent, by deleting your account at any time.

Washington residents (My Health My Data Act): you have the right to know what consumer health data we collect, to request its deletion, and to withdraw consent. We do not sell consumer health data.

California residents (CMIA / CCPA): you have the right to know, delete, and opt out of any sale of personal information. We do not sell personal information.

Other U.S. states: if you live in a state with a comprehensive consumer-privacy law (for example Virginia, Colorado, Connecticut, Oregon, Texas, or Florida), you may have similar rights to access, correct, delete, and opt out. Contact us and we'll honor them.

Security

• Encrypted connections (TLS) for all data in transit
• Encrypted local database (SQLCipher, AES-256) on your device
• Encrypted storage at the server database level
• Authentication required for all data access
• Per-user row-level authorization controls
• Optional two-factor authentication (TOTP)

No system is perfectly secure, but we design, test, and operate Valeska to keep your data protected.

Health breach notification

In the event of a breach of unsecured health data, we will notify affected users in accordance with the FTC Health Breach Notification Rule and applicable state breach-notification laws.

Children's privacy

Valeska is intended for adults managing chronic illness, including parents or caregivers managing a child's chronic illness. We do not knowingly collect data directly from children under 13. Health information about a child in a dependent profile is provided and controlled by the parent or guardian who created that profile (see "Dependent profiles and families" above). If you believe a child has provided us data directly, contact us and we'll remove it.

Changes to this policy

If we materially change how we handle your data, we'll notify you in the app and update the "Last updated" date at the top of this page.

Governing law

This policy is governed by the laws of the State of Florida, United States, without regard to its conflict-of-laws rules. Valeska is offered to users across the United States, and we honor the privacy rights described above regardless of where in the U.S. you live.

Contact us

Questions about this policy or your data? Emailinfo@valeska.app.

PhoenixCKK LLC