Skip to content
Megashift.
← Back to Megashift

MEGASHIFT / LEGAL

Privacy Policy

How Megashift processes information in the app, account and cloud features, device-calendar integration and this website.

1. Data Controller and Contact

Last updated: September 18, 2026

This Privacy Policy explains how Megashift processes information when you use the Megashift mobile application, the website at https://www.megashiftapp.com, and connected account, cloud, purchase, analytics, advertising and support services.

Data Controller:
Pattarachanok Klinjan
1020 Green House Moo 7
Tambon Nokmuang, Ampur MuangSurin
Surin 32000
Thailand

Privacy and support contact: megashift.app@gmail.com

If you have questions about this Privacy Policy or want to exercise a privacy right, contact us at the email address above.

2. Information Stored on Your Device

Megashift is designed so that much of your schedule information is stored locally on your device. Depending on the features you use, local information may include:

  • work calendars and shift schedules;
  • shifts and additional work entries, including dates, titles, abbreviations, start/end times, durations, colors and overtime information;
  • shift templates, break information, alarms and rotation patterns;
  • notes you enter in the app;
  • holiday settings and holiday entries;
  • working-time settings, target/actual-hour settings and related balances;
  • income settings such as hourly rates, monthly salary settings, currency, allowances and calculation rules;
  • theme and other app preferences; and
  • local information used to render home-screen widgets.

Unless a feature described below sends information to a service provider, this information remains in the app's local storage on your device.

3. Device Calendar Access

If you enable calendar access, Megashift uses the calendar interfaces provided by Android or iOS to show calendars and appointments that are available to your device. Megashift does not use the Google Calendar API to retrieve these appointments.

Depending on the information made available by your operating system and calendar provider, Megashift may process calendar metadata and event details such as calendar name/account information, event title and description, start/end time, all-day status, recurrence information, reminders and, where available, location, URL, attendee or availability/status information.

Megashift can also create, edit or delete calendar events when you initiate those actions in the app. These actions are performed through the operating system's calendar interface. If a calendar belongs to a synchronized account, such as Google Calendar or iCloud, your operating system or calendar provider may synchronize the change according to your device and account settings.

The list of device calendars and your selected-calendar settings are stored locally. Device-calendar events are not included in Megashift's Supabase cloud-sync tables.

Calendar access is optional. You can grant or revoke the relevant permission in your device settings. If you revoke it, calendar-related features may no longer work.

4. Accounts and Authentication

Megashift offers account features using Supabase for authentication and account sessions.

Email and Password

If you register with email and password, Supabase processes your email address, authentication credentials, account identifier and session information. Password-reset requests are also handled through Supabase. Megashift does not store your plaintext account password in its own local app database.

Sign in with Google

If you choose Sign in with Google, Megashift requests basic Google identity/profile information for authentication. Depending on what Google makes available, this may include your Google account identifier, email address, display name, profile picture and authentication tokens used to complete sign-in.

Megashift uses this information to authenticate you with Supabase, create or access your Megashift account, maintain your signed-in session and display account information in the app.

Megashift does not use Google sign-in tokens to access the Google Calendar API and does not request Google Calendar OAuth scopes for the device-calendar feature.

Google sign-in data is not used by Megashift for advertising and is not sold. Information required for authentication is shared with Supabase as part of the sign-in process.

Megashift's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements where applicable.

Sign in with Apple and X

On supported platforms, Megashift also offers Sign in with Apple and Sign in with X. Depending on the provider and your settings, the provider may supply an account identifier, email address, name and profile information. Authentication tokens are exchanged with Supabase to establish your Megashift session. Each identity provider also processes information under its own privacy policy.

5. Cloud Sync and Backup

When cloud synchronization is active, Megashift synchronizes selected app information between the local app database and a Supabase backend so that your Megashift data can be restored or used across devices.

Synchronized information may include:

  • work-calendar and schedule definitions;
  • shift and work entries;
  • breaks;
  • templates and alarm-template settings;
  • notes;
  • working-time and workday-definition settings;
  • theme and holiday settings;
  • holidays;
  • shift patterns and rotation values;
  • target/actual working-time settings;
  • hourly-rate and income settings; and
  • income and allowance rules.

Synchronized records are associated with your Megashift user ID. For multi-device synchronization, Megashift also uses an app-generated device identifier, last-active information and synchronization timestamps to coordinate changes between devices.

Ongoing Cloud Sync & Backup is an entitlement-controlled feature. After the first sign-in on a device, Megashift may temporarily enable an initial synchronization window for up to approximately 15 minutes even if the account does not have an ongoing Cloud Sync entitlement. This allows existing local data to be associated with the signed-in account and initially synchronized. After that window, ongoing synchronization is disabled unless the account has the required Cloud Sync entitlement.

Device-calendar events obtained through Android or iOS calendar access are not included in these Megashift cloud-sync tables.

6. Purchases and Subscriptions

Megashift uses RevenueCat to manage purchase and subscription entitlements. Apple App Store or Google Play processes the actual payment transaction.

RevenueCat may process information such as an App User ID, subscription and entitlement status, purchase history, store receipt or purchase-token information, first-seen/last-seen information and technical information needed to provide the subscription service.

When you are signed in, Megashift may associate RevenueCat with your Megashift/Supabase user ID so that subscription status can be associated with your account. When you are not signed in, RevenueCat may use an anonymous App User ID.

Megashift does not receive your full payment-card or bank-account details from Apple or Google.

7. Analytics and Crash Diagnostics

Megashift uses Google Firebase services to understand app operation and diagnose technical problems.

Firebase Analytics

Firebase Analytics is used for app-open and selected app events. Depending on the Firebase/Google configuration and platform, Firebase may process app-instance or installation identifiers, app/version information, device and operating-system information, approximate region derived from network information, and information about app events and interactions.

