Privacy

On your Mac

SimDock’s settings, recents, favorites, workspaces and scenarios are stored on your Mac. Quick Input values are stored in your Keychain. SimDock talks to the iOS Simulator through Apple’s xcrun simctl, on your Mac.

Usage analytics — optional and off by default

Starting with SimDock 1.2, you can choose to share usage analytics in Settings → Usage Analytics. It stays off unless you turn it on.

Starting with SimDock 1.3, SimDock also asks once, at launch, if you haven’t chosen yet — on a new installation, or after updating if you never used the setting. The question offers two buttons,Share Usage Analytics and Not Now. Neither is pre-selected. While the question is on screen, nothing is sent and no installation ID is created. Analytics turns on only when you choose Share Usage Analytics; Not Now keeps it off. If you already turned analytics on or off in SimDock 1.2, your choice is kept and you aren’t asked. There is no event for the question itself; choosing Share Usage Analytics simply turns analytics on, as described below. You can change your choice anytime in Settings → Usage Analytics.

When analytics is on, SimDock sends two kinds of event to this website’s own server — no third-party analytics service is involved:

App session started

When SimDock launches, and when you turn analytics on — in Settings or by choosing Share Usage Analytics.

Tool used

The category of a tool you open, such as “location” or “screenshot” — at most once per tool per session.

Each event contains only:

• a random installation ID,
• the event type and, for “tool used”, the tool category,
• SimDock’s version and build number,
• your macOS major and minor version,
• the time it was sent.

The installation ID is generated at random when you turn analytics on. It isn’t derived from your Mac, your Apple Account or anything else, and it’s deleted from your Mac when you turn analytics off. Because the ID links events from the same installation, this data is pseudonymous rather than anonymous.

Crash reports — optional and separate

Starting with SimDock 1.4, SimDock can send a crash report when it quits unexpectedly. This is separate from usage analytics: it has its own question, its own setting (Settings → Crash Reports) and its own storage on the server, and choosing one never turns on the other.

SimDock asks once, at launch, until you choose — on a new installation, and once after updating from SimDock 1.3, even if you already answered the usage analytics question. The question offers two buttons,Send Crash Reports and Don’t Send. Neither is pre-selected, and nothing is sent while the question is on screen. Your usage analytics choice is kept as it was.

The crash information comes from macOS: after a crash, macOS hands SimDock a diagnostic of its own crash the next time it starts (Apple’s MetricKit). SimDock doesn’t read or upload the crash logs macOS keeps in your Library (.ips files) and needs no extra permission.

Send Crash Reports

Crashes that happen after you chose it are reported automatically.

Not chosen yet

SimDock asks about that one crash — Send Report or Don’t Send, again with neither pre-selected — and you can read the exact report first. The same applies to a crash that happened before you turned crash reports on. Once you answer, SimDock doesn’t ask about that crash again.

Don’t Send

Nothing is sent, and SimDock doesn’t ask about crashes.

A quit that macOS doesn’t report as a crash — a force quit or a power loss, for example — is never reported.

Each crash report contains only:

• the kind of crash: exception type, signal and termination category, and for an uncaught Objective-C exception its standard class name (never its message),
• code locations of the crashed thread, as binary names and offsets inside SimDock and macOS — any other library appears only as “other”,
• a crash signature computed from those values, to group identical crashes,
• SimDock’s version and build, your macOS major and minor version and your Mac’s processor type,
• the hour the crash happened.

Reports are reduced and sanitized on your Mac before anything is stored or sent: file paths, your user name, folder and volume names, web addresses, command arguments, error messages and anything that looks like a secret are removed, and every value has to be a short technical token. A report contains nothing you typed or worked on — no project, simulator, Quick Input, clipboard or deep link content — and no memory contents or screenshots.

Crash reports carry no installation ID and no device identifier, so they aren’t linked to your Mac or to each other. We still don’t describe them as anonymous: versions and code locations are technical details of the Mac a report came from.

Turning off Settings → Crash Reports takes effect immediately: SimDock stops sending and deletes reports still waiting on your Mac. Because a sent report has no ID, it can’t be looked up and deleted for one Mac afterwards; instead, individual reports are kept for up to 90 days and then reduced to counts per crash signature and version, without code locations. Delete My Data applies to usage analytics only. The crash-report database stores no IP addresses, and crash reports are not written to the web server’s access log.

What SimDock never collects

• Anything you type, paste or copy, including Quick Input values and your clipboard.
• Deep links, URLs, push payloads, locations or routes you send to a simulator.
• UserDefaults keys or values, Keychain contents, files, folders or file paths.
• Project, app or bundle names; simulator names, device identifiers (UDIDs) or runtimes.
• Screenshots, recordings or console logs.
• Your name, email address, Apple Account, Mac serial number or any hardware or advertising identifier.
• Error messages, command output or environment variables.
• The full crash logs macOS keeps (.ips files), memory contents or crash messages.

Your controls

Turn off

Takes effect immediately and doesn’t need a network connection. SimDock stops sending and deletes the installation ID.

Reset ID

Replaces the installation ID with a new random one, so later events can’t be linked to earlier ones.

Delete My Data

Turns analytics off and asks the server to delete every event sent with your current ID. If the server can’t be reached, the events expire on their own (see below).

Crash Reports

A separate switch. Turning it off stops crash reports and deletes any waiting on your Mac; sent reports expire as described above.

Storage and retention

Analytics events and crash reports are stored, in separate databases, on the server that hosts this website. Crash reports follow the retention described above. Individual analytics events are kept for up to 90 days; after that they are reduced to daily totals that contain no installation IDs. The analytics database stores no IP addresses, and analytics requests are not written to the web server’s access log. Requests that fail or that the server rejects, for example for exceeding its rate limit, can appear in its error log, which is deleted after 14 days.

Software updates

SimDock 1.2 and later check for updates by downloading a signed update feed from this website, and SimDock asks before checking automatically. The check sends no information about your Mac beyond what any web request includes. Updates are verified with SimDock’s signing key before they’re installed.

This website and downloads

This website uses no cookies, no analytics scripts and no third-party trackers. Like most web servers, it keeps an access log — IP address, time, requested address and browser identification — for operation and security. The log is rotated daily and deleted after 14 days. Download numbers are computed from this log as daily totals; no addresses are kept with them.