Privacy

Privacy
Last updated: 11 November 2026
Who’s responsible. Franco Soldera, trading as U-Things, Denmark. Address: Drejøgade 26C, 2100 København Ø, Denmark. Contact: contact@u-things.com.
1. This website and codes made here
One Tap QR does not ask you to create an account.
Analytics. We use Google Analytics to count visits to this site. It counts visits on our pages, never on code redirects. In the EU, UK and Switzerland, it loads and sets cookies only if you choose Accept, and you can change your choice any time under Cookie settings. Everywhere else, it loads when the page opens. Analytics relies on consent where consent is required.
Usage counts from Apify When you use One Tap QR through Apify, our server sends Google Analytics a short count each time you create a code, change where a code points, or check its scans. The count says which of those you did, whether it was a TEST code or a real one, whether it worked, and that it came from Apify. It doesn’t include your Apify account, your link, your code, or your IP address. It doesn’t use cookies, so the cookie banner on this site doesn’t apply to it. We use these counts only to see which features people use and where things fail.
2. Editable codes bought through Apify
The links you enter. We process the links you enter as Actor input only to run the service for you. For those, we act as your processor.
When someone scans one of your codes, we are responsible for the scan data (the controller), and we store:
•
which code was scanned, and when
•
the country, plus an estimated city and region (Cloudflare works these out from the IP address)
•
the device type: mobile, tablet or desktop
We don’t store the IP address, the browser details, or anything that identifies the person who scanned. Cloudflare, which runs our redirects and blocks abuse, sees each visitor’s IP address while it handles the request, on our behalf. Scan counts are approximate.
We use scan data only to count scans and show you statistics. We don’t sell it, and we don’t build profiles of people who scan. You see only totals, never individual scans.
Abuse limits. To prevent abuse, we limit how often each buyer can use the service, and we keep one overall counter. For this we keep a hashed version of your Apify account ID, never an IP address, and overwrite it each time window. There is no sign-in.
When an AI agent sends us feedback, it reaches our team by email without your IP address or Apify user ID. To limit how often feedback can be sent, we keep a salted hash of the IP address (or Apify user ID) for up to one day.
How long we keep it. We keep individual scan records for 90 days. After that we keep only one total per code per day, for a rolling 12 months. When a code ends, or after the shutdown year, we delete everything for that code within 30 days. When you delete a paid code, we delete its scans, stats, label and link right away, except a small record we keep for as long as One Tap QR runs: the code ID, your Apify user ID, and the dates the code was made and deleted. We keep it so the code ID is never reused and anyone who scans the code sees that it was deactivated (our legitimate interest). If you ask us to delete your data, we do it within 30 days.
Buyers. We know you by your Apify account, not by your email. We store your codes, their links and their scan counts. The Actor runs with Apify’s limited permissions, so it sees only its own runs and storage, the input you give it, and basic account information Apify passes to every Actor (your Apify user ID, and whether you are a paying user). It can’t see other data in your Apify account. Apify doesn’t give us your payment details. Apify may show us your Apify username in our run statistics. Don’t put personal data in the links your codes point to. If you do, you’re responsible for it.
3. Test codes
Test codes are separate from regular codes and kept in their own storage. Each Apify account can have up to 50 active test codes at a time. Each test code is deleted 48 hours after it’s made, which frees its place.
When someone scans a test code, we store the scanner’s IP address, network, approximate location, browser, and connection (TLS) details. We keep these for 48 hours to prevent abuse (our legitimate interest), then delete them for good, along with the code.
To deal with abuse, we keep a short record for 6 months: the code, its destination, a hashed Apify account ID, a hashed IP address, the network and the time. Then we delete it.
4. Who processes data for us
•
Cloudflare (hosting this site, redirects, scan data)
•
Apify (sales, accounts, payment)
•
Google (Google Web Risk link safety checks: links you enter in the Actor are checked against Google’s lists of unsafe sites)
•
Google Analytics (visits to this site, as described above, and usage counts from the Apify Actor, as described above)
Cloudflare and Google are US companies. Cloudflare is certified under the EU-U.S. Data Privacy Framework, and its data processing addendum, which includes the EU standard contractual clauses as a fallback, applies to our use. Google is certified under the EU-U.S. Data Privacy Framework, and Google Cloud’s data processing terms apply to our use of Web Risk.
5. Legal basis
Running the service for you relies on our contract with you (GDPR art. 6(1)(b)). Scan statistics, abuse limits, the abuse log and link safety checks rely on our legitimate interest in providing statistics to code owners and keeping the service safe (GDPR art. 6(1)(f)). Analytics relies on consent, as described in section 1.
6. Your rights
You can ask to see, correct or delete your data, object to its use, or move it elsewhere. Email contact@u-things.com and we’ll answer within one month. For data Apify holds about your account, ask Apify. You can also complain to the Danish Data Protection Agency (Datatilsynet).
Privacy
Last updated: 11 November 2026
Who’s responsible. Franco Soldera, trading as U-Things, Denmark. Address: Drejøgade 26C, 2100 København Ø, Denmark. Contact: contact@u-things.com.
1. This website and codes made here
One Tap QR does not ask you to create an account.
Analytics. We use Google Analytics to count visits to this site. It counts visits on our pages, never on code redirects. In the EU, UK and Switzerland, it loads and sets cookies only if you choose Accept, and you can change your choice any time under Cookie settings. Everywhere else, it loads when the page opens. Analytics relies on consent where consent is required.
Usage counts from Apify When you use One Tap QR through Apify, our server sends Google Analytics a short count each time you create a code, change where a code points, or check its scans. The count says which of those you did, whether it was a TEST code or a real one, whether it worked, and that it came from Apify. It doesn’t include your Apify account, your link, your code, or your IP address. It doesn’t use cookies, so the cookie banner on this site doesn’t apply to it. We use these counts only to see which features people use and where things fail.
2. Editable codes bought through Apify
The links you enter. We process the links you enter as Actor input only to run the service for you. For those, we act as your processor.
When someone scans one of your codes, we are responsible for the scan data (the controller), and we store:
•
which code was scanned, and when
•
the country, plus an estimated city and region (Cloudflare works these out from the IP address)
•
the device type: mobile, tablet or desktop
We don’t store the IP address, the browser details, or anything that identifies the person who scanned. Cloudflare, which runs our redirects and blocks abuse, sees each visitor’s IP address while it handles the request, on our behalf. Scan counts are approximate.
We use scan data only to count scans and show you statistics. We don’t sell it, and we don’t build profiles of people who scan. You see only totals, never individual scans.
Abuse limits. To prevent abuse, we limit how often each buyer can use the service, and we keep one overall counter. For this we keep a hashed version of your Apify account ID, never an IP address, and overwrite it each time window. There is no sign-in.
When an AI agent sends us feedback, it reaches our team by email without your IP address or Apify user ID. To limit how often feedback can be sent, we keep a salted hash of the IP address (or Apify user ID) for up to one day.
How long we keep it. We keep individual scan records for 90 days. After that we keep only one total per code per day, for a rolling 12 months. When a code ends, or after the shutdown year, we delete everything for that code within 30 days. When you delete a paid code, we delete its scans, stats, label and link right away, except a small record we keep for as long as One Tap QR runs: the code ID, your Apify user ID, and the dates the code was made and deleted. We keep it so the code ID is never reused and anyone who scans the code sees that it was deactivated (our legitimate interest). If you ask us to delete your data, we do it within 30 days.
Buyers. We know you by your Apify account, not by your email. We store your codes, their links and their scan counts. The Actor runs with Apify’s limited permissions, so it sees only its own runs and storage, the input you give it, and basic account information Apify passes to every Actor (your Apify user ID, and whether you are a paying user). It can’t see other data in your Apify account. Apify doesn’t give us your payment details. Apify may show us your Apify username in our run statistics. Don’t put personal data in the links your codes point to. If you do, you’re responsible for it.
3. Test codes
Test codes are separate from regular codes and kept in their own storage. Each Apify account can have up to 50 active test codes at a time. Each test code is deleted 48 hours after it’s made, which frees its place.
When someone scans a test code, we store the scanner’s IP address, network, approximate location, browser, and connection (TLS) details. We keep these for 48 hours to prevent abuse (our legitimate interest), then delete them for good, along with the code.
To deal with abuse, we keep a short record for 6 months: the code, its destination, a hashed Apify account ID, a hashed IP address, the network and the time. Then we delete it.
4. Who processes data for us
•
Cloudflare (hosting this site, redirects, scan data)
•
Apify (sales, accounts, payment)
•
Google (Google Web Risk link safety checks: links you enter in the Actor are checked against Google’s lists of unsafe sites)
•
Google Analytics (visits to this site, as described above, and usage counts from the Apify Actor, as described above)
Cloudflare and Google are US companies. Cloudflare is certified under the EU-U.S. Data Privacy Framework, and its data processing addendum, which includes the EU standard contractual clauses as a fallback, applies to our use. Google is certified under the EU-U.S. Data Privacy Framework, and Google Cloud’s data processing terms apply to our use of Web Risk.
5. Legal basis
Running the service for you relies on our contract with you (GDPR art. 6(1)(b)). Scan statistics, abuse limits, the abuse log and link safety checks rely on our legitimate interest in providing statistics to code owners and keeping the service safe (GDPR art. 6(1)(f)). Analytics relies on consent, as described in section 1.
6. Your rights
You can ask to see, correct or delete your data, object to its use, or move it elsewhere. Email contact@u-things.com and we’ll answer within one month. For data Apify holds about your account, ask Apify. You can also complain to the Danish Data Protection Agency (Datatilsynet).