Calyraen
Searching the site...
No matches. Try another word.
Log in
Data safety

Your data stays yours.

Here is what we collect, what leaves your device, and what never does. Plain answers, no fine print.

See what we hold Talk to us
The short version

The short version, in plain words.

You should not need a law degree to know how your data is treated. So here is the whole of it, in a few sentences.

We keep only what the device and your services actually need. Most of it never leaves your hands. What we do hold, you can see, export or delete whenever you like. That is the promise. The rest of this page is just the detail, if you want it.

Privacy by default, not by request

0 Third-party trackers in CalyOS
AES-256 Encryption, at rest and in transit
On-prem Option, so data never leaves the building
Never Sold, rented or profiled
The four commitments

Four commitments, in full.

Imagery in production

We collect the minimum

Only what the device and your services actually need. Everything else is opt-in.

We ask for the least a device or a service needs to work, and nothing more. Anything beyond that is yours to switch on, never assumed on your behalf. And you can see the full list of what we hold at any time, so there are no quiet exceptions to find later.

Imagery in production

It stays on your device

Processing happens locally, or on-prem, by default.

By default, your work is handled on your own machine or on your own premises. There is no background telemetry sending your activity back to us while you are not looking. If you never turn anything on, nothing leaves the building. That is the starting point, not a setting you have to hunt for.

Imagery in production

Encrypted, and the keys are yours

AES-256, at rest and in transit. We hold no spare key.

Your data is encrypted while it sits on the device and while it moves across the network, using AES-256. The keys belong to you, and we have no secret way in. Your files stay readable to you and to the people you choose, and to nobody else.

Imagery in production

Never sold, never profiled

No ad networks, no trackers, no behavioural profiles.

We do not run ad networks, we do not embed third-party trackers, and we do not build a profile of how you behave. Your data is never sold or rented to anyone. This is not a promise we ask you to trust on faith. It is simply how the system is built.

“Privacy by default, not by request.”
Calyraen
Common questions

Asked and answered.

Can you read my files?

No. Everything is encrypted with AES-256, at rest and while it moves, and the keys belong to you. We have no secret way in.

Do you sell or share my data?

Never. There are no ad networks, no third-party trackers and no behavioural profiling. Your data is not sold or rented to anyone.

Does my activity get sent back to you?

No. Processing happens on your device or on-prem by default, and there is no background telemetry. If you switch nothing on, nothing leaves the building.

Can I see everything you hold, and remove it?

Yes. Everything held about you sits in one place, ready to view, export or delete. You do not have to ask, and you do not have to wait.

Your data, your control

See exactly what we hold.

Everything held about you is in one place, ready to view, export or delete. You do not have to ask, and you do not have to wait.

See and manage your data Talk to a person
Your data, your control

It is all yours.

See exactly what Calyraen holds, why each item is there, and take a copy or delete it whenever you want. It sits in one place, with plain steps and clear timeframes so you always know when it is done.

What we hold

The minimum, and why.

Imagery in production
Account and licence

Who you are and what you own

A name, a sign-in credential, and proof the device is licensed. This is what lets you own the device outright and stops anyone else claiming it.

Imagery in production
Device health

Whether the machine is well

Model, firmware version, storage state, and whether the last update applied. The update service reads this to keep your device patched across its seven supported years.

Imagery in production
Service data you create

The content you put in

If you use a Calyraen service, it holds the content you put into it, such as files or settings. That content belongs to you and is processed on the device or on-prem wherever it can be.

Beyond the baseline

Everything else is opt-in.

That is the baseline. There is no fourth category behind it. Past the baseline, collection happens only if you ask for it.

  • Crash and diagnostic reports stay off until you turn them on. They help us fix faults faster, and you can read one before it is sent.
  • Optional features that need more data, such as a shared workspace, declare that need at the point you enable them.
  • No silent background gathering. We do not build a profile of how you use the device, and we do not collect location, contacts, or browsing to sell or target you.

If a setting is unclear, the plain note in Privacy tells you what it does and what turning it off costs you. The full legal detail lives in the Policies section.

Timeframes

Seeing, exporting and deleting.

