Vai al contenuto
Credenziale digitale Sistema fisico controllo degli accessi
Prodotto Sicurezza Settori Piani Domande frequenti
Accedi Inizia gratis
Accedi Inizia gratis

Documento legale · Credencial Digital

Terms and Conditions of Service

These terms govern access to and use of the digital credential and physical access control platform operated under the Credencial Digital brand. Please read them before creating an account, purchasing a plan or issuing a credential.

Versione: 2.0 Efficace da: 2026-10-25 Lingua: English

Sommario
  1. Operator and acceptance
  2. Definitions
  3. The Service
  4. Accounts and security
  5. Roles and responsibilities
  6. Plans, pricing and billing
  7. Payments and gateways
  8. Renewal, suspension and termination
  9. Refunds and withdrawal
  10. Acceptable use
  11. Personal data
  12. Intellectual property
  13. Third parties and integrations
  14. Security
  15. Availability and support
  16. Warranties and disclaimers
  17. Limitation of liability
  18. Indemnification
  19. Changes
  20. Governing law and disputes
  21. General provisions
  22. Contact
  23. Annex A — DPA
  24. Annex B — Subprocessors
  25. Annex C — Support

One-sentence summary. The platform is a B2B tool that lets an organization issue signed digital credentials and control physical access. The organization that subscribes decides whom to credential and which access to grant; Credencial Digital provides the infrastructure and does not replace the organization's decisions or issue official identity documents.

These Terms and Conditions of Service (the “Terms”) are a contract between you and the Operator and govern access to and use of the platform, websites, administration interfaces, mobile validation application, APIs and related services (together, the “Service”).

1. Operator and acceptance

1.1 Operator. The Service is operated under the Credencial Digital brand (the “Operator”, “we” or “us”). Notice address: the address stated in the applicable service order or contract. Legal contact: [email protected]. Privacy contact: [email protected]. Support: [email protected].

1.2 Acceptance. By creating an account, checking the acceptance box, purchasing a plan, issuing a credential or using the Service, you accept these Terms and the Privacy Policy. If you act on behalf of an organization, you represent and warrant that you have authority to bind it. If you do not agree, do not use the Service.

1.3 Form of consent. Consent may be given through checkboxes, acceptance buttons, service orders or electronic signature. The parties agree that electronic records and electronic signatures have the same force as written, signed documents to the extent permitted by applicable law (for example, the U.S. ESIGN Act, 15 U.S.C. § 7001, state electronic signature laws, Regulation (EU) 910/2014 —eIDAS— and local electronic signature and e-commerce laws). We retain the accepted version, its date, time, the text shown and reasonable technical evidence of acceptance.

1.4 Order of precedence. In case of conflict: (a) the signed service order or contract prevails; (b) Annex A (DPA) prevails for personal data; (c) these Terms; (d) the Privacy Policy; and (e) technical or commercial documentation. Mandatory provisions of applicable law prevail over any contrary term.

1.5 Capacity. Administrator accounts are intended for organizations and individuals aged 18 or older with legal capacity. Administrator accounts are not created for minors. The Entity is responsible for verifying the age, capacity and applicable legal basis for the Holders it onboards, including minors where its law permits.

2. Definitions

  • “Entity”: the legal person or organization that subscribes to the Service and issues credentials to its Holders.
  • “User”: any person authorized by the Entity to use the Service (administrator, manager, officer, auditor or other role).
  • “Holder”: the natural person to whom the Entity issues a digital credential.
  • “Credential”: the cryptographically signed digital record linking a Holder to an Entity, a role, a validity period and, optionally, a photograph stored on the platform.
  • “Personal Data”: any information relating to an identified or identifiable natural person.
  • “Controller” and “Processor”: as defined in the GDPR and applicable data protection laws; the Controller determines purposes and means, the Processor acts on the Controller's behalf.
  • “Subscription”: the plan and period purchased by the Entity to use the Service.
  • “Payment gateway”: the provider that processes payments, including Stripe (card and Stripe Connect), PayRam (self-hosted) and any other enabled by the Operator or the Entity. The platform does not custody third-party funds and does not operate as a payment institution.
  • “Cryptoasset”: the digital asset accepted as a means of payment by a Payment gateway, where enabled for the specific transaction.
  • “Sanctions”: applicable restrictive measures and sanctions lists, including OFAC (including the SDN List), the European Union, the United Kingdom, the United Nations and any other competent authority.
  • “Registration order”: a request to purchase a credential from an Entity in the public sales module.

