Skip to content
Gradexa
Security & deployment

Your borrowers' data stays yours.

Lending data is regulated data. The controls below are the ones a compliance team asks about in the first call, with the same honest status labels we use everywhere else on this site.

API infrastructure
Controls

What protects the data.

Read from the code of the engine and the Suite. Built means implemented and tested in our codebase; Roadmap means we intend to build it and have not.

  • 01

    Tenant-isolated data

    Every tenant-scoped table has row-level security enabled and forced in Postgres, and queries run as a non-superuser role. Isolation is enforced by the database, not by application code.

    Built
  • 02

    API-key-scoped access

    Keys belong to one tenant, are stored as hashes, and can be rotated or revoked. A request only ever sees that tenant's policies and decisions.

    Built
  • 03

    Role-based access in the Suite

    Five staff roles (admin, CRM agent, underwriter, collections agent, viewer) plus a separate borrower principal, with MFA and session controls for staff.

    Built
  • 04

    PII access logged, append-only

    Sensitive identifiers are masked by default. Every reveal of a full value is written to an immutable access log before the value is returned.

    Partial
  • 05

    Field-level encryption of identifiers

    Phone, PAN, Aadhaar and bank account numbers are encrypted at the application layer with AES-256-GCM, with a separate keyed index for lookups and key versioning for rotation.

    Built
  • 06

    Append-only decision log

    Decisions cannot be updated or deleted; a database trigger blocks both. Each carries the policy version it was made under.

    Built
  • 07

    Bureau-report view logging

    Logging each view of a bureau report by a named user, alongside the existing PII access log.

    Roadmap
  • 08

    Request signing

    HMAC signing of API requests in addition to the bearer key.

    Roadmap

Built = implemented and tested in our codebase.Partial = core logic built, not production-ready.On onboarding = adapter built, enabled with your vendor credentials.Roadmap = not built yet.Gradexa is in active development; no production lenders yet.

Deployment

Managed cloud, one tenant per lender.

The Credit Engine and the Suite run as multi-tenant services on managed infrastructure, with each lender isolated at the database row level. The Suite talks to the engine over HTTP with its own tenant key, exactly as an external client would.

What we commit to

  • 01Bureau data is used only to produce your decision. It is never pooled across tenants, resold, or used to build models for anyone else.
  • 02Your borrowers, policies and decisions stay yours. If you leave, they are returned or deleted on the terms in your agreement.
  • 03We say which controls are built and which are planned. Ask us for the evidence behind any line on this page.

Security questions: hello@gradexa.in

Next step

Bring your compliance team.

We'd rather answer the hard questions before a contract than after. Request a demo and put security first on the agenda.

Request a demo Read developer docs