Straight answers for owners, buyers and IT people: how data is encrypted, how cards are handled, which vendors we use and how to report a problem. Last updated October 11, 2026.
Data is encrypted while it moves and while it is stored.
Every page, app screen and API call uses HTTPS (TLS). Browsers are told to always use HTTPS on topospos.com and its subdomains (HSTS, one year). Our servers reach the database and every vendor below over encrypted connections, and the database refuses unencrypted ones.
App data (bookings, clients, sales and staff records) is stored with Netlify, which encrypts data at rest with AES-256 or stronger. Marketing contact records live in a Neon Postgres database, which encrypts them at rest with AES-256. Call recordings and transcripts are kept on our phone server's disk in Google Cloud (us-east1, United States), which Google encrypts at rest with AES-256 by default.
Card payments run on Stripe, a PCI DSS Level 1 service provider, the highest level of card security certification. When a customer taps, dips or types a card, the number goes from the card reader or Stripe's own payment form straight to Stripe. The full card number never reaches topos's servers, database or code. We keep a record of each payment (amount, date, card brand and last four digits) so the shop can give receipts, refunds and reports.
These are the outside services (subprocessors) topos uses to run the product, and what each one touches.
| Vendor | What they do for us | Data they handle |
|---|---|---|
| Netlify | Hosting, server functions and data storage | All app data: bookings, clients, sales, staff records |
| Neon | Postgres database | Marketing contact records: name, email, phone |
| Stripe | Card payments online and on the in-shop card readers, memberships | Card details (Stripe only), name, email, amounts |
| Resend | Email delivery: receipts, booking confirmations, reports | Email address and the message |
| Anthropic | AI features: website chat, message summaries, reading expense receipts | Only the text or image sent to that feature |
| OpenAI | Clem, the AI phone assistant: its voice on calls and the notes it writes after a call | Call audio and transcripts, and the booking details Clem looks up during the call |
| Google Cloud | The phone system server we run for shop lines and Clem: call routing, call recordings and transcripts | Call audio, call recordings, transcripts and phone numbers |
| VoIP.ms | Shop phone lines and text messages, where a shop uses them | Phone numbers, call and text records |
| Twilio | Text messages and click to call, where a shop uses them | Phone numbers, call and text records |
We update this list when it changes. We do not sell shop or customer data.
topos runs on managed cloud services: Netlify for the apps, website, server code and app data, and Neon for marketing contacts, plus one phone server we run on Google Cloud for shop phone lines and Clem, our AI phone assistant. Clem's voice runs on OpenAI. Each provider runs its own redundancy and publishes live status.
Our terms set a 99.9% monthly uptime target, with bill credits if a month falls below 99.5% (section 11 of the terms). We do not publish a measured uptime figure yet. When we do, it will come from real monitoring, not a guess.
Found a weakness in topos? Tell us. Include what you found, the steps to reproduce it and the page or app involved. We aim to reply within 3 business days and will keep you posted until it is fixed.
Machine-readable contact details are at /.well-known/security.txt.
If we confirm a security incident that exposes your shop's data, we tell you within 72 hours of confirming it, explain what happened and help with any notices you need to send (section 11 of the terms).
topos has not completed a SOC 2 audit yet. We run our security program against the SOC 2 criteria and keep this page current. Need a security questionnaire filled in? Email security@topospos.com.