What leaves your Mac
Parallex runs on your Mac and keeps your instances, their data and your settings there. This page lists everything it sends anywhere. It's short.
From October 31, 2026, Parallex is free to use, Pro included, until further notice. To know that it still is, Parallex asks this site every few hours, sending nothing but its name and version. What follows about licenses, trials and accounts applies to Macs with a license bought before then.
On this page
The update check
Every few hours while it runs, when your Mac wakes up, and whenever you choose Check for Updates, Parallex asks parallex.mandip.dev whether there's a new version. The request says six things:
X-Parallex-OS: 26.6 (macOS version)
X-Parallex-Arch: arm64 (Apple silicon or Intel)
X-Parallex-Active: day,week (first check today, this week, this month, or ever)
X-Parallex-Bucket: 42 (a number from 0 to 99 picked at random once)
X-Parallex-Mac: 3f2a…9c1e (a random number picked once, from Parallex 1.7)
That's how many Macs use Parallex gets counted, and which versions, without knowing whose they are. The random number is there so each Mac is counted once, whether it checks once a month or ten times a day: it's made on your Mac, isn't derived from anything about you or it, and is never tied to the usage report's number. The server keeps a count per day, version, macOS, chip and kind of check; the days each number was seen, for 90 days; each number with the day it was first seen and the version, macOS and chip it last came with, until 90 days after its Mac last checked, when it's forgotten; and a running total of Macs. The request also names Parallex and its version in its User-Agent, as apps do.
The number lets a new version go out to a few Macs first (those under 10, say) before everyone, so a bad release reaches few people. About one Mac in a hundred has each number, so it doesn't single yours out.
Like any website, the server sees the address a request comes from while answering it. Parallex doesn't store it and keeps no request logs; for a minute it's used, in memory, to ignore a burst of checks from one place. The first time a Mac number is seen, a one-way code made from the address with a secret key (for IPv6, from its network) is kept for two days, only to count how many new Mac numbers come from one place, so they can't be made up in bulk. Cloudflare, which runs the server, handles requests under its own privacy policy.
The update itself, like the disk image and the Terminal installer's download, comes from parallex.mandip.dev too. The server adds one to a running total for that file and keeps nothing about who downloaded it. Versions before 1.9.3 ask GitHub directly when the server doesn't answer, and GitHub is told only that a Parallex is checking (it sees the address too, as it does for any visit). Updates are verified against a signing key built into the app either way, so the server couldn't hand you a bad update even if it wanted to.
From Parallex 2.0, updates come with a license or the trial. When the server answers that this Parallex needs one, Parallex asks for the release a second time, with its license token instead of the random Mac number: that second request carries the token, this Parallex's version, macOS's version, the chip and the 0 to 99 number, and nothing that's counted. The token and the Mac number are never sent in the same request. See Your license for what the token is, and for the one time the Mac number goes with a license: when you claim a founding license.
You can turn automatic checks off in Settings › About.
The Terminal installer
curl -fsSL https://parallex.mandip.dev/install | sh asks the same server for the latest version and says it's an install, with the macOS version and chip. It's counted the same way.
The anonymous usage report
Parallex changes every week. To know which releases and app updates break things, often before anyone has to write in, it sends a short report once a day, with the update check. New installs choose in the first-run setup, where it's on unless you turn it off; people who used Parallex before version 1.6 are asked once (if you had turned the old weekly report off, it stays off). Nothing is recorded before you've said yes. It's one switch, Share anonymous usage in Settings › About (or parallex usage --no-share in Terminal), and See What's Sent shows the whole report first, as does parallex usage.
What it holds:
- A random install number, made on your Mac and renewed every 180 days, so a Mac's reports count once rather than daily. It isn't derived from anything about you or the Mac, and it's sent nowhere else. With it goes the week Parallex was first used, so newcomers of the same week can be counted together. Each report also has a random id of its own, the same if it has to be sent again, so a report whose answer was lost isn't counted twice; the server keeps the id alone, never with the install number, for 8 days.
- This Parallex's version, the macOS version and the chip, as with the update check.
- What this Mac has: how many instances of each kind; the apps they copy, with each one's version, named only if it's Apple's, from the App Store or a well-known app (Slack, Chrome, Spotify…), and otherwise only counted; which website presets you use (WhatsApp, Teams…), never other sites; and which features are in use, like workspaces, snapshots or a pinned version, and how many.
- What happened since the last report, counted, each with the Parallex version it happened on: instances made (whether from the app or Terminal, and when one couldn't be, at which step), copies that quit at launch or ran, refreshes, updates and app version changes and whether they finished, isolation checks and whether they found anything, snapshots, agent workspaces made and agent runs, which of the MCP server's tools were used (by name), how far the first-run setup got, and which Terminal commands ran, by name only, never what they were given. An agent's runs, reports, proxy log and transcripts stay on your Mac.
- Parallex's own crashes and hangs, as macOS reports them to it: the kind, and the places in Parallex's own code where they happened (a file offset per frame). Frames in macOS or in the apps you copy are dropped on your Mac before anything is sent.
Never sent: instance names, file names, paths, what's inside your instances, sites of your own, or apps that aren't well-known. The server accepts only a fixed list of event names and values, checks app IDs, app names and versions against fixed patterns, takes only a few new app IDs a day, and drops anything else. It doesn't store your IP address with a report, or at all. What it keeps is how many different networks reports come from (an IPv4 address's first three numbers, an IPv6 address's first three groups), each only as a one-way code made with a secret key and never with the install number: for 8 days, which networks reported each Parallex version and whether one saw it crash or fail, and for 90 days, which networks said an app's copies quit at launch. That's so a few made-up reports from one place can't stop a release or mark an app as broken. New install numbers from one network are counted the same way, for two days.
The usage report never carries your license, its token or anything from it, and it's never stored with them, so a report can't be tied to a license or to the email it was bought with.
What a Mac reported on a given day is kept for 90 days; after that only totals remain, per day and version, with no install numbers. The number itself is forgotten 90 days after a Mac last reports. Turning sharing off deletes the number and anything waiting to be sent on your Mac, and nothing more is recorded.
Notices and the compatibility list
Twice a day Parallex downloads parallex.mandip.dev/advisories.json, a signed list of notices about apps whose copies misbehave. It's the same file for everyone, and fetching it sends nothing about you, your license or your apps. It's fetched by itself only while Parallex checks for updates automatically: with automatic checks off (in Settings › About, or by your organization), it's fetched only when you choose Check for Updates or run parallex notices. The compatibility list shows only apps Parallex's maintainer adds, with usage reports summed up; reports alone never put an app there.
Your license
From Parallex 2.0, Parallex needs a license, or the 14-day trial, to make and change instances. This is what that sends and what's kept. Copies you've already made keep opening without any of it.
When you buy. Stripe takes your payment and your email address; it's the merchant of record, through its Managed Payments, and its checkout shows "Sold through Link". Your card details go to Stripe and never reach me. Stripe sends me your email address, what you bought, the price and the order's reference. I keep your email, what you bought and the order's reference for as long as the license exists. The key itself isn't kept: only a one-way code made from it, which can't be turned back into the key, and its last five characters, to help you find it. Stripe handles your payment under its own privacy policy.
When you add a Mac. Parallex sends your key and a code made on this Mac from its hardware ID by a one-way function, so the server can tell your Macs apart without knowing their hardware IDs. With it go Parallex's version, macOS's version and a name for the Mac you can change (by default its model, like "MacBook Pro"). The server answers with a license token: a short note it signs, saying which license this Mac has, until when. About once a day Parallex asks for a fresh token, sending the one it has, macOS's version and the Mac's name (so a name you change reaches the license's list of Macs).
On macOS 27 and later, Parallex also proves it's the signed Parallex on a real Mac, using Apple's App Attest. Apple's service vouches for a key that Parallex makes and keeps on this Mac; the server keeps that key's public half and a counter with the Mac's entry, to check later requests. Apple handles App Attest under its own privacy policy.
Trials. Starting a trial sends the same Mac code, Parallex's version and macOS's version, so a trial is once per Mac. The network address it comes from is used, as a one-way code, to count how many new trials one address starts in a day; the count is gone within two days.
Founding licenses. To show that a Mac used Parallex on or before October 4, 2026, claiming a founding license sends, once, the random Mac number from the update check, along with the Mac code and versions above. The server checks that the number was seen on or before October 4, and keeps only a one-way code made from it, with the founding license, so the same number can't claim twice. This is the one place where the update check's anonymous number and a license meet, and it happens only if you claim. Once the claim goes through, Parallex picks a new random number for its update checks, so the number you claimed with doesn't turn up in later checks and they can't be tied to your license. The number you claimed with stays on your Mac, in Parallex's license folder, and is never sent with update checks; Parallex sends it again only if you claim again (say, after your keychain was reset), to get the same license back. So that claims keep working, the numbers seen on or before October 4 are kept on a list of their own until claims close on January 31, 2027, and then deleted. You can add an email address when you claim, so you can find the key again; it's optional.
Asking for a founding license. If your Mac has no update-check number to claim with (a Parallex before 1.7, or update checks turned off), you can ask for a founding license from the app instead, and a person checks it by hand. Asking sends your email address (required, because the key is emailed to it), the Mac code and versions above, the Mac's name, and three things Parallex knows on this Mac: the day your first instance was made, how many instances you have, and the earliest Parallex version it has a record of. The country your request comes from is noted too (from the network address, which isn't kept). The server keeps all of that with the request, and a one-way code made from your email, until the request is decided; 90 days after it's approved or denied, the request is deleted. If it's approved, the license itself is kept like any other: with your email, for as long as it exists. If that email already has a founding license, approving the request emails that address a link instead, and the Mac is added to the license only once the link is used; the Mac that asked is never sent that license's key. A notice that a request came in goes to a private chat channel, with the country, the first instance's day and Parallex's version, never your email. You can also write to hello@mandip.dev.
Accounts, if you want one. An account is optional: keys work without one, and the trial never needs one. Signing in, in Parallex or on the account page, sends your email address; the server emails it a 6-digit code and a link, which work once, for 10 minutes. Asking again while that sign-in is still open sends the same email again (at most once a minute) rather than a new code. The email is the same whether or not you have an account, and asking doesn't look anything up. From the app, the request also carries the Mac code, the Mac's name and the versions above (and, on macOS 27 and later, Apple's App Attest proof). Once the code or link checks out, every license bought with that email is linked to the account, and this Mac gets a session: a random secret the server keeps only as a one-way code, tied to this Mac, kept on your Mac in the login keychain, like the license key. The session is checked with the license once a day, and lasts 90 days past the last check. On the account page, Cloudflare Turnstile checks that you're a person before a code is sent. Asking for a code sets a cookie for 10 minutes, holding a random value the server keeps only as a one-way code, so the browser that asked can finish signing in; a sign-in finished in any other browser first asks you to confirm the address it's for, shown with most of it hidden. Signing in sets one cookie, which holds that page's session and ends after 30 minutes. Signing in never takes a seat on its own: a Mac is on a license only when it's activated, as with a key. A Mac that gets its license from the account never receives the key; the account page shows it, after a fresh code. A sign-in from a country or a Mac the account hasn't used lately is posted to a private chat channel, with the account's id and the country or Mac's name, never your email, and you're emailed about it too (a few times a day at most). Buying while signed in fills your email in at checkout and links the purchase to the account. You can sign a Mac out in Parallex (Settings › License), and any Mac on the account page.
Kept apart from the usage report. Your license, its token and the Mac code are never sent with the usage report's random number, and never stored with it. Apart from a founding claim, they're never sent or stored with the update check's Mac number either. Your anonymous usage report can't be tied to your email.
Emails. You get your key after buying (or after claiming a founding license with an email address, or when your request for one is approved), a sign-in code and link when you ask for one, a note when your account is signed in to from a country or a Mac it hasn't used lately, and a note when your account is deleted, so you'd know if it wasn't you. All are sent through Resend. Nothing else, and no newsletters. Because the key is in the email, it passes through Resend, which keeps a log of the emails it sends, key included, for a limited time under its own policy.
What the license server keeps, and for how long:
- Your license: your email (for a founding license, only if you added one), the one-way code made from the key and its last five characters, the tier, how many Macs, where it came from, the payment's reference and whether it was refunded. Kept while the license exists.
- Each Mac on it: the one-way code made from its hardware ID, the name it sends, Parallex's and macOS's versions, its App Attest key on macOS 27 and later, and when it was added, last checked in and freed. Kept with the license.
- Trials and founding claims: the Mac's code and the dates, so each Mac gets one of each, and for a founding claim, the one-way code made from the update check's Mac number.
- Founding requests: your email and a one-way code made from it, the Mac's code, name and versions, what Parallex sent about your instances, the country, and whether App Attest vouched for the app. Deleted 90 days after the request is approved or denied; a pending one stays until it's decided. If you delete your account and choose to remove your email from your licenses, your requests stay without your email or its code: a pending one can still be approved, and its Mac gets the license without a key or an email.
- What happened to a license (Macs added and freed, refunds), with the date. The network address it came from is kept only as a one-way code, with the country, and both are erased after 90 days. They're there to spot a leaked key.
- Orders: what was bought, the price before tax, the currency, and refunds. Kept for 7 years, for tax records.
- Your account, if you made one: your email and a one-way code made from it, which licenses are linked to it, its sessions (each Mac's code and name, Parallex's and macOS's versions, its App Attest key on macOS 27 and later, when it signed in and was last seen), and its sign-ins and what was done on the account page, with the times and, from a Mac, its code and name. The network address is kept only as the same one-way code as above, with the country; the address's code, the country and the Mac's code and name are erased from this history after 90 days. Sessions that ended are deleted 90 days later. Kept until you delete the account.
- One-time sign-ins (the email they went to, one-way codes made from the code and the link, the code and link themselves encrypted with a server key so the same email can be sent again while it's open, cleared once it's used, from the app the Mac's code, and from the account page a one-way code of the browser's cookie) last 10 minutes and are deleted the next day. Counters that slow down abuse are deleted after two days.
Cloudflare runs the server, Stripe takes payments, and Resend sends the emails. Each handles what passes through it under its own privacy policy.
Deleting it. Sign in on the account page and choose Delete my account, or write to hello@mandip.dev. The account, its sessions, its history and its sign-ins are deleted, and every Mac is signed out. Your licenses keep working and keep your email, so a lost key can still be sent to you. To remove your email from your licenses too, tick Also remove my email from my licenses: then it's removed from every license on the account or bought with it, and from any founding request (which stays, without it). Each license keeps working from its key; without the email, nobody can send you a key again. Orders stay for tax records, without your email. Either way, an email to that address says the account was deleted.
Things you do yourself
- Something's Off (in the menu bar, the Help menu and Settings) sends a note you write to
parallex.mandip.dev, only when you press Send. With it go this Parallex's version, macOS's version and the chip, and, if you pick an instance, its kind, its app if that's a well-known one (with its version), and how it has been doing: how often it has quit at launch, what its isolation check found, whether it's running, whether it uses Guard, a keychain of its own, a pinned app version or the original's settings, and what it needs (a repair, an update). Never its name, paths or contents. See What's Sent shows the whole note first. An email address goes only if you type one, and it's deleted once the note is dealt with, or after 90 days. A note dealt with is deleted 90 days after it was sent; your IP address isn't stored with it (notes from one network are counted for two days, by the same kind of one-way code as usage reports, so one place can't fill the day's). Mission Control may post that a new note has arrived to a private chat of the maintainer's, without its words or your address. - Collect Diagnostics (in the Help menu, or
parallex diagnose) makes a zip on your Mac to attach to a support email yourself: Parallex's and macOS's versions, how your instances are set up and doing (their names only if you tick the box), the last day of Parallex's own log, its checkup, and Parallex's own crash records. Your home folder, account and computer names, emails, keys and tokens are taken out first, and you see every file in it before it's saved. Nothing is sent anywhere by it. - Crash records. When one of Parallex's own programs crashes, it writes a short record (which program, its version and where it stopped) to Parallex's folder on your Mac, kept 30 days. They go into a diagnostics zip you make, and are counted in the anonymous usage report only while you share it.
- Report How It Works opens a GitHub issue with the app's name, its version and how the instance was made filled in. Nothing is sent until you submit it on GitHub, and it never includes instance names or file paths.
- Website instances talk to the sites you add, like any browser.
- Getting a site's icon downloads it from that site when you create a website instance.
- Buy and Upgrade open Stripe's checkout in your browser. See Your license.
Nothing else
Inside a copy, the app's own updater is turned off, and its update address is parallex.mandip.dev/no-updates.xml, a file that never has an update, so the vendor's build can't replace the copy. Should that updater ever ask, it gets that file, like any web page; nothing about it is counted or kept.
Three plain requests send nothing but Parallex's name and version: the purchase screens and Settings › License ask parallex.mandip.dev for the current prices; when Parallex can't confirm a license, it asks whether licensing is paused; and Doctor (Diagnostics, or parallex doctor) checks that the server answers. Nothing about them is counted or kept.
The audit log, from Parallex 3.7, is a record of what's done with Parallex that matters for security (instances made and removed, repairs, license changes, updates and the like), kept in Parallex's folder on your Mac and in macOS's own log there. It's never sent anywhere. Every address Parallex contacts is listed with what each request carries and how to turn it off.
Tips, the coach (off until you turn it on) and the monthly recap are worked out on your Mac from Parallex's own records, kept in tips.json, coach.json and recap.json in Parallex's folder, and never sent anywhere, the usage report included. What they look at.
No analytics beyond the report above, no third-party trackers or SDKs, and no account needed: it's optional, for getting your license on a Mac without a key. Your instances' names and anything inside them stay on your Mac.