MileIQ Teams brings the mileage tracking and drive management that businesses rely on into a shared workspace for their people, and it is built on the same secure platform as the MileIQ app used by individuals. The information on this page explains how our security and privacy practices apply to a Teams plan: how a team's drives and records are managed, how they stay private to the team, the account-security protections that sit behind every MileIQ account, and the providers that help us run the service. As we add new capabilities and make security improvements, we will continue to expand and update this information.
MileIQ Teams is built for businesses that need their people's drives and mileage records organised together. A Teams plan gives you team and drive management, so the drives and records that belong to your organisation can be handled as a group and team members can focus on the driving that needs attention rather than on the record-keeping around it. Because Teams runs on the same application our individual users rely on every day, the features your team uses are the same features that have been designed, reviewed, and secured through our normal development and security processes.
A Teams plan runs on the same secure backend as the individual MileIQ app, so teams benefit from the same foundation of protections. That foundation includes the same account-security practices, the same encryption of traffic in transit, and the same separation of production from our other environments. It also includes the same monitoring and response: our security function keeps watch over our systems for signs of suspicious activity, reviews security alerts, sees that code is reviewed before it is deployed, and monitors our dependencies for known vulnerabilities. These protections are not specific to individuals or to businesses; they sit behind every MileIQ account, whether it is used on its own or as part of a team.
Data in a Teams plan stays with the team. Like the rest of the MileIQ service, Teams is multi-tenant, and we treat a team's data as private: it is not made available to people outside the team unless the owner explicitly shares it, and it is not exposed to other MileIQ customers. This is the same principle that governs the individual app — your data is private and not accessible to other users unless you choose to share it — applied to the drives and records a team manages together. Please see our Privacy Policy for more information about how MileIQ collects, uses, discloses, and safeguards personal information.
Team members sign in with the same account security as any other MileIQ user. MileIQ never stores passwords in plaintext; we store a cryptographic hash, so that actual passwords remain protected even in the unlikely event of a breach. You can sign in with Google or Apple, or with an email address and password; when you use Google or Apple, you can reach your account without creating or sharing a MileIQ-specific password. These protections apply whether a MileIQ account is used on its own or as part of a team.
MileIQ performs automated backups with point-in-time recovery, and we regularly back up our users' content. If data is lost or removed, those backups allow us to restore it, so that a team's drives and mileage records are not permanently lost through a simple mistake. Backups are operated on the same public cloud infrastructure as the rest of the service, under the same separation between production and our other environments.
MileIQ relies on a limited set of trusted service providers to help us operate the service, and Teams is supported by the same providers as the rest of MileIQ. We evaluate and perform due diligence on all of our vendors prior to engagement to ensure their security and privacy practices meet a suitable standard; if they do not meet our requirements, we do not proceed with them. Our current subprocessors, and the services each one provides, are published on our subprocessors page.