For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
  • Getting Started
    • Introduction
    • Getting Started
    • Tia — Operations Assistant
    • Architecture
    • Security Architecture
  • Onboarding & Plans
    • Onboarding Overview
    • Plans & Subscriptions
    • Tia Credits
  • Tenancy & Governance
    • Roles & Members
    • Audit Log
    • Notifications
    • Economic Operators
  • Authoring Studios
    • Content Studio
    • Theme Studio
    • Advanced Studio (Track B)
  • Product Module
    • Products
    • Custom Fields
    • Global Search
    • Identifiers
    • Product Import
    • Bulk Editing
    • Bulk Updates
    • Resolver & GS1 Digital Link
    • GS1 Digital Link Contract
  • Localisations
    • Overview
    • Market Packs
    • Multilingual Content
  • Domains & Custom Hostnames
    • Domain Architecture
    • Resolver Domain Flow
    • Custom Hostname Setup
    • DNS Setup Guide
    • Resolver & Passport Rendering
    • Custom Hostname Lifecycle
    • Troubleshooting
  • Passports
    • Overview
    • Passport Operations
    • Lifecycle States
    • Controlled Update & Break-Glass
    • Content & Templates
    • Themes & Presentation
    • Consumer Experience
    • Publication Lifecycle
    • Brand Setup & Readiness
    • Drafts
  • Passport Intelligence
    • Passport Intelligence
    • Intelligence Overview
    • Scan Visibility
    • Trust Signals
    • Engagement Insights
    • Investigation Timelines
    • Data & Privacy
    • Roadmap
  • Minting
    • Overview
    • Lifecycle
    • Architecture
    • Limits & Performance
    • Token Preview
    • Exports & Print Jobs
    • Carrier Output Profiles
    • Bring-Your-Own Serials
    • Security
    • FAQ
  • API Reference
    • API Credentials Guide
    • API: Credentials
    • API: Products
    • API: Identifiers
    • API: Import
    • API: Batches
    • API: Attachments
    • API: Bulk Updates
    • API: Minting
    • API: Resolver
    • API: Search
On this page
  • Brand-Scoped Access
  • Retention Posture
  • Identity Awareness Without Personal Profiling
  • Auditability
  • In Summary
Passport Intelligence

Data & Privacy

Was this page helpful?
Previous

Roadmap

Next
Built with

Passport Intelligence is designed to give operators useful visibility into Digital Product Passport activity without unnecessary personal exposure. This page summarises the privacy and governance posture customers and developers should be aware of.

Brand-Scoped Access

All Passport Intelligence surfaces are scoped to the active brand. Access to the workspace, signals, and investigation tools is governed by the platform’s role model. Sensitive operations — such as triggering a manual trust recompute — are restricted to authorised roles (typically Owner and Admin).

Retention Posture

Passport Intelligence applies finite, operationally appropriate retention windows.

DataPosture
Visitor IPsMasked after the defined retention window
Engagement eventsRetained for a finite period appropriate to operational use
Aggregated metricsRetained for trend analysis as part of the platform’s analytical model

The intent is to give operators a credible operational view while limiting unnecessary retention of identifying information.

Identity Awareness Without Personal Profiling

Passport Intelligence is identity-aware in the product sense — it knows about products, passports, batches, and lots — not in the consumer-profiling sense. Signals are interpreted against the platform’s own identity model rather than against individual consumer identities.

Auditability

Operations performed within Passport Intelligence — including manual recomputes and investigations — fit within the platform’s broader audit posture, supporting after-the-fact review where required.

In Summary

Passport Intelligence is built to be enterprise-safe by default: brand-scoped, role-aware, identity-aware, and conservative on personal data retention.