CrewHours privacy policy

Effective date: October 6, 2026. Analytics described below applies to builds with Firebase Analytics enabled. Earlier analytics-disabled builds do not send usage events.

Work records on your device

CrewHours stores the employees, contact details, projects, work records, rates, amounts, notes, attachments, preferences and reminder definitions you enter in local storage on your device. These business records are not uploaded to a CrewHours database or included in analytics events. CrewHours does not require its own account or provide a shared cloud database.

Photos, contacts and notifications

You may choose photos or take a photo for a work record, select a contact to import employee details, or enable local reminders. CrewHours uses the related system controls and permissions. Imported details and attachments become part of the records stored on your device. You can change permissions in device settings.

Exports and backups

Reports, email attachments, printed content and ZIP backups are sent only to the destinations you select. Those destinations may include Apple or third-party services and are subject to their policies. A backup can contain business data, photos, preferences and reminder definitions. It does not include analytics activation markers or analytics purchase-association state. Keep backup files secure. Device backups managed by your operating system may also include app data, depending on your settings.

Subscriptions

Apple processes purchases and payments. CrewHours uses StoreKit to verify subscription status and stores limited transaction identifiers locally to handle delivery and avoid duplicate analytics conversion events. Restoring a backup does not transfer purchase entitlement. We do not receive your payment card details. Analytics includes coarse subscription results, such as monthly or annual plan, trial or paid access, purchase environment, cancellation, pending approval, verified Pro activation, renewal or purchase restoration. CrewHours does not send receipt data or transaction identifiers in custom analytics events, or call Firebase's transaction-revenue reporting API.

Product analytics

Analytics-enabled builds use Google Analytics for Firebase to understand first successful time entry, feature use, Pro conversion, active use and retention. Collection starts automatically in production builds. There is no separate analytics consent prompt or in-app switch to disable it.

Custom events contain only predefined screen names, operation types, coarse outcomes, counts and free or Pro status. They cover employee and project management, single and batch time entry, pay review, report preparation and delivery, subscriptions, backup and restore, photo attachment operations and reminder settings. Employee and project names or identifiers, contact details, work dates and times, wages, rates, budgets, notes, photo content, reminder messages, file paths and raw error messages are excluded.

The Firebase SDK also collects an app-instance identifier, session and engagement information, app and operating-system versions, device information and language, and limited SDK diagnostic metadata. Google Analytics derives general regional information from network addresses; CrewHours does not request GPS or precise location for analytics. Events are associated with an installation identifier, so the analytics is not described as completely anonymous and does not identify the employees in your work records.

CrewHours uses Analytics without advertising-identifier collection capability. IDFV collection, advertising storage, advertising user-data use, ad personalization and ad-network registration are disabled. We do not set a personal analytics user ID, link Analytics to an advertising account or use analytics for cross-app advertising tracking. The support website itself has no analytics script.

Analytics processing and retention

Google processes analytics data through Firebase and Google Analytics, potentially in countries other than yours. See Google's privacy policy and Firebase privacy and security information. The CrewHours GA4 property is configured for 14 months of user-level and event-level detail retention. User-data retention may refresh with new activity. Standard aggregated reports are not subject to this detail-retention limit.

Development builds disable analytics by default. Designated analytics-validation runs may send test events in DebugView; automated tests do not send analytics. Test purchases are identified by environment and excluded from production conversion analysis.

When you contact support

If you email support, we receive the email address, message and any attachments you choose to send. We use that information to respond and investigate the issue. Please avoid sending employee records or sensitive information unless necessary. Contact us to request removal of support correspondence, subject to applicable retention requirements.

Your choices

You control the business information you enter, optional device permissions and the reports or backups you share. Deleting the app removes its active local container, but does not immediately erase analytics already processed by Google or copies you previously exported or included in device backups. You can manage those exported copies separately. For requests about previously collected analytics, contact support; we will explain the available options and any limits to locating installation-based data without a CrewHours account.

Policy updates and contact

Changes to these practices will be reflected here with an updated effective date. For privacy questions, contact support@myxhd.com.

Use of CrewHours is governed by Apple's Standard Licensed Application End User License Agreement.