Privacy Policy

Last updated September 20, 2026.

This policy covers three things. The apps I publish, this website, and what happens when you buy a license or send me a message. Each has its own section below, because they behave very differently. The short version is that the apps collect nothing, the website runs no tracking of any kind and keeps only a running count of app downloads alongside the daily totals my host already produces, and buying a license means I hold your email address for as long as the license is valid.

The apps

None of my apps collect personal data, use analytics or tracking, or transmit your files or library data. This applies to every app I publish unless its store listing says otherwise.

Data stored on your device

Application preferences, security-scoped bookmarks, cached thumbnails, and any per-app data (such as tags, favorites, recents, or playlists) are stored locally on your Mac. They are not transmitted to me or any third party. Uninstalling an app removes its data from your device.

Network connections

My apps connect to the network only for the following purposes:

• Software updates (non-Mac App Store builds). Apps periodically check for new versions by fetching an update feed from storage.douglaslassance.me. The request includes only standard HTTP metadata such as your IP address and macOS version, and is not used for tracking.
• Public assets and metadata. Some apps fetch publicly available assets from community sources (for example, thumbnails, cover art, or reference data) to enrich what you see. These requests include only standard HTTP metadata.
• License checks (directly sold apps). An app holding a license key may check that the key is still valid against api.douglaslassance.me. The check sends the key, not your email address.
• In-App Purchases (Mac App Store builds). Purchases and receipt validation are handled by Apple's StoreKit framework. I never see your payment information. Apple's privacy policy applies.

Files and folders

My apps only read files and folders that you explicitly grant access to via the macOS sandbox. Previews, waveforms, suggestions, and similar features are computed entirely on your Mac. No file content is uploaded.

Analytics and crash reporting

My apps do not use analytics, telemetry, crash reporting, or advertising SDKs. No usage data is collected.

This website

The website collects nothing about you. No script measures you, nothing identifies you, and nothing follows you from one page to the next. What follows covers the site and the API behind its contact form and license keys.

Cookies

None, which is why there is no consent banner to dismiss. The only thing kept in your browser is the display preference you picked yourself, such as the theme. It stays on your device and is never sent anywhere.

Page visits

No analytics service runs on this site. There is no tracking script, nothing is written to your browser, and no page you open is tied to you or to any other page you opened.

What I do read is the daily traffic summary Cloudflare produces as my host, from the requests described under Hosting below. It gives me one line per day. How many pages were served, and how many distinct addresses made a request, both counted by Cloudflare at its edge. That address count is not a count of people, because it covers everything on the domain including my own apps checking a license. I never see the addresses themselves, which pages any one person opened, or anything else that would let me pick a visitor out of a day.

Downloads

Downloading an app writes one row to my own database, recording which app, which version, which build, and when. That is the whole record, and it exists so I can see download numbers over time. No IP address, no country, no browser, and nothing that identifies you or ties a download to you.

Errors

The site itself reports nothing when it breaks. The API behind the contact form and license keys does report its unhandled errors to Sentry, so that a failure there gets noticed rather than sitting broken. A report carries the error and the address of the request it came from, with the query string stripped first. It does not carry cookies, request headers, request bodies, or the values of any variables in scope when the error occurred, which is what keeps license keys and email addresses out of it.

Hosting

The site and the API behind it both run on Cloudflare. Both see the standard request metadata any web server sees, including your IP address, as part of delivering a response. Cloudflare rolls those requests up into the daily totals described above, which is the only form I ever see them in.

Buying a license and getting in touch

License purchases

Some apps are sold directly rather than through the Mac App Store. Payment is handled by Stripe, and I never see your card details. When a purchase completes, Stripe passes my licensing API your email address, and that address is stored alongside the license key, the Stripe identifiers for the purchase, when it happened, and whether the key is still valid. The key is then emailed to you.

That record is what makes the key keep working, so it is kept for as long as the license is valid rather than deleted on a schedule. If you refund a purchase, the record stays but the key is marked revoked. Stripe's own privacy policy covers the payment itself.

The contact form

The contact form asks for your email address, a subject, and a message. They are sent to me as an email, with your address set as the reply-to so that I can answer you. Nothing from the form is written to a database or kept on a server; it lives in my mailbox like any other email, for as long as it is useful to keep.

Who else handles this data

Nothing described here is sold, and nothing is shared beyond the services that make it work:

• Stripe, for payments on directly sold apps.
• Cloudflare, which serves this website, runs the API, stores license and download records, summarizes the daily traffic, and delivers the emails it sends.
• Sentry, which receives that API's error reports.
• Apple, for Mac App Store purchases and receipt validation.

Those error reports are kept under the retention settings on my Sentry account and are not exported anywhere else.

Children

My apps and this website are not directed at children under 13 and do not knowingly collect data from them.

Changes to this policy

If this policy is updated, the revised version will be posted on this page with a new "Last updated" date.

Contact me

If you have any questions or concerns regarding this policy or your personal information, including a request to delete a license record, you may contact me using this form.