App privacy statement
Last updated on October 26, 2026
Privacy is important to me. My apps are therefore designed so that Robin van Holst does not receive personal data or app content, except when this is expressly described for a specific feature below. Data you enter remains stored locally on your device or is processed only through a synchronization or network feature you choose to use.
Rally Rampage
Rally Rampage stores game progress, credits, cars, settings and customizations on your device. When iCloud is available for the app, it synchronizes this data between your devices through the key-value store in your own Apple iCloud account. Apple processes this data under its privacy terms. I do not receive your game data or have access to your iCloud account. The app has no developer account, advertising or tracking.
Vault
Vault stores vault names, notes, links, attachments, settings and browser cookies in encrypted form. Robin van Holst does not receive or have access to this content.
iCloud synchronization is optional. When you enable it, Vault uploads only already-encrypted vault data to your personal Apple iCloud and CloudKit environment so you can synchronize it across your own Apple devices. Apple processes data according to its own privacy terms.
When Vault retrieves a link preview or you open a website in its private browser, the app makes a normal network connection to the website you selected. That website and its service providers may receive ordinary network information such as your IP address. A bounded set of website cookies may be stored encrypted inside your vault to preserve sessions within that vault. Vault does not persist browsing history, cache, website local storage, tab titles or tab addresses; the live browser session is destroyed when Vault locks or you switch vaults.
Adwords Manager dashboard sharing
When you create a share link in Adwords Manager, a limited read-only snapshot of the selected campaign data is stored on my own server. This may include campaign names, status, budgets, dates, aggregated performance and selected leading keywords. Google access tokens, refresh tokens, developer tokens and original Google account numbers are never uploaded.
The share link contains a random, unguessable reference and remains available to anyone who receives it until its expiry date or until you revoke it in the app. A separate management secret is stored on the server only as a hash. Shared data is not used for analytics, profiling or advertising.
Anonymous usage counter
Some apps send a simple anonymous usage event to appstats on my own server. This event is used exclusively to maintain a general usage-count counter.
The counter contains no personal data, IP addresses, device characteristics or unique identifiers. No user profile is created and the data cannot be linked to a person or device.
Technical diagnostics
Some apps may send privacy-minimal technical diagnostics to my own server when an error is caught, after an unexpected app termination on the next launch, or through Apple’s MetricKit crash diagnostics. Reports may contain the error type, technical context, a bounded error message and stack information, app and build version, operating-system version, hardware model, platform, and whether the app is a development or production build.
Reports do not contain photos, document content, filenames, account, session or installation identifiers, or complete local file paths. Matching technical reports are grouped by an anonymous fingerprint and retained only as aggregate counts for troubleshooting. They are not linked to a person or device, are not used for tracking, advertising or profiling, and are used solely to improve app functionality and stability.
First-party infrastructure
appstats runs on my own server environment, hosted in the Netherlands and the European Union. No external analytics services, advertising networks or other third parties are used for this measurement.
No tracking or fingerprinting
My apps do not use tracking cookies, advertising identifiers, analytics SDKs or fingerprinting. The anonymous counter is neither intended nor suitable for tracking individual users, devices or usage patterns.
Photo Expander
This information applies to the Mac App Store version of Photo Expander. The app edits photos entirely on your Mac. Photos, projects (.pex), recipes and settings stay on your device; nothing is sent to me. The app has no diagnostics upload or app account. Version 1.0 build 2 and earlier do not send usage statistics. The number of free Pro exports used is stored locally in app settings and, when available, the keychain; this counter is not sent to me.
Anonymous usage statistics
Starting with version 1.0 build 3, Photo Expander may send anonymous usage statistics to my own server at robinvanholst.nl: counts of opened documents, types of completed edits, selected or used models, and successful, failed or cancelled exports. A bounded sequence of fixed steps helps compare editing paths that lead to an export. No photos, prompts, filenames, editing content or user, installation, device or session identifiers are sent, and no individual user profiles are created. Statistics are stored as daily aggregates and are not used for advertising or tracking.
You can disable this in Settings → Privacy → Share anonymous usage statistics. The app then stops collecting and clears unsent counters and measurement paths. Existing anonymous aggregates cannot be linked to you or individually deleted. Daily counts older than 180 days are removed on a later valid usage request, so removal can be delayed when no traffic arrives. As with ordinary HTTPS connections, hosting infrastructure sees a network address; the statistics tables do not store IP addresses or user agents.
Optional model downloads
Some fills, upscalers and the AI denoiser need a model file. The app downloads it only after you choose to download it, from GitHub or Hugging Face (including GitHub’s raw-file and release-download hosts), and checks it against a fixed checksum. Those download hosts can see your IP address; model downloads do not send them your photos or other app content.
Purchases
Subscriptions and the Lifetime purchase are handled by Apple via the App Store. I only receive the information Apple makes available to developers (such as anonymous sales figures); I never see your payment details or Apple ID.
Apple and the App Store
When you download an app through the Mac App Store or make a purchase, Apple processes data according to its own privacy terms. I only receive the information Apple makes available to developers and do not have access to your complete payment details.
Contact
Because my apps do not collect personal data, the anonymous usage counter cannot be linked to an individual user. For privacy questions, email privacy@robinvanholst.nl. For general questions, support or feedback about an app, email apps@robinvanholst.nl.
Changes
This privacy statement may be updated when apps, services used or legal requirements change. The latest version is always available on this page.