Privacy Policy

The short version: we collect what we need to sell you apps and make them work, and nothing else. No ads, no tracking cookies, no profiling, and we never sell your data.

Who is responsible

The controller of your personal data is Federico Infelici, a sole trader in Arezzo, Italy, VAT number IT02427350513, who runs Quits and publishes its apps.

For anything about your data, write to support@getquits.app with “Privacy” in the subject. We haven’t appointed a Data Protection Officer, because the law doesn’t require one for a business like ours.

What we collect, and why

The waitlist

• What: your email address, the date, the page you signed up from, your browser’s language and whether you ticked the box for the private beta.
• Why: to send you a single email when Quits opens. If you ticked the private beta box, we may also write to you once, in April 2027, to invite you to the beta. We don’t use it for anything else and we don’t share it.
• Legal basis: your consent (Article 6(1)(a) GDPR), which you can withdraw at any time.
• How long: until we send the launch email, then we delete it within 30 days. If you leave the list before then, you won’t get the email and we delete your address within 30 days.

The makers waitlist

• What: your email address, the name and web address of your app, and the date.
• Why: to contact you when Quits starts selling apps from independent makers.
• Legal basis: your consent, which you can withdraw at any time.
• How long: until we contact you about it, and no longer than 36 months after you sign up.

Your Account

• What: your sign-in email address, the name in your profile, any other email addresses you link, and when each one was confirmed. An Account can open before your first purchase. If you sign in with Apple, we receive an account ID, your email address (or an Apple relay address, if you choose to hide yours) and your name only if you choose to share it. If you sign in with Google, we receive an account ID, your verified email address, your name and your profile picture. Apple and Google also send the technical tokens that confirm the sign-in: we discard the ID token once the sign-in is checked, and store the access and refresh tokens encrypted, so we can ask Apple or Google to end the connection when you disconnect it or close your Account. We never get your Apple or Google password, or access to anything else in those accounts.
• Sign-in links and codes: the email contains a link and a 6-digit code. Each works once and expires after 10 minutes. We store hashes, rather than the link token or code itself, and allow at most 5 incorrect attempts per code. Opening a link first shows a confirmation button, so an email scanner cannot use it up just by visiting it.
• Sessions: while you’re signed in, we keep a session record with the IP address and browser type it started from. A session lasts up to 30 days and can renew while you use it. You can see and end active sign-ins in your Account. Signing out removes that session immediately; expired records are removed by daily cleanup.
• Security limits: we count requests to prevent sign-in guessing and email abuse. These short-lived counters use keyed hashes of email addresses, IP addresses or Account IDs, rather than storing those values in the counters. Daily cleanup removes expired counters. Legal basis: our legitimate interest in protecting Accounts (Article 6(1)(f) GDPR).
• Why: to give you your Library, let you sign in without a password, and activate your apps.
• Legal basis: the contract with you (Article 6(1)(b) GDPR).
• How long: as long as your Account exists, because your Licenses have no end date.

Orders and Licenses

• What we store: for each order, its number and date, the apps, their prices, the currency and total, the email used, when you gave the consent we ask for before payment, whether anything was refunded or the payment was disputed, and Stripe’s reference numbers for the payment. For each License, its keys, when they were issued and whether they were revoked.
• Payments in progress: you sign in before paying. When you start a payment we record it with your Account and its email, the cart and its prices, the currency and total, when you gave consent and Stripe’s reference for the payment page. This keeps the same payment from starting twice and makes sure a confirmed payment reaches your Library. A payment you don’t finish expires on its own, in about 30 minutes. We keep these records as long as your Account exists; if you close it, they lose your Account and its email.
• Refund requests: when you choose Refund in your Account, we record the request, its amount and its state at Stripe. Your License and its key change only when Stripe confirms the refund.
• Delivery emails: emails about purchases, refunds and new keys wait in a delivery queue. For up to 30 days we retry them until our email provider accepts them. Acceptance doesn’t guarantee arrival in your inbox; your Licenses remain available in your Library. A queued copy holds the recipient’s address and the details of the message, never a License key. We delete each copy, sent or not, 30 days after it was created.
• What Stripe shares with us: after checkout, Link (Stripe’s merchant of record, see below) shares the order details with us, as its terms explain: your name, email address, billing address, what you bought, the amounts and the type of payment method (for a card, its brand and last 4 digits). We can see these in our Stripe account, but we copy into our own database only what’s listed above. We never see your full card number.
• Why: to deliver your apps and updates, handle refunds, answer support and keep our accounts.
• Legal basis: the contract with you, and our legal obligations (Article 6(1)(c) GDPR) for accounting and tax.
• How long: as long as your Account exists. If you close it, we keep order records for up to 10 years where we need them for accounting and tax obligations (article 2220 of the Italian Civil Code) or to defend legal claims.

