Trust Center
Private child records need visible trust.
LittleArc is preparing for public GA with plain-language privacy commitments, evidence-gated launch claims, and documented limits for offline emergency use.
Last updated: 2026-06-27
Commitments
What parents should be able to understand quickly
No ads or public feed
LittleArc is not designed around an attention feed, public posting, or ad inventory.
No sale of child data
We do not sell family or child data. Infrastructure providers process data only to run the service.
Parent-controlled access
Parents choose who is invited into a child vault, and roles limit what family members can do.
Controls
How LittleArc protects records today
Account and session security
Better Auth manages sessions using first-party, HttpOnly cookies. Production sign-in requires email verification, and auth endpoints are rate-limited.
Access controls
The API checks active child membership and document visibility before child profiles, vault metadata, signed URLs, and offline-pack blobs are returned.
Files and signed links
Vault files are stored in private object storage. Upload and download links are short-lived, generated after authorization, and signed-link responses are marked no-store.
Encryption scope
The production claim is encryption at rest and in transit, backed by hosting, database, object-storage, and TLS evidence. It is not an end-to-end or zero-knowledge claim.
Offline device copies
Optional pinned emergency documents are encrypted in browser IndexedDB with device-local Web Crypto keys. Emergency summary fields may be kept locally for offline access and should be used only on trusted devices.
Export and deletion
Owners can request child data exports and delete child vaults or accounts. Export files expire, and object deletion is processed by background jobs.
Monitoring and analytics
Operational logs, error monitoring, and privacy-minimized product analytics may be used for reliability and abuse prevention. Analytics must not include child names, health notes, file names, tokens, or secrets.
Audit trail
Sensitive actions such as profile edits, family access changes, offline pinning, and offline document downloads create audit records for incident review.
Limits
What we do not claim
What LittleArc can access
LittleArc is not zero-knowledge. Authorized systems and operators may access data when needed to provide the service, export records, investigate abuse, support users, or meet legal obligations.
Legal and DPDP status
The product is designed with India's DPDP Act in mind, but counsel sign-off, grievance officer details, and the final rights notice remain GA evidence gates.
Clinical status
LittleArc stores and organizes parent-entered information. It does not provide medical advice, diagnose conditions, replace a clinician, or replace emergency services. Vaccine and growth references remain subject to clinical review before stronger claims are made.
Incident contact
A public security and grievance contact path will be published before GA. Until then, do not send secrets or health records through unsolicited email.
Subprocessors and data residency
Infrastructure providers process data so the service can run.
A counsel-reviewed subprocessor and data-residency summary is a GA evidence item. This draft list explains the categories before final legal publication.
- Hosting and networking
- Railway services, private networking, domains, and TLS termination
- Database
- Managed PostgreSQL for account, child, consent, audit, and metadata records
- Object storage
- S3-compatible storage for vault documents and export archives
- Transactional email for verification, invites, reminders, and account flows
- Observability
- Error reporting, operational logging, and privacy-minimized product metrics when configured