Privacy Policy

Overview

Mint is a local-first macOS application designed to help you organize files on your Mac. We built Mint with a fundamental commitment to your privacy: your files never leave your computer. This policy explains in detail what data Mint does and does not access, process, or transmit.

Controller and Legal Basis

DZG Studio LLC, San Francisco, California, United States, is the controller for Mint’s first-party service records. From Mint 1.0.76 in the Direct edition and Mint 1.0.36 in the Setapp edition, both editions share the privacy-minimized usage data described below by default, as this Privacy Policy, linked under Get Started on the Welcome page, says. We rely on our legitimate interest in knowing whether Mint opens, installs and sets up, whether its core features work, and how they are used, so that we can fix failures and improve Mint. The data is limited to fixed events, carries no files, names, accounts or hardware identifiers, and you can object at any time by turning off Account > Share my usage statistics without losing any functionality. Installations that acknowledged an earlier version of this policy without making a choice are asked once before this default applies. The Mac App Store edition requires your separate analytics choice for every product event, including setup completion; agreeing to the Terms and acknowledging this Privacy Policy does not enable that collection. Turning sharing off stops future collection and does not affect processing that was lawful before.

Where applicable, we process Mint account, purchase, entitlement, free-trial check-in, and connected-device records to provide the product you requested, restore paid access, meet accounting or legal obligations, and protect the service from fraud and abuse. We process support messages to answer your request. We do not sell or share personal information for cross-context behavioral advertising.

You may have rights to request access, correction, deletion, restriction, or portability of personal data, to object where processing relies on legitimate interests, and to lodge a complaint with your local data-protection authority. Email dev@dzgapp.com to exercise a right. We may need enough information to verify that a request concerns you, but we do not collect additional identifying data solely to make anonymous installation records re-identifiable.

Local-First Architecture

Mint operates entirely on your Mac. All core functionality runs locally without requiring an internet connection:

• File analysis and organization — All scanning, categorization, and file-moving operations happen on your local filesystem. No files, file contents, filenames, or directory structures are ever uploaded to any server.
• OCR text recognition — Document text extraction is performed entirely on-device using the Apple Vision framework. Extracted text is processed in memory and never transmitted externally.
• Content-aware processing — Mint uses on-device metadata analysis, filename tokenization, OCR, language detection, and image classification to organize files and power cleanup search. All processing runs locally on your Mac.
• Activity logs — Mint maintains logs of its operations (file moves, renames, organization actions) stored locally at ~/Library/Application Support/Mint/. These logs never leave your machine and exist solely so you can review and undo actions.

Privacy-Minimized Product Analytics

Mint can send a small set of first-party product milestones, subject to the edition-specific choices below, to help us find onboarding drop-off, confirm that releases reach active installations, and understand whether core work completes successfully. The fixed event list covers the first time Mint is opened, one activation per Mint release, weekly activity, later onboarding pages and completion, an onboarding page that could not do its job, the Full Disk Access prompt and grant, first-use milestones, free-limit blocks, the free cleanup allowance or the week’s free organizing running out, which way the plan page was opened (at launch, from a removal, from an organize run, from Auto Care, or from the plan strip), Auto Care pausing because a free weekly allowance ran out, upgrade-checkout clicks, whether signing in after a purchase found it (or a fixed reason it did not, such as no purchase found or a Mac limit), and each attempted disk cleanup, storage optimization, memory release, folder organization, app uninstall, file redaction, and undo of an earlier Mint operation. For those core operations, the only additional detail is a fixed feature, kind of operation, entry surface (such as the app, the first-run setup, the menu bar, or Auto Care), outcome (such as success, partial, failed, cancelled, blocked, or no change), fixed reason code, and a duration range (such as under 5 seconds or 30 seconds to 2 minutes). For the first scan during setup, Mint can also send the same kind of duration range together with how the scan ended, including whether it kept running after you left its page, and a size range for what the first storage optimization offered. From Mint 1.0.94, during setup Mint can also send which of its own buttons and controls were pressed on each setup page, as a fixed label (for example, the Disk page’s Optimize button), at most ten times per control each time Mint is opened, and, when a setup page stops responding, a fixed label for the area of Mint where it was stuck (for example, preparing the Disk results). When macOS records that Mint itself crashed, Mint can also send a fingerprint made only of the crash signal and the name of the Mint function or library involved. When one of Mint’s own consistency checks fails (for example, a result Mint showed did not match what is on disk), Mint can send the fixed name of that check, once per check per day; the values the check compared stay on your Mac.

