Privacy Policy

This Privacy Policy explains how NewbieStudio Co., Ltd. ("Company", "we"), operator of Braido (braido.ai), collects, uses, and protects personal data. Braido is local-first: your source code, workspace files, and full conversation content stay on your machine and are not uploaded to us. This policy describes the limited data we process to run your account, meter usage, process payments, and provide optional features such as multi-device sync and remote access.

1. Controller

The data controller is NewbieStudio Co., Ltd. Contact details are in Section 12.

2. What we collect

Account & authentication: email address (account identifier and sign-in); one-time login codes stored only as a short-lived hash; optional display name; Terms acceptance timestamp.

Device & session: device type, platform, app version, device name (for multi-device and remote access); session metadata — user agent, IP address, timestamps — for login management and abuse detection.

Usage & billing: usage metadata — token counts (input/output/cache), Credits charged, run status, model and provider used, timestamps; we do not store the full prompt or output as part of this metadata. Billing records via Paddle: plan, subscription status, transaction amounts, tax, and Paddle customer/subscription IDs.

Lightweight summaries (for sync & remote access): workspace summaries with a name and hashed path/project identifiers, counts, and feature flags — not file contents or full paths; conversation summaries with a title, a short truncated preview, status, and counts — not the full conversation; agent-run summaries; and User Memory items (facts/preferences) synced across your devices, with secret-like strings redacted before storage (Section 8).

Downloads: platform and version (anonymous, with a hashed IP, if you are not signed in).

3. What we do NOT collect

Because Braido is local-first, we do not collect or store on our servers: your source code or file contents; full conversation history or full AI outputs; workspace/project configurations, diffs, or checkpoints; secrets, API keys, or environment variables; or original uploaded attachments. Provider API keys are held server-side in our infrastructure (you do not provide your own) and are never exposed to your device.

4. How prompts reach AI Providers

To run a model, the desktop app sends your prompt and included context to our server-side provider gateway, which forwards it to the selected AI Provider to generate a response, metered in Credits. We do not retain prompt or response content as part of our stored data; however, the content is transmitted to and processed by the Provider. Paddle processes only billing metadata (not prompt content). See the sub-processor list in Section 6.

5. How we use data

To create and authenticate your account and manage devices/sessions; calculate, charge, and display Credit usage; process payments, subscriptions, and refunds through Paddle; provide optional sync, Remote Access, and related features; maintain security and prevent abuse; provide support; and comply with legal obligations. Where GDPR/UK GDPR applies, our legal bases are performance of a contract, legitimate interests (security, abuse prevention, operation), consent (where required), and legal obligation.

6. Sub-processors

We require sub-processors to handle data consistently with this policy and applicable law. AI Providers process content under their own terms; we recommend reviewing the terms of any model you use.

7. International transfers

We and our sub-processors may process data in countries outside your own, including the United States and other jurisdictions where Providers operate. Where required, we rely on appropriate safeguards such as standard contractual clauses.

8. Security

We apply measures appropriate to the data, including: secret redaction (maskSecrets) stripping keys/tokens from logs and free-text fields before storage; encryption in transit (HTTPS/TLS, HSTS in production); hardened authentication (passwordless OTP with hashed, short-lived codes; short-lived 5-minute access tokens with 30-day refresh tokens and device revocation; auth rate limiting); webhook integrity (HMAC-SHA256, fail-closed in production); application isolation (context isolation, tool sandboxing, agent approval controls); and tenant isolation (per-user scoping; relay isolation). No method of transmission or storage is perfectly secure, and we cannot guarantee absolute security.

9. Data retention

Usage records and credit-ledger entries: at least 12 months for accounting, audit, and tax. Account, device, and billing records: for the life of your account and as required for legal/tax obligations after closure. One-time login codes: deleted shortly after expiry (within ~10 minutes). Relay commands: short-lived (typically up to ~1 hour). On Account deletion we delete or anonymize your personal data except where retention is legally required (e.g. tax and transaction records).

10. Your rights

Depending on your jurisdiction (Korea's PIPA, EU/UK GDPR, CCPA), you may access, correct, delete, object to/restrict, or port your data, and withdraw consent. Contact us at Section 12 to exercise these rights; we respond within the period required by law. You may also complain to your data-protection authority — in Korea, the Personal Information Protection Commission and KISA's privacy report center (118).

11. Children

The Service is not directed to children under 14, and we do not knowingly collect their personal data. If you believe a child provided us data, contact us and we will delete it.

12. Privacy contact

NewbieStudio Co., Ltd. · Person responsible for personal-data management: Seon Hong Kim
201ho 110 38, Ewhayeodae 1-gil, Seodaemun-gu, Seoul, 03766, Rep. of KOREA
Email: [email protected]

13. Changes

We may update this policy, posting the updated version with a new "Last updated" date and, for material changes, additional notice (e.g. email or in-app).