Security and trust

You are going to trust us with documents that matter. Here, with no hype, is how we protect them, what we guarantee, who answers for it — and also what we don’t have yet. We would rather you checked it yourself than took our word for it.

01You can seal without giving us the document

It is the shortest way to settle the question: if we never receive it, we cannot look at it. With “Seal without uploading the document”, your browser computes the file’s SHA-256 fingerprint and sends only those 32 bytes. The document never leaves your machine at any point.

And you don’t have to take our word for it: check it yourself. Open your browser’s developer tools, go to the Network tab and seal a file. You will see a single request of about a hundred bytes, with the fingerprint and whatever name you give it. Nothing else. If the file were being uploaded, its full size would show up there.

What we store in that case: the fingerprint, the date and who sealed it. The fingerprint is a 64-character number from which the content cannot be reconstructed — that is what lets it serve as proof without revealing anything.

02When you do give us the document

If you use normal sealing —uploading a PDF or drafting it here— the content is stored on our servers, because the live link has to be able to show it to whoever you send it to. We say so plainly rather than leaving it in the small print: in that mode, technically, we could access it.

The data is stored on infrastructure in the European Union, with access separated by customer and under the processor’s contractual commitment on data processing. But a commitment is a promise, and a promise has to be believed. That is why the mode above exists: for anything you don’t want to entrust to anyone, don’t give it to us.

03Who answers for it

CODEX is not an anonymous start-up or a weekend crypto experiment. It is a product of AIM, the software division of BIOMAG, S.L.U. — a European company with its own brands on the market and years of shipping products. Behind every seal there is an identifiable company, with a registered address, an entry in the commercial register and legal liability.

04The cryptographic guarantee

It is the heart of CODEX, and it can be verified independently — you don’t have to rely on our word:

The practical consequence: the validity of a sealed document survives even if CODEX, or even its issuer, ceased to exist — provided you have kept the downloadable proof. It is the property that no system based solely on “trust the provider” can offer.

05Your data is yours

No holding your data hostage and no lock-in. At any time you can export:

• The complete evidence log as CSV (who, what, when, with which seal).
• Your entire CODEX as a ZIP: documents, versions and proofs.

If one day you decide to leave, you leave with everything. Portability is not a premium feature: it is a right.

06Privacy, GDPR and AI

CODEX is a service of a European company, subject to Regulation (EU) 2016/679 (GDPR), Spain’s LOPDGDD and the LSSI. How data is processed is set out in the Privacy policy, and the data processing terms in the corresponding document.

07Encryption and access control

• All traffic between your browser and the service travels encrypted over HTTPS (TLS). This is not end-to-end encryption: when you upload a document, our server receives it decrypted (if you seal without giving us the document, it never receives it).
• Access via an authenticated account with roles and permissions per organisation.
• Document links are served with indexing disabled (they do not appear in search engines) and an integrity check every time they are opened.

08European sovereignty, no small print

Your account and your documents are stored on servers in the European Union (Amsterdam, the Netherlands). To be precise, as with everything else: the company that operates those servers (Railway) and the one that sends our emails (Resend) are American, with processing agreements that include the European Standard Contractual Clauses; and the text you send to the artificial intelligence features is processed in the United States. Who processes what, and where, is in the list of sub-processors.

Not even our fonts call Google. Most websites —including those of many e-signature providers— load their fonts from Google’s servers, which sends every visitor’s IP address to a third party outside the EU without anyone asking (there have been rulings against it, such as the one by the Munich Regional Court in 2022). Here we serve them from our own domain: when you open this page, your browser contacts no third party. You can check it yourself in your browser’s Network tab — you shouldn’t believe us, you should verify it.

09Sub-processors

To provide the service we rely on a limited set of providers (infrastructure, transactional email, payments and zero-retention AI assistance), published with their name, the data involved and location in the list of sub-processors. The contractual guarantees are set out in the data processing agreement, which you can review before signing up.

10What we don’t have yet

11If you find a security flaw

Write to us at hola@aim-codex.ai with the subject “Security” (also in security.txt). Our commitment:

• We acknowledge receipt within 5 working days at most and tell you what we are going to do.
• We will not take legal action against anyone researching in good faith: without accessing other people’s data beyond what is strictly necessary to demonstrate the flaw, without degrading the service, and giving us a reasonable period to fix it before making it public.
• Scope: www.aim-codex.ai and its API.
• If you wish, we will credit you by name once it is fixed. We do not offer financial rewards.

See plans and pricing →