Data Processing Addendum

Last updated November 15, 2026

This Data Processing Addendum ("DPA") is between you, the account holder ("Customer"), and Outside The Box ("we"), which runs myqr.sh. It applies when we process personal data for you that's protected by the EU GDPR, the UK GDPR, the Swiss Federal Act on Data Protection or similar laws. It forms part of our Terms and takes effect when you accept them, with no signature needed. If you need a countersigned copy, contact us.

1. Roles

For the data described in section 2, you are the controller (or a processor acting for your own client) and we are your processor. For your own account and billing details, we are the controller, as described in our Privacy Policy.

2. What we process

  • Purpose and nature: redirecting people who scan your QR codes or open your short links, picking a destination when you set routing rules or an A/B test, hosting the files, business cards and pages you add, collecting responses to forms on your pages, loading your ad pixels where you turn them on, adding your UTM tags and conversion tokens to your destinations, recording visits, taps and conversions so we can show you analytics, and emailing campaign reports to the people you choose.
  • Data subjects: people who scan your codes, open your short links or fill in forms on your pages, and anyone whose details you choose to put in a destination, name, note, tag, hosted file, business card or page.
  • Personal data: time of visit; whether it was a scan or a click; approximate location (country, region, city, continent); device type, browser and operating system; referring site; the destination URL including any query parameters. To count repeat visits once, a one-way hash of the network address and browser is kept for one hour, then deleted. We don't store IP addresses.
  • Routing: to pick a destination, we use the visitor's device type, country, browser language and the time of the visit. Nothing about this is stored beyond the visit fields above.
  • Hosted files and business cards: the files (PDF, PNG, JPEG or WebP) and card details (name, photo, job title, company, phone, email, website, address and note) you upload. We store them and serve them to anyone who opens the code or has the link; they're public by design.
  • Pages: the text, links, images, videos, contact details, menus, addresses and any custom CSS or HTML you add to a page. Like files and cards, pages are public by design. We count taps on a page's buttons, links and social icons as a daily total per element. Video, Spotify and map elements load nothing from YouTube, Vimeo, Spotify or Google until the visitor taps them; after that, the visitor's browser loads that provider's content directly, and we don't receive what it collects. If a page uses Google Fonts, the visitor's browser requests the fonts directly from Google (fonts.googleapis.com and fonts.gstatic.com) when the page loads. Google isn't our subprocessor for this: we don't send it any data, and it receives the request the way any website's font request reaches it. An HTML embed you add (Pro) loads when the page loads, inside a sandboxed frame, and whatever it loads comes from the services you chose.
  • Form responses: what a visitor submits through a form on your page (the fields you choose, such as name, email, phone, a message or other answers) and when. This is personal data we process for you as your processor: we store them, show them in your dashboard, let you export them as CSV and, if you turn it on, email each response to you. They're stored until you delete the response, the page or your account.
  • Ad pixels: if you turn pixels on for a code, we show the visitor a brief “Opening…” page that loads the Meta Pixel, Google tag or TikTok Pixel IDs you saved, then sends them on. Pixels never load for visitors in the EEA, the UK, Switzerland or Quebec, visitors whose location is unknown, browsers sending a Global Privacy Control signal, or bots; those visitors are redirected straight away. The data the pixels collect goes from the visitor's browser directly to those platforms. We don't receive or store it.
  • UTM tags and conversion tracking: we add the UTM tags you set to your external destinations. If you turn on conversion tracking for a code (Pro), we add a signed myqr_cid token holding the code, the visit time, scan or click, and a random number; nothing about the visitor, and no database record is made to create it. Our tag (/t.js) on your site keeps the token in your site's own browser storage for your attribution window, sets no cookies on our domain, and does nothing for browsers sending a Global Privacy Control signal. When your site or server reports a conversion, we store the code, campaign, goal, time, visit time, scan or click, and any value, currency and order number you send. A one-way hash of the sender's network address is used only as a short-lived rate-limit key. You're responsible for describing conversion tracking in your own privacy notice and for any consent your site needs for it.
  • Campaign reports: the email addresses you add to a campaign's reports (up to five), used only to send those reports. Each recipient can unsubscribe themselves.
  • Special categories: none intended. Don't put sensitive data in destinations, names, notes, tags, hosted files, business cards or pages, and don't use forms to ask for it.
  • Duration: while your account exists. Deleting a code or page deletes its visit history, conversions, tap counts and form responses; deleting a campaign deletes its numbers and report recipients; deleting your account deletes everything.

