Subprocessors
The third-party services we use to operate Morse.
Last updated: October 2026
Morse uses the third-party services below to operate the platform. Each one is used only to operate Morse. We do not sell your data, and we do not send your telemetry to any service outside this list.
| Subprocessor | Purpose | Data processed | Processing location |
|---|---|---|---|
| Google Cloud | Application hosting (Cloud Run), managed PostgreSQL (Cloud SQL), managed Redis | All platform data — account records and telemetry | United States |
| Railway | Previous application hosting, managed PostgreSQL and Redis; being retired after the move to Google Cloud | All platform data — account records and telemetry | United States |
| Cloudflare | DNS, CDN, and R2 object storage for large trace payloads | Trace payloads above the inline size threshold; site traffic metadata | United States |
| Cloudflare Turnstile | Bot protection on sign-up | IP address and browser signals from the sign-up page | United States |
| Tinybird | Analytics database behind dashboard queries | Trace and span records as stored by Morse: names, timings, token counts, costs, metadata and error messages after redaction; prompt and completion bodies only in encrypted form | United States |
| Stripe | Payment processing and subscription billing | Billing contact and payment details (card data never reaches Morse) | United States |
| Resend | Transactional email delivery | Email address and message content for alerts and account notifications | United States |
| Google Workspace | Morse team email, including the support, privacy and security mailboxes | The content of emails you send us, and your email address | United States |
| Slack | Internal notifications to the Morse team | Design-partner request details (name, email, company and answers), in-app feedback with the sender's email and organization, and support alerts naming the affected organization | United States |
| OpenAI | LLM inference for Ask Morse (Copilot), the Anomaly Investigator, quality evaluation scoring, trace pattern classification, agent topology discovery, and documentation search embeddings | Trace excerpts and evaluated spans after PII redaction; the questions you ask; agent descriptions you provide during setup | United States |
| PostHog | Product analytics for the Morse dashboard itself | Usage events for your Morse session — not your telemetry data | European Union |
| Sentry | Error monitoring for the Morse application | Stack traces and request metadata from Morse errors | United States |
| Better Stack | Uptime monitoring and the public status page | Endpoint availability only — no customer data | European Union |
AI Subprocessors
OpenAI is the AI provider that receives customer data at launch. It is called by Ask Morse (Copilot) when you ask a question, by the Anomaly Investigator when an alert fires, by quality evaluation scoring on sampled spans (all plans), by trace pattern classification when you open a trace explanation, and by agent topology discovery from the website, repository or files you provide during setup. Each call carries only the trace excerpts or setup material it needs, after the PII redaction configured for your organization has been applied at ingestion. OpenAI is contractually barred from training its models on data submitted through its API.
Quality scoring runs on every plan, including Free, so redacted excerpts of sampled spans reach OpenAI whenever your organization sends traces. There is no in-product setting to turn it off yet.
Changes to This List
We will update this page before a new subprocessor begins processing customer data, and notify account owners by email at least 30 days in advance. If you object to a new subprocessor, contact us and we will work with you on an alternative or, where none exists, allow you to terminate without penalty for the remainder of your paid term.
Contact
Questions about this list, or about a Data Processing Agreement: [email protected].
See also our Privacy Policy, Security & Trust page, and Data Retention Policy.