No forced model path.
Use the provider and model appropriate for the project, including local model paths where supported.
Data boundary
Local-first, stated precisely.
ADDOM keeps product state close to the machine and makes consequential actions visible before they cross the active boundary.
The boundary
What remains local and what can leave the device.
“Local-first” does not mean remote providers are local. It means ADDOM's own application state is device-anchored and remote transmission follows explicit provider use.
Kept on the device
Never transmitted by ADDOM
Projects and workspace registrationLocal
Threads and continuity stateLocal
Credentials and settingsLocal
Artifacts and local memoryLocal
Telemetry for ADDOMNot collected
Remote when you choose it
Only after an explicit choice
Prompts sent to a remote modelSelected provider
Files included in model contextSelected provider
Remote knowledge featuresConfigured service
Links opened in your browserDestination site
Issue or discussion postsGitHub
Provider responsibility: remote model requests are governed by the provider and account you configure. Review that provider's terms and privacy controls before sending sensitive project material.
Control surfaces
Privacy is reinforced by visible operation.
Data boundaries become more useful when the actions crossing them are understandable and adjustable.
Scope machine-side work.
Permission modes define what the current thread may inspect or change.
Review consequential actions.
Tools that cross the active boundary can pause for an explicit decision.
Inspect the implementation.
The MIT-licensed source makes the application's behavior reviewable beyond this policy statement.
Questions
Short answers without vague promises.
Does ADDOM send analytics or crash telemetry to the developer?
No. ADDOM does not include remote product telemetry or developer data collection.
Can project data still be sent to an AI provider?
Yes. When you choose a remote model, the request and context you provide are sent through that configured provider path. ADDOM does not make the remote provider local.
Where are credentials stored?
Provider credentials are stored on the device for the local ADDOM profile and used for the provider path you configure.
Does uninstalling ADDOM delete local project files?
No. ADDOM operates on project folders you choose; removing the application does not make those folders ADDOM-owned data. Consult the repository documentation for current application-data behavior.
Verify the claim
Read the source, not only the promise.
The repository contains the implementation, security policy, contribution guidance, and issue tracker.