Privacy policy
Updated October 19, 2026
Ripple receives messages from your scripts, servers and tools and shows them to you. This page explains what Ripple keeps to do that, who else handles it, and how to delete it.
- Ripple keeps what it needs to deliver, sync and show your messages.
- Your messages are never used for advertising, analytics or training AI models.
- Ripple has no ads and no third-party trackers, measures only errors and speed, and doesn’t sell personal information.
What Ripple keeps
- Your account
- Your email address, the ways you sign in, and your settings, such as appearance and how sources are sorted.
- Messages and sources
- Everything sent to your account: titles, text, links, thread names and alert levels, with their read, archive, pin and snooze state. Sources keep their names, icons, images and default links. All of it stays until you delete it.
- Signed-in browsers
- For each browser, its description (for example, Safari on a Mac), how it signed in, and when it was last used, so Settings can list your devices.
- API keys
- Kept as a one-way hash that checks requests, and as an encrypted copy so you can reveal the key in Settings.
Signing in
Email codes. Ripple emails a six-digit code that works for five minutes. The email names the country the request came from, looked up from your IP address in a copy of IPinfo’s database on Ripple’s own servers, so IPinfo never sees it. Codes are stored only as keyed hashes.
Apple. Apple shares your Apple ID’s identifier, its verified email address, which can be a private relay address, and, the first time, your name if you choose to share it. Ripple keeps these with your account, along with the sign-in tokens Apple issues.
Google. Ripple asks Google only for your verified email address, never your name, photo, contacts or files, and accepts only Gmail and Google Workspace addresses. It keeps that address, your Google account’s identifier and the sign-in tokens Google issues. Ripple’s use of information received from Google follows the Google API Services User Data Policy, including its Limited Use requirements.
Staying signed in. A browser stays signed in while it’s used, for up to a year, and signs out after 180 days without use. Sessions don’t record IP addresses. To limit abuse, Ripple counts sign-in requests per IP address and deletes those counts a day after the last request.
Browser notifications
When you turn on notifications, your browser gives Ripple an address at its push service, run by Apple, Google, Mozilla or Microsoft depending on the browser. Each notification carries a message’s title, the start of its text, its link and its source, encrypted so only your browser can read it. The push service sees that a notification was sent, not what it says.
Cookies and browser storage
Ripple sets only its own cookies, each needed to run it: one that keeps you signed in, one that identifies this browser so it keeps its own layout, two that hold your language and time zone so dates read correctly, and a few that remember the layout. A short-lived cookie protects Sign in with Apple. Commands also remembers the last 12 commands you ran in this browser, such as going to a source, so it can list them first. That list stays in this browser until you clear its site data and is never sent to Ripple.
Images from senders
A source icon given as a web address, and any image inside a message, loads from wherever its sender hosts it. That host can see your IP address and browser when you view it.
Who else handles your data
Ripple shares personal information only with these providers, so they can run Ripple, or when the law requires it.
- Railway
- Runs Ripple’s servers and database in the United States.
- Cloudflare
- Carries traffic to Ripple’s addresses, and stores an encrypted copy of the database each night.
- Amazon Web Services
- Sends the emails with sign-in codes.
- Sentry
- Receives error reports and the timing of one in five requests and page loads. These can include the page’s address, your account’s ID and your browser’s description, never message content, email addresses, cookies or your IP address.
- Better Stack
- Checks that Ripple is up. It receives no personal information.
- Apple and Google
- Learn that you signed in to Ripple when you use them to sign in.
How long it stays
Messages and sources stay until you delete them. Deleted items wait in Trash for 30 days, then go permanently; Delete forever and Empty Trash remove them at once. Database backups hold everything, deleted items included, for up to about four weeks, and are used only to recover the service.
Security
Connections to Ripple are encrypted. Ripple stores messages on its servers so it can search, sync and show them; they aren’t end-to-end encrypted. Ripple looks at your messages only to fix a problem you report, or when the law requires it.
Your choices
You can delete messages and sources, revoke your API key and sign out other browsers at any time. To ask what Ripple holds about you, to correct it, or to delete your account, email [email protected] from the address you sign in with. Ripple deletes an account and its data within 30 days of the request; backups let go of it about four weeks later.
Children
Ripple isn’t meant for anyone under 13 and doesn’t knowingly collect their information.
Changes
When Ripple changes what it keeps or shares, it updates this page and the date at the top.
Contact
Questions about privacy go to [email protected].