Trust
An inventory of evidence. Four rows hold something. Five hold nothing, and they stay in the table.
What we can prove
| Claim | Evidence | Standing |
|---|---|---|
| Every page meets WCAG 2.1 level AA | axe-core on every page, at 1280 px and 320 px, on every build | Automated check |
| The site collects nothing | Content security policy in public/_headers; no analytics tag | Verifiable in the headers |
| At least 70% practical time per module | Passive and active minutes for each module, published on the curriculum page | Published, arithmetic checkable |
| Published prices are the real prices | The pricing page and the Product markup it emits carry the same amounts | Published |
| Independent security certification | None. No SOC 2, no ISO 27001, no equivalent | No evidence |
| Independent penetration test | No test has been run | No evidence |
| Independent accessibility audit | No auditor or assistive-technology user has assessed the site | No evidence |
| Client reference | No institution uses Crediteris | No evidence |
| Production hosting in Canada | Designed, not yet in client use | Design only |
A trust page that lists only strengths is a brochure. You find the gaps in the security questionnaire anyway, three weeks later.
What we will not publish
- No customer logos
- We have no customers. When we do, we publish nothing without their written approval.
- No testimonials or results
- Nobody has used the product, so any quote would be invented.
- No certification badge
- We hold none. A badge we do not hold is the easiest lie to tell and the easiest to check.
- No benchmark we cannot source
- We will not quote a competitor's price or completion rate we have not verified.
- No metric without its method
- Every figure on this site names where it comes from.
The boundary the product enforces
Crediteris teaches credit judgment and does not exercise it. Case tools accept case data only, and nothing asks for a client document.
That is a design constraint, not a policy. There is no configuration that turns it off.
Where things stand
| Item | Status | Notes |
|---|---|---|
| Curriculum specification | Complete | Version 1.0, September 23, 2026: 27 modules, cases, assessments and tools. |
| Module content | Not yet available | No module is available to learners yet. |
| Learning platform | In development | |
| Production hosting in Canada | Designed | Not yet in client use. |
| Security certifications and independent audits | None yet | Details on the security and compliance page. |
| Client deployments | None | No institution uses Crediteris yet. |
What to ask us for
During a procurement we send the architecture description, the curriculum specification and a written statement of the gaps above.
If a requirement is one we cannot meet today, the answer says so in writing rather than in a meeting.