Sub-processors
v0.1-draft · last reviewed 15 September 2026
Working draft. This page says how Clarvyn intends to operate. It has not been reviewed by a Ghana-qualified lawyer, and the wording will change when it is. We publish it now because a school deciding whether to trust us with children’s records should be able to read what we claim to do. Tell us where it is wrong: support@clarvyn.ai.
Who else can touch a school’s data
Clarvyn is built by Roam Labs and runs on infrastructure operated by the companies below. There are no others: no analytics vendor, no advertising network, no data broker, and no customer-support tool with a view of school records.
| Who | What they do for us | What they can see |
|---|---|---|
| Railway | Runs the application servers and the PostgreSQL database that holds every school's records. | All of it. |
| Cloudflare R2 | Stores uploaded files: school crests and banners, student photographs, and documents. | Files a school uploads, and the names they were given. |
| Resend | Sends email: account setup links, notices, and the demo requests from this website. | Name and email address of the recipient, and the contents of the message. |
| mNotify | Sends the SMS codes parents use to sign in to the parent app. | The mobile number the code is sent to. |
| Flutterwave | Card and mobile-money payment processing, where a school turns it on. | Payment details of the person paying, handled by Flutterwave rather than by us. |
What this page does not yet say
We have not yet countersigned a data-processing agreement with each of these vendors, and we have not fixed the region each one runs in. Both are in progress and both will be stated here when done, rather than left to be assumed. See data protection.
Changes
If we add a vendor that can see school data, this page changes first. A school that has asked to be told will be told.