Skip to content
Balipse
Security

Financial intelligence requires trust.

Balipse handles sensitive financial relationship data. Security is a foundational requirement of the platform, not an afterthought.

01Encryption

Data is encrypted in transit using TLS, and encrypted at rest within our storage infrastructure.

02Authentication

Access to the platform requires authenticated sessions, with support for strong credential practices.

03Access controls

Access to underlying data is limited to what is necessary to operate and support the platform.

04Role-based permissions

Organizations can scope what team members are able to view and act on within their network.

05Data isolation

Customer data is logically separated to prevent cross-organization access.

06Audit logs

Key actions within the platform are logged to support traceability and internal review.

07Secure integrations

Connections to banks, processors, and other financial systems are handled through secure, credentialed channels.

08Data retention

Data is retained only as long as necessary to provide the platform, consistent with our Privacy Policy.

09AI data boundaries

Data used for AI-assisted analysis is scoped to the organization it belongs to and is not used to train models shared across customers.

A note on certifications

Balipse does not currently hold formal compliance certifications such as SOC 2, ISO 27001, PCI DSS, or GDPR-specific attestations. Pursuing relevant certifications is part of our roadmap as the platform matures. We will update this page as our compliance posture evolves.