BTG Bridge guide
A bridge for authorized digital activity
BTG Bridge is the proposed consumer-facing entry point to the data economy. Its purpose is to help an individual decide which permitted activity, if any, can be processed through a personal FarmNode. It is separate from BTG Exchange.
What an individual could contribute
Potential supported sources include web-search activity, permitted browser history, selected social-media activity, public posts, product comparisons and other deliberately connected sources. Coverage depends on operating-system permissions, provider APIs, account-export rules and contracts. No single app can universally inspect all other apps.
Intended user workflow
- Review supported source types and plain-language notices before connecting anything.
- Choose exactly which categories to contribute; exclude medical, banking, identity, credentials and other restricted categories by default.
- Review which purposes are allowed: private analysis, research participation or an expressly authorized commercial contribution.
- Approve each permission and see a record of what the Bridge collected or derived.
- Revoke future use where possible, export an activity report and submit deletion/access requests subject to applicable lawful retention.
- Separately approve any proposed market release. Connecting a platform must never automatically list personal activity for sale.
Important limitations
A conversation can contain another person's personal information. Recording and commercialization require an appropriate lawful basis for all affected parties; a participant's consent may not be sufficient by itself. Social-media or search exports may be restricted by the original platform's contract, even if downloaded by the account holder. Pseudonymized data can still identify someone when linked to other records.
No surveillance promise: This documentation does not claim that BTG Bridge can intercept private apps, record calls silently, bypass provider restrictions or guarantee earnings.
Individual rights
The intended design includes a readable consent receipt, purpose limitation, contribution history, access controls, withdrawal procedures, rights-dispute handling and transparent compensation agreements. Those rights are product requirements; deployed controls must be demonstrated before accepting live participant data.