What actually happens to your shop's data

Putting years of your business into someone else's software is a real decision, and "trust us" is not an answer. So here is what happens to it, specifically.

It is backed up every night, off-site, encrypted before it leaves. The database and the racket photos both. We keep thirty nightly copies and one copy per month for a year. On the first of every month, a machine automatically restores the most recent backup into a clean database and checks it came back whole — because a backup nobody has ever restored is not a backup, it's a hope. We ran that restore and compared it against production row for row before we called the feature done.

Shops are separated in the database itself, not by application code remembering to filter. One shop cannot see another's players or business figures even if something above the database goes wrong. Tables that run the platform rather than your shop are unreachable except by the service that operates them.

We are not quietly inside your account. Racketworks staff hold no membership in customer shops and there is no impersonation feature in the product — no button that logs us in as you. Administrative actions run through a small number of levers that record who used them and from where.

And when it's down, you find out somewhere else. The status page is hosted away from Racketworks on purpose, so it can still answer when we can't. A status page that goes down with the product is decoration.

What isn't true yet, and it matters. There is no self-serve delete button. Exporting or deleting a shop's data is something we do by hand, within thirty days of you asking. And because backups are kept on the schedule above, deleted data can still exist inside an encrypted backup until those copies age out. We would rather write that sentence than let you assume otherwise.

Where to start. status.racketworks.tennis is public and always has been. The privacy policy describes every vendor that touches your data by name.