Trust and student data
Built so your customers' security review has easy answers.
EdTech buyers ask about student data before they ask about features. These are the design facts behind every module we build, written so your team can repeat them to districts and institutions.
The short version
- Synthetic data in the Sprint.
- Production student data stays in your cloud.
- No production credentials for Datics.
- No training on your data.
- A person approves anything material.
- Everything is logged.
Student data
We build without touching production student data.
The safest data is data we never hold. The Sprint and the first production release are designed so we do not need it.
How data is handled
- Sprint work runs on synthetic or de-identified data, never on production student records.
- Production student data stays in your cloud, under your access controls. It does not move to Datics systems.
- We hold no production credentials, database access or raw logs. Code reaches your product as pull requests through your CI/CD.
- If a later phase genuinely needs data access, it happens under your agreements and your counsel decides how they apply.
AI controls in every module
- No training on your data or your customers' data.
- Approved model endpoints only, listed with region and retention. Your choice of model and hosting.
- An approval step before anything material is written, sent or changed.
- An audit log of what the AI saw, drafted and did, and who approved it.
- Answers that cite their source, and a clean handoff to a person when the AI does not know.
Evaluation
Quality, safety and cost are measured before launch.
Every Sprint ends with evidence, not a demo alone.
What the Sprint Pack tests
- Quality evals on a test set your team reviews, so quality is a number before launch.
- Safety tests for cross-tenant access, prompt injection, personal-data leakage and refusals.
- A cost-to-serve estimate on two models, so the feature's margin is known before it ships.
- Institution isolation: one customer's data never reaches another's answers.
Accessibility
- New screens are designed and tested against WCAG 2.1 AA: keyboard use, contrast, labels and captions.
- We can review existing flows ahead of ADA Title II deadlines and fix what we find, as an engineering review, not a certification.
Security reviews
Answers ready for HECVAT, district questionnaires and DPAs.
We help you answer the parts of your customers' reviews that cover the features we build.
What you get
- A security overview and a data-flow sheet for each module, ready for your customers' reviews.
- Help answering the AI and data sections of HECVAT and district questionnaires for the features we build.
- Architecture and data-flow documentation for production releases, including the models used and a way to switch the feature off.
Who you are working with
- Datics AI is headquartered in Austin, Texas, where our CEO is based. Product Review calls run in US Central time.
- Engineering runs from our center in Lahore, Pakistan, with a named lead engineer and US-hours overlap on every engagement.
We build around your FERPA, COPPA, accessibility, security and institutional requirements. Compliance depends on the complete product, contracts, policies and operating environment; Datics does not present software engineering alone as legal certification.
See one module on your own product.
Bring one product, workflow or AI initiative. In 30 minutes we pick the module that fits first, what it would cost to serve and what your customers' security review will ask.
Calls run in US Central time. No generic AI presentation: we discuss your product, users and production constraints.