Privacy Policy — Mindtronic AI Fleet Management System
Data Controller: Mindtronic AI Co., Ltd. ("Mindtronic AI", "we", "us", "our")
Registered office: Cayman Islands
Service covered: Mindtronic AI Fleet Management System and its associated web dashboard
(MAIFleet), mobile applications (MAIFleet, FleetReg), in-vehicle devices,
and related APIs (collectively, the "Service").
Effective date: 2026-11-17
Version: 1.1
This Privacy Policy explains how Mindtronic AI collects, processes, stores, discloses, and protects personal data in the course of providing the Service. It is published in accordance with the Taiwan Personal Data Protection Act (個人資料保護法, "PDPA") and its Enforcement Rules. Where users or data subjects are located outside Taiwan, additional local laws (e.g., GDPR for the EU/EEA, UK GDPR, CCPA/CPRA for California) may also apply; in case of conflict, the stricter standard prevails.
Use of the Service is also governed by our Terms of Service.
Contents
- 1. Who this policy applies to
- 2. Personal data we collect
- 3. Sources of personal data
- 4. Recipients and disclosure
- 5. International transfers
- 6. Retention
- 7. Your rights as a data subject
- 8. Security
- 9. Children's data
- 10. Contact and complaints
- 11. Cookies and similar technologies
- 12. Automated decision-making and profiling
- 13. Changes to this policy
1. Who this policy applies to
The Service is a business-to-business ("B2B") fleet management platform. Personal data is collected about three categories of data subjects:
- Fleet account users — administrators, dispatchers, managers, and other employees of our customers ("Customers") who sign in to the web dashboard or mobile app.
- Drivers — operators of vehicles equipped with our in-vehicle devices, whose biometric, location, behavioural, audio and video data are processed to deliver the Service to the Customer.
- Third parties incidentally captured — pedestrians, other road users, vehicle license plates, package recipients, and other individuals whose data may be captured by in-vehicle cameras, automatic license-plate recognition ("ALPR"), or dispatch records.
For categories (2) and (3), the Customer is typically the data controller and Mindtronic AI acts as a data processor. For category (1), Mindtronic AI is the data controller in respect of account credentials and platform telemetry.
2. Personal data we collect
We collect the categories of personal data listed below.
2.1 Account and identity data
- Name, email address, phone number, role/permission level, organization ("fleet") membership, language preference, profile photo.
- Authentication credentials (handled via Firebase Authentication); password hashes are not stored on Mindtronic AI servers.
- Session tokens (JWT), sign-in timestamps, and device/browser metadata.
- Install codes issued to installers for the FleetReg app, with the fleet they belong to and their expiry.
2.2 Driver data
- Driver name, employee ID, contact phone, assigned vehicle, driving licence reference, duty-shift schedules, clock-on/clock-off records.
- Face biometric templates used for in-vehicle Face ID driver recognition. These are mathematical embeddings derived from face images captured at enrolment and during driving; they are classified as "special category" /sensitive personal data under PDPA Article 6 and equivalent provisions.
2.3 Vehicle and location data
- Vehicle registration (license plate), VIN, device serial number, firmware version, VPN IP.
- GPS coordinates (latitude, longitude), heading, speed, ignition status, fuel level, mileage, and other CAN-bus telemetry collected continuously while the vehicle is operating.
- Trip history, geofence entry/exit events, route playback data.
- Device installation records created with the FleetReg app: the vehicle plate number being registered and the install code used. The SIM PIN entered in FleetReg is only encoded in the QR code shown to the in-vehicle device; the app does not send it to our servers.
2.4 Driver-monitoring and safety events
- Driver-Monitoring System ("DMS") events: drowsiness, distraction, smartphone use, smoking, seat-belt status, and similar attention/behaviour events.
- Advanced Driver-Assistance System ("ADAS") events: forward-collision warning, lane departure, pedestrian/cyclist proximity, headway warnings.
- Harsh-driving events (acceleration, braking, cornering), speeding, idling, and driver-score metrics.
2.5 Audio and video data
- In-vehicle DVR video and audio recordings (cabin-facing and road-facing cameras) — stored on the in-vehicle device and selectively uploaded on event triggers or manual request.
- Event snapshots/clips attached to safety events.
- Live-view streams initiated by authorized fleet users.
2.6 ALPR (Automatic License Plate Recognition) data
- License plates detected from road-facing cameras, with timestamp, location, and detection confidence.
- Watchlist matches (hotlist hits) and operator-created sighting reports.
2.7 Communications and notifications
- In-app notifications, alert delivery records (FCM push tokens), read/ack state, and any messages exchanged via the platform.
2.8 Technical and usage data
- IP address, device type, OS version, app version, crash logs, diagnostic logs, feature-usage metrics, and audit logs of administrative actions.
2.9 Special categories
The following are treated with elevated safeguards under PDPA Article 6 and relevant overseas equivalents:
- Biometric data (face templates).
- Precise geolocation of identifiable drivers.
- Audio recordings that may contain identifiable speech.
3. Sources of personal data
We obtain personal data from:
- The data subject directly — when an account user signs in or updates their profile, or a driver enrols their face.
- The Customer — when a fleet administrator creates accounts, imports drivers, watchlists, or recipient lists.
- In-vehicle devices — automatically generated telemetry, video, audio, and event data while the vehicle is in operation.
- Third-party services — geocoding providers (to resolve coordinates to addresses), map providers, Firebase Authentication, and Firebase Cloud Messaging.
4. Recipients and disclosure
We disclose personal data only to the categories of recipient listed below, each bound by confidentiality and data-protection obligations:
- The Customer that operates the fleet the data subject belongs to.
- Authorised users within the Customer organisation with role-based access (administrators, dispatchers, safety officers).
- Sub-processors engaged by Mindtronic AI to deliver the Service:
- Cloud hosting and storage providers;
- Firebase Authentication and Firebase Cloud Messaging (Google LLC);
- Map and geocoding providers;
- Crash-reporting and logging services;
- Email/SMS gateway providers. A current list of sub-processors is available on written request.
- Professional advisers (auditors, lawyers, accountants) under professional duties of confidentiality.
- Competent authorities, courts, or law-enforcement agencies where disclosure is required by law or to protect the rights, property, or safety of Mindtronic AI, our Customers, or the public.
- Successors in the event of merger, acquisition, or reorganization, subject to equivalent protection.
We do not sell personal data, and we do not use personal data for third-party advertising.
5. International transfers
Personal data is primarily processed in Taiwan. Some sub-processors (e.g., Firebase, Google Cloud, map providers) may process data outside Taiwan, including in the United States and the European Union. Where data is transferred outside Taiwan, we rely on:
- Sub-processor contractual commitments equivalent to PDPA protections;
- Standard contractual clauses or adequacy decisions where required by the data subject's local law (e.g., GDPR);
- The data subject's informed consent where applicable.
The National Development Council (NDC) of Taiwan has not imposed cross-border restrictions on the categories of data we transfer; if such restrictions are imposed in the future, we will update this policy and notify affected Customers.
6. Retention
We retain personal data only for as long as necessary for the purposes set out above, or as required by law:
| Data category | Default retention period |
|---|---|
| Account profile | Duration of account + 3 years after closure (for audit/legal) |
| Driver records | Duration of employment with the Customer + 5 years |
| GPS / trip history | 6 months (rolling), unless extended by Customer contract |
| DMS / ADAS event metadata | 6 months (rolling) |
| Event video/audio clips | 90 days, unless flagged for incident review |
| ALPR detections | 90 days; watchlist hits up to 2 years |
| Face biometric templates | Until driver de-enrolment or end of assignment |
| Audit / security logs | 2 years |
| Diagnostic / crash logs | 90 days |
Retention periods may be extended where required to comply with a legal obligation, resolve a dispute, or enforce our agreements. After the retention period, data is securely deleted or irreversibly anonymized.
7. Your rights as a data subject
Under PDPA Article 3 (and Articles 10–11), data subjects have the following rights with respect to their personal data:
- Right of inquiry and access — to ask whether we hold your data and obtain a copy.
- Right to a copy / data portability — to receive a machine-readable copy where technically feasible.
- Right to rectification — to correct or supplement inaccurate or incomplete data.
- Right to deletion — to request erasure when data is no longer needed.
- Right to restrict processing — to ask us to stop collecting, processing, or using your data.
- Right to withdraw consent — where processing is based on consent.
- Right to object — to certain processing on the basis of legitimate interests.
- Right to lodge a complaint — with the competent supervisory authority (see Section 10).
If you are a Driver whose Customer is the data controller, please direct your request to your employer/fleet operator first; if they are unable to resolve it, you may contact us directly at the address in Section 10.
To exercise any right, contact us via the channels in Section 10. We will respond within 30 days of a verified request. We may need to verify your identity before acting on a request and may decline requests that are manifestly unfounded, excessive, or would prejudice the rights of others.
Consequences of refusing to provide data
For account users, refusing to provide name, email, and authentication credentials means we cannot create or maintain an account. For drivers, refusing telematics, video, or biometric processing means the in-vehicle safety features and Face ID recognition cannot operate; alternative non-biometric driver-identification methods may be available — please consult your fleet administrator.
8. Security
We implement administrative, technical, and physical safeguards appropriate to the risk, including:
- Encryption in transit (TLS 1.2+ for all client–server traffic; SRTP for live media where supported).
- Encryption at rest for stored video, audio, and database content.
- Role-based access control with least-privilege defaults; audit logging of privileged actions.
- Network segmentation and VPN-only access to in-vehicle devices.
- Periodic security reviews and penetration testing.
- Vendor due-diligence and data-processing agreements with sub-processors.
- Personnel confidentiality undertakings and security awareness training.
- Incident-response procedures including notification to affected Customers and authorities where required by law.
No system is perfectly secure. If you become aware of any vulnerability or suspected incident, please report it to [email protected].
9. Children's data
The Service is not directed to children under 16, and we do not knowingly collect personal data from children. If you believe a child's data has been collected, please contact us so we can delete it.
10. Contact and complaints
For privacy-related inquiries, rights requests, or complaints:
- Data Protection Contact: Mindtronic AI — Privacy Office
- Email: [email protected]
- Postal address: Mindtronic AI Co., Ltd., Taipei, Taiwan (R.O.C.)
If you are not satisfied with our response, you may lodge a complaint with the competent Taiwan supervisory authority. Under the PDPA, the supervisory authority is the central competent authority for the relevant industry; for private-sector data controllers in the technology sector, complaints can be directed to the Ministry of Digital Affairs (數位發展部) and the National Development Council (國家發展委員會) for matters of cross-border data flow, or to the local government's Bureau of Legal Affairs at the data controller's place of registration.
Data subjects located in the EU/EEA may also lodge a complaint with their local Data Protection Authority.
11. Cookies and similar technologies
The web dashboard uses essential cookies and local storage for authentication, session management, language preference, and user-interface state. We do not use third-party advertising or cross-site tracking cookies. Analytics, where used, is limited to first-party, aggregated usage metrics without persistent cross-service identifiers.
You can disable cookies in your browser; doing so may prevent you from signing in or using certain features.
12. Automated decision-making and profiling
We use automated detection for DMS/ADAS events, driver scoring, and ALPR matches. These detections may be reviewed by a fleet manager and form the basis for coaching or operational decisions. Decisions that produce legal or similarly significant effects on a data subject (e.g., disciplinary action) are made by the Customer with human review; Mindtronic AI does not make such decisions on behalf of the Customer.
Where required by law, data subjects have the right to obtain human intervention, express their point of view, and contest an automated decision; please contact the Customer or us as set out in Section 10.
13. Changes to this policy
We may update this Privacy Policy from time to time. Material changes will be notified through the Service and/or by email to account holders, and the effective date at the top of this document will be updated. Continued use of the Service after the effective date constitutes acceptance of the updated policy.
© 2026 Mindtronic AI Co., Ltd. All rights reserved.