Not a substitute for store forms: Firebase settings, sign-in methods, support processes and future SDKs can change the correct answers. Re-check the final release binary and console configuration.
CategoryCurrent behaviorMain purpose
Account informationEmail, display name, authentication ID, company membership and staff access metadata.Authentication and authorization
Business contentConstruction operational, financial, workforce, safety, quality and document records entered by authorized users.ERP functionality and reporting
Device and sync dataDevice ID, platform, app/schema version, versions, timestamps, queue, conflict and permission context.Security, synchronization and recovery
Crash diagnosticsAndroid release builds may send crash and device/app context to Firebase Crashlytics.Reliability and troubleshooting
AdvertisingNo advertising SDK is included in the inspected current app.Not applicable
Data saleThe current privacy design does not sell personal information.Not applicable
Local protectionEncrypted local database and device-secured key.Protect data at rest
Backup protectionArgon2id + AES-256-GCM encrypted user-created backup.Disaster recovery
Account deletionIn-app deletion and a public request pathway; active company ownership must be transferred or closed first.User control and legal compliance

Production checklist

  • Confirm the store developer/publisher name matches the Privacy Policy.
  • Publish working HTTPS privacy, support and account-deletion URLs.
  • Review Firebase Authentication, Firestore, App Check and Crashlytics settings.
  • Verify whether production support emails or logs create additional retained data.
  • Keep Data safety answers consistent with the final binary and actual business process.
  • Update this page whenever a new SDK, analytics tool, cloud attachment service or payment system is added.