Loading SchemeKnit
What SchemeKnit stores, why, and how deletion works.
Last updated: October 2026
This policy describes the data categories SchemeKnit actually stores, why they are kept, whether the user can delete them, and whether deletion is immediate.
Under section 24 of the Data Protection Act, 2012 (Act 843), personal data should not be retained longer than necessary for the purpose for which it was collected, subject to the statutory exceptions.
Section 27 of the Revenue Administration Act, 2016 (Act 915) requires necessary tax records — including relevant receipts, invoices, vouchers and contracts — to be retained for at least six years from the relevant date, or longer in specified unresolved matters. Section 8 of the Electronic Transactions Act, 2008 (Act 772) applies a six-year electronic-record rule where a law requires the relevant record to be retained. These rules apply to the records they cover; they are not a general justification for keeping every account, curriculum, security or operational record indefinitely.
This policy does not promise immediate destruction of every copy. Categories without a scheduled expiry are identified below as owner/engineering follow-up items; no automatic destructive cleanup is claimed or introduced here.
| Data | Why stored | User deletion | Retention |
|---|---|---|---|
| Account and profile | Sign-in, role and service delivery | Request account deletion | Until the request is processed; limited records may be retained |
| Uploaded schemes of work | Extraction and lesson generation | Yes — delete the scheme | Deleted with the scheme; the private stored original is removed when no other scheme references it |
| Generated lesson plans | Review, editing and export | Yes — delete the scheme/lesson where offered | Until deleted or account deletion is processed; no scheduled automatic purge |
| Export files (DOCX/PDF/XLSX/ZIP) | Download and regeneration | Request removal | No scheduled automatic 30-day purge is implemented. Download links expire after 10 minutes and are single-use; stored export files may remain until operational cleanup or a deletion request. Owner/engineering follow-up: define an approved cleanup period. |
| Payment and verification records | Payment verification, accounting and fraud prevention | Normally retained | Tax-relevant accounting records: at least six years from the relevant date under Act 915 section 27, or longer in specified unresolved matters. Other operational payment data should be minimised to its purpose. |
| Paystack webhook events | Idempotency, recovery and payment integrity | Normally retained | No scheduled expiry currently. Not automatically justified by tax or audit rules. Owner/engineering follow-up: define a retention period consistent with payment reconciliation and security needs. |
| Security, login and audit records | Security, abuse prevention and accountability | Normally retained | No scheduled expiry currently. Not automatically justified by tax rules. Owner/engineering follow-up: define a retention period proportionate to security and legal needs. |
| Password-reset tokens | One-time account recovery | Not applicable | Expire after 30 minutes and are single-use; the database row may remain as a used marker |
| MFA and recovery information | Privileged-account security | Disable MFA or request account deletion | Until disabled, regenerated or account deletion is processed |
| AI enrichment and generation caches | Reuse identical output and avoid repeated provider cost | Limited; removed with associated data/cleanup where implemented | No scheduled automatic expiry; the whole-lesson cache is not tied to a lesson row. Not automatically justified by tax or audit rules. Owner/engineering follow-up: define a cleanup period. |
| Database backups | Disaster recovery at the infrastructure provider | Indirect; request support | Controlled by the hosting/database provider. Deleted live data may persist in backups until the provider's backup cycle expires; immediate removal cannot be guaranteed |
To request account deletion or another privacy request, email [email protected]. We may need to verify your identity. We will delete or anonymise data that we are not required to keep. Payment, tax, fraud-prevention and security records may be retained for as long as a genuine legal or operational obligation applies.
Deleting an uploaded scheme removes its stored original when no other scheme references the same object. Generated exports are not guaranteed to be removed by that action; ask us to remove residual export files if needed.
When a school deactivates SchemeKnit, teachers normally keep access to their individually generated lesson plans for export according to the account status. School licence, membership and payment records are retained for legitimate financial and audit purposes.
The following currently have no automatic deletion schedule. They are recorded as owner/engineering follow-up items; this policy does not claim that their indefinite retention is already justified:
Any retention period or automated deletion mechanism for these categories must be separately justified, approved and tested before it is introduced. Tax-relevant accounting records are treated separately under Act 915 section 27.
BloomCore Technologies — [email protected]. See also our Privacy Policy and Cookie Policy.