3. The Service

3.1 Components. Depending on the plan, the Service includes: (a) a multi-entity web console to manage users, roles, access points, credentials and designs; (b) credential issuance with QR code and ECDSA P-521 digital signature; (c) a mobile validation application that can verify the signature offline with the Entity's public key; (d) access traceability and reports; (e) notifications, support and chat; and (f) an optional public credential sales module with payment through the configured gateway.

3.2 Nature of the Service. The Service is a technical identity management and access control tool. It is not an official identity document, does not by itself prove a person's civil identity and does not guarantee that a credential belongs to the person presenting it. The Entity is solely responsible for deciding whether to issue, renew, revoke or accept a credential and whether to allow or deny access.

3.3 Offline validation. The mobile application can verify the cryptographic signature and validity of a credential offline using a previously downloaded public key. In that mode, revocation, Entity suspension or later changes may not be reflected immediately. The Entity must define fallback procedures and human review for those cases.

3.4 Plan limits. The Operator defines and publishes the plan catalog and the glossary of applicable limits (active credentials, officers, managers, access points, design projects and retention periods). On subscription, the then-current plan content is frozen in a snapshot of the Entity and the Service enforces those limits server-side. Later changes to the catalog do not alter a plan already purchased: they take effect on upgrade or renewal. The Entity is responsible for choosing a plan suited to its operations and for reviewing the current catalog before renewing.

3.5 Public sales module. If the Entity enables the public sales module, it acts as the seller of its own credentials. Credencial Digital only provides the registration infrastructure, the integration with the chosen gateway and credential issuance. The Entity sets prices, quotas, terms, refund policy, taxes and consumer support.

3.6 International scope and restrictions. The Service is available internationally, except: (a) countries, territories and regions subject to comprehensive Sanctions, which are not admitted; (b) persons and entities on Sanctions lists or subject to export controls; (c) where the Payment gateway cannot lawfully operate in the customer's or Entity's country; and (d) where local law requires licences, registrations or conditions that the Operator does not meet. Actual availability depends on the plan, the enabled gateway and Sanctions screening. We may reject or cancel an order and refund the amount where collection or performance cannot lawfully take place.

4. Accounts and security

4.1 Accurate information. You must provide accurate, complete and current information and keep it up to date. The Entity warrants that it has the legal basis and authorizations to onboard its Users' and Holders' data.

4.2 Access credentials. Each User must keep passwords, 2FA codes and devices confidential. Sharing accounts or bypassing access controls is prohibited. The Entity must promptly deactivate accounts of persons who are no longer authorized.

4.3 Authentication. The Service may use Firebase Authentication (Google) as its primary identity provider and two-step verification (TOTP). The Entity and Users accept the provider's terms as applicable to them.

4.4 Incidents. If you suspect unauthorized access, a data breach or misuse, notify us immediately at [email protected] and, where personal data is affected, at [email protected]. Notification does not relieve the Entity of its legal obligations as Controller.

4.5 No administrator accounts for minors. Administrator accounts may not be created for persons under 18. Minor Holders may be onboarded only when the Entity has the legal representative's authorization, a valid legal basis and the safeguards required by its law.

5. Roles and responsibilities

5.1 The Entity as Controller. For the data of its Users, Holders, access events and credentials, the Entity is the Controller. Credencial Digital acts as Processor, except for processing inherent to the commercial relationship (account, billing, security and communications), where it acts as Controller.