Daily activity and presence in the Direct and Setapp editions. Direct versions that support daily activity reporting, and Setapp versions released after October 9, 2026, can also report that you opened or returned to Mint, at most once per calendar day in Pacific Time, while usage sharing is on. This helps us understand whether people return to Mint over time. A background launch alone does not count toward that signal. From versions released after October 9, 2026, both editions also send a presence signal, at most once per calendar day in Pacific Time, saying only that Mint was running on your Mac that day, whether or not you opened its window; it tells us how many installations are still in place. Both signals use the same anonymous installation identifier and event fields described below, include no new personal or file information, and stop when you turn off analytics sharing. Neither is sent by the App Store edition.

Standard usage events contain only a random installation identifier, a random event identifier used to make network retries idempotent, the UTC occurrence timestamp, the event name, an optional short allowlisted detail label (an onboarding step or fixed failure code, a core-operation feature/kind/surface/outcome/reason with a duration range, a crash fingerprint, or the fixed name of a failed consistency check), the Mint version and build, the distribution channel (Direct, Mac App Store, or Setapp), and the consent-schema version. Mint does not include scan results, file activity, filenames, file contents, paths, folder structure, document text, search terms, file counts or sizes, account details, hardware identifiers, advertising identifiers, undo history, or free-text error messages in these events. The analytics record does not store an IP address or user-agent string and is not linked to a Mint account, name, email address, purchase record, or Setapp account.

Task and performance summaries in the Direct and Setapp editions. While you share usage statistics, the Direct edition, and the Setapp edition from its first version released after September 28, 2026, also send task summaries; there is no separate choice for them. The Mac App Store edition does not send them. These summaries include random task identifiers, fixed operation, stage and file-type categories, counts of requested, distinct, successful, skipped, failed and cancelled items, aggregate byte totals, timings, cache hits, repeated visits and fixed refusal codes. They also include performance timings: how many times and for how long Mint’s window stopped responding on a given day, grouped by a fixed area of the app (such as the Disk drawer), how long stopping a scan took, and how long preparing a scan’s results took. From Mint versions released after October 6, 2026, they also include numbers macOS itself measures about Mint through Apple’s MetricKit: how often and for how long Mint stopped responding each day, how long it took to draw its first window, the processor time it used and the data it wrote, and how many hang, processor, disk-write and crash reports macOS made about it. The reports themselves, which contain Mint’s call stacks, stay on your Mac. They help us measure reliability and efficiency. They never contain personal data, filenames, paths, contents, conversation titles, names of Mint’s own code, or free-text errors. Summaries recorded locally before you turned sharing on are not uploaded. Turn usage statistics off to stop transmission. These summaries use the same retention and access protections as other optional analytics. Bounded task summaries are also kept locally for diagnostics.

