Trust

Your data. Your call.

FieldTrip ships with two ways to run. A shared, multi-tenant core product, where your photography improves models that get better for everyone. And an Enterprise partnership, where your data stays in a single-tenant environment, models stay yours, and nothing leaves your perimeter. This page tells you the difference, in plain language. The binding details live in your Data Processing Agreement.

Two tiers. One comparison.

Core product

  • Multi-tenant, workspace-isolated
  • Social login and email/password
  • Shared pole detection models, kept current with every release
  • Your photography contributes to the next training run. That's how the model gets better — for you and every other engineering team on the platform. We don't sell it. We don't share it. We don't show your data to other customers. We use it to train shared models that ship to everyone, you included.

Enterprise partnership

  • Single-tenant environment at fieldtrip.{your-domain}.com
  • SCIM provisioning and SSO via WorkOS
  • Bespoke models trained on your photography alone
  • Your data never leaves your tenant. No contribution to shared models. No co-mingling with other customers. Hosted to security standards agreed up front. Built for engineering firms that need data sovereignty as a hard requirement.

Workspace isolation

Every Core-tier customer operates in a logical workspace. Other customers cannot access your photography, classifications, signoffs, or metadata — only users you authorize within your workspace can.

Workspaces are isolated by tenant ID at every layer:

Enterprise partners get the same isolation guarantees plus a dedicated single-tenant environment — separate hosting, separate models, separate data plane.

How we train models

Core tier

Your photography, classifications, and reviewer signoffs in the Core product contribute to FieldTrip's shared pole detection models. That's the mechanism by which the platform gets better with every release. You benefit from every other engineering team's photography. They benefit from yours.

Beyond training shared models, we do not:

  • Sell Customer Data.
  • Make raw photography available to other customers. Only the trained model behavior is shared — through inference, not data.
  • Use your data for anything outside providing and improving the Service.

Enterprise partnership

Enterprise Customer Data is not used to train FieldTrip's shared models. Period. Bespoke models trained for an Enterprise partner are available only within that partner's single-tenant environment. They're not co-mingled, not co-served, not co-anything. Your route is yours.

Authentication and access

Core tier

Social login (Google, Microsoft) and email/password, with role-based permissions per team. Workspace admins assign roles to control who can review, sign off, write back, and manage settings.

Enterprise partnership

SCIM provisioning and SSO via WorkOS — SAML, OIDC, and directory sync against your IdP. Granular RBAC. Audit log of every permission change.

Programmatic access (MCP, CLI, agents) uses workspace-scoped bearer tokens with the same scopes a user has — details on Build.

Infrastructure

FieldTrip runs on Google Cloud Platform with multi-region redundancy.

Your data rights

Whether you're on Core or Enterprise, you can:

Export

Pull your photography, classifications, and audit data via the Service or by written request.

Audit

Request a written summary of how your data has been processed.

Delete

Remove Customer Data from active Service. Trained shared models retain weights learned from past contributions; future training runs will not incorporate deleted data.

Subprocessors

The third-party services that touch Customer Data in the course of providing the Service.

SubprocessorPurposeRegion
Google Cloud PlatformCompute, storage, databases, logging, ML inference, Gemini models (Vertex AI)US (Core), customer-specified (Enterprise)
Google FirebaseWeb hosting, Android push notificationsUS
AppleiOS push notificationsUS
WorkOSAuthentication, SSO, SCIM, integration key storageUS
OsoAuthorization policy managementUS
MapboxMap rendering, geocoding, road lookupUS
SentryCrash and error reporting (no photography or location)US
PostHogProduct analytics (no photography)US
ResendTransactional email deliveryUS
SlackCustomer support channels, internal team alertsUS
CloudflareTurnstile bot prevention (marketing site)Global edge

The full, up-to-date subprocessor list is maintained in your Data Processing Agreement.

Security questions and incident reporting

Found a vulnerability, want a DPA, or need to flag a security concern?

Incidents that affect Customer Data are reported to affected customers promptly, generally within 72 hours of confirmation.

Need a DPA, security questionnaire response, or compliance documentation?

Reach out — we route Enterprise procurement requests directly to the team that handles them. We'll work with your security team on what they need.