JustPic ID privacy notice
A clear account of the identity layer.
This notice describes how JustPic ID processes information for identity, authentication, account management, and the JustPic ID services that are currently enabled.
Dedicated to JustPic ID · Published for JustPic ID
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.
What JustPic ID does
JustPic ID provides a central identity and authentication account for independent JustPic products. It is separate from the business logic and content of those products.
This notice applies to JustPic ID at justpic.id and its identity API. A product you access through JustPic ID may have its own notice for product-specific processing.
Information used for an account
When you create an account, JustPic ID stores your display name, username, selected region, a password hash, a username-derived @justpic.id address, permanent identity identifiers, sessions, challenge and device context, and security audit records.
Account creation does not require an outside email address or phone number. Internal JustPic Mail is enabled only when mail infrastructure is configured for this deployment; check your Account Center for current mailbox availability.
JustPic Mail
When enabled, internal messages and attachments are stored in a mailbox associated with your permanent JustPic UID. Mailbox status, quota and activity metadata are stored separately from message content. Sending and receiving outside @justpic.id are not enabled in this phase.
Local encrypted backups can include mailboxes and queued messages on the same SSD. Seven verified snapshots are retained by default when the local backup job is enabled; this is a snapshot count, not a promise of seven-day retention or protection against disk loss. Message deletion does not erase older backup copies. Account-level mail export, deletion and backup rights requests currently require manual review through the privacy contact page.
Authentication and security
JustPic ID processes session, device, challenge, and login activity information to authenticate you, prevent abuse, protect accounts, and support recovery. Passwords are stored as hashes, not as readable passwords.
For abuse prevention, the API stores keyed hashes derived from request IP addresses, usernames, and account identifiers with request counts and rate-limit window timestamps. The raw bucket key is not stored in that table. Expired rows are removed opportunistically; a maximum retention period is not yet configured or published.
We retain security records for as long as needed to protect the service, investigate abuse, meet operational requirements, and resolve disputes; specific retention periods and cleanup schedules remain to be set.
Connecting an existing JustPic account
If you choose to connect an existing JustPic account, Firebase Phone Authentication verifies the phone number associated with that account. The identity API checks the verified Firebase UID, phone number, Passion ID, and any distinct premium Passion ID against the existing profile and ownership mappings.
The new JustPic ID account uses the display name you confirm, the username and region you choose, and a password hash for your new backup password. The username determines your @justpic.id mailbox address. The migration links the verified Firebase UID and existing Passion ID/PPID to the new permanent JustPic UID. The legacy email address and other product data are not imported into the new account.
A migration record is written to Firebase and PostgreSQL with verification/completion status, identifiers, timestamps, and the confirmed display name. Migration-record-specific retention and cleanup periods are not yet configured or published; see the retention limits described in this notice.
JustPic Storage
The current Account Center storage foundation processes the files and file metadata you explicitly upload, including names, sizes, content types, folders, and timestamps. Storage is owned by your permanent JustPic UID and partitioned by the selected account region in the configured persistent data volume.
Authorized JustPic ID administrators can view account-linked storage metadata: JustPic UID, username, region, allocated quota, used and available bytes, file count, and storage status. The Admin Portal does not provide file names, previews, downloads, or file contents.
The current default quota is 5 GiB and is enforced against actual stored bytes. File deletion removes the active file and metadata; backup retention and account-level deletion require the operational retention and recovery procedures to be configured and verified.
JustPic ID app
If you link the JustPic ID mobile app, JustPic ID stores a device record: the platform, the device name you choose, the device's public signing key and its fingerprint, and when the device was linked, confirmed, last used, and revoked. App sessions, single-use request codes, and sign-in approvals or declines are recorded with the device so they can be checked and audited. Your Activity list in the app shows a subset of these security records.
Your security code, fingerprint or face data, and camera images stay on your phone and are never sent to JustPic ID. The camera is used only to read JustPic codes. When you approve a sign-in, the app shows the requesting website and browser so you can decide; JustPic ID does not store your location for this. You can remove JustPic ID from the phone in the app or revoke the device in the Account Center. Revoked device records remain as security records; a maximum retention period is not yet configured or published.
Sharing and regional processing
A complete user-manageable connected-app grant and identity-data delivery flow is not currently enabled in the Account Center. Registered clients and authentication challenge foundations do not by themselves mean a product is connected or receiving account data. Product-specific data remains with the relevant product.
The account region is recorded as an account setting and used as a logical storage partition. It does not establish separate regional hosting, database routing, backup location, or a data-residency guarantee.
Your choices
You can review your identity, mailbox status, and storage usage, edit your display name, manage active browser sessions and existing device records, and change your password using your current password in the Account Center. A password change keeps the requesting browser session and revokes other browser sessions. Device revocation stops that device from approving sign-ins and ends its app sessions; it does not erase data on the device or promise to terminate existing external mail connections.
The privacy contact page describes the current limitations of manual requests to access, correct, export, restrict, or delete account information, including enabled JustPic ID Mail and Storage. Contact delivery, monitoring and the manual review process are not yet verified. Retention schedules for sessions, challenges, audit records, active storage, and backups are not yet published; the deletion process must account for those categories and applicable security or legal exceptions.
Human Data and AI principles
The Human Data & AI Manifesto is a vision for the ecosystem, not a replacement for this notice. Its minimisation, no hidden profiling, and personal-data AI exclusion principles are not verified ecosystem-wide controls today.
Reference integrations include Google Vision processing of uploaded identity documents and a Gemini helper that accepts extracted identity-document text. Account-linked activity records also exist in reference code. This evidence does not establish which integrations are deployed, provider retention or training practices, or the processing of every independent product. Product owners must verify those facts before broader claims can be made.
This public-content update adds no AI processing, tracking, or new data collection. It does not change existing account, storage, authentication, or product processing.

