Legal
Privacy Policy
Last updated: October 9, 2026
Local session processing
relai reads existing AI coding session files without modifying the originals. Reading, caching, search indexing and cost estimates run on your device. Local settings, cached session data, archive state and generated reports are stored on your device. Local-first does not mean every feature works offline or that no data is sent to services.
AI features and providers
Summaries, issue scans, classification, study reports and handoff preparation can send session excerpts and project context to the configured AI provider. These may use your installed AI tools or configured AWS Bedrock credentials. Jev uses TypeSafe's API when enabled with a token. Jev masks recognized credential patterns; this cannot guarantee removal of every secret. Ollama can run locally, but selecting it does not prevent cloud requests when provider fallback is enabled. Review AI provider and fallback settings before processing sensitive sessions, including scheduled scans.
Sign-in and licensing
Google sign-in and online license checks communicate with authentication and licensing services. Account email, license and subscription information are processed to provide trial access and paid features. Payment and billing flows use Stripe. License credentials are stored locally with Electron's operating-system-backed encryption when available. Licensing requests do not include session transcripts.
Sync, teams and exports
Cloud sync is disabled by default. When enabled, selected session files and archive metadata are uploaded; session files are encrypted with AES-256-GCM before upload using a key supplied by the sync service. This is not a device-only key system. Team reporting sends aggregate usage and cost data; optional session sharing sends titles, project names, tool, timestamps, token counts, cost and tags, without transcripts. Export integrations such as Notion, Readwise and Linear send the content selected for export to those services. Obsidian exports write files to your selected vault.
Product analytics
The desktop app uses Pendo for high-level navigation and feature events, with a pseudonymous identifier derived from the signed-in email and plan/license information. The app disables automatic interaction capture and text collection to keep prompts, session contents and project paths out of those events. Product analytics is enabled by default and can be disabled in Preferences → Product Analytics.
Website analytics
This website uses configured PostHog analytics and a first-party event collector to understand page visits and button clicks. Marketing events include page paths, browser information, landing path, external referrer hostname and selected campaign parameters. The event collector also records IP address and user-agent information on the server. The collector's storage has a 730-day expiration lifecycle. These are usage analytics, not a promise of anonymous browsing; authentication routes are excluded from marketing events.
Managing your data
You can disable product analytics, cloud sync and optional team session sharing in Preferences. Removing local caches does not delete source sessions, and removing local files does not by itself remove data already exported or uploaded. Account, billing, sync and third-party service data are handled separately. Contact support@relai.fyi for questions about information held by relai or requests concerning your account.
Contact and updates
Questions about this privacy information can be sent to support@relai.fyi. We may update this page as the application and services change; the revision date is shown above.