Security and data handling
How Rupert handles card payments, business records and access. Updated Nov 17, 2026.
Draft for review. This page has not yet been approved by CSP Cyber Security Pilot. Highlighted items are still to be filled in.
In short
- Rupert’s servers never receive, store or send full card numbers, expiry dates or security codes.
- Everything travels over HTTPS. Saved provider credentials and sensitive records are encrypted in the database.
- Backups are encrypted before they are written, and the server cannot decrypt them.
- Each business sees only its own workspace. Our support staff see it only when the business grants temporary access.
Card payments and PCI DSS
Rupert is business software, not a payment processor or gateway. Card payments are approved and settled by the merchant’s own payment provider under the merchant’s agreement with that provider.
- Online and keyed cards. Card details are typed into fields hosted by the payment gateway (Authorize.net Accept.js hosted fields; NMI Collect.js, test accounts only for now). The gateway returns a one-time token, and Rupert sends only that token to complete the sale.
- In-store card terminals. Terminal connections are semi-integrated: the card is read on the terminal, and Rupert sends the amount and receives only the result. A connection to Dejavoo counter terminals works on Dejavoo’s test system only; live terminal payments are switched off until the merchant’s processor approves the account and the owner signs off.
- Payments on a phone. The iPhone and iPad app has no card reader and takes no card payments today. A planned option hands the amount to the payment provider’s own app on an iPhone, which reads the contactless card and returns only the result. It is not available yet, and it will not work on iPad.
- What Rupert keeps. The sale, amount, tip and any fee, tender, approval result and approval code, the provider’s transaction and batch references, the card brand, the last four digits and how the card was presented. Nothing else from a payment result is stored: no first digits of the card, cardholder name, expiry date, card token or chip data.
- Confirmed with the provider. A terminal or payment-page sale is marked paid only after Rupert’s server confirms the payment with the provider. A result that arrives through a browser or an app by itself is never trusted.
- Logs. Card numbers, security codes and payment result fields outside that list are removed from request logs, error reports and chat before they are written.
Because the page that shows the hosted card fields is served by Rupert, it still matters for the merchant’s PCI DSS assessment. The PCI Security Standards Council expects merchants that embed a provider’s payment fields to protect the scripts on that page (PCI DSS requirements 6.4.3 and 11.6.1) and to run external vulnerability scans. Each merchant completes its own PCI DSS self-assessment every year. Using Rupert does not do that for you. Your payment provider tells you which self-assessment applies to your business.
Rupert does not currently hold a PCI DSS attestation of compliance, a SOC 2 report or a third-party penetration test report. We will say so here when that changes.
Encryption
- In transit: HTTPS only, with HTTP Strict Transport Security, for the website, the iPhone and iPad app and the API.
- At rest: provider tokens and credentials, imported bank and processor files, and other sensitive records are encrypted in the database with application-level encryption. Passwords are stored only as one-way hashes.
- Keys: database encryption keys are held on the server. They protect a copied database file, but they do not stop the people who run the infrastructure from reaching the data. Customer-held keys are planned.
Hosting and backups
Rupert runs on a dedicated server operated by CSP Cyber Security Pilot, in an isolated Linux container behind a web server that renews its TLS certificates automatically. Location: [Owner to add: server location (city/state or data centre) and any hosting provider].
- Every backup is encrypted before it is written. The server holds only the public key; the private key exists only in the owner’s offline recovery kit.
- Backups run on a schedule, from rolling snapshots every few minutes to six-hourly sets, with a copy kept outside the app’s container. Off-site copy: [Owner to add: whether a copy on a second machine or cloud storage is running]
- A backup is never written unencrypted. Restoring one needs the recovery kit, and the steps are documented.
Access control
- Each business has its own workspace. Records are scoped to that workspace, and tests check that one workspace cannot read another.
- Workspace administrators give each person a role, and the role decides which pages and actions they can use.
- Sign-in is with Google or with an email and password. Repeated failed sign-ins are locked out for a while. The iPhone and iPad app can also require Face ID.
- Our support staff can open a workspace only after the business grants temporary, read-only support access, which it can revoke at any time.
- Sign-ins and changes are recorded in the workspace’s activity history.
- Connecting Shopify, Square or any other provider is a separate step that a workspace administrator authorizes. Signing in to Rupert never connects anything on its own.
Availability
Rupert is monitored with automatic health checks, and an update that fails its checks is rolled back automatically. There is no public status page yet. [Owner to add: status page link, if you set one up]
We do not promise a specific uptime. Any service level is set out in your agreement with us.
Report a security problem
Email sdolbec@rupertpos.com with what you found and how to reproduce it. Please do not access other businesses’ data or disrupt the service while testing. We reply as soon as we can.
iPhone, iPad and Face ID are trademarks of Apple Inc., registered in the U.S. and other countries and regions. Other company and product names are trademarks of their owners. Rupert is an independent product: naming a company on these pages does not mean it sponsors or endorses Rupert.