QR Report Data Processing Agreement Effective date: 17 November 2026 This DPA and its annexes form part of the Terms. It covers processing customer data on instructions; the German version prevails. 1. Parties and conclusion The processor is WHITESPACE AS, Sævarevegen 30, 5628 Herand, Norway, organisation no. 916 934 424. The customer is the user acting in their own business capacity or the organisation they validly represent and for whose processing QR Report is used. A workspace is a technical unit and not necessarily a separate legal entity. Assignment follows the account and organisation details and electronic contract record. For agency-managed client workspaces, the agency is our contracting party; its instructions from the client and the required authorisations remain necessary. This DPA and its annexes are accepted together with the Terms during registration accompanied by the acceptance notice. No additional checkbox or separate signature is required. Acceptance covers later workspaces created with proper authority and assigned to the contractual relationship; creating them does not require renewed acceptance. Another organisation is bound only with valid representation or instructions. An invitation or membership alone does not replace this authority. The specified versions are available to read and download before acceptance and remain accessible in the user account’s contract area afterwards. Evidence includes user identifier, email, timestamp, signup or confirmation method, language and contract version. Email verification is documented separately. Assigned workspaces are recorded with their identifier, name at assignment, creating or authorised responsible person and assignment time. The assigned contract account’s email initially serves as the contact for data protection and subprocessor changes; the customer informs us of changes. Individually agreed terms take precedence. For data protection matters this DPA prevails over the other Terms. For existing customers, application of this version requires valid acceptance and assignment to the relevant contractual relationship. A technical legacy exemption does not replace acceptance and does not by itself establish new deletion rules. 2. Roles and instructions For the data in Annex 1, the customer is controller and WHITESPACE AS is processor. If the customer processes for another controller, WHITESPACE AS acts as subprocessor; the customer ensures the necessary instructions and authorisation throughout that chain. WHITESPACE AS’s own account, billing, support and security processing is separately covered by the Privacy Policy. We process customer data only on documented instructions, including for transfers. Instructions consist of this agreement, product configuration and documented additional instructions sent to support@qrreport.app (mailto:support@qrreport.app). We inform the customer before legally required processing unless the law prohibits notice. If we consider an instruction contrary to data protection law, we inform the customer immediately and suspend the affected instruction pending clarification. 3. Customer obligations The customer determines lawful purposes and legal bases, provides information to scanners and other data subjects, and issues only lawful instructions. It limits content, recipients and access rights to what is necessary. QR destinations must not contain special-category or criminal conviction data without a separate agreement. Merely linking to an external website does not mean we host or process its content. 4. Confidentiality and security We ensure persons authorised to process data are bound by confidentiality or an appropriate statutory duty. We implement appropriate measures under Art. 32 GDPR as set out in Annex 2. Changes must not reduce the agreed protection. Customer data is not used for advertising, data sales or training our own AI models. 5. Assistance and personal data breaches Taking into account the processing and information available, we assist the customer with data subject rights and obligations under Arts. 32–36 GDPR, including security, notifications, data protection impact assessments and prior consultation. We promptly refer direct requests concerning data processed on behalf of the customer to it, unless instructed or legally required otherwise. We notify the customer of a personal data breach without undue delay, at the latest within 48 hours after becoming aware of it, by email to the agreed contractual contact. Available details include nature, scope, affected data and people, likely consequences, countermeasures and a contact. Missing details follow without undue delay; the initial notification is sent within this deadline even while the investigation is ongoing and does not await its completion. The customer’s statutory deadlines are not extended. 6. Evidence and audits We make available all information necessary to demonstrate compliance with Art. 28 GDPR and allow and contribute to audits, including inspections, by the customer or its independent auditor. Confidentiality, security and reasonable scheduling apply without frustrating audit rights. This agreement does not represent that QR Report is certified. Routine audits should generally be coordinated 30 days ahead and take place once annually where suitable evidence is insufficient. Incident-driven or authority-required audits and mandatory rights are not limited by this arrangement. Each party generally bears its own costs; additional fees require prior agreement and may not frustrate audit rights. Statutory claims govern costs following established breaches. 7. Subprocessors and transfers The customer grants general authorisation for the subprocessors in Annex 3. We notify the contact identified in the agreement record directly by email at least 30 days before intended additions or replacements. The customer may object on data protection grounds within that period. We seek an appropriate solution; if none is found, the customer may terminate the affected service before the new provider is engaged. Silently updating the list does not replace notice. We impose the same relevant data protection obligations on subprocessors and remain responsible for their performance. Transfers outside the EEA take place only in compliance with Chapter V GDPR. We document recipients, transfer grounds and necessary supplementary measures and make that information available. This agreement does not treat Norway as a third country or replace any required, fully completed transfer agreements. 8. Retention, deletion and data return The DPA applies during processing on behalf of the customer, including the agreed retention for reactivation, and survives as needed for return, deletion and confidentiality. The end of a subscription alone therefore does not trigger immediate deletion. When the instructed retention also ends, or the customer requests earlier deletion, we delete the scan data under the paragraph on return and deletion further below in this section; there is no separate general scan-age limit. Scan data are retained during the contractual term unless the customer instructs a shorter period. The customer is responsible for necessity and storage limitation; WHITESPACE AS’s own statutory duties remain unaffected. No fixed general maximum age is agreed for individual scans. On instruction, we also delete scans for selected periods, such as all scans before a specified date. Instructions are currently sent by email to support@qrreport.app; an app feature may follow. When plan or trial access ends, the following organisation rules apply, subject to an earlier deletion instruction; the agreed retention remains part of processing on behalf of the customer. When that processing ends, scan data are deleted under the paragraph on return and deletion further below in this section. Scan events are retained to provide the agreed analytics. When a subscription ends, the organisation and its scans are initially retained for reactivation. An active subscription includes billing through an agency. While an organisation has active complimentary access (a comped plan as defined in Terms section 1), it is not automatically deleted because of inactivity or lack of payment. After paid use, organisations without either an active subscription or active complimentary access are deleted, including all scans, following a twelve-month retention period; notice of deletion is sent beforehand by email. For this purpose, paid use also includes one-off codes redeemed with a voucher, including a 100% discount. The period is based on the end of the subscription or, for organisations using only one-off codes (including those redeemed with a voucher), the expiry of the last code. Only after paid use may the customer actively request a further twelve months of retention at a time, free of charge. The active request for a free extension may be sent to support@qrreport.app; we confirm the new retention end date. Organisations with no previous paid use as defined above and no active complimentary access are deleted, including all scans, following a 30-day retention period. The starting point is the end of the trial or, if there is no trial, the creation of the organisation. Notice of deletion is sent beforehand by email. These organisations are not eligible for a free extension; data are only retained beyond this period through paid use as defined above, for example a subscription or the purchase of at least one one-off code. Neither organisation retention period starts before 1 October 2026, when the contract version that introduced these periods took effect. Each period starts on the later of the starting point described above (trial end or, without a trial, creation of the organisation; after paid use, subscription end or expiry of the last code) and 1 October 2026. Earlier end dates therefore do not result in periods that have already expired retroactively. When the customer deletes an organisation, associated scans are deleted from the live system with it. Organisation periods are not individual scan-age limits. We reserve the right to further reduce older data; no future aggregation or anonymisation is promised. At the end of the instructed processing, we return personal customer data in a commonly used electronic format before deletion or delete them, at the customer’s choice, including existing copies unless law requires retention. Export and deletion may be requested at support@qrreport.app. Any required restricted retention will be explained to the customer. Live deletion and backups are distinct: existing database backups may contain deleted data until normal backup expiry. They serve recovery rather than further analytics; immediate physical removal of individual records from every backup is not promised. Following restoration, prior deletion instructions must be reapplied before the affected data resume normal processing. Annex 2 describes backup scope and the confirmed technical state. 9. Liability and law The Terms’ provisions apply only insofar as mandatory data protection law permits. Data subject rights and supervisory powers remain unaffected. DPA changes are documented; material processing changes require effective agreement. The German version prevails. Annex 1 Processing details Subject and purpose: QR code management, redirection, scan analytics, organisation access and requested report delivery. Operations: collection, storage, organisation, analysis, provision, transmission and erasure. Duration: active use plus the retention, return and deletion periods agreed in section 8. Data subjects: scanners, users authorised by the customer and report recipients, and people whose data the customer includes in stored content. Data types: QR destination URLs and content, names and email addresses where instructed, organisation references, scan timestamps, pseudonymous daily identifiers, device/browser/operating system categories, referring hostnames and IP-derived location data including coordinates rounded to one decimal place. The technical legacy cleanup of previous IP hashes and full user-agent strings is described in Annex 2. IP addresses and user-agent strings are processed for technical connections and identifier generation; new scan records store neither IP addresses nor IP hashes nor full user-agent strings. Retention and deletion: scan data during the contract unless the customer instructs shorter retention; selected periods may also be deleted on email instruction to support@qrreport.app. Section 8 alone governs retention, return and deletion, including after termination. Annex 2 explains the daily identifier technology. When processing on behalf of the customer ends, deletion follows section 8. Annex 2 Technical and organisational measures HTTPS/TLS transport, Supabase Auth, organisation-scoped database policies and server-side role checks. Privileged database keys are used server-side. The operator has confirmed MFA for administrative accounts at Vercel, Supabase and AhaSend and the administration/recovery email account. The identifier changes daily at 00:00 UTC. It estimates unique visitors within the same day and organisation, including across codes and campaigns. Multi-day figures sum daily estimates rather than reliably identified people. Shared networks and device changes can distort the estimate. Records also include device categories, referring domain and available IP-derived location data (country, region, city, timezone and coordinates rounded to one decimal place). This is not a guarantee of a fixed kilometre radius or city-level precision. We do not treat these data as automatically anonymous. The identifier is computed server-side from organisation, IP address and browser, operating-system and device categories with a secret, independently generated daily key. The computation does not log these inputs or the key. New scans store no additional IP hash or full User-Agent. Referring URLs are reduced to hostnames. Coordinates are rounded to one decimal place; precision and reliability vary. Campaign figures follow current code assignments. Organisation figures deduplicate across codes within the UTC day rather than sum campaign totals. Matching daily identifiers remain linkable within stored scans. Key rotation does not delete events or automatically anonymise them. An hourly job at minute 10 removes keys for past UTC days from the active database, normally first at 00:10 UTC the following day or after failure on the next successful run. The application cache stops using a key ten minutes after its UTC day ends and removes expired entries on the next access. Physical memory erasure at an exact instant is not promised. Key copies may remain until database backups expire. For older scans, the daily legacy cleanup removes former IP hashes and full User-Agents after 30 days. It does not delete new daily identifiers or rounded coordinates. This technical legacy cleanup is not a general scan-age limit or a promised future aggregation process. Supabase creates a daily physical database backup with normally seven days of recovery history. These backups contain Storage metadata but not uploaded files/logos. No additional automated file/logo backup is currently configured; deleted files cannot be recovered from database backups. Customers should retain originals separately. Annex 3 Subprocessors The table identifies subprocessors for instructed processing. Public provider terms: Vercel DPA (https://vercel.com/legal/dpa), Supabase DPA (https://supabase.com/legal/dpa), AhaSend DPA (https://ahasend.com/dpa). Plausible processes our own website statistics; Polar acts independently for purchase/invoice data. Google OAuth concerns login. These services are not generally subprocessors for customer scans; their roles and transfers are described in the privacy notice. Provider | Purpose / role | Location | Transfer / evidence Vercel Inc. (Delaware, USA) | Website, functions, QR redirects; processor for customer data | Primary processing facilities in the US according to provider; our functions: Frankfurt, Dublin, Paris, Stockholm; worldwide edge delivery | EU–US Data Privacy Framework (DPF), Vercel is certified; supplemented by Standard Contractual Clauses (SCCs), Modules 2 or 3 for processing on instructions depending on the role, in the Vercel DPA (https://vercel.com/legal/dpa). The DPA covers Pro/Enterprise; we use Pro. Supabase Pte. Ltd. (Singapore) | Database / Auth / Storage; processor | Database Frankfurt; subprocessors and support may be in other countries according to the provider list (https://supabase.com/legal/customer-resources/subprocessor-list) | SCC Modules 2 or 3 depending on the role, incorporated through the Supabase DPA (https://supabase.com/legal/dpa) forming part of the agreement. Transfers to Supabase Pte. Ltd. in Singapore do not rely on the EU–US DPF. AhaSend B.V. (Amsterdam, Netherlands) | Transactional and report email; processor | DPA lists Hetzner (Germany/Finland), DA International Group / AlphaVPS (Bulgaria), Blix Solutions (Norway); US infrastructure optional at customer choice; recipient mail servers worldwide | EEA processing; for any third-country transfers, the AhaSend DPA (https://ahasend.com/dpa) provides for adequacy decisions including DPF for certified US recipients, or SCCs with necessary supplementary measures, depending on the recipient.