Customer data platform · Your cloud or ours

Customer data you can trust, from the first event to every destination.

Collect, govern, unify and activate first-party data with privacy built into the pipeline.

Bootstrap Data checks every event against your tracking plan, sensitive-data rules and customer consent before it reaches a warehouse, data lake or marketing tool. Run it in your own cloud account, or let us run it for you.

Illustrative policy model — deterministic browser demo, not live product telemetry.

Event type
Consent profile
OMIT
  • warehouse
  • analytics

Omitted fields: user_email

event:    checkout_started
consent:  Analytics only
─────────────────────────────
decision: OMIT
removed:  [user_email]
proposed: warehouse, analytics
blocked:  activation (pii_present)

eventcheckout_startedcart_value149.00currencyUSDuser_emailu@example.com

See how every verdict is defined

Trust foundations

Governance that runs in the pipeline, not in a quarterly audit

  • Enforced at intakeEach event is checked against its contract and privacy rules before it moves.
  • Consent fails closedA tool only receives a record when the consent it needs has been granted.
  • Your cloud or oursDeploy in your AWS, Google Cloud, Azure or Oracle Cloud account, or use our managed cloud.
  • Audited by defaultEvery configuration change is recorded with who made it and when.
The problem

Customer data moves faster than the rules meant to protect it.

In most stacks, data is copied into warehouses, analytics and ad platforms first. Governance happens later, by hand, if at all.

  • Broken or unplanned events reach dashboards and campaigns before anyone notices.
  • Personal data ends up in tools that were never meant to hold it.
  • Consent is collected in a banner, then ignored once data starts flowing.
  • A single deletion request becomes a manual hunt across every system.
  • Security teams push back on sending raw customer data to another vendor’s cloud.
The Bootstrap Data way

Decide what data may do before it moves.

Bootstrap Data puts your tracking plan, privacy rules and consent in the path of every event, then delivers only what passes.

  • Versioned data contracts define what each source is allowed to send.
  • Personal and sensitive fields are classified and removed or blocked automatically.
  • Consent categories decide which destinations may receive each record.
  • Deletion and suppression requests (early access) reach every connected store and tool from one place.
  • Run it inside your own cloud account, so event data and personal data stay there.
Platform

One platform for the whole customer data lifecycle.

Collect events, enforce your rules, build unified profiles (early access) and deliver to the tools your teams use, with the same governance at every step.

  • CollectAvailable

    Event collection

    One collection layer for web, mobile, game and server events.

    • Android, iOS, JavaScript, Unity and server-side sources
    • Segment-compatible calls: track, page, screen, identify, group, alias, batch
    • Per-source write keys and IP allowlists
  • GovernAvailable

    Contracts & privacy rules

    Your tracking plan and privacy policy, enforced on every event.

    • Versioned data contracts built from reusable event and property blueprints
    • Allow, block or omit unplanned events, unplanned properties, schema violations, PII and sensitive PII
    • Field classification by name, value or pattern
  • ShapeAvailable

    Filters & transformations

    Send each tool exactly the data it needs.

    • Drop or sample events; allow or block fields per destination
    • Custom JavaScript transformations in a sandbox, at the source or per destination (early access)
    • Choose what happens on error: dead-letter, drop or pass through
  • StoreAvailable

    Warehouses & data lakes

    Own a clean, governed copy of every event.

    • Snowflake, BigQuery and Databricks, with typed tables generated from your tracking plan
    • Amazon S3 and S3-compatible storage, Google Cloud Storage and Azure Blob Storage
    • JSON or Parquet, your choice of compression and retention
  • UnifyEarly access

    Identity resolution & profiles

    Join a customer’s activity into one profile, without storing raw identifiers.

    • Deterministic matching on user ID, anonymous ID, email and phone, by rules you set
    • Identifiers stored only as keyed hashes; limits and blocklists prevent bad merges
    • Declared profile traits resolved by rules such as latest value or source priority
  • ActivateAvailable

    Destinations

    Deliver governed events to the tools your teams already use.

    • Amplitude, Braze, Customer.io, Google, Iterable, Meta, Mixpanel and any webhook
    • Field mappings with triggers, so each tool gets the right shape
    • Automatic retries that respect vendor rate limits, plus a dead-letter queue
  • ObserveEarly access

    Source debugger

    See what each source sends and what the platform did with it.

    • Live stream of incoming events with personal data masked
    • Search and filter; compare what was received with what was forwarded
    • Unmasking is limited to privacy officers and every reveal is audited
  • ProtectEarly access

    Deletion & suppression requests

    Act on data subject requests across the whole platform.

    • Suppress, delete, or both, by user ID, anonymous ID, email or phone
    • Erasure across warehouses, lakes, profiles and destinations, with status tracking and manual sign-off where a tool has no deletion API
    • Record the regulation behind each request: GDPR, CCPA, CPRA, LGPD or India’s DPDP Act
  • AssistAvailable

    AI assistant access (MCP)

    Let AI assistants work with your tracking plan through the Model Context Protocol.

    • Browse contracts, sources and governance rules
    • Validate a sample event against its contract before you ship it
    • Read-only by default; changes need explicit write permission
  • AutomateAvailable

    Configuration as code

    Manage the platform from Git and CI, not just the UI.

    • Command-line tool to export and apply configuration declaratively, with dry runs
    • Validate events against contracts in CI
    • Typed tracking clients for TypeScript, Java, Kotlin, Swift and Python
