Testimonial Studio

Privacy policy

Updated 25 October 2026

Testimonial Studio stores the proof a project owner asks a person to share, and the account data needed to run that project.

What a person submits

A public form can collect a name, role, quote, star rating, photo, video, a transcript of that video, a social link, and extra fields the project owner added. The consent checkbox is required. The form also stores the time of that consent. A hidden field is used only to drop automated submissions.

What an account stores

Project owners and invited teammates have a name, email, password hash, and role. The dashboard session is an httpOnly cookie that lasts 12 hours. Invite and reminder emails go out through the configured mail server. Each invite includes an unsubscribe link.

Where it lives

Records are in MongoDB. Photos and videos are on Cloudinary. Google Gemini may read a quote or a video to suggest a key line, a score, spam flags, tags, a social draft, a case study, or a transcript. Those fields are stored on the testimonial.

Who can see it

The project owner and teammates with access can see submissions, including ones that are still pending or hidden. Approved testimonials can appear on the wall, in an embed, and in the project read API when the caller has the project key. A signed webhook can notify a URL the owner configured.

A person’s controls

After submitting, the thank-you screen gives a private link to download the submission as JSON or delete the quote and its video. Unsubscribe stops further reminder emails for that invite.

Errors

If a Sentry DSN is configured, error reports from the app are sent to Sentry. Those reports are for fixing failures and are not used to build a marketing profile.