Security, reliability & trust

Your data, exportable any time. No hostage games.

Reliability and lock-in are the two complaints we hear most from stores leaving their current system. So we published a status page, wrote export into the product rather than the sales pitch, and kept your payment processor out of the deal entirely.

Ask us anything on a call How data comes in and out
Public status page Full export, no ticket Month to month
status.ringups.com
Last 60 days
All systems operational
60 days agotoday
App & point of saleoperational
Online bookingoperational
Notifications & textsoperational
Nightly backupslast run 03:12
Incidents are posted here, with a written explanation afterwards. You should never learn about downtime from a bride standing at your counter.
The four promises

Written here so you can hold us to them

Your data leaves when you do
Full export of brides, orders, payments, alterations and appointments — self-serve, no ticket, no exit fee, no "let me check with the team."
Downtime is published, not buried
A public status page and a written post-incident note. We tell you before your customers do.
Your stores stay separate
Row-level security on 53 tables, every policy written against one shared rule, and isolation proven by a script that signs in as another store and fails to read a single row — not asserted in a sales deck.
Nobody trains a model on your brides
Your client data is never handed to an outside company to learn from. Drafting features read your own records to produce a draft and stop there. See where drafting is used.
Backups & access

The boring parts, done properly

Encrypted in transit and at rest, nightly backups with point-in-time recovery, role-based access so a seamstress account can't read your margins, and guards enforced by the database rather than promised by the app: payments cannot be deleted, ledger entries cannot be rewritten, a signed contract is frozen with a SHA-256 hash over its own snapshot, and a customer carrying financial history cannot be deleted at all.

Staff accounts are per person, not one shared login on the counter iPad
Removing a departing employee takes one click and doesn't lock anyone else out
SMS and email consent recorded per person, per role
Audit trail · order #2291
14:22Transfer requested from Kamloops · Jess T.
11:40Alterations price set $180 · S. Reyes
11:32Contract signed, terms v4 · bride
11:28Deposit $1,320 recorded · Jess T.
When a bride disputes what she was told, the record shows who did what and when — including the exact version of the terms she signed.
Payment security, stated plainly

PCI-compliant card processing sits on our roadmap alongside in-app payments. Until it ships, you keep your own processor and its own security posture — nothing about your existing setup changes, and card data never enters RingUps.

Which also means there's nothing here for us to lose.

Certifications: where we actually stand

Encryption in transit & at restIn place
Nightly backups & recovery testingIn place
Role-based access & audit trailIn place
SOC 2 auditNot yet
PCI scope (in-app payments)Not yet

We're a small team and we haven't bought a certification we can't yet operate behind. If a formal audit is a requirement for your group, say so on the call and we'll tell you where it sits on the roadmap.

Bring the hard questions

Ask us what happens if we're acquired, if you leave, or if the site is down on a Saturday. You'll get a straight answer from the people who built it.

Book a demo Read the FAQ