5.2 Entity obligations. The Entity must: (a) inform Holders and Users about the processing; (b) identify a legal basis; (c) obtain consent where required; (d) handle data subject rights; (e) avoid sensitive or special categories without a legal basis and adequate safeguards; (f) define access policies and human review; and (g) comply with applicable labor, education, consumer and sectoral law.

5.3 Access decisions. Decisions to allow or deny access belong to the Entity. The Service only verifies the integrity and validity of the credential and records the event. The Entity must not base decisions producing legal or similarly significant effects on a person solely on automated validation; it must provide human review and a complaint channel.

5.4 Users and roles. The Entity manages its Users and internal roles. Credencial Digital does not control the hierarchy, permissions or instructions configured by the Entity, except for technical restrictions of the Service.

5.5 Multi-entity Holders. A Holder may have credentials from several Entities. Each Entity may only see and manage its own data and credentials. Removal from one Entity does not affect credentials from the others.

5.6 Operator's own processing. For account, billing, platform security, fraud prevention and service communications data, the Operator acts as Controller and determines its own purposes and means. For Holder and operational User data, the Operator processes only for the purposes instructed in Annex A. If the Operator processes that data for its own purpose, it will rely on its own legal basis and document it, without prejudice to Article 28(10) GDPR.

6. Plans, pricing and billing

6.1 Catalog and currency. Current plans, limits, prices and discounts are published at /planes/. The reference price is expressed in United States dollars (USD). Where the enabled gateway charges in a Cryptoasset, the amount, applied quote, network and fees are shown before confirming the transaction. Prices exclude taxes and gateway fees unless stated otherwise.

6.2 Free trial. The Free or trial plan lasts for the period stated in the catalog (by default, 7 days) and may be feature-limited. At the end, the Entity must purchase a paid plan to continue using plan-gated features. The trial does not automatically convert into a paid subscription.

6.3 Periods and plan freeze. Periods are monthly (30 days), quarterly (90), semi-annual (180) and annual (365). The period price is calculated using the published formula and frozen in the payment order. The content of the purchased plan —price, limits and features— is frozen in the Entity's snapshot at the time of purchase. Catalog changes do not affect the current plan: they apply on upgrade or renewal, which follow the catalog in force on that date.

6.4 Billing. The Operator is the seller of the Subscription purchased by the Entity. The Entity receives the plan, period, amount, currency and payment reference. The proof of payment is the record of the gateway that processed the transaction and, where applicable, the Service's internal record. Tax invoicing will be issued according to the Entity's and the Operator's jurisdiction; the Operator may request the tax or VAT identification number and apply the reverse charge where applicable. The Entity is responsible for its own taxes and for invoicing the charges of its public registration.

6.5 Plan changes. Upgrades may generate a credit for unused time, calculated under the published policy, and apply the catalog in force at the time of the change. Downgrades apply at the end of the period or under the catalog rules. Until an upgrade or renewal occurs, the Entity retains the plan content frozen in its snapshot, even if the catalog changes.

6.6 Non-payment. If payment is not received by the due date, the Service may suspend features, retain data and apply a grace period. Suspension does not eliminate the debt or the Entity's obligations.

7. Payments and gateways

7.1 Platform subscriptions (B2B). The Operator configures the Payment gateway for its own subscriptions, which may be Stripe and/or PayRam. Depending on the enabled gateway, collection is made in USD or in the Cryptoasset accepted by the gateway. Payment is deemed received when the gateway confirms it and the Service validates the reference, amount, currency and corresponding account.

7.2 Cryptoassets. Where Cryptoasset payment is enabled: (a) the reference price is the published USD price and the gateway shows the quote and exact amount before confirmation; (b) the Operator does not custody, exchange or transfer Cryptoassets on behalf of third parties and does not provide exchange or custody services; (c) the transaction may be irreversible and is subject to network confirmations, fees, congestion and volatility; (d) the risk of a transfer to an incorrect address or network lies with the payer; (e) we may require additional verification and apply Sanctions screening before crediting payment; and (f) the record is the gateway's record and the Service's internal reference.

