Security — how ProviderQMS looks after your data

Where your records live

The application and its database run on a server in Kuala Lumpur, Malaysia, operated by Hostinger. Everything the app holds for you sits on that server, and the paragraphs below name which records those are. We are an Australian company: the Australian Privacy Principles bind us wherever the records sit, and they cover this disclosure overseas. The detail is in the privacy policy, and Your data sets out what you can take, cancel and delete.

Purchase records — your receipt, the email address you paid with and the products it entitles — are held in a database in Sydney, Australia. Card details never reach us: payment is handled entirely by Stripe, and a refund goes back through Stripe to the card you paid with.

Your account and how you get in — the address a sign-in link was sent to, the session it opened, the entitlement your receipt carries and any ticket you raise with us — are held on that same Malaysian server.

Workspace records you create in the app — registers, worker checks, actions, notes — are stored in your browser on the device you use. They do not leave that device unless you export them. Account storage that follows you between devices arrives in October. Until then, start on the device you will keep using and export before you change it.

Documents you upload for the document check (annual plan) are stored on that Malaysian server — the file itself and the text read out of it — and can be deleted from your Library. Records of a kind that carry a retention period are hidden from your list rather than destroyed, and the screen says so at the moment you delete.

How you get in

Your receipt link is the key to your Library — there is no password to lose. Keep the link; Get my files re-sends it to the address you paid with.
Sign-in emails carry a link that is valid for 24 hours and then stops working.
The sign-in hint the marketing site uses to show “Go to your dashboard” carries no entitlement, no receipt code and no email — forging it gets you a different button label and nothing else.

What we do

HTTPS on every page and every request between the site, the workspace and our servers.
Our web-server logs mask session identifiers and entitlement links before they are written, so a receipt link in a URL is never stored in a log line.
Uploads for the document check are limited by size and rate, and the file type is checked before anything is read.
Questions you ask Ethan are processed by the third-party provider named in our privacy policy; the answer is shown to you and its limits are stated with it.
We answer within one business day — including a question that begins “I think something is wrong”.

What we do not claim

We hold no security certifications, and we say so rather than borrow our suppliers’ badges. Stripe’s standards are Stripe’s. Our own posture is the list above — and the fact that the sensitive records are the ones we do not hold: no card details, and no workspace records. Account storage that follows you between devices arrives in October. This page will then say where those records live and how they are backed up.

Measurement

The site uses Meta’s pixel and Google Analytics to measure which advertisements lead to a purchase, and Microsoft Clarity for anonymised session replays with typed text masked. The identifiers involved, and how to block them, are described in the privacy policy. None of it is used to build a profile of you for anyone else.

Something wrong?