Privacy Policy
Effective date: 16 November 2026
At a glance
WHITESPACE AS in Norway (EEA) is responsible for the website, accounts and its own business operations. It provides QR Report as licensee.
We use necessary login and language cookies, but no analytics or advertising cookies. Public website statistics use Plausible and are separate from QR scan analytics.
For QR scans, the customer is controller and we process on its instructions. Records include pseudonymous daily identifiers, device categories and IP-derived location information. New scan records contain neither raw IP addresses nor full browser strings; infrastructure logs are separate.
The customer determines the necessary retention of its scan data. DPA section 8 governs storage and deletion. The database is in Frankfurt; this does not mean that all provider processing takes place exclusively in Europe.
Owners and admins can allow AI agents such as ChatGPT, Claude or Grok to access their organisation’s data. The feature is off until it is switched on; details in section 6a.
Privacy contact and data subject rights: support@qrreport.app.
1. Controller and contact
WHITESPACE AS, Sævarevegen 30, 5628 Herand, Norway, organisation no. 916 934 424. Contact for privacy, access and erasure requests: support@qrreport.app. We act as controller for account administration, our own support, security and business relationship management. Roles for scan analytics are explained in section 6.
These notices cover the website, user accounts and service, including agreed tests. For scan data and customer content, the roles described in section 6 apply.
2. Infrastructure and recipients
Vercel operates the website, server functions and redirect service. Supabase provides the database, authentication and file storage; the product database is located in Frankfurt (EU). AhaSend sends transactional emails, including contact enquiries, authentication, invitations and reports. Our email sending does not enable open or click tracking. Recipient mail servers process delivered messages under their own responsibility.
Polar Software, Inc. sells paid products as merchant of record and processes purchase, billing and tax information as an independent controller. This includes email, company name, billing address, tax identifiers and payment information. We receive purchase and status information needed to provide access and manage subscriptions, but no full payment card details. See also Polar’s privacy policy.
When you sign in with Google, the account information required for OAuth is exchanged between Google, Supabase and QR Report. Font files are served through our own website; your browser does not need to connect to Google Fonts to load them. Disclosures may also be made to competent authorities where legally required or to establish or defend legal claims. Section 6b applies to place search and pasted Google Maps links for map codes.
3. Account and legal bases
We process your email, profile information, credentials through our authentication provider, organisation details and memberships to provide the service. The legal basis is Art. 6(1)(b) GDPR where you are the contracting party; for employees or other representatives of a customer organisation it is Art. 6(1)(f) GDPR (the interest in providing and administering business access). Required fields are necessary to create the account.
We handle support requests to perform the contract or pursue our legitimate interest in responding to enquiries (Art. 6(1)(b) or (f) GDPR). Technical access and error logs support secure operation and troubleshooting (Art. 6(1)(f) GDPR); infrastructure providers’ logs may contain IP addresses. We process legally required business records under Art. 6(1)(c) GDPR.
To document contract acceptance, we record the account ID, email address, acceptance and verification times, acceptance method, language and contract version, plus the assignment of workspaces created with appropriate authority. Records support contract performance and legal claims (Art. 6(1)(b) or (f) GDPR). They may be required beyond account deletion and are retained only as long as needed for those purposes. An operational exception for an existing account is not evidence of acceptance.
4. Contact form and email
When you contact us, we process your email address, message and name if you provide it. The form requires your email address and message so we can answer your enquiry; your name is optional. Sending an enquiry does not create an account or subscribe you to a newsletter.
We use these details to handle your enquiry and related follow-up questions. The legal basis is Article 6(1)(b) GDPR for enquiries about a contract with you; for other enquiries or when you act for a business, Article 6(1)(f) GDPR applies (our legitimate interest in responding to business enquiries).
Vercel processes the form and AhaSend delivers the message to our business mailbox. Our email provider also processes the message for delivery and mailbox storage. Technical request identifiers and hashed IP-related counters held briefly in memory help prevent spam and repeated submissions (Article 6(1)(f) GDPR). Messages are sent without open or click tracking.
We retain contact enquiries for as long as needed to handle them and necessary follow-up questions. We then delete them unless statutory retention duties or specifically necessary legal claims justify longer storage.
Our business mailbox is operated by Proton AG, Geneva, Switzerland (Proton Mail). Processing locations: Switzerland, Germany or Norway according to the Proton Mail privacy policy. Section 8 describes transfers.
5. Cookies and local storage
We use login and language cookies and local or session storage for settings and interrupted workflows. We do not use analytics or advertising cookies; QR scan redirects set no analytics cookies of their own.
5a. Public website statistics
We use Plausible Analytics, provided by Plausible Insights OÜ, Estonia, for statistics on our public website. Plausible records page views, referral sources, visit duration and scroll depth, device type, browser and operating system, and approximate location (country, region, city). We also count selected events, such as clicks on buttons and links, opening and sending the contact form, completed registrations and downloads. With an event, we send at most fixed details, such as which button was clicked or where a link leads, but no information about you, such as form contents, names or email addresses. We do not measure pages inside the app or QR redirects; the only exception is the notice that a registration has been completed.
Plausible sets no cookies and stores no persistent device identifiers. A daily-changing identifier is derived from the IP address and browser information; according to the provider, the IP address and browser information themselves are not stored. According to the provider, the data are processed exclusively in the EU. Plausible stores the individual page views and events; we see aggregated statistics derived from them. We send page addresses without query parameters; the only exception is the campaign (UTM) parameters in our own ad and campaign links, in which we do not use personal data. Referral sources are sent as the domain only. See Plausible's data policy for details.
The purpose is statistical evaluation and improvement of our public website. Where personal data are processed, the legal basis is Article 6(1)(f) GDPR; our legitimate interest is improving our public information offering. Section 9 explains objection rights.
6. QR code scans and customer content
When a QR redirect URL is requested, we process time, code and organisation identifiers, IP address and browser string. Together with broad device, browser and operating-system categories, these are used to create a pseudonymous daily identifier per organisation. New scan records contain neither the IP address nor a stable IP hash or full User-Agent. Infrastructure logs may separately contain connection data.
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. Technical details are in DPA Annex 2.
For customer scan analytics, the customer is controller and determines purpose, legal basis and necessary retention; WHITESPACE AS is processor. In agency chains, the customer may itself be processor and WHITESPACE AS subprocessor. DPA section 8 governs retention and deletion instructions. Our own security processing is separate. Scanners do not need an account with us.
The customer provides the required information to scanners and obtains required consent. UTM parameters may be appended to the destination URL. Its operator is responsible for destination-site analytics and required consent; redirection does not replace these obligations.
6a. AI agents
Owners and admins of an organisation can allow AI agents, for example ChatGPT, Claude or Grok, to access that organisation. The feature is off for every organisation until an owner or admin switches it on. An agent only gets access to organisations that an owner or admin has expressly granted for that connection; a grant can be withdrawn at any time. What the agent may do depends on the organisation’s setting; currently only reading is possible. The consent page shows which service is requesting the connection.
The agent can read: the organisation’s name, short name and timezone and the user’s own role; QR codes with name, short URL, destination URL, status and campaigns; campaigns with name, period and number of codes; scan counts and estimated visitors as totals and time series; also the image of a QR code with its stored design and logo, as in the QR Report download. We do not pass individual scans, IP addresses, device or location data or information about members to agents. Names and destination URLs contain whatever the customer entered there.
The customer chooses and connects the service. Its provider receives the retrieved data because the customer connected it, and processes them under its own terms and privacy notice. It is not a subprocessor of WHITESPACE AS. The provider may be located outside the EEA; the transfer results from the connection the customer establishes. For the data delivered to the agent, we act as the customer’s processor (section 6).
To operate and secure the connection, we process as controller: the user account, the connected service, the granted organisations and the times of the connection; access keys only as a hash; a log of sign-in, grant, revocation and every retrieval (user, service, tool, organisation, number of records, result, time), without the retrieved content. For rejected connection attempts, we also store the shortened program identifier (User-Agent), but no IP address. To protect against abuse, we count requests per IP address only through a check value derived with a secret key, not through the IP address itself. Owners and admins see which members have connected their organisation to which service. The legal basis is Art. 6(1)(b) GDPR where you are the contracting party, otherwise Art. 6(1)(f) GDPR (providing the access the customer wants); for logs and abuse protection, Art. 6(1)(f) GDPR (secure operation and traceability).
A connection ends 90 days after consent at the latest, earlier if the agent does not use it for a longer period, and immediately when it is revoked in QR Report or when you change your password. An organisation drops out of the connection when you leave it, when you are no longer an owner or admin there or when it switches AI agents off; once no organisation is granted any more, the connection ends. We delete access keys and codes no later than seven days after expiry or revocation, abuse-protection counters one hour after the counting window ends, and the log after twelve months. We delete ended connections twelve months after they end.
6b. Place search and Google Maps links
(1) For map codes you can search for a place or paste a link from Google Maps. When you type a place name or an address, our server sends the search text to the Google Maps Platform and shows you Google’s suggestions. When you paste a share link from Google Maps, our server requests this link from Google once to read the place. So that you can see which place was chosen, our server uses Google’s identifier for the place to request its address and, where needed, its name from the Google Maps Platform, also when you edit a code. Google only receives the search text, the link or the place identifier, the address of our server and technical details such as the language, and for a search also a random identifier for that single search. Google does not receive your IP address, your account data or scan data.
(2) Google Ireland Limited processes this data as an independent controller, for the search and place details under the Google Maps Platform terms, and in each case under Google’s privacy notice. Google is not our processor for this. The search is optional; you can enter a link or coordinates instead.
(3) We only store the destination you choose for the code: for a search, your search text and Google’s identifier for the place; for a pasted link, the place from that link. We do not store names or addresses that we show you from Google. Only enter names or private addresses of private individuals when the code needs them.
(4) The legal basis is Art. 6(1)(b) GDPR where you use the feature as our contracting party, otherwise Art. 6(1)(f) GDPR. Our legitimate interest is a simple and precise choice of place for map codes.
7. Retention and deletion
As controller, the customer determines how long scan data are necessary for its purpose. As processor, we retain and delete on its instructions. Details, including deletion of selected periods and post-contract rules, are governed exclusively by DPA section 8. Technical measures are described in Annex 2.
Our own account, contract and support data are retained only as needed for service provision, handling requests, legal obligations or specifically necessary legal claims. Account deletion can be requested at support@qrreport.app. Section 4 applies to completed contact enquiries; no fixed general period has been set.
Provider logs: Vercel retains runtime logs for one day on our Pro plan without Observability Plus. Supabase Pro retains API and database logs for seven days. These periods cover the specified log categories, not all provider security or billing data. AhaSend applies the purpose-specific periods in its privacy notice; for its own server logs containing IP addresses for security and operational purposes, AhaSend specifies one month. This is not a general period for email content or delivery metadata; their retention depends on the agreements and settings applicable to email delivery.
Retention periods for connections with AI agents are set out in section 6a.
Website statistics: up to five years on the Plausible Business plan. If the website is removed from Plausible sooner, its statistics are deleted earlier. The provider may also delete data earlier after the Plausible subscription ends.
Business mailbox: emails are retained until the matter and necessary follow-up enquiries are resolved. Correspondence relating to accounting or contracts is subject to the applicable statutory retention periods; other emails are then deleted unless specifically necessary legal claims justify longer retention.
Statutory business records: under section 13 of the Norwegian Bookkeeping Act (bokføringsloven), primary accounting records, such as accounting vouchers and annual accounts, are generally retained for five years after the end of the financial year. Supplementary records subject to retention, such as certain contracts and business correspondence, are generally retained for three years and six months after the end of the financial year; where they themselves serve as accounting vouchers, the primary-record period applies. Specific legal duties or authority orders may require longer periods. Polar issues customer invoices as Merchant of Record; our own accounting and record-keeping duties remain.
Database backups are separate from live data; DPA section 8 explains their treatment for customer data deletion.
8. Transfers outside the EEA
Norway belongs to the EEA. An EU database location is not a promise of exclusively European processing. The table distinguishes providers, purposes and possible non-EEA access. Copies of applicable safeguards may be requested from our privacy contact.
9. Your rights
Subject to the legal conditions, you have rights of access, rectification, erasure, restriction and portability (Arts. 15–20 GDPR). You may object on grounds relating to your particular situation to processing under Art. 6(1)(f) GDPR (Art. 21 GDPR). You set up your objection to website statistics on the opt-out page, which sets the plausible_ignore entry in your browser. Where processing relies on consent, you may withdraw it for the future. Please contact support@qrreport.app. We verify entitlement and generally respond within one month, notifying you within that period of any legally permitted extension.
For scan data, we assist the responsible customer in handling your request. Where possible, provide the QR link and approximate scan time so the request can be routed appropriately. You may complain to Norway’s Datatilsynet or a competent supervisory authority, including one at your habitual residence in the EEA.
The described service does not make solely automated decisions about individuals with legal or similarly significant effects within Article 22 GDPR.
10. Changes
We update this notice when processing changes and appropriately inform affected account holders of material changes. The effective date stated above applies.