SimShelf

Privacy Policy

Last updated: 10 August 2026

This policy explains what data the SimShelf app (“SimShelf”, “the app”) records, how it is used, and your choices. SimShelf is published by TraLand.com (“we”, “us”). If you have any questions, contact us at [email protected].

The short version

No account, no sign-in. SimShelf does not ask you to register.
SimShelf makes no network connections of any kind — it links no networking library, so there is nothing to send and nothing to opt out of.
It has no analytics, no advertising, and no third-party SDKs.
The Simulator data you inspect stays on your Mac. We — the developer — never see it.
Version 1.0 is fully read-only; it never writes to the data you inspect.

What the app does

SimShelf inspects the local data of iOS apps running in Apple’s iOS Simulator on your Mac — databases, preferences, caches, JSON and plist files, and App-Group data. It is a read-only tool for looking at data your own apps wrote on your own machine.

The data you inspect

The files and databases you open stay where they are. SimShelf reads them directly on your Mac — using SQLite’s own read-only guarantees, or from a private copy inside SimShelf’s sandbox — and never copies, uploads or transmits their contents anywhere.

The app runs inside Apple’s App Sandbox and can only reach the Simulator locations and files you explicitly choose through a system open panel. It does not call simctl, does not use private APIs, and does not scan outside what you select.

What is stored, and where

To work the way you would expect between launches, SimShelf stores the following on your Mac only, inside the app’s own sandboxed storage:

the list of sources (containers, App Groups, snapshots) you have recently opened, so they can be reopened;
a local activity log of your own actions, kept for your history;
temporary private working copies of databases, used so a live database can be read safely.

None of this leaves your device. It is not uploaded to any server and we never receive it. The activity log is for your own reference and is never transmitted. Deleting the SimShelf app removes all of it.

Snapshots you export

If you export a .simshelf snapshot, SimShelf writes a single ZIP file to a location you pick. It is not sent anywhere. Because a snapshot is a faithful copy of what your app saved, it may contain sensitive data — authentication tokens, personal or customer information. Before every export, SimShelf plainly reminds you of this. SimShelf does not scan a snapshot for secrets and never claims to; the reminder is a prompt for your judgement, not a guarantee. You are responsible for how you store and share the snapshots you create.

Diagnostics

SimShelf has no automatic error reporting. Nothing is ever sent when something goes wrong. If you choose to email us for support, you decide what to include.

Purchases

SimShelf is sold through the Mac App Store. Payment is handled entirely by Apple; we never see your payment details. Apple provides developers with anonymised, aggregated sales reports that contain no information identifying individual customers. The app validates its App Store receipt locally on your Mac, which involves no network connection and sends nothing to us or to Apple.

Third parties

SimShelf contains no third-party SDKs, analytics libraries, advertising frameworks or crash reporters. It is built on Apple’s own SDK (Swift, SQLite and zlib) with no third-party dependencies. There is no code in it that talks to anyone.

Data retention and deletion

Everything lives on your Mac and is under your control:

Clear the Recent Sources list from within the app.
Delete any .simshelf snapshots you exported, like any other file.
Deleting the SimShelf app removes all of its stored data from your Mac.

Because we never receive your data, there is nothing for us to retain or delete on your behalf.

Children’s privacy

SimShelf is a developer utility and is not directed at children. It collects no personal information from anyone, including children.

Changes to this policy

If this policy changes, we will update it here and revise the “Last updated” date above. Material changes will be reflected in a future app update.