How Armalo Vibe Cloud handles personal data. Last updated July 22, 2026.
This Policy covers personal data Armalo handles when you visit, register for, purchase, administer, or use Armalo Vibe Cloud, including support, security, sales, and business communications.
Independent model providers used with your own keys are governed by their own notices. A customer organization may provide its own notice for workspace content it controls.
Armalo is a controller for account identity, service administration, billing, fraud prevention, security, support, service communications, and legal compliance.
Armalo is a processor when it processes personal data in workspace content on a business customer’s documented instructions. The business customer is the controller for that content. Armalo does not sell personal data and does not use workspace content to train general-purpose AI models by default.
Account and OAuth data can include name, email, profile image, organization, workspace, role, identifiers, authentication metadata, and communication preferences. Google OAuth does not provide Armalo with your Google password.
Billing data includes billing identity, organization and tax information, plan, seats, invoices, transaction status, credits, and metered usage. Payment card details are handled by the payment processor; Armalo may receive limited card metadata.
Workspace content can include prompts, messages, source code, files, agent outputs, artifacts, integrations, collaboration events, approvals, and audit events. Telemetry can include IP address, browser, device, session, feature, error, network, and approximate-location data.
Armalo uses personal data to provide and secure accounts, workspaces, agents, builds, sandboxes, previews, integrations, billing, support, auditability, reliability, security, service communications, legal compliance, and aggregated anonymized metrics.
Workspace content is not used to train general-purpose AI models by default. Optional training use requires affirmative opt-in and separate disclosure.
Contract supports account creation, authentication, service delivery, workspace operation, billing, support, and requested integrations.
Legitimate interests support security, fraud prevention, reliability, product improvement, business administration, customer communication, and legal claims where those interests are not overridden by your rights. Consent supports optional cookies, marketing, and optional data uses. Legal obligation supports tax, accounting, sanctions, regulatory, and similar duties.
Armalo uses providers for Hetzner hosting in Germany and Finland, Cloudflare edge services, E2B sandboxes in EU or optional US regions, authentication, payments, communications, monitoring, support, and customer-selected model, repository, or integration services.
Workspace owners and administrators may access workspace data according to permissions. Armalo may also disclose data for valid legal process, safety, professional advice, or a protected business transaction. Armalo does not share personal data for cross-context behavioral advertising.
See the current subprocessor schedule →Armalo uses EU-primary infrastructure. Hetzner dedicated hosting is in Germany and Finland. Cloudflare uses a global edge. E2B US execution is optional when enabled.
Where EEA, UK, or Swiss transfer rules apply, Armalo uses a lawful mechanism such as an adequacy decision, eligible EU-US Data Privacy Framework coverage, Standard Contractual Clauses, the UK Addendum, or another lawful mechanism, with supplementary measures where required.
Personal data is retained only as long as needed for the stated purposes, contracts, and law. Billing and tax records may remain for seven years. Encrypted rolling backups expire through scheduled rotation. Legal holds and security investigations can create limited exceptions. Properly anonymized metrics may remain indefinitely.
Read the detailed retention schedule →Armalo uses access controls, tenant isolation, encryption, logging, credential scoping, change controls, backup protections, and incident response. The infrastructure posture uses Hetzner dedicated hosting, Cloudflare edge controls, and isolated E2B sandboxes.
No system is perfectly secure. Protect your authentication methods and configure workspace permissions for your use.
Read the security program →Depending on location and context, you may request access, rectification, erasure, restriction, portability, or object to processing. You may withdraw consent where consent is the basis and may have rights concerning solely automated decisions with legal or similarly significant effects.
You may complain to your local supervisory authority. Armalo may verify identity and authority. When Armalo is a processor, the request may be directed to the customer controller. Requests are not treated discriminatorily.
The Services are not directed to children under 16. You must be at least 18 to create an account under the Terms. Armalo does not knowingly collect personal data from children under 16 through the Services or data from children under 13 in a manner subject to COPPA without required parental consent.
Necessary cookies support authentication, security, continuity, and service operation. Preference and analytics cookies may be used where permitted and, when required, with consent. Armalo does not use cookies to sell personal data or for cross-context behavioral advertising as a standard practice.
The table below lists every cookie Armalo sets or reads on `app.armalo.ai`. Essential cookies are set regardless of choice; the optional `ab_visitor_id` cookie is set only after explicit consent. The consent banner is the single entry point for changing the optional analytics decision and is reachable from any marketing page.
Open the consent banner settings to flip the optional analytics category on or off. Reopening the banner settings is just as easy as the original decision (GDPR Article 7(3)). The audit log of consent changes is available to authorized operators at `/api/admin/consent-audit` and is retained for the period required by Article 5(1)(e).
Read the security program →California residents may request to know, delete, correct, or receive a portable copy of eligible personal information and may opt out of sale or sharing. Armalo does not sell personal information or share it for cross-context behavioral advertising and honors applicable opt-out preference signals.
Armalo may update this Policy as the Services, law, or practices change. Material changes receive at least 30 days’ notice unless law or an urgent security need requires earlier effect. The date at the top will be updated.
Armalo Inc. — Privacy questions and rights requests: privacy@armalo.ai. Legal questions: legal@armalo.ai. Do not send passwords, OAuth codes, API keys, or other secrets.
Every cookie Armalo sets or reads on app.armalo.ai. Essential cookies are functional necessities; the optional analytics cookie is set only after explicit consent via the consent banner.
| Cookie | Purpose | Category | Expiry | Data flow |
|---|---|---|---|---|
| ab_visitor_id | Anonymous visitor analytics | Optional | 1 year | Set client-side after explicit consent; the middleware reads it to thread anonymous telemetry events. No PII. |
| armalo_consent | Consent decision | Essential (functional necessity) | 1 year | Set regardless of the user's choice. The middleware reads it to gate optional telemetry; the banner reads it to decide whether to render. |
| armalo_consent_at | Consent timestamp | Essential (audit evidence) | 1 year | ISO-8601 timestamp of the most recent consent decision. Read by the consent audit endpoint as Article 7(1) evidence. |
| armalo.theme | Theme preference | Essential (preference) | 1 year | Stores the user's `light` / `dark` choice. The inline boot script reads it before the page renders to prevent a flash of the wrong theme. |
| armalo_session, armalo_account, armalo_oauth, armalo_oauth_pkce, armalo_csrf | Authentication & CSRF | Essential | 8 hours (session) / 12 hours (CSRF) | Bounded tokens issued by the canonical OIDC path; never raw credentials. See `apps/web/lib/google-oidc.ts` for the cookie attribute contract. |
| __Host-armalo_room | Workspace room bearer | Essential | ~4 hours + refresh grace | Cryptographic bearer minted by `/start`. See `apps/web/lib/room-cookie.ts`. |
| __Host-armalo_session_issuer | Signed session-issuer JWT | Essential | ~8 hours + refresh grace | Minted alongside the room bearer on every `/start` visit; httpOnly, secure, SameSite=Lax. See `apps/web/lib/room-cookie.ts` and `apps/web/lib/mint-session.ts`. |
| __Host-armalo_guest | Anonymous guest workspace key | Essential | 1 year | Anonymous admission for un-authenticated visitors. See `apps/web/lib/guest-cookie.ts`. |
| armalo_default_project | Browser-scoped default workspace | Essential | Until cleared | Remembers the most recently opened workspace. |
Reopen the consent banner settings at any time to flip the optional analytics category on or off. The change persists across reloads via the armalo_consent cookie and is recorded in the Article 7(1) audit log.
For the security posture that protects these cookies (TLS 1.3, AES-256 at rest, isolated execution, scoped credentials), see the security program.
Email privacy@armalo.ai. We may verify identity and authority before acting.
Contact privacy