Access and system context in the Direct and Setapp editions (from Mint versions released after October 9, 2026). While you share usage statistics, these two editions also report, at most once a day for each value, how this copy of Mint is allowed to run and the Mac it runs on. In the Direct edition that is your plan type (free, subscription, rent to own or lifetime) and, on the free tier, how much of the free cleanup allowance is used, in coarse steps, and in the same way how much of this week’s 50 free files of organizing is used. In the Setapp edition it is what the Setapp Framework says about your access: a Setapp membership or a single-app purchase, whether the license is active, how long until it expires in coarse steps, the version of the Setapp app and whether a newer Mint is waiting for you. Both editions also report where this copy runs from (the Setapp folder, Applications or elsewhere), whether it carries Mint’s own code signature, which kind of app macOS recorded as having downloaded it (Setapp, a web browser, another app, or none) but never that app’s name, and the first language and the region chosen in your Mac’s settings, as standard two-letter codes. From Mint versions released after October 11, 2026, both editions also report whether Mint is set to open when you log in, and how Mint’s previous run ended, as one fixed label: quit by you, quit by another app or a script, ended by logout, restart or shutdown, relaunched for an update, or ended without a clean exit (for example a force quit or a crash). This tells us how people get Mint, which plans they use, whether copies run outside the store they came from, and which languages to support. It never includes your Setapp or Mint account, email address, purchase or order identifiers, network location, or any file information. The Mac App Store edition does not send it. Turn usage statistics off to stop it.

App-opened signal (from Direct 1.0.76 and Setapp 1.0.36). The first time you open the Direct or Setapp edition, before the Welcome page, Mint creates a random installation identifier and reports that Mint was opened and which app version, build and distribution channel is running; afterwards it reports each new version once. This tells us whether a downloaded copy of Mint was ever opened. It carries nothing else.

Setup signal (from Mint 1.0.25). Once you press Get Started on the Welcome page of the Direct or Setapp edition — the line under that button states that continuing means agreeing to the Terms of Use and acknowledging this Privacy Policy, which describes the anonymous usage data Mint sends — and as you move through first-run setup, Mint reports a small setup signal to Mint’s first-party analytics endpoint: that Mint was installed, which app version and build is running, which setup pages were reached, a fixed failure code if a setup page could not do its job, and whether setup was completed. Each of these records carries only the random installation identifier, the event name, the allowlisted step label, the UTC day, and the app version, build and distribution channel — never file names, paths, contents, your name, email, or network address beyond what any HTTPS request carries in transit. If you answer the optional question “How did you hear about Mint?” on the last setup page, in any edition, your answer is sent once, together with setup completion and only when completion itself is sent, as one fixed label from the options shown or, if you choose Somewhere else, the few words you type there (letters, numbers, spaces and basic punctuation only, lowercased, at most 48 characters; the one place Mint sends anything you typed); skipping it sends nothing. The app-opened and setup signals continue if you turn usage sharing off; they are how we know whether Mint could be opened, installed and set up at all.

Usage data in the Direct and Setapp editions (from Direct 1.0.76 and Setapp 1.0.36). After you press Get Started, these two editions also send the usage events described above — which features are used for the first time, whether operations finish, crash fingerprints, activity, task and performance summaries (in the Setapp edition from its first version released after September 28, 2026), and access and system context (from Mint versions released after October 9, 2026) — by default, without a separate question. If you installed an earlier version and acknowledged the earlier policy without making a choice, Mint asks you once, with sharing preselected, before this default applies; until you continue, nothing beyond the app-opened and setup signals is sent. A choice you made earlier is kept. In earlier versions these usage events were off until you chose to share them.

Mac App Store choice. In App Store versions that offer usage sharing, no Mint product event is collected or sent, and no analytics installation identifier is created, until you explicitly enable the optional choice on the final onboarding page or in Settings. If you enable it before entering Mint, setup completion can be reported. Earlier setup activity is not recorded for later upload. Declining sharing does not prevent setup or use of Mint. Earlier App Store versions without this choice do not send Mint product analytics.

You can turn usage sharing off at any time under Account > Share my usage statistics (open Mint’s menu and choose Account) without losing product functionality. Turning it off stops future usage events and clears usage events still waiting locally for delivery; in the Direct and Setapp editions it does not disable the disclosed app-opened and setup signals. In the Mac App Store edition, turning sharing off stops all Mint product analytics and clears every event still waiting locally for delivery. Events already sent are stored only for the retention period below, and network retries use the same event identifier so one event is not recorded twice.

