Privacy Policy

01Who we are

Ondřej Šumbera, Město Touškov, Školní náměstí 4, 33033, registration no. 05808685 ("we", "the operator") runs cliphearth.com and publishes the ClipHearth desktop application. We are the data controller for the processing described in this policy.

Contact: info@cliphearth.com. We have not appointed a data protection officer; use the same address for anything related to your personal data.

Payments are processed by Stripe, and Link (Stripe's payment service) is the merchant of record for every purchase made on this website. Stripe is an independent controller for the payment data it collects on its own checkout pages; its privacy policy applies to that part of the purchase.

02What this policy covers

This policy covers:

• visits to cliphearth.com, including the contact form,
• what reaches us when you buy or renew a licence through Stripe,
• the ClipHearth desktop app and the activation and update service it talks to,
• the e-mails we send you about your licence or your questions.

It does not cover the websites you open inside the app's built-in browser. Those sites see your visit as they would from any browser. ClipHearth does not report to us which pages you visit or which files you download, convert or edit. The browser's history, favourites and the cookies of the sites you visit stay on your computer. Its filters for ads, trackers and cookie prompts run on your computer from lists that ship with the app, so they send nothing to us or to the authors of the lists.

03Visiting the website

When you open cliphearth.com, our web server records the usual technical log: your IP address, the time, the page requested, the referring page and your browser's user-agent string. We use these logs to run and secure the site (legal basis: our legitimate interest, Art. 6(1)(f) GDPR). Log files rotate automatically and are kept for a few days.

The site is delivered through Cloudflare, which acts as our content delivery network and protection against attacks. Cloudflare sees the same connection data and may set a security cookie only when it needs to verify suspicious traffic (see the Cookie policy).

Fonts, images and scripts are served from our own domain. No third-party fonts, embeds or tracking scripts load unless you allow an optional category in the cookie settings.

04Website analytics

We measure how cliphearth.com is used without cookies, local storage or any identifier stored on your device. When a page loads, your browser sends us the page path, the domain you came from and, if present, a campaign tag. Our server derives a temporary visitor number from your IP address and browser signature using a secret key that exists only in memory and changes every day; the IP address itself is never stored, and once the key rotates the number cannot be linked back to you. We keep only daily totals: page views, unique visitors, referring domains, country, operating system and downloads.

We honour the Global Privacy Control and Do Not Track signals: if your browser sends either, no analytics request is made. Download links pass through our server so we can count downloads per platform; this records the file, the country, the day, the campaign tag of the link you arrived with and whether the request came from a click on our site or on another web page (read from the standard headers every current browser sends), nothing about you.

We designed this measurement so that nothing is stored on or read from your device and the figures we keep cannot identify you, which is why we do not ask for consent for it. The brief handling of your IP address and browser signature in memory is based on our legitimate interest in knowing how the website is used (Art. 6(1)(f)). You can object at any time: switch on Global Privacy Control or Do Not Track in your browser, or write to us.

If you allow Analytics in the cookie settings, we additionally store a random visitor id (ch-vid) in your browser so that we can recognise returning visits and see which pages lead to downloads and purchases. That id is sent only to our own servers and is deleted when you withdraw the choice (legal basis: consent, Art. 6(1)(a)).

05Contact form and e-mail

When you use the contact form or write to us, we process your name, e-mail address and message in order to answer you (legal basis: steps prior to a contract and our legitimate interest in handling enquiries, Art. 6(1)(b) and (f)). The form sends your message by e-mail to our mailbox through Brevo, our e-mail provider; the website does not store it. We keep the correspondence for 24 months after the last exchange, unless it relates to a purchase or a legal claim.

To keep automated spam out, the form uses Cloudflare Turnstile. When you scroll to the form, your browser loads it from Cloudflare, which checks technical signals such as your IP address, TLS fingerprint and user agent to tell people from bots, and gives the form a one-time token that our server confirms with Cloudflare before sending the message (legal basis: our legitimate interest in protecting the form and our mailbox, Art. 6(1)(f)). Cloudflare describes this processing in its Turnstile privacy addendum.

06Buying or renewing a licence, adding computers

Checkout happens on pages hosted by Stripe. Your card or other payment details, billing address and country are entered there and processed by Stripe and Link, the merchant of record. We never see your card number.

From Stripe we receive, and store together with your order:

• your e-mail address,
• the checkout session, customer and (for subscriptions) subscription identifiers,
• the plan, amount, currency and payment status, including later refund or dispute events.

If you came through a partner's link or a campaign link, we also store that label (for example a partner code) with the order, so that we can pay commissions and see which links work. The label identifies the link, not you.

After a confirmed payment we create your licence on our activation server, where the key is stored only as a keyed hash, and we keep an encrypted copy of the key with your order so that support can find it for you. The key is shown on the confirmation page and sent to your e-mail address through Brevo, our transactional e-mail provider.

On the renewal page you can enter your activation key or licence id; it is used to look up the licence and start the renewal checkout.

On the Add computers page you enter your activation key or licence ID to add computers to a lifetime licence. The page shows only the plan and the number of computers, never the e-mail address of the licence or the names of its computers. Whoever pays enters their own e-mail address at checkout, and we store the order like a purchase, with the licence it is for and the number of computers. We e-mail the payer a confirmation without the licence key and, if the licence was bought with a different e-mail address, send that address a short notice that computers were added. If a payment for extra computers is refunded or disputed and computers have to be released from the licence, we e-mail the address the licence was bought with the names and platforms of the released computers, taken from the activation records (see Activation and licence checks below).

Legal basis: performance of the contract (Art. 6(1)(b)) and our legal obligations to keep business records (Art. 6(1)(c)); the invoice for your purchase is issued by Link.

Retention. We keep your order with its personal data for as long as the licence is valid and for three years after it ends - after a refund or revocation, or after the last paid period of a subscription. A lifetime licence stays valid, so its order is kept so that we can help you recover your key. Orders for extra computers are kept and anonymised together with the licence they belong to. Checkouts that were never paid are kept for 90 days. After these periods we anonymise the order automatically: your e-mail address, the Stripe identifiers, the licence link and the stored key are removed, and only anonymous figures remain (plan, amount, currency, status and date) for our statistics. Payout records from Stripe, which contain amounts but no contact details, are kept for as long as tax and accounting law requires.

07Partners, resellers and free licences

When we work with a reseller, affiliate or business customer, we process the contact person's name and e-mail address, the licence keys we issue to them, the related orders and the commission statements (legal basis: performance of the contract and our legal obligation to keep business records). When we send a free licence - for example to a reviewer - we process the recipient's e-mail address, the key and the reason it was issued (legal basis: our legitimate interest in promoting ClipHearth).

Contact e-mail addresses of partners are removed three years after the last issued batch or after the partnership ends. Free licences follow the same rule as purchases: kept while the licence is valid and anonymised three years after it ends. Commission statements are kept for as long as tax and accounting law requires.

08The ClipHearth desktop app

ClipHearth runs on your computer: downloading, converting and editing happen locally. The app contacts our activation server only for the purposes below. It contains no analytics or telemetry and never sends us the pages you visit or the files you process.

Device identifier. Several requests carry a device identifier: a SHA-256 hash of a stable machine identifier and your operating-system user name. It cannot be turned back into those values; it only lets the server recognise the same computer again. Where the server records your IP address, it stores only an HMAC-SHA256 hash computed with a secret key that never leaves the server. To limit how many requests one address can make, the server also uses your IP address for a few minutes in memory, without storing it.

Statistics. From the records described below, the activation server works out daily totals for our admin, such as how many computers started ClipHearth for the first time, began or used up the trial, or activated a licence, by platform. The totals hold only counts, never a device identifier, an IP address hash or an e-mail address, and the app itself sends nothing extra for them. Basis: our legitimate interest in knowing how ClipHearth is used without any analytics in the app.

Accepting the terms on first start

The version and checksum of the terms, the device identifier, your platform and app version; the server adds the hashed IP address and browser-style user-agent of the app. Purpose: proof that the terms were accepted. Basis: legitimate interest and legal obligations.

Free trial

The device identifier, platform and app version, so that 3 free tasks per computer can be counted; the hashed IP address is used for a daily limit on new trial devices per network. Basis: performance of the pre-contractual trial and legitimate interest in preventing abuse.

Activation and licence checks

The device identifier, your computer's name (so you can recognise the device), platform, app version and hashed IP address. Your key is stored on the server only as a keyed hash. While you use the app, it confirms the licence with the server using the device identifier, platform and app version; a confirmation is reused for a few minutes and renewed at least once a day. Without a connection the app keeps working for a limited number of tasks and days. If the app loses its local licence file, it can ask the server to restore the licence for this computer; that request carries the same device identifier, platform and app version. Purpose: binding the licence to your computer, device limits and revocation. Basis: performance of the contract.

Update check

Only the app version, platform and update channel in the request - no device identifier - plus the IP address in our server log. On Linux, the .deb package adds our apt repository, so your package manager fetches ClipHearth updates from our server in the same way: nothing but the request and your IP address in the server log. Purpose: delivering signed updates. Basis: performance of the contract and legitimate interest in security.

AI subtitles and translation

Speech recognition and translation run on your computer: the audio and the text never leave it, and the hardware details used to suggest a model stay on it too. The models are downloaded once, when you choose them, from models.cliphearth.com, which is served by Cloudflare (R2 storage, EU location). Cloudflare sees your IP address, the requested file and the app's user-agent like for any download; we keep no log of these downloads of our own and see only totals. No device identifier, licence key or cookie is sent. Basis: legitimate interest in delivering the models and preventing abuse.

Support form in the app

Subject, message, your e-mail address if you choose to give it, the device identifier, platform, app version and hashed IP address. Purpose: answering you. Basis: legitimate interest.

Sign-in on websites

When you download from a page you opened in the built-in browser, the download sends the same cookies your browser would send to each address it contacts (for example your sign-in to that site), so it works the way playback does. Each cookie goes only to the hosts it belongs to, also after redirects, and never to ClipHearth servers. For some sites the cookies are handed to the local download tool in a temporary file that is deleted right after use.

Screen recording and voice-over

Screen recording and the Editor's voice-over record only what you choose (a screen, a window or an area, the computer's sound, your microphone, your camera) and only after you start them; on macOS the system asks for your permission first. Recordings are saved on your computer and nothing of them is sent to us. If you switch on instant replay, the app keeps the last few minutes in a temporary file on your computer while it is on, so you can save them. Mouse clicks and the pointer's position are noted only to draw click effects and zooms that follow the pointer in your recording. If you switch on Keep the keyboard shortcuts I press, the app also notes the key combinations you press with Ctrl, Alt, ⌘ or the Windows key, so that the Editor can show them on the video; it never notes typed text or passwords. Other keystrokes are not recorded, apart from the shortcut keys you set up for recording. All of this is kept next to the recording on your computer. Removing or blurring the background behind you on the camera also runs on your computer (Apple's Vision on macOS, a model that comes with the app on Windows and Linux), so the camera picture never leaves it.

