Alesia Privacy Policy

This policy covers all of Alesia: the app, the browser extension and the console. The short version: checks run on your own machine, and data leaves your device only for the features described below.

Last updated: 19 November 2026

Data Controller

The data controller is seatbase Technologies GmbH, Starterzentrum, Geb. A1.1, Campus, 66123 Saarbrücken, Germany. Email: contact@seatbase.io. The seatbase website is covered by the separate website privacy policy.

What Alesia Is

Alesia has three parts. The app runs on your computer and does the checking. The browser extension is its companion in Claude, ChatGPT, Gemini and Microsoft Copilot, where it lets the app see what you are about to send. The console at app.getalesia.com is where an organisation sees what was synced. All three are covered by this policy. Alesia is a tool for organisations and their teams, and it is not directed at children.

What the Extension Reads

The extension reads the message you are about to send, the AI tool's own reply, and the address of the AI site in the current tab, on Claude, ChatGPT, Gemini and Microsoft Copilot only. It needs the reply because that is how token counts are measured, and it reads the name and type of a file you attach so your file rules can be checked. It reads no other page content.

Traffic Inspection

Traffic inspection is optional and stays off until you consent. When it is on, Alesia installs a local certificate and routes AI traffic through a proxy on your own machine, so requests and replies can be read from any application, not only the browser. That content is checked on the device and is not sent to us. You can turn it off at any time in Settings. In a company deployment your organisation may switch this on for you; the basis for that is described under Legal Bases.

Shadow AI Discovery

Shadow AI discovery is optional and stays off until you consent. When it is on, Alesia records which AI hostnames this device contacted, how often, roughly how much data moved, and which local program opened the connection. Executable and script paths are shortened so your home directory is removed. These daily counts are sent to us without your identity: the organisation is derived from the API key on your device. You can turn it off at any time in Settings. In a company deployment your organisation may switch this on for you; the basis for that is described under Legal Bases.

Agent Guardrails

Agent guardrails are optional and stay off until you consent; on macOS they also need Full Disk Access. With them on, an endpoint security extension lets Alesia see which file paths AI coding agents open, create or delete on this Mac, and which commands they run, including the working directory. Those paths and commands are what File Guard and Command Guard check, and the check runs on the device. File contents are not read for this. You can turn it off at any time in Settings. In a company deployment your organisation may switch this on for you; the basis for that is described under Legal Bases.

Every Check Runs on Your Device

Every check runs on your machine. The extension hands text to the app over the local loopback interface at 127.0.0.1 and receives a decision back. It sends nothing to a server and stores none of your text itself.

What the App Stores

The app keeps, locally on your computer: usage events such as provider, model, token counts and time; incidents, meaning the rule that fired, its outcome and the reason; decisions about text it has already checked; and the shadow AI daily counts described above. Values that were redacted stay on disk as they are, locally, because that is what lets a redacted message be restored later; parts that were allowed or removed are kept only as digests. Decisions about checked text expire after 30 days, and incidents remain until you delete them.

What Is Sent to Alesia

When you are signed in to an Alesia organisation, usage events and incidents are sent to our cloud API, and shadow AI counts too if that feature is on. A usage event carries a client id for the installation, the sensor that reported it, the provider, the model, token counts and a timestamp. An incident carries the organisation, the rule and the outcome, and no user, machine or client identifier, though in a small organisation the time, the tool and the device can still point to one person. A shadow AI count carries no identity at all. Signed out, none of these leave your device.

The Cloud Console

Usage, incidents and shadow AI counts appear in your organisation's Alesia console at app.getalesia.com. Your own administrators can review them there, change the rules and delete what they no longer need. Organisation members do not see each other's data; administrators see the whole organisation's. We access it only to run and support the service. When an organisation uses Alesia, that organisation decides what is collected and why, and we act as its processor. Without an account there is no console, and nothing is sent to us.

Audit Logs

Actions taken in the console are recorded: who added or removed a user, changed a rule or deleted data, when it happened, and the IP address and browser or app version the request came from. Your administrators can read this log; it is how they check who changed what. The log follows the retention periods below.

Analytics in the Console

The console uses PostHog, our analytics provider in the EU, to see how the product is used: which pages are opened, which actions are taken, and where errors happen. It runs only after you agree to analytics in the console, and it is never used for advertising. We do not record your sessions and we do not capture what you type. Once you sign in, analytics events are linked to your account, including your email address, so we can support you if something goes wrong. You can withdraw this consent at any time in the console's cookie settings.

Server Logs

Any request the app or the console makes to us, whether signing in, syncing or checking for an update, reaches our servers, which record the time, the IP address, the user agent or app version, and the endpoint called. We keep these logs for 7 days to detect abuse and diagnose failures, then delete them. They are not used to build a profile and never for advertising.

Your Account

Signing in gives us the email address on your account, the organisation you belong to, and the subscription and device records needed to keep this app authorised. Sign-in itself runs through Logto, our identity provider. A profile image or organisation logo you upload is stored with ImageKit, and notifications are delivered through Novu. Payments are handled by Stripe: card details go to Stripe directly and never reach our servers, and we receive the subscription status and the billing details Stripe reports. We use all of it to run your account, not to build a profile.

Product Telemetry

Product telemetry is optional and stays off until you consent. When it is on we send events to PostHog, hosted in the EU, under a random install id that is not linked to your account: the app being installed, started, stopped and updated, errors by category, which consents you granted, which settings changed, which sensors connected, and when you sign in or out. When encrypted traffic cannot be read, an event also carries the host involved, the local program, the certificate authority and the TLS fingerprint. No message content is included, and you can withdraw consent at any time in the app.

What We Never Do

We do not sell your data. We do not share it with third parties for advertising, and we do not use your messages to train models. Logto, Novu, ImageKit, PostHog, Stripe and Hetzner process data on our behalf under contract.

How Long Data Is Kept

On your device Alesia keeps its records until you delete them, and decisions about checked text expire after 30 days. In the cloud, audit logs are kept for 1 month on Free, 6 months on Pro, 1 year on Business, and as agreed for Enterprise. Incidents, usage and shadow AI analytics are kept for 6 months, 1 year and 3 years on the same plans. Server logs are kept for 7 days.

Legal Bases and Transfers

Where the GDPR applies, we rely on three bases: performance of a contract for your account and the service (Art. 6(1)(b)); our legitimate interest in keeping the service secure and working, which covers usage records, incidents, the checks themselves, and our audit and server logs (Art. 6(1)(f)); and your consent for traffic inspection, shadow AI discovery, agent guardrails, product telemetry and the console's analytics, which you can withdraw at any time (Art. 6(1)(a)). Where an organisation deploys Alesia to its team, that organisation decides the basis for those features, usually its legitimate interest in protecting its own data, and we act as its processor; the consent above is the basis when you use Alesia on your own device under your own account. We do not make automated decisions that produce legal effects about you. Our hosting and the cloud API run on Hetzner servers in Germany, and PostHog processes in the EU. Stripe handles payments under its own terms. Where any of our providers processes data outside the EEA, the transfer rests on the EU Standard Contractual Clauses or an adequacy decision. If a customer runs Alesia on their own infrastructure, that deployment is under their control.

Your Rights

You have the right to information about your stored personal data, to correction or deletion, to restriction of processing, and to data portability. You may object to processing at any time, withdraw any consent you gave, in the app's Settings or the console's cookie settings, and lodge a complaint with a supervisory authority. Write to contact@seatbase.io.

Changes to This Policy

We will update this page and the date above before we change what Alesia collects or where it goes.

Questions about this policy: contact@seatbase.io