This notice supplements the general privacy policy (in German). For the free generator, everything remains as described there: the processing takes place in your browser. With the paid “Dynamic QR codes” service, a short link replaces the destination, and we store the data listed here.
1 Controller
The controller responsible for the processing is TFB Beyond UG (haftungsbeschränkt), Blieschendorferweg 24, 23769 Fehmarn, Germany, email info@tfb-beyond.com, telephone +49 160 97016864 (details as in the Imprint).
2 What data we store
When you book a plan with dynamic QR codes, we store the following data. For each group, we state what we need it for, on what legal basis and for how long. How we proceed after the end of the contract is described in section 7.
Codes
- Data: short link number, name, destination address (URL), status (active, paused, blocked, deleted), timestamps, change history of the destination address.
- Purpose: redirection, management, checking for abuse.
- Legal basis: contract, Art. 6(1)(b) GDPR.
- Retention: for as long as your contract exists; afterwards see section 7.
Account
- Data: email address (from the checkout), language, plan, billing period, number of extra codes, currency, amount, payment status, paid-until date, identifiers at Stripe (customer and subscription number), and, if an account is blocked, the reason for the block.
- Purpose: performance of the contract, billing, reconciliation with Stripe, contract confirmation, notifications about payment and cancellation, restoring your management link.
- Legal basis: contract, Art. 6(1)(b) GDPR; statutory retention, Art. 6(1)(c) GDPR.
- Retention: for as long as the contract exists. Data that belongs to accounting records we retain in accordance with the statutory retention periods of commercial and tax law (six to ten years, depending on the document).
Orders and plan changes
- Data: selection, amount, time, version of the Terms, time of your consent to the immediate start of performance, result. For an order, also the destination address and the name you entered for the first code.
- Purpose: proof of the conclusion of the contract, of your consent and of the consequences of a withdrawal.
- Legal basis: contract and our legitimate interest in proof, Art. 6(1)(b) and (f) GDPR; statutory retention, Art. 6(1)(c) GDPR.
- Retention: same as the account data. Orders that were not completed we delete after 30 days. The destination address and name from an order we delete no later than 12 months after the order is completed.
Secret management links, password and pickup secret
- Data: Of your management links, we store only a checksum, not the link itself (at most ten per account, plus the time of last use). The one-time pickup secret of your order we likewise store only as a checksum. If you set a password, we store only a non-reversible hash of it (scrypt), never the password itself, plus the time at which you set it.
- Purpose: access to the management page via the management link or with email address and password.
- Legal basis: contract, Art. 6(1)(b) GDPR.
- Retention: until renewal, until you sign out, or until your account is cleaned up after the end of the contract (section 7). Links from emails expire after 30 days if you do not use them. We store the hash of your password until you replace the password or your account is cleaned up.
Cancellations and withdrawals without signing in
- Data: email address, name, code, type of statement, desired date, reason, time of receipt, reference, result, confirmation link (only as a checksum).
- Purpose: processing, statutory confirmation obligation, proof, protection against abuse by third parties.
- Legal basis: contract and legal obligation, Art. 6(1)(b) and (c) GDPR; our legitimate interest, Art. 6(1)(f) GDPR.
- Retention: statements that we can match to a contract: same as the account data. Statements that we cannot match to a contract we delete no later than 12 months after they are dealt with.
Abuse reports
- Data: code, reason, description and, if the reporting person provides them, contact details.
- Purpose: combating abuse, protecting third parties.
- Legal basis: our legitimate interest, Art. 6(1)(f) GDPR.
- Retention: we delete them no later than 12 months after the report is dealt with.
Outbox of emails
- Data: recipient, subject, text and sending status of the emails we send you. We make management links and confirmation links in the stored text unrecognizable after sending.
- Purpose: proof of sending, retrying in case of delivery errors.
- Legal basis: contract and our legitimate interest, Art. 6(1)(b) and (f) GDPR.
- Retention: we delete sent emails after 90 days and emails that finally failed after 180 days.
Notifications to us as the operator
- Data: internal operational notifications, for example about duplicate subscriptions, deviating amounts, chargebacks or refund requests, with the identifiers of the account and the case.
- Purpose: operation, accounting, troubleshooting.
- Legal basis: contract and our legitimate interest, Art. 6(1)(b) and (f) GDPR.
- Retention: we delete notifications that have been dealt with after 180 days. Notifications not yet dealt with remain until they are dealt with.
Payment events from Stripe
- Data: event number, type, time and, where applicable, type of error.
- Purpose: reconciliation of payments, protection against duplicate processing.
- Legal basis: contract, Art. 6(1)(b) GDPR.
- Retention: we delete processed events after 90 days. Events that we could not process we delete no later than 12 months after they are dealt with.
Scan counter
- Data: code, day, device type, number (details in section 4).
- Purpose: statistics for you.
- Legal basis: contract, Art. 6(1)(b) GDPR.
- Retention: we delete daily values after 24 months.
We receive a name, an address or bank details from you only to the extent that you provide them to us in the Stripe checkout or in a cancellation or a withdrawal. Payment details such as the card number are processed by Stripe; they do not reach us.
3 Payment via Stripe
Payment is made through Stripe Checkout (card only). When we redirect you to the checkout, Stripe processes your payment and contact details (for example name, email address, card, country) in a separate checkout on Stripe's page. From Stripe we receive the payment status, your email address, the customer and subscription number, the plan booked and the billing period of the term. In the event of chargebacks and fraud warnings, Stripe notifies us of the case.
For payment processing in the European Economic Area, our contracting party is Stripe Payments Europe, Limited, One Wilton Park, Wilton Place, Dublin 2, D02 FX04, Ireland. Stripe processes the data for the payment, in part as an independent controller, for example for fraud prevention and to meet legal obligations. Stripe may transfer data to the USA and other countries. As the basis, Stripe names in its own privacy policy the EU-U.S. Data Privacy Framework and the standard contractual clauses approved by the European Commission. You will find further information in the Stripe privacy policy.
4 Redirection, scan counter and server logs
When someone scans the QR code, their device calls up the short link (for example https://qr.easyfreeqr.com/K7M2P9X) and is redirected to the destination you have set. In doing so, we count the call in a daily counter per device type (Phone, Tablet, Computer, Other). We do not store an IP address, an identifier of the person or individual calls, but only: code, day, device type and the number. We do not count recognizable search engine crawlers and automated checking programs. We derive the device type from the browser identifier of the call; we do not store the browser identifier itself in the counter.
The counter serves you for the statistics of your code (contractual service, Art. 6(1)(b) GDPR). We delete daily values after 24 months.
The response to the short link call is not cached (Cache-Control: no-store) and does not pass on the referring page (Referrer-Policy: no-referrer). The destination page to which you redirect receives the usual connection data from the device of the person scanning, for example the IP address. The respective operator of that page is responsible for it.
Server logs: As with every page of our website, the web server technically generates a log with IP address, browser identifier, requested address, time and referring page. This also applies to calls to the short address qr.easyfreeqr.com; there, the requested address contains the number of the short link. We delete these logs after 11 days, as described in section 2 of the general privacy policy (in German). The legal basis is our legitimate interest in operational security, Art. 6(1)(f) GDPR.
5 Protection against abuse
When a code is created and when the destination address is changed, we check the destination address technically: format, a blocklist of known harmful domains, known short link services and our own addresses. At regular intervals we check the destinations of all existing codes again, and new destinations after a short time. For this we do not retrieve the destination page. To limit abuse, we temporarily count requests per connection in working memory (for IPv6, per network range); the IP address is not stored or logged for this. The legal basis is our legitimate interest in protecting the service and third parties, Art. 6(1)(f) GDPR.
6 Management link and browser storage
Your management link contains a secret string of characters. On the first call, the page asks you whether it is your account, stores the string in your browser's local storage (localStorage, entry efqr-dyn-token) so that you stay signed in, and removes it from the address bar. On the server, we store only checksums, not the link itself. You can sign out on the management page on this device; the entry is then deleted. Keep the link secret.
When you place an order, the page stores these entries in your browser:
efqr-dyn-claim(sessionStorageandlocalStorage): a random pickup secret so that you can sign in after the checkout. It is valid for at most two hours and is removed after pickup.efqr-dyn-sid(sessionStorageandlocalStorage): the session identifier of the checkout, so that reloading the page after you return does not lose the order. At most three hours, removed after pickup.efqr-dyn-draft(sessionStorage): an order draft with destination address, name, plan, billing period and number of extra codes, so that your entries are not lost on the way to the checkout and back. At most two hours, removed after pickup.efqr-dyn-path(sessionStorage): the page from which you placed the order. Removed after pickup.efqr-dyn-cur(localStorage): your currency choice (euro or US dollar). It remains until you delete your browser's data. The page suggests the currency based on your browser's time zone; this information does not leave your device.
All of this is necessary for the service you requested (§ 25(2) no. 2 of the German Telecommunications Digital Services Data Protection Act (TDDDG)).
7 Retention after the end of the contract and deletion
Deleting a code. If you delete a code, the short link immediately stops redirecting. We keep the code's row with the short link number, the status “deleted” and the time of deletion, so that the number is never reassigned. The name, destination address and change history of the destination address of the deleted code initially remain stored. We delete them no later than 12 months after the code is deleted.
After the end of the contract. If your contract ends, we keep your codes (short link, destination address, name) for up to 365 days so that you can order again. After that, we mark the codes as deleted, remove your email address and your access links, and delete the emails to you that are still stored. We delete the name and destination address of these codes, as described above, no later than 12 months after deletion.
Statutory retention. We retain accounting records and proof relating to the contract in accordance with the statutory retention periods of commercial and tax law (six to ten years, depending on the document).
Dealt with. Where section 2 says “no later than 12 months after being dealt with,” we mean the point in time at which the case is concluded, for example a report has been processed or an order has ended.
8 Emails to you
We send you contract and service emails (confirmation, plan change, cancellation, payment problem, end of contract, restoration, blocking of a code or account). These are not advertising emails. We do not send you advertising on the basis of this order. If emails do not get through, we try to send them several times (after 1, 5 and 30 minutes and after 2 and 12 hours) and then report the error internally.
9 Recipients
The recipients of your data are:
- Stripe Payments Europe, Limited (payment, see section 3);
- our hosting provider Oracle Deutschland B.V. & Co. KG, Riesstraße 25, 80992 Munich, data center Frankfurt am Main (see section 2 of the general privacy policy);
- for sending the emails, Migadu-Mail GmbH, Rohnen 587, CH-9414 Schachen, Switzerland, where the mailbox of our domain tfb-beyond.com is hosted, through which the emails to you are sent;
- tax advisors and authorities, to the extent that we are legally obliged to do so.
Your data is not sold.
10 Your rights and right to lodge a complaint
You have the rights set out in section 7 of the general privacy policy (in German): right of access, rectification, erasure, restriction of processing, data portability, objection, and the right to lodge a complaint with a supervisory authority. Write to us at info@tfb-beyond.com. Please tell us one of your codes and the email address of your account so that we can identify you. You can object at any time to processing based on legitimate interests (Art. 6(1)(f) GDPR).
The supervisory authority responsible for us is the Independent Centre for Privacy Protection Schleswig-Holstein (Unabhängiges Landeszentrum für Datenschutz Schleswig-Holstein), Holstenstraße 98, 24103 Kiel (datenschutzzentrum.de).