Security & data handling
Documented controls, limited claims and clear responsibilities.
This public summary describes controls implemented in the current NEXT architecture. It is not an independent audit, penetration test, certification or guarantee that incidents cannot occur.
Current technical controls
Authenticated access
Organization and learner workspaces require authenticated accounts.
Organization separation
NEXT records use organization identifiers and database row-level security policies to restrict access by organization and role.
Defined staff roles
Owner, administrator, manager, case-manager, facilitator and viewer roles support different operational permissions.
Restricted privileged functions
Sensitive database helpers are kept outside the exposed public schema where practicable, with execution grants limited to authenticated roles.
Transport and managed infrastructure
The application uses HTTPS through managed hosting and relies on managed database, authentication and storage infrastructure.
Data minimization
NEXT is designed for learning delivery and reporting—not detailed legal, clinical, correctional or case-management files.
Data flow in plain language
- Authorized staff or learners submit information through the BriteLink application.
- Managed infrastructure providers deliver the web application, authenticated access, database and selected storage functions.
- Selected AI features may send the minimum required prompt or learning text to an approved AI service provider. Partners can scope whether AI-assisted functions are enabled for a pilot.
- Program reports are generated from recorded assignments, activity, assessments and progress—not from hidden case-management data.
Incident response
BriteLink’s response process is to contain the issue, preserve relevant evidence, assess affected systems and information, correct the weakness, document decisions and notify affected organizations or individuals when required by law or contract. Suspected vulnerabilities should be reported to hello@britelink.org with the subject “Security”. Do not include live credentials or participant records in the initial email.
Deletion and offboarding
Before a pilot begins, the implementation agreement should identify the organization’s retention period, export requirements and deletion timetable. On authorized offboarding, active records will be removed or de-identified according to that agreement, subject to legal obligations and managed-provider backup cycles.
Current assurance status
BriteLink does not currently claim SOC 2, ISO 27001, independent penetration testing or third-party security certification. Before handling higher-risk or large-scale participant data, BriteLink should complete independent security testing and provide the resulting scope and remediation status to the partner.