PRIVACY

Shared breaks, not surveillance.

Last updated: October 23, 2026.

Account information

If you create an account or invite a friend, DioPact processes your email address or identity from Apple, Google or email sign-in, your chosen name, an account identifier, invitations and the check-ins you choose to send. This information supports your account and the two-person features.

What stays in the app

Your pet choice, pet name, earned seeds, break times, selected app identifiers and any usage measurements are stored locally. DioPact does not send selected app identifiers, usage measurements or break times to Firebase or your friend.

On supported iOS devices, temporary app protection requires Screen Time authorization. On Android, optional Usage Access can measure activity for selected apps; DioPact does not block apps on Android. A timer-only break remains available when these capabilities are declined or unavailable.

What you share with a friend

An invitation or check-in is sent only after you choose the action. App usage, selected apps, break duration and check-ins are never shared automatically. Notifications, if enabled, contain only a generic update signal; the authenticated app fetches the current details.

Notifications and service providers

If you enable notifications, the app associates a notification token and platform with your account to send a generic update signal. The token is not shared with your friend and is removed when you opt out or delete your account. Firebase Authentication, Firestore and authenticated Functions process account and shared information.

Retention and deletion

Records with configured expiry become eligible for deletion after these periods: time requests after 30 minutes, encouragement messages after 24 hours, pact events after 30 days, time grants after 90 days, policy proposals after 365 days, and invitations, command receipts and synchronization signals after 7 days. Canonical policy records and older records without an expiry are not covered by the current TTL configuration. Firestore TTL deletion is asynchronous and typically occurs within 24 hours after eligibility, but that timing is not guaranteed. A 365-day eligibility period is not a guaranteed deletion maximum.

You can delete your account in the app after recent reauthentication. For an Apple-linked account, you must also reauthenticate with Apple and revoke its authorization grant before the server deletion request proceeds; if that step fails or Apple does not provide the required code, account deletion does not continue. Server deletion immediately removes the authentication account, profile and device records, and every active or historical pact with its data. An active pact is ended and the other member's active-pact reference is cleared before removal. This also deletes the other member's data within those deleted pacts, but not their profile, devices, local progress or unrelated pacts. Related invitations, receipts, counters and processing messages addressed to the account are also removed. Generic update signals for other people may remain until their seven-day expiry; they can include routing identifiers for the recipient, such as a target UID and command ID, but contain no identifier for the deleted account and no check-in or usage content. TTL removal is asynchronous. Deletion also clears the local accountability ledger; local pet and seed progress is not an account record and may remain on this device.

Voluntary tool

DioPact is not medical treatment and does not guarantee exact measurement or app blocking. A timer or local measurement does not prove abstinence.

Contact

For questions about your information, email support.frenchtech@gmail.com.