Mobile-ID Privacy Policy v2.0
Effective 08/07/2026
Mobile-ID Sign points to the issued official policy and does not replace approved legal wording.
TRUST & ASSURANCE
Personal Data Protection
Define purpose, data categories, access, retention and responsibilities for the deployed service.
ON THIS PAGE
EVIDENCE REGISTER
Evidence & publication scope
Consent & purpose
Service-specific implementation
Purpose, categories and consent follow the applicable service/transaction.
Rights & retention
Official policy governs
Data-subject rights and retention must be read against the current official policy.
PERSONAL DATA
Privacy summary points to the current canonical policy
Mobile-ID Privacy Policy v2.0 is published as current from 08/07/2026 and describes cookie categories, collection/use purposes, retention, access/correction rights and contact details. Mobile-ID Sign does not duplicate the full policy and instead links to the canonical source.
PERSONAL DATA
Personal data follows the transaction context
Mobile-ID Sign links the Sign-specific summary to the current Mobile-ID privacy policy and the 2026 personal-data legal framework instead of duplicating legal text.
If the table is wider than its frame, scroll horizontally to see all columns; use arrow keys when the table region has focus.
| Area | Publication posture |
|---|---|
| Actor / role | Controller/processor responsibility depends on the scenario, contract and deployment. |
| Purpose | Collect/process only for defined service and business purposes. |
| Consent / legal basis | Separate identity, attribute sharing, signing authorization and marketing consent. |
| Retention | Retention is governed by product, evidence, contractual and legal requirements; do not publish an invented universal period. |
| Rights | Canonical corporate privacy policy provides the public rights/request channel. |
ASSESSMENT DETAIL
Data-processing roles by scenario
Controller/processor roles should not be fixed across every deployment. In an integration, the enterprise may determine the purpose and data of the business workflow; Mobile-ID may process data within the service scope; identity providers, CA/RSSP or billing providers have their own roles under contract and applicable law. Deployment documentation therefore identifies actors, purpose, data category, lawful/consent basis where applicable, retention, disclosure and rights handling for each flow.
If the table is wider than its frame, scroll horizontally to see all columns; use arrow keys when the table region has focus.
| Flow | Data to consider | Governance point |
|---|---|---|
| Identity/SSO | Identifier/session/result | Purpose, scope and session retention |
| ShareInfo | Requested attributes | Consent/authorization and minimization |
| Signing | Document/signing context/certificate reference | Necessity, retention and evidence |
| Support | Logs/diagnostic metadata | Access, redaction and retention |
| Billing | Customer/tax/payment/invoice references | Accounting/legal retention and access |
The website summarizes product context and links to the canonical Privacy Policy; legal/privacy wording is versioned and does not replace a customer-specific data-processing assessment.