Ubriot privacy policy

Ubriot is mobile release infrastructure for engineering teams. We collect and process data needed to authenticate users, run builds, manage release artifacts, submit to store channels when requested, send push notifications when configured, provide support, secure the service, and operate billing.

Last updated: 25 July 2026.

Data we collect

Account data

Name, email address, password hash, session tokens, team membership, and role information.

Release data

App names, bundle identifiers, repository metadata, build settings, build status, logs, artifacts, diagnosis, and store handoff state.

Credential records

Credential metadata and encrypted credential material needed to run requested release workflows.

Device data

Push tokens, platform, installation identifiers, and delivery logs when Ubriot Notify or Preview device registration is used.

Billing data

Plan, invoice, subscription, payment status, and billing provider references.

Operational data

IP address, user agent, request logs, security events, support messages, and error diagnostics.

How we use data

We use this data to provide the product, authenticate access, run requested workflows, store release history, protect accounts, diagnose failures, communicate with users, process payments, and satisfy legal obligations. We do not sell personal data. We do not use build logs, artifacts, or credentials for advertising.

Sharing and processors

Ubriot may use infrastructure, email, storage, payment, analytics, Apple, Google, and repository providers where needed to deliver the service. Those providers process data only for product operation, security, billing, support, or release workflows requested by the user.

Retention and deletion

Account and release records are retained while the account is active and as needed for security, billing, audit, product operation, and legal obligations. Users can request account deletion from the app or at ubriot.dev/account/delete. We remove account data that is no longer required and retain only records we are legally or operationally required to keep.

Security

Credentials are scoped to release workflows and protected in storage. We avoid exposing secret material in public records, app screens, logs, and support copy. Users should not paste passwords, private keys, or store credentials into support messages.

Contact

For privacy or support requests, email support@ubriot.dev. This policy is published at https://ubriot.dev/privacy.