1. Overview & Scope

This Privacy Policy explains how Sentry Relay ("we", "us") handles information when you visit sentryrelay.com or use our API, MCP server, SDK, CLI, developer console, and inbound addresses at in.sentryrelay.com (the "Service"). It applies to account holders and visitors, and describes how we handle messages that our customers receive through the Service.

Role. For account, billing, and usage data, we act as the controller (or "business"). For message and secret content that customers route through the Service ("Customer Data"), we act as a processor (or "service provider") on the customer’s behalf.

2. Information We Collect

Account information: name, email address, profile photo, and authentication identifiers from Google, GitHub, or email/password sign-in via Firebase Authentication; workspace names and member roles.

Billing information: your plan, subscription status, and Stripe customer and subscription identifiers. Payments are processed securely by Stripe; we do not receive or store full payment card numbers.

Service configuration: identity names, assigned email addresses and phone numbers, custom extraction rules, webhook URLs, human-fallback destinations (email, webhook URL, phone number), API key metadata (a SHA-256 hash and short display prefix, never the raw key after creation), and settings.

Encrypted secrets: TOTP seeds you store in the vault, held only in encrypted form (see Security below).

Transient message data: inbound emails and SMS messages sent to your identities, and metadata about voice calls to your numbers, processed to extract one-time codes and magic links.

Sanitized audit and usage data: event types, timestamps, masked sender (for example "***@github.com"), classification, latency, quota counters, and API/IP request logs. Audit logs do not contain raw message bodies, full subjects, or plaintext codes or links.

Website and device data: IP address, browser type, pages viewed, and cookies or similar technologies needed for sign-in sessions and security. We do not use third-party advertising trackers.

Communications: messages you send to support and your preferences for product and billing emails.

3. How We Handle Message Content (Zero-Retention Design)

Sentry Relay is designed not to persistently store message content:

We never write raw email bodies, raw SMS text, or plaintext one-time codes to our primary database or logs.
Extracted codes and links, with limited metadata (channel, sender, subject, received time), are held only in an in-memory event store (Upstash Redis) for a short time-to-live that you configure between 60 and 600 seconds (default 600 seconds), or deleted immediately after retrieval if "burn after read" is enabled.
Extraction is deterministic (rules and pattern matching). Message content is not sent to any large language model or AI service.
Messages that are not authentication messages are discarded, except that if Human Fallback is enabled, non-authentication texts and call forwarding are relayed to the destination you configured (for example via Resend email, a webhook, or a voice bridge). Those destinations are under your control.

If you configure outbound webhooks, extracted data is delivered to the endpoint you choose, and that endpoint’s handling is your responsibility.

4. How We Use Information

To provide, operate, secure, and support the Service, including routing inbound messages to the correct identity and enforcing quotas and rate limits;
To process payments, manage subscriptions, and send billing, quota, and account notifications;
To detect, investigate, and prevent fraud, abuse, and violations of our Terms;
To send service announcements and, where permitted, product updates (you can opt out of non-essential emails);
To maintain, debug, and improve the Service using aggregated or de-identified data; and
To comply with legal obligations and enforce our rights.

We do not sell personal information, and we do not share it for cross-context behavioral advertising. We do not use Customer Data to train AI models.

5. Legal Bases (EEA, UK & Similar Regions)

Where GDPR or similar laws apply, we rely on: performance of a contract (providing the Service); legitimate interests (security, fraud prevention, service improvement) balanced against your rights; legal obligation (tax, accounting, compliance); and consent where we ask for it, which you may withdraw at any time.

6. How We Share Information

We share information with service providers that process it on our behalf under contractual protections, and only as needed to run the Service:

Stripe, Inc. (payments, billing, and merchant-of-record services; Stripe acts as an independent controller for its own payment, fraud, tax, and compliance purposes);
Google Cloud / Firebase (hosting, authentication, Firestore database, Cloud KMS key management);
Cloudflare (inbound email routing and processing);
Telnyx (phone numbers, inbound SMS and voice);
Upstash (ephemeral in-memory event storage); and
Resend (transactional email such as invites, alerts, and Human Fallback notices).

We may also disclose information: to workspace owners and admins for workspaces you belong to; to comply with law, legal process, or government requests; to protect rights, safety, and security; and in connection with a merger, acquisition, financing, or sale of assets (with notice where required). We may share aggregated or de-identified information that does not identify you.

7. Data Retention

Extracted codes, links, and message metadata: 60 to 600 seconds (or immediately after read with burn-after-read).
Sanitized audit logs: automatically deleted after 24 hours (Sandbox), 7 days (Builder), 14 days (Growth / Pro), or 30 days (Agency & Fleet), depending on plan.
Account, workspace, identity, and configuration data: kept while your account is active and deleted or de-identified within a reasonable period after you delete your workspace or account, typically within 30 days, except as noted below.
Encrypted TOTP secrets: deleted when you delete the secret, identity, or workspace.
Billing and tax records: retained as required by law and by Stripe, typically several years.
Backups and legal holds: residual copies may persist briefly in backups, and we may retain information needed to resolve disputes, prevent abuse, or meet legal obligations.

8. Security

We protect information using measures such as TLS in transit; per-workspace envelope encryption of TOTP secrets using AES-256-GCM with keys wrapped by Google Cloud KMS; SHA-256 hashing of API keys; signature verification of inbound webhooks; role-based access controls; and workspace and identity isolation. No method of transmission or storage is perfectly secure, and we cannot guarantee absolute security. If we become aware of a breach affecting your personal information, we will notify you and regulators as required by law.

9. International Transfers

We and our providers are located in and process data in the United States and other countries where those providers operate. If you are in the EEA, UK, or Switzerland, we rely on appropriate safeguards for transfers, such as Standard Contractual Clauses or equivalent mechanisms offered by our providers.

10. Your Rights & Choices

Depending on where you live (including the EEA, UK, California, and other US states), you may have the right to access, correct, delete, or export your personal information; to object to or restrict certain processing; to withdraw consent; and to not be discriminated against for exercising privacy rights. You can update much of your information in the console. To make a request, email privacy@sentryrelay.com. We may need to verify your identity, and may decline requests where permitted by law. You may appeal a denial by replying to our response, and you may lodge a complaint with your local data protection authority.

If you are an end user whose messages were received by a Sentry Relay customer, please contact that customer, as they control that data. We will assist them in responding to requests.

We do not respond to browser "Do Not Track" signals because we do not track users across third-party sites.

11. Cookies

We use essential cookies and similar technologies for authentication (session cookies), security, and preferences. You can block cookies in your browser, but the console may not work without them. We do not use advertising cookies.

12. California & Other US State Disclosures

In the past 12 months we have collected the categories of personal information described above (identifiers, commercial information, internet activity, and account credentials) for the business purposes described above, and disclosed them to the service providers listed above. We do not sell or share personal information as those terms are defined under California law.

13. Children

The Service is intended for business and developer use and is not directed to children under 18. We do not knowingly collect personal information from children. If you believe a child has provided us information, contact privacy@sentryrelay.com and we will delete it.

14. Changes to This Policy

We may update this Privacy Policy from time to time. For material changes we will notify you by email or in the console before they take effect. The "Effective date" above shows the current version.

15. Contact

Sentry Relay, https://sentryrelay.com. Privacy requests and questions: privacy@sentryrelay.com. Security reports: security@sentryrelay.com.