Public business information
Demo requests, contact enquiries, partner applications and resource preferences should contain only the information needed to respond to the person or organisation.
DATA & PRIVACY
School information deserves clear boundaries.
BL TECHNO separates public marketing, authenticated school operations and privileged administration so each environment can be governed for its purpose.
PUBLICBLTECHNO.NETMarketing, demos, resources, contact
↓
AUTHENTICATEDSchool AppAuthorised school, teacher, student and driver workflows
↓
PRIVILEGEDGlobal AdministrationSeparate protected security boundary
THREE DATA CONTEXTS
Do not mix marketing information with school operations.
Different information needs different access, purpose and retention decisions.
School operational records
Learner, family, attendance, finance, workforce, learning and transport records belong inside authorised school workflows—not public marketing pages.
Privileged platform administration
Global administrative controls remain separate from ordinary public, partner and school-user experiences.
ACCESS MODEL
Identity → Role → Scope → Action.
The School App is designed so browser visibility alone is not the authority for protected actions.
IdentityWho is signed in?
→RoleWhat responsibility do they have?
→ScopeWhich school or centre?
→ActionOpen, create, edit, delete, approve or export?
MARKETING HYGIENE
Show the product without exposing the school.
The public website should never depend on production learner or customer records to prove product capability.
Public product visuals should use fictional names, schools, records and financial values.
Do not publish passwords, tokens, internal security configuration, private administration paths or developer-only controls.
Show workflows and outcomes instead of raw sensitive configuration screens.
Every new screenshot, video and customer story should receive a privacy and commercial-sensitivity review.
PRODUCTION DISCLOSURES
Publish only what has been verified.
Before launch, BL TECHNO should document the production facts behind each trust statement.
Contracting entity & registered addressPrivacy/contact channelHosting & data-location factsEncryption controlsBackup & recovery approachRetention policiesSubprocessor/service-provider listIncident response processCountry-specific transfer mechanismsCertification status, if any
TRUST THROUGH CLARITY
Security and privacy claims should be evidence-based.
BL TECHNO will continue strengthening the public trust centre as production controls are verified.