Free desktop tools for PC enthusiasts. Built by one person. Free features work without an account. Optional CLU Store purchases use a verified shop account. No cloud sync or MR.CLU app telemetry. If you join, buy in the CLU Store, recover purchases or redeem a Founder code, the app contacts mr-clu.com for the licence operations, and it is described in full below, along with everything else that leaves your machine.
LAST UPDATED: 17 November 2026
Overview
Our Approach to Privacy
The principles behind how Mr.Clu software handles your data
Mr.Clu operates as a solo developer making free tools for PC enthusiasts. Current public releases of all Mr.Clu applications are designed to operate without requiring personal information. Free features work without an account. Optional CLU Store purchases use a verified shop account. There is no cloud synchronisation or MR.CLU app telemetry.
The complete list of outbound network activity across Mr.Clu software is: update checks shortly after startup (CLU VIEW also about 10 minutes later and then once a day while it runs), with no personal payload; the CLU VIEW CLU Store while open, for its catalogue, previews, chosen downloads and ratings; VU1 Dial Controller's optional weather; and, only if you join, buy, recover purchases or redeem a Founder code, the licence checks, checkout and membership actions described below. Free users do not send a licence identifier. CLU VIEW's update feeds are mr-clu.com/cluview-update.json and cluview-latest.json; VU1, Spec Card and CLU'D IN use their own update feeds. Each contact is described below.
One more download happens during installation, not while the apps run: on Windows, if the PC does not have Microsoft Edge WebView2 Runtime (CLU VIEW needs it to draw its window), the CLU VIEW installer downloads it from Microsoft and installs it. Windows 11 already includes it.
This policy covers the mr-clu.com website and all current Mr.Clu applications. It is the complete and accurate record of what data is involved in using Mr.Clu’s services. If you identify an omission, please email support@mr-clu.com.
Optional CLU Store
CLU VIEW's free features work without an account. Browsing free content does not require shop sign-in. A verified shop account is required before buying a membership, pack, collection or individual item through the CLU Store. Your purchases are linked to that account. Cancelling a membership does not delete the account or remove purchases you bought or monthly picks you claimed.
For website sign-in, WorkOS AuthKit handles account creation, sign-in, email verification and password reset in your browser. You enter your email and password on its authentication page. WorkOS processes account and security information to provide those services, including the email address and request information such as IP address and browser details. This website sign-in does not send your password to CLU VIEW. The MR.CLU licence database does not store your email, password or name. Payment details remain with the payment provider.
The MR.CLU licence service stores an account identifier derived from WorkOS's user identifier and connects it to your purchase and membership record. Changing your email address does not move ownership to a different account. An earlier purchase is linked only after ownership has been verified; matching an email address alone is not enough. Sign-in checks the verified account and active authentication session with WorkOS when shop access is requested. These account checks do not run while you use the free app with the shop closed.
If you ask for the one-time welcome pack for free Patreon members who have never paid, MR.CLU verifies eligibility and that the shop account belongs to you. We keep a keyed hash of your Patreon membership ID with the pack grant to prevent repeat gifts for the same membership record. The plain Patreon membership ID is not stored. The hash cannot sign you in or connect a PC. The grant and its hash stay with your purchase record while we provide your owned-pack access; deleting that record removes them. We do not ask for your Patreon password, a payment card or an access key for this gift.
Shop sign-in uses strictly necessary browser cookies for the pending sign-in, the shop session and protection against forged requests. On the public HTTPS shop they are host-only, Secure and HttpOnly. Pending sign-in expires after 10 minutes. The shop session and its request-protection cookie expire after 30 minutes, long enough to finish a checkout. Signing out clears the shop cookies and ends the local session. WorkOS's authentication pages have their own cookies and processing, described in its privacy information. MR.CLU's account page contains no analytics script. Checkout and PC-connection context is kept in the current browser tab so you can return to the order or recovery request after signing in.
Pending sign-in records contain hashes, an encrypted verification secret and an optional app request hash. Website shop session records contain hashes and encrypted WorkOS user/session references. Native app session retention is described below. Provider access and refresh tokens are not kept. Expired sign-in and session records are removed by the next daily purge. The account-to-purchase connection is retained while the account exists. Existing payment, licence, recovery and backup retention rules remain listed in this policy. WorkOS's own security, backup and residual-record retention follows its applicable agreement and privacy information.
Connecting CLU VIEW on a PC uses the separate random PC public key described under licence access. Up to five registered installation slots can be connected. When all slots are used, you explicitly choose one to disconnect. Reinstalling or moving to another PC may require reconnecting through your shop account. Compare the browser's code with the code in CLU VIEW before approving a PC. Purchases can be refreshed in the Library. Purchase emails do not contain a reusable access key.
To link an earlier purchase record, you confirm a recent shop sign-in and review the records and the code shown in CLU VIEW. The link is tied to a signed CLU VIEW request from a PC that holds the earlier record. Ownership is checked through recent verified recovery, or by briefly comparing the verified account email fetched from WorkOS with the original payer's email fetched from the payment provider. Those email addresses are not stored in the MR.CLU licence database or returned to CLU VIEW. A matching email address alone does not transfer purchases. Records are joined only after you confirm; purchases, refund history and registered PC slots are retained, and existing billing plans keep their status. If the combined records exceed five slots or contain a duplicate PC, you must remove an unwanted slot before linking. A Founder code is added to the record of the shop account you are signed in to. It does not create a separate record and does not grant control over any other record. When ownership cannot be verified, including some earlier Founder records or unavailable original inboxes, verified support recovery remains available.
CLU VIEW provides shop sign-in, sign-out and account controls inside the app. A sign-in held by your browser is separate from the app's connection.
When you request permanent account deletion, CLU VIEW shows the consequences and asks you to type DELETE in the app. It sends a one-use deletion request through the existing licence service, linked to your purchase record and the random PC public key already used for licence operations. The request contains no password, email, name or provider access token. It expires after 30 minutes; expired requests are removed by the existing daily cleanup. Removing its app request removes the associated deletion consent. A fresh WorkOS sign-in must match this purchase record before the service starts deletion. A different browser account cannot authorize deleting the record reviewed in CLU VIEW.
If deletion is pending, CLU VIEW keeps a local pending-deletion flag and the existing protected PC credential so you can check completion. Paid access is disconnected while this is pending. Local profiles and installed pack files remain. The existing server deletion-retry, provider erasure and seven-day hashed completion receipt rules still apply. The app reports completion only after the service confirms it; closing an app message does not cancel a deletion already requested. These actions add no free-app startup account request or continuous background account check.
When you sign in or create a shop account inside CLU VIEW, you type your email address in the app. CLU VIEW sends it over HTTPS to the MR.CLU licence service, which asks WorkOS to email you a 6-digit code. You type the code into CLU VIEW, and it goes the same way to WorkOS to be checked. There is no password to create. An account made earlier with a password signs in the same way, by code. MR.CLU does not write your email address or the code to its licence database, app settings, logs or analytics. Both are cleared from the app form when sign-in finishes or is cancelled, and neither is saved for a later sign-in.
While you wait for the code, the licence service keeps the pending sign-in only for that sign-in. It is encrypted at rest, bound to the requesting PC's random public key, and refused after at most ten minutes. Expired records are removed by the existing daily cleanup. They contain no saved email address or code. WorkOS sends the code email and keeps its own records of it, as described in its privacy information. Provider access/refresh tokens and the WorkOS server API secret are not returned to the app page or included in URLs.
The existing account identifier, purchase record and five registered PC slots continue to provide access and recovery. Signing out inside CLU VIEW removes access on that PC while preserving purchases, billing plans, installed pack files and local profiles. A different account cannot silently take ownership of earlier purchases. Permanent deletion still requires typed DELETE and fresh authentication for the exact reviewed owner. Existing deletion-retry and completion-receipt retention rules continue to apply.
Google and other external identity-provider sign-ins, where offered, use your system browser rather than an embedded OAuth page. WorkOS and those providers handle their own account/security processing under their policies. CLU VIEW's free features remain usable without a shop account. These account operations run only when requested and add no free-app startup authentication request.
Remember me on this PC is optional and is on by default; you can untick it. When it is on, CLU VIEW saves its existing PC-bound access credential and signed access statement locally so you can reopen the app without signing in each time. Windows protects the saved credential for your Windows user account; Linux limits access to the current user. Your email address and sign-in code are not saved. If you untick Remember me, ordinary shop access stays in the current app session and is not restored after you close the app. The app may still retain the existing protected proof and pending flag needed to finish an account deletion you explicitly requested, and queued requests needed to disconnect a PC.
For native shop sign-in, the licence service holds hashed session secrets and encrypted WorkOS user/session references for up to 24 hours without Remember me, or up to 30 days with Remember me. WorkOS session expiry or revocation can end access earlier. These native records are bound to the registered PC and purchase record. They contain no saved password or email address and no provider access or refresh token. Expired records are removed by the existing daily cleanup. Each emailed sign-in code expires within ten minutes. The app's sign-in request lasts at most thirty minutes, so you can ask for a new code inside it. Website sign-in and checkout browser cookies expire after thirty minutes.
Signing out removes shop access on this PC and ends its licence-service shop session. It does not cancel your membership or delete your purchases. If the service cannot be reached, local access is removed immediately and the app keeps a protected disconnection request to retry. Registered PC slots remain until disconnection or explicit replacement is confirmed. A different PC uses the same verified shop login to access the same purchases and membership, with at most five registered PCs. Connecting a sixth PC requires you to choose an existing PC to disconnect; none is removed silently. These changes add no free-app startup account request or continuous authentication polling.
When you sign out, shop access on this PC ends immediately. The licence service also asks WorkOS to end that sign-in session. If WorkOS cannot be reached, the service keeps an encrypted reference to that session for up to seven days so its existing daily maintenance can retry. It removes the reference after WorkOS confirms the session has ended, or after seven days. Completing account deletion also removes these retry references. They contain no password, email address, verification code, provider access token or refresh token. Signing out of this PC does not sign your other PCs out.
When you request shop-account deletion, we require a recent sign-in and a separate confirmation. New shop access is blocked while deletion is pending. We verify that paid subscriptions have ended and resolve pending checkouts before removing your WorkOS sign-in and local purchase and PC-access records. Deleting the account removes purchase recovery and downloads through that account. It does not remove files already installed on your PCs or local profiles. Membership cancellation remains a separate action that keeps your account and retained purchases.
Two strictly necessary deletion-retry cookies expire after 24 hours. On the public HTTPS shop they are host-only, Secure and HttpOnly. They allow only checking or retrying an already-confirmed deletion; they cannot sign in or access purchases. MR.CLU stores hashed retry checks and an encrypted WorkOS user reference while deletion is pending. No password, email, name or provider access/refresh token is kept in this record. If billing or authentication services fail, the request remains pending for retry or verified support. The existing daily server maintenance also retries pending deletion requests. We do not report deletion complete until both provider and local erasure finish.
On completion the encrypted provider reference and local licence link are removed immediately. A minimal hashed completion receipt is kept for seven days and removed by the next daily purge. Existing hashed payment replay records, anonymous audit actions, backup retention and the providers' legal retention remain as described elsewhere in this policy. Provider backups and legal payment records are not erased by removing the shop sign-in.
Contact support@mr-clu.com if you cannot access your account, need an earlier purchase linked, or want to request account deletion. Ownership is verified before support changes access or deletes data. We explain the effect on your purchases and any active billing before completing deletion. Membership cancellation and account deletion are separate actions. Never send support a password or access key. The payment provider may retain records required for payments, disputes and its legal obligations after an account is deleted.
WorkOS and Cloudflare process data for these services under their applicable agreements. Processing may take place outside your country. See WorkOS's privacy policy, data processing addendum and current subprocessor list, and Cloudflare's privacy information. MR.CLU's ordinary visit counter remains separate from shop account access.
WorkOS privacy policy · WorkOS data processing addendum · WorkOS subprocessors · Cloudflare privacy information
Data Practices
What Mr.Clu Does Not Collect
An explicit list of data types that Mr.Clu does not receive or store
Mr.Clu applications never send your content, settings or hardware data to a server. Website visit and free-download statistics use daily anonymous hashes. If you join, buy, recover purchases or redeem a Founder code, the licence database holds the record described below. The website also holds a per-licence daily counter for owned downloads; it is not anonymous, and its retention is described below. Free users send no licence identifier. The apps do not collect the following data:
The exceptions are the private licence credential and random PC public key created only when you choose to join, buy, recover purchases or redeem a Founder code. They are persistent identifiers used to connect your licence and enforce its five registered PC slots. They contain no hardware information. Apart from these licence operations there is no persistent identifier in Mr.Clu software. Earlier anonymous install tracking was removed, and updating deletes its old local identifier.
Website
mr-clu.com — What the Website Collects
Cloudflare hosting plus a small, anonymous, first-party visit counter, and nothing else
mr-clu.com is served by Cloudflare and runs no third-party analytics, no advertising pixels, no retargeting tools, and no cookies for visitors. The only measurement on the site is a small first-party visit counter that Mr.Clu built and hosts on Mr.Clu’s own Cloudflare infrastructure. Your data is never shared with, or collected by, any analytics company.
Cloudflare — Hosting & CDN
What it does: Cloudflare hosts and serves the website globally. When you visit any page, Cloudflare processes standard HTTP request data including your IP address, browser type and version, operating system, referring URL, requested URL, and response codes. This processing is necessary to deliver the website and protect it from abuse.
Data retained by Cloudflare: Cloudflare may retain request logs and security signals per its data retention policy. Mr.Clu does not have access to individual request logs. Cloudflare’s full privacy policy: cloudflare.com/privacypolicy.
First-Party Visit Counter
What it records: Each page on the site reports basic, anonymous visit statistics to a private database on Mr.Clu’s Cloudflare account: the page viewed, the referring site (if your browser sends one), country and device type (desktop or mobile), time spent on the page, how far you scrolled, which links you clicked, which installers are downloaded via the site’s /dl/ links, and the address of any page on this site that returns “not found” (a daily count per address, so broken links can be found and fixed; no visitor detail is attached to it). This exists so a solo developer can see which pages and downloads people find useful, and which links are broken. Nothing more.
Privacy design: No cookies are used for this and your browser is not fingerprinted. Repeat visits are counted with a salted, truncated SHA-256 hash of your IP address and browser signature whose salt rotates every day. It cannot be reversed to reveal your IP, cannot recognise you from one day to the next, and cannot follow you to any other website. Your raw IP address is never written to the database. A random session id lives in your tab’s sessionStorage and is deleted the moment the tab closes.
Retention: All visit statistics are automatically and permanently purged after 90 days.
Opt-out: Two ways, and you can use either. Global Privacy Control: if your browser or extension sends the Sec-GPC signal (Brave and DuckDuckGo send it by default; Firefox has it under “Tell websites not to sell or share my data”), every counter described above is switched off for every request you make, including downloads you open directly and pages that return “not found”. Nothing to install and nothing to remember. Or run localStorage.setItem('mc_ignore','1') in your browser’s console on mr-clu.com, which stops all page, scroll, timing and click measurement in that browser and marks any download you start from a link on this site so it is not counted either. Because the visit counter sets no cookie, that setting lives only in your browser and cannot be read by the server, so a /dl/ address opened directly rather than clicked, and a page that returns “not found”, are the two cases it cannot reach. Global Privacy Control covers those.
Site owner’s dashboard
The site owner’s private dashboard reads two counts from outside services: the Patreon campaign’s members by status (paid, free, trial, declined) through Patreon’s creator API, and the Discord server’s member count. They run nightly and when the dashboard is opened. Only daily totals are kept, never names, IDs or messages.
Application
CLU VIEW — Sensor Panel
What CLU VIEW stores locally and what (if anything) leaves your machine
CLU VIEW stores all user data locally on your PC in the application’s AppData directory. This includes dashboard profiles, widget configurations, theme preferences, layout settings, and application logs. None of this data is transmitted to Mr.Clu or any third party.
| Data Type | Where It Stays | Detail |
|---|---|---|
| Dashboard profiles | LOCAL | Stored in AppData. Never transmitted. |
| Sensor readings | LOCAL | Read from hardware and displayed on-screen. Never transmitted. |
| Music and sound | LOCAL | What your music player is playing (which player, title, artist, album, cover, position, play state, shuffle and repeat), the volume, and the sound going to your speakers (never the microphone), read only while a pack widget that uses them is on screen. Never recorded, never transmitted. |
| Installed apps | LOCAL | The names and icons of your installed apps, read only while you have the app list open to choose an app for a button. While a button that opens an app is on screen, that app’s icon and whether it is running. Never transmitted. |
| Button settings | LOCAL | What each button does, and any picture you put on it, are kept in your settings. A button acts only when you tap or click it. Never transmitted. An exported layout leaves out what its buttons do; a button’s picture goes with it. |
| Application logs | LOCAL | Written to AppData. Never transmitted to Mr.Clu. |
| Version check | EXTERNAL | HTTPS request to mr-clu.com. No personal data in payload. IP address processed by Cloudflare per their policy, then reduced to the daily anonymous hash described in the Website section. |
| CLU Store | EXTERNAL | Only while the store is open. Fetches the catalogue, preview images and any template you install; sends a star rating only if you give one. See the CLU Store section below. |
Update check detail: CLU VIEW requests https://mr-clu.com/cluview-update.json shortly after it starts, once more about 10 minutes later, and then once every 24 hours while it stays running. It also checks whenever you press Check for Updates. CLU VIEW NOVA (2.x) additionally fetches a signed release manifest and, if you accept an update, downloads the installer. CLU’D IN behaves the same way as CLU VIEW NOVA, using cludin-update.json and its signed manifest cludin-latest.json. These requests are strictly domain-whitelisted to mr-clu.com, use HTTPS only, are limited in response size to prevent abuse, and contain no hardware data, no configuration and no personal identifier beyond the IP address inherent to any HTTPS request.
What is recorded: the update check writes at most one row per day for each internet address and application, holding the date, which application checked, and the daily anonymous hash described in the Website section. Nothing else, and no version number. Because that hash is re-salted every day it cannot be followed from one day to the next, so these rows indicate traffic rather than a count of people. Those rows are purged after 90 days along with the rest of the visit statistics.
Application
CLU VIEW — No Install Tracking
There is no install counter, and no persistent identifier unless you join, buy, recover purchases or redeem a Founder code
CLU VIEW does not count installations or create an identifier for free use. If you choose to join, buy, recover purchases or redeem a Founder code, it creates a random signing key for that installation and sends its public key with licence requests. This identifies a registered PC slot for your licence, without reading a hardware fingerprint. It is described in CLU VIEW Membership below.
What changed
Earlier CLU VIEW 2.0 builds did include an anonymous install counter: a random identifier generated on your PC at first run and sent, at most once a day, with the app version and whether you were on Windows or Linux. It was removed in full: the code, the setting, and the disclosure that described it.
If you are updating
The anonymous install-counter identifier in older configuration files is deleted when the new version starts. Free use sends no persistent identifier. Optional licence operations use the private licence credential and random PC public key described below.
What this cost, stated plainly
Mr.Clu can no longer say how many installations exist. Downloads and update checks are still counted, but only in aggregate against the daily rotating hash described in the Website section. That hash is deliberately re-salted every day, so it cannot be followed from one day to the next. It shows traffic, not a user count. That trade was made on purpose, in favour of free use carrying no persistent identifier.
Application
CLU VIEW CLU Store
Browsing, downloading, rating, and sharing a template of your own
The CLU Store lets you install dashboards other people have made. It is inert until you open it: nothing is fetched, and nothing is recorded, while you are simply using a dashboard.
Browsing and installing
What is sent: ordinary HTTPS requests to mr-clu.com for the catalogue, for preview images, and for the template file itself when you install one. No hardware data, no dashboard of yours, and no identifier are attached to any of them.
What is recorded: installing a template writes a download row (the date, which template, the country Cloudflare reports, and the same daily anonymous hash used everywhere else), and repeat installs of the same template from the same daily hash within an hour are counted once. That is what produces a template’s download count. Browsing the catalogue and viewing preview images record nothing. Download rows are purged after 90 days.
Rating a template
Rating is optional and only offered for templates you have installed. When you download a template the server issues a one-time token; if you rate it, CLU VIEW sends the star value with that token. What is stored is the template id, the number of stars, a hash of the token, and timestamps. The token itself is never stored, and the record contains nothing about you. The hash exists so one download cannot be counted as two votes. Ratings are kept for as long as the template is listed, because they are what produces its score.
Sharing a template of your own
Uploading is entirely optional and happens on this website, not inside the application: CLU VIEW opens mr-clu.com/upload in your own browser. If you submit a template, you provide a display name of your choosing (there is no account, and it does not have to be your real name), a title and description, the template file, and a preview image (required; a submission without one is rejected). Those are stored so the template can be listed, and the display name is published with it. Treat that field as public.
The upload is also recorded against the same daily anonymous hash, to enforce a submission limit of three per hour. That hash is additionally stored on the template’s own record for as long as the template exists, so a submission can be traced back to its other submissions if one has to be moderated; it is not covered by the routine analytics purge. The form is also checked by Cloudflare Turnstile, a privacy-preserving alternative to a CAPTCHA that confirms a human is submitting the form. Turnstile is operated by Cloudflare under its own privacy policy.
Submitted templates are reviewed by hand before they appear in the store. A template you submitted can be taken down on request. Email support@mr-clu.com.
Application
CLU VIEW Membership
Only if you connect one. Nothing here happens if you never do.
CLU VIEW works fully without a membership. Joining adds the monthly pick, 20% off whole packs and early access in the CLU Store. Buying content, joining or redeeming a Founder code connects a licence. Purchases stay on that licence when a membership ends. LIBRARY offers REFRESH PURCHASES for a recent payment and RECOVER PURCHASES after reinstalling or moving to another PC.
What is sent, and when
The private licence credential is sent over HTTPS for licence checks and purchase or membership actions. Each app licence request also sends its random PC public key, a timestamp, a one-use random request value and a signature covering the request. These identify a registered installation and prevent a copied licence credential alone from authenticating another PC. Automatic licence refresh remains at most once per day; opening or refreshing the Store and using its controls can make additional requests. Checkout and recovery use random claims, with the app checking an active claim every three seconds for up to 30 minutes. A download of owned content sends a signed entitlement token. No hardware details, sensor readings, layouts or user name are sent. The app identifies itself as CLU-VIEW and its version number.
Payments and your card. You pay on Link's page. CLU VIEW and mr-clu.com never see your card number. To show the MEMBERSHIP tab, the licence service asks Stripe for your plan, next payment, card brand and last 4 digits; those card details are not stored. Stripe supplies the payment email to deliver a receipt or recovery message; the licence database does not store the email. Link handles payment, receipts and its customer data under its privacy policy. Checkout and recovery store short-lived random claims and email lookup hashes, as described below.
Licence identifiers. Your private licence credential and random PC public key link checks to your licence and its purchases, Founder code or gift. Up to five registered installations may be connected. Recovery on the same registered installation uses its existing slot. When all slots are occupied, the owner chooses a slot to disconnect; the service never silently removes a different PC. This is a registration limit, not a hardware fingerprint or a guarantee against copying all local credentials.
The earlier payment-email recovery flow starts in CLU VIEW on the PC you want to connect. Where that flow is available, the website asks for your payment email and uses Cloudflare Turnstile to limit automated requests. The licence service looks up the email with the payment provider, handles it in memory, and keeps only short-lived hashed lookup and recovery values. Its response does not reveal whether an email has purchases. The emailed link expires after 15 minutes and requires you to match a code in CLU VIEW before explicitly approving the PC. Recovery pages run no analytics, save no credentials in browser storage, and remove the email token from the address before making requests. Sensitive billing and deletion actions require a recent ownership approval. If automated recovery fails, MR.CLU can verify your receipt or Founder record and issue a single-use approval for the waiting PC through the protected support dashboard. Support records include the ticket reference and a hashed administrator identifier.
On your PC
The private licence credential and private signing key stay beside CLU VIEW settings. Windows protects them for your Windows user through DPAPI; Linux limits their files to that user. They are not emailed, displayed, copied to the clipboard, returned to website pages, or included in exported layouts, diagnostics or logs. Your Support ID is displayed for help. Removing the local settings can remove these credentials; purchase recovery reconnects the original licence after ownership verification. Installed purchases remain available offline.
What the licence database holds
For each licence the database holds a random licence ID and Support ID; accepted terms version; source, status and paid-through date; eligible monthly-pick periods; owned content and its prices; payment-provider references; and one-way access-credential hashes with public keys for up to five registered installations. It also holds checkout claims, hashed recovery tokens, short-lived request values to prevent replay, temporary ownership approvals, receipt-delivery records and licence activity. The service keeps today's check count and the highest daily count in the last 30 days to review abuse. A short-lived native-app claim may hold encrypted credentials and a signed token for delivery only to its initiating app. Payment email is processed temporarily to send a receipt or recovery link; it is not stored in the licence database. No hardware fingerprint, stored name, raw IP address or card number is held there.
Founders are decided from Patreon and Discord records outside the licence service, and I send codes by hand. Codes are stored as hashes. Each code is issued to one email address. The licence service does not keep that address: beside the code it keeps a keyed one-way fingerprint of it, so that only a shop account with that verified address can use the code. When you enter the code, the verified email of your shop account is fetched from WorkOS, compared and not stored. The fingerprint is erased when the code is used or cancelled. If you ask me to erase it before you use your code, I cancel the code. CLU VIEW does not link to or sync with Patreon. Legacy Founder eligibility hashes and encrypted review records from the earlier testing design are not automatically cleared by switching syncing off; any retained records remain subject to review and deletion. Their absence in the production database must be verified before launch.
IP addresses. Cloudflare sees your IP address when the app contacts mr-clu.com, as for any web request. The licence service does not store it, and its request logging is switched off.
How long it is kept
Removed access credentials: 90 days. Licence activity logs: 730 days. Checkout and recovery app claims expire after 30 minutes; encrypted native-app delivery copies are removed on acknowledgement or the next daily purge after expiry. Recovery links are single-use and expire after 15 minutes. Ownership approval for billing changes or licence deletion lasts 10 minutes. Request-replay values expire after four minutes and are removed by the daily purge. Receipt-delivery records are retained for 90 days; failed receipt sending retries for up to seven days without storing or emailing an access key. Old encrypted key-email retry records are cleared during maintenance without sending keys. Processed payment-event references, deletion replay tombstones and completed payment-replay jobs: 90 days; unresolved jobs remain for review. Daily member download counters are cleared by the next daily sweep. Aggregate service metrics: 396 days. A lapsed subscription-only licence can be purged after 730 days; Founder, lifetime and pack source records, including refunded pack records, prevent that automatic purge. Payment ledgers and reservations follow their licence's retention. You can request deletion at any time.
Where. In a Cloudflare D1 database. The primary region requested is Oceania; Cloudflare does not guarantee it, and read replication is switched off.
Why (lawful basis). Providing the membership you asked for (contract), and stopping key sharing and abuse (legitimate interests).
If something goes wrong. If the licence database is ever exposed, Mr.Clu will tell the people affected and, where the law requires, the regulator, within 72 hours of finding out.
Application
VU1 Dial Controller
What VU1 Dial Controller stores locally and the optional weather feature’s external contacts
VU1 Dial Controller stores all configuration locally, including dial assignments, theme settings, and serial port preferences. None of this data is transmitted to Mr.Clu.
| Data Type | Where It Stays | Detail |
|---|---|---|
| Dial configuration | LOCAL | Stored in AppData. Never transmitted. |
| Hardware readings | LOCAL | CPU, GPU, RAM, fan data read and displayed locally. Never transmitted. |
| Audio data | LOCAL | Captured and processed locally via WASAPI. Never transmitted. |
| IP geolocation (weather) | OPTIONAL | Sent to ipapi.co when weather feature is first enabled. Returns approximate location. See below. |
| Weather query | OPTIONAL | Lat/lon co-ordinates sent to Open-Meteo. Returns weather data. See below. |
| Location co-ordinates | LOCAL | Stored locally after ipapi.co lookup. Used for Open-Meteo requests. Not sent to Mr.Clu. |
| Update check | MR.CLU | Automatic on start-up: fetches mr-clu.com/vu1-update.json and compares the version number. No payload beyond the request itself. |
Weather feature, step by step: When you enable the weather feature for the first time, or when you request a location refresh, the following sequence occurs:
https://ipapi.co/json/. Your device’s IP address is transmitted to ipapi.co. It returns your approximate city name, country, latitude, and longitude. The returned co-ordinates are stored locally. Governed by ipapi.co’s Privacy Policy.https://api.open-meteo.com/v1/forecast with the latitude and longitude from Step 1. No additional personal data is included. Governed by Open-Meteo’s Terms of Service.If the weather feature is never enabled, neither request is ever made. You can disable the weather feature at any time in the application settings, after which no further requests to ipapi.co or Open-Meteo will be made.
Application
Spec Card Generator
Fully local: hardware data and images never leave your machine
SPEC CARD 2 reads hardware information through Windows APIs (WMI, DXGI, the display configuration API, NVML on NVIDIA cards, and HWiNFO or LibreHardwareMonitor if you run them): CPU, GPU, memory modules, drives and free space, motherboard and BIOS, monitors, network adapters, audio and USB device names, uptime, and live temperatures, loads and clocks. Spec Card Generator 1.x reads CPU model, GPU model, RAM capacity, storage devices and display details using the systeminformation library. For CPU temperature, fan speeds and voltages, SPEC CARD 2 can run with administrator access and use the PawnIO hardware driver; both happen only after your explicit yes, and an in-app update never installs the driver. In both versions everything is read on your machine and rendered on your machine. Nothing is transmitted. The one outbound request is the update check described in the Overview: on start-up the app fetches mr-clu.com/speccard-update.json and compares the version number, sending nothing beyond the request itself.
Generated spec card images are saved to a location you choose on your local file system. If you subsequently share a generated image via a third-party service (Discord, Reddit, social media, etc.), that service’s own privacy policy governs what happens to the image once you upload it.
Application
CLU’D IN — Gaming Diagnostics
All diagnostics stay local; the only network activity is the update check
CLU’D IN stores gaming session data, hardware readings, crash records, and diagnostic logs in a local SQLite database on your PC. None of it is transmitted to Mr.Clu or any external service.
Its only outbound network activity is the update check described above: a request to https://mr-clu.com/cludin-update.json at startup and whenever you press Check for Updates, carrying no hardware data, no configuration, no version number and no identifier beyond the IP address inherent to any HTTPS request. If an update exists and you accept it, the app fetches the signed release manifest and downloads the installer from mr-clu.com, verifying its cryptographic signature before running it.
As development progresses and new features are added, this section will be updated to reflect any changes to data handling before those features are released.
Website
Cookies & Tracking
What cookies are set and by whom when you visit mr-clu.com
Ordinary visitors get no cookie from Mr.Clu. Two exceptions, both strictly necessary sign-in cookies that page scripts cannot read: the owner’s private dashboard sets __Host-mcd when MR.CLU signs in to it (it lasts at most 12 hours), and the CLU Store sign-in uses cookies whose names start with __Host-clu-shop-. Mr.Clu does not use advertising networks, social media tracking pixels, session replay tools, heatmap tools, or any third-party analytics platform. The site’s own visit counter (described above) is cookieless by design.
The website uses a few plain flags in your browser’s local storage. None of them contains an identifier and none is sent to any third party:
mrclu_seen, mc_seen): simple yes/no markers so the site can adjust what it highlights for returning visitors. No identifier is created or transmitted.mc_sid in sessionStorage): a random value used by the visit counter to group the pages viewed in one tab; deleted automatically when the tab closes.mc_ignore for the analytics opt-out, or remembering a banner you dismissed): stored only in your browser.__cf_bm, cf_clearance) to protect the site from abuse. These are not advertising cookies and are not set by Mr.Clu.CLU VIEW shop sign-in opens in your browser and uses the account cookies described above. Free desktop features work without a shop account.
External Services
Third-Party Services & Links
Services linked from the website or integrated into Mr.Clu software
The Website and Software may link to or integrate with the following third-party services. Each service operates independently under its own terms and privacy policy. Mr.Clu has no control over, and accepts no responsibility for, any third party’s data practices.
| Service | Context | Privacy Policy |
|---|---|---|
| Cloudflare | Hosting, CDN, security | cloudflare.com/privacypolicy |
| Microsoft (WebView2 Runtime) | CLU VIEW Windows installer only, when the PC does not already have it | privacy.microsoft.com |
| Link (Stripe) | Membership and pack checkout, receipts, payment support and billing management on Link's pages | link.com/privacy |
| Cloudflare Turnstile | Human check on the CLU Store upload and purchase recovery forms | cloudflare.com/privacypolicy |
| YouTube | CLU VIEW videos. Home page: loads and plays muted when you scroll to the video. /cluview: loads only after you press play. Both use youtube-nocookie.com (YouTube’s privacy-enhanced mode) | policies.google.com/privacy |
| ipapi.co | VU1 weather location lookup (optional) | ipapi.co/privacy |
| Open-Meteo | VU1 weather data (optional) | open-meteo.com/en/terms |
| Buy Me a Coffee | Optional voluntary support (linked from Website) | buymeacoffee.com/privacy-policy |
| Patreon | Voluntary support, early builds and older packs. CLU VIEW does not connect to Patreon. The owner dashboard reads aggregate campaign counts. | patreon.com/policy/privacy |
| Discord | Community server (linked from Website and Software) | discord.com/privacy |
| Google Forms | Bug report form (linked from Website and Software). Whatever you type into it goes to Google, not to this site | policies.google.com/privacy |
Security
Data Security
How data in transit and at rest is protected
Because Mr.Clu applications keep your data on your own machine, the primary security responsibility for locally stored application data (profiles, configurations, logs) rests with your own device and OS security practices. The website’s visit statistics are anonymised before storage and held in a private database accessible only to Mr.Clu.
All outbound network communication from Mr.Clu Software uses HTTPS (TLS). The CLU VIEW update checker enforces a strict domain whitelist and response-size limit to reduce exposure to malicious responses.
If you discover a security vulnerability in any Mr.Clu Software or this website, please report it responsibly by emailing support@mr-clu.com before public disclosure, allowing time for a fix to be developed.
Age
Children’s Privacy
Mr.Clu software is not directed at children
Mr.Clu Software and this Website are not directed at children under 13 years of age (or the applicable minimum digital age in your jurisdiction, which may be higher). Mr.Clu does not knowingly collect personal information from children.
If you believe that a child has provided personal information through any Mr.Clu channel, please notify support@mr-clu.com and any such information will be promptly deleted.
Rights
Your Privacy Rights
Your rights under GDPR, UK GDPR, CCPA, and similar laws
Most data never leaves your PC, so most rights are exercised by managing local files. Website visit statistics are anonymous and deleted after 90 days. For licence data, CLU Store > MEMBERSHIP > REQUEST MY DATA shows your record. DELETE MEMBERSHIP cancels any running subscription immediately and deletes the licence, keys and owned-content records, so those packs cannot be downloaded again. Installed packs keep working. A Founder licence cannot be restored. Limited hashed payment replay tombstones and processed-event references remain for 90 days to prevent delayed events recreating a deleted licence; licence activity records retain an anonymous deletion action. Without the app, email support@mr-clu.com with your Support ID or from the email you paid with. Requests are answered within one month. Link holds its own payment data: contact Link support for its deletion process, which cancels subscriptions sold through Link.
EU / UK GDPR Rights
If you are in the European Economic Area or United Kingdom, you have the following rights regarding personal data that Mr.Clu processes (which for the website is limited to the anonymised, short-lived visit statistics described above):
You can complain to your data protection regulator (the OAIC in Australia, the ICO in the UK, or your national authority in the EU). For any request, contact support@mr-clu.com.
California Residents (CCPA / CPRA)
California residents have specific rights under the California Consumer Privacy Act. Mr.Clu does not sell or share personal information. Mr.Clu does not use personal information for cross-context behavioural advertising. Access and deletion work as described above; there is nothing to opt out of, because nothing is sold. For any California privacy request, contact support@mr-clu.com.
Updates
Changes to This Policy
How and when this privacy policy is updated
This Privacy Policy may be updated from time to time to reflect changes in Mr.Clu software features, applicable law, or third-party services. Significant changes will be posted on this page with a revised “Last updated” date. For material changes affecting your rights, Mr.Clu may additionally post a notice in the Software or on the Website.
Continued use of the Services after a revised policy is posted constitutes acceptance of the revised policy. If you disagree with any change, stop using the affected Software or Website features.
Contact
Privacy Questions & Requests
How to reach Mr.Clu about this policy
For privacy questions, data-subject rights requests, security vulnerability reports, or any concerns about this policy, email support@mr-clu.com. Please include “Privacy” or “Security” in the subject line as appropriate.
The controller for the licence database is Nathan Blake Wood trading as MR.CLU SOFTWARE, ABN 85 428 650 614, Victoria, Australia. Contact: support@mr-clu.com.
Related documents: Terms of Use • Licenses & Attributions