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

Read and decide

Take out the phone number. Change nothing else.

A testimonial arrives with a client's phone number in it, or an opposing party's name, or a case number. You can take that span out and publish the rest — and the reader is told that something was removed.

PlanEvery plan. Removing by hand uses no AI reading.

How it works

Removing a detail, step by step

  1. It proposes the spans; you approve them

    The detail is found and offered with a reason. Nothing disappears from your page because a model thought it should.

  2. Or you select them yourself

    Select the words on the card, press Mark them, and save: each becomes [removed]. No AI reading is used, so it works when the month's readings are spent, and on a version already removed it can only take out more.

  3. What is left is what they wrote

    The removed span becomes [removed]. Every other character is the character your customer typed.

  4. What they meant stays what they meant

    A removal is refused when it would take a word that negates or limits (not, never, no, only, except, but, without, or the same word in Portuguese, Spanish, French or German) out of a sentence that stays, because "It did not work" without "not" says something your customer never said. You are told to remove the whole sentence instead. The same check runs on the AI's proposals and on what you select.

  5. The reader knows

    A published testimonial with a removal says so under it. A quotation with a silent hole in it is a different sentence from the one somebody wrote.

Your dashboard · Pending
Customer name

Every word arrives as they wrote it — even the 555-0142 they meant to leave out.

Read this before publishing"555-0142" A phone number. Take it out before this goes on your site.Read automatically when it arrived. It points; you decide.
A version with parts removed is readyEvery word arrives as they wrote it — even the [removed] they meant to leave out.
ApproveRejectPublish this version instead
Drawn from the product's own markup and labels, with example words — not a real customer.

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 fix a typo, improve grammar, or shorten a sentence.
  • It will not remove a span without telling your reader that it removed one.
  • There is no API field, no dashboard control and no admin path that can change a testimonial's text.
  • Removing by hand will not take out every word: a testimonial you do not want shown is rejected, not emptied.
  • It will not take "not", "never", "only" or a word like them out of a sentence it leaves on the page: the whole sentence goes, or the word stays.

Where it lives in the code: lib/redact.ts, components/HandRedact.tsx

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.