Ukraine solidarity. Service offered free to Ukrainian businesses for as long as the war lasts. Request free access
Privacy · GDPR-native

Privacy policy

Designed ARDNTECH zero-knowledge: we cannot read your secrets, even if we wanted to.

Updated on 01/08/2026 GDPR-native Hosting in France AGPL-3.0
01 / Contents

Twelve sections, four themes.

Direct access to each chapter of the policy. The full text is readable below; the links anchor directly to the section that interests you.

Rights

Read this first

Zero-knowledge architecture

ARDNTECH encrypts your secrets in your browser before any transit. We technically have no access to their cleartext content. This privacy policy describes the data we actually process (email, password hash, technical metadata) and the associated legal bases.

02 / For DPOs and CISOs

What we see, what we do not see.

Three educational boxes to qualify the technical boundary of privacy ARDNTECH. This visibility map is technically enforceable: it follows directly from the cryptographic architecture, not from a contractual commitment.

What we NEVER see

Inaccessible by design

  • Your master password in cleartext
  • The decrypted content of your secrets (passwords, API keys, notes)
  • Your OpenPGP private key , which never leaves your browser

No judicial requisition can compel us to hand over these elements: we do not hold them.

What we see without being able to read

Stored encrypted for you

  • The encrypted OpenPGP blobs of your secrets, sealed for your public key only
  • The shared encrypted blobs , sealed for the public key of each recipient

A full dump of our database reveals no secret in cleartext: the blobs are AES-256-GCM SEIPDv2 per RFC 9580.

What we see in cleartext

Technical metadata

  • Your email address account
  • The secret name (for searching) and its type
  • The folder hierarchy and the list of share recipients
  • The dates of creation, modification, last access

Strictly necessary to the organisation of the service. Retained in accordance with the durations detailed in section 7.

03 / Section 1

Controller for processing.

The legal entity responsible for the processing of your personal data and the point of contact for its data protection officer.

The data controller is the Publisher (ARDNTECH), whose details appear on the Legal notice.

Data Protection Officer (DPO): dpo@aegirex.eu.

04 / Section 2

Zero-knowledge architecture: what we cannot read.

ARDNTECH encrypts your secrets in your browser before any sending. Our servers store only opaque OpenPGP blobs, encrypted for your public key only.

Technical consequences of the architecture

As a result, we have no technical access:

  • to the cleartext content of your secrets,
  • to your master password,
  • to your OpenPGP private key (downloaded by you at sign-up, never transmitted).

You can verify these claims by consulting the public source code in our GitHub repository. The security architecture page details the cryptographic stack RFC by RFC.

05 / Section 3

Data processed.

To run the Service, we process the following categories of data, grouped by purpose.

3.1 · Account data

Authentication and cryptographic identity

  • Email address: authentication, transactional communications, session recovery.
  • Master password (Argon2id hash only): identity verification at login. The cleartext password is never stored.
  • OpenPGP public key: allows other users to share secrets with you.
  • Public key fingerprint (SHA-256 truncated): consistency checks.
3.2 · Technical data

Operation and security

  • Connection IP address: security (rate limiting, anomaly detection). Retained for 30 days.
  • User-Agent of the browser: diagnostics and audit.
  • Session cookies: strictly necessary to the operation of the Service (HttpOnly, Secure, SameSite Strict in production).
3.3 · Opt-in

HIBP scan (can be disabled)

If enabled, we compute a partial hash of your email address (k-anonymity) to check whether it appears in a public breach. HIBP never receives your email in cleartext. Can be disabled from your privacy settings (GDPR Art. 21).

3.4 · Metadata

Secret metadata visible server-side

Although the content of the secrets is encrypted and inaccessible to the Publisher, certain technical metadata are necessary for organisation and remain visible server-side:

  • Secret name (entered in cleartext for searching),
  • Type (password / API key / note / certificate),
  • Folder hierarchy,
  • List of share recipients (by their public key fingerprint),
  • Creation, modification, last access dates.

The content (password, API key value, etc.) is encrypted and inaccessible to the Publisher.

06 / Section 4

Purposes and legal bases.

For each processing activity, the corresponding GDPR Article 6 legal basis. No data is processed without an explicit basis.

Purpose Legal basis (GDPR Art. 6)
Provide the encrypted storage servicePerformance of the contract (Terms)
Authentication and security (rate limiting, audit chain)Legitimate interest + security obligation (GDPR Art. 32)
Transactional communications (signup, sharing, alerts)Performance of the contract
HIBP scan (opt-in)Explicit consent
Retention of audit logsLegitimate interest + legal obligation (traceability)
07 / Section 5

Recipients of the data.

Your data is communicated only to the technical subprocessors strictly necessary to the operation of the Service.

