Legal

Terms of service

Mirryl (the application, its source code, and its associated branding) is an independent product designed, developed, and owned by Johan Socarras (“the Developer”). All rights not expressly granted in this agreement are reserved.

Scope — Mirryl Beta only

Mirryl is in beta. During the beta it costs nothing; a paid version is planned. This agreement covers Mirryl Beta: the application offered for download at mirryl.com at no charge, and the activation service it uses. It does not cover any paid edition. Any paid edition the Developer may offer in the future would be a separate product, obtained separately and governed by its own terms. Nothing in this agreement grants you any right to a paid edition, to any price, or to an upgrade from the beta, and offering a paid edition would not by itself change or end this agreement for copies of the beta. This agreement continues to apply to every installed copy of the beta, including after its validity period has ended.

License grant — Mirryl Beta

Subject to your compliance with this agreement, the Developer grants you a personal, non-exclusive, revocable license to install and run Mirryl Beta on any computer you own or control. While that computer’s license remains valid under Software license below, this covers the full feature set; after that period, and whenever the application holds no valid license, it covers only the reduced feature set described there. Each computer activates separately and runs its own six-month period. A license belongs to the computer that activated it and does not move to another one.

This license does not grant you any right to: sell, rent or sublicense the application, remove or alter any copyright or licensing notice, or reverse engineer or decompile the application beyond what applicable law permits notwithstanding this restriction. Copying the application folder to another computer you own or control, for your own use, is fine — each copy activates on its own. Redistributing Mirryl to other people, or repackaging it, is not. Any source code the Developer publishes under an open-source license is governed by that license, not by this one.

Availability and discontinuation

The beta is offered at the Developer’s discretion, for as long as the Developer chooses to offer it. To the extent permitted by applicable law, the Developer may change, suspend or discontinue the beta, the activation service, the download at mirryl.com, updates, email support, or any part of them, at any time, for any reason or none, and without prior notice. No purchase, fee or account is involved, and nothing in this agreement is a promise that the beta, the activation service or this website will remain available for any length of time — including the full validity period described under Software license below. The Developer has no obligation to provide updates, new versions, maintenance or support for the beta, and may release new versions on any terms, or not at all. The Developer’s liability for any change, suspension or discontinuation is limited as set out under Limitation of liability below.

If the activation service stops responding — because it has been discontinued or for any other reason — the application behaves as described under Software license below. A computer that still holds the license the service issued to it keeps the full feature set until that license’s own expiry date, as long as the license file stays in the Windows user profile that activated, on that computer, its fingerprint does not change and its clock is not set back; a computer that holds no such license — because it never activated, because its period has ended, because the stored license is gone, or because the computer was rebuilt or reinstalled — runs with the reduced feature set. No new license period is issued to any computer after the service is discontinued. This describes how the application is built today; it is not a promise that any computer’s period will run to its end. An installed copy will keep trying to contact the activation service on each launch and, while it cannot be reached, every few minutes thereafter, and may show a notice that the service cannot be reached; that notice is expected and is not a defect. No further update notices will be delivered; a notice the copy already received may stay visible while its stored license lasts. Discontinuing the beta or the activation service does not by itself terminate your license to a copy already installed.

Termination

This license terminates automatically if you violate any term of this agreement. Upon termination, you must stop using the application and delete all copies in your possession. Ceasing to offer the beta or the activation service, as described under Availability and discontinuation above, is not a termination of your license for breach and does not require you to stop using, or delete, copies already installed.

Changes to this agreement

The Developer may update this agreement at any time by publishing the updated text on this page with a new “Last updated” date. The updated agreement applies from that date to every copy of the beta, and continued use of the application after that date constitutes acceptance of the updated terms. Where the copy of this agreement shipped with the application and this page differ, this page governs while it is published; if this page is no longer published, the copy shipped with the application is the text that applies.

Governing law

This agreement is governed by the laws of the State of Texas, without regard to its conflict-of-law rules. Any dispute arising out of it belongs in the state or federal courts located in Harris County, Texas, and you and the Developer each agree to that venue.

Privacy policy

Who runs Mirryl

