Privacy
Short, because there is not much to say. This site sets no cookies, runs no analytics and loads nothing from anyone else.
Last updated 4 October 2026
Who is responsible
RigDesk is made and run by Ivan Yordanov (Иван Йорданов), a private individual in Bulgaria. That person is the data controller for everything described below, and the way to reach them is support@rigdesk.app. There is no company behind this, no team, and nobody else who gets a say in what happens to your data.
This website
- No cookies. The site does not set a single one.
- No analytics, no trackers, no advertising pixels. There is no Google Analytics, no Facebook pixel, nothing of that kind in the page.
- Fonts are served from here, not from Google Fonts — so no third party learns that you visited.
- The page fetches only its own files:
downloads/release.jsonfor the current version and its fingerprint,downloads/changelog.jsonfor the list of changes, andclip/shockpoint.js, the game shown in the video at the top. The film under it comes frommedia/on this site too, and only once you press play. All of it comes from here and sends nothing back.
One thing is stored in your browser: if you close the privacy notice at the
bottom of the front page, that choice is remembered in
localStorage so it does not come back on every visit. It is a
single yes/no, it never leaves your device, and clearing your browser data
removes it.
Server logs
The site is hosted on Cloudflare. Like every web host, it records ordinary request logs — IP address, time, which file was asked for — which exist so the thing can run and be defended from abuse. We do not build profiles from them and do not pass them to anyone.
Why we are allowed to: legitimate interest — a site that cannot see its own traffic cannot be kept running or defended.
Counting downloads
When the app file is downloaded — from this site, or as an update inside RigDesk — a number goes up by one, together with which file it was. That is all that is kept: a count, with nobody in it.
So that one download is not counted twice (Android often asks for the same file twice in a row), a one-way hash of your IP address together with the file and the date lives for ten minutes and is then gone. It cannot be turned back into the address and is not tied to anything else. No cookie, nothing on your device.
Why we are allowed to: legitimate interest — knowing how many people get RigDesk, with the least data that can answer the question.
The RigDesk app
Your profile stays on the phone. Email, password, nickname, picture and friends live in a file inside the app, encrypted with a key from the phone's hardware keystore. There is no server holding your account, and no way for us to read it.
Two things do leave the phone, both small and both listed here:
- A counter. When a profile is created, when RigDesk is opened
with a profile, and when a login code is emailed, the app sends the
SHA-256 of the email address and which of those three
happened — nothing else. It exists so we can see how many people use RigDesk.
It carries no email, no password, no name, no phone model, no list of your
programs. See
core/system/RigDeskPulse.ktin the app. - The code email. To verify an address, the app asks our mail
relay to send a six-digit code to it. The relay is a Google Apps
Script running under the author's own Google account, so the address
passes through Google on its way to you. It is used for that one message and
for the relay's own limits against abuse — one code a minute, ten an hour
per address, sixty a day in total. See
tools/mail-relay/apps-script.gs.
Why we are allowed to: the code email is the thing you asked for when you started making a profile, so sending it is necessary to do what you requested. The counter is a legitimate interest — knowing how many people use RigDesk, with the least data that can answer the question. It is a hash, it is never matched to a name, nothing is profiled, and it goes if you ask.
Payments
The store is not open yet. When it is, checkout runs on Paddle, who are the merchant of record — that is, the seller you actually buy from. They handle the card details, the invoice and the tax, and none of it reaches us or the app.
What comes back to us is which item was paid for and the same SHA-256 of the
email, kept under acc:<hash> so a purchase can be matched to a
profile. For RD Pass, which is a monthly subscription, we also
keep the status and the renewal date exactly as Paddle reports them.
Why we are allowed to: without it there is no way to know what you bought, so it is necessary in order to give you the thing you paid for.
Bug reports
If you send a report through rigdesk.app/bug, we keep exactly what
you typed into the form: what went wrong, how to make it happen again, where in
RigDesk, the phone, the Android version and the RigDesk version — and an
email address only if you chose to give one, so we can answer you.
It is stored with Cloudflare under bug:, and a copy arrives as an email
in the author's own Gmail inbox so it gets read the same day. Nobody else reads it.
Your IP address is not stored. To stop one sender from flooding the
form, a one-way hash of it together with the date lives for one hour and allows
five reports in that hour; after that it is gone and cannot be tied to anything.
See worker/index.js, handleBug.
Why we are allowed to: you asked us to look at a problem, and the report is what that takes — necessary for what you requested. The one-hour limit is a legitimate interest: keeping the form usable.
How long any of it is kept
- The one-per-person marker (
made:) — two years, so reinstalling does not count you twice. After that it goes, and a fresh install counts as new. - "Opened recently" (
who:) — thirty days, then it expires by itself. This is what "active" is counted from. - "A code went here today" (
mailed:) — two days. This is what stops one address being mailed over and over. - Purchases and RD Pass (
acc:) — for as long as you own them, because they are what unlocks what you bought. Ask and they go. - "This file was just downloaded from here" (
dlseen:) — ten minutes. A one-way hash, only so one download is counted once. - Daily totals — ninety days. Plain numbers with nobody's data in them.
- Bug reports (
bug:) — one year, then they expire by themselves. Ask and yours goes sooner. - The report limit (
bugrl:) — one hour. - Server logs — kept by Cloudflare on its own schedule. We do not export them, copy them, or keep any of our own.
Who else sees any of it
Three companies, each for one job and nothing besides:
- Cloudflare — hosts the site and holds the counters and the bug reports.
- Google — the mail relay is an Apps Script, so an address passes through Google to become an email; and a bug report you send lands in the author's Gmail inbox.
- Paddle — the seller of record for anything you buy.
Cloudflare and Google are in the United States and Paddle is in the United Kingdom, so that data leaves the EU. Each of them publishes the standard safeguards for such transfers, none of them is given anything beyond what is listed above, and nothing is ever sold to anyone.
Children
RigDesk is not aimed at children under 13 and asks for nothing from them.
Your rights, and how to use them
Since your profile is on your phone, deleting it in the app deletes it — there is no copy here to ask about. For the few things that did leave the phone, you have all of these:
- To see it — what is held about you, and why.
- To correct it, if it is wrong.
- To have it deleted.
- To have it frozen rather than deleted, while something is being sorted out.
- To object to the counter, which runs on legitimate interest. Object, and it stops for you.
- To take it with you, in a file a machine can read.
Write to support@rigdesk.app and say what you want. There is no form to fill in and no account to log into — an email is enough, and it is answered within a month.
If the answer does not satisfy you, you can complain to the Bulgarian supervisory authority, the Commission for Personal Data Protection (cpdp.bg), or to the one in the country where you live. You do not need our permission and you do not have to ask us first.
If this changes
Anything new that leaves your device gets written here on the same day it ships, with the file it lives in. If it is not on this page, RigDesk does not do it.
Which rules this page follows
The law asks for the facts, not for article numbers on the page. They are here anyway, so that anyone who wants to check can do it without guessing which paragraph is meant to answer what. Everything refers to the GDPR, Regulation (EU) 2016/679.
- Who is responsible — Art. 13(1)(a).
- Why we are allowed to, in each section — Art. 13(1)(c) with Art. 6: necessary for what you asked for, 6(1)(b); legitimate interest, 6(1)(f).
- Who else sees any of it — Art. 13(1)(e), and Art. 13(1)(f) for the United States.
- How long any of it is kept — Art. 13(2)(a), and the storage-limitation rule of Art. 5(1)(e).
- Your rights — Art. 13(2)(b), and Arts. 15 to 21 for the rights themselves.
- Complaining — Art. 13(2)(d).
Ownership and copyright
RigDesk — the app, its source code, this website, the name “RigDesk”, the RD mark, the icons and the artwork inside RigDesk Designs — is the original work of its author and is protected by copyright. © 2026 RigDesk. All rights reserved.
You may install and use RigDesk on your own devices. You may not copy, republish, sell or redistribute it, ship a modified build, or reuse the name, the logo or the artwork in your own product — whether or not you charge for it. Reverse engineering beyond what the law expressly allows is not permitted either.
If you want to build on RigDesk, use part of it, or work together on it, that is a conversation, not a refusal — write to support@rigdesk.app and ask. Permission given in writing is the only kind that counts.
RigDesk runs Windows programs through Wine (LGPL) and other open-source components. They keep their own licences and their own copyright holders, and nothing above claims any right over them. The Wine build RigDesk downloads is unmodified upstream Wine, and its source stays public at desk-wine-dist.