Sub-processors

1. The current list

Each of the following processes personal data on our behalf in order to deliver part of the platform. Every one is bound by terms no less protective than the Data Processing Agreement.

• Supabase — managed PostgreSQL database and authentication. Holds the School's records. Encrypted at rest and in transit.
• Cloudflare R2 — object storage for uploaded files: photographs, documents, certificates and imports.
• Vercel — application hosting and delivery. Processes requests; does not store the School's records.
• Razorpay — payment processing for school fees and for the software subscription. Handles card and bank details directly; we receive only a reference. PCI-DSS compliant.
• ZeptoMail — transactional email delivery: receipts, notifications and account emails. Receives recipient addresses and message contents.
• Sarvam AI — the language model behind the built-in assistant. Receives the text of a question and the results of the lookups run to answer it. Receives no bulk export and no direct database access.

2. What the assistant sends

This is worth being precise about. When someone asks the assistant a question, what reaches the model is the conversation text and the output of the specific lookups the model chose to run — for example a set of totals, or a class list. There is no shared index across schools, no training on a School's data, and no way for a request to name a school other than the signed-in user's own.

A School that does not want the assistant used at all can have it disabled for its tenancy.

3. Changes to this list

We will give at least thirty days' notice before adding or replacing a sub-processor, and a School may object on data-protection grounds as set out in the Data Processing Agreement.