← Faderia

Privacy Policy

This policy explains what personal data Faderia processes on the website, in your account, in the licence service and in the desktop app. We collect what the service needs to work and nothing for advertising.

This English text is the authoritative version. Translations are provided for convenience; in case of any discrepancy, the English text prevails.

1. Who is responsible

Faderia is provided by Egor Markin, a self-employed individual. Contact for anything in this policy: [email protected].

2. Your account

When you register we store your email address, an optional name and your password as a salted hash (never the password itself). For your purchases we store the IDs Paddle gives us for your customer record, subscription and transaction, your plan, billing interval and renewal date. We do not receive or store card details or billing addresses: Paddle handles those.

If you arrived through a partner or referral link (?from= on the pricing page), that tag is remembered in your browser and saved with the licence you buy, so we know which channel brought the purchase.

We need this data to provide your account and licence (performance of a contract).

3. Licence activation

When you activate a licence in the desktop app, the app sends our licence server:

  • the licence key;
  • a machine identifier: a SHA-256 hash of the Windows installation ID (on Windows) or the hardware UUID (on macOS); if neither is available, of the computer name, user name and home folder;
  • the computer name as set in your operating system;
  • the app version.

The server stores the machine identifier, computer name and app version with your licence, so you can see and free your computers in your account. Each activation attempt is also logged with the machine identifier and your IP address, to detect keys being shared or resold. After activation the app works offline; it does not report back to us to keep the licence alive.

Signing the app in to your account

Signing in is optional and separate from the licence. If you press Sign in in the app, it sends our server the computer name, the machine identifier described above and the app version, and opens your account in the browser, where you confirm the sign-in. The server then stores, with your account, a session for that computer: the computer name, machine identifier, app version, when it signed in and when it was last seen (updated at most once an hour). The app keeps the session token in your operating system's key store.

While signed in, the app checks with our server when it starts that the session is still valid. You can see and sign out your computers in your account under Consoles; signing out in the app, or changing or resetting your password, ends the session. Sessions are deleted together with your account.

4. Usage statistics (optional)

The desktop app can send usage statistics, but only if you turn this on: it is off by default and the app asks once. If enabled, once a day it sends the app version, operating system, how many days, sessions and minutes the app was used, counters of which tabs, features and first steps were used, and the vendor and product IDs (vendor:product, without names or serial numbers) of up to 16 USB devices connected to the computer. Among the feature counters are the AI assistant's: in how many sessions an AI client connected, how often it read or diagnosed the show, how many of its proposals were applied, rejected or did not apply, and how often it hit the plan limit — numbers only, never fixture names or text from the model. There are also counters of the plan offer shown at the free channel limit: how often it was opened and whether the yearly, monthly or a higher plan was chosen. The report carries the same machine identifier as activation, so it is pseudonymous, not anonymous. We use it to decide what to improve and, by matching it with a licence activated on the same computer, to see whether people who saw the plan offer went on to buy. You can turn it off at any time in the app settings; turning it off stops future reports. Clearing the counters in the app deletes them on your computer only — to delete reports already sent, write to us.

The legal basis is your consent.

5. Updates, downloads and crash reports

  • Update checks. Installed copies ask our server for updates every few hours. The request contains a random installation ID generated by the updater (not linked to your licence or account); we do not store these requests.
  • Downloads. Installers are hosted on GitHub. When you click Download, our server redirects your browser to GitHub, which then sees your IP address like any website you visit. We count downloads per day by platform and by the tag of the link you followed (?from=) — a number only, without your IP address, cookies or any identifier.
  • Crash reports are not sent automatically. "Report a problem" saves a text file on your computer; you decide whether to send it to us.
  • Philips Hue. If you search for Hue bridges in the app, it asks Signify's discovery service (discovery.meethue.com) for bridges on your network.

6. Emails

We send only service emails: address confirmation, password reset, a notice to the old address when you change it, and notices about your licence key (for example a new key after a block). Receipts and invoices come from Paddle. We send no newsletters or marketing.

7. Cookies and browser storage

  • phx_customer — keeps you signed in; necessary; expires after 14 days.
  • faderia-theme (browser storage) — your light/dark choice.
  • faderia-source (browser storage) — the partner tag from a ?from= link, see section 2.

We use no advertising or tracking cookies. To count visits to the website we use Cloudflare Web Analytics: it sets no cookies, uses no browser storage and does not follow you across websites; we see only aggregate numbers — pages viewed, the sites visitors came from, countries, device types and page load speed. Prices on our pages come from our own server. Paddle's script — which may use its own cookies and Paddle's customer-retention service — loads only on the checkout page, once you choose to pay; see Paddle's privacy notice.

8. Who else processes data

  • Paddle.com — our reseller and Merchant of Record: checkout, payments, taxes, receipts, refunds. To show prices in your currency we pass your country (as detected by our network provider) to Paddle. At checkout we pass your email address and account ID. Paddle is responsible for payment data under its own privacy notice.
  • Resend — delivers our service emails; receives your email address and the email content.
  • Cloudflare — carries all traffic to our website and licence server, and counts website visits (Web Analytics, see section 7).
  • GitHub — hosts the installers you download.

We do not sell personal data.

9. How long we keep data

  • Account data — until you delete your account.
  • Activation attempt logs (with IP addresses) and the audit log — records older than 90 days are removed during routine clean-up.
  • Licences and computer records — kept with the licence, because they are part of the purchase record, also after you delete your account.
  • Usage reports — kept until you ask us to delete them.
  • Backups — a nightly copy of the database is kept in private storage for about 14 days.

10. Deleting your account

You can delete your account in the account settings (once no subscription is active). This removes your account data. Licences you bought and their computer records remain, no longer linked to an account. Audit log entries, which can include your email address, are removed with the 90-day clean-up. Paddle keeps its own records of your purchases as required by tax law, and backups roll over within about 14 days. If you want the remaining records removed sooner, write to us.

11. Your rights

Depending on where you live, you can ask for access to your data, a copy of it, correction, deletion, restriction of processing, or object to processing, and you can complain to a data protection authority. Write to [email protected]; we answer within 30 days.

12. Children

Faderia is not directed at children under 16.

13. Changes

We may update this policy. The date at the top shows the latest version.

Updated: 2026-10-27 · rev. 4

EnglishРусскийEspañolDeutsch