7.3 Entity public sales (B2C). In the public sales module, the Entity configures and operates its own Payment gateway, isolated per Entity, through Stripe Connect Standard or its PayRam server; one Entity's credentials are not shared with another. The Entity charges directly into its own account and may do so in USD or in the Cryptoasset accepted by its gateway. Credencial Digital does not custody or process those funds, is not the seller and does not receive the credential price. The Entity is solely responsible for the consumer relationship, refunds, taxes, Sanctions compliance and the law of its jurisdiction.

7.4 Payment verification. The Service validates payment against the reference, the amount, the currency and the account of the corresponding gateway. If payment does not match or arrives late, the order is flagged for the Entity's review. The Entity must manually resolve doubtful cases and must not promise automatic crediting in every scenario.

7.5 Irreversibility. As regards the gateway, transactions it processes may be irreversible under its rules and those of the network it uses. The platform cannot cancel or reverse them. The Entity bears the risks the gateway attributes to it, including price, volatility, congestion and fees.

7.6 Compliance and Sanctions. The Entity and the Operator must comply with applicable anti-money laundering, counter-terrorist financing, Sanctions and export control laws. The Service may not be used from or for countries, territories, regions or persons subject to comprehensive Sanctions, or to evade Sanctions, conceal the origin of funds or conduct prohibited activities. We may request reasonable information, apply identity verification and suspend or reject suspicious operations, refunding the amount where appropriate.

7.7 Payment data. We do not store full card numbers or CVV codes. Payment data is processed by the relevant gateway. We retain references, amounts, currencies, statuses and the last four digits where the gateway provides them, for reconciliation and audit; we never store full card numbers, CVV codes or plaintext secrets.

8. Renewal, suspension and termination

8.1 Renewal. Unless the order provides for automatic debit, renewal requires manual payment. The Service may send reminders before expiry. If payment is not made, the Entity becomes delinquent or suspended and loses access to features, without prejudice to data retention required by law and the Privacy Policy.

8.2 Cancellation by the Entity. The Entity may cancel renewal from the console or in writing. Cancellation does not refund the current period unless mandatory law requires otherwise. The Entity should export its data before termination.

8.3 Suspension by the Operator. We may suspend or limit the Service if: (a) payment is overdue; (b) there is a security risk; (c) these Terms, Sanctions or the law are breached; (d) an authority requires it; or (e) necessary to protect third parties. Where reasonable, we will notify before or promptly after.

8.4 Termination. Either party may terminate for material breach not cured within 30 days of notice. We may terminate immediately for illegal use, fraud, Sanctions or serious risk. Termination does not affect accrued obligations.

8.5 Effects. For 30 days after termination, the Entity may request a copy of the data available in the Service (credentials, reports and exportable records). Afterwards, data will be deleted or anonymized in accordance with the Privacy Policy and legal retention obligations. Backups rotate on the published schedules.

8.6 Survival. Intellectual property, confidentiality, personal data, limitation of liability, indemnification, governing law and other provisions that by their nature should survive will survive termination.

9. Refunds and withdrawal

9.1 General B2B rule. Unless mandatory law requires otherwise or there is an error attributable to us, subscription payments are non-refundable. No refunds are given for partial periods, unused features or unused credits.

9.2 Exceptions. We will review in good faith refunds for: (a) duplicate charge; (b) unauthorized charge; (c) serious technical failure attributable to the Service that prevents essential use for a significant period; and (d) legal requirement. Refunds will be made by the same means where possible.

9.3 Cryptoasset payments. Cryptoasset payments are final. Where the law requires a refund, it will be made in USD or, if the payer agrees and the gateway permits, in the same Cryptoasset, net of network and gateway fees. The reference value is the amount actually received and settled, not a later quote.

