Skip to main content

Security and FAQ

Where does rubry.ai keep my agent's key?​

Only in your browser: an HttpOnly, Secure, SameSite=Strict cookie, sealed with AES-GCM by rubry.ai's server, so scripts on the page can't read it and it is unreadable without the server's secret. rubry.ai keeps no account and stores no copy. Each message is sent to your endpoint from rubry.ai's servers, with that key.

Clearing your cookies, or Remove in the connect dialog, forgets it. The cookie lasts 30 days.

What does rubry.ai keep from my conversations with it?​

Like conversations with Rubry's own agents: the last messages of each chat, to give the agent context and list your chats in the sidebar, kept for up to three days and tied to your connection for the day, not to an account.

How are keys kept in my deployment?​

  • API keys (rk_…): only a SHA-256 hash is stored; the key is shown once, when created.
  • Your provider's key: AES-GCM encrypted with SECRET_KEY, and sent only to your agents Worker, over a service binding.
  • The agents Worker has no public URL; set AGENTS_API_KEY on both Workers for a second lock.
  • Tool secrets live in the agents Worker's secrets and never reach a prompt.

Do my agents count against Rubry's limits?​

No. Messages to an agent you connected skip Rubry's daily message allowance and budget; only the general anti-abuse checks apply (a valid session and a few requests a minute). Your agent's model usage is billed by your provider, or by your Cloudflare account for Workers AI.

Is the example safe to use?​

example.rubry.ai runs in demo mode: its admin token is public, so it can't change the provider or agents, nobody can see others' keys, and keys expire in a day. Don't send it anything private.

License​

The template and the library are free software under the GPL-3.0: you can use, change and redistribute them, and works built on them that you distribute must stay under the GPL too.