Mirryl is built and run by Johan Socarras (“the Developer”), an independent developer working on his own. He operates mirryl.com and the activation service at activate.mirryl.com. No company is involved beyond the infrastructure providers named further down.

You can reach him about anything on this page at legal@mirryl.com.

In the language of the GDPR he is the data controller for the activation record: he decides what is collected and why, and no one else shares that role. Two providers process data on his behalf, each a different thing: Cloudflare, which hosts this site and the activation service — the activation record lives in its storage and nowhere else — and Google Workspace, which hosts the mailbox behind that address, so it handles the mail you choose to send and not the record. Both are processors: they hold what they hold because they run the infrastructure, on the Developer’s instructions.

What Mirryl sends over the internet

The desktop application makes one kind of outbound request, to one address.

License activation. Mirryl computes a SHA-256 hash of one hardware identifier read from your computer: the identifier its motherboard reports to Windows (the system UUID, or failing that the board’s serial number) or, if the motherboard reports nothing usable, the serial number of the disk Windows is installed on. On a computer that offers neither, it falls back to the formula earlier versions of Mirryl used: the Windows MachineGuid (a value Windows generates for itself when it is installed) joined with the serial number of your C: volume. The result — 64 hexadecimal characters — is your fingerprint, the one shown in the application. The request also carries the hashes of whichever of those other identifiers the computer has, computed the same way, so that a computer first registered under the old formula keeps its period. The request carries those hashes and nothing else: no name, no email, no account, no username, no hostname, no MAC address, no hardware model, no Windows version, no identifier in readable form, and nothing about the Android phone you connect.

That request goes to activate.mirryl.com. It is made when the application starts, and then about every six hours for as long as it stays open — so a computer left running all day contacts the service a handful of times a day. If a request fails it retries with a short backoff — and, while the service stays unreachable, about every five minutes for as long as the application is open — and there is a Retry button that triggers one on demand.

The reply is a small signed record: which edition your computer is on, when its fingerprint was first registered, the time by the service’s own clock when it was signed — which is what the application judges the end of the period by, rather than your computer’s clock — and the version number of the current Mirryl release, so the application can tell you an update exists. The signature is verified before any of it is read.

That is the only thing the desktop application sends anywhere. There is no analytics service, no crash reporter and no usage tracking. The mirroring engine does run a small web server while it is mirroring, but it is bound to 127.0.0.1 — your own machine — and is not reachable from your network. Pairing and mirroring talk to your phone directly, over USB or over your local network. Nothing about the phone, the apps on it, or what is on its screen leaves your computer.

The Android app sends nothing. It makes no network requests at all. It reads your phone’s own Wi-Fi address in order to show it to you — that is the address a wireless connection needs — and it writes to three places: its own private storage on the phone, a .devid file holding a device identifier in the app’s folder on external storage — so your PC can read it when pairing — and the one Android setting that turns Wireless debugging back on. Turning that setting back on is what the app is for, and it is what the WRITE_SECURE_SETTINGS permission in its manifest is for. From version 1.0.11 the manifest does not declare INTERNET, so Android itself does not let the app open a network connection. Earlier versions declared it, but no code in them used it.

From version 1.0.11, when Mirryl on your PC connects to your phone it also puts the Android app on Android’s battery optimization exemption list, the same way it grants that permission. Without it, Android holds back the app’s background checks on a phone that has been idle, and Wireless debugging can stay off after a Wi-Fi drop until you pick the phone up. This changes nothing that is sent anywhere. You can remove the exemption on the phone under App info > Battery; Mirryl on your PC puts it back the next time it connects.

What mirroring captures

Mirroring means Mirryl reads what your phone is showing and playing and brings it to this computer, over the cable or over your own network. It is worth being exact about what that includes, because the rest of this policy is about a licence check and this is what the product actually does.

Your phone’s screen. The picture in the mirror window is video encoded on the phone and decoded here. It is not written to a file.

Your phone’s sound. Mirryl also carries the audio your phone is playing, so a video or a game is heard through your computer. Two things are worth saying plainly. It is never the microphone — Mirryl contains no code that opens one, so nothing around you or said near the phone is picked up; only what the phone itself is playing. And there is no setting to turn the sound off: it starts with the mirror and stops with it.

