Privacy policy
A published contact channel — whether that is an email address, and which one, is still an open product decision — and a lawyer's review, which the project requires for all legal copy before launch. What follows describes accurately what the site and the app do today; what is missing is the form, not the facts.
The short version
This website collects nothing. It sets no cookies, runs no analytics, has no forms, executes no JavaScript, and loads not one third-party resource.
The PDFsigna applications have no accounts. No sign-up, no email, no login, in any version. Your documents are never uploaded to any server, and your certificate never leaves your machine.
Who is responsible
The data controller is Color Vivo Internet, S. L., the company that develops and publishes PDFsigna. Full identification details and a contact channel will be published on this page before the applications go on sale.
The website
What we don't do
- We set no cookies at all. The detail is in the cookie policy.
- We use no analytics of any kind, first-party or third-party.
- There are no tracking pixels, no social buttons, no embedded video.
- We load no external fonts: a font served from another domain is a request to a third party with your IP address inside it.
- There are no forms, so there is nothing you can send us from here.
The only thing that gets logged
The site is served from Cloudflare's network. Like any web server, their infrastructure logs the requests it serves — IP address, time, page requested, user agent — in order to serve them, protect them from abuse and detect faults. Those logs belong to the provider, they are operational, and we do not cross-reference them with anything or use them to profile anyone. It is mentioned here because it exists, not because we make use of it.
The applications
What stays on your machine
All the work on the document. Reading, annotation, the signature and stamp library, placement and signing all happen locally. Your private key is never exported: the signature is produced by your operating system's key store and the app only receives the result — which is also what reinforces the "sole control" requirement of Article 26(c) of the eIDAS Regulation.
What does go out to the network, and why
A signing application cannot be entirely offline and still do its job. These are the connections it makes, all of them to third parties that are not us:
- Timestamping. When you sign with a timestamp, the app requests one from a timestamping authority. What travels is the cryptographic digest of the signature — not the document.
- Revocation checking. To find out whether a certificate was still valid, the app queries OCSP or downloads revocation lists (CRLs) from the certificate's issuer. The certificate identifier travels; the document does not.
- Trusted lists. To classify the legal level, the app uses the European trusted list (LOTL/TSL), which is public information.
In all three cases the request goes to the relevant provider under its own policy. None of those connections passes through any server of ours, because we have none in the signing path.
What there isn't
- Accounts, sign-up and passwords: they don't exist.
- Telemetry, usage statistics and automatic crash reports: not sent.
- Advertising and profiling: none.
- Selling or sharing data with third parties: does not happen, and will not.
Your rights
The GDPR (Regulation (EU) 2016/679) gives you the right to access your personal data, rectify it, erase it, restrict or object to its processing, and to data portability, as well as to complain to a supervisory authority.
There is very little here to exercise them over, and that is deliberate: we do not process your personal data through this site or the applications, because we do not collect any. If that changes — for instance the day the product is sold from this website and there is billing — this page changes first, not afterwards, and it will say what is collected, what for, and for how long.
Children
The product is not directed at children and collects no data from anyone, so it processes no children's data.
Changes to this policy
If it changes, the date at the top changes and we say what changed. One text is not quietly swapped for another.