--- title: "Security & Trust" description: "An overview of the security, privacy, and operational safeguards used to protect customer information within Autopilot." source: "https://legal.aplt.ai/legal/security-trust" updated: "2026-06-30T09:01:23.604658+00:00" product: Autopilot content_type: legal --- # Security & Trust An overview of the security, privacy, and operational safeguards used to protect customer information within Autopilot. ## Purpose Autopilot is a dealership operations platform that stores and processes operational and customer information on behalf of the dealerships that use it. This includes information such as customer contact details, vehicle sales, finance and administration workflows, team activity, communications, reporting, and dealership configuration. Protecting this information is a fundamental part of how the platform is designed and operated. This Security & Trust page describes Autopilot's current security practices at a high level. It is provided for informational purposes and is not intended to create a separate contractual commitment, security guarantee, or exhaustive technical specification. It does not replace, modify, or expand Autopilot's [Terms of Service](/legal/terms), [Privacy Policy](/legal/privacy), or other legal terms. It explains Autopilot's security principles, technical controls, and operational practices, including how customer information is protected, how access is controlled, and how security risks are managed over time. Autopilot uses a defence-in-depth approach, combining multiple layers of protection rather than relying on a single security feature. These layers include managed infrastructure, authenticated access, database-level security policies, role and field permissions, secure integrations, account protection features, and operational processes designed to reduce risk and limit the impact of potential security incidents. No software platform can guarantee that security incidents are impossible. Autopilot's approach is to implement practical, layered controls that reduce the likelihood of unauthorised access and help customers manage security and privacy risks responsibly. It should be read alongside Autopilot's [Privacy Policy](/legal/privacy), [Subprocessors](/legal/subprocessors), and [Terms of Service](/legal/terms), which describe how personal information is handled, which third-party service providers may process customer information, and the legal terms governing use of the platform. ## Security principles Security is an ongoing process, not a single feature or guarantee. These principles guide how Autopilot designs and implements security controls. ### Defence in depth Autopilot uses multiple independent security controls to reduce reliance on any single technology or process. These controls include managed infrastructure, authenticated access, database-level security policies, role-based permissions, session management, export controls, operational logs, and trusted server-side operations. ### Least privilege Users should only be able to access the information and functionality required for their role. Access to dealership information is controlled through authentication, organisation membership, role-based permissions, field-level permissions, and database security policies. Administrative capabilities are limited to authorised users, and sensitive operations run through server-side services rather than browser clients. ### Security by default Security controls are built into the normal operation of the platform where practical, rather than relying solely on user configuration. Examples include encrypted communication, secure session handling, server-side validation, protected application secrets, and permission checks across application workflows. Additional account protection features, including multi-factor authentication and passkeys, are available for customers who choose to enable them. ### Privacy by design Because Autopilot processes customer and dealership information, privacy considerations are incorporated into the design of the platform. Access to information is restricted according to user permissions, customer information is logically separated between organisations, and third-party service providers are used to support secure service delivery. Autopilot includes practical and reasonable safeguards designed to help customers manage personal information responsibly and support their own privacy obligations, including obligations that may apply under the New Zealand Privacy Act. ### Continuous improvement Security threats, technology, and industry practices continue to evolve. Autopilot's security controls are reviewed and improved over time as new platform capabilities are introduced, security guidance changes, customer requirements evolve, and potential risks are identified. New security features are added to strengthen the platform while maintaining usability for dealerships and their staff. ## Information security Autopilot is designed to protect dealership and customer information as it is entered, stored, processed, and accessed by authorised users. This section describes the primary technical and operational controls used to protect customer information. ### Infrastructure and hosting Autopilot is built on managed cloud infrastructure for hosting, authentication, database management, and storage. Autopilot manages application configuration, access controls, server-side credentials, and permission checks on top of those managed services. Sensitive application secrets and privileged credentials are stored server-side and are not exposed to browser clients or end users. Customer information is stored in managed database and storage infrastructure. Autopilot does not currently claim separate application-level field encryption for customer or deal records. Autopilot relies on third-party service providers for infrastructure-level controls. Autopilot does not make specific statements about provider-level encryption at rest, backups, point-in-time recovery, redundancy, or disaster recovery unless those controls have been separately verified. Information transmitted between users and the platform is protected using transport encryption. ### Data protection Autopilot stores dealership operational information, customer records, reporting information, communications, and application configuration on behalf of authorised customers. Multiple layers protect access to this information, including authenticated user accounts, organisation membership, role-based permissions, database security policies, and application-level permission checks. Where practical, access decisions are enforced at multiple layers rather than relying solely on the application interface. ### Organisation and dealership isolation Autopilot is designed as a shared platform serving multiple independent organisations. Customer information is logically separated between organisations and dealerships so users can access only the organisations they have been authorised to access. Database-level security policies and application permissions work together to support customer information isolation between organisations. ### Access controls Protected application routes, APIs, and server-side workflows evaluate access using authentication, organisation or dealership membership, role permissions, field permissions, and database security controls. Some authorisation is implemented route-by-route or action-by-action rather than through a single global authorisation layer. Depending on a user's role, permissions may determine: - which dealerships they can access; - which modules and features they can use; - which records they can view or modify; - which fields are visible; - whether they can export information; and - whether administrative functions are available. This layered permission model limits users to information and functionality appropriate for their responsibilities. ## Account security User accounts are the primary way authorised staff access Autopilot. Because compromised credentials are a common cause of unauthorised access across online services, account security is designed to provide multiple layers of protection rather than relying solely on passwords. Autopilot combines password requirements, modern authentication methods, session management, and optional additional security features to help reduce the risk of unauthorised account access. ### Password security Autopilot encourages the use of strong passwords and validates passwords against defined security requirements before they are accepted. Where the authentication platform supports it, Autopilot checks for commonly used or compromised passwords to reduce the likelihood that users select credentials that are widely known or easily guessed. While password strength is important, Autopilot does not rely on passwords alone as the sole method of protecting customer information. ### Multi-factor authentication Autopilot supports multi-factor authentication using authenticator applications. When enabled, users are required to complete an additional verification step after entering their password before access to protected areas of the application is granted. This provides an additional layer of protection if a password is compromised through phishing, credential reuse, or other forms of account compromise. ### Passkeys Autopilot supports passkeys as an alternative to traditional passwords. Passkeys use modern authentication standards designed to reduce the risk of phishing attacks and eliminate the need for users to remember complex passwords. On compatible devices and browsers, passkeys can provide a simpler and more secure sign-in experience. ### Session management Successful authentication creates a user session that allows authorised users to access the platform without repeatedly entering their credentials. Autopilot provides visibility into active sessions and allows users to revoke sessions from other devices. Session management helps reduce risk if a device is lost or shared, or if an account is suspected to have been accessed by an unauthorised person. ### Account recovery Autopilot provides account recovery processes through its authentication platform. Recovery workflows are designed to verify user ownership of an account before access is restored. ### Human factors Technology alone cannot eliminate every security risk. Unauthorised access often results from credential compromise, password reuse, phishing, or social engineering rather than attacks against the underlying infrastructure. Autopilot helps reduce this risk through strong password requirements, multi-factor authentication support, passkeys, session management, and the ability for users to review and revoke active sessions. Customers are encouraged to enable additional account security features and educate staff on good security practices. ## Application security and data access Protecting customer information extends beyond user authentication. Once a user has signed in, Autopilot applies multiple layers of authorisation and application security controls to help ensure users can only access the information and functionality appropriate for their role. Access decisions are enforced across application workflows, database policies, and trusted server-side services to help reduce the risk of unauthorised access. ### Role-based access control Every user account is assigned permissions that determine the actions they are authorised to perform within Autopilot. These permissions can control access to application modules, administrative functions, reports, exports, and operational workflows. This allows dealerships to give staff access appropriate to their responsibilities without granting unnecessary privileges. Restricting access according to user roles helps reduce the likelihood of accidental data exposure and limits the impact of compromised accounts. ### Field-level permissions Some fields require greater protection than others. In addition to controlling access to modules or records, Autopilot supports field-level permissions that allow individual fields to be shown, hidden, or restricted based on a user's permissions. This gives dealerships greater flexibility when managing access to commercially sensitive or confidential information. ### Database security Autopilot applies security controls within the database itself using Row Level Security. Rather than relying solely on the application interface, database policies provide an additional access-control layer before information is returned through supported access paths. Row Level Security applies to public application tables and client-side Supabase access. Some trusted backend operations use service-role credentials that bypass Row Level Security, so those operations rely on server-side authentication, membership, scope, and permission checks. This layer helps prevent users from accessing records outside the organisations, dealerships, or information they have been granted permission to view. ### Server-side security Certain operations require elevated privileges that should not be available to browser clients. Where privileged access is required, these operations are performed by trusted server-side services using protected credentials that are not exposed to end users or client applications. Because some server-side operations may use elevated credentials, those operations must enforce the relevant authentication, membership, scope, and permission checks in server-side code. This reduces the risk of sensitive credentials being disclosed while keeping privileged operations controlled. ### Export controls The ability to export information is controlled through the same permission framework used throughout the application. Users can export only information they are authorised to access through export workflows, and protected fields remain subject to the same permission checks applied elsewhere within the platform. This reduces the risk of sensitive information being disclosed through reporting or export functionality. Once information has been exported from Autopilot, customers are responsible for handling it appropriately. ### AI and Companion access Autopilot includes AI-powered features that assist users with specific tasks within the platform. AI features are designed to use authenticated, dealership-scoped, and permission-aware tools when retrieving application data. These controls depend on the relevant tool-level permission checks and prompt or tool design. AI prompts, responses, transcripts, feedback, and related context may be stored by Autopilot where reasonably needed to provide, support, secure, monitor, or troubleshoot the relevant feature, unless another specifically disclosed basis applies. That content may be processed by AI subprocessors as described in the [Subprocessors](/legal/subprocessors) documentation. Autopilot does not use customer information submitted through Autopilot as general product-training data or to train public AI models. Customers retain control over who can access AI-assisted functionality through the platform's permission system. ### Secure integrations Autopilot integrates with third-party service providers to provide functionality such as authentication, payments, email delivery, and AI capabilities. For integrations that receive data from external systems, authentication mechanisms such as signed requests, secrets, or other verification methods are used when available to help ensure requests originate from trusted sources. Integration credentials are managed server-side and are not exposed to browser clients. ## Privacy and data handling Autopilot is designed to support dealerships in managing customer and operational information responsibly. Security focuses on protecting information from unauthorised access. Privacy also considers how personal information is collected, used, stored, and disclosed. Autopilot includes safeguards designed to help customers manage personal information responsibly and support privacy obligations that may apply under the New Zealand Privacy Act. ### Collection and use of information Autopilot collects and processes information reasonably required to provide the services requested by its customers. This generally includes dealership operational information, customer records, communications, reporting information, and application configuration necessary to operate the platform. Autopilot does not sell customer information or use it for unrelated advertising purposes. Further information about the categories of information processed by Autopilot is available in the [Privacy Policy](/legal/privacy). ### Third-party providers and Subprocessors Autopilot uses selected third-party service providers to deliver core platform functionality, including hosting, authentication, email delivery, payment processing, and AI-powered features. Where these providers process customer information on Autopilot's behalf, they are identified as Subprocessors and are listed in the [Subprocessors](/legal/subprocessors) page, which is the source of truth for current provider names, purposes, and related provider information. These providers support the services required by the platform. ### Customer information access Through normal platform use, customer information stored within Autopilot is accessible to authorised users acting within the permissions assigned to their account. Autopilot personnel access is limited to circumstances where it is reasonably necessary to investigate a support request, resolve a technical issue, maintain the platform, or meet legal or operational obligations. ### Supporting privacy obligations Autopilot provides technical controls designed to help customers manage personal information responsibly, including authenticated user accounts, permission management, access controls, data storage within managed infrastructure, and selected audit capabilities where available. Autopilot provides controls to protect information within the platform. Each customer remains responsible for ensuring that personal information is collected, entered, and used in accordance with its own legal, regulatory, and organisational obligations. ## Security monitoring and incident response Autopilot is designed with multiple layers of security, but incident response planning remains necessary. For this reason, Autopilot's security approach includes not only preventative controls, but also processes that support the investigation, containment, and response to potential security events. The objective is to reduce incident impact, protect customer information, and support customers with relevant legal and operational obligations. ### Monitoring and investigation Autopilot records operational logs and selected audit events that may be used to investigate suspected security issues, unexpected behaviour, or unauthorised access. When a potential security issue is identified, available logs, application telemetry, and operational information may be reviewed to understand the nature and scope of the issue. Audit and operational logging is not comprehensive across every feature or workflow, and coverage may vary depending on the activity involved. ### Containment If an account or security incident is suspected, appropriate measures may be taken to reduce the risk of further unauthorised access. Depending on the nature of the incident, this may include revoking active sessions, requiring password resets, temporarily restricting access, or implementing additional safeguards while the issue is investigated. The specific response will depend on the circumstances of the incident. ### Communication If a confirmed security incident affects customer information, Autopilot will work with affected customers to provide timely information about the nature of the incident, the actions being taken, and any recommended next steps. Where required by applicable law, Autopilot will support customers with relevant notification obligations. ### Learning from incidents Security incidents, vulnerabilities, and customer feedback are used as opportunities to improve the platform. Security controls, operational procedures, and platform features may be updated to reduce the likelihood of similar issues occurring in the future. ## Shared security responsibilities Protecting customer information is a shared responsibility between Autopilot and the organisations that use the platform. Autopilot is responsible for securing the Autopilot application, configuring and operating its managed cloud services appropriately, protecting privileged credentials, and maintaining the platform's technical controls. Underlying cloud infrastructure controls are provided by Autopilot's third-party service providers. Customers remain responsible for managing access to their own accounts, assigning appropriate permissions, and using the platform in accordance with their own security and privacy obligations. This shared approach helps ensure both the platform and its users contribute to maintaining a secure operating environment. ### Autopilot responsibilities Autopilot is responsible for the security of the application and the services it provides. This includes: - securing the Autopilot application; - configuring and operating managed cloud services appropriately; - protecting customer information using layered security controls; - managing authentication and access control systems; - applying security updates and platform improvements; - protecting privileged credentials and server-side services; - investigating reported security issues and responding appropriately to confirmed incidents; and - maintaining transparency regarding third-party service providers, Subprocessors, and platform security practices. ### Customer responsibilities Customers play an important role in protecting their own information and user accounts. This includes: - assigning appropriate permissions to staff members; - removing or disabling access for users who no longer require it; - encouraging the use of strong passwords and enabling multi-factor authentication; - protecting account credentials and authentication devices; - verifying exported information is handled appropriately once it leaves the platform; and - ensuring information entered into Autopilot is collected and managed in accordance with the organisation's own legal and regulatory obligations. ### Working together Autopilot provides technical safeguards to help protect customer information while giving organisations flexibility to manage their own users, permissions, and operational processes. Strong security outcomes are achieved when secure platform design is combined with good organisational security practices, including appropriate staff training, account management, and access reviews. ## Continuous improvement and transparency Security is not a one-time implementation. Threats, technologies, and industry practices continue to evolve, so maintaining a secure platform requires ongoing review and improvement. Autopilot reviews security controls as new platform capabilities are introduced and as the application evolves. Improvements may be driven by changes in technology, customer feedback, security research, operational experience, or evolving regulatory expectations. Improvements may include strengthening authentication mechanisms, expanding permission controls, improving monitoring and operational processes, enhancing audit capabilities, or adopting additional security features that improve the protection of customer information. Security enhancements are evaluated alongside usability to ensure the platform remains practical for day-to-day dealership operations. As Autopilot evolves, this Security & Trust page and related documentation may be updated to reflect significant changes to the platform's security controls and practices. Customers can review the latest version of this page alongside the [Privacy Policy](/legal/privacy), [Subprocessors](/legal/subprocessors), and [Terms of Service](/legal/terms) to understand how customer information is protected. ## Technical reference The main sections of this page describe Autopilot's security controls in plain English. This reference provides additional context on the technologies and security concepts mentioned above. ### Provider encryption at rest Encryption at rest refers to controls used to help protect information stored within database, storage, and infrastructure systems. **Autopilot:** Stores customer information in managed database and storage infrastructure. Autopilot does not currently claim separate application-level field encryption for customer or deal records. Autopilot does not make specific statements about provider-level encryption at rest, encryption standards, backup features, point-in-time recovery, redundancy, or disaster-recovery arrangements unless those controls have been verified against provider documentation or production configuration. **Why it matters:** Encryption at rest can help protect stored information if underlying storage media or infrastructure were accessed without authorisation. ### TLS encryption Transport Layer Security, or TLS, encrypts information transmitted between a user's device and an online service. **Autopilot:** Uses TLS for connections between users and Autopilot. **Why it matters:** TLS helps protect authentication credentials, customer information, and other sensitive data from interception while travelling across the internet. ### Authentication Authentication verifies a user's identity before access to protected information is granted. **Autopilot:** Uses managed authentication to establish authenticated user sessions. **Why it matters:** Authentication helps ensure only authorised users can access dealership information and platform functionality. ### Multi-factor authentication Multi-factor authentication requires users to provide an additional verification factor after entering their password. **Autopilot:** Supports authenticator application-based MFA for customers who choose to enable it. **Why it matters:** MFA can reduce the likelihood of unauthorised account access if a password is compromised. ### Passkeys Passkeys are a modern authentication method that can replace traditional passwords using cryptographic credentials stored on trusted devices. **Autopilot:** Supports passkeys on compatible devices and browsers. **Why it matters:** Passkeys can improve both security and usability and help reduce phishing risk. ### Secure sessions After successful authentication, a session allows users to continue using the platform without repeatedly signing in. **Autopilot:** Manages authenticated sessions and allows users to view and revoke sessions. **Why it matters:** Session management can help reduce the impact of lost devices or suspected account compromise. ### Row Level Security Row Level Security is a database feature that restricts which records individual users are permitted to access. **Autopilot:** Applies database-level security policies to public application tables and client-side Supabase access. Some trusted backend operations use service-role credentials that bypass Row Level Security and therefore rely on server-side authentication, membership, scope, and permission checks. **Why it matters:** Row Level Security provides an additional layer of protection beyond the application interface itself and helps prevent users from accessing information outside their authorised scope through supported database access paths. ### Role-based access control Role-Based Access Control assigns permissions according to a user's responsibilities within an organisation. **Autopilot:** Uses permissions to determine which modules, records, administrative functions, and features individual users may access. **Why it matters:** Restricting access according to job function reduces unnecessary exposure to sensitive information. ### Field-level permissions Field-level permissions allow access to individual pieces of information within a record to be controlled independently. **Autopilot:** Can hide or restrict sensitive fields based on a user's assigned permissions in views, workflows, and exports. **Why it matters:** Field-level permissions provide greater flexibility when protecting commercially sensitive or confidential information. ### Server-side operations Certain operations require elevated privileges that should not be available to browser clients. **Autopilot:** Performs privileged operations on trusted server-side services using protected credentials. Where elevated credentials are used, the relevant server-side code is responsible for enforcing authentication, membership, scope, and permission checks. **Why it matters:** Server-side operations help prevent sensitive credentials from being exposed to end users while keeping privileged operations controlled. ### Service-role credentials Service-role credentials provide elevated access for trusted backend services performing privileged operations. **Autopilot:** Stores these credentials server-side and does not expose them to browsers or client applications. Because service-role credentials can bypass database Row Level Security, server-side operations using them must enforce their own scope and permission checks. **Why it matters:** Keeping privileged credentials on the server reduces the risk of exposing sensitive operations to unauthorised users or client-side code. ### Signed webhooks Webhooks allow trusted external services to send information to an application. **Autopilot:** Verifies webhook requests using signatures, shared secrets, or similar authentication mechanisms where configured. **Why it matters:** Verification helps ensure requests originate from trusted systems and have not been modified during transmission. ### Server-side validation Server-side validation verifies requests after they reach trusted backend systems rather than relying solely on checks performed in a user's browser. **Autopilot:** Validates important security decisions and permission checks on the server before protected operations are completed. **Why it matters:** Server-side validation helps prevent client-side manipulation from bypassing security controls. ### Principle of least privilege The Principle of Least Privilege means users should receive only the minimum level of access required to perform their role. **Autopilot:** Designs permissions to limit access to the features and information appropriate for each user. **Why it matters:** Reducing unnecessary access limits the impact of accidental mistakes and compromised accounts.