Generated clientsGenerated from that contract
  • TypeScript
  • Java
  • Kotlin
  • Swift
  • Python
Bootstrap ContractGoverned Schema · One Source of Truth
Source typesCollected into one contract
  • Android
  • iOS
  • JavaScript
  • Unity
  • Direct API

Three decisions. Applied to every event.

For each source you choose what happens to unplanned data, schema violations and personal data: allow it, block it, or omit the sensitive fields.

ALLOW

Pass and deliver

The event matches its contract and carries nothing your rules restrict, so it continues to storage and to every destination its consent allows.

Consent is still checked per destination, so “allowed” never means “sent everywhere”.

decision: ALLOW
destinations: [warehouse, analytics, activation]

BLOCK

Stop at the door

Unplanned events, schema violations or sensitive data your policy forbids stop at intake. Nothing reaches downstream tools.

Use the source debugger (early access) to see why an event was blocked and fix it at the source.

decision: BLOCK
reason: unplanned_event

OMIT

Strip, then deliver

Personal or sensitive fields are removed and the rest of the event continues, so analytics keeps working without the risk.

Fields are matched by name, value or pattern, so sensitive data is caught wherever it appears.

decision: OMIT
removed: [email, date_of_birth]
destinations: [warehouse, analytics]

These verdicts aren’t static docs — try them live in the policy evaluator above.

Walk-through

One event, through every check.

Scroll to follow a checkout_started event as it is validated, classified, consent-checked and delivered. One personal field is removed on the way.

checkout_started
  • eventcheckout_started
  • cart_value149.00
  • currencyUSD
  • user_emailu@example.comOMITTED
  1. ContractValidated against a versioned contract
  2. PII / SPII policySensitive fields classified and removed
  3. ConsentChecked against granted categories
  4. DestinationsClean payload delivered downstream
OMIT
  • warehouse
  • analytics

Follow one event from collection to delivery.

Every event takes the same governed path: collected, checked against its contract, cleaned of what it shouldn’t carry, delivered where consent allows, and recorded.

CollectStep 1 of 5

Familiar calls, one collection layer.

Send events from web, mobile, games and servers using Segment-compatible calls, so existing instrumentation needs little rework.

Sources: Android, iOS, JavaScript, Unity, Direct API. Typed clients for TypeScript, Java, Kotlin, Swift and Python.

bd.track("checkout_started", {
  cart_value: 149.00,
  currency: "USD",
  user_id: "u_7732"
});
Integrations

Works with the stack you already run.

Connect your apps, your data platform and your marketing tools. Every connection goes through the same contracts, privacy rules and consent checks.

Collect from

Sources

  • Android
  • iOS
  • JavaScript
  • Unity
  • HTTP API
Load into

Warehouses

  • Snowflake
  • BigQuery
  • Databricks
Archive to

Data lakes

  • Amazon S3 & S3-compatible
  • Google Cloud Storage
  • Azure Blob Storage
Activate in

