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

Why this one

Nine promises, each held in code rather than in a policy

Every tool in this category collects testimonials and puts them on a page. The difference is what it will refuse to let you do — and whether that refusal is a sentence in a policy or a check that runs.

The nine

  1. A customer's words are never editable

    No route anywhere — no dashboard control, no API field, no administrator, no support request — can change a testimonial's text. You may publish it as written, or publish it with a span removed and the reader told so. If a removal proposal differs by a single word, it is discarded rather than applied.

  2. Permission is enforced, not merely stored

    The website and social answers decide what may be served, on every request: a testimonial that refused your website cannot be served by a widget, a wall or the API, however many times it is approved, and one that refused social cannot be made into an image or a clip. Hazelsong places no ads, so that answer is recorded and handed to you.

  3. On a paid plan, typed words are read for risk on arrival, while the month's readings last

    A promised outcome, a figure, a claim of specialization, somebody's private detail — flagged with the reason, on arrival, on Starter and Pro within the month's readings, and never published automatically. On the free plan, which carries no readings, nothing is read and the dashboard says so; a recording or a picture is never read by AI, and anything not read waits for you.

  4. Nothing is invented, anywhere

    Not on your page and not on ours. The testimonials on this site are read from Hazelsong's own wall through the same public endpoint your site would read, and the page shows nothing when it is empty. The model may flag, remove, split, translate, transcribe and draft; it may never write praise or a figure.

  5. Your files come out whole, on the free plan

    One copy of a video is stored — the original — and it is handed back at that quality to anybody who can open the project. We never made a worse copy in order to sell you the better one.

  6. You can leave completely, and check that you did

    Destroying a project removes every record it holds and every file under its storage, each key named in full rather than swept up by a pattern, with a test that walks the whole store and fails if one survives.

  7. A reader can check how any of it was collected

    Every testimonial you publish carries a link to its own record, on an address that is not your website: how it arrived, which permission was given and by whom, whether it was read before publication, whether anything was removed, whether a reward was attached. Built from what was stored at the moment it happened, so there is nothing to compose. It cannot be styled, bought or switched off — on any plan, including the ones that take our name off your wall.

  8. We will not help you hide the unhappy half

    The 0-to-10 question is often sold with routing: the nines and tens to a public review, everybody else to a private form. Here the score changes the wording of the question above the box and nothing else. Everybody is offered the same place to write and the same permission checkbox, and your figure is calculated over every answer you collected rather than the ones you chose to publish.

  9. An incentive is disclosed everywhere, permanently

    If a reward was attached to writing — before or after the words — every published copy says so, and there is no field anywhere that can turn that back off.

And the ordinary things, at the ordinary size

  • 15 testimonials held on the free plan — held, not per month, so deleting one frees a slot
  • 23 widget layouts, all of them on every plan
  • 40 places to import from, none of them scraped
  • Video recorded in the browser, with nothing to install
  • Named walls on every plan — 100 a project on Pro — each with its own address and review markup
  • Reels, testimonial images, case-study drafts and thank-yous
  • API, signed webhooks, seats, your own domain and your own mark
  • A CSV and every original file, on every plan

Every one of them has a page, and each page ends with what it will not do.

Our own wall

The same endpoint, the same rules, the same refusals. If we had written ourselves a better one, it would be sitting on a page that says nothing is invented.

The home page reads Hazelsong's own wall through the same public endpoint your site would read, and shows the testimonials there only once real customers have written them and allowed it. Until then it shows none — never a placeholder dressed as a customer.

Judge it by what it refuses

Everything above is running now. Open a project and try to break one of the nine.