How it works
Permission, step by step
They choose the places, one by one
Website, social media, advertising — separately, because somebody happy to appear on your site may not want to be in a paid ad.
The sentence and the date are kept
The exact words they agreed to, with the timestamp, stored beside the testimonial and included in your export.
Every channel here asks before it serves
A testimonial that did not consent to the website cannot be served by a widget, a hosted wall, or the API, however many times it has been approved. A testimonial that did not consent to social cannot be made into an image or a clip. Hazelsong runs no advertising channel, so there is nothing here for that third answer to stop — you have it, and it is yours to honor.
Your own release, as well as ours
On Starter and Pro a form can carry a paragraph you wrote, such as an authorization or an image release, which the person must check in addition to the permission. A submission without that box is refused with a sentence that says so. The paragraph's words, its version and the time are stored with the testimonial, beside the permission and never in place of it: where the words may appear is still decided by the places they checked off.
Where may they show it?
I give Your Business permission to publish this testimonial — including my name, role, company and photo, as written here. They may not reword it.
on their websiteon their social mediain their ads and printed materialThe sentence they check off is stored with the date. A place they have not checked off is a place where it cannot appear — the widget, the wall and the API all check.
Send testimonialSafe by design
The rule that makes it safe to have
Clear boundaries
What it will not do
Every capability page ends with this list. It is the part that says what you are actually buying.
- It will not let an approval override a refusal.
- It will not put an author's email address in any public answer, ever.
- It will not treat silence as permission.
- It will not enforce the advertising answer for you. There is no ad served from here to withhold, so that answer is stored, shown to you and included in your export — and honoring it in your own ads and printed material is your job, not ours.
- It will not let your own release replace, narrow or widen the permission. A release only adds an agreement; it decides nothing about where the words are shown.
- It does not write, review or vouch for your release, and does not tell you whether it meets a rule you are held to.
Where it lives in the code: lib/consent.ts · app/api/v1/testimonials/route.ts · lib/release-rules.ts
Questions
Asked about this
From Help, where every answer is written from the product as it runs.
Where is the consent kept?
Beside the testimonial: its recorded permission sentence, scopes, date and source. For a customer submission, the sentence records what the person agreed to here. Imports, connected feeds and API additions carry an account holder statement instead; they do not claim the writer agreed here. These records are included in your CSV export.
Which permissions does Hazelsong actually enforce?
There are four separate choices: your website, public pages hosted by Hazelsong, social media, and ads or printed material. Website widgets and the testimonial API require website permission; public hosted walls require hosted permission, plus publication enabled by a verified project owner. Social images and clips require social permission. Approval alone grants none of these, and missing scopes grant no permission. Ads and printed material are made outside Hazelsong, so that answer is recorded for you to honor rather than enforced by an advertising channel here.
They checked off website but not ads. What happens if I use it in an ad?
Nothing here stops you, because nothing here places ads. What the product does is keep the answer where you can find it: the consent sentence on the card names only the places that person allowed, and your CSV export lists what they checked off — which is the form you would want it in if they, or anybody else, ever asked what they had agreed to. The decision, and the responsibility for it, are yours. Hazelsong checks the recorded website, hosted-page and social permissions when serving those respective channels.
Does the API respect the website permission too?
Yes, and that is on purpose: an integration reading your testimonials is a publishing pipe. /api/v1/testimonials filters on website permission and says in its own answer that it did.
This is running now
Open a project and use it. Nothing on this page is a roadmap.