Privacy and telemetry

Aseptic includes diagnostic telemetry to detect and fix its own failures. It’s opt-in: it ships off and first launch asks you. Nothing is sent until you turn it on, and you can change your mind at any time.

What is collected

Only when Aseptic suffers an error, a report is sent that may include:

• The message and trace of Aseptic’s own exception.
• The version, the operating system and technical data of the environment.
• A pseudonymous installation identifier (random, local) that holds neither your name nor your email, but tells one installation from another.
• The IP address from which it is transmitted, processed by the provider during sending.

What is NOT collected

• The content, the output or the logs of your microservices are not collected.
• Your credentials, tokens or secrets are not collected: before sending anything, a scrubber redacts your user folder path and the values of known credentials.
• The provider’s automatic collection of personal data is not enabled.

Provider and location

The provider is Sentry. The data is sent to its European Union region (Germany) and kept for the configured retention period (by default, 90 days).

How to turn it on or off

• In the app: Settings → Privacy → “Send error diagnostics”.
• In the CLI: aseptic telemetry on / aseptic telemetry off.

Once turned off, Aseptic stops sending any report (the SDK doesn’t even initialize).

Report a problem

From Settings → Support → Report a problem you can describe unexpected behavior for the team to review.

It takes the same path and the same switch as automatic diagnostics —same provider, same region, same retention— but here you write the content: what travels is the text verbatim (subject and description) plus the pseudonymous installation id, and nothing else. Your services’ logs are not attached. It goes through the same scrubber, which recognises formats —a password in a URL, a token with a known prefix, your home folder— but does not guess: a client’s name pasted into the text travels as written.

Session and sign-in record

If the project has sign-in, the app remembers your session and renews it on its own, but not forever: 10 days after you last entered your credentials (auth.maxSessionDays), it asks for them again.

Every sign-in, every time you open the app with a remembered session, every sign-out and every expiry is recorded in your account: type, date, app version and pseudonymous installation identifier, no IP. You see them in the account portal, under “Recent sign-ins”, and they are kept for 365 days. Offline, they wait on the machine and are sent as soon as the connection is back (aseptic access sync).

Consent

Before signing in, the app asks you to accept the Terms of use and the Privacy policy; each acceptance is recorded with its version and date (aseptic consent info / history).

The full and current legal text is published together with the Software and on the project’s website.