CareShiftER privacy policy

Updated October 14, 2026. This policy describes CareShiftER by Lucentix Labs LLC, including the account, scheduling, pay-estimate, backup, and purchase features in version 2.5.0.

Contact support@lucentixlabs.com for product and data requests, or legal@lucentixlabs.com for privacy questions.

Information used by CareShiftER

Account information. The configured production app requires a verified sign-in. Email registration and sign-in send the email address and password to Firebase Authentication. Firebase supplies an account identifier and authentication tokens. Sign in with Apple, when used, supplies an Apple sign-in credential and may supply a name and email address or Apple relay address. The app retains account identity and verification state on the device. Authentication tokens and information used for sign-in or reauthentication are stored through the operating system’s secure storage.

Schedule and profile information. Information you enter can include a name, work role, department, workplace, profile email, shift dates and times, notes, tags, repeating patterns, and custom presets. Optional pay information includes rates, unpaid breaks, Scheduled/Worked status, employer/pay groups, currency, overtime and premium rules, and pay-period settings. Calendar, language, appearance, time-zone, and reminder preferences are also saved on the device.

Cloud backups. When you choose the manual cloud save action, CareShiftER sends the schedule, profile/pay information, patterns, presets, preferences, and an update time to Firebase Firestore under your account. This can include shift notes and other personal information you entered. Cloud restore retrieves that saved information. Creating an account does not itself mean that every schedule change is continuously backed up.

Purchases. The platform store processes payment. RevenueCat processes purchase information and an app user identifier so the app can validate purchases, restore access, and determine lifetime entitlement. Store and RevenueCat records can include purchase history, product and transaction identifiers, and entitlement status. The app does not ask you to enter payment-card details into CareShiftER. RevenueCat also receives technical request information such as app and operating-system versions, device model, preferred languages, and, on Apple devices, the vendor identifier (IDFV). This supports purchase services and purchase analytics; it is separate from your payment-card information.

App usage information. The included Expo Insights library automatically sends an app-launch event with a persistent, randomly generated installation identifier, the app version, operating-system version, and platform to Expo. This measures app usage across versions and platforms. The event does not contain your schedule, pay, notes, sign-in email, or Firebase account ID. It is sent automatically when the app starts; there is currently no in-app switch for this usage measurement.

Service and security information. Firebase Authentication processes connection information such as IP address and user agent for authentication and abuse prevention. Firebase App Check uses app/device attestation and tokens to help protect service access. These providers handle service information according to their own policies. If you contact support, we receive the message, reply address, and any attachments you choose to send.

How information is used

Information is used to authenticate your account, display and manage your schedule, calculate the pay estimates you request, remember preferences, schedule reminders, create or restore backups, validate lifetime access, understand app usage and purchase activity, protect service access, and respond to support or data requests.

CareShiftER pay amounts are estimates based on the details and rules you enter. Schedule notes are general user-entered content; keep information you do not want included in a backup or shared schedule out of those fields.

Local files and sharing

Save Backup to Files creates a readable JSON file containing the schedule and included preferences. The file includes personal notes and pay details, but excludes sign-in credentials, authentication tokens, purchase access, and trial dates. You choose where to save or share it. A storage or messaging provider you choose will handle the file under its own terms.

Before a restore replaces data, the app creates a local recovery copy. This copy remains on the same device and can be replaced by a later restore. It is not an independent cloud backup.

Text sharing, schedule images, calendar files, and calendar export disclose the selected information to the destination you choose. Those copies may remain after you delete data inside CareShiftER. CareShiftER does not control recipients’ copies or files you save outside the app.

Permissions

Notifications are used for shift reminders when you allow them. Calendar permission is requested for native calendar export. The file picker gives access to a backup you select for import. Biometric sign-in uses the device’s authentication system; CareShiftER receives an authentication result, not your face or fingerprint template.

Workplace/location fields contain text you enter. They do not require GPS location tracking. A file chosen for import is different from unrestricted access to all personal files.

Services

CareShiftER uses Firebase Authentication, Firestore, and App Check for the account, cloud-backup, and security functions described above. Firebase’s privacy and security information explains its service processing and retention.

RevenueCat provides purchase validation and entitlement management. See its privacy policy. Apple processes App Store purchases and Sign in with Apple under Apple’s applicable privacy terms. Other stores, file providers, calendars, and messaging apps handle information when you choose their services.

Expo provides the app-usage measurement described above. See its privacy policy and EAS Insights app-usage information.

Network requests to these services use HTTPS. Local storage and exported backups have different protections: exported JSON is not password-encrypted by CareShiftER. Device and file-provider protections depend on your settings.

Retention and deletion

Schedule/profile data stays in the app’s local storage until you edit, replace, or delete it. Recovery data is kept locally until replaced or cleared. Uninstalling the app is not a request to delete a cloud account, a cloud backup, store transaction records, or files outside the app.

Use Settings → Delete All Data to clear local schedule/preferences and the local recovery copy while keeping the account. In the updated app, cloud deletion must succeed before local data is cleared; a failure keeps the account and local data available for retry. Use Settings → Delete Account to request removal of the Firebase account, saved cloud schedule, and local app data. An authentication or service failure can prevent part of the request; contact support if you need cloud-deletion confirmation or cannot access the account.

For a web-based request, email support@lucentixlabs.com with the account email and whether you want the cloud schedule deleted or the account and associated cloud schedule deleted. We may need to verify account ownership. Do not send a password or verification code. Details are in the account and data deletion instructions.

Deleting the Firebase account does not automatically erase purchase records held by Apple or RevenueCat, provider security records, Expo app-usage records, exported files, or recipients’ copies. Service providers may retain information according to their documented retention obligations. Requests about those records can be raised with support and the relevant provider. No fixed deletion completion time is promised here.

Your choices and requests

You can edit your schedule/profile, choose whether to use manual cloud backups, control notification/calendar permissions, export a complete backup, and request deletion as described above. Privacy rights depend on where you live; contact us to request access, correction, export, or deletion, or to ask how a specific data item is handled.

Updates

Changes to the app or its services may require updates to this policy. The date above identifies the latest revision. The published policy and store disclosures should describe the version distributed to you.