All of this runs from one place, with no queue. Seeing what is held is immediate. Small exports are ready in minutes and larger ones within a few hours, with a link emailed to you. Deleting a single item clears it from live systems and search at once, and a full account erase finishes within 30 days with an email to confirm. Two honest details are worth knowing.

  • Backups roll off on a schedule. A deleted item can sit in an older encrypted backup until that backup expires, usually within 35 days. We never restore it into your account, and it is not used for anything in the meantime.
  • Some records are held by law. Invoices, tax records, and fraud-related logs have a required retention period. We keep only those specific records, only for as long as the rule requires, and we name them on the Close account screen.

Anything processed on your device, such as local files and on-device model data, you can delete yourself in CalyOS at any time. It never needed a request in the first place.

Questions

Common questions.

Imagery in production

Does Calyraen collect my files or what I type?

No. The content you create stays on the device or on your own on-prem systems and is treated as yours. We do not scan your files or your keystrokes to learn about you. A service only holds the content you deliberately put into it.

Imagery in production

Do I have to ask support to see, export, or delete my data?

No. See, export, and delete all run from the Data controls page in your account, or from Settings on a CalyOS device. There is no request to file and no queue to wait in. Support is there if something is unclear, but the actions are yours to run.

Imagery in production

If I delete something, why might it stay in a backup for a while?

Live copies go at once and stop appearing in your account and in search. Encrypted backups are kept on a fixed schedule and then overwritten, so a deleted item can linger in an older backup until it expires, usually within 35 days. During that window it is not restored or used for anything.

Related topics.

What leaves your device

*Local*

Little or nothing leaves without you asking. CalyOS works on the device or on your own server by default, with no background telemetry running in the shadows.

## What stays, what moves

Almost everything CalyOS does happens on the machine in front of you. Search indexes, photo tagging, voice input, document previews, and print jobs are handled by the local processor. They do not need an account and they do not phone home.

A few things need the network by their nature. When you fetch email, open a web page, install an update, or use a service you set up yourself, that traffic goes where you sent it. That is you asking for something, not the device deciding on its own.

- No background telemetry. CalyOS Desktop, Server, and Embedded do not stream usage data, timing, or behaviour to us in the background. There is no hidden metrics pipe. - On-prem by default. On a domain-joined fleet, updates, roaming profiles, and policy all come from your own server if you run one. Nothing has to route through Calyraen. - Your services are yours. If you connect a mail host, a calendar, or a cloud drive, data flows to that provider on your terms. We are not in the middle of it.

## When you choose to send diagnostics

If something breaks, you can send us a diagnostic report. It is opt-in every time. Nothing is queued in the background waiting to be sent.

Before it leaves, the report opens in a plain viewer so you can read the whole thing. A typical report contains:

- Device and OS build: model, CalyOS edition and version, and which updates are installed. - The fault: the error code, the component that failed, and a short technical log around the moment it happened. - Hardware state: free memory, disk health flags, and driver versions relevant to the fault.

It does not include your files, your messages, your passwords, or a picture of your screen unless you attach one on purpose. You choose whether to send, and you can delete the report instead.

Step by step

Check what leaves before you send.

A diagnostics report is the main thing you might ever send us, and only if you choose to. Here is how to see its full contents first, decide what to include, and send or delete it.

  1. Open the report from where the fault happened

    When something fails, CalyOS offers to build a diagnostic report. You can also start one yourself from Settings, then Support, then Create diagnostic report. Nothing is sent at this stage. The report is written to your device and waits for you.

  2. Read the whole thing in the viewer

    Select Review before sending. The report opens as plain, readable text: your device model, the CalyOS build, the error code, and a short technical log from around the moment of the fault. Scroll through all of it. There is no hidden section.

  3. Decide what to attach, if anything

    By default the report carries no files, no messages, and no screenshots. If a screenshot or a specific log would help explain the problem, you can attach it here on purpose. If you would rather not, leave it as is. The choice is yours each time.

  4. Send, save, or delete

    Choose Send to submit the report to Calyraen support. Choose Save a copy to keep it on the device or hand it to your own IT team instead. Choose Delete to remove it entirely. If you do nothing, the report stays local and is never sent.

  5. Confirm nothing else is queued

    Open Settings, then Privacy, then Data that leaves this device. You will see that no report is pending and no background diagnostics are scheduled. This screen is the honest picture of what, if anything, is on its way out.

Questions

Common questions.

Does CalyOS send usage data back to Calyraen in the background?

