Privacy Policy
Effective
This page covers the eomics.com website, MFX for Mac, MFX Remote for iPhone and MFX Booth for Mac. It says what each one collects, where it goes and how to have it removed.
Who we are
eomics is the brand. The apps are developed and sold on Apple's stores by Netspedition. "We" and "us" on this page mean eomics and Netspedition.
Questions, or a request to see or delete your information: frontdesk@eomics.com.
The short version
- MFX Remote and MFX Booth collect nothing for us. They talk only to MFX on your own Mac.
- The website keeps what you type into its forms, with the time, your IP address and your browser's user agent. It uses Google Analytics.
- MFX for Mac (the beta) tells us a handful of setup milestones, under the email address on your license. Nothing about your music or your sets is sent.
- We email you from frontdesk@eomics.com. Reply "unsubscribe" and we stop.
- We don't sell your information.
The website (eomics.com)
Forms
Each form on the site sends what you type to our server:
- Private beta signup: your email and, if you fill it in, your setup (for example your Mac, Traktor version and controller).
- Contact form: your name, email and message.
- Community 26 ideas: your idea. Your email only if you tick "Notify me when the pack is available".
- Notify-me lists (for example, MFX Remote's App Store launch): your email.
With each submission our server also records when it arrived, your IP address and your browser's user agent (the string that names your browser and system). Your IP address also caps how many forms one address can send in an hour, which keeps out spam. Submissions that look like spam are dropped and not stored.
All of this is kept in our database on Fly.io, in its Toronto region. Contact form messages are also forwarded to our inbox at frontdesk@eomics.com.
Emails we send
When you use a form with your email, we send one confirmation email. Mail goes out from frontdesk@eomics.com through Zoho Mail, which also holds that inbox, so your replies are stored there.
If you signed up for the private beta, we may write to you personally about it: an invitation, a follow-up or two, and your download when you're in. We keep a record of each email we send you, with its text, and a note of how you replied, so we don't write twice or lose track. Every invitation tells you how to opt out.
Action packs
To get an MFX action pack you give your email. For a paid pack, payment is handled by Stripe on its own checkout page. We never see your card. We keep your email, the pack, the amount, the currency and Stripe's reference for the payment, and we get a notification email for each purchase.
The MFX pack installer signs you in with a 6-digit code emailed to you (no password). It tells our server, under your email, when it starts, how many packs it found, and which packs you install or remove. Each code request, sign-in and download is recorded with your IP address and user agent. Pack files are downloaded from Cloudflare R2.
Server logs and analytics
Like most web servers, ours logs each request: the page, the time, your IP address, your user agent and the page that linked you. Fly.io keeps these logs for about a week. We copy them to our own computer to see how much traffic the site gets and roughly where it comes from (to the city, using an offline lookup database; your address isn't sent anywhere to be looked up).
Most pages load Google Analytics, which counts visits and records things like the pages you view, your approximate location, and your device and browser. Google handles that data under its own privacy policy.
Cookies and content from other sites
We don't set cookies of our own. Google Analytics sets cookies to tell repeat visits from new ones. The demo video on the home page is embedded from YouTube, which may set its own cookies when it loads. Some pages load scripts from unpkg.com, a public code host, and the pack and action lists are loaded from Cloudflare R2. Like any web server, those see your IP address when your browser asks them for a file. You can block cookies in your browser; the site still works.
MFX for Mac
Your license
A beta copy of MFX runs on a license: a small .mfxlicense file with your email address, the day
it was issued and the day it ends, signed by us. MFX checks the signature on your Mac and keeps a copy in
~/.mfx/license.json. Checking it doesn't contact us.
Milestones
So we know how far each tester got and where people get stuck, MFX sends our server a note the first time each of these happens:
- MFX is launched (once per version),
- the license is added,
- Traktor is set up for MFX,
- the MFX mapping is installed,
- the first action is played.
Each note carries the email on your license, the MFX version and, for two of them, the Traktor version or the
mapping version. Our server records it with your IP address. Nothing else is sent: not your tracks, sets,
actions or settings. A note that can't be sent waits in ~/.mfx/milestones.json until the next launch.
Nothing else leaves your Mac
MFX has no crash reporting, no update check and no other analytics. Its logs stay on your Mac. Its window loads an icon font from Google Fonts, so Google sees that request.
While it runs, MFX answers on your local network so MFX Remote and MFX Booth can find it. A phone or Mac can control it only after you approve the pairing on the Mac running MFX. MFX keeps the paired device's name and a hashed key on that Mac.
MFX Remote for iPhone and MFX Booth for Mac
MFX Remote and MFX Booth control MFX on your own Mac over your local network. They don't collect any data for us, don't contact our servers and don't track you. There are no analytics or advertising tools in them.
When you pair, the app sends the Mac running MFX the device's name and an app-specific identifier (on iPhone, Apple's identifier for vendor; MFX Booth makes a random one), so the Mac can show you who's asking and recognize the device if it pairs again. That stays on your Mac. The pairing key is kept in your device's Keychain and the app's settings stay on the device.
Apple runs the App Store and TestFlight. If you test through TestFlight, Apple may pass us crash reports and any feedback you choose to send, under Apple's own privacy policy.
The private beta
When you're invited, you get a link to your own download, which holds the app, a guide and your license (with your email in it). The download is stored on Cloudflare R2 in a folder named by a scrambled form of your email, not the address itself. The link works for 7 days and the license for 90.
To decide who fits each wave of the beta, we sometimes note facts about applicants alongside their signup: things you tell us in your replies (such as your name, your setup or your language), things you've published about your DJ work that we find by searching the web (for example a SoundCloud, Facebook or Apple Music profile), and guesses drawn from these (such as a likely region). Ask us and we'll tell you what we have about you.
Who handles data for us
- Fly.io hosts the website and our server and database.
- Zoho Mail sends our email and holds the frontdesk@eomics.com inbox.
- Cloudflare R2 stores beta downloads, action packs and the pack lists.
- Stripe takes payments for paid packs.
- Google runs Google Analytics and serves the MFX icon font. YouTube serves the embedded video.
- Apple distributes the iPhone app through the App Store and TestFlight.
How long we keep it
We don't delete signups, messages or the records described above on a schedule. They stay until you ask us to remove them, or we do. Fly.io keeps server logs for about a week; our copy of them stays on our computer. A beta download stays in storage after its link stops working, until we remove it.
Your choices
- Stop our emails: reply "unsubscribe" to any of them. We take you off and don't write again.
- See or delete your information: email frontdesk@eomics.com from the address you used, and we'll tell you what we hold or remove it.
- Milestones: MFX sends them only while it has a valid beta license, and the beta needs one to run. To have the ones already sent removed, email us.
- Cookies: block or clear them in your browser.
Changes
When we change what we collect, we update this page and its date.