Your Macs

• What: a License counts 5 active Macs, so each app sends us a code for the Mac it runs on: a keyed hash (HMAC-SHA256) of the Mac’s hardware UUID, computed on your Mac. The UUID itself never leaves your Mac, and the code can’t be turned back into it. The code stays the same for every Quits app on that Mac and after you reinstall macOS, so we recognise the same Mac instead of counting it twice. Because it still identifies a Mac, we treat it as personal data. With it we store, for each key, when the Mac was first activated and when it last checked in.
• When the app contacts us: once when you activate it, then at most once a day when it’s online, sending only the License key and that code. As with any connection, our server sees your IP address, but we do not keep request access logs.
• Why: to honour the limit of 5 active Macs and to revoke a key automatically when a 6th Mac becomes active.
• Legal basis: the contract with you, and our legitimate interest in preventing misuse of Licenses (Article 6(1)(f) GDPR).
• How long: a Mac stops counting 90 days after its last check-in. We delete its record 12 months after its last check-in, or when you close your Account.

Revocation at the 6th Mac is automatic: no person decides it. It doesn’t take anything away from you, because your License gets a new key at once: choose “Activate again” in the app, and we email you to tell you. If you think it happened by mistake, write to us and a person will look at it.

Updates

Our apps check for updates with Sparkle, from getquits.app. An update check sends what any web request sends: your IP address, and the app’s name and version. Sparkle can also send a profile of your system (Mac model, macOS version and more): in our apps that option is turned off. Update files are downloaded from our file storage.

What the apps do on your Mac

The apps contain no analytics and no advertising code. Apart from activation, the License check and the update check described above, an app sends data only when a feature you use needs it, and its page on the Store says so.

The older versions of Tone and QuickMD on the Mac App Store don’t contact us for Licenses or updates: Apple handles their updates, under Apple’s privacy policy.

Support emails

• What: what you write to us, your email address, and what we need from your Account to help you.
• Why: to answer you.
• Legal basis: the contract with you, or our legitimate interest in answering people who aren’t customers yet.
• How long: 24 months after the last message of the conversation.

Visitor statistics

We count visits with Umami, which runs on our own server. It uses no cookies, doesn’t store IP addresses and doesn’t follow you across websites. It records the page, the site you came from, your browser, operating system, device type, screen size, language and country (worked out from the IP address, which is then discarded). We also count demo interactions, successful cart additions and checkout steps, collect page loading measurements, and keep campaign labels from links. We use these anonymous numbers to improve the Store. Legal basis: our legitimate interest in running the Store.

On the cart and sign-in page for checkout, we record only the step, whether sign-in is complete and a general error category. Email addresses, form contents, Account identifiers, License keys, access codes and private URL parameters are never sent to Umami. After a confirmed payment, the Store can send 1 purchase event with the apps, amount and currency. It verifies the purchase on our server first and removes the receipt identifier before sending the event. It does not record Library pageviews or activity. Account, activation and other private pages have no visitor statistics.

We respect your browser’s Do Not Track setting. You can also disable statistics on this browser using the control below. A temporary checkout progress flag, with no identifier, stays in this tab only until sign-in is completed or the tab is closed.

Server logs and backups

• Our Store and its proxy do not keep request access logs. Technical error logs help us troubleshoot failures; the application and its scheduled tasks replace email addresses with [email] before writing them. Each service keeps at most 3 log files of 10 MB, the oldest replaced as new ones fill, and they are removed when its container is recreated. Legal basis: our legitimate interest in keeping the Store secure.
• Our email provider, Brevo, keeps a delivery log for each email: sender and recipient addresses, subject, delivery results, and whether the email was opened and its links clicked. We have set it to delete these logs after 1 month and never to store a copy of the message. We use them to diagnose delivery failures, under our legitimate interest in operating the Store. They are not included in database backups.
• We back up the database every day to storage in the EU, and keep at most 30 backups, for up to 30 days.

