checkb.tech
Sign in
Legal

Privacy Policy

Who we are & Scope

checkb.tech is a dedicated coursework verification and management workspace built for Pearson BTEC International centres, assessors, and Internal Verifiers (IVs). Single point of contact for technical support, partnerships, and data protection: Contact: support@checkb.tech

GDPR Role & Lawful Basis

Under the General Data Protection Regulation (GDPR) and UK Data Protection Act 2018: • Your Educational Institution / Centre is the Data Controller. • checkb.tech acts as a Data Processor, operating upon your documented instructions to check submitted evidence against BTEC criteria and track coursework. Lawful Basis: Processing is conducted under Article 6(1)(b) (performance of a contract/service delivery) and Article 6(1)(f) (legitimate interest in facilitating educational verification and Standards Verification compliance).

What data we collect & process

1. Centre & Assessor Account Data: • Institutional work email address • School / Centre name and country • Departmental role (e.g. Lead Internal Verifier, Quality Nominee, Assessor) 2. Coursework Submissions: • Text content of submitted student assignments for automated criteria verification. • Learner reference codes (initials or student candidate numbers). We strongly recommend centres use student candidate numbers or initials. We do not require or seek student personal identities, home addresses, contact details, or special category data.

Storage, retention & deletion

• Submitted files are stored in cloud object storage and submission records, extracted text, and verification results are stored in the application database to support review and re-checking. • The current application does not publish a retention period for completed submissions. A one-day storage lifecycle rule applies to abandoned upload chunks only; it does not establish a deletion schedule for completed student files. • Removing a file or student in the application removes associated database records, but the current deletion flow does not confirm removal of the stored file object. Contact support@checkb.tech before relying on deletion of a stored file or requesting account closure.

Third-party infrastructure & functional categories

To protect technical integrity while ensuring full compliance, checkb.tech utilizes enterprise-grade sub-processors categorized functionally: • Cloud Object Storage — Stores submitted assignment files. The current application does not configure a scheduled expiration for completed submissions. • AI Model Inference Infrastructure — Processes extracted text against Pearson specification grids. Extracted text and verification results are also stored in the application database for re-checking. • Relational Database — Hosted in the European Union (EU) for centre configuration, submission records, extracted text, and verification results. • Identity & Authentication Infrastructure — Secure token-based session authentication for educators. • Application Delivery & Hosting — Enterprise CDN and edge delivery. • Payment Processing — PCI-DSS Level 1 compliant merchant of record. Payment details are held directly by the processor; checkb.tech never stores payment cards. We do not sell personal data, nor do we deploy advertising trackers or social media tracking pixels.

Your rights under GDPR

Under GDPR, school personnel and learners have the right to access, rectify, restrict, or request erasure of their personal data. Because the Centre is the Data Controller, student data requests should be initiated through the school. checkb.tech assists centres in fulfilling any such requests within 5 business days. For any data protection inquiries, email: support@checkb.tech.

Cookies & Analytics

checkb.tech uses strictly necessary session cookies required for authentication and security, alongside privacy-preserving product telemetry to measure feature performance. We do not use third-party advertising or marketing trackers.

Changes to this policy

If we make material changes to this policy, registered centres will be notified by email at least 14 days prior to implementation. Last updated: September 2026