USA/CANADA UK,EUROPE AND REST OF THE WORLD
Snowplow BDP Cloud provides behavioral data management. Companies use Snowplow BDP to create and manage behavioral data.
Behavioral data is generated in / collected from different digital touchpoints, typically including websites and mobile apps (referred to as “Sources”). Sources can include third party SaaS solutions that support webhooks (e.g. Zendesk, Mailgun).
Snowplow BDP Cloud processes and delivers this behavioral data to different destinations. From there, companies use that data to accomplish different use cases. Snowflake is currently the only destination supported within Snowplow BDP Cloud.
As part of Snowplow BDP Cloud we provide standard data models (e.g. web or mobile models) that transform the data in the data warehouse to make it easier to consume by downstream applications and systems (e.g. business intelligence).
Key features
Snowplow BDP Cloud is a SaaS product.
Open core
The core data processing elements of the Snowplow pipeline are predominantly open source and the code is available on GitHub under the Apache 2 license.
Key elements of the Snowplow BDP Cloud technology stack, including the UI, are proprietary to Snowplow and all rights are reserved.
Data residency
All data processed and collected with Snowplow BDP Cloud is undertaken within Snowplow’s own cloud account (AWS eu-central-1 or us-east-2 region, depending on customers preference). Data is stored in Snowplow’s cloud account for 7 days to provide resilience against potential failures.
The customer decides:
- What data is collected
- The destination that the data is finally stored (i.e. Snowflake)
- What the data is used for
It is the customer’s obligation (and not Snowplow’s) to maintain and administer the final storage destination that is set-up upon signing up for BDP Cloud (i.e. Snowflake). Each of the customer’s and Snowplow’s obligations with respect to data protection and privacy are set forth in the data privacy section of the BDP Cloud terms and conditions.
Event volumes
Snowplow BDP Cloud customers are charged in arrears for the volume of events collected in the billing period. The “volume of events” in a given time period is calculated as the number of records written to the good enriched stream in that time period (UTC).
BDP Cloud pipelines are limited to receive up to 60 requests per second (maximum rate limit). In the event that this rate limit is exceeded, the excess data over and above that limit will be lost for the period that it is exceeded for.
Updates
As our business evolves, we may change this Product Description including the maximum requests per second that a BDP Cloud pipeline can receive. Customers can review the most current version of the product description at any time by visiting this page.
List of subprocessors
We currently use the following entities as sub-processors of the data that passes through BDP Cloud. The below table describes the nature of the services provided by the sub-processor and their location.