Subprocessors and service providers
Last updated: .
This page describes external services involved in processing personal data when you use the BusMaps website, accounts, API, MCP server or contact our team. It supplements our Privacy Policy and Terms and Conditions.
A provider is a processor when it handles personal data on our behalf, and a subprocessor where BusMaps itself acts as a processor for a customer. Some services also process data for their own purposes. The distinctions below describe the relevant services; listing a provider does not classify all of its activities as subprocessing.
Hosting and operational services
These services support our infrastructure and operations. Data is transmitted when the relevant feature runs, as described in each row.
| Provider/service | Purpose | Data processed | Processing locations |
|---|---|---|---|
| OVHcloud hosting | Host BusMaps application and routing services, the MCP service, geocoding and our own Umami analytics. Infrastructure processing on our behalf during service use. | Requests and responses, MCP account identifiers and encrypted connection authorization state, IP addresses, technical logs, search text, coordinates and analytics events handled by those services. | Deployment countries have not yet been verified. See the privacy policy and data processing documents. |
| Akamai Cloud / Linode hosting | Host our application database and website test environment. Infrastructure processing on our behalf when records are stored or accessed. | Account and contact information, password hashes, access credentials, project requests, subscription records and technical logs held in those systems. | Deployment countries have not yet been verified. See the privacy statement and data protection addendum. |
| Cloudflare CDN, security and R2 storage | Deliver and protect traffic passing through Cloudflare; store exported web/API logs and configured analytics backups. Processing of customer content on our behalf, with separate processing of service information under Cloudflare's policy. | IP addresses, request headers and content, URLs, browser and connection information; log records and analytics data in stored backups. | Global network. The locations of our R2 buckets have not been verified; no EU-only storage commitment is made here. Privacy policy, data processing addendum, R2 locations. |
| Google Workspace / Gmail | Send account and subscription messages and handle email correspondence. Mail content is processed to provide the email service when a message is sent or received. | Sender and recipient addresses, names, message content and attachments, including account confirmation or password-reset links where applicable. | Google's terms allow processing where Google or its subprocessors have facilities. A BusMaps-specific data-region restriction has not been verified. Data processing addendum, privacy policy. |
| OpenRouter and its routed model provider | Generate a project-request summary when an administrator requests it and no saved summary exists. This is separate from the MCP service. | Selected project requirements, including business activity, use case, coverage and free-text requirements. Dedicated contact fields, credentials and internal review notes are excluded; personal data entered in free-text requirements can still be transmitted. | The integration uses OpenRouter's global endpoint without a fixed inference provider. The actual downstream provider, processing countries and account-level restrictions have not been verified. Privacy policy, provider data handling. |
Services with separate or mixed processing roles
The following recipients provide payments, security, identity, advertising or public map services. Their own policies also apply; they are not described here as acting exclusively on BusMaps instructions.
| Provider/service | Purpose | Data processed | Processing locations |
|---|---|---|---|
| Stripe payments and billing | Process payment and billing interactions when you use Stripe-backed billing. Stripe acts as a processor for some activities and as an independent controller for others, including its own compliance and fraud-prevention activities. | Email, name, BusMaps account identifier, subscription and transaction details; payment details and device/network information collected directly by Stripe's payment interfaces. | International processing, including the United States and India, as described by Stripe. Privacy policy, data processing agreement. |
| Cloudflare Turnstile | Check protected forms and authentication flows for bots. Cloudflare processes signals for site protection and acts as a controller when improving its bot detection. | IP address, browser/device signals, interaction and challenge results; the challenge token is verified by BusMaps. | Cloudflare's international infrastructure; no BusMaps-specific region restriction has been verified. Turnstile privacy notice, privacy policy. |
| Google Sign-In | Authenticate you when you choose Google Sign-In. Google operates the identity service under its own policies. | Authentication requests and network/device information. Google returns your identifier, email and available profile information to BusMaps. | Google operates servers worldwide. Privacy policy. |
| Google AdSense | Serve advertising on pages where ads are enabled. Google and its advertising partners process data under the applicable advertising policies and settings. | IP address, browser/device and page information, advertising interactions, cookies or similar identifiers where used. | International processing on Google's infrastructure and that of its advertising partners. Partner-site data use, privacy policy. |
| Google map imagery | Load map or satellite tiles when a Google map layer is selected, including a previously saved selection. | IP address, browser/request information and tile coordinates identifying the area displayed. | Google operates servers worldwide. Privacy policy. |
| OpenStreetMap Foundation public services | Provide public Nominatim search/reverse-geocoding fallback if our primary geocoder fails, and map tiles when an OpenStreetMap layer is selected. These are external public services. | Search text or coordinates for geocoding; tile coordinates for maps; IP address, browser and request information sent directly by your browser. | OSMF describes non-tile personal data storage in the United Kingdom and Netherlands, with EU backups. Tile requests use a global cache network. Privacy policy. |
| OpenRailwayMap | Provide railway map tiles when that layer is selected. The operator handles requests under its own policy. | IP address, requested tile coordinates, access time, browser information and referrer information sent by the browser. | The linked policy does not establish the processing countries for our tile requests. Operator and privacy policy. |
Systems operated by BusMaps
We operate Umami for usage and error analytics, EspoCRM for customer and request management, and Listmonk for mailing lists. These software projects are not external processors merely because we use their software. Hosting, email delivery and storage providers are the relevant external services.
Our website sends named interaction and error events to our own analytics endpoint. Events can include the page path, referrer, language, screen size, browser information and feature-specific properties such as search text or coordinates. The collector receives the connection's IP address. Automatic pageview collection is currently disabled. We do not currently use Google Analytics for this collection.
MCP and AI clients
When you connect an AI client of your choice to our MCP server, that client sends tool arguments to BusMaps, such as place searches, coordinates or transit identifiers, and receives the results. You sign in to BusMaps with email and password or Google and explicitly allow the connection. The MCP service uses your current API account access server-side; requests share the coverage and limits of your REST access. The client can read your display name, API plan, allowed coverage and data sources, but does not receive your password or API key.
The AI client provider processes your conversation and tool results under your relationship with that provider. Connecting it does not by itself make it a BusMaps subprocessor. BusMaps receives the tool requests and connection information, not an automatic copy of your entire conversation. The MCP service does not itself send these requests to OpenRouter or another AI inference provider. It keeps encrypted authorization state for the connection; expiry and revocation are described in our Privacy Policy.
Verification limits
This is not yet a complete contractual subprocessor register. The hosting location and backup arrangements for our CRM and mailing-list systems, the full set of backup destinations, deployment countries, R2 bucket locations and OpenRouter's downstream inference provider still require confirmation. A provider's registered address is not treated as a processing location.
Links above describe providers' published terms. They do not establish that BusMaps has signed a particular DPA or SCC, enabled a regional restriction, or obtained a certification.
Updates and contact
We update this page as our services change and additional processing details are verified. The date above identifies the latest update.
For questions about these services or your data, use our contact form or email alex@busmaps.com.