Sub-processors
Effective 2026-06-11. These are the third-party services (“sub-processors”) Stacktree uses to operate. Each processes data only as needed for the purpose listed, under its own data-processing terms. We do not sell personal data, and no sub-processor receives more than its purpose requires.
| Sub-processor | Purpose | Data involved | Location |
|---|---|---|---|
| Cloudflare | All hosting: Worker compute, R2 storage, D1 database, DNS, CDN | Hosted content, account metadata, operational logs (IPs HMAC-hashed at the edge) | Global edge (EU SCCs in place) |
| Clerk | Authentication and sessions for the dashboard | Email address, social-provider profile, session tokens | United States |
| Stripe | Payment processing (subscriptions, pay sessions) | Payment details (never visible to us), customer identifier | United States / EU |
| Resend | Transactional email (magic-link viewer verification, notifications) | Recipient email address, message content | United States |
| Sentry | Error monitoring | Error events with URL paths (query strings stripped); no raw IPs or request bodies | United States / EU |
| PostHog | Product analytics | Hashed event properties and paths; no raw IPs | United States / EU |
Slack integration
The Stacktree Slack app stores your workspace's team ID and OAuth tokens on Cloudflare (above) to operate the Host on Stacktree message shortcut. Slack itself is the platform you authorize, not a sub-processor of ours; its handling of your workspace data is governed by Slack's privacy policy.
Changes to this list
If we add or replace a sub-processor, we update this page and its effective date before the change takes effect, and announce material changes to registered users by email. Questions: privacy@stacktr.ee.
Last updated 2026-06-11.