ANABHIX TRUST CENTER
Trust begins with clear boundaries, evidence, and accountable operation.
This public trust center connects reviewed security, privacy, access, delivery, and support information without inventing certifications or guarantees.
Identity and access
Sign-in is handled by a dedicated Keycloak identity provider rather than by passwords stored in the application. The web client uses the OpenID Connect authorization-code flow with PKCE (S256), so no long-lived credential is held in the browser, and access tokens are refreshed against the identity provider instead of being extended locally.
Password rules are enforced centrally at the identity provider: a minimum of twelve characters with upper case, lower case, digit, and special-character requirements. Repeated failed sign-ins trigger automatic temporary lockout after five failures, and self-service registration is disabled so accounts are created only by an authorized administrator. Time-based one-time-password (TOTP) second-factor authentication is supported; it is not currently mandatory for all users.
Authorization is evaluated in the responsible service. Permission checks are declared per endpoint against a central permission catalogue, so a visible control in the interface does not itself grant authority. Every request to a protected service carries a signed token, and roles and institution context travel as claims inside that token, so a service authorizes against a signature it can verify rather than a header a client could set.
Tenant isolation
A tenant identifies the institution that owns a record. Tenant context is carried as a signed claim on the authenticated token and resolved by the responsible service before institution data is returned or modified. Identity alone does not grant access to an institution: a valid sign-in still has to resolve to an authorized tenant and role for the requested scope.
Isolation is enforced twice, on the assumption that one layer can be wrong. A shared request filter compares the tenant claim inside the verified token against the tenant supplied in the request and rejects the call outright when they disagree, so a valid token for one institution cannot be pointed at another by editing a header or query parameter. Cross-institution access is limited to explicitly assigned platform and organization administrator roles.
Beneath that, institution data is separated in the database itself. Tenant-scoped tables carry row-level security policies that are forced for the table owner as well, and the application connects through a database role that cannot bypass them. The policies are fail-closed: with no tenant context set, a query returns no rows rather than returning everything, and a write that does not match the active tenant is rejected.
Data protection
Public traffic is served over HTTPS only. TLS certificates are issued by public certificate authorities and renewed automatically, and the site sends HTTP Strict-Transport-Security with a one-year max-age, includeSubDomains, and preload, so a compliant browser refuses to fall back to plain HTTP.
Payment card details are never entered into or stored by Anabhix systems. Card, UPI, and net-banking details are collected inside the payment provider’s hosted checkout; Anabhix receives only an order reference, a payment identifier, and a signature that the server verifies before a subscription is activated.
Application security
The public site sets a Content-Security-Policy with an explicit source allowlist, object-src none, base-uri self, form-action restricted to the Anabhix identity provider, and frame-ancestors self. It also sends X-Content-Type-Options nosniff, X-Frame-Options SAMEORIGIN, Referrer-Policy strict-origin-when-cross-origin, and Cross-Origin-Opener-Policy.
A Permissions-Policy header disables geolocation, serial, USB, HID, Bluetooth, and related device APIs. Camera, microphone, and screen capture are at most allowed for Anabhix’s own origin, because live classes and meetings need them, and are never delegated to third-party frames; the browser still asks before any access.
Server-side amounts are authoritative for billing: the checkout amount is computed from the subscription plan on the server and never taken from the client.
Infrastructure security
Workloads run on Kubernetes with per-application network policies in the production namespace, so a service reaches only the dependencies it is explicitly permitted to reach. A default-deny baseline is being rolled out progressively across environments and is not yet the default in every namespace.
Application and infrastructure state is declared in version-controlled manifests and reconciled by GitOps, so a production change is a reviewable commit rather than an ad-hoc edit to a running system. Admission policies are enforced in the cluster; runtime threat monitoring is not yet deployed in the production cluster.
Application secrets are held in HashiCorp Vault and delivered to workloads by the External Secrets Operator rather than being committed to source control. Production runs on Oracle Cloud Infrastructure in India, where block volumes and object storage are encrypted at rest by default with Oracle-managed keys. Additional field-level encryption is applied to selected sensitive fields in some services, not yet in all of them.
Monitoring and logging
The platform runs Prometheus for metrics, Alertmanager for alert routing, and Grafana for dashboards, with alerting rules defined for application, database, billing, and platform conditions. Centralized log aggregation and distributed tracing are not yet running in the production cluster. Services expose health and readiness endpoints that the orchestrator uses to withdraw traffic from an unhealthy instance.
Security-relevant events in the identity and account services are written to an append-only audit log. Each entry is chained to the previous one with a SHA-256 hash, so a later edit, deletion, or reordering of audit rows breaks the chain and is detectable on verification, including where it was made directly against the database rather than through the application. Audit history recorded before this chaining was introduced is not covered by it.
Secure development
Changes reach the default branch through an automated pipeline. It runs type checking, linting, dependency audit, content and claim validation, an accessibility check, a link and SEO check, a bundle-size budget, and the unit test suite before an image is built. Branch protection is in force on the default branch; Anabhix does not claim a mandatory two-person review on every change.
Shared pipeline templates add blocking security gates: secret scanning, static application security testing, and a container-image vulnerability scan at high and critical severity. These fail the pipeline rather than reporting advisory findings, so an image with an unresolved high or critical fixable vulnerability does not reach a release. Repository-wide dependency scanning is enabled per repository rather than fleet-wide, and is not yet on everywhere.
The shared security and deployment templates are pinned to a reviewed infrastructure commit, so release behaviour does not change underneath an application commit.
This trust page is itself under an automated honesty gate: a build fails if an availability percentage, a certification name, or a guarantee is introduced anywhere in the published site content.
Backup and recovery
Production databases are backed up every hour, keeping the latest twenty-four hourly copies, and every day, keeping the latest seven daily copies, in versioned object storage in India that removes copies after thirty-five days. Cluster-level backups run daily, kept for thirty days, and every six hours, kept for seven days. Backup storage is replicated from Hyderabad to a disaster-recovery region in Mumbai.
Restore capability is exercised, not assumed: a scheduled restore drill restores from backup on a weekly cycle. Recovery-time and recovery-point objectives are agreed per contract and are not asserted here as a general figure.
Incident management
Alerts are routed to the engineering team through Alertmanager against defined rules, and deployments are reversible: releases are version-pinned in Git and can be rolled back to the previously serving revision. Anabhix does not currently publish a formal on-call rotation or a named incident-response runbook.
To report a suspected vulnerability or a security concern, contact Anabhix through the published contact route and mark the message as a security report. Please do not include credentials, tokens, or student records in a first report. Anabhix does not currently operate a paid bug-bounty programme, and contractual breach-notification timelines are set in the agreement rather than promised here.
Privacy
On the public website, analytics, marketing, personalization, and functional cookies all default to off. Analytics and tag providers stay unloaded until a visitor explicitly opts in, and that choice can be changed or withdrawn from the cookies page. Only strictly necessary storage operates without consent.
Anabhix processes institution data as a processor on behalf of the school, which remains the controller of its student, staff, and family records. Public forms ask only for business contact and operating context, and account-specific matters are handled through authenticated channels rather than public forms.
India’s Digital Personal Data Protection Act, 2023 is the framework Anabhix is aligning to for Indian school customers, including the treatment of children’s data. To be plain about the current state: a consent-record capability exists in the platform, but Anabhix has not completed a published DPDP readiness assessment, does not yet offer self-service data erasure (deletion is handled on request, as described on the Delete account page), and publishes only a summary of retention periods in the Privacy Policy rather than a full retention schedule. A data-processing agreement, retention schedule, and records of processing are agreed per contract. Ask for the current position in writing before relying on it.
Production is hosted on Oracle Cloud Infrastructure in India (Hyderabad), with disaster-recovery copies in Mumbai. Payments in India are processed by Razorpay, SMS by MSG91, email is sent through Oracle Cloud Infrastructure, the sites are served through Cloudflare, and business mailboxes are hosted by Zoho. The providers in use are named in the Privacy Policy.
Certifications and contractual commitments
Anabhix holds no third-party security certification. There is no SOC 2 report, no ISO 27001 certificate, no PCI-DSS attestation of our own, and no published independent penetration test. Where this page describes a control, it describes something implemented in the platform, not something an external auditor has attested.
Two controls are deliberately described here as in progress rather than in force, because claiming them would overstate the platform. A centralized policy engine is deployed and evaluating gateway authorization decisions in observation mode, where denials are recorded but not applied; per-endpoint checks in each service are the enforcing layer today. A service-mesh policy for mutual TLS between internal services is configured but not yet active in production. Both are being completed, and neither should be read as a control you are buying today.
No uptime figure or availability service level is published. The Terms of Service state that Anabhix does not guarantee uninterrupted access, and no marketing number on this site may contradict that.
A data-processing agreement, data-residency commitments, encryption-at-rest specifics, defined retention periods, and recovery objectives are provided under an authorized review or in the contract, because they depend on the deployment being purchased. The hosting region and the providers in use are published in the Privacy Policy. If a commitment matters to your procurement, obtain it in writing rather than inferring it from this page.
Scope and limitations
- Anabhix is not SOC 2, ISO 27001, or PCI-DSS certified, and no independent penetration-test report is published. Any statement to the contrary did not come from Anabhix.
- No uptime percentage, availability service level, recovery-time objective, or retention period is claimed on this page. Those are contractual and are confirmed in writing.
- Hosting region and data-residency commitments are confirmed per deployment and are not asserted here.
- Controls described here are those implemented in the platform. Customer-specific evidence, architecture detail, and incident procedures are shared only through an authorized security review.