SAVEL
What SAVEL does with your school's data
Your school's data belongs to your school. Here is how we handle it, in plain terms.
We don’t store Social Security numbers. SAVEL keeps no SSNs — there is nothing to encrypt because there is nothing there. Where a school needs a Social Security card for enrolment, SAVEL records that the document arrived. The number stays on paper, in your file.
Two-step sign-in is available. Anyone at your school can add an authenticator app to their account, and a school can require it of its principal — the account that can reach the most. There is no text-message option, on purpose: that would put a phone company between your staff and their accounts. If someone loses their phone, a printed recovery code lets them set up a new one, and if the codes are gone too we can clear it and start them over.
We keep our outside services short. Four companies help SAVEL run, and that is the whole list. Supabase holds the database and sign-in. Cloudflare serves the site. Stripe handles card payments — card numbers go straight to Stripe and never reach SAVEL. Resend is our email provider.
SAVEL sends nothing to an AI. There are no AI features in SAVEL and no connection in it to any AI service, so your school's records have nowhere to go.
You get a human, not a queue. When you have a question, you reach a person who knows the platform and wants to partner with your school — not a ticket number.
Ask us anything
Have a question about how we handle your school's data? Write to security@savel.app and a person will answer you plainly. If you think something here is wrong, tell us that too — we would rather be asked than have it discovered.
A full data-handling document is available on request. It covers the mechanics behind everything on this page, and the things SAVEL does not do yet. Ask and we will send it.