Since Filemorph 2.8 the app can send two kinds of report to our own server: a daily count of which tools ran and how they turned out, and the crash and hang reports Apple's MetricKit hands the app. This page shows both, field by field. Neither contains a file, a file name, text from a document or an account number, and one switch in Settings turns both off.
virtualMemoryRegionInfo) and the free-text part of the exception reason (exceptionReason, reduced to its exception name and class).https://telemetry.filemorph.app/v1/, a Cloudflare Worker we run. It drops your IP address and stores the data with New Relic in its United States region, and raw crash reports in Cloudflare R2.Until 2.8 the app sent no usage or crash data at all, so when a conversion failed or the app crashed we had no way to know which one, or why. These reports exist to find and fix those failures. They are not used for advertising, not sold, and not combined with data from any other company.
Sent at most once a day: when you open the app or bring it back to the foreground, at least 24 hours after the last successful report, and only if something was counted. It carries the counts since the last report. If sending fails, for example with no connection, the counts keep adding up on the device and the app tries again the next time you open it; there is no background retry. A report is a few kilobytes and never more than 8 KB.
A sample report (the install identifier is shortened with … for display; a real one is a full 36-character UUID):
{
"schema": 1,
"kind": "usage",
"install": "7c1f4a0e-…",
"app": "2.8",
"build": "31",
"platform": "ios",
"os": "26.1",
"device": "iPhone16,2",
"channel": "appstore",
"tier": "free",
"periodStart": "2026-11-01T00:00:00Z",
"periodEnd": "2026-11-02T08:14:03Z",
"launches": 3,
"ops": {
"pdfToOFX": { "ok": 3, "fail": 1, "cancel": 0 },
"imageConvert": { "ok": 12, "fail": 0, "cancel": 1 },
"enhanceOldPhoto": { "ok": 1, "fail": 2, "cancel": 0 }
},
"errors": {
"pdfToOFX|processingFailed|No transaction table found": 1,
"enhanceOldPhoto|modelDownloadFailed|NSURLErrorDomain#-1009": 2
},
"models": { "gfpgan": { "ok": 1, "fail": 2 } }
}
| Field | What it means |
|---|---|
schema |
Format version, currently 1. A new field means a new version, and this page changes with it. |
kind |
usage for this report. |
install |
The random install identifier (see Reset the identifier). |
app, build |
Filemorph version and build number. |
platform |
ios, ipados or macos. |
os |
Operating-system version, major and minor only. |
device |
The hardware model identifier, such as iPhone16,2 or Mac16,10. It names the model, which every device of that kind shares, not your device. It is what lets us match a crash to the hardware it happens on. |
channel |
appstore, testflight or debug, so our own test builds can be filtered out. A Mac TestFlight build reports appstore. |
tier |
free or pro. |
periodStart, periodEnd |
The span of time the counts cover, in UTC. No time zone is sent. |
launches |
How many times the app was launched in that span. |
ops |
For each tool, by its internal name: how many runs succeeded (ok), failed (fail) or were cancelled (cancel). A chained job or a preset counts once per step. Nothing about the file or the settings you chose. |
errors |
For each kind of failure, tool|error code|detail and how many times it happened. The error code is a fixed name such as processingFailed or timeout. The detail is one of three things: the fixed opening of an error message as written in the app's source code (such as No transaction table found), a system error identity such as NSCocoaErrorDomain#257, or nothing. Whatever the app inserted into a message at the point of failure, a file name for example, is never part of the detail. |
models |
For each AI Enhance model download: how many succeeded and how many failed. |
truncated |
Present only when the report was cut down to the 60 busiest tools and the 50 most frequent errors. |
dropped |
Present only when earlier counts were too large to send and were discarded instead: how many such periods. |
Our server adds one field before storing a report: country, the two-letter country code Cloudflare derives from the connection. The app does not send it, and the IP address it comes from is not stored.
When the app crashes or hangs, iOS and macOS later hand it a diagnostic report through Apple's MetricKit framework; for a crash, usually the next time you open the app. MetricKit also reports CPU exceptions and disk-write exceptions (the app used too much processor time, or wrote too much to storage, in a short span) and, on iOS where the system delivers them, slow app launches; these are uploaded the same way. While sharing is on, the app wraps the report in a small envelope and uploads it straight away. If that fails it waits on the device, at most the newest 20, and the app tries again the next time you open it. A report is typically 5 to 60 KB.
{
"schema": 1,
"kind": "diagnostic",
"install": "7c1f4a0e-…",
"app": "2.8", "build": "31", "platform": "macos", "os": "15.1", "device": "Mac16,10",
"channel": "appstore",
"payload": { …Apple's MXDiagnosticPayload JSON without virtualMemoryRegionInfo,
and with exceptionReason cut to exceptionName and className… }
}
The envelope fields mean the same as in the usage report. payload is Apple's own crash report JSON, with the memory-map dump (virtualMemoryRegionInfo) removed and the exception reason (exceptionReason) cut to its exception name and class, dropping its free-text message, so it carries no file names or user text. It is shortened above. It contains:
US), whether Low Power Mode was on (lowPowerModeEnabled), whether the app is a TestFlight build (isTestFlightApp), the process ID of that run of the app (pid) and the app's bundle identifier (bundleIdentifier, com.filemorph.app).It is produced by the operating system, not from your documents: it does not include your files, their contents or their names. MetricKit's daily performance metrics (launch time, memory, battery) are never uploaded; they stay on the device as before.
https://telemetry.filemorph.app/v1/usage or https://telemetry.filemorph.app/v1/diagnostic, using Apple's own networking. There is no third-party SDK in the app and no vendor key in it.In the app, open Settings and, under Analytics & Improvements, tap What gets shared. It shows the usage report that would be sent right now, built from the live counts on your device in exactly the format above, how many crash reports are waiting, and when the last report was sent. A Copy button puts the JSON on your clipboard.
To watch the network side, run the Mac app behind a firewall monitor such as Little Snitch or LuLu. The connections you will see are to models.filemorph.app when you download a model, and to telemetry.filemorph.app at most once a day and after a crash, only while sharing is on.
Settings → Analytics & Improvements → Share Filemorph Analytics (on a Mac, Filemorph → Settings). It is on by default and the app does not interrupt you with a prompt about it: the Settings section itself, its About Analytics & Privacy… link to this page, our privacy policy and the App Store privacy label are the disclosure. Turning it off stops counting and sending at once and deletes the counts and crash reports waiting on the device. Crash reports MetricKit delivers after that stay on the device, as they always did. Every feature works the same either way.
The install identifier is a random UUID the app creates for itself. It is not derived from your device, your Apple ID or any advertising identifier, and it is sent nowhere except in the two reports on this page. Settings shows its first eight characters, so you can quote it in a support email if you want us to look at your reports. Settings → Analytics & Improvements → Reset Identifier replaces it with a new random one and clears the waiting counts and crash reports; from then on, new reports cannot be connected to old ones. Deleting and reinstalling the app has the same effect. Reports already received stay under the old identifier until they are deleted as described above.
These reports are not linked to you and not used to track you: they are never combined with data from other companies' apps or websites, never used for advertising and never passed to data brokers. The app's privacy manifest and its App Store privacy label list them under Data Not Linked to You as Usage Data (Product Interaction), Diagnostics (Crash Data, Performance Data) and Identifiers (User ID). For every other way the app uses the network, see every network call the app can make; the full policy is in the Privacy Policy.
No. A usage report is counts, error codes and a few facts about the app and the device model; a crash report is Apple's MetricKit diagnostic, made of call stacks and crash codes. Neither contains a file, a file name, text from a document or an account number. Settings → Analytics & Improvements → What gets shared in the app shows the exact report that would be sent next.
In the app's Settings, under Analytics & Improvements, switch off Share Filemorph Analytics. Counting and sending stop at once, and the counts and crash reports waiting on the device are deleted. Every feature keeps working the same.
Not from the report. It carries a random install identifier, not your name, email, Apple ID or any device or advertising identifier, and our server drops your IP address. The identifier only groups one install's reports together, and you can reset it at any time in Settings.
Last reviewed: November 2026 · Filemorph 2.8. If a report gains a field, this page changes first.