How the sound is carried depends on the phone, and you will notice the difference. On Android 13 and later Mirryl first asks for a copy, which leaves the phone playing through its own speaker as well. If the phone refuses that — and always on Android 11 and 12 — Mirryl takes the phone’s output instead, and the phone’s own speaker stays quiet while the mirror is open. On Android 10 and earlier there is no sound at all.

What you type, paste and copy. Keys and clicks you aim at the mirror window are sent to the phone as input, and Ctrl+A, Ctrl+C, Ctrl+X and Ctrl+Z reach the phone as those shortcuts. While a mirror window is open, text is shared between the two clipboards both ways. When you paste into the mirror window, the text on your PC’s clipboard is put on your phone’s clipboard and pasted there; that is the only moment your PC’s clipboard is read. Whenever your phone’s clipboard changes while the mirror window is open — whether you copied from the PC or with the phone’s own Copy button — Mirryl reads that text and puts it on your PC’s clipboard, replacing what was there. With no mirror window open, Mirryl does not read your phone’s clipboard. Only text is carried, up to 64 KB per copy. It travels over the cable or your own network and is not stored anywhere; the session log notes only how many bytes were carried.

None of this is recorded to a file, and none of it leaves the two devices. There is no server in the middle: the picture, the sound and the input travel over the USB cable, or straight between your computer and your phone on your own network.

Why the activation record exists

The trial runs for six calendar months per computer. For that to mean anything, the service has to be able to tell it has seen a given computer before — otherwise reinstalling Mirryl would restart the clock every time.

The legal basis for keeping that record is the Developer’s legitimate interest — Article 6(1)(f) of the GDPR — in enforcing the terms of the beta; concretely, in knowing whether a computer has already started its trial. Consent is not the basis, and calling it that would be dishonest: the check runs whenever Mirryl starts, and you cannot switch it off and keep using the application, so agreeing to it would not be a real choice.

Worth being exact about what that check does and does not catch: because the fingerprint is built from the motherboard (or the system disk), it stays the same when Windows is reinstalled or the drive is reformatted — that is the reason it is built that way. Replacing the motherboard, or the disk on a computer whose fingerprint comes from it, produces a different fingerprint, and the service treats the result as a computer it has never seen. So does a computer on the old formula when Windows is reinstalled.

The hash is how the count is kept without knowing who you are. It carries no name, no email and no account; it is not looked up against anything else, not combined with any other data, and not used for advertising, profiling or analytics. It identifies one computer, not a person.

And the honest limit of that, rather than an overclaim: a hash of a fixed hardware value is a durable pseudonym for a machine — more durable now that it follows the motherboard rather than the Windows installation. What keeps it harmless here is not the mathematics, it is that nothing is ever stored beside it.

What the activation service stores

One record per fingerprint. The fingerprint is the key the record is filed under; the record itself holds five fields: which edition the computer is on (today there is only one, “free”), the date the fingerprint was first seen, the length of its period (six months for a computer registered today; this is the field the Developer raises to grant an extension), a flag noting that the record’s own expiry has been set, and the number of days the record is kept. A record carried over from an older fingerprint (see above) holds a sixth: that older fingerprint, so the two can be found together. That is the entire record. The record under the older fingerprint is left as it was until its own expiry, described below.

The service does not store your IP address, a log of your requests, a count of how many times you have activated, your country, your Windows version, or which release of Mirryl you are running.

It has two routes and no others: the activation endpoint described above, and a health check. There is nothing to query, nothing to browse, and no endpoint that lists records.

How long the record is kept

Each record is stored with an expiry of three years, counted from the moment that fingerprint was first registered, not from the last time it was seen. The expiry is set once, when the record is created; re- activating does not extend it. When it passes, the storage deletes the record on its own. Three years is deliberately far longer than the trial it describes: a record that expired around the same time as the license would make the computer look new again, and the trial would quietly start over instead of ending.

That has a consequence worth stating plainly rather than hiding. The three years run from the first registration and are not refreshed by use, so three years after a computer first activated, its record is deleted whether or not it kept running Mirryl. If that computer activates again after that, it is a computer the service has never seen, and it starts a fresh period. The window is long enough that the trial genuinely ends, and short enough that a hardware fingerprint is not kept forever. If the activation service is discontinued, the records it holds are deleted when it is shut down rather than kept for the remainder of the three years.

