TB

Last updated: March 2026

Security

Security is foundational to TrancheBook. We handle sensitive financial data and AI-generated analysis, and we take our responsibility to protect that data seriously. This page describes our security practices, threat mitigations, and incident response procedures.

1. Communication Channels

Legitimate communications from TrancheBook will only come through verified channels:

  • Emails from @tranchebook.com domain only.
  • In-app notifications within the authenticated Platform interface.
  • Our verified social media accounts.

We will never contact you via personal email addresses, third-party messaging apps, or social media direct messages to request sensitive information. If you receive a suspicious communication claiming to be from TrancheBook, report it to security@tranchebook.com.

2. Anti-Fraud Warnings

Be aware of the following common threats:

3. AI-Specific Security

AI systems introduce unique security considerations. We implement the following protections:

3.1 Prompt Injection Prevention

Prompt injection attacks attempt to manipulate AI systems by embedding malicious instructions in data inputs. We defend against this through:

3.2 Output Validation

AI-generated outputs undergo validation before being presented to users:

3.3 Model Supply Chain

We maintain security over our AI model supply chain by using only enterprise-grade API access from Anthropic, verifying model versions and capabilities before deployment, and monitoring for unexpected changes in model behaviour. We do not use open-source models from unverified sources.

4. Portfolio Data Security

Portfolio data receives the highest level of security protection:

  • Encryption at rest: AES-256 encryption for all stored portfolio data. Encryption keys are managed through a dedicated key management system with automatic key rotation.
  • Encryption in transit: TLS 1.3 for all data transmission. HSTS enforced with a minimum 12-month max-age.
  • Per-user isolation: Portfolio data is logically isolated per user at the database level. Row-level security policies prevent cross-user data access even in the event of application-level vulnerabilities.
  • Access controls: Automated systems access portfolio data only during active analysis. Human access requires documented justification, management approval, and is logged for audit purposes.
  • Deletion: Users can request hard deletion of portfolio data at any time. Deletion is cryptographically verified and includes removal from backups within the backup rotation window.

5. Infrastructure Security

Our infrastructure is designed with defence in depth:

6. Incident Response

We maintain a documented incident response plan with the following commitments:

  • Detection: Automated monitoring systems are designed to detect security incidents within minutes. We operate 24/7 alerting for critical security events.
  • Response: Confirmed incidents trigger our response plan with defined escalation paths and responsibility assignments.
  • Notification: Affected users will be notified within 72 hours of a confirmed data breach, consistent with GDPR requirements. Where regulatory notification is required, we will comply within applicable timeframes.
  • Remediation: Root cause analysis is conducted for all security incidents, and findings are incorporated into our security controls.
  • Transparency: Material security incidents will be disclosed publicly with sufficient detail to inform affected parties while not aiding further attacks.

7. Responsible Disclosure

If you discover a security vulnerability in the TrancheBook platform, we encourage responsible disclosure. Please report vulnerabilities to security@tranchebook.com. We commit to:

Contact

For security concerns or to report a vulnerability, contact security@tranchebook.com.