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.

License grant — free edition

Subject to your compliance with this agreement, the Developer grants you a personal, non-exclusive, revocable license to install and run the Mirryl free edition on any computer you own or control, for as long as that computer’s license remains valid under Software license below. Each computer activates separately and runs its own 212-day 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.

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.

Changes to this agreement

The Developer may update this agreement for future versions of Mirryl. Continued use of a version after an update constitutes acceptance of the updated terms for that version.

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 two values read from your computer: the Windows MachineGuid (a value Windows generates for itself when it is installed) and the serial number of your C: volume. Those two are joined, hashed, and the result — 64 hexadecimal characters — is the only thing sent. The request carries that fingerprint and nothing else: no name, no email, no account, no username, no hostname, no MAC address, no hardware model, no Windows version, 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 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, 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. The manifest also declares INTERNET, which you will see if you inspect the APK, but no code in the app uses it.

Why the activation record exists

The free edition runs for 212 days per computer — a little over six months. 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 free edition; concretely, in knowing whether a computer has already started its free period. 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 MachineGuid and your C: volume serial, reinstalling Windows or reformatting that drive does produce a different fingerprint, and the service treats the result as a computer it has never seen. The check defeats reinstalling the application, not rebuilding the machine.

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 Windows installation on one disk, not a person.

And the honest limit of that, rather than an overclaim: a hash of two fixed hardware values is a durable pseudonym for a machine. 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 three fields: which edition the computer is on (today there is only one, “free”), the date the fingerprint was first seen, and a flag noting that its expiry has been set. That is the entire record.

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 free period it describes: a record that expired around the same time as the license would make the computer look new again, and the free period 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 free period genuinely ends, and short enough that a hardware fingerprint is not kept forever.

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, and its hardware serial number — 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: 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 Documents\Mirryl\activity.log, recording things like a failed license check or a device limit being reached. It is written for you, not for the Developer, and is never uploaded. It is not rotated or trimmed, so it grows slowly; you can delete it whenever you like.

Session logs from the mirroring engine. While mirroring, the engine writes per-session performance figures — frame rate, latency, dropped frames — to log files next to the application. They describe the quality of the connection, not what you did on the phone, and they stay on disk.

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. 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 free period 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 three fields 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 free period 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

The free edition activates automatically the first time it runs, by sending a one-way hash derived from two of your computer’s hardware identifiers (“the fingerprint”) to Mirryl’s activation service (activate.mirryl.com). 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 the fingerprint and nothing else. The privacy policy above describes exactly what is stored, and what Cloudflare sees as the network carrying the request.

The free edition is valid for 212 days from the date your fingerprint was first registered with the activation service — not from the date you installed or reinstalled the application. Reinstalling Mirryl does not extend or reset this period.

After the free edition’s validity period ends, Mirryl keeps running and does not lock itself, but everything that uses the network stops: pairing a device, connecting to one over Wi-Fi, finding devices on your network, and mirroring over a wireless link. Device tools — status and restarting a device — also stop, even though they do not use the network. Mirroring over a USB cable is unaffected. Devices you have already paired stay in your list, but Mirryl will not add a new one while a device is already there. The application will point you to mirryl.com. This is not a guarantee that a newer release, or a paid edition, will be available there at that time.

Mirryl registers up to three (3) Android devices permanently per computer, and this limit applies to every installation. A device beyond that limit is not registered permanently: it 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. Reaching the limit is not announced. Removing a device from your list does not free a slot. 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.

Mirryl is provided free of 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 states 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 as a free edition only — 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. This section will be replaced with a real refund policy if and when a paid edition is introduced.

Contact

Legal questions: legal@mirryl.com