Cookies and browser storage

The Store sets only the cookies it needs, so there is no cookie banner:

None of them is used to track you.

Our pages load fonts and scripts only from getquits.app, not from Google or other companies. The payment page is Stripe’s, on Stripe’s own website, and it uses Stripe’s cookies under Stripe’s privacy policy.

Who else sees your data

Our service providers, who handle data only on our instructions, under a data processing agreement:

We send Store emails through Brevo: sign-in links and codes, notices about purchases, new keys and refunds, and the launch email. To deliver a message, Brevo receives the recipient’s address, the subject and the content, over an encrypted connection, and the message is signed for getquits.app. Brevo adds a tracking pixel to each email and passes its links through its own addresses, so it records whether an email was opened and which links were clicked. Brevo doesn’t let us turn this off. We don’t use these records for anything, and they are deleted with the delivery logs after 1 month. The plain-text version of each email has the direct links. Your email provider receives the messages to deliver them to your inbox.

Companies that decide for themselves how to use your data, under their own privacy policies:

• Stripe. Sold through Link, LLC and the other Stripe companies take your payment, issue receipts and invoices, handle tax, refunds, disputes and fraud checks, and look after the Link account you may use at checkout. They are responsible for the data they collect at checkout: see Stripe’s privacy policy.
• Apple and Google, only if you choose to sign in with them.
• Public authorities, only when the law requires it.

We never sell your data or share it for advertising.

Transfers outside the EU

Stripe’s merchant of record is based in the United States, and Backblaze is a US company even though our data stays in its EU region. Brevo keeps our data in the EU; where it or its subcontractors process data elsewhere, the European Commission’s standard contractual clauses apply. Apple and Google may process sign-in data outside the EU under their privacy policies. Where data goes to the United States, the transfer relies on the EU-US Data Privacy Framework when the company is certified under it, and otherwise on the European Commission’s standard contractual clauses.

Your rights

You can ask us to:

• see the data we hold about you and get a copy of it;
• correct it;
• delete it;
• limit how we use it, or object to a use based on our legitimate interest;
• receive the data you gave us in a machine-readable format;
• stop using data based on your consent: withdrawing it doesn’t affect what we did before.

Write to support@getquits.app with “Privacy” in the subject. We reply within 1 month, and we may ask you to confirm the request from your Account’s email address so nobody else can make it for you.

Your Account lets you correct your name, choose which confirmed email address is your Account email, end sign-ins, download your data as JSON and close your Account. The download holds your profile with its picture, your confirmed addresses, active sign-ins, the Apple or Google account IDs you connected (never their tokens), orders, payments in progress, refund requests, Licenses, keys and the records of your Macs. Changing your Account email, adding an email address, disconnecting Apple or Google and closing your Account require a sign-in from the last 10 minutes.

Closing your Account deletes your profile, linked email addresses, sign-ins, Licenses, keys and the records of your Macs. It ends your Licenses, so the form asks you to type your email and confirm that consequence. While a payment of yours is in progress, closing waits until it is completed or expires, so a payment never arrives for an Account that is gone. We also ask Apple or Google to revoke connected sign-ins. If we can’t confirm that revocation, we still close your Account and show you how to remove the connection in your provider settings. Existing database backups expire within 30 days. We keep order records only as explained above, with their payment and refund records, without an association to the deleted Account. You can also ask us for help by email. For the data Stripe holds about your payments, ask Link at support.link.com.

If you think we’re handling your data unlawfully, you can complain to the Italian data protection authority, the Garante per la protezione dei dati personali, or to the authority of the EU country where you live or work.

Security

Every page and connection uses HTTPS. The database is not reachable from the internet, and only the people who need it can access our systems. Session cookies cannot be read by page scripts, private pages are not cached, and sensitive Account changes require a recent sign-in. License keys are signed with a private key that stays on our server, and your Mac’s hardware ID never reaches us.

Payment details are entered on Stripe’s hosted checkout. We grant Licenses only after Stripe confirms the payment to our server, through a signed notification or a direct check with Stripe, and we record each payment once, so a repeated confirmation cannot create another order or License.

Children

Quits is not meant for children under 14, and we don’t knowingly collect their data.

Changes to this policy

When we change this policy, the date at the top changes too. If a change affects how we use data you have already given us, we’ll tell you before it applies.