DevSpace Privacy Policy

DevSpace is a local-first developer storage and environment manager for Windows. It is designed to help users understand, clean, and relocate supported developer-tool storage while keeping project source code and sensitive locations protected.

1. Local-first design

DevSpace 1.0 does not require a DevSpace account, cloud account, or Mokaio sign-in.

DevSpace 1.0 does not include a cloud backend, advertising SDK, analytics SDK, or telemetry service. Scan results, settings, operation history, recovery journals, and application logs are stored locally on the Windows PC.

DevSpace does not upload scanned files, developer projects, file paths, cleanup history, relocation history, or recovery data to Mokaio.

2. Information DevSpace processes locally

To provide its features, DevSpace may inspect local information such as:

• Installed or discoverable developer tools and their versions.
• Configured developer-tool paths and environment settings.
• Developer cache and storage locations owned by supported providers.
• File and directory metadata required to measure storage usage.
• Filesystem allocation information, including hard-link-aware storage accounting where Windows exposes the required metadata.
• Drive type, filesystem type, free-space information, and relevant Windows filesystem properties.
• Process information used to determine whether a developer tool or related runtime may be active during a safety-sensitive operation.
• User-configured project roots and ignored paths.
• Cleanup, relocation, recovery, and scan operation state.
• Local diagnostic logs generated by DevSpace.

This processing occurs on the user's PC.

3. Project files and source code

DevSpace is not designed to index or upload project source code.

Project discovery is limited to roots explicitly configured by the user. DevSpace may inspect filesystem structure and metadata within those roots to identify supported projects and generated developer artifacts, but project source remains protected by the Safety Engine.

DevSpace does not intentionally transmit project files or source code to Mokaio.

4. Cleanup operations

Cleanup is user-initiated and permanent.

DevSpace only exposes cleanup candidates that pass provider-specific and central safety checks. Items may be classified as:

• Safe to clean — recognized regenerable provider data.
• Review before cleaning — removable data that may affect offline availability, installed development state, or future rebuild/download work.
• Protected / not managed — data DevSpace will not treat as a normal cleanup target.

DevSpace revalidates supported cleanup targets immediately before mutation. Cleanup data is removed directly and is not routed through the Windows Recycle Bin.

Cleanup operations and their verification results are recorded locally for audit and recovery purposes.

5. Move & Relocate operations

DevSpace can relocate only explicitly supported developer storage roots.

The relocation engine uses a safety-gated, transactional workflow that may include:

• Preflight validation.
• Physical path and filesystem identity checks.
• Destination and topology validation.
• Staging and copy verification.
• Supported provider configuration changes.
• Provider rediscovery.
• Source-retirement checks.
• Rollback or recovery handling if the operation cannot complete safely.

Relocation journals are stored locally so DevSpace can detect interrupted operations after a crash, forced termination, or restart.

DevSpace uses fail-closed behavior: if ownership, path identity, configuration state, or filesystem topology cannot be proven safe, destructive actions are blocked.

6. Recovery information

Incomplete relocation journals and other recovery-critical records may be retained locally even when ordinary history is pruned.

This is intentional. Recovery-critical data is preserved until DevSpace can determine that the operation has been completed, rolled back, manually resolved, or otherwise moved to a terminal state.

7. Logs and diagnostics

DevSpace keeps local diagnostic logs that may contain technical information such as:

• Timestamps.
• Operation identifiers.
• Provider names.
• Operation states.
• Error types.
• Non-secret diagnostic details needed to troubleshoot failures.

DevSpace is designed not to log secret environment-variable values or credentials as part of normal operation.

The exact local database and log locations are shown inside Settings → Privacy in the application.

8. Network access and third-party developer tools

DevSpace 1.0 does not require a Mokaio cloud service to scan, clean, relocate, or recover developer storage.

DevSpace may invoke supported developer tools installed on the local PC for discovery, configuration, or verification. Those third-party tools remain governed by their own software, configuration, privacy practices, registries, repositories, and network behavior.

DevSpace does not control network activity independently performed by third-party developer tools outside DevSpace.

9. Data sharing and sale

Mokaio does not receive DevSpace scan results, local file data, local developer-tool paths, cleanup history, relocation history, or recovery journals through DevSpace 1.0.

DevSpace 1.0 does not sell personal information and does not share local DevSpace data with advertisers or data brokers.

10. Data retention and deletion

DevSpace data remains on the local PC until it is removed through application controls, retention settings, application-data cleanup, or uninstallation, subject to safety rules for unresolved recovery records.

Users can review history-retention settings and local-data controls in the DevSpace Settings page.

Unresolved recovery records may be retained beyond ordinary history limits when necessary to prevent unsafe automatic actions.

11. Security and safety

DevSpace includes safety controls intended to reduce the risk of accidental deletion or unsafe relocation, including provider ownership checks, protected-path rules, filesystem identity checks, topology checks, revalidation before destructive actions, operation journaling, and recovery handling.

No software can guarantee protection against every possible filesystem failure, operating-system fault, hardware failure, third-party process race, or unexpected environment. Users should maintain appropriate backups of important development data.

12. Children's privacy

DevSpace is a professional developer utility and is not directed to children. DevSpace 1.0 does not provide account registration, social features, advertising, or cloud profiling.

13. Changes to this policy

Mokaio may update this Privacy Policy when DevSpace features, data practices, or applicable requirements change.

Material changes will be reflected on this page with an updated effective date.

14. Contact

For privacy questions or DevSpace support:

Email: support@mokaio.store Website: https://www.mokaio.store DevSpace Support: https://www.mokaio.store/support/devspace