Skip to content
Hazelsong is still being built.Skip to content
Hazelsong

Read and decide

A testimonial in a language your reader does not have

A customer wrote in Portuguese and your page is in English. The translation is published beside the original, and it says it is a translation — with the original one click away.

PlanPro.

How it works

Translation, step by step

  1. The original is kept, always

    A translation is an addition. It never replaces what somebody wrote, and it never becomes the thing your export contains instead.

  2. It is labeled on the page

    A reader can see it was translated and can read the original.

Safe 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 overwrite the original.
  • It will not publish a translation without marking it as one.

Where it lives in the code: lib/languages.ts · lib/ai.ts

Questions

Asked about this

From Help, where every answer is written from the product as it runs.

What does Hazelsong check before publishing, and what does it not verify?

Before anything is public, Hazelsong checks three things: that its recorded permission (the writer's own sentence, or, for an import, the API or a feed, the business's statement that it has permission) allows the place it would appear, and it is served nowhere else; the risk reading of its typed words, when the month's AI readings allow, while a recording or a picture is never read by AI and anything not read says so; and that the business approved it, in person or through the automatic moderation it chose to switch on. Nothing is published before that approval. Hazelsong does not verify that what a testimonial says is true, who wrote it, or that they bought anything, beyond what its record shows: how it arrived (the business's collection page, an import, the API or a feed), its permission and when it was given, whether a reward was attached, and whether a second person approved it. Publishing through it is not an endorsement of any testimonial.

Can I fix a typo in a testimonial?

No. There is no route in this product — no dashboard control, no API field, no administrator, no support request — that can change a testimonial's text. That is the rule the whole product is built around, and it is checked in code rather than promised in a policy.

Then what do I do about a phone number somebody left in it?

Remove that span: press Check for things to remove for a proposal, or Remove a part yourself to select the words, which uses no AI reading. The span becomes [removed], every other character stays exactly as written, and the reader is told something was taken out. If a result differs from the original by a single word anywhere else, it is discarded rather than applied.

Can I shorten a long testimonial for a widget?

Not by storing a shorter version: nothing here can keep a cut-down copy as though it were what somebody wrote. What a layout may do is show less of it — the compact, marquee, toast and sidebar layouts stop a long testimonial at six lines, and there is no control that opens the rest. Every other layout shows the whole of it, so the choice to make here is the layout.

More on the testimonials themselves

This is running now

Open a project and use it. Nothing on this page is a roadmap.