Privacy Policy

ModulTone is a trade name of Ivo.j music, a sole proprietorship registered with the Dutch Chamber of Commerce (KVK) under number 96501305, at Veldenseweg 56, 5914 ST Venlo, the Netherlands. We decide what happens to the personal data this site collects. For anything in this policy, email info@modultone.com.

That makes us the controller of the personal data described here.

This site shows no ads. Tracking cookies are only set if you agree to them: for Google Analytics and for PostHog's statistics with cookies and recordings, and for the Meta pixel, each in the cookie banner (section 10), and for Google's review question after a purchase (section 3). Without that, we still count visits with PostHog, without cookies and without storing your IP address (section 10). Everything your browser loads comes from modultone.com, fonts included, except Paddle's checkout, and Google's review question, Google Analytics, Google Ads' measurement and the Meta pixel if you agree to them (sections 3 and 10). We collect an email address when you buy, sign in, download MS Widener, ask for a trial or join the newsletter. We use it for that, and when you buy, redeem a KVR code, sign in, ask for MS Widener or a trial, or join the newsletter, also for our mailing list about new plugins and sales. We never sell or rent it to anyone.

Checkout runs on Paddle's own checkout, which opens over this site. Paddle.com, our online reseller, is the merchant of record: it takes the payment and handles VAT, invoicing and fraud checks, and it's the controller of the payment data it collects, under its own privacy policy (paddle.com/legal/privacy). Your card details go to Paddle and never reach us. Orders placed before our checkout moved to Paddle went through Stripe's payment page, with Stripe in that same role under its own privacy policy.

From Paddle, or from Stripe for orders placed before the move, we receive your email address, your country, what you bought and an order number. In their dashboards we can also see the name and address details you entered. We store your email address, the order number, the order date, the plugins in the order and the amount you paid, so we can email your licence keys, show your purchases when you sign in to your account, and work out what the rest of a bundle costs you. Each licence key contains your email address, the plugin and the date.

If you bought through KVR Marketplace, KVR took the payment under its own privacy policy and gave you a code; it doesn't tell us who you are. When you redeem the code in your account, we store the code, the address you're signed in with and the date, and add the plugins to your account the same way as a purchase here, with licence keys made the same way.

We need this to deliver what you paid for (the contract between us). We keep it for as long as your licence exists, because that's what lets you download the plugin again and get your keys back. You can ask us to delete it. After that we can no longer resend your keys or show the purchase in your account, but plugins you've already activated keep working.

Buying a plugin on this site also puts your address on our mailing list about new plugins and sales (section 7). This is in our legitimate interest in telling customers about our other plugins. Every email has an unsubscribe link, and you can also email us, before or after you buy, to be left off. Redeeming a KVR Marketplace code puts you on it too, the same way.

A few days after a purchase we send you one email with what the rest of our bundle would cost you, if you own part of it and haven't unsubscribed. For that we store your email address and the date it's due. It's one of the list's emails, with the same unsubscribe link.

After a purchase, the thanks page asks whether Google may email you a short survey about your order (Google Customer Reviews). Nothing from Google loads unless you press Yes. Then the page loads Google's script and passes Google the order number, your email address, your country and the delivery date, which is the day of the order, and Google asks you once more in its own window. If you agree there, Google emails you the survey and uses your answers for our rating on Google; if you don't, it sends you nothing. Google handles this under its own privacy policy (policies.google.com/privacy), and its window is a frame from google.com, where Google's own cookies apply. The legal basis is your consent, given with that Yes.

The first time you activate a plugin on a computer, it sends us your licence key, an identifier the plugin creates for that computer, and the computer's name. We store the identifier, the name and the date, to hold a licence to three machines and to show you which machines are using it.

This is part of the contract, and in our legitimate interest in keeping a licence to three machines. The record stays until you free the machine in your account or ask us to delete it.

From version 1.1, the plugins also read a public list on modultone.com. When you open a plugin's window, at most once a day for all our plugins on that computer together, it downloads the version numbers of our plugins and the fingerprints of withdrawn licences (a licence ends with a refund, or for a breach such as a shared key; see the Terms). It sends nothing with that request: no licence key, email address, computer identifier or settings. The plugin compares its own key with the list on your computer. Like any download, the request reaches our host Netlify with your IP address and the usual details of a request (section 9).

