Local-First by Design: Where Your Data Actually Lives
No account required to see how it works, no hidden database, no analytics pipeline reading your conversations. Here's the actual architecture.
"Local-first" gets used loosely in marketing, so it's worth being precise about what it means inside RG AI: your API keys and your model preference live in your browser's localStorage. Nowhere else. There's no database row with your key in it, because there's no database call that ever receives one.
What that means in practice
- Clear your browser data, and your keys are gone. There's nothing to delete on our end, because we never had it.
- Use RG AI on a different device, and you'll need to add your key there too, since it doesn't sync anywhere by default.
- A server breach can't expose keys that were never sent to the server in the first place.
What still touches our servers
To be fully transparent: your chat message and the model you picked do pass through a lightweight RG AI API route on their way to the provider, because browsers can't stream from most provider APIs directly without exposing CORS issues. That route forwards the request and streams the response straight back. It doesn't log message content or persist it anywhere.
Local-first isn't a slogan here. It's the reason there's no "forgot your data" support ticket to write.
Next up
Getting Started with RG AI in Under 2 Minutes