Destinations

  • Amplitude
  • Braze
  • Customer.io
  • Google
  • Iterable
  • Meta
  • Mixpanel
  • Webhook
Run on

Deploy & operate

  • Amazon EKS
  • Google GKE
  • Azure AKS
  • Oracle OKE
  • Helm
  • Argo CD
  • Flux
  • OpenID Connect SSOEarly access

Need a connector that isn’t listed? Webhooks cover most HTTP APIs today. Tell us what you need.

Reverse ETLIn development

Put warehouse insights to work, safely.

Your best audiences, scores and traits live in the warehouse. Reverse ETL is designed to sync them to the tools your teams use, with the same privacy and consent rules as your event data.

Planned sync modes
  • Add
  • Update
  • Upsert
  • Delete
  • Mirror
  • List add / remove

Reverse ETL is in development and not yet available. Planned capabilities may change before release.

  • Confirmed delivery

    Designed to count a record as synced only after the destination confirms it, so a cancelled or interrupted run resumes where it stopped.

  • Guard against mass changes

    Designed so unusually large changes or deletes wait for approval instead of reaching a destination.

  • Same privacy rules

    Designed to apply the same suppression and consent checks used for events before any synced record is sent.

  • Only what changed

    Designed to track changes on mapped columns only and skip runs when the source data hasn’t changed.

  • Preview before you sync

    Planned dry runs, primary-key checks and re-baselining let you test a sync before it touches production.

  • Runs on your schedule

    Planned triggers: intervals, cron with time zones, API calls, or after your dbt Cloud, Airflow, Dagster or GitHub Actions jobs finish.

How a governed sync is designed to work

Warehouse modelhigh_value_customers
  1. cus_1042Pro · high LTVSynced: Updated
  2. cus_2210Pro · high LTVSkipped: Suppressed
  3. cus_3381Team · mid LTVSkipped: No change
  4. cus_4517Pro · high LTVSynced: Added

From Snowflake, BigQuery, Databricks, Postgres

Governed sync
  • Consent
  • Suppression
  • Changed since last run
Your tools
  • Braze
  • Customer.io
  • Iterable
  • Webhook

2 delivered and confirmed, 2 skipped

Illustration of planned behaviour with sample records. Reverse ETL is in development.
Deployment

Your cloud or ours. Same platform.

Choose where Bootstrap Data runs based on your data residency, security and operating needs. Both run the same platform.

Bring your own cloud (BYOC)

Runs inside your cloud account. Customer data stays there.

  • Deploy to Kubernetes on AWS, Google Cloud, Azure or Oracle Cloud with versioned Helm charts
  • Event data, logs and personal data stay in your account; only aggregated usage counts are sent for billing
  • Use your own managed databases and identity provider, or run them in the cluster
  • Only the app and the event intake are exposed; internal traffic is denied by default
  • You choose when to upgrade; roll back if needed

Best for regulated industries, strict data residency, and teams that run Kubernetes.

Bootstrap Data Cloud

Fully managed by us. Start collecting fast.

  • We run, monitor and upgrade the platform for you
  • The same contracts, privacy rules, consent checks and connectors
  • Single sign-on and role-based access (early access)
  • Configuration exports as code, so you can move to BYOC later
  • Talk to us about hosting regions and data residency

Best for teams that want to go live quickly without operating infrastructure.

Not sure which fits?

Answer three questions for a starting recommendation.

Must customer data stay inside your own cloud account?
Do you have a team that operates Kubernetes in production?
Is going live quickly, without new infrastructure, the top priority?

Answer the questions to see a recommendation.

Security & trust

Built for the security review.

Least privilege, full audit history and a verifiable software supply chain are part of the product, not add-ons.

  • Early access

    Single sign-on and fine-grained roles

    Sign in with your OpenID Connect identity provider. Ten built-in roles, from viewer and analyst to privacy officer and auditor, assigned through groups. Access is denied unless granted.

  • Early access

    Sensitive actions locked down

    Stored connection secrets are never shown back, even to administrators. Unmasking personal data in the debugger is limited to privacy officers and an emergency break-glass role, and every reveal is logged.

  • Complete change history

    Every change to sources, contracts, policies and connections is recorded with who made it and when.

  • Credentials and identifiers protected

    Connection credentials are encrypted at rest, write-only and never returned by the API. With unified profiles (early access), identifiers are stored only as keyed hashes.

  • Minimal network exposure

    In BYOC, only the app and the event intake are reachable from outside. Internal traffic is denied by default, and metering is outbound only.

  • Verifiable releases

    Versioned releases for amd64 and arm64, each with a software bill of materials (SPDX) and signed build provenance attestations.

