Subprocessors

Riptide relies on the third-party services below to operate the platform. Connected commerce platforms also operate their own services under their own terms; listing them here does not mean they act only as our processors. Each one processes a specific slice of data for a specific purpose, nothing more. This list changes as Riptide evolves; we will update the page and the effective date when we add, remove, or materially change a subprocessor.

Effective
October 13, 2026
Services
8
Hosted in
United States listed for 4 of 8; other provider regions vary
Questions
privacy@riptidequeue.com

Hosting, recovery storage, identity, connected stores, optional message delivery and analytics. Each row describes when that service is used.

ServiceWhat it does for RiptideData that reaches it
Fly.ioHosting and primary database · United States (primary region iad, Ashburn, Virginia)Primary application hosting: the web app, API, connected-store webhook handlers, realtime (SSE) endpoints, and the on-stream overlay run on Fly Machines. Fly also hosts the primary Postgres database in Virginia, terminates TLS, stores application secrets and retains encrypted volume snapshots.Workspace, order, buyer delivery, queue and webhook data; request traffic, application secrets and server logs/metrics. Provider credentials are additionally encrypted by Riptide.
TigrisDatabase recovery storage · Provider-managed Global placement; not restricted to the United StatesStores database full backups and write-ahead logs for recovery of the Fly Postgres service.Recovery copies of database records, including workspace, order, buyer delivery, queue and integration data. Access is restricted to recovery operations.
ClerkIdentity · United StatesSeller identity, workspaces (organizations), and role management.Email address, display name, hashed password (if used), sign-in session metadata, and organization membership.
ShopifyOrders · Shopify-operated regionsMerchant integration authorized by the seller at install time. Source of truth for orders and line items.Orders and line items the seller has authorized Riptide to receive via OAuth scopes and webhook subscriptions.
TikTok ShopOptional native order connection · TikTok-operated regionsSeller-authorized shop connection, order backfill, status webhooks and queue eligibility where the native integration is available. Development-shop access does not mean public app approval.Authorized shop identifiers, order and line-item records, eligibility/status and buyer delivery details available to the integration.
Expo / Apple / GoogleOptional mobile push delivery · Provider-operated infrastructure; no US-only processing claimExpo relays enabled mobile notifications to the device platform push service (Apple or Google). In-app security-control alerts do not use this channel.Device push token, notification title/body, category, badge, notification identifier and app destination. Depending on the alert, content can include buyer aliases, show names and operational exception text.
DiscordDelivery · United StatesOutbound delivery target for queue events, stalled-queue alerts, and wrap-up summaries when the seller configures a Discord webhook.Embed payloads the seller has opted to send (queue state, buyer handles, session metadata). The webhook URL is stored encrypted by Riptide.
PostHogAnalytics · United States (PostHog US Cloud, Riptide project)Optional acquisition and seller product analytics, enabled by browser consent and a separate owner/admin workspace preference for completed operations. Autocapture is disabled. Separately consented, masked session recordings are limited to supported public marketing and top-hits pages; private workspaces are excluded.Allowlisted event and normalized page names, pseudonymous seller/workspace identifiers, live/manual/sandbox/test source labels and bounded task durations/error categories. Optional masked public-page recordings and allowlisted analytics exclude customer contact details, order contents, payment details, signed URLs, tracking numbers and unrestricted form text.

Paid workspace owners get email before a material new subprocessor. The effective date above is the source of truth.

Workspace owners on a paid plan will receive email notice before we add a new subprocessor that materially changes how your data is processed. For day-to-day changes, check back on this page. The effective date at the top is the source of truth.

Questions about this list go to the privacy mailbox.

Questions about this list should go to privacy@riptidequeue.com. The contact page explains which mailbox reads what.