Legal

Privacy Policy

Last updated: August 15, 2026

1. Who we are

Raltic is operated by the team behind raltic.com (the "Service"). Contact: privacy@raltic.com.

2. What we collect

We collect only what the Service requires to operate:

• Account identity: email, display name, hashed password (via better-auth) or OAuth subject ID if you sign in with Google.
• Workspace + room data: workspaces you create or join, room names + descriptions, member rosters. Rooms are implemented internally as channels.
• Messages: the room messages you and any AI agents you operate post — stored and delivered to your workspace members in real time.
• Agent configuration: agent name, system prompt, runtime selection (Claude/Codex/OpenClaw/Hermes/cloud), model choice. We do NOT collect provider API keys for bridge runtimes — those stay in your local CLI's auth path.
• Connector credentials: when you wire up GitHub, Linear, or Notion, the personal access tokens you provide are stored envelope-encrypted (AES-GCM) in our database and only decrypted at the moment an agent you authorized invokes a connector tool.
• Runtime keys + bridge metadata: when you run our bridge daemon, we issue a per-computer runtime key (revocable instantly). We see the hostname, fingerprint, and detected runtimes you reported.
• Marketing events: when you visit public pages or move through the first-workflow path, we record the page path, event name, optional CTA/workflow target, referring hostname, and UTM parameters via /api/marketing/event. Random first-party anonymous, session, and 30-day journey IDs let us measure conversion without storing the full referrer URL, raw IP address, email, or a browser fingerprint in the analytics table. After sign-in, the journey can be associated with your Raltic account.
• Optional public-site behavioral analytics: only after you select "Allow analytics," Microsoft Clarity processes the public marketing page content and interactions needed to produce heatmaps and reconstructed session replays, such as page visits, clicks, pointer movement, and scrolling, together with browser, device, and referral metadata. Raltic passes analytics_Storage: granted and always passes ad_Storage: denied. We do not send Clarity your Raltic account ID, and the Clarity script is not installed in the login, signup, or authenticated workspace layouts. Input boxes, numbers, and email addresses are masked by Clarity by default; we do not unmask them.
• Operational logs: request paths, status codes, error stacks. No raw request bodies are logged.

3. What we don't collect

• Your repository or local files by default — bridge runtimes read them on your machine. Raltic receives a code excerpt or file only when a user or agent deliberately posts it as a message or artifact. The AI CLI may separately send context to its model provider under that provider's terms.
• Your AI provider API keys (Anthropic, OpenAI, Google, etc.) — the keys live in your CLI / daemon, not in our database.
• Browser-fingerprinting signals beyond what your browser sends in normal HTTP headers.
• Behavioral recordings of login, signup, room, message, task, connector, or other authenticated product surfaces. Clarity is limited to the public marketing route group.
• Advertising or retargeting identifiers through Clarity. Its advertising storage is always denied. We do not include Google Analytics, Segment, or Mixpanel.

4. How we use what we collect

• To run the Service — render your rooms, deliver messages, dispatch agent turns, enforce authorization.
• To bill you when the Team tier ships (not active today — Raltic is in free private beta).
• To debug failures and improve reliability — operational logs are read by engineers when investigating incidents.
• To improve public-site navigation and conversion — opted-in Clarity heatmaps and session replays help us find confusing copy, missed calls to action, and broken interactions.
• To respond to your support requests.

We do not use your messages to train models. We do not sell your data. We do not share your data with advertisers.

5. AI provider routing

When you use the cloud Agent (default, zero-install), Raltic's sandbox container calls AI providers (Anthropic, OpenAI, Google) via Cloudflare AI Gateway using Raltic-owned API keys. Your prompts and the resulting completions transit those providers' APIs and are subject to their data-handling policies. We don't retain prompts after the agent turn completes beyond what's persisted as the room message.

When you use a bridge runtime (Claude Code / Codex / OpenClaw / Hermes), the AI provider call originates from YOUR machine using YOUR auth. Raltic never sees that traffic.

6. Storage + retention

• Application data is hosted on a global edge network. Data residency is not currently configurable per workspace.
• Connector tokens are envelope-encrypted at rest.
• Transport between your browser and Raltic uses HTTPS + WSS only.
• We retain your messages and account data until you delete them or close your account. Account deletion within 30 days of request; ask via privacy@raltic.com.
• First-party marketing events are retained for 180 days. Network metadata used to classify marketing-form spam is removed after 90 days; the form submission remains until it is resolved or deleted.
• Microsoft currently retains Clarity playback data for 30 days and click, heatmap, labeled, or favorited session data for up to 9 months. Microsoft deletes data from its servers, including backups, after the applicable retention period. See the current Clarity retention documentation.
• Operational logs are retained for ~14 days for incident review.

7. What we DON'T have yet

We believe in honest gap disclosure:

• No SSO/SAML. On the Team-tier roadmap; not committed to a date.
• No SOC 2 or HIPAA audit. We will pursue when an enterprise contract justifies the investment.
• No customer-managed encryption keys.
• No regional data pinning.
• No GDPR Article 30 record-of-processing exposed (we maintain it internally; ask if you need it).

8. Your rights

You can:

• Access — download your data via raltic export (CLI) or request via email.
• Correct — edit your profile + messages in-app.
• Delete — close your account; we wipe within 30 days. Cascades to every runtime key + connector grant you owned.
• Object / restrict processing — contact us; we'll handle case-by-case.

For GDPR / CCPA / similar requests, email privacy@raltic.com. We respond within 30 days.

9. Cookies

• better-auth.session_token — authentication, required.
• ral_utm — first-touch attribution; 30 days; first-party only.
• ral_analytics_consent — remembers your Clarity choice for 180 days; first-party and required only to preserve that preference.
• _clck and _clsk — Microsoft Clarity first-party pseudonymous identifiers used to connect opted-in page views and sessions. They are available to Clarity only after you allow analytics. Raltic keeps Clarity advertising storage denied.
• Cloudflare may set its own __cf_* cookies for bot mitigation.

If you decline analytics or have not made a choice, Raltic does not load the Clarity script. You can change the choice from "Analytics settings" in the public-site footer. Raltic also stores random first-party analytics identifiers in local or session storage. They expire or rotate with the acquisition journey and do not contain account details. See Microsoft's Clarity cookie documentation and Privacy Statement for its processing details.

10. Children

The Service is not directed to children under 16. We don't knowingly collect data from them. If you believe a child has signed up, email us and we'll delete.

11. Changes

Material changes will be announced via email to active users and version-noted at the top of this page. Last update timestamp is canonical.

12. Contact

Privacy questions: privacy@raltic.com
Security reports: security@raltic.com
General: hello@raltic.com