Trust
Data processing agreement
For schools and businesses whose codes are scanned by the public: what the agreement covers, and how to sign it before your first invoice.
Who does what
Your organisation decides what its codes are for; qurl processes the scans on your behalf. The agreement says so, and says we only use scan data to run your codes and show you your figures.
What it covers
- The data: the time, code, rule, destination, rough area and type of phone for each scan. No IP addresses and no profiles.
- How long: each scan for 35 days, then only totals, by the hour for 13 months and then by the day; a closed workspace deleted within 30 days, and from backups within a further 35 days.
- Where: stored in Finland, in the EU; scans sent on by Cloudflare under UK-approved safeguards.
- Sub-processors: listed below.
- Breaches: we tell you without undue delay, and within 48 hours of becoming aware of one.
How to sign it
On the School plan, the agreement and the list of sub-processors will be ready to sign from your account before your first invoice. A UK privacy lawyer is reviewing the agreement now, and qurl isn’t taking payment yet.
Sub-processors
- Hetzner, Finland: runs the servers and stores scan records and accounts.
- Google Cloud, Belgium: keeps encrypted database backups for 30 days.
- Cloudflare: sends scans on to their destination.
- Google Web Risk: the lists of known harmful sites that every destination is checked against. Nothing about the person scanning is sent to it.