9.4 Consumers. Where a Holder purchases a credential from an Entity and the consumer law of their country provides a withdrawal or refund right, that right is exercised against the selling Entity. Credencial Digital is not the seller of that credential and cannot replace the Entity's decision, although it will reasonably assist with communication.

9.5 Chargebacks. If a chargeback or reversal is initiated, we may suspend the Service while investigating and request proof of payment. The Entity will reimburse reasonable investigation costs if the chargeback is unfounded.

10. Acceptable use

The Entity and Users must not use the Service to:

  • Impersonate identities, forge credentials, alter signatures, QR codes or access records.
  • Access systems, accounts, data or facilities without authorization.
  • Issue credentials with false data or without consent or legal basis.
  • Process sensitive or special categories without a legal basis and adequate security measures.
  • Conduct mass surveillance, non-consensual facial recognition, covert biometrics or invasive profiling.
  • Make employment, credit, housing, insurance, education, health or public benefits decisions based solely on automated validation, without human review and legal safeguards.
  • Discriminate on prohibited grounds or use a credential to deny fundamental rights.
  • Scrape, reverse engineer, decompile or circumvent technical or security limits.
  • Introduce malware, spam, illegal content or material that infringes third-party rights.
  • Use the Service from or for countries, territories, regions or persons subject to comprehensive Sanctions, or in violation of export control laws.
  • Conduct regulated financial activities without the required licenses or registrations.
  • Allow use by minors without applicable authorizations and safeguards.

We may investigate and suspend conduct that puts the Service, Holders or third parties at risk, and cooperate with competent authorities.

11. Personal data

11.1 Privacy Policy. The Privacy Policy forms part of these Terms and describes data categories, purposes, legal bases, recipients, transfers, retention and rights.

11.2 DPA. Where the Entity acts as Controller and Credencial Digital as Processor, Annex A (Data Processing Agreement) applies. If the Entity requires the EU Standard Contractual Clauses, they are incorporated by reference and prevail in case of conflict.

11.3 Instructions and own purposes. The Entity instructs the Operator to process its Holder and operational User data for the purpose of providing the Service. The Operator will not use that data for its own purposes other than platform security, strictly necessary fraud prevention and legal compliance, and where it does so it will identify its legal basis and document it. For account, billing and communications data, the Operator is Controller and does not act on the Entity's instructions. We do not use data for third-party advertising or sell it.

11.4 Subprocessors. The Entity authorizes the subprocessors listed in Annex B. We will notify material changes at least 30 days in advance and provide an opportunity to object on reasonable grounds.

11.5 Rights. The Entity is the contact point for Holder rights. If a data subject contacts us directly, we will refer them to the Entity and reasonably assist with the response.

11.6 Incidents. We will notify the Entity without undue delay and, where possible, within 48 hours of becoming aware of a security breach affecting its data, with the information reasonably available and the measures taken. Notification to the supervisory authority and data subjects is the Entity's responsibility as Controller.

12. Intellectual property

12.1 Ownership. The Service, its code, design, trademarks, documentation, databases and improvements are owned by Credencial Digital or its licensors. No ownership is transferred under these Terms.

12.2 License. We grant the Entity a limited, non-exclusive, non-transferable and revocable license to use the Service during the Subscription, in accordance with these Terms and the purchased plan.

12.3 Entity data. The Entity retains ownership of its data, content, designs and trademarks. It grants us a limited license to host, process, display and back up them for the purpose of providing the Service.

12.4 Feedback. If you send suggestions or comments, we may use them freely to improve the Service, without compensation or attribution.

12.5 Restrictions. You may not copy, modify, distribute, sell, sublicense, decompile, reverse engineer or create derivative works of the Service, except with written authorization or mandatory legal permission. Open-source licenses are governed by their own terms and identified in the documentation.

12.6 Trademarks. “Credencial Digital” and associated logos are trademarks of the Operator. The Entity may not use them without authorization, except to identify the Service in its internal operations.

13. Third parties and integrations

