We serve our website exclusively via HTTPS, and serve all our APIs over HTTPS by default. We offer two-factor authentication for logins to help you protect your account, and we let you create multiple customizable access tokens for granular control over access to your account resources.
Our infrastructure runs inside data centers designed and operated by Amazon Web Services (AWS). AWS data centers feature state of the art environmental security controls to safeguard against fires, power loss, and adverse weather conditions. Physical access to these facilities is highly restricted and they are monitored by professional security personnel. Our offices are equipped with access control, intrusion detection, and video surveillance systems.
Our systems run the latest stable versions of Ubuntu or Amazon Linux and our applications run on the latest stable version of Node.js. We monitor documented threats from public security research databases (such as the Common Vulnerabilities and Exposures catalog), and we run automated vulnerability scanners at regular intervals across our infrastrcure and before each deploy. Our developers receive training for secure software development, including Open Web Application Security Project guidelines. All major code changes are subject to a multi-point code review with specific attention paid to security.
Maps and location can be politically charged subjects. We maintain firewalls on our edge servers and origin load balancers to protect against bandwidth and protocol-based attacks, and we use intelligent web application firewalls and elastic scaling of our compute capacity to mitigate attacks at the application layer, including complex and evolving attacks.
From raster imagery from a drone to GPS traces from a fleet of vehicles, data uploaded by Enterprise users can be secured with private maps. New maps are private by default and existing maps can be made private with a single click. Access tokens provide a powerful way to control permissions: in our management interface, users can create, revoke, and monitor the usage of resources based on tokens.
Mapbox team access is controlled by a carefully managed and audited security policy. Employees must revalidate their credentials every hour using two-factor authentication. All team members sign non-disclosure agreements to protect your data. All employees receive tools and training for handling sensitive data (including credentials) and for avoiding social engineering and other non-technical attacks.
We log activity across our platform, from individual API requests to infrastructure configuration changes. Logs are aggregated for monitoring, analysis, and anomaly detection and archived in vaulted storage. We implement measures to detect and prevent log tampering or interruptions.
We process payments with Stripe, which has been audited by a Payment Card Industry Standard-certified auditor, and is certified to PCI Service Provider Level 1. This is the most stringent level of PCI DSS certification available. Payment information is transmitted directly to Stripe via HTTPS for secure storage and is never transmitted to or stored on Mapbox servers.
We conduct regular internal security audits and work with external auditors to review our hardware, software, and physical security configurations. We are SOC 2 Type 2 compliant. Download our SOC 3 report here. Our security vulnerability program rewards users and security researchers who find issues with our software and web services. If we discover a vulnerability, we follow a formal incident response framework to ensure rapid mitigation and transparent customer communication.