Desktop app privacy
Last updated:
Files.co PDF Suite processes your PDFs on your computer. It does not upload them anywhere, has no account and sends no telemetry or usage data. This page explains the few connections the app makes and, above all, what data we handle if you buy Pro on the direct download from this website. The privacy of the files.co website is covered by its own policy.
Your documents
The PDFs you open, edit, sign or convert with the app never leave your computer. There is no cloud and no copy on our servers, and the app works offline. When you sign with your certificate, the private key stays in the system store (or in the app’s keychain, on Mac) and is never sent.
Purchases: store or direct download
Files.co PDF Suite is available for Mac, Windows and Linux, and Pro can be bought in two ways. In the Mac App Store or the Microsoft Store, as an in-app purchase: Apple or Microsoft charge you and we receive neither your payment details nor your email. On the direct download from this website, in the browser: what then happens to your data is explained in the sections below. On Linux there is only the direct download.
Direct download: who handles your data
The controller is Color Vivo Internet, S.L. You can write to us at [email protected].
Payment is handled by Stripe with Managed Payments: Stripe, through Link, is the merchant of record for the purchase — it charges you, issues the invoice and takes care of taxes. To sell to you we only need your email; your name, address, card details and tax ID are requested and handled by Stripe under its privacy policy and that of Link. We never see your card.
Cloudflare processes data on our behalf: it hosts the licence server and its database, sends the emails and serves downloads from download.files.co. When you ask for a sign-in link to your account, Cloudflare Turnstile checks invisibly that you are not an automated program; to do so it handles technical data about your browser and connection, such as your IP address and browser characteristics, and Cloudflare states that it does not use them for advertising or tracking (Turnstile privacy addendum). We keep nothing from that check. Transfers outside the European Economic Area that this involves are covered by the safeguards in Cloudflare’s data processing agreement.
Direct download: what we keep and for how long
Your email, the Stripe identifiers of the purchase and your billing country. They identify your licence, let us send you the key and service notices, and let you sign in to your account; the country is also used for statistics and support. Legal basis: the contract (the country, legitimate interest). Kept while you hold licences.
The devices where you activate the licence. On activation, the app sends a device identifier (a hash the original cannot be recovered from), the operating system and its version, the architecture, the language and the app channel. The device name is only sent if you leave the box to show it in your account ticked, and you can untick it. This is used to count how many devices the licence uses and so you can recognise them. Legal basis: the contract. Kept while the licence exists.
The IP address, country and network an activation comes from, with date and time, as proof of activation and to prevent fraud. Legal basis: legitimate interest. The IP address is deleted after 24 months.
The licence history: activations, deactivations, changes made by support, automatic notices sent and, if you move it to another email or change email when buying again, the old and new email. Used to support you, avoid repeating notices and stop abuse. Legal basis: contract and legitimate interest. Kept while the licence exists.
Your preferred language (just the code, for example "en"), to write to you and show the portal in your language, while your account exists.
For security, for a very short time: a keyed hash of the email and IP address of each sign-in link request (2 days); the link itself (15 minutes) and the open session (30 days); and the server’s technical logs, with emails masked and no keys or tokens (7 days).
Data that does not identify you: for each sale, the amount, VAT, country, plan and the website you came from, for internal statistics. We keep the domain of that website (just the domain, no path or IP) for 90 days.
The free mode has no sign-up and we do not ask for your email: the free-mode limits are counted on your own device.
Direct download: what the app does online
The direct-download version connects to our licence server only to activate, renew and deactivate the licence, to check now and then that it is still valid, and to download the signed list of revoked licences. Without a licence, it asks for the Pro price to show it to you: an anonymous request, without your email or device identifier, and the server does not keep the IP address. It sends no telemetry or usage data, and your documents never leave your computer.
Updates are downloaded from download.files.co, which sees your IP address and the installed version. On Mac, the app only looks for them if you allow it. On Windows, they are handled by the system’s App Installer. On Linux, the .deb and .rpm packages update from our repositories on download.files.co along with your system updates, and the Flatpak from our Flatpak repository. The Linux app can also read a public file (latest.json) on download.files.co to tell you when a new version is out: at most once a day, and only if “Check for updates automatically” is on in Preferences › Updates — on by default for the .deb and .rpm packages, off for the Flatpak (where the software centre and flatpak update do the job). The request carries no data about you or the app — no parameters, no cookies, not even the installed version — and the server only sees the IP address, as with any connection. The app never updates itself: APT, DNF or Flatpak do.
The Mac App Store and Microsoft Store versions do not connect to our licence server: the store handles the purchase.
Direct download: your account and its cookies
In your account you see your licences and devices, recover your key, download invoices and move the licence to another email. You sign in with a one-time link sent to your email, with no password. Our support team can view your account as you see it, read-only, and every access is logged.
The portal uses technical cookies: the session cookie (__Host-cv_portal, 30 days) and short-lived ones while you sign in (__Host-cv_auth and __Host-cv_xfer, for as long as the link lasts; __Host-cv_next, one hour). It also stores the preferences you choose: language (cv_lang) and theme (cv_theme), one year, and the app you came from (cv_app), 30 days. It uses no analytics or advertising cookies.
If you move a licence to another email, the new address gets a link to accept it and sees the previous email; once accepted, we let the previous address know, and it sees the new one. Invoices stay in the buyer’s name.
We only send the notices the service requires, such as your key when you buy. They are not marketing: there is no newsletter and no advertising sent from the app.
Your rights
You can ask for access, rectification, erasure, restriction and portability of your data, or object to its processing, by writing to [email protected]. In your account you can see your licences and the devices using them at any time. If you delete your account, your licences stop working; Stripe keeps the invoices because the law requires it. If you disagree with our answer, you can complain to the Spanish Data Protection Agency (AEPD).