Data partnersDocumented sources, durable relationships

Turn permitted signals
into useful data.

BGraph works with organizations that have a clear user relationship, demonstrable data rights, stable digital signals, and the ability to support a documented privacy and quality review.

Program principle

A useful partnership starts with provenance and permission. Volume matters only after the source, rights, user controls, signal quality, and permitted applications can be explained.

Potential partners

Who should start a conversation.

01

App and extension teams

Browser extensions, mobile apps, and desktop products with a clear user relationship and documented permission to process relevant signals.

02

Panel and research operators

Panels and research programs with transparent recruitment, consent records, participant controls, and a defined measurement universe.

03

Data and infrastructure platforms

Platforms that can license permitted event, category, commerce, search, referral, or journey signals with traceable provenance.

04

First-party data owners

Organizations exploring an approved, privacy-secured use of their own digital interaction data beyond internal reporting.

Partner review

Five checks before integration.

  1. 01

    Source and rights

    Who collected the data, what notices and permissions apply, which parties have licensing rights, and which uses are prohibited.

  2. 02

    Signal and coverage

    Available fields, platforms, geographies, history, cadence, stability, missingness, duplication, and the population the data can represent.

  3. 03

    Privacy and risk

    Direct identifiers, sensitive categories, age restrictions, small groups, re-identification risk, transfers, retention, and user controls.

  4. 04

    Technical validation

    A limited sample, schema review, quality checks, secure transfer route, documentation, and a repeatable refresh process.

  5. 05

    Commercial scope

    Permitted products, buyer restrictions, support responsibilities, reporting, pricing basis, contract terms, and termination handling.

Not accepted

Direct identity and sensitive access

Do not send credentials, direct identifiers, precise location histories, private message content, private AI conversations, unlawfully collected signals, or data intended for re-identification or surveillance.

Read data principles ↗
Technical routes

Secure, documented delivery

Depending on the source and review, integration may use encrypted server-to-server transfer, controlled object storage, scheduled files, or an approved API. The minimum useful fields are preferred.

Read the methodology ↗
Commercial model

Terms based on verified utility

Commercial structure is scoped after validation. Relevant volume, geography, quality, cadence, permitted uses, exclusivity, support, and processing cost may affect the agreement.

Discuss a partnership ↗
Partner FAQ

Before you share a sample

Who can apply to become a BGraph data partner?

App and extension teams, panel operators, research providers, data platforms, infrastructure providers, and first-party data owners may apply. Acceptance depends on documented rights, user transparency, signal quality, geography, and intended use.

Does BGraph accept private AI conversations or raw prompts?

Private conversations and account-linked prompt histories are not part of the standard partner scope. A query-derived signal requires its own source-rights, privacy, sensitivity, and use assessment before any technical review.

Does pseudonymisation make a dataset anonymous?

No. Pseudonymisation can reduce risk, but it is not automatically equivalent to anonymisation. BGraph reviews the fields, joins, population, access, retention, and intended use together.

How are commercial terms determined?

There is no universal public rate. Terms depend on verified rights, relevant volume, geography, stability, granularity, quality, refresh cadence, technical cost, permitted products, and buyer demand.

What should be included in the first message?

Describe the product or source, user relationship, collection notice and consent path, available signal categories, approximate geography and scale, history, cadence, current format, and the rights you can grant.

Start with context

Describe the source.
Do not send live data yet.

Send a short overview of the product, collection path, rights, fields, geography, scale, history, and cadence. BGraph will identify the next review step.

Introduce your data source ↗