The Service integrates external providers, including Firebase Authentication (Google), Resend (email), Cloudflare (network, tunnel, inbound email and bot verification), Backblaze B2 (encrypted backups), Stripe and PayRam (payments), Sentry (error diagnostics, if enabled) and the gateway configured by the Entity. These providers have their own terms and policies. We are not responsible for their acts, omissions or availability, although we select reasonable providers and apply contractual and technical measures.

Support chat machine translation may run in the user's browser through Google Translate. The text is sent to the provider from the browser; we do not store the translation on the server. The Entity must inform its Users about this feature.

14. Security

14.1 Measures. We apply reasonable technical and organizational measures appropriate to the risk, including encryption in transit, 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 and incident management.

14.2 Limits. No system is completely secure. We do not warrant that the Service will be immune to attacks, errors or interruptions. The Entity must apply its own controls, train its Users and keep its devices and credentials secure.

14.3 Credential content. A credential's 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. The Entity must limit the diffusion of the credential, collect only necessary data and obtain applicable authorizations.

14.4 Audit. We may audit use of the Service to verify compliance and security. The Entity will reasonably cooperate and retain records required by law.

15. Availability and support

15.1 Reasonable efforts. We provide the Service with commercially reasonable efforts and maintain maintenance windows. We do not guarantee a specific availability level unless a service order or written SLA establishes one.

15.2 Support. Support is provided through the enabled channels (tickets, chat and email to [email protected]). The first-response time is 24 to 72 business hours, unless the plan or a written agreement states otherwise. Critical security or availability incidents are prioritized. Support does not include custom development or legal, tax or compliance consulting.

15.3 Maintenance. We may perform scheduled and emergency maintenance. Where possible, we will give advance notice and minimize disruption.

16. Warranties and disclaimers

16.1 Limited warranty. We warrant that the Service will be provided materially in accordance with the documentation and with reasonable professional diligence. If we breach this warranty, the Entity must notify us and we will have the opportunity to cure. If we fail to cure, the Entity may terminate and receive a pro rata refund of the unused period.

16.2 Disclaimer. Except for the limited warranty and to the maximum extent permitted by law, the Service is provided “as is” and “as available”. We disclaim implied warranties of merchantability, fitness for a particular purpose, non-infringement and accuracy. We do not warrant that the Service will be error-free, that every validation will be correct or that it will prevent all unauthorized access.

16.3 No advice. The Service does not provide legal, tax, compliance or security advice. The Entity is responsible for assessing its own compliance.

17. Limitation of liability

17.1 Cap. To the maximum extent permitted by law, each party's total liability for claims arising out of these Terms will not exceed the total amount paid or payable by the Entity to the Operator in the 12 months preceding the event giving rise to the claim. For the Free plan, the cap is USD 100.

17.2 Exclusion. Neither party will be liable for indirect, incidental, special, punitive, consequential damages, loss of profits, revenue, data, goodwill or business interruption, even if advised of the possibility.

17.3 Exceptions. Nothing in this section limits: (a) liability for fraud, gross negligence or willful misconduct; (b) indemnification obligations; (c) breach of confidentiality or data protection; (d) intellectual property infringement; (e) mandatory consumer rights; or (f) any liability that cannot be limited by law.

17.4 Risk allocation. The parties acknowledge that these limitations reflect the allocation of risk and that prices were set with them in mind.

18. Indemnification

18.1 By the Entity. The Entity will indemnify and hold the Operator harmless from third-party claims arising from: (a) its data, content or instructions; (b) use of the Service by its Users; (c) breach of law, Sanctions or these Terms; (d) Holder or consumer claims relating to issuance, price, refund or access; and (e) infringement of third-party rights.

18.2 By the Operator. The Operator will indemnify the Entity from third-party claims alleging that the Service, as provided by us, infringes intellectual property rights. This obligation does not apply if the claim arises from the Entity's data, designs, trademarks or modifications, or from unauthorized use.