No. There is no background telemetry stream. CalyOS Desktop, Server, and Embedded do not report your usage, timing, or behaviour to us on their own. The one thing that ever reaches us is a diagnostic report, and only when you choose to send it.

What is actually in a diagnostics report?

Your device model, the CalyOS edition and build, the error code, the component that failed, and a short technical log from around the moment of the fault. It also notes basic hardware state like free memory and driver versions. It does not include your files, messages, passwords, or a screenshot unless you attach one yourself.

If I run my own server, does anything still route through Calyraen?

No. On a domain-joined fleet, updates, profiles, and policy can all come from your own on-prem server. Once you point the machines at it, Calyraen is not in the path. You can confirm this in Settings under Data that leaves this device.

Related topics.

Imagery in production
Encryption

Scrambled unless it is you.

Your files are scrambled on the device, and again while they travel. Only someone with the key can read them, and on Calyraen gear that key can be yours.

Two states

At rest and in transit.

At restIn transit
What it covers Data sitting on a drive: your files, your photos, the system itself. Data moving over a network: a page loading, a file syncing to your own server, a backup copying across the building.
How Calyraen protects it AES-256 full-disk encryption. TLS, the same standard your bank uses.
What that stops Pull the drive out and plug it into another machine, and it reads as noise without the key. It is encrypted the moment it leaves and decrypted only at the far end.
At-rest protects the device you can hold. In-transit protects the wire between two devices.
Calyraen
Who holds the key

Keys you can hold.

Encryption is only as private as who holds the key. Our stance is simple: where we can, the key is yours.

  • On the device, the unlock key can be bound to a hardware security chip, your sign-in, or a passphrase. We do not keep a copy.
  • On-prem, when you run CalyOS Server in your own building, you hold the keys to what it stores. There is no Calyraen key that opens your data.
  • End-to-end, offered where the feature supports it, means data is encrypted before it leaves your device and only the intended recipient can open it. Nobody in the middle, including us, can read it.

If you lose your key and there is no recovery key, we cannot recover the data. That is the honest trade for real privacy.

Common questions.

At-rest encryption protects data stored on a drive, so a lost or stolen device is unreadable. In-transit encryption protects data as it moves across a network, so nobody can read it on the wire. Calyraen uses both: AES-256 for storage and TLS for transfers. You want both because they cover different moments in a file's life.

On many Calyraen devices it ships on by default, but you should confirm. Open Settings, Security, Encryption and check the status reads On. If it is off, you can turn it on there and save a recovery key at the same time.

No, not where you hold the key. On-device and on-prem, the unlock key stays with you or your admin, and we keep no copy. Where end-to-end encryption is offered, data is locked before it leaves your device and only the recipient can open it. The honest flip side is that if you lose your key and your recovery key, we cannot recover the data either.

Related topics.

No ad-tech or profiling

Unwatched

CalyOS ships with no ad networks, no third-party trackers, and no behavioural profiling. We do not build a picture of you, and we never sell your data.

What we do not do

What we do not do.

CalyOS is not funded by advertising, so the machinery that ad funding requires is simply absent.

Why

You are the customer, not the product.

Because you buy the device and the licence, you are the customer. On ad-funded platforms, the advertiser is the customer and your attention is the product being sold. That difference decides how the whole system is built.

Imagery in production

No ad networks

The OS does not embed ad SDKs, ad auctions, or sponsored placements. There is no code path that fetches an ad.

No third-party trackers

We do not bundle analytics beacons, pixels, or tracking libraries from other companies into the system or its first-party apps.

No behavioural profiling

We do not stitch together what you open, search, type, or install to model your interests, mood, or likely purchases.

No data sale

We do not sell, rent, or trade your personal data. It is not a revenue line, and there is no arrangement that would let a third party buy access to it.

Why it holds

Why this holds up.

Promises are easy. These are the reasons it stays true in practice.

  • The business model. Calyraen earns money when you buy hardware, licences, and support. It does not need your behaviour to sell ads, so there is no pressure to collect more than the product needs.
  • On-device by default. Search, suggestions, and most processing run locally. Data that never leaves the device cannot be profiled by anyone, including us. See the What leaves your device tab for the detail.
  • Inspectable. The Activity and Network views let you watch what the system actually does, and independent testers can do the same. Claims that can be checked tend to stay honest.

