Data handling
Your venue owns its data. Allhouse holds it on your behalf, walls it off from every other customer, and returns or deletes it when you ask.
Who is responsible for what
The venue, or the group or franchisor that signs up, decides what personal information it collects about its staff and guests and why. Allhouse stores and processes that information only to provide the service, under the venue's instructions. We never use one customer's data for another customer.
Where data lives
| Stage | Host | Region | Backups |
|---|---|---|---|
| Beta | Railway | Singapore | Daily and weekly, kept up to 27 days |
| General release | Amazon Web Services | Sydney (ap-southeast-2) | Daily to Melbourne (ap-southeast-4), kept 35 days |
Groups that need Australian-only storage during the beta should wait for general release or ask us about a dedicated Sydney setup.
Encryption
- In transit: HTTPS for every page, API call and connection to integrations
- Connected-system tokens and two-step sign-in keys are encrypted by Allhouse before they are saved
- Passwords and clock-on PINs are stored only as salted one-way hashes; sign-in and reset links are stored only as hashes
Who can see what
- Every record belongs to one venue, and every request is checked against the venues the signed-in user is allowed to see
- Roles limit what each person can do: owners and head office see every site; managers see their own venues; staff see only their own shifts and the team chat
- Two-step sign-in is available to every user and can be made compulsory for a whole organisation
- Wrong passwords, two-step codes and clock-on PINs are limited, with a 15-minute pause after repeated failures
- Every sign-in and every change to money, people, rosters and settings is written to an audit log the owner can read
- Allhouse staff access customer data only to resolve a support request the customer raised
Connected systems
When a venue connects its point of sale, Xero, rostering or booking system, Allhouse stores the access token that system issues, encrypted, and never the venue's password for it. A venue can disconnect any system from the Integrations page, which deletes the token straight away.
Groups and franchises
Head office sees a roll-up of every site; each site manager sees only their own. Royalty and marketing-fund figures are calculated from each site's sales. A franchisee leaving the group can take its own site's data with it.
If something goes wrong
- We contain the incident and preserve evidence as soon as we know of it
- We tell affected venues within 72 hours, with what happened, what data was involved and what we are doing
- We assess within 30 days whether it is an eligible data breach under the Notifiable Data Breaches scheme
- If it is, we notify the OAIC and help the venue notify affected staff and guests
- We write up the cause and the fix and share it with affected venues
Leaving Allhouse
A venue can ask for a full export of its data as CSV files at any time, and we provide it within 10 business days. When it cancels, we keep its data for 90 days in case it comes back, then delete it; backups roll off within a further 35 days. We confirm deletion in writing on request.
Sub-processors
| Provider | What it does | Data it receives | Location |
|---|---|---|---|
| Railway (beta) | Hosting and database | All venue data | Singapore |
| Amazon Web Services (from general release) | Hosting, database, file storage, email | All venue data | Sydney and Melbourne |
| Anthropic | AI model behind Ask Allhouse and the design studio | The question and the venue figures needed to answer it, not guest contact details | United States |
| Open-Meteo | Weather history and forecasts | The venue's location only | Europe |
| Unsplash | Stock photos in the design studio | Search words only | United States |
| Canva (only if the venue connects it) | Design editing | The designs the venue sends | United States |
We give customers 30 days' notice before adding a sub-processor that receives personal information.
Testing and assurance
We test the app's security before general release and again each year, using an independent penetration tester, and fix any high-risk finding before launch. A summary of the latest test is available to customers under a confidentiality agreement.
How we collect and use personal information is set out in the privacy policy. Questions: hello@allhouse.com.au