dcouple.
Research Ethics & Data Handling
dcouple. Associate Data Handling Protocol
Objective
To ensure that "Field Intel" and source data remain decoupled from the identities of researchers and participants. This protocol transforms passive security into an active Sovereign Defense System, protecting both associates and the integrity of the oversight mission.
1. The Anonymization Hierarchy
Associates must apply the "Motivated Intruder Test" before any submission. This means assessing if a well-resourced actor could "single out" a source by combining your report with other public data.
→Generalization
Replace exact values with ranges to prevent precise identification.
✗ "Company X's revenue: €42,847,392"
✓ "Revenue between €40M-€50M"
→Perturbation
Add "statistical noise" to data points to maintain the pattern without revealing the exact, identifiable figure. Useful for time-series data and trend analysis.
→Pseudonymization
Use alphanumeric codes instead of names.
2. Secure Intake & Storage
Need-to-Know Access
Data is stored using Row-Level Security (RLS). Associates only have permissions to view or modify data relevant to their specific "Decoupling" sector (Capital Lab, Logistics Autonomy, Sovereign Tech, etc.).
Zero-Trace Submission
Never submit intel over unsecured channels like standard email.
✓ Use: Submit Intelligence portal (strips metadata automatically)
✗ Avoid: Standard email, public messaging platforms
The portal automatically removes: location data, device ID, browser fingerprint, IP geolocation.
Encrypted "At-Rest" Storage
All raw field notes must be stored on encrypted volumes. If an associate's device is seized or lost, the data must remain unreadable.
3. Operational Security (OPSEC)
Conflict of Interest Disclosure
Associates must disclose any financial or institutional ties to "Big Actors" before engaging in specific oversight audits. This includes:
- Employment or contractor relationships
- Equity holdings or investment positions
- Advisory board memberships
- Research grants or sponsored partnerships
Clear Desk/Remote Policy
Do not process sensitive hub data in public spaces or leave physical folders unattended.
✗ Prohibited: Cafes, coworking spaces, airport lounges
✓ Permitted: Secured home office, private office space, encrypted VPN connection
Incident Reporting
Critical Requirement: If you suspect a breach or a "motivated intruder" attempt, you must notify the Security Desk within 2 hours.
Security Desk: privacy@dcouple.com
Examples of incidents: suspicious login attempts, unexpected data access requests, phishing attempts targeting associates, social engineering contact from monitored entities.
Why This Protocol Exists
Liability Protection
If a "Big Actor" claims misinformation, this Protocol proves rigorous, data-centric verification processes.
Trust for Growth Projects
Regional alternatives will only share insider data if associates follow strict non-disclosure and anonymization rules.
Scaling Your Workforce
Acts as a manual so you don't explain security to every new associate personally, saving time for your job.
Associate Compliance Certification
By submitting Field Intel to the dcouple. hub, associates certify that:
- They have applied the Motivated Intruder Test to all submitted data
- All identifiable information has been properly anonymized
- They have disclosed any conflicts of interest
- They understand the 2-hour incident reporting requirement
- They accept responsibility for OPSEC compliance in their work environment
Questions or Concerns?
For questions about this protocol or to report security concerns:
Security Desk: privacy@dcouple.com
Data Protection Officer: dpo@dcouple.com