18.3 Procedure. The indemnified party must notify promptly, allow control of the defense and reasonably cooperate. No settlement imposing non-indemnified obligations will be made without consent.

19. Changes

We may modify these Terms for legal, technical or commercial 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 at least 30 days in advance, unless law or a security emergency requires a shorter period. Where the law requires express consent, we will obtain it before the change takes effect. If you do not agree, you may terminate before that date.

20. Governing law and disputes

20.1 Governing law. Unless a mandatory rule provides otherwise, these Terms are governed by the laws of Estado de Delaware, Estados Unidos de América, without regard to conflict-of-laws rules. If a competent court finds that choice unenforceable, the law of the Operator's domicile will apply, without prejudice to mandatory rules protecting consumers.

20.2 B2B arbitration. Any dispute between the Operator and an Entity not resolved amicably within 30 days will be submitted to binding arbitration administered by the American Arbitration Association (AAA) under its Commercial Rules, seated in Condado de Miami-Dade, Florida, Estados Unidos de América, in Spanish or English. The award will be final and enforceable. The parties waive a jury trial and participation in class actions, to the extent permitted by law.

20.3 Exceptions. Either party may seek interim relief, protect intellectual property or collect debts in court. Consumer disputes will be resolved under the mandatory law of the consumer's domicile and before the competent courts of that domicile. EEA and UK users retain the protections of their national law.

20.4 Prior notice. Before starting an action, the party must send a written notice describing the dispute and the requested remedy to [email protected].

21. General provisions

  • 21.1 Assignment. The Entity may not assign these Terms without our written consent. We may assign them in a merger, acquisition or sale of assets, with notice.
  • 21.2 Entire agreement. These Terms, the Privacy Policy, the DPA and service orders constitute the entire agreement and supersede prior communications.
  • 21.3 Severability. If a clause is invalid, it will be modified to the minimum extent necessary and the remainder will remain in effect.
  • 21.4 No waiver. Failure to exercise a right is not a waiver.
  • 21.5 Notices. Notices will be sent to the Entity's registered email and to [email protected]. They are deemed received on the next business day after sending.
  • 21.6 Force majeure. Neither party is liable for delays due to causes beyond its reasonable control, including disasters, conflict, network failures, cyberattacks or acts of authority.
  • 21.7 Independence. The parties are independent contractors; no partnership, agency or employment relationship exists.
  • 21.8 Language. The Spanish and English versions have equal value. In case of discrepancy, the Spanish version prevails, unless applicable law requires otherwise or a consumer is entitled to the version in their language.
  • 21.9 Survival. Provisions that by their nature should survive will survive.
  • 21.10 Electronic records. The parties accept the use of electronic means for the formation, performance and retention of the contract.

22. Contact

For questions about these Terms: [email protected]. For privacy and data rights: [email protected]. For technical support: [email protected].

Annex A — Data Processing Agreement (DPA)

A.1 Parties and roles. The Entity is the Controller and Credencial Digital is the Processor for personal data processed to provide the Service. The Operator is the Controller for account, billing, security and its own communications data.

A.2 Subject, duration and purpose. The processing covers the provision of the Service: hosting, credential issuance and validation, access control, traceability, support, security and billing. It lasts for the contractual relationship and applicable retention periods.

A.3 Data categories and data subjects. Users (name, surname, email, role, authentication data, IP, user agent), Holders (name, surname, email, role, optional photograph, credential, validity dates and access records) and Buyers in the public module (order data, amount, currency, payment reference and IP). The photograph is processed automatically to detect and crop the face; no biometric templates are extracted and it is not compared with other images. Special categories are not contemplated, unless the Entity introduces them under its responsibility, in which case it must identify, justify and apply the additional safeguards required by law.

A.4 Processor obligations. The Processor: (a) processes data only on documented instructions from the Entity, including transfers to third countries, unless applicable law requires otherwise; (b) ensures confidentiality of authorized personnel; (c) applies appropriate security measures; (d) assists the Entity with data subject requests and impact assessments; (e) notifies security breaches; (f) does not subcontract without authorization; (g) returns or deletes data on termination; and (h) makes reasonable information available to demonstrate compliance.

