JustPic ID
Delete your account
Account deletion is separate from downloading or offloading Your Data. Read this page without signing in; a deletion request requires account ownership verification.
Dedicated to JustPic ID · 2026-11-16
The Human Data & AI Manifesto sets out ecosystem principles and future direction. It does not replace this notice or establish that every product meets those principles today.
Request deletion
Sign in to JustPic ID, open Settings and choose Delete account. Enter your current backup password and explicitly confirm the request. No email confirmation is required. Submitting signs out all JustPic ID browser and mobile sessions. Normal JustPic ID access and server-managed first-party product access are blocked while the request is pending. Independent Firebase product sessions may not honor the request.
Request availability depends on whether deletion intake is enabled for this deployment. Disabling new requests does not cancel or pause an existing request. Check status and cancel by verifying with your current backup password at /account-deletion/status before the deadline; no normal session is created. Do not send passwords, recovery keys or security codes to support.
30-day grace period
The server records one fixed deadline exactly 30 days (720 hours) after your request. This is the maximum recovery window. Normal sign-in is blocked while the request is pending. Repeating the request does not extend the deadline.
To keep your account, verify with your current backup password at /account-deletion/status and explicitly cancel before the original deadline. After cancellation succeeds, sign in again to restore normal access. A new request starts a new grace period.
After the deadline
Normal JustPic ID sign-ins and account access are blocked throughout the pending request, and remain denied after the deadline even when the background worker has not run. Cancellation is no longer available after the deadline. This is not a promise that every data copy has been erased at that time. The separate status page verifies your current backup password and reports status without restoring access.
After the deadline, your request becomes ready for manual processing in the Admin deletion queue. An authorized operator prepares a receipt, completes account-owned cleanup, and records completion after the PostgreSQL account is removed. This is a manual workflow, not an automatic job or a guarantee of erasure exactly at the deadline. The deadline remains the end of the cancellation window.
The background worker, if enabled, restricts additional sessions and devices but does not erase data. Manual completion requires the operator to address product, Firebase, Mail, Drive, shared ownership, and retained-copy dependencies. The Admin completion record verifies PostgreSQL account removal; external cleanup is operator-confirmed, not automatically verified. A minimal receipt retains the account identifier, request deadline, and operator completion identifiers and timestamps; its retention period still requires review.
Your Data and pending deletion
Download & Offload is separate from deletion and is available only when your account and the service meet their requirements. When available, prepare the archive, save the archive and its separate key, then reselect and verify them before confirming offload. Keep both safe: the current recovery process cannot restore offloaded content if you lose the archive or key.
The current archive covers eligible JustPic ID profile content, not all account or product data. Identity and security records and separate Mail, Drive and external copies can remain. Offloading limits normal account access and is not required before requesting deletion.
Your Data offload and restore are blocked while a deletion request is pending. A new deletion request also requires a normal, non-offloaded account.
An account already offloaded outside this workflow may still have a recorded deletion request. Its restore-only screen shows the deadline, but that session cannot cancel deletion. This unsupported combination needs operator review; the deadline is not paused. No recovery or successful erasure is promised.
Data and dependencies
Identity and credentials, devices and sessions, QR and mobile grants, Admin memberships, application ownership, security history, Mail, Drive and filesystem copies require coordinated cleanup. Shared application records and other people's data are not blindly cascade-deleted. Ownership transfer or another usable administrator may need manual review; this does not prevent making a request.
Firebase Auth, Firestore and independent product copies need owner-scoped manual cleanup. The current deletion worker does not erase these copies. Operators must review the known dependencies before recording completion; the system does not claim to discover or delete data in unknown external projects.
Backups and retained records
Older encrypted backups, logs and lifecycle journals are not promised to disappear in 30 days. Which records may be retained, for what purposes, for how long, and with which exceptions still require review. The current local backup policy counts verified snapshots; it is not a fixed number of days.
Recovered backups must remain isolated until current deletion evidence and security controls are reconciled. A backup must not be used to reactivate an expired deletion request. A verified deletion-specific restore promotion gate is not yet implemented, so erasure completion remains blocked.
Mobile access
A pending deletion blocks new JustPic ID mobile sessions and invalidates existing sessions. After cancellation through the password-verified status page, sign in again on mobile. Activity shows up to 50 recent deletion events. Independent Firebase apps may not enforce this restriction. This page does not claim App Store, Google Play or legal compliance; the full workflow and release policies require independent review.