The one exception: if the Developer extends a computer’s period, its record is kept until 30 days after that longer period ends, when that is later than the three years, so the extension is not lost while it still runs.

Third-party services

The activation service runs on Cloudflare Workers, and the record lives in Cloudflare’s key-value storage. Cloudflare handles the fingerprint as part of running that infrastructure, subject to its own privacy practices.

As with any website, Cloudflare’s network also sees the IP address a request arrives from. That is unavoidable for anything served over the internet, and it is separate from what Mirryl stores — which, as above, does not include it.

Email you send to the address on this page is hosted on Google Workspace, so Google handles messages you choose to send.

Nobody else receives any of it. It is not sold, shared, or transferred to any other party.

What stays on your computer

Your device list and settings. Mirryl keeps a folder in your Windows user profile holding the license it received, the list of phones you have paired — each one’s alias, its address on your network, its hardware serial number, and when it was last seen connected — the list of phones set up to reconnect on their own (by serial number), the notes the reconnection service keeps for itself, a private key that identifies this PC to your phone, and preferences like theme and keyboard shortcuts. The private key is generated on your machine and never leaves it. None of this is sent anywhere.

Files from earlier versions. Up to version 1.0.0, Mirryl could save Android bug reports and screenshots under Documents\Mirryl, in a folder named after the device. Version 1.0.1 removed that, and version 1.0.11 moved the activity log described below out of that folder too: nothing is written there any more. If a folder is still on your computer it belongs to you and you can delete it — and it is worth knowing what is in it, because an Android bug report can contain that phone’s serial number, the list of apps installed on it, and system logs. Nothing there was ever uploaded.

An activity log. Mirryl appends plain text to activity.log in a Mirryl folder in your Windows user profile (%LOCALAPPDATA%\Mirryl, beside the other logs), recording things like a failed license check or a device limit being reached; a failed check is noted when it starts failing, not on every retry. It is written for you, not for the Developer, and is never uploaded. It is kept under 2 MB: when it grows past that, only its most recent 500 lines are kept. It is deleted when Mirryl is uninstalled, and you can delete it yourself whenever you like. Versions before 1.0.11 kept this file as Documents\Mirryl\activity.log, without a limit; the first time 1.0.11 runs it deletes that old file, and the Documents\Mirryl folder if nothing else is left in it.

Session logs from the mirroring engine. While mirroring, the engine writes one log file per session, in a Mirryl folder in your Windows user profile. It records per-second figures about the connection — frame rate, latency, dropped frames — and, so that a fault can be traced back to the phone it happened on, which phone the session was with: its hardware serial number over a cable, or its address on your network over Wi-Fi, together with the alias you gave it. It also copies the lines the Mirryl agent writes to the phone’s own system log while the session runs. It does not contain the picture, the sound, or anything you typed.

These logs stay on your computer and are never uploaded. Mirryl keeps the most recent of them up to 5 MB per phone and deletes that phone’s oldest beyond that, so one phone’s sessions never push out another’s. The check happens when a mirror session starts, so a long session can carry a phone over the limit while it runs and is tidied up at the next one. You can delete the folder yourself whenever you like.

The other logs, all in that same Mirryl folder, all kept for you and never uploaded, and all deleted when Mirryl is uninstalled: the reconnection service’s log (watcher.log: one line every 25 seconds about which phones it sees, with their serial numbers and network addresses), one short status file per phone that the mirroring engine overwrites on every session (mirryl-engine-<serial>.log), the pairing log (qr_pairing.log: each step of a QR pairing), and the setup log (setup.log: what the installer and the Repair button did). Each of these is kept under 2 MB; past that only its most recent 500 lines stay.

When you uninstall. The uninstaller deletes every one of those logs without asking, and offers to remove the startup task and the firewall rules it created (that needs administrator permission once, which is why it asks). It keeps your device list, the license it received and the private key that identifies this PC to your phones, unless you tick “Delete app data” — and it warns you before doing that, because a new key is not accepted by phones that know the old one, so every phone would have to be set up again. Your activation record on the service is not touched by uninstalling: installing Mirryl again on the same computer picks up the same period, as described above.

