Sub-processors
Last updated 11 August 2026
The suppliers we rely on to run QRtub, what each one does, and where it operates.
Running QRtub means using a handful of other services. Each one below may handle personal information on our behalf, and each is bound by contract to protect it and to use it only for the purpose described.
This page is part of our privacy policy. It is kept separate so it stays accurate as suppliers change.
| Supplier | What it does | What it may handle | Where |
|---|---|---|---|
| Supabase | Database, authentication and file storage — the core of the service | Account details, your content, uploaded images | AWS ap-southeast-2 (Sydney, Australia) |
| Vercel | Application hosting and content delivery | Request data in transit, standard server logs | United States, with global edge delivery |
| Stripe | Subscription billing and payments | Billing name, email, payment details — held by Stripe, never by us | United States, Ireland |
| Resend | Transactional email — sign-in links, invitations | Recipient email address and message content | United States |
| Upstash | Rate limiting on sensitive actions | IP address, held briefly and expiring automatically | Regional, currently Asia-Pacific |
| Slack | Internal error and operational alerts so we can fix faults | May include an account email address or user identifier in an error report | United States |
| Logo.dev | Fetching a website icon when you add a link, so buttons look right | The website domain you entered. No personal information | United States |
What is not on this list
There is no analytics provider, no advertising network and no tracking service, because QRtub does not do those things. We do not record who scans your codes, so there is no supplier processing that information — it does not exist.
Changes
If we add or replace a supplier that handles personal information, we will update this page. Business customers with a data processing agreement can ask to be notified in advance — email hi@qrtub.com and we will add you to the list.