Skip to content
Patrol

Legal

Privacy Policy

Last updated: 16 September 2026

This policy covers the website at patrol.hellenic.dev and the hosted service, Patrol Cloud. The Patrol library runs inside your own process and sends us nothing; it is out of scope here on purpose.

1. Who we are

Hellenic Development ("we", "us") operates patrol.hellenic.dev and Patrol Cloud. For the data your service sends to Patrol Cloud we are the processor and you are the controller: it is your data, held on your instruction, and you decide what goes into an event. For your account details we are the controller. Write to contact@hellenic.dev about either.

2. The website

The pages are static files on GitHub Pages. There is no analytics script, no tracking pixel and no advertising cookie, and there never will be: a build check fails the deploy if one appears. GitHub, as the host, keeps standard server logs including IP addresses and timestamps. The one thing stored in your browser is the theme you picked, under the keyptl-theme, and it never leaves the device.

3. Your account

Signing in uses GitHub. We receive your GitHub user id, login, name, avatar URL and verified email address, and store them so the console knows who you are. We never receive your GitHub password and never ask for repository access. The session is a refresh token in a HttpOnly cookie plus a short-lived token held in memory by the console; nothing about your account is kept in local storage.

4. The events you send

Patrol Cloud stores each event exactly as your producer sent it: type, project name, message, the capture, send and receive timestamps, the fields you attached, any attached files, the Slack user IDs you asked to mention, and the stacktrace with its file paths and line numbers. That content is chosen by your code. If you put a customer email in a field, we hold a customer email.

We also keep the projects, ingest keys (as hashes), destinations and delivery results your account creates, and per-month counts of events and bytes for billing and quotas.

How long

Events are deleted when the retention window of your plan passes: Free 7 days, Pro 30 days, Business 90 days. Deletion drops the storage partition, so an expired event leaves nothing behind. Account records are kept while the account exists. Ask us to delete the account and everything under it goes within 30 days, apart from what tax law requires us to keep about a payment.

What we do with it

Store it, show it back to you in the console, and deliver it to the destinations you configured. We do not read your events, mine them, train anything on them, or sell or rent them to anyone.

5. Who else processes it

  • GitHub hosts this website and provides the sign-in. It sees your GitHub identity and the standard request logs of the pages you load.
  • Stripe handles payment when you take a paid plan. Stripe receives your billing details directly; card numbers never reach our servers. We store the customer and subscription references Stripe gives us and nothing else about the card.
  • A cloud infrastructure provider runs the API and the database that hold your events. Email us and we will name it, tell you which region the machines are in, and say what protects your data if any of it is processed outside the European Economic Area. Business customers get the same list in writing in the data processing agreement, and we tell you before we change it.

Destinations are a different matter. When you connect Slack, Discord, Twilio or an email address, we send your events there because you told us to, and what happens to them after that is between you and that provider.

6. Security

Everything travels over HTTPS. Ingest secrets are stored as SHA-256 hashes and compared in constant time. Credentials you give a destination are encrypted at rest with AES-256-GCM and are never returned by the API. The full account is on thesecurity page, including how to report a vulnerability.

7. Your rights

You can access, correct, export or delete your personal data, object to processing, or ask us to restrict it. The console does most of this directly: delete a project and its events go with it. For anything else, emailcontact@hellenic.dev and we will answer within 30 days. If our answer does not satisfy you, you can complain to your local data protection authority.

8. Changes

We update this page when the product changes. The date at the top is the last change. A change that affects how we handle your events will also be announced in the console before it takes effect.

9. Contact

contact@hellenic.dev, or thecontact page for the other ways to reach us.