How we keep your family's information safe

RubyLou is built so that each family's records stay with that family. Here's how, in plain terms.

Your records are locked to your account

Every table that holds family information has database rules that let a signed-in parent see only their own family's rows. Visitors who aren't signed in can't read any of it.

The keys stay on our side

The key that can reach every record is kept on RubyLou's servers and never sent to your browser. Automated tests check this on every change.

Less information goes out

Your password is stored only in scrambled form.
Error reports have the fields that hold names, emails, zip codes and notes removed before they're sent.
Our server logs don't record names, emails, zip codes or notes.
There's no session recording, ad tracking or analytics inside the app.
Every connection to RubyLou is encrypted.

Every change is checked

Before any change goes live, it passes automated tests, including tests that try to read another family's records and must fail. Changes that touch sign-in, family data or security get an independent review first.

If something goes wrong

No system is perfectly secure. If we learn of a problem that exposed your family's information, we'll tell you without unreasonable delay: what happened and what we're doing about it.

Found a problem?

If you think you've found a security problem, please write to hello@learnwithrubylou.com before sharing it anywhere else. We'll reply, and thank you.

← Back to RubyLou