How local processing works in Invisly

Understand what local processing means for privacy: your code stays on your device with no cloud storage, server transmission, or residual files left behind.

When Invisly describes itself as a locally processed application, that has a concrete meaning for how your data is handled. Your code never travels to a remote server for analysis during normal operation, no cloud storage is involved, and no third-party service receives your work unless you explicitly use an advanced feature that requires it.

What “local processing” means for you

All core analysis — reading the problem you captured, generating solution suggestions, and displaying results — runs as a process on your own device using local compute resources. The workflow looks like this:

1. You trigger a capture using a keyboard shortcut.
2. Invisly processes the captured content on your machine.
3. Results are displayed directly in the overlay.
4. No data is transmitted as part of this flow.

Because the analysis stays on your device, your code is never exposed to network interception, third-party data handling policies, or server-side logging.

Your code never leaves your device (for basic functionality)

Invisly’s basic functionality does not require an internet connection and does not send your code anywhere. This means:

• There is no cloud storage account associated with your sessions.
• Your solutions and captured content are not backed up to any server.
• No copy of your code exists outside your local filesystem.
• Deinstalling Invisly removes all local application data with it.

For all core features, your code remains exclusively on your device from the moment you capture it to the moment the session ends.

How temporary files work

During a session, Invisly creates temporary files to support its analysis pipeline — for example, to hold a screenshot of a captured problem or an intermediate representation of your code before processing. These files are:

• Written to a sandboxed temporary directory on your device.
• Never synced, shared, or transmitted.
• Automatically deleted when the session ends.

You do not need to manually clear any data after using Invisly. The cleanup process runs automatically at session close, leaving no residual files that could expose your work.

If Invisly exits unexpectedly, any remaining temporary files are cleaned up the next time the application launches.

You control exactly what gets captured

Invisly only analyzes content you explicitly provide. There is no passive screen monitoring and no background recording. Every capture is triggered by a deliberate action on your part — a keyboard shortcut or a manual activation.

This means:

• If you do not trigger a capture, nothing is processed.
• If you close or hide the overlay, no further analysis runs.
• You can deactivate Invisly at any time, immediately stopping all activity.

Advanced AI processing and external services

Some advanced features optionally use external AI services to deliver higher-quality results. If you use one of these features:

All communication with external services is encrypted using industry-standard protocols. Only the specific content you submit for advanced processing is transmitted — your session history, device information, and other code are never included in those requests.

You can identify which features use external services in the application settings. Sticking to the core local features keeps your data entirely on your device at all times.