DRAFT — REQUIRES LEGAL REVIEW BEFORE PUBLIC LAUNCH. Not attorney-approved. Not a compliance determination.
Version draft-v1-2026-09-29 · Effective date: [EFFECTIVE DATE — COUNSEL INPUT REQUIRED]
Privacy Policy (Draft)
This draft describes Laveni’s current product behavior for counsel and beta participants. It is not a legal compliance determination and is not attorney-approved.
Who Laveni is
Laveni is a parenting guidance product that helps caregivers notice what is happening with a child now and prepare for what may be ahead. Contact for privacy questions during controlled beta: support@getlaveni.com. Also see /support.
Who the service is for
Laveni V1 is for adult parents and caregivers. There are no child accounts. Caregivers may enter information about children; children are not expected to sign in as account holders. Whether youth-privacy laws apply is a question for counsel — this page only states the product model.
Information parents provide
- Account email and password (via Firebase Authentication)
- Family membership and caregiver invitations
- Child profile basics such as display name and birth date / age band
- Parent-entered family context (Our Family, Something Changed, onboarding notes)
- Corrections and permission choices about how information is used
Information about children
Child information is provided by caregivers, not by child accounts. Sensitivity classifications include OPERATIONAL, BASIC, PERSONAL, SENSITIVE, and RESTRICTED. SENSITIVE/RESTRICTED content is encrypted at rest when production encryption custody is available, or blocked from persistence when it is not.
Information collected automatically
- Technical signals needed to run the service (authentication state, App Check tokens when configured, basic request metadata)
- Privacy-safe operational error events (no Ask transcripts or child stories)
- Opaque rate-limit counters (not family content)
How information is used
To personalize developmental guidance using Laveni’s intelligence engine and curated knowledge library; to respect your permission choices; to secure the service; and to operate a controlled beta.
Personalization and permissions
For individual pieces of family context you can typically choose:
- Don’t bring this up on its own → stops proactive use
- Don’t use for recommendations → stops reasoning use
- Forget this where allowed → suppresses active use and clears stored content for that item where the product model allows
A separate “don’t send to AI” permission exists in the data model (useForAI). When open-ended Ask is active, only context items that parents have permitted for AI use may be minimized through Laveni’s AI Context Firewall and included in a server-only model request. Conversation itself is not automatically saved as family memory.
AI status
An external language model is active for open-ended Ask. Laveni sends only minimized, permission-filtered context — not your full family database — and does not auto-save the conversation as lasting family facts. When open-ended Ask is active, Laveni may send minimized, permission-filtered family context through an AI Context Firewall to a server-only external language-model provider to generate conversational guidance. Knowledge Objects deepen answers when relevant but do not limit what parents can ask. Conversation is not automatically saved as family memory. When open-ended Ask is not active, Ask remains deterministic and does not call an external LLM.
How information is protected
- Firebase Authentication for caregiver identity
- Firestore Security Rules and server-side authorization checks
- Encryption for SENSITIVE/RESTRICTED vault fields when keys are configured
- App Check available (enforcement intentionally off for now)
- Distributed rate limiting; production does not fall back to local memory
- Logging firewalls that aim to keep child-story content out of telemetry
No system is perfectly secure. We do not claim “100% secure” or “completely private.”
Service providers
Laveni uses processors such as Firebase / Google Cloud, Vercel hosting, a Redis-compatible rate-limit service, optional invitation email delivery (Resend when enabled), and Google Cloud backup/PITR for Firestore. Counsel must review each provider’s terms and DPA. See the legal handoff packet for the inventory.
Advertising and data sale
Laveni V1 does not run ads, does not build advertising profiles from family vault content, and is not designed to sell child or family data.
Session replay
Session replay / DOM / input recording is off and not present in V1 observability policy.
Retention
Context items may carry retention intents such as SESSION_ONLY, UNTIL_RESOLVED, TIME_LIMITED, UNTIL_USER_FORGETS, or ACCOUNT_LIFETIME. Operational disaster recovery currently uses Firestore PITR retention of 7 days and weekly backups with 7-day retention. Suggested telemetry windows (~14 days system / ~90 days security-audit metadata) are operational targets, not counsel-approved legal promises.
Backups and deletion reality
When you forget or delete information, Laveni’s primary active records are updated according to product lifecycle rules (for example SUPPRESSED, DELETED, or DELETION_PENDING). Protected disaster-recovery copies may retain data for the PITR/backup window. Restore procedures are supposed to reconcile deletions so that a parent’s deletion is not treated as a temporary request. Absolute erasure from every offline copy is not instantaneous.
Parent controls available today
- Our Family: correct items; change use mode; forget where allowed; an Owner can remove a child profile and the information linked to that child
- Owner-authorized export and full family deletion exist in the product backend model
- Self-serve UI for family export, full family deletion, and account deletion is not fully shipped for controlled beta — request help via support@getlaveni.com or Support
Children’s privacy
Because caregivers enter information about children, counsel must assess COPPA and other youth-privacy regimes. This draft does not declare those regimes satisfied or inapplicable.
Changes
If this policy changes materially, we will update the version identifier and ask for renewed acceptance where appropriate.