Privacy policy
Last updated 5 October 2026 · version 2026-10-05
The short version
- No account needed for static codes. What you type into the free generator is only used to draw the image. We do not store it.
- Accounts hold only what we need. Your email address, a securely hashed password, your settings, and the codes and files you create.
- Scans are counted without tracking. When someone scans a dynamic code, we use no cookies, no fingerprinting and no third-party scripts. We never store their IP address. Code owners only see anonymous daily totals.
- Teams see what they share. In a shared workspace, the members see each other's name, email address and role. When you leave, your name goes with you.
- Everything is free. No ads, no paid plans, and we never sell your data.
- Hosted in the EU. Our servers, database and file storage are in Ireland.
- You are in control. You can download all your data or delete your account at any time in your account settings.
- Questions? Write to privacy@1codigoqr.com.
Who is responsible for your data
Página Comum ("we", "us") runs https://1codigoqr.com. We are the controller of the personal data described in this policy, unless we say otherwise below.
- Address: [REGISTERED ADDRESS]
- Email for all privacy matters: privacy@1codigoqr.com
Write to that address for any question about this policy, about your data, or to use your rights.
There is one important exception. When you put personal data about other people into your QR codes (for example, a colleague's contact card), you decide what goes in and why. For that content, you are the controller and we are your processor. See "Content you put in your codes" below.
What we collect and why
When you visit the website
Every request to https://1codigoqr.com passes through our hosting provider, Heroku. Its routers log each request, including your IP address, the address you requested and the time. Heroku keeps these router logs for a short period. We do not forward them to any log storage service, so we do not keep them ourselves.
To protect the service from overload and abuse, we limit how many requests one visitor can make. For this we keep short-lived counters. Each counter is identified by a keyed hash (HMAC) of your network address, not the address itself. The counters are deleted within minutes to hours.
- Why: to deliver the website and protect it from abuse.
- Legal basis: our legitimate interest in running a secure and reliable service (Art. 6(1)(f) GDPR).
We do not use analytics or advertising tools anywhere on the website. Our cookie policy lists the few cookies we use.
When you use the free generator without an account
You can create static QR codes without an account. The content you type (for example a link, a text or WiFi details) and any logo you add are processed only in memory to draw the image. The image is sent back to your browser. We do not store the content, the logo or the image.
A static code contains your content directly. Scanning it does not involve our servers, so we cannot see or count those scans.
- Why: to create the QR code you ask for.
- Legal basis: providing the service you request (Art. 6(1)(b) GDPR). The rate-limit counters described above are based on our legitimate interest in preventing abuse (Art. 6(1)(f) GDPR).
When you create an account
You need an account to create dynamic QR codes. For your account we store:
- your email address and whether you have verified it;
- your password, stored only as an Argon2 hash, so we cannot read it;
- your name, if you choose to give it;
- your language and time zone;
- your two-factor authentication secrets and recovery codes, if you turn on two-factor authentication;
- the passkeys you add: the name you give each one, its public key and when it was added and last used. The private key and any fingerprint or face data never leave your device;
- whether you want emails about new sign-ins;
- which version of the Terms of service and of this privacy policy you accepted, and when.
You can sign in with your password, with a one-time code that we send to your email address, or with a passkey.
- Why: to create and run your account and let you sign in securely.
- Legal basis: performance of our contract with you (Art. 6(1)(b) GDPR). We also keep the acceptance records because we have a legitimate interest in being able to show what you agreed to (Art. 6(1)(f) GDPR).
- How long: until you delete your account. If you never verify your email address, we delete the account after 30 days.
The human check on the sign-up page
To stop automated sign-ups, the sign-up page may ask you to complete a human check. By default we use Cloudflare Turnstile, provided by Cloudflare, Inc. When the sign-up page loads, the check runs in your browser, and Cloudflare receives your IP address and information about your browser and device. Cloudflare may set its own strictly necessary cookies. We only receive the result of the check. We use the human check only on the sign-up page.
- Why: to protect the service and its users from automated abuse.
- Legal basis: our legitimate interest in preventing abuse (Art. 6(1)(f) GDPR).
If you cannot complete the check, write to hello@1codigoqr.com and we will help you create an account.
Keeping your account secure
We keep a security log of important events, such as sign-ups, sign-ins, password and email changes, two-factor authentication changes, API key and webhook changes, deleted codes and data exports. Each entry holds the action, the time and a shortened network prefix: the first three parts of an IPv4 address (/24) or the first 48 bits of an IPv6 address (/48). We never store your full IP address in this log.
To block attempts to guess passwords, we record failed sign-in attempts together with the email address that was used, a shortened network prefix and basic technical details of the request, such as the browser's user agent. We delete these records after 24 hours.
- Why: to protect your account, detect misuse and investigate security problems.
- Legal basis: our legitimate interest in keeping accounts and the service secure (Art. 6(1)(f) GDPR).
- How long: security log entries for 12 months, failed sign-in records for 24 hours.
Where you are signed in, and new sign-in alerts
When you sign in, we record the session so that you can see where your account is signed in and sign out other devices in your account settings. For each session we keep when you signed in, the browser family and operating system (for example "Firefox on Windows") and the shortened network prefix (/24 or /48). We do not store your full IP address or your browser's full user agent. On the sessions page and in emails we may show the approximate city and country of the network, which we look up in a local database when we show it and do not store.
To warn you if someone else signs in to your account, we keep a one-way fingerprint of the browser family, operating system and network prefix of each sign-in, with when we first and last saw it. The fingerprint is a keyed hash: it cannot be turned back into those details. When you sign in with a combination we have not seen in the last 90 days, we email you the time, the browser, the operating system and the approximate network, and what to do if it was not you. We do not send this email for the first sign-in after you create your account. You can turn these emails off in your settings: we then delete your fingerprints and stop keeping them until you turn the emails back on.
- Why: to let you manage your sessions and to protect your account against takeover.
- Legal basis: performance of our contract with you for the sessions list (Art. 6(1)(b) GDPR), and our legitimate interest in keeping accounts secure for the fingerprints and alerts (Art. 6(1)(f) GDPR).
- How long: a session record until the session ends (when you sign out, sign it out from another device, or after 2 weeks at most); sign-in fingerprints for 90 days after the last sign-in that matched them. Both are deleted with your account.
Content you put in your codes
When you create dynamic codes, you give us content such as destination links, contact cards, WiFi details, menus, lists of links, coupons, PDFs and images. You can also save designs and organise codes in folders and with tags.
- You can upload logos, PDFs of up to 10 MB and images of up to 5 MB. We re-encode uploaded images and remove their EXIF metadata, including any location data.
- Anything you put on a hosted page can be seen by anyone who scans the code or has its link.
Some of this content may be personal data about you or about other people. For personal data about other people that you put into your codes, you are the controller and we act as your processor. In a shared workspace used by an organisation, that organisation is the controller. We process that content only to provide the service, following your instructions. The processor terms are part of our Terms of service.
- Why: to store, show and deliver your codes and hosted pages.
- Legal basis: performance of our contract with you (Art. 6(1)(b) GDPR).
- How long: until you delete the content or your account. Uploaded files that no code uses any more are deleted within 2 days.
API keys and webhooks
If you create API keys, we store only a SHA-256 fingerprint of each key. We cannot show you the full key again after we create it.
If you set up webhooks, we store the endpoint address you give us and a signing secret, which is encrypted at rest. We keep a log of webhook deliveries for 30 days so you can check whether they worked.
If you send an API request with an Idempotency-Key, we keep our answer to it for 24 hours, so that if you send the same request again (for example after a network error) you get the same answer instead of a second code. We store a fingerprint of the request, not the request itself, and delete the answer after 24 hours, when you leave the workspace or when your account is deleted.
- Legal basis: performance of our contract with you (Art. 6(1)(b) GDPR).
Apps you connect to your account (OAuth)
You can let another app use your account through OAuth, for example a tool that creates QR codes for you. On our consent page you see the app's name, what it asks to do and where you will be sent back, and you choose the one workspace it may use. We then record which app you authorised, for which workspace and with which permissions, and when (your consent record), and we issue the app tokens: we store only a fingerprint (hash) of each token. The app can only do what your role in that workspace allows; if you leave the workspace or your role changes, that applies to the app at once. If the app asks to know who you are, it receives a user number and, if you allow it, your email address and name.
You see every app you authorised under Authorised apps and can revoke any of them there; its tokens stop working immediately. What the app does with the data it receives is its own responsibility under its own privacy policy.
If you are a workspace admin and register an OAuth app, we store its name, its redirect addresses and a hash of its secret, and record who registered it in the workspace's audit log.
- Legal basis: performance of our contract with you (Art. 6(1)(b) GDPR).
Workspaces and teams
Everything you create belongs to a workspace. You always have a personal workspace that only you can see. You can also create shared workspaces and invite other people, or join one when someone invites you. Each member has a role: viewer, editor, admin or owner.
-
What other members see. In a shared workspace, every member sees the other members' names, email addresses, roles and the date they joined, and the codes, folders, files and statistics in the workspace. While you are a member, admins can also see which codes, files and API keys you created.
-
The workspace's audit log. Admins and the owner see a log of important changes in the workspace and when they happened, for example who invited or removed someone, changed a role, created an API key or deleted a code. It does not show network addresses. Once you leave, the log no longer shows your name, only "Former member". Entries are deleted after 12 months.
-
Invitations. To invite someone, an admin enters their email address. We send that address an email with a link that works for 7 days; the email says where we got the address, how long we keep it and who sees it, and links to this policy. One address gets at most 5 invitation emails a day, from all workspaces together. We store the address, the role, who sent the invitation and when, until 30 days after the invitation is accepted, revoked or expires. Nobody who invites is told whether the address already has an account.
-
Leaving. You can leave a shared workspace at any time, and an admin can remove you. API keys you created there stop working, invitations you sent and that are still pending are revoked, webhooks you added are paused, and your name is removed from the codes and files you made there. The codes themselves stay, because they belong to the workspace. If you stop being an admin, the API keys you created and the invitations you sent there stop working too.
-
Owners. The owner can hand the workspace over to another member, or delete it. We email both people when a workspace is handed over, and all members when it is deleted.
-
Data processing agreement. When an organisation uses a shared workspace, its owner or an admin can accept our data processing agreement on the organisation's behalf. We record the organisation's name, the name of the person who accepted, the version and the date, for as long as the workspace exists.
-
Exporting a workspace. Admins and the owner can download everything in a shared workspace, including the members' email addresses and roles and the audit log.
-
Notes on statistics. Editors can add short dated notes to the insights charts, such as "Poster went up". Every member sees them. We keep a note until someone deletes it, or its code or the workspace is deleted. The workspace export names who wrote a note only while that person is a member.
-
Weekly summary. Each member can turn on a weekly email with a summary of a workspace's scans, just for themselves. It is off until you turn it on. Every email has a link that turns it off without signing in. We store your choice and the day we last sent it, with your membership.
-
ZIP files of codes. Any member can ask for many codes at once as a ZIP file of images. We prepare it in the background, email you a link and keep the file for 7 days; only you can download it, and only while you are a member. We keep a note of the request (which codes, formats, when) for 30 days. Changing codes from a CSV file is checked and shown to you first; we do not keep the file. The "Check with camera" button reads a printed code in your browser only: the camera image is never sent to us.
-
Why: to let people work together on QR codes.
-
Legal basis: performance of our contract with each member (Art. 6(1)(b) GDPR). Emailing an invitation to someone who may not have an account is based on the legitimate interest of the team that invites them in reaching them (Art. 6(1)(f) GDPR). We keep the records of accepted data processing agreements to show that we meet our obligations (Art. 6(1)(c) and (f) GDPR).
When someone scans a dynamic QR code
This section is for anyone who scans a dynamic code made with our service. A dynamic code points to a short link such as https://1codigoqr.com/Ab3dE7x. When you open it, we send you on to the destination or show you the hosted page.
On short links and hosted pages, we use no cookies, no fingerprinting and no third-party scripts.
For each scan, we store:
- the time of the scan;
- the country and city. We work these out in memory from your IP address, using a MaxMind GeoLite2 database that is stored on our own servers. Your IP address is never sent to MaxMind and is never stored;
- the type of device (for example phone, tablet or computer), the operating system family and the browser family;
- a visitor hash, so we can count unique visitors without recognising anyone. It is a keyed BLAKE2b hash of a shortened form of your IP address, your browser's user agent and the code's ID. The key is a random value that exists only for the current day (UTC) and is deleted when that day ends. After that, nobody, including us, can recreate the hash. We erase the hash from the stored scan two days later.
If your browser sends Do Not Track or Global Privacy Control, we only store the fact that a scan happened and its time.
We do not count known bots or link previews (for example, when a messaging app loads a link to show a preview).
We delete individual scan records after 90 days, or after 30 or 60 days if the workspace that owns the code chooses a shorter period. A workspace can also choose not to record the city of scans. Code owners never see individual scans. They only see anonymous daily totals, and places, devices and hours with fewer than 5 scans in a period are grouped together or shown as "< 5", so that a line in their statistics cannot point to one person.
Your request also appears for a short time in our hosting provider's router logs, as described in "When you visit the website".
If a code sends you to another website, that website's own privacy policy applies. The content of hosted pages comes from the code owner.
- Why: to give code owners anonymous statistics about how their codes are used.
- Legal basis: legitimate interests (Art. 6(1)(f) GDPR): the code owner's interest in knowing how their code performs, and our interest in offering this feature.
- Balancing of interests: people who scan a printed code can reasonably expect the scan to be counted. We collect as little as possible and avoid anything that would let us or the code owner follow you: no cookies, no stored IP address, location only to city level, a daily key that is destroyed, short retention, and only anonymous totals for the owner. We believe this keeps the impact on you very low, so our interests do not override your rights.
- Your right to object: turn on Global Privacy Control or Do Not Track in your browser. From then on, we only store the time of your scans. You can also write to privacy@1codigoqr.com. Because the data we keep does not let us identify you, we usually cannot find your past scans (Art. 11 GDPR).
Safety checks on destination links
To protect people from phishing and malware, we may check the destinations of dynamic codes against a list of known harmful domains. If enabled, we also use Google Safe Browsing. We send Google only the destination URL, when the code is created and in a daily re-check. We never send any data about the people who scan codes. If a link is flagged, people who scan the code see a warning page.
- Legal basis: our legitimate interest, and that of the people who scan codes, in protection from harmful links (Art. 6(1)(f) GDPR).
Some of these checks are automated. If an automated check affects one of your codes, you can ask us to review the decision.
Once a day we also check that the page each dynamic code leads to still opens, by requesting it as a visitor would, and we email the owner and admins of the workspace when it stops working. Only the page itself is requested; nothing about the people who scan codes is involved. Admins can turn these emails off.
Abuse reports
Anyone can report a code that they believe is illegal or breaks our Terms of service, using the report form or by writing to abuse@1codigoqr.com. We store the report: the category, your explanation, your name and email address if you give them, the short code and the time.
If you give an email address, we confirm that we received your report and tell you our decision. If we restrict a code, we send its owner a statement of reasons explaining our decision and how to challenge it.
When a code is reported several times from different networks within a few days, or a safety check flags its destination, people who scan it automatically see a warning page until a person on our team reviews the case. We never block a code automatically. We tell the code's owner that automated means were used and how to contest the decision. To count the networks, we keep a keyed hash (HMAC) of the reporter's network (the first part of the IP address, never the full address) together with the reported code. It cannot be turned back into an address, and we delete it after 7 days, or earlier with the report. We publish yearly totals in our transparency report.
- Why: to handle reports of illegal content and abuse, as required by the EU Digital Services Act.
- Legal basis: our legal obligations under the Digital Services Act, Regulation (EU) 2022/2065 (Art. 6(1)(c) GDPR), and our legitimate interest in keeping the service safe (Art. 6(1)(f) GDPR).
- How long: 2 years after the case is closed.
Emails we send
We only send emails needed to run the service. These include email address verification, sign-in codes, password resets, alerts about new sign-ins and changes to your password, email address, two-factor authentication or passkeys, links to your data exports, workspace invitations, notices that a workspace was handed over to you or deleted, confirmations and decisions about abuse reports, statements of reasons, a weekly summary of a workspace's scans if you turn it on, and important notices about your account or our terms.
Our email provider is Amazon Web Services EMEA SARL (Amazon SES, eu-west-1).
- Legal basis: performance of our contract with you (Art. 6(1)(b) GDPR). Emails about abuse reports and moderation decisions are based on our legal obligations under the Digital Services Act (Art. 6(1)(c) GDPR).
Downloading your data
In your account privacy settings you can download all your data as a ZIP file with JSON and CSV files: your account, the workspaces you belong to and your role in each, everything in the workspaces you own, and what other workspaces record about you: the codes, files, API keys and webhooks you made there, invitations sent to you or by you, changes to your membership, and the apps you authorised or registered through OAuth. We prepare the file in the background and email you when it is ready. The download link only works when you are signed in. We delete the file after 7 days.
Admins and the owner of a shared workspace can also download everything in that workspace, from its settings. That file works the same way, and only while the person who asked is still an admin there.
- Legal basis: your rights of access and portability (Art. 15 and 20 GDPR) and our legal obligation to respond to them (Art. 6(1)(c) GDPR).
Error monitoring
If enabled, we use Sentry, provided by Functional Software, Inc., in its EU data region, to receive reports about technical errors. We configure it not to send personal data.
- Legal basis: our legitimate interest in finding and fixing errors (Art. 6(1)(f) GDPR).
Legal bases at a glance
| Legal basis | What we use it for |
|---|---|
| Contract (Art. 6(1)(b) GDPR) | Your account, sign-in, your codes, designs, uploads, folders, tags, API keys, webhooks, OAuth apps and the apps you authorise, workspaces and memberships, service emails and the free generator |
| Legitimate interests (Art. 6(1)(f) GDPR) | Security, the security log, new sign-in alerts, protection against password guessing, rate limits, the human check on sign-up, safety checks on links, error monitoring, anonymous scan statistics, invitations to people who may not have an account, and records of what you accepted |
| Legal obligation (Art. 6(1)(c) GDPR) | Handling abuse reports and keeping moderation records under the Digital Services Act, answering requests to use your rights, records of data processing agreements, and responding to lawful requests from authorities |
We do not ask for consent for analytics or advertising, because we do not use any.
How long we keep data
| Data | How long we keep it |
|---|---|
| Content and logos in the free generator | Not stored. Processed in memory only |
| Rate-limit counters | Minutes to hours |
| Account data and acceptance records | Until you delete your account |
| Accounts with an unverified email address | Deleted after 30 days |
| Failed sign-in records | 24 hours |
| Records of your signed-in sessions | Until the session ends (2 weeks at most) |
| Sign-in fingerprints for new sign-in alerts | 90 days after they were last seen |
| Security log entries, including a workspace's audit log | 12 months |
| Workspace memberships | Until you leave or are removed, or the workspace or your account is deleted |
| Invitations (with the invited email address) | 30 days after the invitation is accepted, revoked or expires |
| Data processing agreement acceptances | As long as the workspace exists |
| Codes, designs, uploads, folders and tags | Until you delete them or your account |
| Uploaded files that no code uses | Deleted within 2 days |
| Individual scan records | 90 days, or 30 or 60 days if the code's workspace chooses |
| Daily key for visitor hashes | Deleted at the end of each day (UTC) |
| Visitor hash in a scan record | Erased 2 days after the scan |
| Anonymous daily scan totals | Until you delete the code or your account |
| Notes on statistics | Until deleted, or until their code or workspace is deleted |
| Webhook delivery log | 30 days |
| API answers kept for retries (Idempotency-Key) | 24 hours |
| OAuth access tokens (as hashes) | 1 hour |
| OAuth refresh tokens (as hashes) | Until revoked, or 90 days without use |
| OAuth consent records | Until you revoke the app, leave the workspace or delete your account, and at most a day after the app's last token expires |
| OAuth apps registered for a workspace | Until an admin deletes them or the workspace is deleted |
| Data export files | 7 days |
| ZIP files of codes (and the request) | 7 days (request: 30 days) |
| Abuse reports | 2 years after the case is closed |
| Retired short codes (no personal data) | Kept, so the code is never reused |
| Database backups | Up to 5 weeks at our hosting provider (daily copies for 7 days, weekly copies for 4 weeks); weekly copies in our EU storage for up to 9 weeks |
| Hosting provider's router logs | A short period, set by Heroku |
Deleting your account
You can delete your account at any time in your account privacy settings. Deletion is immediate and permanent. We delete your personal data and your personal workspace, with its codes, uploaded files and statistics.
-
If you own a shared workspace that has other members, it passes to its longest-standing admin, or else editor, or else viewer, and we email that person, so the team keeps its codes. A shared workspace with no other members is deleted. Before you confirm, the page lists which workspaces will be handed over and which deleted.
-
You leave every other workspace: API keys you created stop working, invitations you sent are revoked, webhooks you added are paused, and your name is removed from the codes and files you made there. The workspace's audit log records that a former member left, without your name.
-
Apps you authorised through OAuth lose access at once: we delete their tokens and your consent records.
-
We keep each of your short codes only as a retired code: the code itself, the reason and the time, with no personal data. Printed codes then show a "deleted" page, and the short code is never given to anyone else.
-
Entries in the security log stay for their normal 12 months but are no longer linked to your account. We also log that an account was deleted, with a short one-way fingerprint of your email address.
-
Database backups may contain deleted data for up to 5 weeks at our hosting provider, and up to 9 weeks in our weekly copies, before it disappears. We use backups only to restore the service, and if we ever restore one, we delete your data again.
Who receives your data
We never sell personal data, show ads or share data with advertisers. We share personal data only with:
- Service providers (sub-processors) that host and run the service for us. They may only use the data to provide their service to us, under data processing agreements. See the full list on our sub-processors page.
- Authorities, when the law requires us to, for example under a valid court order.
- The other members of your workspaces. They see your name, email address and role, and what you do in the workspace, as described in "Workspaces and teams".
- People you choose. Content on your hosted pages is visible to anyone with the link. Webhooks send data to the endpoints you set up. Invitations go to the addresses you enter.
MaxMind does not receive any data from us. We download their location database and use it on our own servers.
Transfers outside the EU
We store your data in the EU. Our application, database and files are hosted in the AWS Europe (Ireland) region, eu-west-1.
Some of our providers are US companies: Salesforce, Inc. (Heroku), Cloudflare, Inc., Functional Software, Inc. (Sentry) and Google LLC. If they access personal data from outside the EU, the transfer is protected by the EU-US Data Privacy Framework and/or the European Commission's Standard Contractual Clauses. Our sub-processors page lists the safeguard for each provider.
How we protect your data
- All connections use TLS (HTTPS), and browsers are told to always use it (HSTS).
- Data is encrypted at rest: files with Amazon S3 server-side encryption, and the database with our hosting provider's encryption.
- Passwords are hashed with Argon2. Webhook signing secrets are encrypted. API keys are stored only as SHA-256 fingerprints.
- You can sign in with passkeys, and turn on two-factor authentication with an authenticator app (TOTP) or a passkey.
- You can see where your account is signed in and sign out other devices, and we email you about sign-ins from new browsers or networks.
- We block repeated attempts to guess passwords.
- A strict Content Security Policy limits what can run on our pages.
- Only the people who need access to run the service have it, with the lowest level of access they need.
- We keep a security log of important account events.
Your rights
You have the following rights under the GDPR:
- Access (Art. 15): get a copy of your personal data. You can download it yourself in your account privacy settings.
- Rectification (Art. 16): correct your data. You can change most of it yourself in your account settings.
- Erasure (Art. 17): delete your data. You can delete your account yourself in your account privacy settings.
- Restriction (Art. 18): ask us to limit how we use your data in some cases.
- Portability (Art. 20): get your data in a machine-readable format (JSON and CSV) through the data export.
- Objection (Art. 21): object to processing based on legitimate interests, on grounds relating to your situation. If you scan codes, see "Your right to object" above.
- Withdraw consent: if we ever ask for your consent, you can withdraw it at any time. This does not affect processing that happened before.
- Complaint: you can complain to a data protection supervisory authority, in particular in the EU country where you live, work or where you think the problem happened. Our lead supervisory authority is Comissão Nacional de Proteção de Dados (CNPD), www.cnpd.pt.
To use your rights, write to privacy@1codigoqr.com. We may ask you to confirm your identity. We reply within one month. If a request is complex, we may need up to two more months, and we will tell you why within the first month.
If your request is about personal data that an account holder put into a QR code, we will pass it on to that account holder, who is the controller, and help them respond.
Children
The service is not directed at children under 16. To create an account, you must be at least 16 years old or have the consent of a parent or guardian.
Changes to this policy
The date at the top of this page shows when we last changed this policy. If we make important changes, we will tell account holders before they take effect, by email or in the app, and ask you to confirm the new version the next time you sign in.
Contact
For any privacy question or request, write to privacy@1codigoqr.com or to Página Comum, [REGISTERED ADDRESS].