Privacy requests across the stack

Early access

Suppress or delete a person’s data across storage, profiles and destinations, and record the regulation behind each request.

Regulations you can record
  • GDPR
  • CCPA
  • CPRA
  • LGPD
  • DPDP Act

Bootstrap Data provides tools to help you act on privacy requests. Compliance with each regulation remains your responsibility.

Who it’s for

One governed model for every team that touches customer data.

Engineering, analytics, privacy and marketing work from the same contracts, rules and consent, so no one has to reconcile them later.

Data platform engineering

Replace one-off pipeline fixes with configuration you can review.

  • Define contracts once and reuse them across every source.
  • Manage configuration from Git and CI with the command-line tool.
  • Debug a source live without exposing personal data (early access).
  • Deploy in your own cloud with versioned Helm charts.

Analytics engineering

Clean, typed data in the warehouse from day one.

  • Get typed warehouse tables generated from the tracking plan.
  • Stop broken events before they reach your models.
  • Keep a raw or typed copy in your own data lake.
  • Resolve users across devices into one profile (early access).

Privacy, security & legal

Enforce privacy policy in the pipeline, not in a spreadsheet.

  • Block or remove personal data before it leaves intake.
  • Make sure tools only receive data their consent allows.
  • Handle deletion and suppression requests from one place (early access).
  • Review who changed what, and who unmasked sensitive data (early access).

Marketing & growth

Activate customer data you are allowed to use.

  • Send events to Braze, Customer.io, Iterable, Meta, Google and more.
  • Map fields to what each tool expects, in the UI.
  • Respect consent automatically in every campaign tool.
  • Coming next: sync warehouse audiences with Reverse ETL.
FAQ

Frequently asked questions.

What is Bootstrap Data?

Bootstrap Data is a customer data platform for first-party data. It collects events from your apps and servers, enforces your tracking plan, privacy rules and consent, builds unified profiles (early access), and delivers governed data to your warehouse, data lake and marketing tools.

What is the difference between BYOC and Bootstrap Data Cloud?

With BYOC (bring your own cloud), the platform runs on Kubernetes inside your own AWS, Google Cloud, Azure or Oracle Cloud account and your customer data stays there. With Bootstrap Data Cloud, we run and upgrade the platform for you. Both include the same features.

What data leaves my account when I use BYOC?

Only aggregated usage counts used for billing. They are signed and sent outbound only, over mutually authenticated TLS. Event payloads, logs and personal data stay in your account.

Can we keep our existing Segment-style tracking?

Yes. The collection API accepts Segment-compatible calls (track, page, screen, identify, group, alias and batch), so existing instrumentation needs little rework. Talk to us about your migration.

Does Bootstrap Data make us compliant with GDPR or CCPA?

No software can make you compliant on its own. Bootstrap Data gives you the controls: consent-gated delivery, blocking or removing personal data at intake, and deletion and suppression requests (early access) across connected systems with the regulation recorded. Your compliance program decides how to use them.

Is Reverse ETL available?

Not yet. Reverse ETL is in development. We are working with design partners on it now. Contact us if you would like to take part.

What do the “Early access” and “In development” labels mean?

Available features are part of a released version. Early access features are complete and are rolling out ahead of general availability. In development features are planned but not yet available, and their scope may change.

Can AI assistants work with Bootstrap Data?

Yes. A built-in Model Context Protocol (MCP) server lets AI assistants browse your contracts and governance rules and validate sample events. It is read-only by default.

How is Bootstrap Data priced?

Pricing is usage-based for both BYOC and Cloud. Contact us for a quote that fits your volume and deployment model.

See it with your own data.

Tell us about your stack, where your data has to live and what you want to activate. We will walk you through the platform on your use case, in BYOC or Cloud.

Or email us at contact@bootstrapdata.in.