Data processing agreement
Last updated 4 October 2026 · version 2026-10-04
The short version
- For organisations. When your organisation puts personal data about other people into QR codes, hosted pages or files, your organisation is the controller and we are its processor. This agreement sets out how we handle that data, as Article 28 of the GDPR requires.
- How to accept it. The owner or an admin of a workspace accepts it on behalf of the organisation in the workspace settings, under Privacy and data. We record who accepted which version and when.
- What we promise. We use the data only to run the service, on your instructions. We keep it in the EU, protect it, tell you about breaches, help you with requests from the people concerned, and delete it when you delete it.
- It adds to our terms. The Terms of service, section 7, already contain short processor terms that apply to everyone. This agreement replaces them for workspaces that accept it.
1. Parties
- The controller is the organisation named when this agreement is accepted ("you"), represented by the workspace owner or admin who accepts it. They confirm that they may accept it on the organisation's behalf.
- The processor is Página Comum, [REGISTERED ADDRESS], VAT number [NIF / VAT NUMBER], registered at [COMMERCIAL REGISTRY] ("we", "us"). Contact for this agreement: privacy@1codigoqr.com.
This agreement covers the workspace in which it is accepted. If this agreement and the Terms of service disagree about personal data that we process for you, this agreement prevails.
2. Subject matter and duration
- Subject matter: hosting, storing, showing and delivering the content of your workspace: QR codes and their destinations, hosted pages, uploaded files, folders, tags, designs, API keys and webhooks.
- Duration: from acceptance until the workspace is deleted or you stop using the service, plus the time needed to delete the data as described in section 9.
3. Nature and purpose of the processing
We store your workspace's content, show hosted pages to the people who scan your codes, redirect scans to your destinations, render QR code images, send webhooks to the endpoints you choose, and keep backups. We do this only to provide the service to you.
Anonymous scan statistics are not part of this agreement: we decide how they are collected, as our privacy policy explains, and they contain no personal data that we give you.
4. Types of personal data
The personal data that your members choose to put into the workspace. Typically:
- names, job titles, phone numbers, email and postal addresses, for example on contact cards (vCard) and hosted pages;
- photos, documents and other files you upload;
- links and text that may identify people.
The members' own account data (their names, email addresses and roles in the workspace) and the email addresses of people invited to it are not covered by this agreement. We process them as controller, to run their accounts and the workspace, as our privacy policy explains.
You must not put special categories of personal data (Article 9 GDPR) or data about criminal convictions (Article 10 GDPR) into the service unless you have a legal basis for it and have checked that our security measures are adequate for it.
5. Categories of data subjects
The people whose data your members put into the workspace, such as your staff, customers, contacts and suppliers.
6. Your instructions
We process the personal data only on your documented instructions. Your instructions are this agreement, the Terms of service, and the actions and settings your members choose in the workspace and through the API. Further instructions must be given in writing to privacy@1codigoqr.com and must be possible within the service.
If EU or Portuguese law requires us to process the data in another way, we will tell you before we do, unless that law forbids it. We will tell you straight away if we think an instruction breaks the GDPR or other data protection law.
7. Our obligations
We will:
- process the personal data only as described in section 6;
- make sure that everyone authorised to process the personal data has committed to confidentiality or is under a legal duty of confidentiality;
- take the technical and organisational security measures described in the annex, as Article 32 of the GDPR requires, and keep them up to date;
- respect the conditions for engaging sub-processors in section 8;
- help you, with appropriate technical and organisational measures and as far as possible, to answer requests from people who use their rights under Chapter III of the GDPR. The workspace export and the editing and deletion tools already let you do most of this yourself. If someone sends us such a request about personal data covered by this agreement, we will pass it on to you without undue delay and will not answer it ourselves unless you ask us to. Requests from members or invited people about their own account, membership or invitation concern data we hold as controller (section 4), and we answer those ourselves;
- help you meet your obligations under Articles 32 to 36 of the GDPR (security, notification of personal data breaches, data protection impact assessments and prior consultation), taking into account the nature of the processing and the information available to us;
- delete or return the personal data at the end of the processing, as described in section 9;
- give you the information you need to show that these obligations are met, and allow and contribute to audits, as described in section 11.
8. Sub-processors
You give us general written authorisation to engage the sub-processors listed on our sub-processors page. It shows each sub-processor's name, what it does, where it processes data and the safeguard for any transfer.
- We will announce a new or replacement sub-processor on that page at least 14 days before it starts processing personal data for you. Any workspace owner or admin can ask us to email them these announcements.
- You can object on reasonable data protection grounds by writing to privacy@1codigoqr.com within that period. We will then try to find a solution with you. If we cannot, you may stop using the service and delete the workspace, and this agreement ends.
- We impose on every sub-processor, by contract, data protection obligations that offer the same level of protection as this agreement. We remain responsible to you for their work.
9. Deletion and return
- While you use the service, your members can download the workspace's data at any time with the workspace export in the workspace settings, and delete codes, files and other content. Deleted content is removed straight away.
- When the workspace is deleted, we delete its personal data straight away, apart from our security log (see below). Short codes are kept only as retired codes without personal data, so that they are never given to anyone else.
- Our security log, which we keep as controller to protect the service, records important actions for 12 months. Its entries can include the names of deleted QR codes and the addresses of deleted webhooks, and they are deleted after that time.
- Copies in our hosting provider's backups disappear within 7 days.
- If EU or Portuguese law requires us to keep some data longer, we keep only that data, only as long as required, and only for that purpose.
10. Personal data breaches
We will tell you without undue delay, and where possible within 48 hours, after we become aware of a personal data breach that affects your workspace. We will email the owner and admins of the workspace and give them the information we have, as described in Article 33(3) of the GDPR: what happened, the categories and approximate number of people and records concerned, the likely consequences, and the measures taken or proposed. Where we do not have all of it at once, we will send it as it becomes available. We will help you notify the supervisory authority and the people concerned where you need to.
11. Information and audits
- On request, we will give you the information you need to check that we meet this agreement, such as descriptions of our security measures and our sub-processor agreements, where we may share them.
- If that information is not enough, you may have an audit done, at your own cost, by an independent auditor bound by confidentiality. Please give at least 30 days' notice. Audits take place at most once a year, during business hours and without disrupting the service, unless a supervisory authority requires otherwise or a personal data breach makes another audit necessary.
- Audits of our sub-processors' infrastructure take place through the certifications and reports that those providers publish.
12. International transfers
We store and process your workspace's personal data in the European Union and the European Economic Area. We do not transfer it outside the EU/EEA, except to the sub-processors listed on our sub-processors page that may access data from outside the EU, and only with the safeguards listed there: an adequacy decision such as the EU-US Data Privacy Framework, or the European Commission's Standard Contractual Clauses.
13. Liability, changes and law
- Each party's liability under this agreement follows the Terms of service and Articles 82 and 83 of the GDPR.
- We may update this agreement, for example when the law or our sub-processors change. The version is shown at the top of this page. The workspace settings then show that a new version is available, and an owner or admin can accept it. The version previously accepted stays in force until then, unless a change is required by law.
- This agreement is governed by Portuguese law. The courts named in the Terms of service have jurisdiction, without prejudice to the powers of the supervisory authorities.
Annex: technical and organisational security measures
Confidentiality and access control
- Access to a workspace only for its members, with roles (viewer, editor, admin, owner) checked on every page and API call. Objects of other workspaces answer "not found".
- Passwords hashed with Argon2. Optional two-factor authentication (TOTP) with recovery codes. Repeated failed sign-ins are blocked.
- API keys stored only as SHA-256 fingerprints. Webhook signing secrets encrypted at rest. Invitation links stored only as fingerprints.
- Staff access to production data only where needed to run the service, with the lowest level of access needed, and under confidentiality.
Integrity and transmission
- TLS on every connection, with HSTS. A strict Content Security Policy on every page.
- Webhook requests are signed. Uploaded images are re-encoded and their metadata removed; PDFs with scripts are rejected.
- A security audit log per workspace, kept for 12 months, with shortened network addresses only.
Data minimisation and pseudonymisation
- No IP addresses stored for scans; city-level location worked out in memory; visitor hashes keyed with a salt that is destroyed every day.
- Retention jobs delete data when it is no longer needed (for example raw scan records after 90 days and closed invitations after 30 days).
Availability and resilience
- Hosting, database and file storage in the EU (AWS Europe, Ireland), with server-side encryption at rest and daily backups kept for up to 7 days by the hosting provider.
- Health checks and error monitoring without personal data.
Testing and organisation
- Automated tests for every change, including access-control tests for every page and API call, and dependency security checks.
- A documented process for handling incidents and personal data breaches.
- Sub-processors chosen for their data protection guarantees and bound by data processing agreements.