Indelo Trust Center
Indelo is built for schools and school groups that need confidence in licensing, EV-signed software distribution, data ownership, synchronization, academic records integrity, and long-term institutional continuity.
Trust posture
The Trust Center documents how Indelo.app supports EV Authenticode-signed software releases, admin-governed licensing, offline-first operation, synchronization trust, responsible disclosure, and institution-owned data movement.
It is written for proprietors, school boards, registrars, bursars, ICT administrators, and implementation teams who need evidence, not slogans.
Core trust domains
These trust domains are the public expression of Indelo’s deeper platform architecture and implementation discipline.
Indelo installers are EV Authenticode-signed and distributed through CABS-controlled licensing and release channels.
Windows shows a verified publisher on signed installers. Public visitors cannot generate licences or freely access binaries; releases remain governed through administrator-controlled entitlement and institution portal access.
A signed enterprise license package is the primary authorization model. Online activation enhances connected deployments but is not a startup dependency.
Core institutional operation remains available when connectivity is weak or unavailable. Activation, heartbeat, update eligibility, and support visibility are connected enhancements — not the foundation of trust.
Indelo is engineered around customer-controlled data movement and institution-owned operational records.
The synchronization model avoids a readable third-party relay as a requirement. File-first packages, local networks, VPNs, and approved institution channels remain central.
Teacher spokes, campus hubs, and HQ consolidation use chained, signed, version-aware packages with scoped authority and auditability.
Synchronization packages detect and refuse silent modification, replay, gaps, out-of-order imports, and version drift. Sync cannot bypass the same business-rule validation used by local entry.
Academic records are long-duration institutional trust assets, not ordinary editable data.
Locks, approvals, audit trails, signed records, and verification workflows preserve the credibility of results and report records across staff changes, disputes, and campus expansion.
Security issues should be reported responsibly so CABS can protect institutions, releases, portals, and public infrastructure.
The Trust Center links security, support, disclosure, documentation, and portal-only implementation guidance in one place.
Tamper-evidence proves records were not altered after entry; it does not prove the original entry matched reality.
That remaining risk is procedural. Indelo controls it through approvals, role accountability, audit review, reversals, reconciliation, and institutional verification workflows.
Public trust documents
These documents are managed by CABS and may expand as Indelo moves through pilot deployment, enterprise rollout, and institution-specific implementation work.
Indelo installers are EV Authenticode-signed and distributed through CABS-governed licensing, release management, and protected download paths.
A signed enterprise license package remains the primary authorization path for Indelo core operation.
Indelo is engineered around institution-owned records, customer-controlled movement, and operational accountability.
Teacher spokes, campus hubs, and HQ consolidation use chained, signed, version-aware packages, scoped authority, and auditability.
Indelo treats academic records as long-duration institutional trust assets.
CABS encourages responsible reporting of security issues affecting Indelo public, portal, release, or licensing infrastructure.
Tamper-evidence proves records were not altered after entry; it does not prove the original entry matched reality.
Controlled distribution
Indelo.app can publicly explain its trust posture while keeping sensitive functions protected: license generation, release binaries, activation records, institution downloads, portal documentation, and admin operations remain access-controlled.
Indelo installers are EV Authenticode-signed; Windows shows a verified publisher on every installer distributed through CABS-controlled release paths.
Frequently asked questions
The Trust Center is the public confidence layer for Indelo.app, bringing together software trust, data ownership, offline-first licensing, synchronization integrity, security, disclosure, and enterprise governance statements.
No. Indelo uses signed enterprise license packages as the primary offline authorization path. Online activation and heartbeat features are optional connected enhancements for support, update eligibility, and deployment visibility.
The institution owns its data. Indelo synchronization is engineered for customer-controlled data movement through file-first packages, local networks, VPNs, or other institution-approved transport.
No. Licenses and binaries are controlled through admin-governed licensing, release distribution, and institution portal permissions.
Tamper-evidence proves records were not altered after entry. It cannot prove the original entry matched reality; that remaining risk is controlled through approvals, role accountability, audit review, reconciliation, and verification workflows.
Enterprise trust discussion
Request a conversation about licensing, implementation, synchronization, data ownership, records integrity, and institutional deployment readiness.