Security and compliance overview for a testimonial platform
This page summarises, in plain terms, how a testimonial collection and display service describes its current protections for accounts, customer content, payments, and personal data.
It is intended as a starting point for buyers, privacy reviewers, and procurement teams who need to know what is documented publicly and what to ask about next.
What this page covers
The service in question helps organisations gather, organise, and publish customer testimonials. The material below explains the controls described for that work, the third-party services involved, and the route for follow-up questions. Legal wording itself sits in the separate privacy and terms documents rather than being reproduced here.
Who to contact
Use the owner contact address for security enquiries, privacy requests, and procurement follow-ups: {{OWNER_CONTACT_EMAIL}}. Include the specific workflow or question you need answered so the reply can address the right part of the service.
Core safeguards
Protections are described as a combination of application-level checks, managed cloud infrastructure, and day-to-day operational tooling. The sections below separate those layers so a reviewer can see which control applies to which kind of risk.
Account protection
Dashboard access relies on signed tokens. Sensitive operations receive additional protection, tokens are kept short-lived, and tokens that have been blocked can be invalidated, which limits how long a compromised session remains useful. Where browser access is involved, it is limited to approved origins.
File and media handling
Uploaded testimonial media can be kept and delivered through AWS for managed cloud storage, with Mux handling video processing and hosting. Customers can manage or remove their own testimonials and media inside the product, and privacy requests can be directed to the team.
Operational tooling
Subscription payments are handled through Stripe. Product analytics and support tools are used to understand usage, improve the product, and answer customer questions. Public pages, widgets, and collection flows may also record view and engagement analytics so customers can see how testimonials perform.
Public subprocessor list
The named services below were visible in the current product, support, and website codebases at capture time. Some are used across the whole service; others apply only to specific pages or features. Destinations a customer connects themselves — such as webhooks, Zapier, Make, or other external apps — are not listed because they are switched on case by case.
Named subprocessors and locations
- Amazon Web Services (AWS) — core infrastructure, file storage, presigned uploads, and serverless processing. Place of subprocessing: United States.
- Stripe — subscription billing and payment processing. Place of subprocessing: United States and Ireland.
- Google Authentication — supports Google sign-in. Place of subprocessing: United States.
- Twitter Authentication — optional; used when a user connects a Twitter account to import testimonials or related content. Place of subprocessing: United States.
- Mux — video ingestion, processing, hosting, and playback for video testimonials. Place of subprocessing: United States.
- PostHog — product analytics in the application experience. Place of subprocessing: United States based.
- Amplitude — product and growth analytics across workflows. Place of subprocessing: United States.
- Crisp — provides the live-chat channel for help conversations across the app and public pages. Processing takes place in the European Union, specifically the Netherlands and Germany.
Procurement checklist
- Confirm which subprocessors touch your data: core hosting and storage (AWS), payments (Stripe), video (Mux), analytics (PostHog, Amplitude), support chat (Crisp), and any sign-in provider you enable.
- Check the processing location for each one against your own data-residency requirements, especially the EU-based support tooling versus the US-based services.
- Separate platform subprocessors from integrations you connect yourself, since the latter are not covered by the public list.
- Ask whether a DPA is available on request, because this page confirms only a public overview.
- For a questionnaire, privacy clarification, or a question about one workflow, email {{OWNER_CONTACT_EMAIL}} with the exact request.
Need a security answer for procurement?
If you need a questionnaire response, a privacy clarification, or confirmation about a particular workflow, email {{OWNER_CONTACT_EMAIL}} and state the exact request. Review the Privacy Policy and Terms of Service for the governing legal terms.
Frequently asked questions
Are GDPR-style privacy requests supported?
Yes. Requests covering access, correction, export, or deletion can be sent to {{OWNER_CONTACT_EMAIL}}. The linked privacy document describes those rights in fuller detail.
Is there a DPA or public subprocessor list?
This page gives a public overview drawn from the current product and website tooling. It names the main third-party services and where their processing is located, while noting that some apply only to particular pages or features.