Shift Calendar Planner Privacy Policy

Effective date: September 8, 2026

Shift Calendar Planner is designed as a local-first shift planning tool. This policy explains what information the app handles, why it is used, and how you can contact us.

Scope

This policy applies to the Shift Calendar Planner mobile app and related support pages.

Information you create in the app

You may create shift names, work times, break durations, locations, reminder preferences, notes, exported schedules, and related planning records. You may also enter currency, hourly rates, unpaid breaks, allowances, and per-shift pay overrides. These records provide the calendar, reminders, hours summaries, income estimates, exports, and settings features.

Local-first storage and account backup

The app keeps schedule records on your device by default. Pay settings and per-shift pay overrides are stored locally and are not included in cloud schedule backup. Income estimates are calculated on your device. If you export a report, it contains the schedule and pay details shown in the report; sharing sends that file to the destination you choose. You can use the core planning flow without signing in. If you choose cloud backup or cross-device restore, we use Firebase Authentication with Apple or Google sign-in to identify your account and back up the schedule records you choose to sync.

Device, diagnostics, and app information

The app may use basic app and device information such as app version, operating system version, device model, coarse network state, crash logs, and diagnostic events to keep the service reliable and to understand whether the app starts successfully. We do not use this information to provide payroll, tax, or employment-law advice.

Account and backup information

When account backup is enabled, we may process your Firebase user ID, sign-in provider identifier, email address or display name if provided by Apple or Google, backup timestamps, and schedule backup payloads. The backup is stored under your authenticated user ID and is used only for cloud backup, sync, and restore.

Notifications, location, and permissions

Notification permission is requested only when you enable shift reminders. Location permission is requested only when you tap Use current location in a shift location field. The app uses that one-time device location to fill the field, may ask the operating system geocoder for a readable place label, and saves the resulting label only if you save the template or calendar entry. You can also type a location manually. The app does not request contacts, SMS, call log, microphone, camera, or calendar permissions for the current core flow.

Analytics

We use Google Analytics for Firebase to understand app launches, feature use, exports, and purchase-flow outcomes. Firebase may process app-instance and device identifiers, app and device information, approximate location derived from network information, usage events, and automatically collected purchase events. Our custom events contain feature names, period types, access levels, and success or cancellation outcomes. We do not send shift names, schedule contents, pay rates, income amounts, notes, or exported report contents as analytics event properties.

Purchases

Apple processes payments for the one-time Pro lifetime in-app purchase. We use RevenueCat to validate purchases, restore access, and maintain Pro entitlements. RevenueCat processes an anonymous app-user identifier, store transaction and purchase-history information, entitlement status, and app/device information needed for this service. The app does not send your account email, schedule contents, or pay settings to RevenueCat. We do not receive your full payment card number from Apple.

Third-party services

The ad-enabled release may use Google AdMob to show ads after the app's privacy consent flow and Google's User Messaging Platform consent checks allow ad requests. AdMob may process app, device, advertising, network, diagnostics, and interaction signals needed to deliver, measure, and protect ads. Shift names, work times, notes, locations, reminder preferences, exported schedules, and backup payloads are not sent to AdMob by the app. Account backup uses Firebase Authentication and may use Apple or Google as sign-in providers. Google Analytics for Firebase provides usage analytics, and RevenueCat provides purchase validation and entitlement management. These services process information as described above under their own service and privacy terms.

Data sharing

We do not sell your personal information. We may share limited information with service providers only as needed to operate analytics, diagnostics, purchases, support, or store distribution, and only according to their service terms and applicable law.

Retention and deletion

Local schedule and pay records remain on your device until you edit or delete them, clear app data, or uninstall the app. Store transaction and entitlement records may be retained by Apple and RevenueCat to restore purchases and meet their record-keeping obligations. Account backup records remain until you delete backup/account data in the app or contact support. Support emails are retained only as needed to respond and maintain support records.

Children

The app is not directed to children. If you believe a child has provided personal information through support channels, contact us so we can review and delete it when required.

Your choices

You can use the app locally without signing in. You can manage app permissions in your device settings, sign out, delete account backup data where available, delete local records, clear app data, or uninstall the app. You can manage ad consent choices when Google UMP indicates that privacy options are required in your region. You may also limit tracking or personalized advertising through your device and platform settings where available. You can contact us to request access, correction, or deletion of support records associated with your email.

Contact

Support email: caoqun6666@gmail.com

Developer: Kevin

Privacy contact: Kevin