Stacktree

Sub-processors

Effective 2026-09-07. 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-processorPurposeData involvedLocation
CloudflareAll hosting: Worker compute, R2 storage, D1 database, DNS, CDNHosted content, account metadata, operational logs (IPs HMAC-hashed at the edge)Global edge (EU SCCs in place)
ClerkAuthentication and sessions for the dashboardEmail address, social-provider profile, session tokensUnited States
StripePayment processing (subscriptions, pay sessions)Payment details (never visible to us), customer identifierUnited States / EU
ResendTransactional email (magic-link viewer verification, notifications)Recipient email address, message contentUnited States
SentryError monitoringError events with URL paths (query strings stripped); no raw IPs or request bodiesUnited States / EU
PostHogProduct analytics and dashboard session recordingsHashed event properties and paths; recordings of dashboard layout and interactions for signed-in account holders, with all text, inputs, links, addresses, labels and other attributes masked or blanked; the address of the dashboard screen and no other; never published pages, their readers, or the addresses of pages; no raw IPsUnited 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-09-07.