Server event records expire after at most 120 days. An undelivered local event also expires after 120 days. When the endpoint refuses an upload it cannot accept, for example a category sent by a newer version of Mint that it does not know yet, it keeps a record of why: a fixed reason code, the event name if it is one Mint sends, the first characters of the random installation identifier, the app version, build and distribution channel, and the date. The refused value itself is never stored. These records also expire after 120 days. The endpoint runs on Cloudflare’s global network and Workers KV storage is not restricted to a single country or region. Where European data-protection law applies to a restricted international transfer, Cloudflare’s Data Processing Addendum provides the applicable transfer safeguards, including the EU Standard Contractual Clauses.

Mint does not include advertising, cross-app tracking, or a general-purpose crash-reporting service. Mint checks locally for macOS crash reports and can show a post-crash prompt in every edition. The automatic privacy-minimized crash fingerprint is sent only while usage sharing is on; a full, redacted diagnostic bundle leaves the Mac only when you choose to send feedback with “Include diagnostics” ticked; untick it and only your message, Mint’s version and basic facts about the Mac (macOS version, processor, memory, disk size and free space, language and time zone) are sent. If you type an email address in the feedback form, we receive it with your message and use it only to reply to you. Direct-edition update checks remain available whether or not you share analytics; Mint serves the appcast without deriving or storing an installation identifier from the request IP address or user-agent string. Setapp may separately process limited technical information through the Setapp Framework for licensing, distribution, reliability, and developer reporting under Setapp’s own privacy notice.

Network Communication

Mint never uploads your files, filenames, folder structure, document text, or activity and undo history. Network communication is limited to the disclosed product-analytics, update, purchase, entitlement, support, and distribution flows:

• Direct website edition — Mint sends the app-opened signal from the first launch and the setup signal after the Welcome acknowledgement; while usage sharing is on (the default from Direct 1.0.76 and Setapp 1.0.36, or after you opted in to an earlier version), it also sends the other privacy-minimized product milestones described above. It also checks the signed Sparkle update feed for new releases. Mint Free does not require an account. If you sign in to unlock or restore Unlimited, your browser securely authenticates with our Cloudflare-hosted Mint account service. The app stores OAuth tokens, a random device identifier, and your verified account email in the macOS Keychain, then sends the token, random device identifier, device display name, Mint version, and release date over HTTPS to check entitlement and enforce the number of Macs your purchase covers (one to five for a one-time purchase, one for Rent to Own). No file information is included in entitlement requests.
• Mac App Store edition — Monthly subscriptions, one-time Lifetime purchases, and restores are handled through Apple StoreKit. Apple processes payment information; Mint receives entitlement status needed to unlock the purchased access. Only after you separately opt in, Mint may also send the privacy-minimized product milestones described above while sharing remains enabled.
• Setapp edition — Mint sends the app-opened signal from the first launch and the setup signal after the Welcome acknowledgement to Mint’s first-party endpoint; while usage sharing is on (the default from Direct 1.0.76 and Setapp 1.0.36, or after you opted in to an earlier version), it also sends the other privacy-minimized product milestones. Mint also communicates with Setapp through the Setapp Framework to verify entitlement, support licensing and updates, and provide the technical usage, performance, and device information described in Setapp’s documentation. From Mint versions released after October 9, 2026, while usage sharing is on, Mint reports to its own endpoint what the framework says about your access, as fixed labels described above. Mint does not send Setapp your file contents, filenames, folder structure, or Mint activity and undo history.
• Account or entitlement validation may occur at app launch and periodically thereafter to confirm paid access.

If you use the free tier outside Setapp without activating or restoring Unlimited, Mint does not need to contact our licensing infrastructure. Beyond the app-opened and setup signals, product analytics follow the usage-sharing setting: on by default from Direct 1.0.76 and Setapp 1.0.36, off until you choose in the Mac App Store edition, and controllable at any time under Account. The Setapp edition communicates with Setapp as described above.

