Open ICAP.

PRIVACY BY PURPOSE

School records stay under school control.

Open ICAP supports school-administered career and academic planning. School administrators manage records; students and families do not create accounts here. The public demo contains fictional records, stored only in browser memory.

What the application records

Student name and school identifier; school, grade and staff owner; postsecondary goals and annual planning; evidence references, dates and reviews; uploaded evidence files and their student, requirement, year, uploader, date and file metadata; support and work-based learning records; privacy-request and disclosure records. Avoid Social Security numbers, tax documents, financial-aid credentials, clinical information, full IEPs and information unrelated to planning.

Who can access school records

Authenticated administrators with active district membership. District administrators are scoped to their district; school administrators to their school. The school determines legitimate educational interest and any lawful disclosure basis. Operator access uses a separately configured, revocable key until school identity is connected; there is no built-in password.

Uses and service providers

Records serve the school's planning and documentation purposes. The application contains no advertising, analytics SDKs or AI-training integration. Managed deployments use Cloudflare Workers and D1. If hosting checkout is configured, Stripe processes district billing and licensed-student quantities; student records are not sent to Stripe.

Uploaded evidence documents

PDFs and supported images are stored privately in the district's Cloudflare D1 database with their student, optional requirement, academic year, uploader and upload date. Every upload, list, preview and download checks the signed-in administrator's district and school scope on the server. District-scoped database keys and relationships keep evidence separate even when districts use the same student identifiers. No public sharing links are created. Existing files remain available for authorized retrieval after subscription expiry, and approved student deletion includes evidence files while respecting retention holds.

PDF and HEIC previews are prepared inside the browser using self-hosted decoders. Files, filenames and natural-language assignment instructions are never sent to external AI services. Assignment uses the scoped roster and requirement names inside ICAP, with staff selection when a match is ambiguous. Uploading evidence does not mark a milestone complete. Downloaded copies must be handled through the school's approved secure process.

District AI controls

No AI is the default. It removes AI assistance and blocks inference while preserving manual planning, authored guidance, template drafts, reviews and exports. District administrators can change this policy in the account control panel; changes are recorded in the activity history.

Full AI power requires explicit district authorization. ICAP scans search queries locally and sends OpenAI only app-defined topics, authored guidance and aggregate counts for search explanations and optional planning questions. Original questions, student names, IDs, school details, individual records, written answers and staff notes never go to the external provider. Student-specific facts are retrieved and displayed within ICAP. The provider receives the server connection's network metadata. The application requests no provider storage of completions; provider retention and processing terms still apply.

Safe AI uses a small open-source model in a private Cloudflare container with internet access disabled and no external-provider fallback. Cloudflare remains the infrastructure processor. Search sends your question and bounded matching records from your authorized school or district scope to that private service. Planning-question suggestions send only a static feature type. Search questions and answers are not persisted by the app. If an AI service is unavailable or unconfigured, local search, authored guidance, manual entry and template helpers remain available.

AI prompts are advisory. They cannot change records, determine evidence status or make student decisions. Staff must review any generated text. Switching modes blocks new requests and discards results produced under the prior policy; it cannot recall a request already sent.

Access, correction and student summaries

Contact the school's records or privacy administrator to request inspection or correction. Schools must verify identity and the appropriate rights-holder. FERPA generally requires access within a reasonable time, no more than 45 days. Rights can transfer to an eligible student. A planning summary excludes staff evidence notes; this does not remove any underlying rights to inspect education records.

Retention, security and transfers

The school sets retention and holds; pending inspection requests must be protected from destruction. Database and backup disposal, recovery windows, vendor agreements and incident response must be configured for the actual deployment. Document exports are prepared by authorized staff, who must use approved secure delivery. A transfer index is not the evidence itself.

Deployment-specific notices

Before collecting real records, the hosting operator must publish its legal identity, privacy contact, contract and subprocessor terms, applicable retention schedule, incident contact and complaint procedures. This page describes the application's data design. It is not a signed school agreement or a claim of legal certification.

Read the legal and state-source research · Deployment and operating guide