Security at JuLenny

JuLenny is built so that no one has to be trusted with your data, including us. Your records are encrypted on your own machine and stay encrypted while they are computed on. We only ever hold ciphertext. This page describes how that works and the controls around it.

What we hold, and what we cannot

We hold ciphertext and account metadata. We do not hold any key capable of decrypting your data. Because the computation runs on encrypted data, your plaintext is never present on our infrastructure, so there is nothing for us, an attacker, or a subpoena to read.

Encryption happens on your machine

You encrypt your data locally with the JuLenny toolkit before anything is uploaded. Only ciphertext leaves your environment. The toolkit is source-available under the Business Source License 1.1, so you can read it, audit it, and compile it yourself rather than take our word for it.

Keys and the decryption you control

The decryption key never exists in one piece on our side. For a collaboration between two companies, the parties run a chained key setup that produces a joint public key for encryption, while each side keeps its own secret share. Nothing can be decrypted without the participation of the key-share holders, so no single party, including JuLenny, can read a result on its own. Every result is released only when you explicitly approve it, and a solo self-test (your company granting to itself) uses a single key set that stays with you.

You decide every time it runs

Each computation runs under permissions you set: how many times it may run, for how long the permission lasts, and which datasets and functions it covers. You review a cost estimate before anything executes, and you can revoke a permission at any time.

Signed, fixed function circuits

Every computation runs as a fixed, signed circuit. The same sequence of operations executes on every run and cannot silently change between the time you approve it and the time it runs.

Where your data is processed

Encrypted data is processed and stored on Google Cloud in the EU. Account metadata is handled under the same regional rules.

GDPR

Because all processing happens on encrypted data, personal information is never exposed to our infrastructure. We act as a processor handling ciphertext only, operate in the EU, and provide tooling for data-subject requests on the account data we do hold.

Sub-processors

We use a small set of third parties to run the service (for example cloud infrastructure, email, and payments). Under our Data Processing Addendum, the current list of sub-processors is available to customers on request. Contact us and we will send you the current version.

Incident response

We follow a documented incident-response process and will notify affected customers of a confirmed incident affecting their data without undue delay.

Compliance program

We are in the early stages of preparing the platform for SOC 2 Type II and ISO/IEC 27001. We will update this page as that program progresses.

Reporting a concern

If you have found a security issue or have a question about our controls, please contact us.