User Consent, Data Rights & Privacy-by-Design
MeshNativeExchange enforces GDPR privacy-by-design — data purpose declaration, consent prompts, right to delete, right to export, and data minimization across every mesh-native app.
Privacy by Design, Enforced by Fabric
GDPR compliance is not an afterthought — it is built into the fabric of the Mesh-Native ecosystem. Every app must declare its data purpose, retention, consent, and deletion policies before it can be published. The Policy Fabric enforces these declarations at runtime; the Privacy & Data Fabric ensures data minimization; and the Observability Fabric logs every consent event.
Data Purpose Declaration
Every app must declare the specific purpose for which it collects data. Data used for any purpose beyond this declaration is a policy violation.
Data Retention Limits
Apps must declare a retention period. Data is automatically purged when the retention period expires — no app may retain data indefinitely.
Consent Before Access
Consent prompts are enforced before any app can access sensitive data or mesh-native capabilities. Consent is logged, timestamped, and withdrawable at any time.
Right to Delete
Users can wipe app data locally and invalidate all cached derivatives. Deletion propagates across the mesh — no derivative or cached copy survives.
Right to Export
Users can export all app-related data in JSON or CSV format. Export includes raw data, consent history, and processing logs.
Data Minimization
Apps may only collect data explicitly declared in their Permission Manifest. Any attempt to collect undeclared data is blocked and logged.
GDPR Data Subject Rights
MeshNativeExchange supports all six core GDPR data subject rights. Each right is exposed as an API that users can invoke at any time — no support ticket required.
Right to be Informed
Users are informed about what data is collected, why, and how long it is retained.
Right of Access
Users can request a copy of all data an app holds about them.
Right to Rectification
Users can correct inaccurate or incomplete data.
Right to Erasure
Users can delete their data and all cached derivatives — locally and mesh-wide.
Right to Data Portability
Users can export their data in JSON or CSV and transfer it to another app.
Right to Object
Users can object to processing based on legitimate interest and withdraw consent at any time.
DOSFI Sovereignty — Closed Core / Open Surface
DOSFI Core is sovereign and closed. All educational content on this page is generated exclusively from open-surface materials — SDKs, ABIs, documentation, tutorials, examples, and conceptual explanations. Internal details of the DOSFI Runtime, Scheduler, Router, Readiness Engine, Privacy Model, Power/Thermal Model, Vital internals, DIU internals, MNE internals, and Mesh-Native App runtime internals are not revealed, described, or inferred.
No proprietary algorithms, system code, or architectural diagrams capable of enabling replication of the DOSFI Core are published. When internal logic is referenced, only high-level conceptual explanations are provided. DOSFI's sovereignty, mission-lock, and non-replicable architecture are preserved at all times.