The full provider-generated login error message is not sent as a Firebase Analytics event parameter.

Firebase Crashlytics

Firebase Crashlytics is used to receive crash and non-fatal error reports. Crash reports may include stack traces, exception/error messages, relevant app state, app/version details, device and operating-system metadata, and Firebase/Crashlytics installation identifiers.

For authentication failures, Megashift may send the full provider-generated error message to Crashlytics, together with diagnostic context such as the sign-in provider, so that login problems can be investigated.

For certain rare database-migration failures, Megashift may include values from the affected local database row in the Crashlytics diagnostic report. Depending on the affected table, this may include content you entered in Megashift, such as shift, note or settings values. This diagnostic information is used to understand the cause of the technical failure and improve reliability; it is not used for advertising.

Because diagnostic information can contain information related to your account or app content, please do not intentionally enter passwords, authentication tokens, payment-card numbers or other highly sensitive secrets into free-text fields such as notes.

8. Advertising, Consent and Tracking Choices

Users who are eligible to see advertising may receive ads served through Google Mobile Ads (AdMob). Megashift uses Google's consent tools and, where applicable, IAB Transparency and Consent Framework information to determine advertising consent choices.

Depending on your consent choices, jurisdiction, device settings and Google's configuration, advertising processing may include device/app information, advertising or app-instance identifiers, IP address and approximate location derived from it, ad interactions, consent status and contextual information about the app.

Personalized advertising may use information about interests or prior activity where permitted and consented to. Non-personalized advertising may still use limited information for purposes such as contextual ad selection, fraud prevention, frequency capping and aggregated measurement.

On iOS, Megashift uses Apple's App Tracking Transparency mechanism where required before accessing the advertising identifier for tracking or personalized advertising.

Where available, you can review or change advertising/privacy choices through privacy options provided in the app or through your device settings.

9. Website and Support Communication

The Megashift website is hosted through Vercel. Hosting infrastructure may process information needed to deliver and secure the website, such as IP address, request/connection metadata, browser/device information, requested URLs and timestamps, subject to Vercel's service configuration and policies.

The public Megashift marketing pages do not intentionally add advertising tags, embedded marketing trackers, third-party web fonts or a custom contact-form backend. The password-reset page communicates with Supabase to complete the password-reset flow.

If you contact megashift.app@gmail.com, we receive your email address, message content and any attachments or information you choose to provide. The mailbox is provided through Google/Gmail, so Google also processes that communication under its own terms and privacy policy. We use support correspondence to answer your request, troubleshoot problems, protect the service and maintain appropriate support records.

10. Service Providers and Recipients

Depending on the features you use, Megashift may use the following third-party providers:

  • Supabase — account authentication, sessions, cloud database, synchronization and backup;
  • Google / Firebase — Firebase Analytics, Firebase Crashlytics, Google sign-in, AdMob and related consent/advertising services;
  • RevenueCat — purchase and subscription entitlement management;
  • Apple — Sign in with Apple, App Store distribution and purchases;
  • Google Play — app distribution and purchases;
  • X — optional X sign-in;
  • Vercel — website hosting and delivery; and
  • Google/Gmail — support email hosting.

These providers process information under their respective agreements and privacy policies. We may also disclose information if required by applicable law, valid legal process, or when reasonably necessary to protect users, the service or legal rights.

12. Data Retention, Account Deletion and Your Rights

Local app information normally remains on your device until you delete it, clear the app's data or uninstall the app, subject to operating-system behavior and device backups.

Account and synchronized cloud information is retained for as long as needed to provide the account/cloud service, maintain security and integrity, resolve support issues, comply with legal obligations and handle deletion/synchronization. Service-provider backups and logs may be retained for additional periods according to the provider's retention and backup processes.

Purchase and subscription records are retained as needed to provide and verify entitlements and as required by Apple, Google, RevenueCat or applicable law. Analytics, advertising and diagnostic information is retained according to the relevant service configuration and provider policies.

Account deletion

At present, account deletion requests are handled manually. You may request deletion of your Megashift account and associated Megashift cloud data by emailing megashift.app@gmail.com from the email address associated with your account, or by providing sufficient information for us to verify the account belongs to you.

We may need to verify your identity before carrying out a deletion request. Information may be retained where required by law, for security or fraud prevention, or to establish, exercise or defend legal claims. Independent records maintained by Apple, Google, RevenueCat or other service providers may also be subject to their own legal or contractual retention requirements.

Deleting a Megashift account does not automatically cancel an active App Store or Google Play subscription. Active subscriptions must be managed through the store where they were purchased.

Depending on applicable law, you may also have rights such as access, correction, deletion, restriction, objection, data portability and withdrawal of consent. You may have the right to lodge a complaint with the competent data-protection authority in your country or region.

13. International Data Transfers and Security

Some service providers used by Megashift operate internationally and may process information outside your country, including in the United States or other jurisdictions. Where required by applicable law, international transfers are handled using appropriate safeguards provided by law and the relevant service-provider agreements, such as adequacy decisions, standard contractual clauses or equivalent mechanisms.

Megashift uses technical and organizational measures appropriate to the service, including platform security mechanisms, authenticated access for account/cloud information and encrypted network connections provided by the relevant services. No method of electronic storage or transmission can be guaranteed to be completely secure.

14. Children, Policy Changes and Third-Party Privacy Information

Megashift is a work-schedule application and is not designed as a service directed to children. If you are a parent or guardian and believe that a child has provided personal information through a Megashift account, contact us at megashift.app@gmail.com so the matter can be reviewed.

We may update this Privacy Policy when Megashift features, service providers, legal requirements or data practices change. The current version will be published at https://www.megashiftapp.com/privacy with an updated revision date.

Third-party privacy information