The essentials. We do not sell your data, we do not use it for third-party advertising and we do not build commercial profiles. We process the data necessary to provide the credential and access control service, for security and to comply with the law. The organization that issues your credential is the primary controller of your data; Credencial Digital acts as processor and, for accounts and billing, as controller.
1. Who we are and scope
1.1 Controller. The Service is operated under the Credencial Digital brand (the “Operator”). Notice address: the address stated in the applicable service order or contract. Privacy contact: [email protected]. Legal contact: [email protected].
1.2 Scope. This Policy applies to the website, public landing page, entity registration, web console, mobile validation application, APIs, public credential sales module, support and communications. It applies internationally, subject to the Sanctions restrictions described in the Terms. It does not apply to third-party sites or services, including Entity pages or external providers.
1.3 Related documents. This Policy supplements the Terms and Conditions and Annex A (DPA) of those Terms.
1.4 Supervisory authority and representation. If the Operator is not established in the European Economic Area or the United Kingdom and offers the Service to data subjects there, it will appoint a representative under Article 27 GDPR and Article 27 UK GDPR and publish their identity and contact details in this section before directing its services to those markets. Until then, requests are handled at [email protected]. You may lodge a complaint with the supervisory authority of your country or region.
2. Our roles
2.1 Operator's own data. Credencial Digital is the controller for the data of the subscribing Entity, its administrators and business contacts, as well as billing, platform security and service communications.
2.2 Holder and operational User data. For the data of Holders and Users onboarded by the Entity (name, photograph, role, credential, access events), the Entity is the controller and Credencial Digital is the processor. The Entity decides what data is collected, for what purpose and to whom it is disclosed; we process it to provide the service and follow its documented instructions.
2.3 Public sales module. When a Holder purchases a credential from an Entity in the public sales module, the Entity is the seller, charges directly through its own gateway configured in isolation and is the controller. Credencial Digital provides the infrastructure, integrates the Entity's gateway and issues the credential; it does not receive the price and is not the seller or the primary controller of that consumer relationship.
2.4 Payment data. The platform does not store full card numbers, CVV codes or plaintext secrets. It retains payment references, amounts, currencies, statuses and the last four digits where the gateway provides them, for reconciliation and audit; complete data is handled by the chosen gateway.
3. Data we process
We process the following categories, depending on your role and use of the Service:
- Identification and contact: name, surname, email, language, role, entity, internal role, access points.
- Authentication and security: encrypted password or hash, Firebase UID, 2FA secret, sessions, last access, IP address, user agent, security events.
- Credential: credential UUID, SHA-256 hash, ECDSA P-521 signature, issuance and validity dates, status, design and, optionally, Holder photograph.
- Photograph: where provided, it is validated and automatically processed to detect a single sharp frontal face, crop it and store it on the platform. No biometric templates are extracted, no facial fingerprint is generated and it is not compared with other images.
- Access control: access point, date and time, result (allowed/denied), handshake hash, user UUID, additional event data and the officer device's public key.
- Payments and billing: plan, period, amount, currency, status, payment reference, gateway, invoice URL and dates.
- Public sales: name, surname, email, optional photograph, plan, validity dates, amount, currency, gateway and payment reference, IP, user agent and consent version/date.
- Support: subject, messages, attachments, delivery/read states, chat presence and feedback.
- Diagnostics: error events and technical data sent to Sentry if the Operator enables it.
- Bot verification: token and browser technical data processed by Cloudflare Turnstile when submitting the contact form, signing in, or completing a public registration.
4. Purposes and legal bases
We process data for the following purposes. Where the GDPR applies, we identify the legal basis in parentheses:
- Create and manage the account, provide the Service and issue credentials (performance of a contract, Art. 6(1)(b) GDPR; for Holder data, on the Entity's behalf under Art. 28).
- Process payments, invoice and maintain accounting records (contract and legal obligation, Art. 6(1)(b) and (c)).
- Security, fraud prevention, audit and incident response (legitimate interest, Art. 6(1)(f), supported by a documented balancing assessment, and legal obligation where applicable).
- Support and operational communications (performance of a contract and, for handling requests, legitimate interest, Art. 6(1)(b) and (f)).
- Sanctions compliance, anti-money laundering and authority requests (legal obligation, Art. 6(1)(c)).
- Service improvement and aggregate statistics (legitimate interest, Art. 6(1)(f), using aggregated or anonymized data where possible).
- Anti-bot verification of the contact form (legitimate interest in site security, Art. 6(1)(f)).
- Consent only for optional purposes separately notified (for example, commercial communications), which you may withdraw at any time. The photograph is not based on the Entity's consent: the basis is determined by the Entity as controller and, where required, the Holder's own consent is obtained.
We do not use data for decisions producing legal effects based solely on automated processing, or for third-party advertising. We do not sell personal data. When acting as processor, we do not set our own legal bases: we follow the Entity's instructions.
5. Cookies and similar technologies
We use cookies and local storage strictly necessary for the operation and security of the site. We do not use advertising cookies, cross-site tracking or third-party analytics. Your cookie notice preference is stored in your browser's local storage (cd_cookie_choice) and is not sent to the server.
The contact form, sign-in and public registration load Cloudflare Turnstile, an anti-bot mechanism that may set cookies or local storage and process browser technical data. It is an essential security service and is not used for advertising or profiling. The full table is in Annex II.
You can delete or block cookies in your browser settings. If you block essential cookies, you may not be able to log in, use the console or submit the contact form.
6. Recipients
We share data with providers that help us deliver the Service, under contracts and security measures:
- Google Firebase Authentication (authentication and identity).
- Resend (transactional email and deliverability).
- Cloudflare (network, tunnel, edge protection and Turnstile bot verification).
- Cloudflare Email Routing (inbound routing for support, privacy and legal email).
- Google (Gmail) (contact email receiving and reply mailbox, when configured).
- Backblaze B2 (encrypted offsite backups).
- Stripe and PayRam (payment processing for the platform and the Entity, depending on the flow and configuration).
- Sentry (error diagnostics, if enabled).
- Google Translate (chat translation in the browser, when the user enables it).
- The Entity that issues the credential, where applicable.
- Authorities, courts and advisers when required by law or necessary to defend rights.
We do not sell data or share it for behavioral advertising. The subprocessor list is in Annex III.
7. International transfers
The Service is hosted on third-party infrastructure located in the United States and, depending on the provider and configuration, may process data in other regions. The provider list and mechanisms are in Annex III. When we transfer data from the European Economic Area, the United Kingdom or Switzerland, we apply the EU Standard Contractual Clauses (Commission Implementing Decision (EU) 2021/914), the EU-U.S. Data Privacy Framework adequacy decision (Commission Implementing Decision (EU) 2023/1795) where the provider is certified, the UK International Data Transfer Addendum or another valid mechanism, together with assessments and supplementary measures where necessary.
For transfers from Latin America, we apply the contractual clauses and safeguards required by local law, or obtain consent where the law permits. Payment data is shared with the chosen gateway and may be accessible globally under its configuration.
8. Retention
We retain data for the time necessary for the purposes described and to comply with legal obligations. The main periods are:
| Category | Period |
|---|---|
| Account and Entity data | While the account is active and up to 30 days after termination; then deleted or anonymized. |
| Billing and receipts | Up to 7 years or the applicable legal period in the relevant jurisdiction. |
| Access traceability and audit | While the subscription is active, subject to the retention limit of the purchased plan (as of the date of this version: Free 7 days, Basic 90 days, Premium 365 days and Enterprise per the catalog). The limit is frozen in the Entity's snapshot at purchase; catalog changes do not apply until upgrade or renewal. After termination, 30 days and deletion, unless a legal obligation applies. |
| Unpaid public sales orders | Anonymized 30 days after expiry. |
| Payment gateway webhook events | Up to 365 days for reconciliation; not purged while a dispute or refund is open. |
| Support | While the ticket is open and up to 12 months after closure, unless a legal obligation applies. |
| Security and diagnostic logs | Up to 12 months, unless an incident requires longer retention. |
| Backups | Rotation under the published policy; securely deleted at the end of their cycle. |
Retention limits form part of the plan catalog defined and published by the Operator at /planes/. The content of the purchased plan is frozen in the Entity's snapshot at purchase: if the catalog changes, the current plan is not altered until upgrade or renewal. Backups rotate on limited schedules and are securely deleted. If the law requires retention of certain data, it will be kept blocked and processed only for that purpose.
9. Security
We apply reasonable technical and organizational measures, including encryption in transit (TLS), role-based access control, multi-entity isolation, two-step verification, audit logging, encryption of secrets and private keys with AES-256-GCM, ECDSA P-521 signatures, encrypted backups, vulnerability management and incident response.
Credential content. The QR code contains an internal Holder and credential identifier, name, surname, role, validity dates and the digital signature. It does not contain the photograph or contact data, and it is not encrypted, so it can be read by anyone who scans it. The photograph, where provided, is stored on the platform and displayed in the Entity's console; it does not travel in the QR code or in offline mode. Do not share the QR outside authorized channels. We do not store full card numbers or CVV codes.
If a security breach affects your data, we will notify the responsible Entity and assist it. Notification to authorities and data subjects is the Entity's responsibility as controller; where the Operator acts as controller of its own data, it will notify as required by law.
10. Your rights
Depending on your jurisdiction, you may exercise the following rights:
- Access: know what data we process and obtain a copy.
- Rectification: correct inaccurate or incomplete data.
- Erasure: request deletion when data is no longer necessary or processing is unlawful.
- Restriction: request that we suspend processing in the legal cases.
- Objection: object to processing based on legitimate interest.
- Portability: receive your data in a structured, machine-readable format.
- Withdraw consent at any time, without affecting the lawfulness of prior processing.
- Not be subject to automated decisions producing legal or significant effects, in the applicable legal cases.
- Complain to the competent data protection authority.
- Appeal a denied request, where your state law provides for it.
To exercise them, write to [email protected]. If your credential was issued by an Entity, contact it first; we will assist with the response. We may request reasonable information to verify your identity and will not charge for the request unless the law permits it and the volume is manifestly excessive. We will respond within the applicable legal period (generally one month, extendable by two further months where justified by complexity).
Account deletion. To request deletion of your SCAF VALIDATOR account and associated data, use the public account deletion form.
11. California and other U.S. states
California (CCPA/CPRA). If you reside in California, you have the right to: know the categories and specific pieces of personal information we collect; request deletion; request correction; opt out of the sale or sharing of personal information; limit the use of sensitive personal information; and not be discriminated against for exercising these rights. We do not sell or share personal information for cross-context behavioral advertising. We provide notice at collection and respond to requests within 45 days, extendable as permitted by law. You may exercise your rights at [email protected] or through an authorized agent.
Other states. If you reside in Virginia, Colorado, Connecticut, Utah, Texas, Oregon, Montana or another state with a comprehensive privacy law, you may have rights of access, correction, deletion, portability and opt-out of sale or targeted advertising, as well as appeal. We will handle requests under applicable law.
Sensitive information. We do not use the photograph for biometric identification or to infer protected characteristics. Automated processing is limited to detecting, validating and cropping the face for the credential. Where a law treats the photograph or access data as sensitive information, we will apply the corresponding safeguards and limitations.
12. Children
Administrator accounts are not intended for minors under 18 and we do not create them for minors. An Entity may onboard minor Holders (for example, students) where its law permits; in that case it must obtain authorization from their legal representatives, inform them about the processing and comply with applicable laws, including COPPA where relevant and, in the U.S. education context, FERPA and the written agreement it requires. If we detect minors' data without a legal basis, we will delete or block it.
13. Automated decisions and profiling
We do not build commercial profiles or make decisions producing legal effects on a person based solely on automated processing. Credential validation is a technical check of integrity, validity and permissions configured by the Entity; it does not assess merit, health, creditworthiness or conduct. Photograph validation is an automated quality control that may reject an image with no face, multiple faces or blur; it does not produce legal effects and can be retried. The Entity must ensure human review and a complaint channel where its access decisions may affect rights.
14. Changes
We may update this Policy for legal, technical or business changes. We will publish the new version with its effective date and a version identifier. If the change is material, we will notify Entities with an active subscription with reasonable advance notice and, where required by law, obtain express consent before the change takes effect. Continued use after the effective date does not replace consent where consent is required.
15. Contact and complaints
For questions, requests or complaints: [email protected]. You may also write to [email protected]. For technical issues: [email protected]. We will respond within a reasonable period and, where required by law, within one month. If you are not satisfied, you may complain to the data protection authority of your country or region.
Annex I — Data, roles, purposes and bases matrix
| Data | Operator role | Purpose | Legal basis | Retention |
|---|---|---|---|---|
| Name, surname, email, role, entity (administrators and contacts) | Controller | Account, billing, support | Contract (Art. 6(1)(b)) | Account + 30 days |
| Name, surname, email, role, entity (Users and Holders) | Processor (Art. 28) | Service performance under the Entity's instructions | Determined by the Entity; the Operator sets no own basis | Credential validity + plan period; 30 days after termination |
| Holder photograph | Processor (Art. 28) | Credential and visual verification in the console; automated detection and cropping | Determined by the Entity (contract or Holder consent, as applicable) | Credential validity + plan period |
| Credential, hash, signature, dates | Processor (Art. 28) | Issuance and validation | Determined by the Entity | Validity + plan period |
| IP, user agent, sessions, 2FA, Firebase UID | Controller (account) / Processor (Entity users) | Security and audit | Documented legitimate interest / Art. 28 | 12 months |
| Access events | Processor (Art. 28) | Traceability and reports | Determined by the Entity | Per plan (7/90/365/contract) |
| Payments and gateway references | Controller (subscription) / Processor (public sales) | Billing and reconciliation | Contract / legal obligation | 7 years |
| Tickets and attachments | Controller / Processor as applicable | Support | Contract / documented legitimate interest | 12 months after closure |
| Contact form: name, email, reason, message, IP and user agent | Controller | Handling support, privacy or legal requests | Documented legitimate interest (Art. 6(1)(f)) / pre-contractual steps (Art. 6(1)(b)) | 12 months |
| Turnstile token and technical data | Controller | Bot verification for the contact form, sign-in and public registration | Documented legitimate interest (Art. 6(1)(f)) | Not stored; verified in transit |
| Technical errors (Sentry) | Controller | Diagnostics and stability | Documented legitimate interest, with scrubbing | 12 months |
Annex II — Cookies and local storage
| Name | Type | Purpose | Duration |
|---|---|---|---|
sessionid | Essential | Maintain the authenticated session | 30 minutes |
csrftoken | Essential | CSRF protection | Session / 1 year |
django_language | Essential | Remember language | 1 year |
cd_cookie_choice (localStorage) | Essential | Remember cookie notice preference | Until browser data is cleared |
Cloudflare (__cf_bm or others) | Essential security | Bot mitigation and edge protection, if enabled | 30 minutes |
| Cloudflare Turnstile | Essential security | Bot verification for the contact form, sign-in and public registration | Session / per Cloudflare |
No advertising, third-party analytics, social media or cross-site tracking cookies are used.
Annex III — Subprocessors
| Provider | Service | Country / mechanism |
|---|---|---|
| Google Firebase Authentication | Authentication | USA — SCC / DPF |
| Resend (Amazon SES) | Transactional email | USA — SCC |
| Cloudflare | Network, security and bot verification (Turnstile) | Global — SCC |
| Cloudflare Email Routing | Inbound email routing | Global — SCC |
| Google (Gmail) | Contact email receiving and reply mailbox | USA — SCC / DPF |
| Backblaze B2 | Encrypted offsite backups | USA — SCC |
| Stripe | Payment processing for the platform and the Entity | USA / global — SCC |
| PayRam | Self-hosted payment gateway | Operator or Entity infrastructure, depending on the flow — SCC where applicable |
| Sentry | Error diagnostics | USA — SCC |
| Google Translate (client) | Chat translation in the browser | Text is sent from the user's browser |
Annex IV — Rights by jurisdiction
EU/EEA and UK: rights of access, rectification, erasure, restriction, objection, portability, withdrawal of consent and complaint to the supervisory authority. Basis: GDPR, UK GDPR and, where applicable, Article 27 representation.
United States: CCPA/CPRA in California (Cal. Civ. Code § 1798.100 et seq.); comprehensive laws in Virginia, Colorado, Connecticut, Utah, Texas, Oregon, Montana and other states. Rights of access, correction, deletion, portability, opt-out of sale/targeted advertising and appeal.
Latin America: Dominican Republic Law 172-13; Colombia Law 1581 and Decree 1377 of 2013; Brazil LGPD (Law 13.709/2018) and ANPD Resolution CD/ANPD No. 19/2024; Argentina Law 25.326; Peru Law 29733 and its Regulation (Supreme Decree 016-2024-JUS); and equivalent rules. They may recognize additional rights of access, rectification, cancellation and objection.
Canada: PIPEDA and provincial laws; rights of access, correction and withdrawal of consent.