Rooik provides this staff scheduling app for restaurant teams. Contact: [email protected].
2. Data we collect
Identity: your name and email address. Your employer enters these when they create your account. The app has no sign-up.
Contact details you enter yourself: phone number, home address, and an emergency contact (name, relationship, phone number). These are optional.
Identity details you enter yourself: nationality, your social security identifier (in the UK, your National Insurance number) and, in the UK, your HMRC share code. These are optional and go to your employer's records.
Documents you upload yourself: one identity document photo, at most 200 KB. The camera and photo library are used only when you tap the upload button. The file is stored privately. You and your employer's admins can open it.
Contracts and other employment documents: documents issued by your employer, your typed signature or acknowledgement, and the completed PDF. Rooik keeps completed contracts for at least three years after signing and employment end.
Bank details you enter yourself for payroll: account name, sort code, account number. These are optional. Sort codes and account numbers use a separate encryption key derived for your employer. The app only ever shows you the last four digits of the account number.
Your social security identifier and HMRC share code also use the separate encryption key derived for your employer.
Work data: shifts, rotas, clock-in and clock-out times, breaks, holiday requests and balances, and notices from your employer.
Precise location: read once, at the moment you tap Clock in or Clock out, while the app is open (foreground only), and only if your site has a clock-in location rule. We never track location in the background. The location is stored with that clock record as evidence and is never used to calculate pay.
Network address: if your site uses a Wi-Fi clock-in rule, the public internet address of your punch request is compared with your employer's restaurant network. Every web server sees this address. It is stored with that clock record.
Notifications: a push token, your device platform and the app version, so your employer can send you holiday decisions and rota notices. You can refuse notification permission.
We do not collect crash logs, analytics, contacts, or any other data. Photos are used only for the documents you choose to upload. The app contains no analytics or crash-reporting software.
The app does not cache your personal profile on your phone. Your sign-in and any offline punch waiting to send use the phone's protected secure storage.
3. Why we use it
To run staff schedules, timekeeping and holiday.
To let your employer contact you and pay you.
To manage accounts and sign-in.
To send you notices about your rota and holiday requests.
4. Who receives it
Your employer (the restaurant operator) sees your details and work data. Rooik processes the data on their behalf.
Our hosting provider (Supabase) stores the data.
The Expo push service relays your push token to Apple and Google so notifications reach your device.
We do not sell personal data or share it for advertising. Nothing tracks you across other apps or websites. The app shows no ads and has no chat function.
5. How long we keep it
Work records stay for 6 years (payroll law).
The details you entered yourself are deleted at once when you remove yourself from the app (Profile > Your data) or ask for deletion (see the deletion page).
Push tokens are disabled when you sign out and deleted with your account.
All traffic uses HTTPS. Data is encrypted in transit and at rest with our host. Bank numbers and social security identifiers also use a separate encryption key derived for each employer.
Sign-in uses Supabase Auth (password or emailed code).
Access is limited to your employer and Rooik support staff.