The third-party companies that process personal data on ScanOrbit's behalf, what each one receives, and where. We'll update this page before adding a new subprocessor.
1. Supabase (on Amazon Web Services)
What for: database, sign-in, file storage and the backend that runs ScanOrbit.
What it receives: all account data, including names, email addresses, QR codes and their content, uploaded images and files, business cards, contacts and form responses, team details, and scan analytics.
Where: United States (AWS us-east-1, N. Virginia).
2. Vercel
What for: hosting the website and dashboard, and handling the redirect behind every QR code scan.
What it receives: request details for visits and scans, including IP address and browser information, which Vercel uses to serve the request and to provide approximate location.
Where: United States, with a global edge network.
3. Brevo
What for: sending email (welcome and security emails, team invites, receipts, lead alerts, weekly digests).
What it receives: the recipient's name and email address and the content of the email.
Where: European Union (France).
4. Razorpay
What for: taking payments for paid plans.
What it receives: billing name and email, the plan and amount, and the payment details you enter on Razorpay's own payment page. ScanOrbit never receives full card numbers.
Where: India.
5. Google (only if you choose Google sign-in)
What for: signing in with your Google account.
What it receives: Google already holds your account; it tells ScanOrbit your name and email address when you sign in.
Where: United States.
6. goQR.me (QR image service)
What for: drawing the QR code image inside business-card setup emails.
What it receives: the card's public scan link only, when the recipient's email app loads the image. No names or email addresses.
Where: Germany.
7. Not our subprocessors: pixels you add
If an account owner adds retargeting pixels (such as Meta, Google or TikTok) to their QR codes, those companies receive data from that owner's scan pages under the owner's own agreement with them. They aren't ScanOrbit subprocessors, and the owner is responsible for them.
Questions regarding Subprocessors?
hello@scanorbit.app