How we protect your shop’s data.

01Card payments

Every card payment on VantaPay is taken by Stripe, a PCI DSS Level 1 service provider. The card form on a booking page, a payment link or an invoice is Stripe's own, so the card number goes from the customer's device straight to Stripe and never passes through our servers. VantaPay does not store card numbers or security codes anywhere. Shops are paid out through Stripe Connect, to the bank account they give Stripe.

The AI phone line does not take cards. If a caller starts reading one out, the line stops them and sends a secure Stripe link instead, and anything that looks like a card number is masked in the call transcript before it is saved. The live audio of the call still passes through the speech providers listed below while the caller is talking.

02Where data lives, and who can see it

The application and its PostgreSQL database run on servers we operate in Amazon Web Services, in the us-east-1 region (Northern Virginia, United States). Traffic reaches them only through Cloudflare.

• Shop by shop. Row-level security rules in the database, and a check of the person's shop and role on every server request, keep each shop's team inside that shop's own records.
• Inside a shop. The owner decides what each team member can see and do, and what Vanta AI, our built-in assistant, is allowed to do.
• The most sensitive files. ID photos and signatures from consent forms sit in private storage. They have no public address: each view uses a link signed for that person, and the link expires.
• Our own access. Server access is limited to a single network address and a key, and the cloud account requires multi-factor sign-in. We look at a shop's data only to support that shop or fix a fault.

03Encryption

• In transit: HTTPS (TLS) between browsers or apps and Cloudflare, and an encrypted connection from Cloudflare to our servers.
• At rest: the server disk and its daily snapshots are encrypted by AWS, and every backup is encrypted before it leaves the server.
• Keys we hold for you: access tokens for a connected Facebook Page are encrypted in the database and never sent to a browser. Access keys for connected AI assistants are stored only as one-way fingerprints, so a copy of the database holds no working key.

04Backups and availability

The database is backed up every hour and in full, with files, every night. Each backup is encrypted and copied to separate storage that the server itself can write to but not delete from, and every copy is kept for at least 30 days. The server disk is also snapshotted daily and the last seven are kept. Restoring a backup onto a fresh database was tested on October 4, 2026, and alarms tell us when a backup is late or the site stops answering.

Today the service runs on a single server in one AWS region. If that region has an outage, VantaPay is down until it recovers or we rebuild from the backups.

05Subprocessors

These companies process data for us so the platform can work. They receive only what their part of the service needs.

Some connections are made by the shop itself, not by us, and the shop's own agreement with that company applies: a Facebook Page or Instagram account (Meta); an AI assistant the shop uses under its own account, such as ChatGPT or Claude. The Privacy Policy covers what each one receives.

08Request our security policies

If you are a customer, or about to become one, and need our policies for a security review, ask for them by email. Write from your company address and tell us which business you are. They are available in English and Spanish:

1. 01Information security
2. 02Access control and least privilege
3. 03Change management
4. 04Incident response
5. 05Backup and business continuity
6. 06Vendor management and subprocessors
7. 07Data retention and deletion
8. 08Encryption
9. 09Acceptable use
10. 10Risk register