Privacy and Telemetry
Separate optional usage and crash reports from online features you choose to use
Last updated: 2026-10-27
Local image work is processed on your computer; model-based tools may require installed models and your GPU. Other features contact online services. Settings → Privacy has separate switches for usage tracking and crash reporting; turning them off does not disable licensing or every network feature.
Local work and network features
| Feature | What leaves your computer / when |
|---|---|
| Local generation and image editing | Image work uses local files. GPU/model requirements depend on the tool; some creation/editing paths use CPU processing. Local processing does not upload each render to a cloud generator. |
| License activation and checks | License/device verification contacts 360hextile.com. Offline rendering requires a previously verified license within its seven-day window. |
| Model downloads and updates | The selected model host or update service receives the requests needed to download files or check a release. Gated models may need your model-host account credentials. |
| Copilot | Your request and selected app context go to the chosen AI provider. Your provider may charge separately for BYOK use. Hosted assistance and your own provider key are separate choices. Cached documentation does not make inference offline. See Copilot. |
| AI prompt assistance | The selected provider receives the text/context needed for that action. Review provider choice and avoid including private material you do not want it to receive. |
| Gallery publishing and metadata assistance | Connecting, preparing online metadata and publishing have separate network effects. Publishing shares the chosen image and metadata; check recipe-sharing choices before submitting. See Publishing. |
| Feedback | Sending transmits your authored message and the diagnostics you opt to include. A local saved report is separate from an online receipt. See Reporting an issue. |
| Usage tracking | Optional counts and device/app facts are sent when enabled, as described below. |
| Crash reporting | Separately optional error details and system information are sent to the reporting service. |
What We Collect
With Enable usage tracking on, usage data includes render/tile counts, feature and pipeline usage, GPU model/VRAM, app/OS versions and error types. Usage events are designed to exclude prompts, images and file contents. This statement describes usage tracking, not the separate features in the table above.
With an active license, usage totals can appear on your login-only account dashboard. They are not your public Gallery profile. Unlicensed opt-in events may be recorded as unattached aggregate counts and do not populate an account dashboard.
Opting Out
Turn off Enable usage tracking in Settings → Privacy to stop future optional usage tracking. Send anonymous crash reports is a separate switch. Neither switch withdraws an already submitted feedback report or published Gallery item, nor disables necessary license verification.
Sentry Crash Reporting
Crash reporting sends error details, stack traces and system information to help diagnose failures. Reporting applies privacy filtering, but arbitrary error text is not a guarantee of complete removal of private information. Keep crash reporting off if you do not want automatic error reports. Manually shared diagnostics are a separate choice: review what you send and remove sensitive material from your message.
Why We Collect It
Optional usage data helps prioritize tools, bug fixes and hardware support. For service data handling, see the Privacy Policy, or contact us with a question.