Home

Legal

Privacy Policy

This Privacy Policy explains how PixelPassport handles information you provide, media processing, private media reference storage, and data retention.

Last Updated: September 27, 2026

1Information You Provide

You may provide information when you create an account, create passports, add metadata, seal media, record provenance events, create copyright records, and generate evidence packages. This includes the content you submit and the declarations you make about your media.

2Account Information

When you create an account, PixelPassport stores your email address and authentication information. Your account ID is used internally to associate passports and records with your account but is not exposed in public verification data, image metadata, or evidence packages.

3Media Processing

Image processing for stamping and reading metadata happens in your browser. When you create a PixelPassport, PixelPassport may also retain a private reference copy of the original media to support integrity verification, previously-seen recognition, future comparison, and owner retrieval. The reference copy is not exposed through public verification.

4Metadata

PixelPassport embeds provenance metadata into your media files using open standards (XMP, IPTC, EXIF). This metadata travels with the file and may include the Passport ID, creator declarations, AI involvement information, and seal references.

5Copyright Contribution Records

Copyright & Human Contribution Records store authorship, contribution, and rights information you provide. These records are owner-readable. Public verification only exposes fields you have explicitly allowed to be public. Private supporting notes are never exposed publicly.

6Evidence Package Metadata

When you generate an Evidence Package, PixelPassport stores minimal package metadata (package ID, hashes, and generation timestamp). The generated PDF and JSON files are delivered to you. Private fields are only included if you explicitly select them.

7Audit and Security Logs

PixelPassport maintains audit logs for sensitive operations such as sealing, provenance mutations, and authorization decisions. These logs do not store private prompts, signing keys, access tokens, passwords, or full image data. Audit logs are admin-readable only.

8Temporary Uploaded Files

Files you upload for stamping or reading may be processed temporarily in your browser. For passports you create, a private reference copy of the original media is stored as described in the Private Media Reference section below. Files uploaded only for reading or verification (not creating a passport) are not permanently stored.

9Private Media Reference Storage

When you create a PixelPassport, PixelPassport stores a private reference copy of the original uploaded media. This reference copy is used to provide integrity verification, previously-seen recognition, future media comparison, visual similarity analysis, reprocessing with improved recognition algorithms, and owner retrieval.

The private reference copy is owner-only by default. Only the authenticated passport owner may retrieve it. Public verification does not expose the original media. Evidence packages do not include the original media. Public copyright views do not expose the original media. Passport summaries do not leak storage identifiers.

PixelPassport also stores derived fingerprints and hashes (including SHA-256 and perceptual fingerprints) associated with the reference. These derived values are used for recognition and comparison without loading the full original file for every search.

Deleted-media retention follows the stated deletion policy. When you permanently delete a passport, PixelPassport denies media retrieval immediately and removes the reference record. PixelPassport does not claim permanent deletion of underlying storage bytes unless and until Base44 confirms deletion has completed.

PixelPassport uses reasonable technical and organizational safeguards to protect private media references. No system can guarantee absolute security.

10Public Verification Data

When a passport is set to public verification, certain fields are visible on the public verification page. Public verification only exposes sanitized fields that you have allowed to be public. Private prompts, account IDs, and internal metadata are never included in public verification data.

11Cookies and Local Storage

PixelPassport uses browser storage for authentication sessions and user preferences. See the Cookie & Tracking Notice for details about the categories used.

12Analytics

PixelPassport may use analytics to understand how the service is used. Analytics data is aggregated and does not include the content of your media, private prompts, or personal declarations.

13Service and Security Logs

Service logs record operational events needed to run and secure the service. These logs may include timestamps, operation types, and error information, but do not include private prompts, signing keys, or full media content.

14Data Retention

Passports, provenance events, seals, and copyright records are retained for the life of your account unless you delete them. Temporary processing data is retained only as long as needed for the operation. Audit and security logs are retained according to operational requirements.

15Deletion

You can delete passports and associated records. Deleting a passport hides it from public verification, prevents further mutations, and denies retrieval of the private media reference immediately. The private reference record is removed when you permanently delete a passport. Some data, such as audit logs, may be retained for security and operational purposes even after deletion. PixelPassport does not claim permanent deletion of underlying storage bytes unless and until deletion has completed.

16Third-Party Services

PixelPassport may use third-party services for infrastructure, authentication, and email delivery. These services have their own privacy practices. PixelPassport does not sell your data to third parties.

17Security

We use reasonable technical and organizational safeguards to protect your data. Private signing keys are stored server-side and never exposed in files or API responses. However, no system can guarantee absolute security.

18Children

PixelPassport is not intended for use by children under the age of 13 (or the minimum age in your jurisdiction). We do not knowingly collect information from children.

19International Users

If you access PixelPassport from outside the region where it is operated, your information may be transferred to and processed in that region. By using PixelPassport, you consent to such transfers.

20Policy Changes

We may update this Privacy Policy from time to time. Changes will be posted on this page with an updated revision date.

21Contact

For privacy questions, please use the Contact page. Privacy contact information will be published here when designated.