3. Our obligations

  • We process the data only on your documented instructions, which are these terms, this DPA and the settings you choose in the service, including routing rules, A/B tests, UTM tags, whether conversion tracking is on, and whether ad pixels load on a code. We'll tell you if we believe an instruction breaks data protection law.
  • Everyone we authorize to access the data is bound by confidentiality.
  • We apply the security measures in section 8.
  • We help you respond to people exercising their rights. You can delete any code, page or form response yourself, and export analytics and form responses as CSV. If a request reaches us directly, we'll pass it to you.
  • We give reasonable help with security, breach notification, data protection impact assessments and consultations with regulators, taking into account the information available to us.
  • If we become aware of a personal data breach affecting your data, we'll notify you without undue delay, with the information you need to meet your own obligations.
  • When you delete data or your account, we delete it from the live service. Copies in our providers' backups are removed when those backups expire.
  • We make available the information needed to show we meet this DPA, and we answer reasonable written questions about it. If that isn't enough, you may audit us once a year at your own cost, with 30 days' notice and under confidentiality.

4. Your obligations

You're responsible for having a lawful basis to collect scan analytics and for telling the people who scan your codes about it, for example in your own privacy notice. You mustn't use the service in a way that breaks data protection law.

If you use ad pixels, you're also responsible for mentioning retargeting and the ad platforms you use in your own privacy notice, and for your relationship with those platforms under your own accounts and their terms. You must have the right to publish anything you put in a hosted file, business card or page, including other people's contact details. If you add a form to a page, you're responsible for telling visitors how you'll use what they send, and for answering their requests about it. If you add an HTML embed or custom code to a page, you're responsible for it and for any data the services it loads collect from visitors, including mentioning them in your own privacy notice.

5. Subprocessors

You authorize us to use the subprocessors below. Each is bound by data protection terms that are at least as protective as this DPA, and we remain responsible for them. We'll update this list, and its date, at least 30 days before adding or replacing a subprocessor. If you object on reasonable data protection grounds, tell us. If we can't resolve it, you can close your account.

SubprocessorWhat it doesLocation
Vercel Inc.Hosting and network. Receives each request to a short link, including the visitor's network address, and works out approximate location.United States (requests first reach Vercel's nearest edge location)
Convex, Inc.Database, file storage and backend. Stores your codes, hosted files, business card details, pages, form responses and the visit records described below.United States
Resend, Inc.Sends account emails, such as password resets and alerts that name a code and its destination, and, if you turn them on, emails with each form response from your pages.United States
Stripe, Inc.Payments for Pro plans. Handles account holders' billing details only, never scan data.United States

Google Analytics measures visits to our own public website. It never receives data about people who scan your codes, so it isn't a subprocessor.

Meta, Google and TikTok aren't our subprocessors either. When you turn on ad pixels, the visitor's browser sends data to them directly, under your own accounts with them, because you chose to use them. We don't send them any data, and your agreements with them govern how they use it.

Google Fonts isn't a subprocessor. When a page uses one of its fonts, the visitor's browser requests the font from Google directly; we don't send Google any data. The same goes for YouTube, Vimeo, Spotify and Google Maps after a visitor taps an embed, and for services loaded by an HTML embed you add.

6. International transfers

Data is processed in the United States. Where personal data from the EEA, the UK or Switzerland is transferred to a country without an adequacy decision, the parties agree to the EU Standard Contractual Clauses (Commission Implementing Decision (EU) 2021/914), which are incorporated into this DPA by reference:

  • Module Two (controller to processor) applies, or Module Three (processor to processor) where you act for your own client.
  • Clause 7 (docking) doesn't apply. Under Clause 9, option 2 (general authorization) applies, with the notice period in section 5. The optional wording in Clause 11 doesn't apply.
  • Clauses 17 and 18: the law and courts of Ireland.
  • Annexes I and II are completed by sections 1, 2, 5 and 8 of this DPA.
  • For UK transfers, the UK International Data Transfer Addendum to the EU Standard Contractual Clauses applies. For Swiss transfers, the Clauses apply with the Swiss Federal Data Protection and Information Commissioner as the competent authority and references to the GDPR read as references to the Swiss Federal Act on Data Protection.

7. Liability and order of precedence

Liability under this DPA is subject to the limits in our Terms, except where the law or the Standard Contractual Clauses don't allow it. If this DPA conflicts with the Terms on data protection, this DPA wins. If it conflicts with the Standard Contractual Clauses, the Clauses win.

8. Security measures

  • All traffic to the service is encrypted in transit (HTTPS).
  • Data is stored with providers that encrypt it at rest.
  • IP addresses of visitors aren't stored, and visit-counting hashes are deleted after an hour.
  • Account passwords and code passwords are stored only as salted hashes.
  • Each account can only see its own codes and analytics.
  • Access to production systems is limited to authorized Outside The Box personnel.

Contact

Questions about this DPA or data protection: contact Outside The Box.