Privacy &
local data.

The short version.

NeuralForge is a local-first, single-user evidence and review workspace. The MVP has no account authentication, cloud workspace sync, payment flow, or live external execution.

Workspace content

Saved in browser storage on this site.

Backups & handoffs

Files you choose to export and keep.

Page requests

Served by the website's hosting infrastructure.

Local-first does not mean encrypted, access-controlled, or immune to data loss. Treat your browser profile and exported files as places where sensitive project information may be stored.

What stays in your browser.

The workspace stores the missions, evidence you add, review decisions, and related local history needed to continue your work. This data belongs to the current browser profile and site origin, not to a NeuralForge cloud account.

A different browser, browser profile, device, or site address will not automatically see the same workspace. Private-browsing sessions, browser cleanup, storage limits, and clearing site data can remove local work.

There is no account-based access control or application-level encryption protecting the local workspace. Someone with access to your unlocked device or browser profile may be able to read it. Be cautious on shared devices, and avoid storing passwords, API keys, or material you are not authorized to retain.

Backups move when you export them.

JSON backups make workspace data portable. Handoff exports let you carry review context into another tool or share it with another person. NeuralForge does not automatically sync those files to a team or an agent provider.

Exported files may contain the project names, evidence, notes, and decisions you entered. They are not encrypted by the application. Review the contents before sharing, store backups somewhere appropriate, and protect them like the source material.

Once you upload or send an exported file through another service, that service's data handling applies. Importing a backup is a deliberate transfer of local data, not a connection between two live workspaces.

A local workspace still has a website.

The marketing site adds no analytics, advertising trackers, tracking cookies, third-party fonts, or CDN scripts. The MVP does not send your workspace content to an AI service or a NeuralForge cloud workspace.

Loading the hosted website and its assets makes normal network requests. The hosting provider may process request metadata such as your IP address, browser information, requested URL, and request time for delivery, security, and operations. This is not a promise of zero network metadata.

Keep private information out of URLs. Browser extensions, device software, downloaded-file sync, and tools you use outside NeuralForge have their own access and data practices.

Local-first is not an offline guarantee.

Local review operations do not need an AI API or remote execution service. An already-loaded workspace can work with its local data without those services.

Opening or refreshing the hosted app may still need network access. This MVP does not guarantee an installable app, offline asset availability, background sync, or recovery after browser data is removed. Keep exported backups even when the workspace appears to be saved.

Clearing local data.

You can remove the site's stored workspace data through your browser's site-data settings. Export anything you need first: clearing browser storage can remove the workspace and its local recovery history.

Clearing the site does not delete files already exported to your downloads folder, other devices, backup tools, or recipients. Remove those separately where appropriate. It also does not erase operational request logs held by the hosting provider.

Your review is a record, not a certificate.

Evidence coverage is a checklist calculation. It is not a truth probability, security guarantee, or certification of the underlying work. Local review receipts are not independently signed attestations.

The MVP's action previews are dry runs, not authority to execute external actions. NeuralForge does not run operating-system commands, deploy code, control your agent accounts, or replace an independent reviewer.

These notes describe the September local MVP. Any future account, cloud, integration, or execution feature would need its own clearly disclosed behavior and data boundaries.