Privacy notice

Accounts and access. Withya uses an adult’s name, email address, sign-in identifiers, and internal account identifiers to sign the adult in and control access. Adults may add a child’s name, date of birth, gender, selected state or territory, and pediatrician contact. Invitations and profile memberships record which adults are linked to a child.

Shared family records. Adults may add feeding, nursing, sleep, diaper, appointment, preparation, checklist, outcome, food-introduction, journal, caption, and photo information. Withya also records changes, export requests, and who performed an action so linked adults can coordinate shared care.

Questions and community. Private resource questions, searches, answers, and conversation history may be stored. If an adult uses the community, Withya handles the community name and profile details they choose, broad child stage or area selections, posts, replies, connections, messages, reports, blocks, moderation records, and notification preferences.

Purchases, devices, and service operation. Withya handles product, purchase, subscription, customer, and transaction identifiers needed to provide per-child access. The service also handles installation identifiers, push tokens when notifications are enabled, notification delivery status, app interactions, retry and recovery state, and operational diagnostic and security records.

Withya uses information to sign adults in, protect account and child-profile access, provide and personalize the selected features, keep shared records synchronized, prepare exports, deliver requested notifications, process and reconcile subscriptions, answer private resource questions when that service is available, operate community features, moderate reports, diagnose failures, prevent duplicate or unauthorized actions, and understand service operation.

Adults linked to a child. Primary and Secondary adults can view, add, change, delete, and export that child’s shared care and journal records, including entries another linked adult made. The Primary manages core profile settings, member removal, child-profile deletion, and billing. Linking one child does not grant access to another child. Removing access cannot retrieve an export or other copy already saved outside Withya.

Community participants. A community post or reply can be seen by eligible community members and moderators. Connected participants can see messages sent through community messaging. Reports and captured report context can be reviewed by moderators. Withya does not automatically publish a private child profile, care log, journal, photo, or private resource conversation to the community; an adult can still disclose information in text they choose to post.

Service providers. Withya uses Amazon Web Services for the backend, sign-in, database, private file storage, and the private-answer service when available; Firebase Cloud Messaging for notifications; Google Play for Android purchases; Google Cloud Pub/Sub for configured purchase notifications; and RevenueCat for subscription verification. These services receive the information needed for their part of the service.

Recipients chosen by an adult. An export contains the shared child information the requesting adult is authorized to access. If the adult sends that export to another app or person, the new copy is outside Withya’s control.

Adults choose photos from their library to add to a child’s journal. Withya prepares a selected photo for upload and can create temporary app copies; it does not delete the original photo from the library. Cleanup can require another attempt after a failure or app restart.

The current Android app sends service traffic to its configured service over HTTPS. Pending care and journal changes can be kept in encrypted app storage, and specific sign-in and recovery records use protected device storage. These measures do not mean that every record is end-to-end encrypted.

Adults choose whether to add optional child details, photos, notifications, private resource questions, and community activity. Notifications require the adult’s permission before Withya binds a push token for delivery. Firebase installation identifiers can still be created by the current Android build before Withya notifications are enabled.

Primary and Secondary adults can request an export of a child profile they can access. A Primary can remove a linked adult; a Secondary can leave a shared profile. Copies already exported or saved by another person cannot be recalled.

Withya keeps ordinary account, family, purchase, community, revision, and service records while they are needed to provide and operate the Withya service. A single general retention period has not been finalized for ordinary records, backups, provider records, manual snapshots, support email, or community report context. This notice does not promise immediate physical removal or a fixed deletion deadline.

The current service default makes a generated export download available for up to 24 hours. Cleanup is asynchronous and can be delayed by a failed attempt. That download window is not a retention period for the family records used to create the export.

An adult can request account deletion through the outside-app account-deletion page or by emailing bunty.pithwa@gmail.com. The deletion page asks the adult to sign in and review affected profiles before confirmation. If the browser flow cannot be completed, use the email contact.

After the service accepts a deletion request, it closes access and starts staged cleanup. A storage or provider failure can leave cleanup pending. Family facts owned by another Primary remain when a departing adult’s membership is removed. Subscription records, minimal records needed to prevent erased information from returning, revision or restoration history, backups, and provider records can remain.

For privacy questions, support, or an account-deletion request, email bunty.pithwa@gmail.com. Withya is operated by Second Innings, Inc.