Common questions.

We sell hardware, CalyOS licences, and support and services. That is the whole model. Because our income does not depend on advertising, we have no reason to collect your behaviour or build a profile, and no product to sell advertisers.

Yes, an app you choose to install can request network access and collect data under its own terms, just as on any platform. CalyOS limits what apps can reach through permissions, and the Activity view shows you what each one is doing so you can revoke access. The no-ad-tech guarantee covers CalyOS and Calyraen's own apps.

Any suggestions you see, such as recently used apps or files, are worked out on the device from your own activity and stay on the device. They are not sent to us, not matched against an advertising profile, and not shared with third parties. You can turn them off in Settings.

Related topics.

Standards & audits

Built to be checked.

We build to the privacy laws that apply to you, and we let outside experts test our work. This page explains the rules we follow, the paperwork businesses can sign, and what happens if something goes wrong.

## The laws we build to

We design our products to meet the privacy laws that apply where our customers are, rather than the minimum we could get away with.

- GDPR and UK GDPR. These set the baseline for how we handle personal data: a lawful reason to process it, clear rights for the person it belongs to, and limits on how long we keep it. - CCPA and similar US state laws. We honour access, deletion, and opt-out rights for residents of states that grant them. - Sector rules. Where you work under rules like HIPAA-style health requirements, our on-prem and Server products let you keep data inside your own walls, which makes meeting those rules easier.

Because CalyOS and our hardware favour local and on-prem processing, a lot of data never leaves your control in the first place. That reduces how much of the law depends on us at all.

## Independent audits

We do not ask you to take our word for it.

- Outside security testing. We hire independent firms to test our software and update systems, including the parts that sign and deliver updates for the full 7-year support life. - What we publish. We publish a summary of each major review, the date it happened, and the status of anything it found. Serious findings are fixed before we call a review closed. - On request. Business customers under agreement can ask for the detailed report and our written responses.

We treat an audit as a normal part of shipping, not a one-off event.

Step by step

Get a data-processing agreement.

If your company handles personal data on Calyraen hardware or CalyOS, you may need a data-processing agreement (a DPA) on file. Here is how to request and complete one.

  1. Confirm you need one

    A DPA covers cases where Calyraen processes personal data on your behalf, for example when you use a service we host. If everything runs on your own devices and on-prem, and no personal data reaches us, you often do not need one. If you are unsure, ask us and we will tell you plainly.

  2. Request the current agreement

    Sign in to your account and open Legal, then Data agreements. Download the current DPA and the list of any sub-processors we use. You can also email privacy@calyraen.com and we will send the same documents.

  3. Read the sub-processor list

    The DPA names every third party that could touch your data, what they do, and where they are based. If you object to a sub-processor, tell us before you sign. We will not add new ones without notice to you.

  4. Fill in your details

    Complete your legal entity name, the categories of data involved, and your contact for privacy matters. Keep a copy for your own records.

  5. Sign and return

    Sign electronically in the account portal, or return a countersigned PDF to legal@calyraen.com. We countersign and send the final version back. Store it with your other compliance records.

  6. Keep it current

    We tell you before the terms or the sub-processor list change. Review the agreement once a year, or whenever your use of our products changes, so it still matches what you actually do.

Common questions.

We give you our audit summaries, the DPA, and the sub-processor list, which together cover what most auditors ask for. Business customers under agreement can request the full reports and our responses. We will point you to exactly which document answers which question so you are not guessing.

That depends on where you and your users are, not where Calyraen is. GDPR covers people in the UK and EU; several US states have their own rules. If you tell us where you operate, we will tell you which of our documents and controls are relevant to you.

We investigate at once, contain the problem, and work out who and what is affected. Where the law sets a deadline, such as the GDPR notice period, we notify the relevant authority within it. We tell affected people directly, in plain language, with the facts we have and the steps we are taking, and we follow up as we learn more.

Related topics.

We value your privacy

We use cookies to run this site and, with your consent, to analyse traffic and improve your experience. You can accept all, reject non-essential, or choose by category. Learn more

Strictly necessary
Required for the site to work — security, sessions, and remembering this choice. Always on.
Preferences
Functional cookies — remember your language, region and interface choices.
Analytics
Help us understand how the site is used so we can improve it.