Your Files Are Never Uploaded

To be unambiguous: Mint does not upload, copy, sync, or transmit your files or any file contents to any server, cloud service, or third party. All file operations are strictly local. Your documents, images, videos, and all other files remain on your Mac at all times.

Website Analytics

The Mint website measures visits, download requests and checkout activity to understand how people discover Mint and return to it. It also records how far a page was read or scrolled: which fixed sections of the homepage came into view, how far down an article was read, and how much of the homepage film played, in fixed steps of 25%. These records contain no text you type. Where website analytics is allowed, a random first-party browser cookie connects visits from the same browser profile across sessions. This is a pseudonymous browser identifier, not a verified identity. We do not use it to track your browsing on unrelated websites.

Browser journey records include public page paths, event times, normalized referral and campaign labels, approximate country, city and region inferred from the network connection, and the checkout session used to associate a verified Direct purchase. Event and session history is kept for up to 90 days; the browser profile and first-observed date expire after 90 days of inactivity. The cookie expires after 90 days without renewal. EEA, UK and Swiss visitors must explicitly allow persistent website analytics. Do Not Track and Global Privacy Control prevent browser journey collection. You can allow analytics or turn it off and delete this browser’s first-party journey history through Website privacy in the footer. A separate preference cookie remembers your choice. Clearing browser cookies or using a different browser can prevent recognition.

Website-to-app visit linking is no longer offered. Mint does not create new installation connections or use app links to connect another browser. Previously collected connection records remain subject to the 90-day retention policy. Website privacy controls can still turn off analytics and delete this browser’s first-party visit history; this does not delete legally required purchase records.

We also use Google Analytics 4 for website and checkout reporting. When analytics storage is allowed, Google’s browser Client ID may be retained with the first-party browser profile so our private dashboard can relate the two website reports. We do not send your name, email address or native anonymous telemetry identifier to Google Analytics. Consent defaults deny analytics storage in the EEA, UK and Switzerland; denied storage may still allow Google’s cookieless measurement pings. Website privacy choices update Google’s analytics consent for the Mint website. Google Analytics and payment-provider records follow their own retention settings; forgetting first-party browser history does not erase those separate records.

The website also takes part in DZG Studio’s public Planet map. Unless your browser sends Do Not Track, an open tab sends a short-lived random tab identifier, the product name, and an approximate city or region to The Planet. The map can show an anonymous Mint visit or download start from that area. It never receives a name, email address, order amount, file information, or stable user identifier. Live visits expire after about 90 seconds without a heartbeat. Older activity is kept only as a coarse product and location summary for up to 30 days.

For each browser-tab session, the site stores a random session identifier and first-touch attribution in sessionStorage. A new analytics session begins after 30 minutes of inactivity, and closing the tab also removes the stored session. The stored attribution is limited to the landing path, referral hostname, traffic channel, browser language, selected website interface language, and the utm_source, utm_medium, and utm_campaign labels when present. When the download page requests the Direct DMG, the event also includes the public Mint version and build that the request targets. A download-start event does not establish that the transfer completed or that Mint was installed.

If you continue from the website to the Direct-edition checkout, the random session identifier and the same normalized source, medium, channel, and campaign labels are sent to LemonSqueezy as custom checkout data. LemonSqueezy returns those labels with signed order and subscription webhooks. This lets us connect an aggregate acquisition source to a real payment or refund. We do not send a referral URL, IP address, file information, name, or email address as checkout attribution data, and our measurement tables do not copy the customer name, email address, street address, or payment credentials from the webhook. For regional reporting, we may separately retain only the country, state or region, and city supplied by our payment provider for orders from the last 90 days. These locations are not linked to anonymous in-app usage records. The in-app records can include the region chosen in your Mac’s settings, as described above; that is a setting, not your network location or your payment address.

