Data Governance
Privacy and Data Use
How data is handled in the Atlas of Coordination, what constitutional boundaries govern its use, and why restraint is architecturally enforced.
The Problem
Data collection in organizational tools frequently enables surveillance, evaluation, and behavioral control—precisely what constitutional governance exists to prevent.
When diagnostic systems collect data, three problematic uses commonly occur:
Data enables surveillance
Collecting individual-level behavioral data creates infrastructure for monitoring people rather than understanding systems, converting diagnostic tools into surveillance platforms.
Data enables evaluation
Performance metrics, productivity tracking, and effectiveness measurements transform structural observation into individual assessment, enabling evaluation the system prohibits.
Data enables control
Behavioral data creates pressure toward optimization, compliance monitoring, and intervention triggering—collapsing observation into management control infrastructure.
These uses transform diagnostic systems into surveillance and control platforms regardless of stated privacy commitments.
Constitutional data governance prevents these uses through architectural constraints on what data can be collected, stored, and analyzed.
Core Principle
Foundational Commitment
The Atlas of Coordination is designed to help people understand coordination systems, not to observe, evaluate, or optimize individuals.
Data governance operates on data minimization by constitutional design:
Collect only what is necessary
Data is collected only where required for system understanding, constitutional boundary enforcement, and operational reliability. Behavioral, evaluative, or surveillance data is not collected even if technically possible.
Aggregate and de-identify
Data is aggregated at system level and de-identified before analysis. Individual-level data cannot be accessed or analyzed without explicit consent.
Prohibit evaluative uses
Data cannot be used for performance evaluation, behavioral scoring, compliance monitoring, or optimization targeting. These uses are constitutionally prohibited.
Maintain structural focus
Data collection focuses on coordination structures and system dynamics, not individual behaviors, personal characteristics, or team performance.
What Data Is Collected
Data collection is limited to structural observation and system reliability:
Anonymous diagnostic responses
Diagnostic completion events and pattern detection results, aggregated and de-identified. Individual responses are not tracked or analyzed without explicit account creation.
System interaction events
High-level events indicating boundary encounters (protected mode triggers, tier access gates, constitutional constraint activations) aggregated at system level.
Optional account identifiers
When users explicitly create accounts, authentication tokens and session identifiers for access control and data persistence. Account creation is optional for all Tier 1 capabilities.
Minimal technical data
Security logs, error diagnostics, and operational reliability data required for system stability and abuse prevention. This data is not analyzed for behavioral patterns.
All data collection is logged and subject to constitutional compliance review. New data collection requires explicit justification for structural necessity.
What Is Explicitly Not Collected
Constitutional boundaries prohibit collection of:
Behavioral profiles or user scoring
No creation of behavioral profiles, engagement scores, user rankings, or comparative assessments between individuals.
Productivity, performance, or effectiveness metrics
No measurement of time-to-completion, efficiency gains, task success rates, or performance outcomes at individual or team level.
Personal communications or content
No collection of messages, documents, conversations, or user-generated content beyond explicit diagnostic inputs.
Psychological, emotional, or biometric data
No collection of emotional state, psychological assessment, biometric identifiers, or health information.
Data for ranking, surveillance, or automated judgment
No collection of data that could enable automated evaluation, surveillance systems, compliance monitoring, or individual judgment without human oversight.
These exclusions are permanent and constitutionally protected. They cannot be modified under commercial pressure or feature requests.
Diagnostic Data
Diagnostic responses describe coordination structures, not people. Results are interpretive and non-evaluative.
Storage is user-controlled
Diagnostic results are stored locally in your browser by default. Server-side storage only occurs when you explicitly create an account and save diagnostics.
Interpretation boundaries
Diagnostic data is not used to infer individual capability, assess organizational health, or evaluate performance. It describes structural patterns without normative judgment.
No cross-organizational comparison
Diagnostic results are not used to rank organizations, create benchmarks, or enable comparative evaluation between users.
User deletion rights
Users can delete diagnostic data at any time through account settings. Deletion is immediate and permanent.
Observability and Analytics
Observability focuses on system understanding, not individual monitoring. See Analytics & Observability Transparency for comprehensive documentation.
System behavior under pressure
Observability tracks how coordination patterns behave under load, ambiguity, or structural pressure—not how individuals perform under those conditions.
Constitutional boundary encounters
Where users encounter observation-prescription boundaries, protected mode enforcement, or tier access gates—indicating demand for prohibited capabilities.
Pattern concentration zones
Where coordination pressure concentrates across diagnostic contexts, revealing structural forces independent of individual actions.
Observability is not used for monitoring individuals, enforcing behavior, evaluating outcomes, or triggering interventions.
Data Access and Retention
Restricted access
Access to stored data is limited to system maintenance, safety review, constitutional compliance verification, and canonical field research aligned with CDI principles.
Minimal retention
Data is retained only as long as necessary for operational purposes, safety requirements, or user-requested storage. Aggregated research data may be retained longer but remains de-identified.
No sale or sharing
Data is never sold, shared with third parties for commercial purposes, or repurposed beyond documented uses. No advertising networks, tracking pixels, or behavioral targeting infrastructure.
Security protections
Data is encrypted in transit and at rest. Access logs are maintained. Security incidents are disclosed according to applicable regulations.
User Rights
Users have comprehensive rights over their data:
Access
Request access to all data associated with your account through account settings or by contacting contact@atlasofcoordination.com.
Deletion
Delete your account and all associated data at any time. Deletion is permanent and cannot be reversed.
Portability
Export diagnostic data in structured format (JSON) for personal use or migration to other systems.
Correction
Update or correct account information through account settings. Diagnostic responses cannot be edited after completion but can be deleted.
Constitutional Enforcement
Data governance boundaries are architecturally enforced:
Data collection review
Any new data collection requires constitutional compliance review verifying alignment with observation-only boundaries and structural focus.
Prohibited use detection
Automated monitoring for data uses that would violate constitutional boundaries (evaluation, surveillance, control). Violations trigger alerts and require remediation.
Transparency documentation
All data practices are documented publicly. Changes to data collection or use are versioned and announced.
If a data practice cannot be clearly explained without evaluative, coercive, or surveillance language, it does not belong in the Atlas.
Data as Boundary
Data governance reflects what the Atlas is: diagnostic infrastructure with constitutional boundaries, not surveillance platform or optimization system.
These practices are not privacy marketing. They are architectural commitments preventing the Atlas from becoming what it explicitly refuses to be.
Data minimization is constitutional enforcement, not user-facing feature.
Canonical Foundations: Version 2.0
Year: 2026
Structural revision to align with rigorous gap-analysis standard. Major version changes indicate structural revisions; minor version changes indicate theoretical refinements.