Privacy Policy

Rippler is a monitoring service for scheduled jobs. This policy explains what we collect, why we collect it, and who else sees it. It covers rippler.io and the Rippler API.

What we collect

Your account. Your email address, which identity provider you signed in with and that provider’s id for you, and your timezone. We do not store a password, because Rippler does not have any — signing in is always Google or GitHub.

What you create. The monitors you set up, their schedules, and the history of pings they receive. If you invite someone to your team, we store the email address you invited.

Technical data. When you sign in we record the IP address and browser user agent of that session, and the time you were last active. Our servers keep ordinary request logs.

Payments. If you subscribe, Stripe processes the payment. We receive your subscription status and never see your card number.

Signing in with Google or GitHub

We ask for the minimum each provider offers: your email address and basic profile information. From GitHub that is the read:user and user:email scopes. We never request access to your repositories, your code, your files or your contacts, and we cannot read them.

Of what the provider sends back, we keep only your email address and the provider’s account id. We do not store your name or your avatar. Your email address is what identifies your account, which is why signing in with Google and with GitHub on the same verified address reaches the same account.

Cookies

We use three kinds, and no advertising cookies at all:

• A session cookie, set when you sign in, so the site knows it is you. Removing it signs you out.
• A short-lived sign-in cookie that exists only while you are being redirected to Google or GitHub and back. It expires in ten minutes.
• Google Analytics, to count visits to our public pages and understand which ones people find useful.

Who else sees your data

We use a small number of services to run Rippler:

• Stripe — payments and subscriptions.
• Resend — sending alert and account emails.
• Google Analytics — traffic statistics on public pages.
• Cloudflare — serving static assets.
• Akamai (Linode) — the server the application runs on.

We do not sell your data, and we do not share it for advertising. We will disclose data if the law requires it.

How long we keep it

Account and monitor data is kept while your account exists. Database backups are kept for fourteen days, and server logs for fourteen days, after which both are deleted. Expired and signed-out sessions are cleared automatically.

Your choices

You can turn off alert emails for your own account at any time from your account settings. You can end a signed-in session by signing out.

To get a copy of your data, correct it, or delete your account and everything in it, email us at contact@rippler.io from your account address and we will do it. There is no self-serve delete button yet.

Security

Traffic is encrypted with HTTPS. Session tokens are stored hashed, never in plain text, so they cannot be read back out of our database. No service can promise perfect security, but we keep the amount of data we hold small on purpose.

Children

Rippler is not intended for anyone under 16, and we do not knowingly collect their data.

Changes

If we change this policy we will update the date at the top, and tell you by email if the change is significant.

Contact

Questions about privacy: contact@rippler.io.