When you open checkout from the Pricing page, LemonSqueezy’s checkout opens over our page, and the page records the steps it reports: that it appeared and how long that took, the plan, price, currency and language it showed, whether a discount code was applied, whether Pay was pressed, and whether the payment completed or you closed it. If you leave checkout without paying, our server reads LemonSqueezy’s record of that checkout once and keeps only whether an email address and a billing address were entered and how many payment attempts were made. It never keeps the email address, the address, card details or the checkout’s identifier. These records carry the tab session identifier, never a name or email address, and are kept for up to 90 days like the other website events.

Short links on the Mint website (addresses that start with /r/, such as the links in our posts on other sites) count each click on our server before they forward you. A click record holds the link, the time, the approximate country, whether the request looked automated, the hostname of the page the click came from and, when that page is one of our Medium stories, the story’s public ID. It holds no cookie, IP address or browser details, and it is deleted after 90 days.

The Mint analytics endpoint retains privacy-minimized website event records for up to 90 days. Direct-edition activation event rows are retained for up to 400 days; older checkout session identifiers are removed from order records after 400 days. Non-personal order totals, refund totals, product identifiers, and keyed account or purchase hashes may be retained for accounting, fraud prevention, entitlement administration, and historical aggregate reporting. For website visits and download starts, we may retain the approximate city and state or region inferred from the network connection for up to 90 days. This is not GPS or a street address, and a VPN can affect the location. Mint’s internal analytics records do not store IP addresses, precise location coordinates, user-agent strings, full referral URLs, arbitrary URL query parameters, or information about files used in the Mint app. The separate Planet summary follows the shorter retention described above.

Contact Form

If you use the contact form on our website, we collect the information you voluntarily provide: your name, email address, and message. This data is processed by a Cloudflare Worker and used solely to respond to your inquiry. We do not attach an IP address, IP hash, or user-agent string to the saved message. To prevent automated abuse, a one-way IP hash is used only in a separate short-lived rate-limit record; scheduled cleanup removes those records after the rate-limit window. We do not sell, share, or use contact information for marketing purposes. Contact form submissions are retained only as long as necessary to address your request.

Product Updates

If you subscribe to Mint product updates, we store the email address you provide together with Mint as the selected product, the website language, signup source, and the time of consent. We use this information to send a welcome email, practical Mac tips, Mint product news, and occasional subscriber offers. For article signups, we also save the public article path so we can recommend a relevant guide. Every email includes an unsubscribe link. Unsubscribing stops these updates; a minimal suppression record is kept to honor that choice. You can ask us to delete your address by emailing dev@dzgapp.com. We do not sell this information or combine your email address with product analytics, purchase attribution, or contact-form messages. Separate one-way network hashes limit abuse and expire after 24 hours. Email delivery records track welcome-email status without storing your address in those records. We do not use email tracking pixels. Asking for a one-time link to continue on your Mac does not subscribe you to these updates.

If you request a Windows version, we separately save your email address, website language, the form you used, the time of your request, and your consent to receive Windows updates. We use these requests to help prioritize development and to email you about Windows progress. This does not subscribe you to our general newsletter. Repeat requests from the same email address count once. You can ask us to remove your request at any time by emailing dev@dzgapp.com. We keep the request until you ask us to remove it. The saved request does not include an IP address or an analytics identifier, and your email is never sent to Google Analytics. To limit automated submissions, we use a separate one-way network hash that expires after one hour.

Download Link by Email

If you ask for the download link on a phone, our Cloudflare account service uses your email address once to send that one email and does not keep it. The address is not saved in any database, key-value store, or log, and our website analytics and Google Analytics record only that the form was sent. To limit abuse, we keep a keyed one-way hash of the address for 24 hours, so an address receives at most one email a day, and a keyed one-way hash of your network address for one hour. Both are deleted when they expire.

Data Storage and Retention

Mint keeps file contents, filenames, paths, workflow history, and learned organization preferences locally on your Mac. The limited service records described below are stored only when the corresponding network feature is used:

