Privacy Policy

Account information. Your email address, a securely hashed password, and your two-factor settings if you enable them.

Infrastructure configuration. The servers you connect and what the platform detects about them, your monitors and where their alerts go, and your backup sources, destinations and schedules — together with the credentials needed to operate them, which are encrypted.

Automation, monitoring and backup records. The runs you start — the playbooks, templates and commands, with what each server printed — server resource readings, monitor check results, incidents and the fixes attempted on them, and backup and verification records.

Billing information. Your subscription and invoices.

Database passwords. Backups read your databases with the server’s own administrator access, so we never ask for a database password.

Backup contents. Backups upload directly from your server to storage you own, and restore tests run on your server. When you download a copy that is kept on your server, it is streamed through the platform to you and not stored.

Payment card details. These are handled entirely by our payment provider and never reach our servers.

Conversations with Juni. Questions put to our assistant, and its answers, are not stored and not used to train anything. See below.

Juni answers questions on this website and in the dashboard. It runs on our own servers from an open-source model: your question is not sent to any other company, and no third-party AI service is involved.

Nothing is kept. A question and its answer are not written to a database or to a transcript. The conversation stays in your browser tab and is gone when you close it; the last few exchanges travel with each question only so a follow-up makes sense.

When you are signed in, Juni may describe your own account — your servers, monitors, backups, runs and subscription — to answer you. It never describes anybody else’s account, and on this public website it cannot see an account at all. It can read; it cannot change anything, start a run or reach your servers.

To run the service: carrying out the playbooks, templates and commands you start, running your monitors and the automatic fixes you allow, and taking and verifying your scheduled backups.

To support you: answering your questions, and diagnosing failures using the run, monitoring and backup records attached to your account.

To bill you, and to send necessary account messages such as password resets.

To keep the platform secure and to meet our legal obligations. We do not sell personal data, and we do not share it for advertising.

A small number of providers help us run the service: hosting for the platform itself, a payment provider for subscriptions, and an email provider for account messages. Each receives only what it needs to do its job.

Your own hosting provider is not one of ours. You chose them and you pay them directly — we are not a party to that relationship.

Account and infrastructure information, run history, incidents and backup records are kept for as long as your account is open. Monitor check results and server resource readings are kept for thirty days.

When you close your account we delete your data, except where we are required to keep records such as invoices — which also means a refund request can still be verified after an account has closed. Nothing on your servers is removed, and backups in your own storage stay there: closing your account removes the platform’s access, not your data.

Server passwords and keys, sudo passwords and storage keys are encrypted. Once saved, none of them can be read back through the dashboard or the API — you can replace one, but nobody can retrieve it.

A sudo password is given to sudo on its standard input rather than on a command line, and each server’s identity is verified on every connection. Commands you run are kept in your run history exactly as you typed them, so do not put passwords or tokens in them. Your backups we have deliberately arranged not to hold at all.

You can view and update most of your information directly in your dashboard, and you can close your account at any time.

You can also ask us for a copy of the information we hold about you, ask us to correct it, or ask us to delete it. Depending on where you live, you may have additional rights under local data protection law.

We may update this policy as the service changes. If a change is significant, we will tell account holders rather than quietly updating this page.

Questions about this policy, or about your data, can be sent through our contact page.