Security and your data

Your data is stored in Sydney, Australia, in a managed Postgres database, and the app runs from Sydney too. Everything travels over HTTPS. The companies we rely on are listed in the privacy policy.

Every record belongs to one business, and the database itself checks that you’re a member of that business before it returns anything. Automated tests try to read across businesses and must fail. Inside a business, roles decide who sees what.

Passwords are never stored in plain text. Owners can require two-step verification with an authenticator app, and repeated failed logins are slowed down. Staff join through an invite or a sign-up link that a manager approves.

The app sends a strict content security policy, so the browser runs only our own scripts. It can’t be framed by other sites, and connections are HTTPS only.

Sensitive actions are logged with who did them and when: publishing a roster, editing it after publishing, changing someone’s role and exporting data.

The AI manager (on AI Plus) works with names, shifts and availability. It never receives dates of birth, pay, contact details or notes, and we don’t log what you ask it or what it answers. It only ever suggests: a person confirms every change, and it can’t publish, message your team or touch pay.

Owners can download all of the business’s data as spreadsheets at any time. Errors are reported to our monitoring without personal details in them.

If you think you’ve found a security issue, email roosta.corp@gmail.com with what you found and how to see it. Please don’t access other people’s data or disrupt the service while testing.