A.5 Subprocessors. The Entity grants general authorization for the subprocessors in Annex B. The Processor imposes equivalent obligations and remains responsible for their performance. It will notify any intended change at least 30 days in advance and allow objection on reasonable grounds; if the objection is not resolved, the Entity may terminate the affected Service without penalty.

A.6 International transfers. Where data is transferred outside the EEA, the UK or Switzerland, the EU Standard Contractual Clauses (Decision 2021/914), the UK International Data Transfer Addendum or an equivalent mechanism will apply, together with impact assessments and supplementary measures where necessary.

A.7 Security breaches. The Processor will notify the Entity without undue delay and, where possible, within 48 hours of becoming aware, with the available information. The Entity, as Controller, is solely responsible for notifications to the supervisory authority and data subjects under applicable law.

A.8 Audit. The Processor will allow reasonable audits, with prior notice and without affecting the security or confidentiality of other customers. It may provide certifications, reports or questionnaires as an alternative.

A.9 Return and deletion. On termination, the Processor will return or delete data as instructed by the Entity, unless law requires retention. Backups rotate and are deleted on the published schedules.

A.10 Liability. Each party is liable under applicable law. The Processor is liable for breach of its obligations and those of its subprocessors.

A.11 Own purposes. If the Processor processes Entity data for its own purpose (for example, fraud prevention or platform security), it will rely on its own legal basis and act as controller for that processing, in accordance with Article 28(10) GDPR, and will document it in its record of processing activities.

Annex B — Subprocessors

Single list of providers that may process personal data to deliver the Service. It supersedes any prior list and is updated with notice when it changes materially.

ProviderFunctionLocation / transfer
Google Firebase AuthenticationAuthentication and identityUSA; SCC / DPF
Resend (Amazon SES)Transactional email and deliverabilityUSA; SCC
CloudflareNetwork, tunnel, edge protection and bot verification (Turnstile)Global; SCC
Cloudflare Email RoutingInbound email routingGlobal; SCC
Google (Gmail)Contact email receiving and reply mailboxUSA; SCC / DPF
Backblaze B2Encrypted offsite backupsUSA; SCC
StripePayment processing for the platform and the EntityUSA / global; SCC
PayRamSelf-hosted payment gatewayOperator or Entity infrastructure, depending on the flow; SCC where applicable
Sentry (optional)Error diagnosticsUSA; SCC
Google Translate (client)Chat translation in the browserText is sent from the user's browser

Annex C — Support and service levels

C.1 Channels. Tickets, chat within the console and email to [email protected]. Support is provided in Spanish and English.

C.2 Response target. First response between 24 and 72 business hours. Critical security or availability incidents are prioritized.

C.3 Scope. Support covers use of the Service, reproducible errors and functional questions. It does not cover custom development, non-agreed data migrations, legal, tax or compliance consulting, or problems caused by third parties or the Entity's environment.

C.4 SLA. No availability SLA is offered unless a written service order establishes one. Scheduled maintenance windows do not count as unavailability.

C.5 Escalation. The Entity will designate a technical contact and a commercial contact. Critical incidents will be communicated through the support channel and, if available, the agreed emergency contact.

Notice. This document is an operational version and does not constitute individual legal advice. Before using it in a regulated market, the Entity should review its suitability with a lawyer competent in its jurisdiction. The Operator will publish its registered name and address once the company is incorporated; until then, identification and the notice address are those stated in clause 1.1. Last updated: 2026-10-25.

© 2026 Credenziale digitale. Tutti i diritti riservati.

Supporto Contatto Privacy Termini

Cookie e privacy

Utilizziamo solo cookie essenziali per il funzionamento del sito. Non utilizziamo cookie pubblicitari o di misurazione. Scopri di più