Active infrastructure providers
| Provider | Purpose | Data categories | Location/status |
|---|---|---|---|
| Cloudflare | Workers hosting, static assets, queues, workflows, object storage, database connection pooling, per-portal coordination, secrets, DNS, and email routing. | Portal-bound application traffic, sessions, queued job pointers, imported/exported configuration artifacts, logs, network and support-routing metadata. | Global edge; primary customer application/data configuration is U.S.-oriented. |
| Neon | Managed PostgreSQL 17/PostGIS database. | Portal, installation, member, program, exact ZIP, normalized managed-record snapshot, decision, exception, audit, job, and billing-entitlement records. | United States primary database region for early access. |
| Hostinger | Destination mailbox hosting for support messages forwarded through Cloudflare Email Routing. | Sender address, recipients, subject, message body, attachments, delivery metadata, and the support operator's replies. | Active for support correspondence. Processing location depends on the destination mailbox account and Hostinger's infrastructure. |
Customer-connected platform
| Provider | Relationship | Data |
|---|---|---|
| HubSpot | The customer's CRM and identity/OAuth provider. Customers authorize the connection under their own HubSpot agreement. | Portal/user/owner identity, supported CRM object and schema reads, app UI requests, and separately authorized object-specific owner writes. |
Map delivery
| Provider | Purpose | Data boundary and current status |
|---|---|---|
| OpenStreetMap Foundation | Raster basemap tiles from tile.openstreetmap.org when no production map style is configured. | Active as the current early-access fallback. The user's browser requests visible tiles directly, exposing ordinary browser/network metadata, referrer, and requested tile coordinates. TerritoryLogic does not intentionally send HubSpot managed-record fields or raw addresses. The community tile service is best-effort and is not the planned commercial map provider. |
| Amazon Web Services / Amazon Location Service | Planned production basemap style/tile delivery after a production style is configured. | Not claimed as active map delivery while the OpenStreetMap fallback above is in use. If enabled, the user's browser would disclose ordinary browser/network metadata and map viewport/tile requests. TerritoryLogic does not use Amazon geocoding in V1. |
Implemented but not enabled for production processing
| Provider | Planned purpose | Current status |
|---|---|---|
| Stripe | Paid Checkout, subscriptions, invoices, and customer billing portal. | Disabled. Public installs create Free; no production paid checkout is available. |
| Twilio SendGrid | Install, publish, conflict, plan-limit, and inactivity transactional messages. | Disabled for application-generated email. Inbound support mail is routed through Cloudflare Email Routing to the Hostinger-hosted destination mailbox listed above. |
| Sentry | Application error monitoring. | No production use is claimed by this page; configuration and privacy review remain pre-launch work. |
No geocoding provider
The current release does not send managed CRM record addresses to Google, Amazon, or another address-geocoding provider. Exact ZIP5 from each object's mapped single-line text or number property is authoritative. Only when that property is missing may normalized city/state evidence support an explicitly claimed whole-state territory; no ZIP is inferred from an address.
Questions or objections
Contact support@territorylogic.com. A binding commercial subprocessor-notice and objection procedure is not yet offered; customers requiring one should wait for the executable DPA.