Local AI and Network Behaviour

The launch direction is to keep ordinary note editing and selected local AI processing on the device. Running a task locally does not require uploading that task’s note content to a hosted model.

Initial model downloads and updates use the internet. Available storage and device memory determine which installed workflows can run.

Accounts, subscription verification, feedback and explicitly connected services can use the network independently of the editor. A paid-plan check is not the same operation as sending a note to an AI provider.

The final privacy policy must identify actual destinations, data categories, defaults and retention. This launch draft is an operation map, not a completed legal or network audit.

Choosing an iCloud or other provider folder means that provider can transfer your files under its own settings and terms. A local file is not necessarily a file that never syncs.

Nearby device connections are another path, with pairing, transport and recovery requirements. Neither route should be described as blanket zero-network operation.

Confirm the selected model, where the folder lives and which optional services are enabled. Download needed assets before a trip without connectivity.

Use the network checklist to record the operation, destination and observed result. This task has not performed a production network audit.

Local storage answers where files live. Local processing answers where a task runs. Store verification, model/worker downloads, optional sync and support each have separate network boundaries. Test the specific task after setup; do not use a local folder as evidence that every operation is offline.