# Encryption and the cloud

How what you sync is stored on Copilka's service, who can read it, and where it is.

Everything sync sends to Copilka's service is encrypted at rest with keys that belong to Copilka, on top of the encryption the storage underneath already has. This page says exactly what that means.

## How it is sealed

- Each account has its own data key, made when the account first writes anything. It is itself wrapped by a master key that only the service holds.
- Every record, an item, a room, a tag, a reading, is sealed with the account's key before it is stored, and bound to its own identity, so that a sealed body cannot be moved onto another record.
- Every file is sealed in pieces of one megabyte, each bound to its place in the file.

What is not sealed is the framing: a record's kind and id, its version numbers and timestamps, which device wrote it, a file's hash and size and type. And the account itself: your email address, your devices' names and when they were last seen, your plan, your monthly usage, and the log of what assistants did, by tool and time.

## Who can read it

Copilka's own service can. This is not end-to-end encryption, and it is deliberate: a connected assistant reads your library through the service, from its copy, which needs the service to be able to unseal it. The model is the one Notion, Slack and Linear use: encrypted with the operator's keys, under rules.

The rules: nobody at Lumilay reads your data. If support ever needed to look at something, you would be told first, and the read would be logged. Every administrative action on the service is logged.

If you would rather nothing of your library were readable by anyone but you, keep sync off. Your library then never leaves your devices.

## Backups

The service keeps thirty days of database history, and the operator takes an encrypted backup of everything by hand from time to time. When you delete your account, what was in a backup is gone within thirty days.

## Where it is

Copilka's service runs on Cloudflare. Your records are in a Cloudflare D1 database and your files in Cloudflare R2 storage, both in the Eastern Europe region. Email is sent through Cloudflare. Sign-in with Google or GitHub goes through Clerk. Models are reached through OpenRouter, which routes to Google with zero data retention.

## On your devices

The library on your Mac and iPhone is plain files, readable by you. It is not encrypted by Copilka; FileVault and the iPhone's own protection are what protect it there. See [Your data on disk](https://docs.copilka.app/account/your-data-on-disk/).

---

This page: https://docs.copilka.app/account/encryption/ · As Markdown: https://docs.copilka.app/account/encryption.md · Every page: https://docs.copilka.app/llms.txt
