Your information
Privacy policy
RosterMate AI is developed and operated by Jagjeet Singh, Australia. Contact sehdevstech@outlook.com with privacy questions, access or correction requests, complaints, or deletion requests.
1. Information we handle
| Information | Purpose and location |
|---|---|
| Profile, employee name or number, shifts, work codes, leave entries, settings and work sessions you enter | Stored on your device to provide roster features. Included in backups according to the backup type. Leave entries can reveal sensitive personal information; enter only what you need. |
| Google account name, email and account identifiers | Google/Firebase authentication, displaying your connected account, linking your plan and identifying your own backups. We do not receive your Google password. |
| Subscription purchase tokens, plan status, expiry, trial usage, import usage and hashed account/device identifiers | Our Firebase/Google Cloud services verify subscriptions, apply limits and prevent duplicate trial claims. Google Play handles payment details; RosterMate does not collect your card number. |
| Roster images/documents and employee name/year submitted for AI import | Sent to our Google Cloud processing service and Google Gemini; OpenAI may be used as a fallback. These providers process the submitted content to extract shifts. |
| Notification content when you enable message monitoring | Android notification access allows the app to inspect incoming notifications. Roster-related candidates, pending changes and learned patterns are processed/stored locally. The current notification parser does not send raw messages to the AI import service. |
| Backup contents | Local copies stay on your phone or wherever you export them. With separate consent, upgraded Drive backups go to your Google account. Older Firebase cloud backups remain in our service until removed. |
| Technical and support information | Service requests can generate timestamps, errors, usage counts, request sizes, IP/network information and provider diagnostics. Information you email us is used to respond and resolve requests. |
2. Google Drive access
The upgraded app requests only the drive.appdata permission for its hidden application-data folder. It uses this to create, list, read and remove RosterMate backup versions. It does not request access to browse your ordinary Drive documents, photos or shared files. Drive authorisation is separate from Google sign-in.
Drive backups contain saved roster data, selected profile/settings, templates and work-session data. Original documents, raw notification messages and temporary pending-message data are excluded from the Drive backup. Local exports can contain more app data, so protect exported files.
The app keeps up to three Drive backup versions, removing older versions after a new upload succeeds. Automatic backups depend on app use, permission, internet access and your plan. They are not guaranteed while the app is closed. Disconnecting Drive stops the app’s connection; it does not itself delete existing backups. You can revoke access through your Google Account and manage/delete hidden app data through Google Drive’s app-management settings.
RosterMate AI’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Google account and Drive data are used for the features you authorise, not advertising or AI model training. RosterMate does not send Drive backup contents to Gemini or OpenAI for roster analysis.
3. AI processing and your choices
AI import is optional. Only submit documents you are permitted to use. A roster may include other employees’ names and shifts, even when you only want your own shifts. Crop or remove unnecessary information before uploading. Manual roster entry avoids AI processing.
The current import service processes images in requests and does not deliberately save the original image as a Firebase roster document. Technical logs and external providers’ retention can still apply. We do not promise zero retention or immediate deletion by external providers. Provider handling is governed by the service configuration and applicable terms. See Google’s privacy policy and OpenAI’s privacy policy. Review imported shifts before saving; AI can make mistakes.
4. Who receives information
We use Google/Firebase/Google Cloud for authentication, hosting, server processing, security and account records; Google Play for billing; Google Drive for authorised backups; Google Gemini and, when needed, OpenAI for selected AI imports; and our email provider for support. We do not sell your personal information or use roster data for targeted advertising. Information may also be disclosed where required by law or necessary to protect the service against abuse.
Our application processing functions are configured in Google Cloud’s Australia region. This does not mean all data stays in Australia. Authentication, billing, Drive, email and AI providers may process information overseas, including in the United States and other countries in which they operate.
5. Retention and security
Local roster data remains until you remove it, clear app data or uninstall, subject to Android’s own backup settings. Exported files remain wherever you save or share them. The upgraded app keeps a rotating set of local snapshots and a separate safety copy before restore.
Server-side account, subscription, trial and usage records are retained to operate the service, verify purchases and prevent abuse, unless deleted through a verified request. Existing Firebase backup data is not automatically removed when you switch to Drive. Technical logs and AI-provider records follow the relevant service retention settings. We retain information only while needed for these purposes or applicable legal obligations; a specific deletion request will be assessed against those needs.
We use authenticated requests, app-integrity checks, access controls and encrypted network connections. No service or backup is completely secure. Protect your device, Google account and exported backups. We do not claim end-to-end encryption for all backup types.
6. Access, correction, deletion and complaints
You can edit your local profile/roster and manage Android permissions. Sign-out does not erase your local roster or close your RosterMate account. To request deletion of your RosterMate account and associated server data, use our account and data deletion page or email us. We verify ownership before acting.
Account deletion does not delete your Google account, automatically cancel a Play subscription or remove copies you exported. Manage your subscription separately in Google Play and remove local/exported/Drive copies as described on the deletion page. We will explain any records that must be retained and why.
You may contact us to ask for access, correction or to complain about how information has been handled. If you remain dissatisfied, you may contact the Office of the Australian Information Commissioner where applicable, or your local privacy regulator.
7. Website and updates
This website has no advertising, analytics scripts, sign-in forms or tracking cookies added by RosterMate. Firebase Hosting may process technical request data to serve and secure the pages. Our app is designed for personal work-roster management, not as a service directed at children.
We may update this policy as features or data handling change. The date above identifies the current version. Material changes will be communicated through the app or website as appropriate.