Security

The controls that protect your store and your buyers.

Selling online means handling a stranger's payment and a growing list of people who trusted you with their details. This page describes the specific controls TapToBuy has in place today — no badges, just what the platform does.

Read the privacy policy

Payments and data

Card details never touch TapToBuy.

Payments are processed securely by Stripe. Buyers enter their card on Stripe's checkout or pay with Stripe Link or Apple Pay, so raw card numbers are handled on Stripe's PCI-compliant infrastructure rather than stored on TapToBuy's servers.

Traffic to TapToBuy is served over HTTPS, and the site sends a Strict-Transport-Security header so browsers keep using an encrypted connection. Newly stored calendar credentials, such as the tokens that connect your Google or Office 365 calendar for bookings, are encrypted with AES-256-GCM before they are stored; older tokens are encrypted when they are next refreshed or reconnected.

Card data stays with Stripe

Card numbers are entered on Stripe's infrastructure, so they never have to live in TapToBuy's systems or yours.

HTTPS everywhere

Data moving between buyers and the platform is encrypted in transit, with HSTS telling browsers to insist on HTTPS.

Encrypted tokens

Calendar connection tokens are encrypted with AES-256-GCM at the application layer before they reach the database.

Privacy controls

Controls for your visitors and for you.

Visitors from the EEA, the UK, and Switzerland see a cookie choice before analytics runs, and anyone can change that choice later from the cookies page. Account data export and account deletion are built into the platform, so a request to take your data with you, or to remove it, is handled by the product rather than by hand.

Cookie consent

In the EEA, the UK, and Switzerland, analytics stays off until a visitor turns it on, and the choice can be withdrawn at any time.

Account data export

Request an export of your account data — products, orders, and customers — as a single file, so your customer list stays yours.

Account deletion

A built-in deletion flow closes your account and removes or anonymizes the personal data tied to it.

Rate limiting

Signup, member sign-in, password reset, data export, account deletion, and other sensitive endpoints are rate limited to slow down brute-force and abuse.

How it fits together

Protection and ownership in one flow.

  1. 1

    A visitor arrives

    The page loads over HTTPS. Where the law requires it, analytics waits for the visitor's cookie choice.

  2. 2

    A buyer pays

    Payments are processed securely by Stripe, so card details stay on Stripe's infrastructure.

  3. 3

    A sale is recorded

    The order and the buyer are added to a customer list that belongs to you.

  4. 4

    You stay in control

    Export your account data or delete your account whenever you decide to.

Sell on a platform that keeps card data out of your hands.

Payments are processed securely by Stripe, traffic is encrypted in transit, and your customer list stays yours to export.