Privacy Policy
Contents
- Who is responsible for your data
- What 2U does, in two parts
- Part 1 — the free QR generator: we process nothing
- Part 2 — accounts, short links and dynamic QR codes
- Scan and click analytics
- Legal basis for processing
- Who else sees your data
- How long we keep things
- Cookies and browser storage
- Your rights
- Children
- Language versions
- Contact and complaints
1. Who is responsible for your data
2U is operated by Eugen Grisco, an individual based in Chișinău, Moldova, not a registered company. For the purposes of data protection law, Eugen Grisco is the data controller for 2u.md and 2n.md.
| Contact | [email protected] |
|---|---|
| Location | Chișinău, Republic of Moldova |
| Applicable law | Moldova Law no. 195/2024 on the protection of personal data, and the EU General Data Protection Regulation (GDPR) where it applies to visitors in the EU |
2. What 2U does, in two parts
2U has two genuinely different halves, and they have very different privacy implications. It matters which one you're using:
- The free QR code generator — open to anyone, no account required. You type or paste something, style a QR code, and download it. This runs entirely in your browser.
- Accounts, short links and dynamic QR codes — currently invite-only. This is where a destination can be edited after a code is printed, and where scan statistics exist.
3. Part 1 — the free QR generator: we process nothing
When you use the generator without logging in, the content you encode never leaves your device. The QR code is built by JavaScript running in your own browser. Nothing you type — a web address, a WiFi password, a contact card, a message — is sent to our servers, logged, or stored anywhere by us.
This isn't a policy choice we're promising to honour; it's how the software is built. Nothing you enter, and nothing about you, is sent to us when you generate or download a static QR code. The only thing that reaches 2U is an anonymous tick when you download: a fixed label for the file format, the kind of content (for example "web address" or "WiFi") and whether it was made on the public site or in the app. It never contains what you typed or the code itself, and we do not record your IP address, browser details, cookies or any identifier, so it cannot be linked to you. As with every request to 2U, it passes through Cloudflare (section 7). You can see this in your browser's Network tab: nothing while you type, and one small request to 2U when you download.
Because the anonymous download count contains no personal data, the legal-basis and retention discussion below does not apply to it either.
4. Part 2 — accounts, short links and dynamic QR codes
This part of 2U is currently available by invitation only. If you have an account, we process:
| Account data | Your email address, a securely hashed password (we never store your actual password), your chosen language, and who invited you. |
|---|---|
| Links and QR codes you create | The destination address, an automatically generated short code (or one an administrator assigned), any styling you chose, whether you've marked it permanent, and its creation/expiry dates. |
| Invites | If you're an administrator, the invite codes you generate and who used them. |
Destinations are publicly checkable. Adding
/who to any 2U short link — 2u.md/abc12/who —
shows a page with the address that link points to, when it was created
and whether it still works. This exists so someone scanning a printed
code can see where it leads before following it, which is the main
defence a stranger has against a malicious QR code.
That page shows nothing about who owns the link — no name, no email, no account details. It also doesn't count as a scan, so it never appears in the owner's statistics.
We do not ask for, and have no field to store, more than this — no physical address, no payment details (the service has no billing in its current form), no government ID.
Destinations are checked against known-malware lists. Before a short link or dynamic QR code is created, its destination is checked against a blocklist we maintain ourselves and against public threat-intelligence feeds — URLhaus and ThreatFox, both published by the nonprofit abuse.ch. A destination that appears on either is rejected outright. Existing links are re-checked periodically; a match there does not switch the link off by itself — it's queued for a person to review, because a feed's own false positive could otherwise take down a legitimate, already-printed link that nobody can reprint. These feeds are downloaded to our own server and matched locally: your destination is never sent to abuse.ch, or to anyone else, to perform this check.
Email we send you. Your address is used for running your account, never for marketing — there is no newsletter, no promotional mail, and we don't pass your address to anyone for their own use. There are three kinds:
- A link of yours is about to expire. A reminder shortly before it runs out, so a printed code doesn't stop working unnoticed. This one is optional and off by default — you switch it on, and off again, from Your account.
- Something changed about your account — it was suspended, restored, or closed by an administrator.
- Something changed about one of your links — it was blocked or unblocked, and on what grounds.
We normally send the last two, because finding out by accident that your account no longer works is a bad way to find out. But they are sent at an administrator's discretion rather than automatically: in a case of active abuse, advance notice can be exactly what makes the measure useless. If something has happened to your account and you weren't told why, ask us — see your rights.
Anti-abuse check when you redeem an invite. The page where you turn an invite code into an account runs Cloudflare Turnstile, a challenge that distinguishes people from scripts without asking you to identify letters in a picture. To do that, your browser loads a script from Cloudflare, and our server sends Cloudflare your IP address together with the challenge result so it can be validated. This happens on that one page only — not on the free generator, not when you sign in, and never when someone scans a code or follows a short link.
5. Scan and click analytics
When someone scans a dynamic QR code or clicks a short link, we record a "hit" so the link's owner can see basic statistics. This is designed to collect as little as the feature can work with:
- Country — a two-letter code, derived from our CDN provider's edge network at the moment of the request. Your IP address is not received, processed, or stored by us at any point in handling a scan or a click: the country code arrives already derived. (The one place the service does handle an IP address is the anti-abuse check when someone redeems an invite — described in section 4. That is a different page, reached deliberately by someone creating an account, and never part of scanning a code.)
- Device class — mobile, tablet, or desktop, worked out from the browser's user-agent string.
- Operating system family — e.g. iOS, Android, Windows — from the same source.
- Referring website's domain — if you arrived via a link on another site, we record that site's domain name only, never the full URL (which can contain identifying information in its own right).
We do not use cookies, browser storage, device fingerprinting, or any other persistent identifier to track visitors across scans. Two scans of the same code by the same phone look identical to us — there is nothing in our data that connects them to each other or to a person. This is a deliberate design choice, not an oversight: it's what lets us rely on legitimate interest (see below) rather than needing consent we have no way to collect at the moment someone scans a printed code.
6. Legal basis for processing
Under GDPR Article 6 (and the equivalent provisions of Law 195/2024), we rely on:
- Contract (Art. 6(1)(b)) — for account data and the links/QR codes you create, because we need this to provide the service you've asked for.
- Legitimate interest (Art. 6(1)(f)) — for the minimal scan/click analytics described above. Our interest is letting link owners see basic aggregate usage; we believe this is proportionate given how little is collected, that none of it identifies an individual, and that it could not practically be consent-based (a person scanning a printed code has no opportunity to be asked first).
- Contract (Art. 6(1)(b)) — for the email we send about your account and your links. Telling you that your account was suspended, or that a link stopped working, is part of providing the service, not something separate bolted onto it.
- Legitimate interest (Art. 6(1)(f)) — for the expiry reminder, and for the Turnstile check on the invite page. Our interest in the first is that a link you paid to have printed shouldn't die silently; you can switch it off at any time, which is how you object to it. Our interest in the second is keeping an invite-only service from being opened at scale by scripts, which cannot be done after the fact.
7. Who else sees your data
We don't sell data, and we don't run ads. A small number of service providers process data on our behalf:
| Cloudflare | Sits in front of 2u.md as our content delivery network and security layer. It sees the technical details of every request (as any CDN must, to function) and is the source of the country code described above. Cloudflare publishes its own Data Processing Addendum and Standard Contractual Clauses for this role. |
|---|---|
| Cloudflare Turnstile | The same company, in a second and narrower role: the anti-abuse challenge on the invite redemption page. For that check only, Cloudflare receives your IP address and signals from your browser, and returns a pass or fail. It is not used on any other page, and we receive no profile or score about you from it — only whether the check passed. |
| Hosting provider | Our web hosting company stores the application and database. It does not use your data for any purpose of its own. |
| Outgoing mail | The mail server that delivers the messages described in section 4. It handles your email address and the content of those messages in order to deliver them. |
We do not use third-party analytics, advertising, or tracking services of any kind.
abuse.ch (URLhaus, ThreatFox) is not one of the processors above, because the relationship only runs one way: we download their published threat feeds to check destinations locally, as described in section 4. No destination, account, or usage data is ever sent to them.
8. How long we keep things
- Individual scan/click events are held only briefly, in a queue, until they're rolled up into aggregate daily counts — typically within minutes to hours — and then deleted. What remains afterward is a count (e.g. "14 scans from Moldova, mobile, on 3 October"), not a list of events.
- Aggregate statistics are kept for a configurable period, currently 400 days, after which older figures are automatically removed.
- Short links and dynamic QR codes last 90 days from creation by default. Their owner can extend that from their dashboard; a link explicitly marked permanent doesn't expire on its own.
- Account data is kept for as long as the account exists, and deleted on request — see your rights, below.
- Moderation records. If an account is suspended or a link is blocked, we store the reason alongside it, so that the decision can be explained and reversed. These live with the account or link they belong to, and go when it goes.
- Flagged links. If a periodic re-check matches one of your links against a threat feed (section 4), we keep a record of the match — which feed, what matched, and a snapshot of the destination at that moment — until an administrator reviews it, and afterward as part of that decision's history. This record isn't pruned on its own schedule; like moderation records, it lives with the link and is deleted if the link is deleted.
- Generator download counts are kept as daily totals. They contain no personal data and are not tied to anyone.
9. Cookies and browser storage
The free generator sets no cookies, and neither does scanning a code or following a short link. There is no consent banner on 2U because there is nothing to consent to: we set no analytics, advertising, or tracking cookies anywhere on the service.
Inside the signed-in dashboard, two cookies are set, both strictly necessary in the ePrivacy sense — essential to a feature you actively asked for, and useless for tracking:
2u-session | Keeps you signed in. Encrypted, marked Secure and HttpOnly, and scoped to the /app path — which means it is not sent when anyone requests a short link, so your session never travels with a scan. It expires after two hours of inactivity, and when you sign out. |
|---|---|
XSRF-TOKEN | A per-session token that lets the dashboard verify a form was submitted from the dashboard and not from a hostile page elsewhere. Same lifetime as the session. |
The dashboard also remembers one thing in your browser's local
storage, under 2u_theme: whether you chose the light or
dark appearance. It never leaves your device, we cannot read it, and
clearing your browser data simply returns the dashboard to following
your system setting.
The Turnstile check described in section 4 is operated by Cloudflare on the invite page, and may place a short-lived token of its own in your browser for that check. It is a security measure, not a tracker.
10. Your rights
Depending on where you live, you generally have the right to:
- Access the data we hold about you
- Correct it if it's wrong
- Delete your account and associated data
- Restrict or object to how we use it
- Receive a copy in a portable format
- Withdraw consent, where consent is the basis for processing
- Lodge a complaint with a data protection authority
If you have an account, two of these you can exercise yourself, immediately, without asking us: sign in and open Your account, where you can download everything we hold about you as a file, and permanently delete your account and all its data. Deletion is irreversible and takes effect at once.
If your account is suspended, you can't sign in, and so you can't use that self-service export — but the right itself is unaffected. Email [email protected] from the address the account uses and we'll send you the same data, together with the reason recorded for the suspension. Being suspended is not a reason for us to withhold your own data from you.
For anything else, email [email protected]. Because 2U is currently invite-only and run by one person, those requests are handled personally rather than through an automated system — expect a reply within a reasonable time, but not necessarily instantly.
If you're in Moldova, you can complain to the National Center for Personal Data Protection (Centrul Național pentru Protecția Datelor cu Caracter Personal):
| Website | datepersonale.md |
|---|---|
| [email protected] | |
| Telephone | +373 22 820 801 |
| Address | str. Serghei Lazo 48, MD-2004 Chișinău, Republic of Moldova |
If you're in the EU, you can complain to your local data protection authority instead. We'd appreciate the chance to sort out any concern directly first, but that's your choice, not a requirement.
11. Children
2U's account features are invite-only and not directed at children. The free generator asks for no personal information and has no age gate, since it processes nothing about the person using it.
12. Language versions
This document is published in English, Romanian and Russian. The translations are provided so you can read it in the language you're most comfortable with. If the versions ever differ in meaning, the English version is the one that applies — not because it matters more, but because there has to be a single authoritative text, and this is the one the others were translated from.
13. Contact
Questions, requests, or concerns about privacy: [email protected].