Skip to content
ShiftGo
How it worksHelp

Privacy policy

Last updated 11 May 2026

ShiftGo is a shift and earnings tracker built for hourly workers. We wrote this policy to explain — in plain English, with no clauses you need a lawyer to parse — what happens to your data when you use the app and this website.

The short version

  • Your shifts, earnings, and personal notes live on your phone. We don't need to see them to make the app work.
  • If you turn on Cloud Sync (a Premium feature), your data is end-to-end encrypted before it leaves your device. We can't read it on the server, even if we wanted to.
  • We never sell your data. We don't share it with advertisers.
  • We don't use third-party analytics or trackers in the mobile app.
  • You can delete your account at any time. When you do, your data is gone for good.

What we collect

Data you create in the app

When you add a shift, set an hourly rate, or save a template, that information is stored on your device using a local database. It doesn't leave your phone unless you turn on Cloud Sync.

Account data (only if you sign in)

If you sign in with email, Apple, or Google, we store your email address so we can sync your data across devices and reach you about your account. That's it. No marketing emails unless you explicitly opt in.

Diagnostic data

If the app crashes, we may collect anonymous crash reports through Apple or Google's standard developer tools (you can opt out in your device settings). These reports never include your shifts, earnings, or personal information.

What we don't collect

  • We don't connect to your bank account.
  • We don't read your contacts, photos, or messages.
  • We don't track your location.
  • We don't use third-party advertising SDKs.
  • We don't sell, rent, or share your data with anyone.

Cloud Sync & encryption

If you enable Cloud Sync (included with ShiftGo Premium), your shifts and earnings are encrypted on your device before being uploaded. The encryption key is derived from your account credentials and never leaves your phone. We store only the encrypted blob — even ShiftGo engineers can't read your data on the server.

Security & data protection

We treat your shifts, earnings, account email, calendar tokens, and any events fetched from Google Calendar or iCloud as sensitive data. The following controls apply across the app, our cloud backend, and the Google Calendar integration:

Encryption in transit

All traffic between the ShiftGo app, our Supabase backend, our edge functions, and the Google Calendar API is encrypted with TLS 1.2 or higher. Plain-HTTP endpoints are not used. Certificate validation is enforced by the platform (iOS App Transport Security; Android Network Security Config).

Encryption at rest

Cloud Sync payloads are end-to-end encrypted on the device before upload (AES-256-GCM); the encryption key is derived from your account credentials and never leaves your phone. The encrypted blobs are then stored on Supabase infrastructure, which adds its own AES-256 encryption at rest on the underlying disks and managed Postgres. We hold no plaintext copy of your shift or earnings data.

Sensitive credentials on device

Google Calendar OAuth access tokens and refresh tokens are stored through the platform's secure credential store — iOS Keychain on iOS and Android Keystore (hardware- backed where available) on Android — via the expo-secure-store module. Tokens are never written to plain preferences, log files, or synced storage. When you disconnect Google Calendar or delete your ShiftGo account, the tokens are erased locally and revoked server-side with Google.

Access controls

Our Postgres database enforces row-level security (RLS): every read and write is automatically scoped to the authenticated user's ID, so one account cannot see or modify another account's rows even if a query were crafted to attempt it. Privileged operations (account deletion, push-token registration) run through audited edge functions, never with broad service-role keys embedded in the client.

Authentication

Sign-in uses passwordless email one-time codes, Sign in with Apple, or Sign in with Google. ShiftGo does not store or transmit user passwords. Session tokens are managed by Supabase Auth and refreshed automatically; you can sign out at any time from Settings → Account.

Personnel access

ShiftGo is operated by a small team. Engineer access to the production database is logged and limited to the minimum needed for service reliability and abuse investigation. Engineers cannot read your Cloud-Synced shifts or earnings (they are end-to-end encrypted), and do not read your Google Calendar data — that data is stored only on your device.

Retention & deletion

When you delete your account from Settings → Account → Delete account, all server-side data tied to your account (Cloud Sync blobs, push-token registration, account email, calendar share links) is permanently erased within 30 days; most rows are removed immediately by cascade. Anonymous crash reports collected by Apple or Google's standard developer tools follow their respective retention policies and contain no shift, earnings, or calendar content.

