Subprocessors
Five companies are involved in getting an invoice from your screen to your customer’s bank. Here is what each one receives, rather than a sentence saying they provide services to us.
Google Cloud (Firebase)
Hosting, database, file storage, functions and sign-in
Everything the platform stores: your workspace, businesses, customers, invoices, payments and the audit log. Files you upload, such as a logo. Sign-in credentials are handled by Identity Platform and never reach our own code.
TranzPay
Card and bank payment gateway
The card or bank details your customer types on the pay page, the amount, and the reference for the invoice being paid. They are the only party that receives a full card number; we store a vault reference, the last four digits and the card type.
Resend
Transactional email
The email address you are sending an invoice to, the message, and the attachment. Nothing about your other customers travels with it.
Twilio
SMS delivery and phone verification
The phone number a message goes to and its text, and the number being verified during sign-in. Consent and STOP handling are per business.
Google (Gemini)
The AI Studio
Only what a specific request needs, and only when you make one — a template brief, the line description you are rewriting. It runs server-side; the key never enters a browser, and the model returns schema-validated JSON that is discarded if it does not fit.
What none of them gets
A full card number is never stored, by us or in our database — it exists inside the charging function while it runs and nowhere else. No analytics script runs on the pay page at all; its content-security policy forbids one, so it is not a setting anybody can change by accident.