Data Processing Agreement(Draft)

Your agency decides why and how your travelers’ personal data is used (you are the controller). Quobo Labs processes it only to run Quobo for you (we are your processor).

[Placeholder — final wording to be supplied: formal definitions and the order of precedence with the Terms of Service.]

Depending on what you collect, this can include:

• travelers’ names, email addresses, phone numbers and mailing addresses;
• dates of birth, passport numbers and other travel documents;
• booking, cabin, payment and message history;
• your team’s names and email addresses.

[Placeholder — final wording to be supplied: duration of processing and the complete categories of data subjects and data.]

• Every record belongs to one agency, and the database itself refuses to show it to any other agency.
• Secrets and sensitive fields are encrypted with a key that belongs to your agency alone.
• Documents your travelers upload are private and opened only through short-lived links.

[Placeholder — final wording to be supplied: the full list of technical and organisational security measures.]

Today Quobo runs on these services:

• Supabase — database, sign-in and file storage
• Vercel — hosting
• Stripe — payments (through your own Stripe account)
• Resend — sending and receiving email
• Anthropic — AI features: the Console’s assistant, suggested replies, Home’s briefing, sorting incoming messages, reading documents and feedback summaries (your owner can switch these off in Settings, under AI assistant), and Studio’s marketing copy
• Google (Gemini) — Studio’s marketing images, from trip details and pictures you choose, not traveler records
• Sentry — error reports, with personal data removed before sending

[Placeholder — final wording to be supplied: sub-processor locations, how you are told about changes, and your right to object.]

[Placeholder — final wording to be supplied: breach notification timelines and what we will tell you.]

[Placeholder — final wording to be supplied: assistance with access, correction and deletion requests from your travelers.]

[Placeholder — final wording to be supplied: where data is stored and the transfer mechanisms relied on.]

[Placeholder — final wording to be supplied: return or deletion of data at the end of the agreement, and timelines.]

[Placeholder — final wording to be supplied: how you can verify compliance.]