Clear terms.
Visible tracking.

Your business subscription

Online MyFleets subscriptions are offered to businesses. The order is the company, monthly base price and assigned-vehicle price shown before checkout, together with Stripe’s tax and payment summary. The company base fee starts at payment. Registering a phone vehicle or assigning a hardware tracker adds the per-vehicle charge; changes may be prorated. Hardware, installation and separately quoted integrations are not included.

Subscriptions renew monthly. Use Billing & cancellation in your workspace to cancel renewal, update payment details or see invoices. Cancellation takes effect at the end of the paid period. Refund requests follow CodifyAI’s refund policy. Failed payments may result in suspension after the applicable grace period; suspension stops access and tracking but does not immediately erase fleet history. Contact support if billing needs attention.

The iPhone app is in TestFlight beta; public App Store availability is not included as a guaranteed delivery date. Browser access does not turn a phone into a tracker. Provider integrations, measured energy data and hardware availability depend on the configured service. Estimates are not certified emissions measurements. No guaranteed uptime, legal mileage certification or emergency service is implied.

Read the Terms of Service, SaaS Subscription Terms, Refund & Cancellation Policy and Acceptable Use Policy. This MyFleets schedule specifies the product and billing model; a separately agreed written order governs any negotiated exceptions. Mandatory legal rights are unaffected.

Privacy for MyFleets

CodifyAI is the controller for customer account administration, purchases, billing, security and support. Your fleet organisation determines why and how its drivers’ and vehicles’ data is used and normally acts as controller for that fleet data. CodifyAI processes fleet data to deliver the service on the organisation’s documented instructions.

Depending on enabled features, MyFleets processes names and business contact details; account, company and role identifiers; vehicle plates and registry information; GPS positions, route timestamps and speed; work shifts, phone health and permission status; dispatch stops and delivery evidence; mileage purposes; maintenance and charging records; uploaded files; and access or change logs. Only enter information necessary for fleet work. Payment card details are entered with Stripe, not stored in MyFleets.

Account and service processing supports the contract; billing records may be required by law; service security relies on legitimate interests. The fleet organisation must identify and document its own lawful basis for employee or contractor tracking. Granting an iPhone location permission or starting a shift is a product control, not proof that an employer has established a lawful basis.

Read CodifyAI’s Privacy Policy, Security Policy and provider information.

Data processing schedule

For MyFleets, the subject matter of the CodifyAI Data Processing Agreement is the hosted fleet workspace, mobile tracking and associated fleet workflows. Its nature and purpose are collecting, storing, displaying and exporting fleet information, providing authorised notifications, and maintaining and supporting the service. Data subjects can include company users, drivers and delivery recipients; data categories are listed above. Processing lasts for the service and the applicable contractual return/deletion period.

The DPA’s provisions on documented instructions, confidentiality, assistance, incidents, audits, subprocessors and data return/deletion apply. MyFleets uses logical company and permission controls in shared services; it does not promise a separate physical database for every company. This product-specific description supplements the DPA’s Odoo hosting examples. Contact [email protected] for a separately signed agreement, agreed retention settings or technical/security evidence.

Services involved include Hetzner hosting; Stripe for checkout and billing; Apple for native maps, app distribution and enabled push notifications; and configured plate-data providers (Synsbasen, TjekBil or Nummerplade.info). Opening a map or requesting a plate lookup can disclose the map area or plate to the relevant provider. Providers’ roles and transfer safeguards depend on the service and agreement; this page does not claim that every provider is a processor or that all processing remains in one country. Refer to CodifyAI’s provider information and request the current service-specific arrangements when required.

Do not assume every record disappears after 90 days: that limit currently applies to generated report snapshots. Fleet records and source tracking data follow the organisation’s retention instructions and the applicable service agreement. After termination, request export or deletion through support within the return period described in CodifyAI’s SaaS terms. Contractual, accounting and dispute records may need separate retention. Deletion and export requests require identity and company-authority checks.

Tracking stays visible

Phone tracking requires the installed app, granted location permissions and an active work shift. Tracking status is visible. A private-use pause remains available even when an owner protects management settings with a PIN. iOS permissions and device controls remain under the phone owner’s control; MyFleets does not claim to prevent someone force-quitting or uninstalling an app.

Fleet organisations must inform affected people before tracking, limit access and collection to the stated purpose, define retention, and assess any workplace-monitoring or data-protection impact requirements. Do not use MyFleets for covert monitoring. GPS devices have their own collection behaviour; the phone’s shift switch does not stop a separate hardware tracker.

Necessary browser storage

The purchase page keeps a random order recovery reference in myfleets.purchase.v1 local storage so an interrupted payment can be resumed in the same browser. It is removed after successful account activation. The browser workspace keeps its access token in myfleets.web.token session storage and uses the Traccar session cookie for the live map. Signing out clears the workspace access and map session. The purchase and workspace pages do not add advertising or analytics scripts.

Other MyFleets screens, maps and Stripe’s hosted checkout may use their own service storage. See the CodifyAI Cookie Policy and the relevant provider notices. Clearing browser storage before activation removes local order recovery; contact support with your receipt if needed.

Requests and contact

For access, correction, export, deletion, restriction or objections concerning fleet data, contact your fleet organisation first. CodifyAI assists it under the DPA. For CodifyAI-controlled account or billing data, use the data-rights page or email [email protected]. We may need to verify your identity and authority. You may complain to your competent data-protection authority, including ANSPDCP in Romania.

Service support: [email protected]. Security reports: [email protected]. General company and consumer information remains in the CodifyAI Legal Center.