1. Who collects your data
ShiftHub is operated by the ShiftHub team ("the ShiftHub team", "we").
- Email: support@shiftshub.app
2. Scope
This policy covers:
- the ShiftHub iOS app (App Store)
- the ShiftHub Android app (Google Play, package com.goodshift.app)
- the ShiftHub web admin (admin.shiftshub.app)
- the ShiftHub website (shiftshub.app)
3. Who is responsible for what
ShiftHub is a scheduling, clock-in and leave tool for businesses.
- The store (owner / admin) decides which staff to add, how to schedule them and how to calculate pay. Staff schedules, clock-ins, leave and pay settings are records the store keeps to manage its own staff, and the store is primarily responsible for them.
- ShiftHub provides the system, stores the data, and processes it only as needed to provide the service.
If you are a staff member and want to see or correct attendance, leave or pay records your store keeps, please ask your store manager first. You can also email us (see Section 15).
4. What we collect
4.1 Account data
| Data | When | Notes |
|---|---|---|
| Email and password | Email sign-up | Passwords are stored hashed by Firebase Authentication; we cannot see them |
| Apple or Google sign-in data | Signing in with Apple / Google | We receive your email and display name, never your Apple/Google password. If you use Apple's "Hide My Email", we only get Apple's relay address |
| Name (display name) and mobile number | Setting up your profile | So your manager can recognise you and to prevent duplicate accounts |
| Role and store | Creating or joining a store | e.g. owner or staff, which store, the invite code used |
4.2 Location and Wi-Fi (for clock-in)
- Store clock-in location: when an owner sets the clock-in area, we store the store's GPS coordinates and the store Wi-Fi name (SSID) and identifier (BSSID).
- Staff location at each punch: when you tap clock in/out, the app reads your GPS position and stores those coordinates with that clock-in record. The purpose is to let the store verify that the punch was made within the clock-in area the store set.
- Wi-Fi name at clock-in: read and stored with the record when you clock in by Wi-Fi, for the same purpose.
- We read location only at the moment you clock in or set a clock-in location. We never track your location in the background.
- You can turn off location permission in your phone settings at any time. GPS clock-in will then not work (you can use Wi-Fi clock-in or ask your manager to add the record).
4.3 Scheduling, attendance and leave
- Schedules: shift types, weekly rosters, publish/edit history, scheduling notes (e.g. "can't work Wednesday evenings").
- Clock-in records: in/out times, method (GPS / Wi-Fi / added by manager), location at punch (see 4.2).
- Attendance exceptions: late, early leave, absence, missed punches.
- Attendance fix requests: date, time, reason, and the manager's decision and reason.
- Overtime requests: date, duration, reason, decision.
- Shift swaps and unavailable times.
- Leave requests: leave type, dates, reason, decision.
- Note: leave types include sick leave and menstrual leave, which may reveal health information, and you may write health-related details in the reason.
- Leave records (including type and reason) can be seen only by the store owner and you, and are used only for leave approval, scheduling and pay estimates.
- We recommend keeping the reason short and not writing any diagnosis.
4.4 Pay data
- Employment type (full-time / part-time), hourly or monthly pay, allowances and deductions.
- Hours, pay and labour cost estimated by the system from clock-ins and schedules.
- The owner sees pay data for the whole store; staff see only their own payslip (Pro feature).
- ShiftHub pay figures are estimates for reference only; actual pay is determined by the store (see Terms of Use).
4.5 Store operations data
- Store name, store images (logo etc.), opening hours, shift types, scheduling rules.
- Announcements and to-dos.
- Inventory items, counts and reports (Pro feature).
- Issue reports submitted by staff (text and attached images).
- Store images and issue-report images are accessible only to members of that store and the ShiftHub team.
4.6 Data you send to ShiftHub
- Feedback: the text and images you submit in "Feedback", plus your email and account ID so we can reply. Feedback is forwarded to the ShiftHub team by email. Feedback and its images are accessible only to you and the ShiftHub team; store owners cannot see it.
- Support emails you send to support@shiftshub.app.
- Optional deletion survey: when you delete your account you may tell us why (tick reasons; if you choose "Other" you may write up to 500 characters). The survey is stored anonymously: only the reasons, whether you were an owner or staff, app version and platform. No account ID, email or name is stored. We use it to improve the product.
4.7 Device and technical data
- Push token (FCM): to send schedule, reminder and approval notifications.
- App version, OS and device type: for compatibility.
- Crash reports (Firebase Crashlytics): when the app crashes or hits a serious error, technical details are sent automatically (error message, stack trace, device model, OS version, app version, screen name).
- Usage analytics (Google Analytics for Firebase): which features you use and how often you open the app, to learn what works and what to improve. Analytics are linked to your account ID, your role (owner or staff) and your store ID, but do not include schedule, clock-in, leave or pay contents.
- Error reports with automatic screenshots: when an error occurs, the app automatically sends to ShiftHub's servers:
- the error message and technical log, screen name, app version, platform;
- your account ID, email, display name, sign-in method, store ID, role and staff ID;
- a screenshot of the app screen at that moment (at most one per device every 30 seconds). It captures whatever was on screen, which may include schedules, staff names, clock-in or pay figures.
- This is used only to find and fix bugs and is accessible only to the ShiftHub team and the owner of your store (so the owner can help troubleshoot).
4.8 Payments and subscriptions
- App Store (Apple): Apple processes payment. We only receive subscription status (plan, active or not, expiry date, transaction ID), never your card number.
- Google Play: Google processes payment. Same as above.
- RevenueCat: we use RevenueCat to manage in-app subscription status, sharing your ShiftHub account ID and purchase records with it.
- Web subscription (NewebPay): when an owner subscribes by credit card on the web admin, NewebPay handles the card. We never receive or store the full card number; we keep only the last four digits, transaction and recurring-payment IDs, charge results, and the payer email (NewebPay uses it to send payment notices).
4.9 What we do not collect
- ShiftHub has no camera or audio-recording feature and does not use your camera or microphone. Images (store images, issue reports, feedback) are always picked from your photo library.
- We do not collect national ID numbers, bank accounts, dates of birth or medical records.
- We do not track location in the background.
5. Why we collect it (purposes and categories)
PDPA specific purposes: 002 personnel management (attendance and pay estimates processed for stores), 069 contract and similar legal relationships, 090 customer management and service, 135 information and communication services, 136 information and database management, 148 online shopping and other e-commerce services, 157 survey, statistics and research analysis.
Data categories: C001 identifying information (name, email, mobile, account ID, location), C002 financial identifiers (card last four digits), C061 current employment (store, role), C065 work and attendance records (schedules, clock-ins, leave, overtime), C068 pay and deductions (pay settings and estimates), C111 health records (only sick/menstrual leave types and reasons you write).
In plain terms:
| Purpose | Data used |
|---|---|
| Scheduling, clock-in, leave, overtime, fixes, pay estimates, inventory, announcements | 4.1–4.5 |
| Verifying that a punch was made within the store's clock-in area | 4.2 |
| Sign-in, identity, owner vs staff permissions | 4.1 |
| Schedule, reminder and approval notifications | 4.1, push token in 4.7 |
| Subscriptions, payments, refunds, plan entitlements | 4.8 |
| AI scheduling (Pro) | see Section 7 |
| Diagnosing crashes and errors, security | 4.7 |
| Understanding feature usage to improve the product | deletion survey in 4.6, analytics in 4.7 |
| Replying to feedback and support | 4.6 |
We do not show you ads, sell your personal data, or use it for marketing unrelated to ShiftHub.
6. Who processes data for us
| Service | Provider | What it processes | Possible location |
|---|---|---|---|
| Firebase Authentication | Sign-in | USA and others | |
| Cloud Firestore (database) | All operational data (schedules, clock-ins, leave, pay, etc.) | Google Cloud data centres | |
| Cloud Functions (backend) | Scheduling computation, notifications, billing | USA and others (default us-central1; some in Taiwan, asia-east1) | |
| Firebase Storage | Store images, issue/feedback images, error screenshots | Google Cloud data centres | |
| Firebase Cloud Messaging | Push notifications | Global | |
| Firebase Crashlytics | Crash reports | USA and others | |
| Google Analytics for Firebase | Usage analytics | USA and others | |
| Google Gemini API | AI scheduling (see Section 7) | USA and others | |
| RevenueCat | RevenueCat, Inc. (USA) | In-app subscription status | USA |
| Apple App Store | Apple | iOS subscription payments | per Apple |
| Google Play Billing | Android subscription payments | per Google | |
| NewebPay | Newebpay Co., Ltd. (Taiwan) | Web credit-card recurring payments | Taiwan |
| Email delivery (SMTP) | Our email delivery provider | Feedback notifications, billing reminders (recipient email and message content) | Per the provider |
| Google Analytics, Google Ads conversion tracking | Website shiftshub.app only (Section 10) | USA and others |
Beyond these providers, we share data only:
- with your store owner, who already sees your schedule, clock-in, leave, overtime, fix-request and pay records for that store;
- when required by law or by a court, prosecutor or regulator;
- in an emergency to protect someone's life, body or property.
7. What AI scheduling sends to AI
AI scheduling (Pro) has two parts:
- Schedule computation: done by ShiftHub's own backend (a mathematical optimisation solver) on Google Cloud. This step does not send data to an AI model.
- AI model (Google Gemini), used in two places:
- Turning free-text rules into system rules: if store rules or staff scheduling notes are written as free text (e.g. "Ming can only work mornings on Wednesday"), the store rule text and each staff member's scheduling note (keyed by internal staff ID, without names) are sent to Gemini for conversion. Notes already in system format are not sent.
- Writing a summary: after computation, a summary of the result (the names and shifts of up to 8 staff, and understaffed time slots) is sent to Gemini to write a short explanation for the owner.
We use a paid Gemini API plan. Under the terms of that paid plan, Google processes this data only to produce the conversion and the explanation, and does not use it to train its models.
We never send clock-in locations, leave types or reasons, pay, email addresses or phone numbers to AI.
Tip: keep scheduling notes to what scheduling needs; do not include health or other sensitive details.
8. Storage location and international transfers
ShiftHub data is stored on Google Cloud servers, which may be located outside Taiwan. Some processing (backend computation, AI scheduling, crash reports, analytics, RevenueCat) takes place in the USA or other countries. By using ShiftHub you understand that your data may be transferred outside Taiwan; we only use providers with appropriate security safeguards.
9. How long we keep data
| Data | Retention |
|---|---|
| Account data | While the account exists; deleted immediately when you delete your account (Section 11) |
| Schedules, clock-ins, leave, overtime, fixes, pay data | While the store exists, so the owner can run payroll and resolve attendance disputes |
| After a staff member leaves, is removed, or deletes their account | That person's clock-in, leave, overtime and pay records at that store remain available to the owner, because the store needs them for payroll, labour disputes and statutory record-keeping (Taiwan's Labor Standards Act requires attendance records to be kept for 5 years). |
| After a store is deleted | General data (schedules, announcements, inventory, images) is deleted immediately; pay, leave and clock-in records are archived for 365 days for labour disputes or legal requests only, then automatically deleted |
| Error reports and screenshots | Automatically deleted after 365 days |
| Feedback and support emails | 365 days |
| Deletion survey answers (anonymous) | 365 days |
| Crash reports (Crashlytics) | Per Google's default retention period |
| Analytics | Per the Google Analytics setting, up to 14 months |
| Payment and subscription records | Kept as required by law |
10. Website cookies
The website shiftshub.app uses Google Analytics to measure traffic and Google Ads conversion tracking to measure ad performance; both set cookies in your browser. You can block or delete cookies in your browser settings without affecting the app. The app itself does not use advertising tracking.
11. Your rights and how to use them
Under Article 3 of the PDPA you may, for your own personal data:
- ask to inquire or review it;
- ask for a copy;
- ask to supplement or correct it;
- ask us to stop collecting, processing or using it;
- ask us to delete it.
What you can do yourself in the app:
| Goal | How |
|---|---|
| View your schedule, clock-ins, leave, payslip | Directly in the app |
| Change your name or mobile number | The name shown in your store is changed by the owner under the staff member's "Edit" screen; for other account data, email support@shiftshub.app and we will correct it |
| Leave a store (staff) | You will no longer belong to that store, but your records there remain with the owner (Section 9) |
| Delete your whole account | Owners: Settings → Delete account. Staff: Me → Delete account. You may give an anonymous reason |
| Delete a store (owner) | Settings → Delete store. Data is handled as in Section 9 |
| Turn off location or notifications | Phone system settings |
What happens when you delete your account:
- Your sign-in account and personal profile (name, email, mobile number) are deleted immediately. If you signed in with Apple, ShiftHub's authorisation for your Apple account is also revoked.
- If you are an owner: the stores you own are closed through the store-deletion process; general data is deleted immediately, and pay, leave and clock-in records are archived for 365 days and then automatically deleted.
- If you are staff: you leave the stores you belong to; your clock-in, leave, overtime and pay records at each store remain with that store's owner (Section 9).
- Deletion cannot be undone.
By email: write to support@shiftshub.app with your account email, store name and the right you want to exercise. We will verify that you are the account holder and reply within 15 days, extendable once by 15 days with notice of the reason (PDPA Article 13).
Please note:
- Stores may have a legal duty to keep attendance and pay records. For such data we will check with the store before deleting or correcting it, and may not be able to delete it fully; we will tell you why.
- Deleting your account does not cancel Apple or Google billing. Cancel your subscription in the App Store or Google Play first.
- You may choose not to provide some data, but related features may not work (e.g. no location means no GPS clock-in).
12. Security
- All connections use HTTPS/TLS.
- Passwords are hashed by Firebase Authentication.
- Sign-in credentials are kept in the phone's secure storage.
- Access is restricted: store data is readable only by members of that store; pay settings, clock-in records and leave records only by the owner and the person concerned; error reports only by the ShiftHub team and the store owner; feedback only by the person who submitted it and the ShiftHub team.
- No system is 100% secure. If a data breach occurs, we will investigate and notify affected users as required by the PDPA.
13. Children
ShiftHub is not intended for children under 13, and we do not knowingly collect personal data from children under 13. If you learn that a child has given us personal data, please tell us and we will delete it after verification.
14. Changes
We may update this policy. The updated version will be posted here with a new "Last updated" date. If a change materially affects your rights or how we process data, we will notify you in the app.
15. Contact
Questions about this policy, or to exercise your rights, contact the ShiftHub team:
- Email: support@shiftshub.app
© 2026 ShiftHub. All rights reserved.