Your data, plainly

Where it lives

Your files and the cleaned records we build from them sit in a PostgreSQL database on Railway infrastructure in Amsterdam, the Netherlands. Payments run through Stripe, so card details never touch our systems. If you connect a Google Drive folder, we read only the folder you share. All traffic is encrypted in transit.

Who can see it

Your own logins, and the DataOZ operator for support and file-mapping work. Our infrastructure and processing providers, listed in the Privacy Policy, handle data to run the service; no person outside DataOZ browses your numbers. Every customer's data sits in its own tenant, and the separation is enforced inside the database itself with PostgreSQL row-level security. The design fails closed: a request that arrives without a valid tenant context sees nothing at all, never everything. Administrative access across tenants sits behind a separate platform-admin boundary with its own authorisation.

What we never do

• Never show your numbers to another customer, in any form.
• Never share your sales data with your retailers, and never with anyone beyond the processors named in our Privacy Policy.
• Never sell data, aggregate it for resale, or use it to advantage any other business.
• Never hold your data hostage: export every report to a clean spreadsheet whenever you like.

Leaving, and worst cases

Cancel any time; export your data for 30 days after your subscription ends, and then we delete it from our production systems. If a breach ever occurs that could cause you serious harm, we will tell you and the Office of the Australian Information Commissioner promptly, as the Notifiable Data Breaches scheme requires, and we will tell you in plain language what happened.