# Privacy Policy — Easy Dispatch Technician **Last updated:** June 30, 2026 **App identifier:** `ro.easydispatch.app` **Data controller:** Autoliv (TRO) --- ## 1. Purpose of This Policy Easy Dispatch Technician is an internal enterprise tool used by factory-floor technicians at our manufacturing plant. The app's sole purpose is to receive, track, and complete dispatch work orders assigned to technicians. This policy explains what data the app collects, why it collects it, and how that data is handled. --- ## 2. What Data We Collect and Why ### 2.1 Employee ID (Identifier) When you log in, you provide your employee ID. This ID is used to: - Authenticate you against the company's internal directory - Assign and display dispatch items relevant to your role and shift - Record who completed each dispatch (audit trail) We do **not** collect your name, personal address, phone number, or any government-issued identifier beyond what is necessary for employment record matching. ### 2.2 Dispatch Data The app displays and tracks dispatch work orders — everything visible on screen (order descriptions, locations, priority, status, due times) mirrors data from the company's backend dispatch system. When you complete a dispatch, the app sends back: - Which dispatch was completed - The timestamp of completion - Any fix notes or free-text answers you entered This data is stored in the company's backend servers for operational record-keeping, shift handover, and compliance with manufacturing procedures. ### 2.3 Firebase Cloud Messaging (FCM) Token The app registers with Google's Firebase Cloud Messaging service to receive push notifications when a new dispatch is assigned. An FCM token (a device-scoped, rotating identifier) is generated by Google Play Services and transmitted to our backend so we can route the notification to your device. The token contains no personal information and is used exclusively for push notification delivery. ### 2.4 Local (SQLite) Storage The app stores dispatch records and previously entered free-text answers locally on your device in an SQLite database. This data: - Is never transmitted to any party other than the company's backend - Enables the app to function offline and show past responses as quick-fill suggestions - Is deleted when the app is uninstalled or when you log out ### 2.5 Crash and Error Telemetry The app includes an optional crash reporter that sends diagnostic data to the company's backend server when the app encounters an unrecoverable error. This data includes: - Device model, Android version, and app version - Stack trace and last actions before the crash - Timestamp of the error This data is used **solely** to diagnose and fix software defects. It is not used for profiling, analytics, or any non-reliability purpose. You may opt out by disabling crash reporting in the app settings. --- ## 3. How Data Is Transmitted All communication between the app and the company's backend servers is: - Encrypted in transit using **TLS v1.2+ with mutual TLS (mTLS)** authentication - Sent over HTTPS only - Authenticated per-request using short-lived token-based session credentials No data is transmitted over unencrypted channels. --- ## 4. Data Retention - **Dispatch records** are retained in the company's backend in accordance with the plant's manufacturing record-keeping policy (typically 1–3 years). - **Crash reports** are retained for up to 90 days, then automatically purged. - **FCM tokens** are regenerated periodically; stale tokens are cleaned up within 7 days of inactivity. --- ## 5. Data Sharing and Third Parties | Party | What Is Shared | Purpose | |-------|---------------|---------| | **Google (Firebase Cloud Messaging)** | FCM token (device-scoped, non-personal) | Push notification delivery — standard Android notification channel | | **Company's backend servers** | All dispatch and usage data | Dispatch operations, audit trail, shift management | We do **not**: - Sell any data to any third party - Share data with advertisers, data brokers, or analytics platforms - Send data outside the company's control except for the FCM push notification delivery described above - Use third-party analytics SDKs, tracking pixels, or behavioral profiling tools --- ## 6. No Automatic Decision-Making The app does not engage in automated decision-making, profiling, or behavioral analysis. Dispatches are assigned by a human dispatcher or by deterministic rules (shift schedule, area coverage) — never by algorithmic scoring or behavioral inference. --- ## 7. Your Rights Since this is an internal enterprise tool, your use of the app is governed by your employment agreement and the company's IT acceptable-use policy. You may: - **Stop using the app** at any time — doing so will not affect your employment status (alternate notification channels are available). - **Request a copy** of dispatch records associated with your employee ID by contacting the IT department. - **Request deletion** of locally cached data by uninstalling the app or logging out. - **Opt out of crash reporting** via the app's settings screen. --- ## 8. Contact For questions about this privacy policy or the data the app collects, contact: **APS Department** — TRO Email: [it-support@autoliv.com] --- ## 9. Changes to This Policy This policy is updated as needed to reflect operational changes. Updates will be announced via the company's internal communication channels. Continued use of the app after an update constitutes acceptance of the revised policy.