Whose Day

Privacy Policy

Last updated: October 21, 2026

Privacy Summary

Whose Day is operated by Pueblo Apps LLC. It saves records in this browser on your device. While you are signed in, your profile and custody logs sync automatically to your Whose Day account using Supabase, including notes and attached screenshots. Offline changes stay on this device until the app is open with connectivity again. You choose when to download backups, export, or share reports.

Information Stored in the App

The app may store the information you enter, including your name or label, co-parent label, email address, children's names, activity labels, custody entries, notes, timestamps, and attached screenshot data. Account records also include agreement versions and acceptance times, theme preference, a randomly generated device identifier, last-sync time, and sync-version metadata.

How Information Is Used

We use account and record information to authenticate you, save and sync your records, restore them, generate the reports you request, and provide account deletion. Agreement metadata records the version and time of your submitted agreement. Device and sync metadata help coordinate changes between devices. Feedback you submit is used to respond to you and improve the product.

Where Your Data Lives

A local copy is stored in this browser. Signing in and completing setup enables automatic profile and custody-log sync; there is no separate backup opt-in. Only successfully synced records can restore on another browser or device. Differences that cannot be safely reconciled are held for review instead of silently overwritten.

A verified email-link account is required to enter the app. Previously authenticated devices may reopen offline using saved account information. Signing out locks access through the app and stops future automatic sync on that device but does not erase its local records. This screen lock does not encrypt browser storage. Protect access to your device and email account.

Browser data and sign-in sessions do not automatically move between browsers, devices, or website domains. Opening the app on a new domain requires signing in there to restore cloud records. Local-only records remain in the original browser and domain until exported or synced.

Service Providers and Access

Supabase provides email-link authentication and cloud storage. Resend delivers sign-in emails and processes the recipient email address, sign-in message, and delivery information. Cloudflare hosts the app and handles account-deletion requests. These services process information needed to provide their respective functions.

Signed-in app users can access only their own cloud records through the app. Cloud sync is not end-to-end encrypted by Whose Day: Supabase processes record contents to provide storage and sync. Avoid entering unnecessary personal details in notes or screenshots.

Exports and Sharing

If you export a CSV, email a report, print a report, or submit feedback, you control that action. Exported files and shared reports may contain sensitive custody information, so store and send them carefully.

Download full backup in Settings creates a JSON file containing the settings and dated records currently saved on this device, including notes, original timestamps, embedded screenshots, account ID and email, and agreement metadata. It does not contain sign-in tokens. This file is not encrypted or password-protected. Your choice of download location or sharing service determines where additional copies are stored.

Restore from backup reads the selected file in your browser and presents a preview before applying changes. The backup must belong to the same account ID. Restoring records can make them eligible for automatic cloud sync. Imported agreement metadata does not replace your current agreement history, and the file cannot sign you in. CSV exports cannot be restored through this feature.

Usage Analytics and Your Choice

We use Mixpanel to understand where people start, complete, or leave signup and check-in steps, which features they use, and whether authentication, sync, exports, restoration, or account deletion succeed. We send predefined screen and step identifiers, event times, elapsed step time, random browser/flow/visit identifiers, report types and range presets, export formats, Settings section names, and generalized outcome or error categories. Calendar-day views indicate today, a recorded day, or an empty day without the selected date. Check-in saves indicate first or repeat use based on records on that device. Custom activity events do not include the activity text. Sharing and download requests do not confirm that an email was delivered, a report was printed, or a file was saved.

These events are associated with a browser rather than your name or sign-in email. Which screens you reach and features you use can indicate which parts of the workflow you used. Sync-conflict resolution records whether you chose the device or cloud copy, without the date or either record's contents.

We do not send names, email addresses, child details, custody dates or answers, notes, screenshots, report contents, sign-in links, or authentication tokens as analytics properties. We do not use automatic form capture or session replay. Requests use Mixpanel's US endpoint; Mixpanel necessarily receives network requests, but we disable IP-based geolocation enrichment and omit the page URL and referrer from event payloads.

You can turn off usage analytics using the checkbox on the welcome page or in Settings. The choice applies to this browser and website address. We also honor Global Privacy Control and Do Not Track signals. Turning analytics off clears pending analytics events and local analytics identifiers; it does not automatically delete events already delivered to Mixpanel. Analytics events may be queued on this device while offline, capped at 200 events and discarded after four days if not sent. Mixpanel's project retention is separate and must not be confused with this local queue limit.

Feedback Form

The feedback button may open a Google Form. If you submit that form, your response is handled by Google and may be visible to the Whose Day team for product feedback. Avoid including sensitive legal details unless you are comfortable sharing them through that form.

Deleting Your Account

In Settings, open Delete account, type DELETE, and confirm deletion to permanently remove your sign-in account and its active cloud profile, custody logs, and device sync records. This cannot be undone. Local records on your devices, JSON backups, and previously downloaded or shared exports are not erased by this action. You can remove local records by clearing the app's browser data separately on each device and website address. Remove downloaded files separately from wherever you saved them.

Copies in service-provider backups or operational logs may remain subject to provider retention policies. Account deletion does not remove messages already delivered to email inboxes or copies held by recipients of your reports. Recreating an account with the same email does not restore the deleted account or let it import backups belonging to the old account ID.

Retention

Local records remain until you remove them or your browser clears or evicts them. Active cloud records remain associated with your account until account deletion; the app does not apply an automatic age-based expiry to custody records. Provider backups, authentication and delivery logs, and support messages have separate retention arrangements. This policy does not promise a fixed purge deadline for those copies.

Data Loss Risk

Clearing browser data, browser storage eviction, changing devices, or using private browsing may remove local records. Records that have not successfully synced may not be recoverable. Keep exports of important records and confirm they have restored before clearing data from an old browser or device. A prior online visit is required for offline app loading; a closed or suspended app does not continuously sync in the background.

What We Do Not Do

Future Changes

If payments, additional analytics collection, or attorney-sharing features are added later, this policy should be updated before those features are used by testers.

Back to Whose Day