Without a connection nothing changes: the plugin keeps the list it last had, and a licence that was never withdrawn keeps working offline for good. The gear next to the version number turns update notices off for all our plugins on that computer; a plugin with a licence still reads the list once a day, because the same list carries withdrawn licences. When a newer version is out, the plugin says so. If you click Update, it downloads the installer from modultone.com, checks that we signed it, and opens it for you to run. We do this under the contract (the licence terms) and in our legitimate interest, and yours, in licences that hold and in you hearing about fixes and new versions. Apart from the activation, this list and an update you start yourself, the plugins don't contact us.

You sign in with a link we email you. To stop anyone flooding an inbox with those links, we count how many were sent to an address in the last hour, stored as a hash of the address rather than the address itself.

Under its button, the sign-in form says you'll also get the occasional email about new plugins and sales. When you ask for a sign-in link, your address joins our mailing list (section 7). This is in our legitimate interest in telling people who use our plugins about new ones, and every email has an unsubscribe link.

Once you're signed in, the site sets one cookie, modultone_account, which keeps you signed in for up to 30 days or until you sign out. It's needed for the account to work at all, so it doesn't ask for consent, and it isn't used for anything else.

MS Widener is free in exchange for your email address. We use it to send you a confirmation link and then the download. The service that sends our email keeps a record of the messages it delivered for a limited time. To stop anyone flooding an inbox through this form, we count the requests per address and per IP address in each hour, stored as a hash of each rather than the address itself.

Under the button, the form says you'll also get the occasional email about new plugins and sales. When you send the form, your address joins our mailing list (section 7). This is in our legitimate interest in telling people who ask for our plugins about new ones. Every email has an unsubscribe link, which also takes your address off if someone else typed it in.

Where a plugin page offers a 7-day trial, asking for one works the same way: you give your email address, we send a confirmation link, and the download comes from that link. When you download, we email you a trial key. Like a licence key, it contains your email address and the plugin, and also the date the trial ends. The plugin checks that date itself, without an internet connection, so a trial never sends us your computer's identifier or name.

To give each address one trial per plugin, we keep a record of when its trial started and when it ends, so asking again from the same address gets the same end date. It's stored under a hash of your address and the plugin rather than the address itself. We keep it for as long as we offer trials, and you can ask us to delete it. The same hourly count as for MS Widener applies to this form.

Under the button, the trial form says you'll also get the occasional email about new plugins and sales. When you send the form, your address joins our mailing list (section 7), the same way as for MS Widener. That is in our legitimate interest in telling people who try our plugins about new ones, and every email has an unsubscribe link. We use your address for the trial itself because you asked for it (the contract between us), and the record that limits an address to one trial is in our legitimate interest in giving each person one trial.

We also send two emails about the trial itself: a few things to try three days in, and on its last day what happens next. They stop when you buy the plugin or unsubscribe, and someone who tries more than one plugin gets them for the first only.

Our mailing list is for news about new plugins and sales. Addresses on it are kept as contacts at Resend, which sends the emails. Every email has an unsubscribe link, and Resend remembers that you unsubscribed, so buying another plugin later doesn't sign you up again. We also keep our own record of when and how you joined, or that you asked not to, so we can show how an address got on the list. You can ask us to delete that record and your contact at any time.

The form at the bottom of each page says "Get an email about new plugins and sales", and that is what an address given there is for: it joins the mailing list above, with the same record and the same unsubscribe link. The legal basis is your consent, which you can withdraw at any time with that link or by emailing info@modultone.com.

We also see which links in our emails are clicked, per address. The links in every email we send, licence and sign-in emails included, go through links.modultone.com, run by Resend for us, which notes the click and sends you on to the page. We use it to see which emails are worth sending, in our legitimate interest in not sending things nobody reads. We don't track whether you open an email.

If you email us, we keep the conversation for as long as it takes to help you, and for up to two years after your last message, so a later question about the same licence doesn't start from nothing.

The site and its server functions run on Netlify. Like any web host, Netlify processes your IP address and the details of each request in order to serve the page, and keeps logs for a short time. Our own function logs record errors, with email addresses shortened so they can't be read in full. This is in our legitimate interest in keeping the site secure and working.

Netlify also adds a small script to every page that measures how fast it loads: which page, the type of browser and operating system, phone or computer, screen size and loading times, without cookies. Our site's security settings don't let that script send anything, so at the moment Netlify receives none of these measurements.