Technical subprocessors

  • Host: French infrastructure operator targeting SecNumCloud qualification (see Legal notice for the precise identity).
  • Brevo (France): sending of transactional emails.
  • Stancer (France): payment processing (paying users only).
  • HIBP (Australia, opt-in): scan via the API k-anonymity (the email is never transmitted in cleartext).
  • DB-IP (Belgium, database downloaded locally): IP geolocation of new connections ("new city detected"). The database is downloaded monthly and queried offline: no user IP leaves our servers . Licence CC-BY 4.0.

No resale, no profiling. No data is resold, exchanged or transmitted for marketing or advertising profiling purposes.

08 / Section 6

Transfers outside the EU.

ARDNTECH favours French or European subprocessors. A single outbound flow outside the EU exists, and it is cryptographically protected.

The only outbound flow outside the EU is the HIBP scan (Australia), which uses a cryptographic mechanism (k-anonymity) guaranteeing that no identifiable personal data leaves the EU. The technical detail is available in the public security documentation.

The HIBP scan can be disabled individually (user settings) and globally on the administrator side of a self-hosted instance.

09 / Section 7

Period of retention.

Each category of data is retained for the minimum duration necessary to its purpose, in accordance with the GDPR Art. 5 minimisation principle.

Category Duration
Active accountThe entire duration of use of the Service
Inactive account (no login for 24 months)Notification + deletion after 30 days
Account deleted on requestImmediate deletion of identifying data
Audit log (one-way hash)3 years (traceability obligation)
Connection IP address30 days
Application server logs30 days
10 / Section 8

Your six GDPR rights tooled.

The rights granted by the GDPR are exercisable directly with our DPO. Several are also tooled in self-service from your account settings.

Right of access

Obtain a copy of all the data concerning you. Available directly from your settings: GDPR export (immediate JSON export).

Right of rectification

Change your personal data at any time (email, OpenPGP public key) from your settings area or by request to the DPO.

Right to erasure

Delete your account and all your identifying data. Available in self-service from Delete my account in the settings.

Right to portability

Retrieve your data in a structured format (JSON), re-importable into any compatible instance. No proprietary lock-in.

Right to object

Refuse certain optional processing (for example: HIBP opt-out scan, product notifications). The nominal operation of the vault does not depend on it.

Right to lodge a CNIL complaint

Refer the matter to the French supervisory authority: cnil.fr/fr/plaintes. No prior step with the Publisher is required.

11 / Section 9

Security measures.

Seven categories of technical and organisational measures implemented to protect your data in accordance with Article 32 GDPR.

Detailed technical measures

  • OpenPGP end-to-end encryption (AES-256-GCM via SEIPDv2, RFC 9580).
  • Argon2id password hashing (5 passes, 256 MiB memory, parallelism 4).
  • HMAC-SHA-256 audit chain chained (tamper detection in O(1)).
  • Two-factor authentication (email + optional TOTP).
  • HTTPS mandatory (HSTS), strict CSP (no inline scripts, Trusted Types).
  • Rate limiters on sensitive routes (signup, login, export).
  • Hosting with a French operator targeting SecNumCloud qualification.

Audit and verification. The detail of the cryptographic stack RFC by RFC, the formalised threat model and the audit chain verification procedure are published on the security architecture page.

12 / Section 10

Cookies strictly necessary.

ARDNTECH uses only cookies strictly necessary to the operation of the Service. No third-party cookie, no tracking pixel, no analytics tool.

Three cookies, all functional

  • Session cookie (HttpOnly, Secure, SameSite Strict in production): authentication of the logged-in user.
  • CSRF cookie: protection against Cross-Site Request Forgery attacks.
  • Onboarding cookie (1-year duration): remembers the closing of the welcome wizard so as not to display it again.

No consent required. No third-party cookie, no tracking pixel, no analytics tool is set. Prior consent is therefore not required within the meaning of the CNIL (Deliberation 2020-091).

13 / Section 11

Changes to the policy.

The conditions and time frames within which this policy may evolve, and the commitments to notify users.

The Publisher may amend this policy at any time. Users are informed by email of substantial changes with a notice period of fifteen (15) days.

The current version is always dated at the top of the page. The change history is archived and available on request to the DPO.

14 / Section 12

Contact DPO.

Contact details of the Data Protection Officer for any question relating to your personal data or the exercise of your rights.

Postal address

See Legal notice.

Response time

One month maximum, in accordance with Article 12 GDPR.

For businesses

Data processing agreement (DPA) available.

15 / Getting started

A question about your data?
The DPO answers.

ARDNTECH was designed so that privacy does not depend on the publisher's good faith. If a question remains about a processing activity, a retention period or a right, contact our Data Protection Officer directly. For businesses, a standardised data processing agreement is available.

Zero-knowledge OpenPGP, encrypted blobs unusable without the private key
GDPR-native, six rights tooled in self-service
Hosting in France, French jurisdiction
HMAC-SHA-256 audit chain independently verifiable
AGPL-3.0 code, fully public and auditable