Current subprocessors
| Company | What they do for us | Data they handle | Where |
|---|---|---|---|
| Google Cloud | Servers, database (Firestore), scheduled jobs and backups. | All account data: account and team details, locations, keywords, results, contacts, review requests and support messages. | United States |
| Firebase | Sign-in and app hosting (a Google service). | Email addresses and sign-in records. | United States |
| Google APIs (Maps Geocoding, Business Profile, Search Console, Analytics) | Place names for map areas; reading and, when you ask, updating your Business Profile; showing your Search Console and Analytics data. | Map coordinates; the Business Profile, Search Console and Analytics data of the accounts you connect. | United States |
| DataForSEO | Runs the Google and Google Maps searches, review lookups, AI visibility checks, citation checks and site audits behind your results. | Business name, address, website and the keywords and prompts you track. Not your account details. | European Union |
| Anthropic | Writes AI drafts: review replies, Business Profile posts, area briefs and To-do summaries. | The review, business details or results needed for the draft you ask for. | United States |
| Resend | Sends email: reports, alerts, review requests and support replies. | Recipient email addresses and the content of each email. | United States |
| Stripe | Payments, subscriptions and invoices. | Billing contact, payment details and subscription records. We never see your full card number. | United States |
| Cloudflare | Delivers our website and app, protects them from abuse, and routes our support email. | Network data such as IP addresses, and support emails passing through. | Global network |
Changes to this list
We’ll update this page at least 30 days before adding a new subprocessor.
Contact us
Questions? Email support@heatmymap.com.