Security and procurement notes

Trust needs more than a good generated worksheet.

Institutional buyers need to understand privacy, data handling, review controls, accessibility expectations, and procurement workflow before approving classroom use. This page summarizes the current review path and links to formal policies.

Request security review Read privacy policy Submit pilot feedback

Current controls

What ClioMake can document for pilots.

Account and access

Authenticated accounts, role-aware dashboard access, secure sessions, and product-scoped credits for ClioMake generation.

Uploaded material handling

Uploaded source materials and prompts are used to provide requested product functionality and are governed by the ClioMake privacy policy and terms.

Generated output ownership

Terms explain user rights in generated worksheets, slides, textbooks, and other outputs. Buyers should review policies before resale or publication workflows.

Human review boundary

Generated educational resources should be checked by a responsible educator before classroom, parent-facing, or commercial use.

Accessibility review

Accessible HTML modules and structured files can be included in pilots. Formal conformance documentation can be scoped for institutional procurement.

Quality evidence

Sample packs can include quality reports, file-family validation, and teacher review checklists to support buying decisions.

Remake policy

If a paid proof pack is missing a promised file type, cannot be downloaded, or has a clear layout failure, the buyer can request one remake or account-credit review within 7 days.

Customer evidence slots

Approved testimonials, pilot summaries, and case-study results can be added only after a real customer gives permission. ClioMake does not publish fabricated adoption claims.

Procurement packet

Documents to request during review.

DPA review

Data-processing agreement review for institutions that require contractual student-data or uploaded-material terms.

Data retention and deletion

Retention, deletion, account closure, and generated-file handling summary for your legal or IT review.

Subprocessor summary

Current infrastructure and service-provider summary can be prepared for a qualified institutional review.

Invoice and PO support

For center pilots, institution sprints, and annual plans that require quote, invoice, or purchase-order workflows.

Privacy review Account data, uploaded-source handling, deletion, retention, and permitted-use summary can be prepared for a buyer review packet. Available

Student-data constraints Institution pilots can define whether student-identifiable data is prohibited, minimized, or contractually governed before generation begins. Scopable

Accessibility evidence Accessible HTML samples, keyboard-friendly modules, alt-text expectations, and educator review checklists can be included with pilot artifacts. Available

External attestations If procurement requires a third-party audit report or formal conformance statement, request that requirement early so it can be scoped honestly. By review

Output remediation Paid packs that are missing promised files, fail to download, or have a clear layout failure can be reviewed for regeneration or account credit. 7 days

Need a formal review?

Use the review request path and include your school, center, jurisdiction, expected users, student-data constraints, and procurement deadline.

Request review See school pilots