Sign In Connect Now

Trust & Security

Our commitment to protecting your data

Privacy-First Message Routing

TetherChat is built on a stateless, privacy-first architecture. Message content is not stored — it is routed in real time through memory. We retain routing metadata (such as message IDs for threads, edits, and reactions) needed to deliver the service. This reduces compliance scope and your risk exposure.

SOC 2 Type II

Audit period underway

We have entered our SOC 2 Type II audit period. An independent auditor is evaluating the design and operating effectiveness of our controls across the Trust Services Criteria. Our security program and control environment are documented in our Trust Center; the formal SOC 2 Type II report will be published there when the audit is complete. View our SOC 2 Trust Center

Security

  • Authenticated and signed API requests
  • Platform signature verification for all incoming events
  • Google Cloud KMS encryption for tokens at rest
  • TLS 1.3 encryption for all data in transit
  • Structured audit logging without sensitive data

Availability

  • Retry logic with exponential backoff
  • Rate limit handling and throttling
  • Serverless infrastructure on Google Cloud Platform

Confidentiality

  • Zero message content storage (stateless architecture)
  • KMS-encrypted authentication tokens
  • No persistent user data beyond connection metadata
A Type II report reflects controls operating effectively over an observation period—typically several months—before the auditor issues a final opinion. Until that report is issued, we are in audit, not yet certified. For security questionnaires or vendor reviews during this period, contact security@tetherchat.io or request materials through the Trust Center.

GDPR Alignment

TetherChat is designed with privacy-by-design principles. Our architecture minimizes data collection by not storing message content and retaining only routing metadata needed for delivery.

Data Protection Principles

  • Data Minimization - No message content storage
  • Right to Erasure - Complete data deletion on request
  • Encryption - KMS-encrypted tokens, TLS in transit
  • Authorization - Workspace admin approval required for installation

How Your Data Flows

When you send a message through a Tether connection, here's what happens:

1

Receive & Queue

Message verified and placed in secure processing queue

Verified
Queued Temporarily
↓
2

Route & Convert

Message format converted for destination platform

Processed
Not Persisted
↓
3

Deliver & Delete

Message sent to destination, then removed from queue

Delivered
Deleted

Transparency Note: Messages briefly pass through Google Cloud Pub/Sub (a managed message queue) for reliable delivery. Once delivered, they're immediately deleted. We never store message content in any database-only connection metadata (which channels are linked) is persisted.

Infrastructure Security

Google Cloud Platform

Enterprise-grade infrastructure with 99.95% SLA uptime

Cloud KMS

Hardware-backed key management for token encryption

TLS 1.3

Latest encryption standards for all data in transit

Serverless

Auto-scaling infrastructure with no persistent attack surface

Security Questions?

We're committed to transparency. If you have questions about our security practices or need additional documentation for your compliance requirements, please reach out.

Contact Security Team

Need to raise an ethics, fraud, or policy concern? Use our confidential reporting channel.

Last updated: May 2026