About this website

mirryl.com serves static pages. Its typefaces are served from this domain rather than from a font CDN, so reading a page here does not fetch anything from an outside company.

This site loads nothing from any outside company: no analytics script, no tracker, no cookie. Nobody counts your visit.

The only things Mirryl itself keeps in your browser are your choice of language and of light or dark theme; they stay on your device.

Asking about, or deleting, your activation record

If you would rather your computer’s activation record not exist, email legal@mirryl.com with your fingerprint and the Developer will delete it, together with the record under the older fingerprint it was carried over from, if there is one. The same goes if you only want to know whether a record for that computer exists.

Your fingerprint is shown, and can be copied, in the application under Settings → Privacy. It is the only way a record can be found: because it holds nothing that identifies you, a request without it cannot be matched to anything.

There is no form and no automated endpoint for this — deletion is done by hand, which is workable at this scale. And it has a consequence worth knowing before you ask: once the record is gone the service treats that computer as one it has never seen, so its trial starts again from that point.

Your rights over that record

That record is personal data under the GDPR, even though it holds nothing that names you, so the usual rights apply to it. You can ask the Developer to confirm whether a record for your computer exists and to give you a copy of it (access), correct it (rectification), delete it (erasure), stop or limit what is done with it (restriction and objection), or hand it to you in a portable form (portability). A record of five fields (six when it was carried over from an older fingerprint) makes most of that a short answer. Erasure is the case described just above, consequence included — and that same consequence is the honest answer to restriction and objection: there is no way to keep the record from being written while you go on using Mirryl, because the check runs at every start and cannot be switched off. Stopping the processing means the record goes and the trial starts again, or you stop running the application.

There is no profiling. What the service does automatically is narrow, and it is already described above: it matches one fingerprint, files or reads the record for it, and signs a reply with the edition, the dates, and the current release number. Nothing about you is scored, ranked or evaluated, and no decision about a person comes out of it.

To use any of these, email legal@mirryl.com and quote the fingerprint shown under Settings → Privacy, exactly as for a deletion request: it is the only way a record can be found. The Developer answers within one month, or writes to say why it will take longer, which the GDPR allows in complicated cases. There is no ticketing system behind that and no automated process; requests are read and handled by one person.

If you are in the EU or the UK and the answer does not satisfy you, you can complain to your national data protection authority. You do not need the Developer’s agreement to do that, and writing to him first is not a condition.

Where the record sits: the activation service runs on Cloudflare’s network, which is worldwide, so the record may be held or served outside the country you are in. The mailbox is on Google Workspace. Both providers publish their own privacy terms, and the fingerprint and your mail are covered by those terms while they hold them.

Changes to this policy

The Developer may update this policy for future versions of Mirryl. If a change alters what is collected or why, it will be described here with a new date rather than folded in silently.

Software license

License validity and activation

Mirryl Beta activates automatically the first time it runs, by sending a one-way hash derived from a hardware identifier of your computer — its motherboard’s or, failing that, the serial number of the disk Windows is installed on (“the fingerprint”) — to Mirryl’s activation service (activate.mirryl.com), together with the same kind of hashes of the computer’s other identifiers, so that a period begun under an earlier version carries over. The application repeats that check when it starts and about every six hours while it stays open, so that an expired license is noticed rather than assumed. The service is not sent your name, email or any account information: the request carries those hashes and nothing else. The privacy policy above describes exactly what is stored, and what Cloudflare sees as the network carrying the request.

The trial is valid for six (6) calendar months from the date your fingerprint was first registered with the activation service — not from the date you installed or reinstalled the application. A computer registered on October 2 is valid until April 2; one registered on August 31 is valid until the last day of February. Reinstalling Mirryl, reinstalling Windows or reformatting the computer does not extend or reset this period, because the fingerprint follows the hardware rather than the Windows installation. Replacing the motherboard — or, on a computer whose fingerprint comes from its disk, replacing that disk — produces a different fingerprint and its own six-month period.

