Useful data needs
clear limits.
BGraph treats privacy, source rights, security, acceptable use, methodology, and editorial review as product requirements. The exact controls depend on the dataset, jurisdiction, delivery fields, and intended use.
About BGraph
What BGraph is building and which claims it does not make.
Read about BGraph ↗02Methodology
How products and public research move from a question to documented evidence.
Review methodology ↗03Editorial policy
Source selection, calculations, automation disclosure, and corrections.
Read policy ↗04Data principles
Regional baselines and public product commitments.
Read principles ↗05Website privacy
How inquiry and website information is handled.
Read notice ↗06Website terms
Rules for website access, public research, synthetic samples, and inquiries.
Read terms ↗07Security overview
Current website controls, reporting process, and assurance boundaries.
Review security ↗08Service providers
Confirmed external services supporting BGraph business correspondence.
Review providers ↗09Synthetic samples
Inspect fields without implying real coverage or scale.
Open samples ↗Six controls before delivery
This framework is a product standard, not a claim that every possible dataset is lawful in every market.
Source and rights review
A dataset should not be offered until its source rights, permitted uses, geography, and contractual limits are understood.
Purpose and field minimization
Fields should support the buyer's defined question. Unnecessary identifiers and sensitive attributes should be removed or excluded.
Aggregation and suppression
Group-level outputs, minimum cohort rules, and suppression may be used according to the risk and market.
Jurisdiction mapping
Consent, opt-out, data broker, retention, individual rights, and transfer requirements are assessed for the relevant countries.
Buyer restrictions
Contracts should prohibit re-identification, individual targeting, unlawful surveillance, and unsupported sensitive uses.
Retention and security
Delivery, access, retention, deletion, and incident terms should match the risk of the approved dataset.
Uses BGraph should not support
- Re-identifying or attempting to identify individuals
- Targeting a person based on sensitive health, political, religious, financial, or sexual information
- Employment, credit, insurance, housing, or similar high-impact decisions without a separate lawful assessment
- Surveillance, stalking, intimidation, discrimination, or unlawful profiling
- Combining fields to defeat aggregation or privacy controls
- Using data outside the documented purpose, geography, or retention period
Ask about fields,
rights, and controls.
Tell us the intended use and market. We will use it to define what can be offered and what should be excluded.
Start a data review ↗