Security at Reconixe

Private application areas require authentication. Organization membership and role checks restrict access to each organization's workflows, files, reconciliation results, exceptions, reports, support records, and settings.

Privileged operations are authorized on the server. Database row-level security and restricted service operations are used where appropriate, so browser visibility is not treated as authority.

Uploaded reconciliation files and derived operational data are handled through protected application paths. Reconixe records relevant organization, reconciliation, exception, usage, support, and billing events to support operational history and investigation.

Access to billing records is restricted. Subscription updates are synchronized through trusted server-side processing, with sandbox and live billing environments kept separate.

The Exception Explainer sends bounded exception evidence through a server-side AI request. It is assistive and read-only: it cannot change an exception, resolve it, add a review note, or grant access.

AI-generated explanations should always be checked against the underlying evidence.

Private service credentials are handled on the server rather than placed in browser-accessible configuration. Reconixe is delivered over HTTPS on its production hosting platform.

If you believe you have identified a security issue involving Reconixe, please contact us at support@reconixe.com and include enough detail for us to investigate.