For schools and madrasahs
School Data Protection & Procurement Information
A plain-language summary of the information Fitra Guard expects to process when a school asks for a proposal or uses the school service.
Roles at each stage
School enquiry
Fitra Guard uses the details submitted by a school representative to assess the request, prepare a proposal and respond. The enquiry is recorded in an admin-only organisation workspace and a notification is sent to the school partnerships mailbox.
Production service
The exact controller/responsible-party and processor/operator roles depend on the chosen deployment and applicable law. They must be recorded in the signed DPA before live school data is processed; this page does not make that legal determination for the school.
Information by purpose
| Stage | Information | Why it is used |
|---|---|---|
| Enquiry | Institution and contact details, location, estimated endpoint count, preferred currency, notes, landing page and optional campaign attribution. | Assess requirements, prevent duplicate submissions, prepare a proposal and reply. |
| Onboarding & administration | Authorised school users and roles, organisation and deployment identifiers, configuration, device/profile labels and service status. | Provision and administer the school's service with organisation-based access controls. |
| Filtering & activity | DNS requests and related operational information needed to apply filtering and, where enabled, show activity logs. | Apply the school's filtering configuration, troubleshoot delivery and display relevant activity. |
| Billing & support | Billing status and provider references where online payment is used, plus information a school chooses to include in a support request. | Administer the subscription, reconcile payments and resolve support requests. |
Do not submit learner names, health information, safeguarding records or other sensitive learner information through the public quote form. Those details are not requested to prepare a proposal.
How Fitra Guard delivers the service
Fitra Guard combines its account management, policy controls, school administration and support workflows with contracted infrastructure services. Named subprocessors, processing locations and transfer safeguards are supplied directly to authorised procurement reviewers and must be recorded in the signed deployment schedule.
| Purpose | Fitra Guard service | Procurement detail |
|---|---|---|
| Accounts & application | Fitra Guard application, authentication and service communications | Contracted infrastructure supports hosting, sign-in and transactional email. The signed schedule identifies the applicable subprocessors, locations and safeguards. |
| Network protection | Fitra Guard DNS filtering infrastructure | Processes DNS requests needed to apply the school's filtering policies, return DNS responses and provide agreed activity information. |
| Online payment, where used | Fitra Guard secure payment processing | A contracted payment service processes payer and payment information for supported online payment methods. Fitra Guard does not request banking details in the school enquiry form. |
| Public-site measurement | Optional analytics and marketing services | Public-site usage and campaign data is processed only after the visitor permits the relevant category. It is not required to deliver school DNS filtering. |
Retention, location and access
- Activity logs: retained for up to 30 days under the current public privacy policy.
- Enquiries and operational records: retained only while needed for the enquiry or service relationship and any applicable legal, accounting, support or dispute obligations. The school-specific schedule must set any more precise periods.
- Hosting and international processing: the actual deployment region, support access and transfer safeguards must be confirmed in the signed schedule before production use.
- Access: enquiry records are restricted to administrative access. Production access for school users must be scoped to their organisation and documented during onboarding.
What the school DPA must settle before go-live
- Legal entity names, contacts and privacy roles
- Documented purpose, instructions and data categories
- Data subjects and authorised school users
- Hosting location and cross-border safeguards
- Subprocessor list and change-notification process
- Access controls and agreed security measures
- Incident notification and rights-request assistance
- Retention, export, return and secure deletion
Request the contract pack or send procurement questions to admin@fitraguard.com. Privacy-rights requests can be sent to support@fitraguard.com.
Last reviewed: 26 August 2026. Also read the Fitra Guard Privacy Policy.