Breach notification

In the unlikely event of a security incident that affects user data, we will notify affected users by email within 72 hours of confirming the scope, in line with GDPR Article 33 obligations. Researchers can report vulnerabilities to support@shiftgo.net and we will acknowledge within two business days.

Calendar integrations

ShiftGo Premium can connect to your Google Calendar and (on iOS) your iCloud Calendar so your work shifts and personal commitments live in one place. Both integrations are opt-in — you choose to connect them from Settings → Calendar Filter → Sync, and you can disconnect at any time.

Google Calendar

When you connect Google Calendar, ShiftGo requests the https://www.googleapis.com/auth/calendar OAuth scope. Here is exactly what we do with that access:

  • Read the list of calendars in your Google account so you can choose which ones to overlay onto the ShiftGo grid.
  • Read events from the calendars you chose, so they appear alongside your shifts. Holiday and birthday calendars are filtered out client-side.
  • WriteShiftGo shifts and reminders to a single dedicated calendar named “ShiftGo” that we create inside your account on first sync. We never modify, delete, or read events from your other calendars.

Apple Calendar (iCloud)

On iOS, you can connect your device's Calendar permission. ShiftGo reads events from the calendars you select and writes ShiftGo shifts to a dedicated “ShiftGo” calendar on your device. iCloud roams the dedicated calendar across your Apple devices via your iCloud account; Apple, not ShiftGo, controls that sync.

Where calendar data is stored

Calendar events read from Google or iCloud stay on your device. They are not transmitted to ShiftGo's servers, not included in Cloud Sync, not used for analytics, and not used to train any model. They are kept in app memory and the local database only for as long as the integration is connected.

Disconnecting and revoking access

You can disconnect either integration at any time from Settings → Calendar Filter → Sync. Disconnecting Google Calendar calls Google's server-side revokeAccess endpoint, which removes ShiftGo from your Google Account permissions list; deleting your ShiftGo account does the same. You can also revoke the grant directly at myaccount.google.com/permissions. The dedicated “ShiftGo” calendar that ShiftGo created stays in your account after disconnect so you don't lose the history; you can delete it manually from Google Calendar / Apple Calendar if you want it gone.

Google API Services User Data Policy

ShiftGo's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We do not transfer Google user data to third parties except to provide or improve user-facing features, and we do not use Google user data for serving advertisements or to train generalized AI / machine learning models. Humans do not read Google user data unless we have your explicit consent for a specific incident, it is required for security purposes (such as investigating abuse), to comply with applicable law, or the data is aggregated and anonymized for internal operations.

Third parties

We use a small number of trusted services to run ShiftGo:

  • Apple App Store / Google Play: handle subscriptions and purchases. We never see your payment information.
  • Supabase: encrypted cloud storage for sync. They host the encrypted blobs; they can't read them.
  • Apple / Google Sign-In: optional authentication. Used only to verify your identity when you sign in.
  • Google Calendar API: optional integration (Premium). Reads your Google Calendar list and events into the app for unified scheduling, and writes ShiftGo shifts to a dedicated “ShiftGo” calendar in your Google account. See the “Calendar integrations” section below for the full data flow.
  • Apple Calendar (iCloud): optional integration (Premium, iOS). Reads your iCloud calendars into the app and writes ShiftGo shifts to a dedicated “ShiftGo” calendar on your device.

Your rights

You can, at any time:

  • Export your data as a PDF (Premium) or read it directly on your device.
  • Delete your account from Settings → Account → Delete account. This permanently removes everything we store about you.
  • Contact us at support@shiftgo.net to request a copy of any data we hold about you.

Children

ShiftGo is intended for people aged 16 and over. We don't knowingly collect data from anyone younger.

Changes to this policy

If we change anything material about how we handle your data, we'll update the date at the top of this page and notify you in the app before the change takes effect.

Data controller

ShiftGo is operated by BE ADS Yazılım Teknoloji Sanayi ve Ticaret Limited Şirketi, a company registered in Antalya, Türkiye.

Contact

Questions? Concerns? Real things you'd like changed? Email support@shiftgo.net and a real person will get back to you.

BE ADS Yazılım Teknoloji San. ve Tic. Ltd. Şti. · Enes Kaya · Antalya, Türkiye