We count visits with PostHog, from PostHog Inc., which keeps this data in its EU data centre in Frankfurt, Germany. It sets no cookies and stores nothing in your browser. For each page view it receives the page address (without anything after the question mark, except campaign tags such as utm_source), the site you came from, your browser, operating system, type of device, screen size, language and time zone, and the country your IP address belongs to, which our host adds on the way. To count unique visitors per day, PostHog combines your IP address, your browser's identification string and our site's address with a random value that is replaced every day into a code that can't be turned back into any of them. It then deletes the IP address and that string, and the daily change means a visit today can't be linked to one tomorrow. PostHog keeps these counts for a year.

We also count these actions, without anything that identifies you: asking for MS Widener or a trial, downloading either, playing and comparing an audio demo (which plugin and clip), adding a plugin to the cart, going on to checkout, and completing a purchase (with what it came to excluding VAT, and which plugins). We also count which links and buttons you click (their text and the address they lead to, never what you type into a field), clicks that do nothing and clicks repeated in quick succession, how long a page takes to load and respond, errors in the page's scripts, and when you leave a page, how far down you scrolled and how long it was open. Clicks aren't counted on your account page or the thanks page. The two downloads are counted by our server, with your IP address and browser details, so they can get the same daily code as your visit. The counting script is part of our site, and these counts pass through modultone.com on their way to PostHog. This is in our legitimate interest in knowing how many people visit and what brings them here. A content blocker that stops it doesn't break anything on the site.

If you allow Statistics in the cookie banner, PostHog also sets two cookies whose names start with ph_ and keeps the same random identifier in your browser's local and session storage, so it recognises your browser on later visits instead of counting a new visitor every day. With it, PostHog makes heatmaps of where on a page people click, move and scroll, and recordings of visits: what the page showed and how you moved through it, with everything you type into a field hidden. Your account page and the thanks page are never recorded. PostHog doesn't store your IP address in this case either, keeps recordings for 30 days and the rest for a year. The legal basis is your consent; until you give it, PostHog works without cookies as described above. Withdrawing it under Cookie settings, or a choice that lapses after a year, deletes PostHog's cookie and what it kept in your browser.

