Niva is a pregnancy wellness product operated by DHRITHI TECHNOLOGIES LLC. Niva provides educational wellness support and tools for pregnancy. It is not medical advice and does not replace care from a doctor, midwife, dietitian, or other qualified clinician.
Information The Niva App Uses
Depending on the features you choose, the app may use:
- Account and profile information, such as your name, email address, sign-in provider, account identifiers, avatar, and app settings.
- Pregnancy and wellness information you enter, such as pregnancy timing, due date or last menstrual period, dietary needs, allergies, conditions, symptoms, hydration, meals, nutrients, mood entries, kick events, contractions, movement preferences, and optional notes or questions for a clinician visit.
- Saved-content and product-interaction information, such as saved recipes or reads, recommendation interactions, onboarding progress, and feature usage.
- Technical and diagnostic information, such as app version, device and operating-system context, request status and timing, crash information, security or integrity signals, and privacy-minimized product analytics.
Information Stored On Your Device
Niva stores some account-scoped settings, cached wellness entries, saved-content state, reminder state, and notification history on your device so app features can work reliably. Local reminders are scheduled by the device. Niva does not use Firebase Cloud Messaging for the current local-reminder feature.
Website And Waitlist Information
The public waitlist may ask for:
- Email address
- First name, if you choose to share it
- Whether you use an iPhone
- A short description of what best describes you
- A short note about what you want Niva to help with
The website may also collect source information such as UTM campaign fields, the referring website, and landing-page path so Niva can understand which outreach channels are useful.
Niva does not load third-party behavioral session replay on public pregnancy education pages. Hosting and security providers may still process ordinary request information needed to serve and protect the site. Do not share medical details, diagnoses, exact dates, or other private health information in public forms or free-text fields.
Do Not Put Health Information In Public Forms
Please do not share exact due dates, last menstrual period dates, diagnoses, medication details, miscarriage history, high-risk pregnancy details, or other private medical information in the public waitlist form.
How We Use Information
- To authenticate your account and keep account data scoped to you
- To provide profile, pregnancy-wellness, nutrition, reminder, saved-content, and personalization features
- To operate, secure, troubleshoot, and improve Niva
- To send account or service messages and optional communications according to your settings
- To send private beta or launch updates and understand public-site outreach
Service Providers
Niva uses service providers to operate the app and website. Their role depends on the feature and current Niva configuration:
The current Niva app is free, has no in-app purchase or restore flow, and does not include the RevenueCat purchase SDK.
- Firebase supports authentication, app-integrity checks, and crash diagnostics. Firebase Authentication may process account identifiers and provider credentials. App Check processes technical integrity signals. Crashlytics processes crash, app-build, device, and operating-system context.
- Hosted PostgreSQL infrastructure stores Niva account, profile, pregnancy, wellness, saved-content, recommendation, and communication records.
- PostHog processes restricted product-interaction events and coordinate-only heatmaps used to improve Niva. Niva disables automatic pageviews, autocapture, and session recording, and its analytics boundary blocks raw names, emails, account IDs, exact pregnancy dates, body measurements, health selections, free text, barcodes, request bodies, and purchase credentials.
- Brevo may process email delivery and privacy-minimized delivery-event records when Niva sends account, service, or optional lifecycle email.
- Public-site hosting, security, analytics, form, and spreadsheet providers process the limited information needed to operate the website and waitlist.
Niva does not use app health or profile information for third-party advertising or data-broker tracking in the current iOS app. Niva does not sell waitlist information. Service providers may keep their own operational records under their published policies and Niva's configuration with them.
Retention
Account-linked Niva database records remain while the account is active. Operational email, suppression, provider-event, diagnostic, and product-analytics records use configured retention windows that vary by record and provider. Niva does not publish one universal retention period because these records serve different security and operational purposes.
Within Niva's directly account-linked application records, the deletion workflow retains only the minimal deletion and suppression state needed to prevent replay, prevent an old identity from silently recreating the profile, finish a pending identity-provider retry, and prevent unwanted lifecycle email. This may include a keyed fingerprint instead of the raw deleted account or email value, request and completion timestamps, and bounded retry status. A raw Firebase account identifier is retained only while Firebase identity deletion is pending and is removed when that step completes. If an email-provider response races deletion, Niva may retain a bounded operational outbox/provider record after removing its user link and account-derived idempotency value; that record does not contain the recipient email, Firebase account ID, internal user ID, or health/profile data. Privacy-minimized operational, diagnostic, and provider records described above may follow their configured retention windows.
Delete Your Niva Account
In the Niva app, open Profile → Privacy & Data → Delete account. Niva asks you to confirm the destructive action and recently verify with the sign-in provider linked to the current account. The deletion flow does not write the password, provider credential, Firebase ID token, or fresh Apple authorization code to Niva's database, localStorage, logs, or analytics. Native Firebase Authentication manages the signed-in session.
Once accepted, deletion removes Niva-owned account, profile, pregnancy, wellness, saved-content, recommendation, communication-preference, and local membership rows. Niva removes the Firebase identity, revokes Sign in with Apple authorization when applicable, clears the deleting account's app cache and local device state, cancels its local reminders, and resets the device analytics identity.
If Firebase is temporarily unavailable after Niva's database deletion commits, the request stays pending, the deleted profile remains blocked from recreation, and Niva retries the identity-deletion step. The app reports that pending state instead of claiming that every step is complete. The device keeps a time-bounded random request receipt so it can recover a lost response and check only whether the request is pending or complete; the receipt contains no email, Firebase account ID, provider credential, or health/profile data. Support is available if the pending state does not resolve.
If Niva cannot confirm Sign in with Apple authorization cleanup, it does not claim that provider cleanup succeeded. Niva keeps the deleted profile blocked, completes Firebase identity deletion after a bounded grace period, and directs the user to Apple's Sign in with Apple settings for any remaining authorization cleanup.
Public Reads Standards
Public pregnancy education follows Niva's editorial standards, medical safety boundaries, and sources policy.
Cookies
The public site uses essential site technology and may rely on service providers for hosting, security, public-site analytics, and the waitlist form. See the Niva cookie policy for the current pre-launch cookie and analytics position.
Contact
For privacy questions, account-deletion recovery, or a request concerning website or waitlist information, email [email protected].