What we collect and why

Version 2026-10 · applies to every account on Sealique

Data we collect

• What you give us: account details, the documents and records you create, the people you invite.
• What the service records: signing and attendance events with time, device and network address, delivery status of e-mails, and an audit trail of actions.
• Technical data: server logs kept briefly for security and reliability.
• Page statistics, first-party and without cookies: for every page served we keep the page path (with any link code or document identifier replaced by a placeholder), the language, the device and browser family (phone, Chrome…), the website you came from (domain only), the time, whether you were signed in, and a visitor code. The visitor code is a hash of your network address and browser with a secret that changes every day, so it cannot be turned back into your address and cannot follow you from one day to the next. Page views are never linked to your account: no account is stored with them, and their visitor code is computed separately from everything that carries an account, so page views cannot be matched with feature records or feedback. Page statistics are deleted after 400 days. No third-party analytics service is involved.
• Feature use: when you are signed in, each use of a feature (a document sent, a PDF merged, an attendance form published…) is recorded against your account, with the time and the item concerned. This is deliberate: it lets the operator see which features registered people rely on and which go unused, so the service can be improved. When you are not signed in, the record carries only an anonymous visitor code of its own (daily secret, not reversible, never matched with page views). Feature records are deleted after two years.
• Feedback: when you use the feedback button we store your rating, category, message, the page you were on, your language and device family, and the e-mail address only if you choose to give one. When you are signed in, the message is linked to your account instead of an e-mail address, so the operator can see what registered people ask for and follow up with you. Messages are read by the platform operator and kept until they have been handled and reviewed.

Why we use it

To provide the service you asked for: signing, verifying and sharing documents, recording attendance, writing minutes, sending the e-mails you trigger (invitations, reminders, sealed copies) and keeping your account secure. Nothing else.

Cookies and storage

We set only the cookies the app needs: a session cookie to keep you signed in, a security token, your language choice and small preferences (theme, layout) kept in your browser. There are no advertising or tracking cookies, and the usage statistics described above set no cookie at all.

Who can see your data

People you invite to sign see the document and the names of the other signers. People you share a document with can read it until you revoke access. Anyone who scans a verification QR sees the document's verification status, signer names and masked e-mail addresses. Our hosting, storage and e-mail providers process data on our behalf under contract, and the typefaces are loaded from Google Fonts, which receives your browser's request for the font files.

Your rights

Access, correction and deletion: use your profile and documents pages. For a full export, account closure or an objection, contact the operator through the address shown in your account e-mails. We answer without undue delay.

Changes

When this policy changes materially, the version number on this page changes and account holders are asked to confirm the updated Data Protection Agreement.

---