Subprocessor Register

ReTestimonial uses the providers below to operate the service or to perform a feature a workspace customer chooses. Not every provider receives every category of data, and conditional providers are invoked only for the stated workflow.

This register describes product use and data categories. Customer-specific processing instructions, confidentiality, security, deletion, audit, transfer, and change-notice terms are governed by the applicable agreement or Data Processing Agreement. Contact privacy@retestimonial.com for those terms or for current transfer-location details relevant to your account.

• Clerk — Authentication, account security, and workspace identity management. Data may include account identifiers, profile details, authentication events, and session data. Used for ReTestimonial account access.
• Vercel — Application hosting, server execution, and delivery; AI model routing (AI Gateway) for Ask AI in the help center and for AI reading of captured text and screenshots; and bot detection (BotID) for Ask AI. Data may include request data, application content processed by a request, Ask AI questions and answers in transit, text and screenshots sent for an AI reading in transit, browser signals for bot detection, and operational logs. Used for the hosted ReTestimonial application and APIs.
• Supabase — Managed PostgreSQL database infrastructure. Data may include account, workspace, testimonial, configuration, and product-event records. Used for primary application data storage.
• Cloudflare — Object storage, edge delivery, caching, security, worker execution, and rendering widget previews for the dashboard. Data may include uploaded files, generated assets, request data, cache keys, and operational metadata. Used for media/assets and selected public delivery surfaces.
• Upstash — Distributed rate limiting and short-lived abuse-prevention counters. Data may include pseudonymous or salted actor keys, project keys, counters, and expiry times. Used when distributed rate limiting is configured.
• Mux — Video upload, hosting, streaming, playback analytics, and transcripts. Data may include video files, captions/transcripts, playback events, and related request metadata. Used when video features are enabled.
• Amazon Web Services — Serverless rendering of social-video exports. Data may include selected testimonial content, source media, render configuration, and generated video. Used when a social-video render is requested.

• Resend — Transactional and customer-configured email delivery. Data may include recipient address, sender details, message content, and delivery events. Used when ReTestimonial sends email.
• Stripe — Subscription, credit, invoice, payment, refund, and billing-management processing. Data may include account and billing details, transaction records, and processor-hosted payment details. Used for provider-hosted payment entry and billing operations; ReTestimonial does not store full card details.
• Tremendous — Gift-card reward fulfillment. Data may include reward recipient details, reward selection, and fulfillment status. Used only when a customer enables and issues rewards.
• Partnero — Affiliate program management, referral tracking, and partner commission payouts. Data may include partner account and payout details and, for a workspace credited to a partner, the workspace identifier, account email, and name sent when the referral is recorded. Used only while the partner program is enabled, for partner accounts and for workspaces credited to a partner.

• Sentry — Application error reporting and operational diagnosis. Data may include error context, stack traces, account correlation, request metadata, and diagnostic events. Used when error monitoring is configured; sensitive request bodies and secrets are not intended inputs.
• PostHog — Product and website analytics: our website, help center and application after you choose Accept optional analytics, the public widget builder, measured without cookies or browser storage, and the main events of each account, sent from our servers. Data may include account identifier and email address; plan and workspace context (counts and states, never names or testimonial content); page and feature events; campaign parameters and, for a sign-up that followed one of our ads, its ad click identifier; device and request metadata. Used when product analytics is configured. On the widget builder, visits are counted with a hash PostHog computes on its servers from a salt that changes every day, the IP address and the browser, and nothing is stored on the device.

• Anthropic — Customer-requested AI analysis, writing, extraction, and OCR features, and answers to help-center questions (Ask AI). Data may include the testimonial, document, image, or prompt content selected for the requested operation, or an Ask AI question with its conversation and help-article excerpts. Used only for features routed to Anthropic.
• OpenAI — Fallback or customer-requested AI and OCR processing. Data may include the testimonial, document, image, or prompt content selected for the requested operation. Used only for features routed to OpenAI.
• Review and social import providers — Customer-requested review and social-content imports, and the business preview in the public widget builder. Data may include public business, product, or profile identifiers, source URLs, and imported public review or post content. Used only when a supported import runs, or when a visitor looks a business up in the public widget builder. These providers are listed by role; their names are provided to a customer on request under the applicable agreement or Data Processing Agreement.
• Google — Customer-requested Google account connection, business discovery, and review imports; business search in the public widget builder. Data may include OAuth/account identifiers, public business/location data, search input, and imported review content. Used only when a customer connects or searches a supported Google integration, or a visitor searches for a business in the public widget builder.

We update this register when our provider set or a provider's material role changes. A customer's right to advance notice, objection, or termination is determined by its applicable agreement or Data Processing Agreement; this page does not replace those terms.

Questions about a provider, a feature-specific data flow, or a transfer mechanism can be sent to privacy@retestimonial.com.