Book a demo

( Trust · Security )

Read-only by design

Riptally reads your company’s sales conversations. That only works if security is the first decision, not the last.

Last updated October 20, 2026PrivacyTermsSecurity

Security at a glance

Access

Connections use OAuth with the narrowest read-only scopes each provider offers. Tokens are encrypted with per-workspace keys and can be revoked from your admin console or from the provider at any time.

Inside Riptally, no employee can read customer messages by default. Support access is granted per ticket by your admin, logged, and expires after 24 hours.

Data handling

  • Encrypted in transit (TLS 1.3) and at rest (AES-256).
  • Raw text is kept for 90 days, then only derived signals remain.
  • Internal-only and personal threads are filtered out before storage.
  • Deletion on cancellation within 30 days, or sooner on request.

Infrastructure

Hosted on a major cloud provider in Frankfurt (EU) and Virginia (US), in isolated accounts per region. Production access requires hardware keys. Infrastructure is defined in code and reviewed before every change.

Programme

  • Annual SOC 2 Type II audit and external penetration test.
  • Background checks and security training for every employee.
  • Incident response plan with customer notice within 72 hours.
  • SAML SSO and SCIM on Enterprise.

Report a vulnerability

Write to security@riptally.example. We reply within one working day, won’t take legal action over good-faith research, and credit researchers who want it.