Your brides trust you with their wedding. You're trusting us with that record. This page says plainly what we hold, why, and what you can take back.
There are two kinds of data here and it matters which is which. Your account data — your name, your staff logins, your billing details — is data we hold about you as our customer.
Your store data — brides, parties, appointments, orders, deposits, alterations, notes — belongs to your business. You decide what goes in it and who sees it. We hold and process it on your behalf, to run the service you're paying for, and for no other purpose.
We do not collect or store payment card numbers. Card data is handled by your own payment processor and never enters RingUps.
To operate the service: showing your team their appointments, computing must-arrive-by dates, tracking deposits and recognizing revenue at delivery, sending the reminders you've configured, and producing your reports.
To support you: when you email support, we look at the record you're asking about. We access store data only to resolve a specific request, to investigate a fault, or where the law requires it — and those accesses are logged.
To improve the product in aggregate: counts and error rates that contain no client identities, so we can see that a screen is slow or a step is being abandoned.
Every store's data is isolated at the organization level — a design decision from the first version, not a later retrofit. No store, and no group of stores, can reach another's records.
Inside your own account, access is role-based: a seamstress account sees the workroom, a consultant sees the floor without margins, a manager sees their location, an owner sees everything. Staff accounts are per person, so removing someone who leaves takes one click and locks nobody else out. Details are on Security & trust.
We use a small number of third-party services to run RingUps — cloud hosting and backups, transactional email and SMS delivery, error monitoring, billing, and a text-generation provider used only for the drafting features. Each receives only what it needs to perform its function.
We keep a current list of sub-processors and will send it on request; if you're evaluating us for a group, ask for it before you sign rather than after.
While your account is active, we keep your store data so your history stays intact — a bride who bought four years ago is still a record you may need.
If you close your account, we keep the data for a short wind-down window so you can export or change your mind, then delete it. Backups age out on their own schedule. Some records may be retained longer where tax or accounting law requires it. Ask us for the current windows in writing and we'll give you exact numbers.
You can export everything — brides, orders, payments, alterations, appointments — at any time, in standard formats. You can correct or delete records yourself inside the app.
When a bride exercises a privacy right with you, you're the one who holds the relationship, and we'll help you honour it: we'll assist with locating, exporting or deleting her record. Consent for texts and emails is recorded per person and per role, so a bridesmaid who never agreed to be contacted isn't.
Privacy questions go to the founders directly, not a queue. Email support@ringups.com, or use the form on our contact page. If a question here needs a firmer answer than plain language allows, say so and we'll put it in writing.