Whether the period has ended is judged by the activation service’s clock, which travels inside the license it signs, and not by your computer’s: setting the computer’s clock back does not extend the period. While the service cannot be reached, the application judges by the latest time the service last reported; if the computer’s clock has been set back more than six hours from the latest time the application has already recorded, it runs with the reduced feature set until the clock catches up again.

The Developer may, at its discretion, extend the period of a particular computer, during the period or after it has ended. Each extension is for up to six (6) calendar months, counted from the day it is granted (or from the end of the current period, if that is later), and no computer’s period runs past three years from its first registration. An extension, once granted, is not shortened or withdrawn; if, by mistake, an extension is recorded for longer than six months, it is corrected to six months.

After the trial period ends, Mirryl keeps running in Basic mode and does not lock itself. Basic mode works with one device at a time, over a USB cable: the first device connected by cable is the one in use, and every other device stays locked until it is unplugged. What stops: pairing a device, connecting to one over Wi-Fi, finding devices on your network, mirroring over a wireless link, and sending files over a wireless link — sending files works over the cable. Device tools — status and restarting a device — also stop, even though they do not use the network. The automatic reconnection after a reboot keeps dialling your devices over Wi-Fi for fourteen days after the period ends — the time it needs to keep re-enabling Wireless debugging on them — and then stops; Basic mode does not use that link, so on your phone you can turn Wireless debugging off and uninstall the Mirryl app: the cable needs neither. Devices you have already paired stay in your list, locked; plugging one of them in by cable unlocks it while it is connected. A device that is not in your list also works over the cable, one at a time, and is not added to the list: Mirryl does not save new devices in Basic mode. A device registered beyond the permanent limit described below stops being re-enabled as well: only the automatic reconnection service counts for this, no connection made more than fourteen days after the period ends counts, and the re-enabling lasts thirty days from the last connection that did. Permanently registered devices are unaffected. The application will point you to mirryl.com/upgrade for the full version. This is not a guarantee that a paid edition will be available there at that time — or, if the Developer has discontinued mirryl.com, that the link will lead anywhere. The same reduced feature set applies whenever the application holds no valid license, including after the activation service is discontinued — see Availability and discontinuation above.

During the beta, Mirryl keeps up to ten (10) Android devices in its device list per computer, and registers each of them permanently. One more device works over a USB cable without being added to the list; two unlisted devices on cables at the same time are not supported. A device keeps its place for as long as it is in your device list: removing a device from your list frees its place for another one, and a phone keeps its own place when the Mirryl app on it is reinstalled or updated. A device that is not registered permanently still has Wireless debugging re-enabled automatically for as long as it connects to that computer at least once every thirty (30) days, and stops being re-enabled if it goes longer than that without connecting — at which point you may need to turn Wireless debugging back on by hand. Mirryl tells you when a device is over the limit. Mirroring over a USB cable is never affected by this limit.

No warranty

Mirryl is provided “as is,” without warranty of any kind, express or implied, including but not limited to warranties of merchantability, fitness for a particular purpose, and non-infringement. The Developer does not warrant that the application will be uninterrupted, error-free, or compatible with every device or network configuration.

Limitation of liability

To the maximum extent permitted by applicable law, the Developer shall not be liable for any indirect, incidental, special, consequential, or punitive damages, or any loss of data, arising out of or related to your use of Mirryl, even if advised of the possibility of such damages.

During the beta, Mirryl is provided at no charge. To the maximum extent permitted by applicable law, the Developer’s total liability for all claims relating to it is limited to one hundred United States dollars (US$100). Some jurisdictions do not allow some of these limitations, so parts of this section and of the section above may not apply to you.

Third-party components

Mirryl includes third-party open-source components, each under its own license. The full list, with attributions and license texts, ships with every copy of the application as THIRD_PARTY_LICENSES.txt, COMPONENT-INVENTORY.txt and mpl-source-code.zip — the three together form one notice.

Refunds

Mirryl is currently offered only as a beta, at no charge — no payment processor or purchase flow is connected to this site, so no purchases are processed through Mirryl right now, no payment details are collected anywhere on it, and there is nothing to refund. A paid edition, if one is ever offered, would be a separate product with its own terms, including its own refund policy.

Contact

Legal questions: legal@mirryl.com