Nexier School Rights Retention and Incident Procedure

1. Intake and authentication

Receive rights, privacy and service complaints at the monitored route identified for nexierschool.com and at the Legal Notice correspondence address. Acknowledge and assign a case reference. Route professional complaints to the actual provider while retaining responsibility for platform matters. Verify identity and representative/guardian capacity proportionately and avoid excessive document collection.

2. Assessment and deadlines

Identify the exact controller, request type and data scope. For applicable GDPR requests, respond ordinarily within one month; where a lawful extension is needed notify the reason and extension within the first month. Explain refusal/limits and complaint rights. A data processor assists its controller promptly rather than giving an unauthorized independent response. Keep a limited request/decision proof without duplicating all sensitive content.

3. Retention and legal holds

Maintain a schedule by data class, purpose, legal basis, actual period/trigger, owner, deletion/export job and backup expiry. Retain active service data only as necessary; separately restrict invoice, professional record or claim material subject to specific mandatory duties. A legal hold needs owner, ground, scope, review and expiry. No blanket forever ledger retention overrides erasure or storage limitation. Use a new minimized correction/revocation event instead of editing protected proof, and design lawful separation of personal payload from integrity evidence.

4. Security incidents

Staff report suspected incidents immediately to the assigned incident lead. Contain and preserve necessary evidence, assess affected tenants, access, confidentiality/integrity/availability and risks, and involve the competent controller. Notify processors/controllers without undue delay as required. A controller assesses supervisory notification within 72 hours after awareness where the GDPR threshold applies, and affected persons without undue delay for the relevant high risk unless a lawful exception applies. Keep reasons for reporting or not reporting; no invented fixed private notification deadline is represented as statutory law.

5. Review and appeal

Give a reasoned resolution, remedy/escalation route and applicable independent authority/court route. Preserve fair review for supplier restrictions and illegal-content decisions where required. Staff cannot unilaterally finalize high-stakes clinical, legal or statutory decisions. Logs and case files are tenant scoped and access is audited; routine denied requests do not flood M10, while proof/approval/exception and SEV-class events follow the established rail policy.

Platform-specific terms

Retention and deletion (ceiling wording)

1. Account data is kept for the life of the account and deleted or anonymised within 90 days after closure, except where a longer period is required by law (tax and accounting records: 6 years; acceptance and consent records: 5 years after the end of the relationship, as evidence of compliance; records subject to a legal hold: until the hold ends).

2. Conversation logs, recordings and uploads not linked to an active contract are deleted no later than «retention.conversations» (default: 12 months) after the last interaction, and earlier on your request, unless a legal hold applies.

3. Backups are rotated on a cycle not exceeding 35 days; data deleted from production is removed from backups at the end of the cycle.

4. Where a provider is an independent controller, its own retention rules apply to its records.

Implementation note: the renderer prints the registry value; the retention job must run at or before the printed ceiling (LGL-T aligned job), which is why the clause uses “no later than”.

---