Last updated: June 24, 2026
Privacy note
This note explains what data Abra processes when someone visits the public site, signs in, configures their runtime, or manages deployments from the dashboard.
1. Data controller
Abra is operated by TRIGUB TECHNOLOGIES OÜ, Harju maakond, Tallinn, Kesklinna linnaosa, Narva mnt 5, 10117 Estonia. For privacy questions, contact us at filipp@trigub.tech.
2. Account and sign-in data
The platform uses Firebase Authentication for Google and GitHub sign-in. During sign-in, Abra processes the identity details needed to create a server session and connect the browser to the correct platform account, such as the authenticated user identifier and basic profile information returned by the sign-in provider.
Session cookies are used to keep dashboard routes authenticated. The dashboard has no local auth bypass; authenticated pages require a valid Firebase-backed session.
3. Settings and runtime configuration
Abra stores account settings in Firestore, including deployment-related preferences and the Telegram bot configuration required to start the runtime.
User-managed skill and API environment values are encrypted at rest before storage. Saved values are summarized with redacted metadata and fingerprints and are not returned to the browser as plaintext after save or import.
4. Deployment and orchestration data
When a user starts, stops, or updates their Abra runtime, the platform processes deployment records, operation status, runtime image details, and the configuration needed to orchestrate that runtime. In hosted mode, this can involve Kubernetes/AKS orchestration and generated runtime secrets for the user account.
5. Purposes, recipients, and retention
We process data to operate Abra, secure dashboard access, persist account settings, deploy and manage the user runtime, troubleshoot incidents, and comply with legal or accounting obligations.
Depending on the feature involved, data may be processed through services used by Abra, including Firebase for authentication and Firestore storage, deployment infrastructure for orchestration, and user-configured providers such as Telegram or publishing integrations when those values are supplied by the user.
We keep data for as long as needed to operate the service, investigate incidents, comply with legal obligations, or defend our rights. Exact retention periods vary by data type and usage context.
6. Your rights
Depending on applicable law, you may have rights to request access, correction, deletion, restriction, or objection to certain processing, and to contact a relevant supervisory authority. For requests, contact filipp@trigub.tech. You can also review the Legal statement.