Contact us

Request a Child Protect Platform briefing.

Talk through your safeguarding workflow, school structure, evidence requirements, security expectations, and rollout model.

Designed to support PDPA-aware safeguarding operations in Thailand.

Child Protect Platform helps schools and child-focused organizations improve data control, evidence preservation, user access, and auditability in ways that support responsible Thailand-focused safeguarding operations.

Request a safeguarding platform briefing.

This briefing request is for schools, education groups, safeguarding teams, IT teams, and child-focused organizations that want to discuss fit, security, rollout approach, and next steps.

Suggested information to include

1
Organization

School name, group name, or organization type.

2
Scope

Number of schools, campuses, users, or safeguarding teams.

3
Main interest

Reporting, case management, evidence preservation, security, Thai/English support, or multi-school administration.

Contact

Email: info@childprotect.co

For security questions, contact security@childprotect.co.

For privacy questions, contact privacy@childprotect.co.

Tip: Do not send child data, case records, evidence, passwords, or sensitive incident details through ordinary email. Use email only to request a briefing or discuss onboarding.

What a demo can cover.

Structured reporting, case lifecycle, school and tenant administration, role-based access, encrypted evidence preservation, audit records, security controls, Thailand alignment, and rollout planning.

For leadershipGovernance, accountability, risk reduction, and multi-school oversight.
For safeguarding teamsReports, triage, notes, evidence, status, and review workflows.
For ITHosting, hardening, access controls, backups, monitoring, and deployment model.
For administratorsTenants, schools, users, roles, onboarding, lock/unlock, and reset links.

Who should request a demo?

A briefing is useful for anyone responsible for safeguarding operations or sensitive school data.

The best demos include both safeguarding and operational stakeholders so the discussion covers workflow, evidence, access, security, and rollout.

School owners and directors

Review governance, risk reduction, accountability, and how the platform supports safer operations.

Principals and heads of school

Understand how reports, follow-up, evidence, and review activity can become more structured.

Safeguarding leads and counsellors

Walk through case intake, triage, notes, assignments, evidence, and case status tracking.

Multi-school administrators

Discuss school separation, tenant oversight, central reporting, and role boundaries.

IT and operations teams

Review hosting, access control, backups, security expectations, and integration needs.

Child-focused organizations

Explore how controlled records and accountability can support sensitive child-safety workflows.

Typical onboarding path

A clear route from first discussion to live use.

1

Confirm structure

Review schools, users, safeguarding teams, reporting process, and evidence needs.

2

Configure workflow

Set up roles, case categories, statuses, tenant boundaries, and evidence handling.

3

Train key users

Prepare administrators and safeguarding users before wider staff access is enabled.

4

Launch and support

Begin live use with a clear support path and room for future workflow adjustments.

What to expect from a demo.

A demo is designed to help you understand whether Child Protect fits your safeguarding workflow, school structure, and security needs.

Workflow discussion

Walk through how your team currently receives concerns, reviews cases, stores evidence, and reports activity.

Platform overview

See how structured reporting, role-based access, case tracking, and evidence preservation work together.

Setup and pricing

Discuss tenant setup, school count, user roles, customization needs, integrations, and likely implementation path.