JOLACODE / DATA NOTES

Your workspace.
Your choices.

These notes explain the version-one implementation. JolaCode is a local application with a model connection that you configure.

On your machine

Conversations, original-file snapshots, workspace memory and audit records are saved in ~/.jolacode, or the directory you set with JOLACODE_STATE_DIR. Audit records may contain commands and their output. Browser storage holds interface preferences and local access state.

At your model provider

The assistant sends conversation context, code it reads and relevant tool output to your configured OpenAI-compatible endpoint. With a local server, inference stays on your machine. With a hosted provider, that provider receives the request and its own terms and data policies apply.

Credentials

Configure provider credentials in your local .env file. Do not commit that file, include it in a release or send it to another person. The source release contains no provider key.

This website

The static product website has no sign-up form, account system, advertising scripts or analytics integration. Download and copy-command controls do not submit personal information. Any future website host may keep its own request logs.

Before sharing a project

Review its contents and your model configuration. Only send material to a hosted provider when you have permission to do so. Keep the local application bound to loopback; it is designed for one operator.