If you allow Statistics in the cookie banner, we also use Google Analytics, from Google Ireland Limited. It sets cookies in your browser (_ga and _ga_1EHFZ9B1VF, which last thirteen months from your first visit and aren't extended by later ones) to recognise it across visits, and, if you also allow Ad measurement, after a click on one of our Google ads _gcl_aw (90 days), which links that click to a later purchase. For each page view it receives the page address, the site you came from, your browser, device and approximate location, and how you use the page: scrolling, clicks on links to other sites, file downloads, form submissions, which plugins you look at and put in the cart, which audio demo clips you play and compare, and that you asked for MS Widener or a trial. When you buy something, it also receives the order number, the products and the amount. Google Analytics doesn't store IP addresses. If you also allow Ad measurement, your visit counts in what our linked Google Ads and Merchant Center accounts show about which Google ads and Shopping listings lead to a purchase. For that, the Google Ads tag also runs: it sets _gcl_au (90 days) and tells our Google Ads account which pages you visit, so a click on one of our Google ads can be linked to a later request for MS Widener or a purchase. Google can also use its own cookies on doubleclick.net for this. If you type your email address into one of our forms (MS Widener, a trial, the newsletter or signing in), Google's tag also sends it to Google, but only as a one-way hash (SHA-256), so Google can match a sign-up or purchase to an ad click made while signed in to a Google account. None of it is used to personalise ads, and Google signals is off. It also sorts visits into groups for our statistics, such as people who asked for MS Widener or put a plugin in the cart without buying; those groups aren't used for advertising either. Google keeps this data for fourteen months after it was collected, so we can compare a month with the same month a year earlier, and then deletes it; later visits don't extend that. What stays in the reports after that are totals, which can't be traced back to you.

The legal basis is your consent, which you give per purpose: Statistics, and Ad measurement on top of it. Both are off until you switch them on. If you press Reject all, or don't answer, nothing from Google Analytics or Google Ads loads. You can change your choices at any time under Cookie settings at the bottom of every page; withdrawing one deletes its cookies. Google processes this data for us under its data processing terms. It can be transferred to the United States, under the EU–US Data Privacy Framework.

If you allow Instagram and Facebook ads in the cookie banner, we also use the Meta pixel, from Meta Platforms Ireland Limited. It sets cookies in your browser: _fbp, which recognises your browser for 90 days, and, after a click on one of our Instagram or Facebook ads, _fbc (90 days). It receives the page address, the site you came from, your IP address, browser and device, and these actions: which plugin pages you look at, adding a plugin to the cart, going on to checkout, asking for MS Widener or a trial (not your address), and a purchase with the order number, the products and the amount. Meta's automatic event collection is off, so the pixel doesn't read buttons or other content on the page, and we don't send Meta your email address or other customer details. We use it to see which of our Instagram and Facebook ads lead to a signup or a purchase, to let Meta show those ads to people likely to buy, and to show our ads on Instagram and Facebook to people who visited this site. Meta can link this to your Instagram or Facebook account if you have one, and also uses it for its own purposes under its own privacy policy (facebook.com/privacy/policy).

For collecting this data on our site and passing it to Meta, we and Meta Platforms Ireland Limited (Merrion Road, Dublin 4, D04 X2K5, Ireland) are joint controllers, under Meta's Controller Addendum (facebook.com/legal/controller_addendum). Under that arrangement we are responsible for asking your consent and for this information, and Meta for what it does with the data once it has received it, including answering requests about the data it holds; Meta's privacy policy (facebook.com/privacy/policy) explains how to reach Meta and its data protection officer. You can exercise your rights with either of us, and we pass on to Meta whatever concerns Meta. Meta keeps the data for as long as its privacy policy describes. From Meta we only receive aggregated reports about our ads, never data about you as a person. The legal basis is your consent, asked separately from Statistics and off until you switch it on. You can withdraw it at any time under Cookie settings, which deletes the _fbp and _fbc cookies, and you can manage how Meta uses data for ads in your Instagram or Facebook settings. Data can be transferred to the United States, under the EU–US Data Privacy Framework.

Besides the account cookie, the cart remembers what you put in it in your browser's local storage. It holds the ids of the products in it and nothing about you, and it stays in your browser until you press Pay.

When you open Paddle's checkout, the tab also keeps a short note in its session storage that a checkout was opened, so the thanks page can count the purchase once. It holds the kind of checkout, the number of items and the time, and once the payment has gone through, what it came to excluding VAT and which products, for the purchase count in PostHog. When the payment goes through, a second note holds the order number, your email address and your country, for Google's review question on the thanks page; it only reaches Google if you press Yes there (section 3). The thanks page removes both when it reads them, and your browser deletes them when you close the tab.

Your choices in the cookie banner are kept in local storage, with the date, so the banner doesn't ask on every page. It asks again after a year, or sooner if what it asks about changes. If you allowed Statistics, PostHog keeps its identifier in local and session storage and in cookies (section 10). If you allowed Statistics or Instagram and Facebook ads, a completed payment also leaves a note in session storage with the order number, the products and the amounts, which the thanks page passes to Google Analytics and the Meta pixel, each only if you allowed it, and then removes.

Netlify (hosting, server functions, data storage and forms), Resend (sending our email and keeping our mailing list) and PostHog (visitor statistics, section 10, kept in its EU data centre in Frankfurt) process data for us under data processing agreements. All three are based in the United States, so your data can be transferred outside the European Union, with the safeguards EU law requires for that, such as the European Commission's standard contractual clauses.

Google Ireland Limited (Google Analytics and Google Ads' measurement, section 10, only if you accept them) processes data for us under Google's data processing terms, and data can go to the United States under the EU–US Data Privacy Framework. Meta Platforms Ireland Limited (the Meta pixel, section 10, only if you allow it) is joint controller with us for collecting and passing on that data, and then uses it under its own responsibility; data can go to the United States under the EU–US Data Privacy Framework. When you visit our Instagram profile, Meta gives us aggregated statistics about those visits (Insights); for those, we and Meta are joint controllers under Meta's Page Insights Controller Addendum (facebook.com/legal/terms/page_controller_addendum), and Meta answers requests about them. Paddle processes payment data as the merchant of record, under its own responsibility and privacy policy, and Stripe did the same for orders placed before our checkout moved to Paddle. Google receives the details of an order for its review question (section 3), under its own privacy policy. Emails you send us are held by our email provider.

We keep your data behind access controls at our host, send it only over encrypted connections, and never hold card details.

You can ask to see the personal data we hold about you, to correct it, to delete it, to limit how we use it, to receive it in a portable format, and to object to processing based on our legitimate interest. Email info@modultone.com; we answer within one month.

If you think we handle your data wrongly, you can complain to the Dutch data protection authority, the Autoriteit Persoonsgegevens (autoriteitpersoonsgegevens.nl). We'd rather hear about it first, though.

When the site starts handling data differently, this page changes with it, and the date at the top shows when that last happened.