Screenshots and text recognition

Screenshots are taken only when you press a shortcut, click a tile or run the app's screenshot command. They are saved on your computer, in your screenshots folder or, for captures you only copied, in the app's own folder for 14 days. To make captures findable, the app keeps a list on your computer with the text it recognised in them and the name of the program they came from. Text recognition runs on your computer (Apple's Vision on macOS, a model that comes with the app on Windows and Linux). Cover private details, and the option to cover them after every capture, use the same text recognition to find e-mail addresses, phone numbers, card numbers, keys and passwords in a capture and cover them; the text found is not sent anywhere or written to a log. Nothing of a screenshot is sent to us; a capture leaves your computer only if you copy it somewhere or put it in a shared box yourself.

Copied links

When you switch to ClipHearth, the app looks at the text on your clipboard once. If it is a link to a video or a playlist, the app offers to download it. Nothing runs in the background, and nothing is stored or sent until you choose to download. You can switch this off in the offer itself or in Settings.

Following

If you follow a channel, a playlist or a podcast, the app checks it for new episodes from your computer while it runs, at the interval you choose. Those requests go to the site you follow, the way your browser would contact it. With a licence, new episodes download on their own (you can turn that off for each source), using the sign-in the built-in browser holds for that site, each cookie only for its own site. The list of what you follow and what was already seen stays on your computer; nothing about it is sent to us.

Shared box

A shared box (called Shelf in ClipHearth 1.6.0 to 1.6.8) passes texts, pictures and files between your computers, or to people you share a box with. The content travels straight between the computers, encrypted end to end, or, when they cannot reach each other, still encrypted through the relay service of Cloudflare (see below); it never passes through or is stored on our server, and we cannot read it. For a shared box, our activation server stores a one-way hash of its ID, a proof derived from its password (never the password), its key encrypted with the password, the licence it counts for (the one that created it, or the licence of the computer its admin role went to), which activated computer of a licence each of its computers is (and so the name, platform and app version that computer was activated under), and, encrypted so that we cannot read them, the names its computers give themselves in the box and the list of what was put in it; it passes on the encrypted messages with which the computers connect, without storing them. The link to the activated computer lets a reinstalled computer take the place of its old membership and keeps a box to as many computers of one licence as the licence has. For each box the server also knows which computer is its admin (the computer's ID within the box; its name stays encrypted), why a computer is no longer in the box (it left by itself, was taken out by the admin, was taken out at a password change, or the box was deleted), and which items are notices (a password change, a computer taken out, a new admin); the text of a notice is written by the computers and stays encrypted. When the admin role moves to a computer of another licence, the box counts for that licence from then on, unless that licence already has three. If you lock a box on a computer, the lock password is never stored and never leaves that computer. The computers in a shared box learn each other's IP addresses, so share a box only with people you trust. A shared box is deleted when it expires (if you set 1, 7 or 30 days), when you delete it, or after 180 days without use; removed computers are deleted after 30 days, together with their link to the activated computer, and so are the records of the computers of a deleted box, kept without the encrypted name, only with the time and the reason, so that a computer that was off learns that the box was deleted. If two or more computers had been in a deleted box for a day, its name cannot be used for a new box during those 30 days. Basis: performance of the contract.

Shared box licence checks

Every computer in a shared box needs a licence. Creating a box checks your licence with the device identifier, like a licence check. Joining a box, taking over its admin role, and deleting a box without its password send your licence ID and device identifier to our activation server to check the licence; on creating and joining, the server keeps with the computer's place in the box which activated computer of the licence it is (see above), and nothing else of these requests is stored. To stop password guessing, the server counts wrong box passwords per licence or computer in memory only, for at most 24 hours, and stores nothing about them. Basis: performance of the contract; for counting wrong passwords our legitimate interest in protecting the boxes.

Shared box relay

When the computers in a box cannot reach each other directly, the encrypted data passes through the relay of Cloudflare (TURN) in real time and is not stored there. Asking for the relay, or how much of it is left, sends the same licence ID and device identifier. The app asks how much is left only while the relay matters or while a box is open on screen, at most once every 15 minutes; nothing of that request is stored. While a box is open on screen, the app also tries a direct connection to the computers that are on, to show how they connect; this uses only the encrypted signals through our server, like every connection, and not the relay. To keep a monthly limit of 20 GB per licence, our activation server records which licence each relay access was given to and how much data passed through the relay for that licence in the month, as counted by Cloudflare, and deletes these records after three months; they hold only numbers about volume, never content or file names. The app itself does not report how much it sent through the relay. Basis: performance of the contract and our legitimate interest in keeping the relay available to everyone.

Browser extension

The ClipHearth extension for Chrome, Edge and Firefox hands the address of the page you are on, or of a link you right-clicked, to the ClipHearth app on your computer when you use its button, its menu or its keyboard shortcut, together with what you chose (for example sound only). It talks to the app directly on your computer and can start it. While downloads run, the app tells the extension only how many there are and how far they got, to show on its button. The extension has access to a page only at the moment you use it, collects nothing and sends nothing to us or anyone else; if ClipHearth is not installed, it shows a page with a link to our website. The app then opens the address from your computer to show what it can download; nothing downloads until you choose. A website can also try to open ClipHearth this way, but your browser asks you first, and the app only shows that choice.

Diagnostics logging

Off by default and switched on only when our support asks for it and shows you how. The log is written only to your computer and is never sent automatically; you decide whether to share it with support.

Retention. Licence and device records are kept for as long as the licence is valid and for three years afterwards. Trial counters and the activation audit log are kept for as long as they are needed to operate trials and prevent abuse; we are introducing automatic deletion or anonymisation 24 months after a device was last seen. Records of accepted terms are kept for six years. Support messages are kept for 24 months. Records of which licence used the shared-box relay, and how much, are deleted after three months.

09Cookies and storage

While you browse, the website sets no cookies of its own; when you buy a license it sets one strictly necessary cookie for 24 hours so the key is shown only in the browser you paid with. It stores your cookie choice in your browser, and only with your consent stores the analytics visitor id or loads Google Ads tags. The full list, durations and how to change your choice are in the Cookie policy.

10Who receives your data

We share personal data only with the service providers needed to run ClipHearth:

We do not sell personal data. We disclose it to authorities only when the law requires us to.

11International transfers

Our servers are in the EU. Stripe, Cloudflare and Google may process data in the United States. Those transfers rely on the EU–US Data Privacy Framework certification of the recipient and, where needed, on the European Commission's Standard Contractual Clauses.

12How we protect your data

All connections use TLS. Activation keys are stored as keyed hashes on the activation server and encrypted at rest in the website's order database. IP addresses on the activation server are stored only as keyed hashes. Licence receipts and updates are cryptographically signed. Access to our systems is restricted to the operator.

13Your rights

Under the GDPR you can ask us to:

• confirm whether we process your data and give you a copy (access),
• correct inaccurate data (rectification),
• delete your data where we no longer need it (erasure),
• restrict processing, or object to processing based on our legitimate interests,
• receive the data you gave us in a machine-readable form (portability),
• withdraw consent at any time - for cookies, use Cookie settings in the footer.

Write to info@cliphearth.com. We may ask you to confirm your identity, for example by writing from the e-mail address used for your purchase. You can also complain to the Czech Office for Personal Data Protection (Úřad pro ochranu osobních údajů, Pplk. Sochora 27, 170 00 Praha 7, uoou.gov.cz) or to the supervisory authority in your country of residence.

14Children

cliphearth.com and ClipHearth are not directed at children under 16, and we do not knowingly collect their data. If you believe a child has given us personal data, contact us and we will delete it.

15Changes to this policy

The version and date at the top tell you when this policy last changed. We announce material changes on the website. The version in force is always the one published here.