Data and privacy
What RamenID stores about students and about you, and how it is protected.
For the legal version, read the Privacy policy and Terms.
About students
| Data | Why | How it is kept |
|---|---|---|
| Email address and school domain | To verify them, show you who verified, and dedupe repeat students | Stored with each verification, and shown to you in the dashboard, webhooks and emails |
| The 6-digit code | To check what they type | Only a salted hash is stored; it expires after 10 minutes |
| Their discount code | To show it to them and to you | Stored with the verification |
| IP address | Rate limiting | Used only as a temporary counter key, not saved with the verification |
The student's email is also saved in the discount code's metadata in your provider, and for Dodo Payments it is filled in on the checkout.
Students are told on the page that their address is used only to confirm enrolment and is shared with you.
About you
- Provider keys and tokens are encrypted at rest and never shown again.
- API keys are stored only as a hash and a short prefix.
- Webhook requests are signed so you can check they came from us.
Retention and deletion
There is no automatic deletion yet. Deleting a discount rule or disconnecting a provider keeps the verification history. To delete your account and its data, email us.
What a verification proves
A successful verification means the person could receive email at a recognised school domain. It does not prove they are currently enrolled.