• Application preferences — Stored in macOS user defaults.
• Activity logs and undo history — Stored in ~/Library/Application Support/Mint/.
• Mint account and entitlement — Our Cloudflare database stores the verified email and account records needed for sign-in, keyed one-way hashes used to match Lemon Squeezy purchase emails, paid status, and connected-device records. The app stores OAuth tokens, the random device identifier, and verified email in the macOS Keychain. Mac App Store entitlement state is managed through Apple StoreKit; Setapp entitlement state is managed through Setapp.
• Direct versions with a free trial — Trial-based Direct releases keep the date their free trial started in the Mac’s Keychain. After you accept the Terms in Mint, a Mac without a purchase that is online also sends a one-way hash derived from its hardware identifier, that start date, and the app version, at most every six hours, so reinstalling does not restart the trial. Our Cloudflare database stores only a keyed hash of that value, the earliest start date, the first and latest check-in times, the app version, and a check-in count, and deletes the record 400 days after its latest check-in. It is not linked to an email address, account, purchase, or analytics record.
• Direct purchase and activation measurement — Our Cloudflare database stores the privacy-minimized order, refund, source attribution, and keyed-hash records described above. It never stores your files, file paths, or payment credentials.
• Direct and Setapp product analytics — Our Cloudflare key-value store retains the random-install milestone records described above for no more than 120 days. These records are not joined to customer, payment, license, Apple, or Setapp account data.
• Website product updates — Our first-party support store retains the subscribed email address and consent details until you ask us to remove them.

You can delete Mint’s locally stored data at any time by removing the application and its associated support files. Uninstalling Mint removes the local random analytics identifier; previously received privacy-minimized events expire automatically within the retention period. Because product-analytics records are deliberately not linked to a name, email address, Mint account, purchase, or Setapp account, we ordinarily cannot identify a particular person’s records from a personal-data request. You can contact us with a privacy request using the details below, and we will delete any record we can reliably identify without exposing another installation’s data.

Third-Party Services

• LemonSqueezy — Handles Direct-edition payments, receipts, subscriptions, cancellations, and refunds. When you purchase Mint, LemonSqueezy processes your payment information according to their privacy policy. Mint itself never sees or stores your payment details. Signed webhooks include the purchase email; our entitlement record stores a keyed one-way hash of that address so a later verified Mint sign-in can claim the purchase.
• Apple — Handles Monthly subscriptions, Lifetime purchases, restores, refunds, and StoreKit entitlement status for the Mac App Store edition. Mint itself never sees or stores your App Store payment details.
• Setapp — Handles distribution, licensing, payments, applicable taxes, entitlement validation, updates, and first-line billing and licensing support for the Setapp edition. The Setapp Framework may collect limited usage, performance, and device information from users who activate Mint through Setapp. Setapp processes this information according to its privacy notice.
• Cloudflare — Hosts the Mint account and entitlement service, D1 account database, sign-in and download-link email delivery, product-analytics endpoint, key-value storage, and website on its global network. Subject to Cloudflare’s privacy policy.
• Optional sign-in providers — If you choose a displayed Google, Apple, or X sign-in option, that provider authenticates you and shares the account information required to create or access your Mint account, including a verified email when available. You can always use Mint’s emailed one-time code instead.

Children’s Privacy

Mint does not knowingly collect personal information from children under 13. The desktop product analytics described above are not linked to a name, email address, account, purchase, or age, and Mint never includes file information in those events. Distribution platforms may separately process limited account, entitlement, usage, performance, and device information under their own privacy policies. If you believe a child has submitted personal information through our contact form or another support channel, please reach out so we can delete it.

Changes to This Policy

We may update this privacy policy from time to time. If we make significant changes, we will update the “Last updated” date at the top of this page. If an analytics change requires a new acknowledgement or consent, Mint will ask before collecting under the changed purpose; continued use alone is not treated as agreement to that changed purpose.

Contact Us

If you have any questions about this privacy policy or Mint’s data practices, email us at dev@dzgapp.com or use the contact form on our website.