How HeatScribe Handles Your Data

Your inspection images stay on your Mac.

No feature in HeatScribe uploads them. Weather lookup sends a location and a timestamp. Report maps send coordinates. Diagnostics contain logs only. None of them include your images.

There is no account to create, no cloud library, and no server-side processing of your inspection imagery. The small number of features that do make network requests are listed below, with exactly what each one sends.

If your client does not permit inspection imagery to leave your control, this page is written for them as much as for you.

What Stays on Your Mac

Everything below is processed and stored locally. None of it is uploaded to HeatScribe:

thermal and visible-light images
the temperature data extracted from them
spot, line, area and reference measurements
Delta T calculations and finding priorities
inspection findings, notes and annotations
client, inspector and equipment details
report templates, branding and logos
generated PDF reports
saved HeatScribe project files

Thermal decoding is local too. HeatScribe runs DJI's official Thermal SDK inside a local environment it manages on your Mac, so the step that turns a radiometric file into temperatures happens on your machine rather than on a server.

What Leaves Your Mac, Only When You Use It

Weather lookup
Sends: location and timestamp from an image
Goes to: Visual Crossing
When: only if you fetch weather

Report location maps (Pro)
Sends: GPS coordinates and map parameters
Goes to: Google Maps Static API
When: only if you generate a map

Purchase and licence activation
Sends: licence, order and activation details
Goes to: Lemon Squeezy
When: at purchase and activation

Support
Sends: diagnostic logs you export and choose to send
Goes to: HeatScribe
When: only if you send them

Diagnostics Contain Logs, Not Images

HeatScribe has an Export Diagnostic Logs feature. It is something you trigger, and the bundle is saved to a location you choose — it is not sent anywhere automatically.

The bundle contains app and runtime logs, plus a summary with the app version, macOS version, machine type and licence tier. It does not include inspection images or project files.

If you send diagnostics to support, review them first, as you would with any support material.

Working Offline

After activation, an activated Mac is intended to keep working offline.

Import, analysis, measurement, findings and PDF report generation all run without a connection.

Weather lookup and report maps are the only parts of the workflow that need one, and both are optional.

This matters in two situations: a site with no usable signal, and a client whose rules do not allow inspection data to be uploaded anywhere.

One Thing We Will Not Overstate

HeatScribe runs DJI's official Thermal SDK inside a virtualized runtime on your Mac, and that runtime has network access.

HeatScribe's own design keeps your images, thermal data, findings and reports local. But we cannot guarantee that DJI's own SDK components make no technical requests of their own, and

DJI's SDK terms and privacy materials describe what DJI may collect in connection with its SDKs.

We do not control those terms. DJI's materials are linked below.

If You Are Reviewing This for a Client or an IT Team

The points that usually matter in a review:

Inspection imagery is not uploaded to HeatScribe and is not processed on a HeatScribe server.
There is no user account and no cloud storage of project data.
The complete inspection-to-report workflow runs offline once the licence is activated.
Optional network features are individually avoidable, and their scope is listed above.
Reports and exports are produced locally and stay where you save them.
HeatScribe is a one-time purchase, so there is no ongoing service dependency for the software to keep functioning.

If a reviewer needs something this page does not cover, email hello@heatscribe.com and we will answer it directly.

HeatScribe:

DJI, for the SDK components described above:

Third-party services named on this page: