RRiloBack to home

Security

Last updated: July 14, 2026

Rilo reads email, so we hold ourselves to a simple rule: collect as little as possible, keep as little as possible. This page describes, honestly and specifically, how the service is built to protect your data. For what we collect and why, see the Privacy Policy.

Your email content is not stored

When you ask Rilo to generate a reply, the email thread you are viewing is sent from your browser to our API and on to Google's Gemini API, and the suggestion comes back. That is the whole journey. Email content is processed transiently and discarded. It is never written to our database and never written to our server logs. The best protection for data is not holding it, so we don't.

Encryption in transit

All communication between the extension, our API, and our service providers uses HTTPS/TLS. There are no unencrypted hops.

Keys and credentials

  • The AI API key lives as a server-side environment variable on our hosting provider. It is never shipped inside the extension, so it cannot be extracted from your browser.
  • Passwords are managed by Google Firebase Authentication. We never see or store your password.
  • Password reset codes are stored only as one-way SHA-256 hashes, expire quickly, and allow a limited number of attempts.
  • We never store card numbers or payment details. Stripe handles all payment data.

API protection

  • Every API request is authenticated by verifying your signed-in session token on the server.
  • All endpoints are rate limited, per account and per IP where appropriate, to prevent abuse.
  • Payment webhooks from Stripe are cryptographically signature-verified before they are trusted, and processed exactly once.

Infrastructure

Rilo runs on reputable managed providers: Google Firebase (authentication and database), Netlify (website and API hosting), and Stripe (payments). Each maintains its own extensive security program and certifications. We deliberately run no servers of our own.

The extension's footprint

  • The extension requests no Google account permissions and no Gmail API access. It reads only the page you are viewing, only when you ask it to generate a reply.
  • It uses one Chrome permission — local storage (for your settings) — plus site access limited to Gmail, our own website, and Google's sign-in endpoints.
  • There is no analytics, tracking, or third-party code in the extension or on our website.

Deleting your data

You can permanently delete your account yourself from the dashboard. Deletion cancels any subscription, removes your billing profile at Stripe, and permanently deletes your data from our database and authentication system.

What we do not claim

We are a small product and we will not pretend otherwise. We do not currently hold formal certifications such as SOC 2 or ISO 27001, and we have not undergone third-party penetration testing. What we offer instead is a deliberately minimal design: no stored email content, no stored payment data, no analytics, and very little data to lose.

Reporting a vulnerability

If you believe you have found a security issue in Rilo, please email support@riloai.app. We will respond as quickly as we can and keep you informed while we fix it.