A small service is best evaluated by the record it leaves behind. Every change to the service, every internal review, every incident lands here in the order it happened. Nothing is rewritten after the fact.
Pass across the legal and marketing surface. Five decisions filed: demo-route privacy, trust-page scope, canonical deployment timeline, refund-language canonicalization, SLA target value. Drift guards added so the wording can't regress during future edits.
New dome composition on the home hero. Tightened the opening message; reduced-motion preference is honored — the motion is cosmetic, never load-bearing for comprehension.
Six-card executive-reassurance format. DPA and sub-processor links go direct. Earlier drafts exposed implementation details; this revision is scoped to commitments a reviewer can sign off on.
Eleven phrases removed that had drifted from the approved register (e.g. product-framing words Loomaru doesn't use about itself). The approved phrase list is now enforced by a build-time check — regressions break CI.
External probe cycle verified end-to-end. First root-cause note template filed so that when an incident happens, the communication artifact exists before it's needed.
Contrast and focus-visible fixes across the analysis page. Baseline accessibility snapshot archived so regressions are detectable on the next visual-diff run.
Every page that states a duration now reads from one constant. Before this, three surfaces had slightly different numbers — a small drift that compounds credibility cost over time. Fixed at the source.
One sentence, one source, identical wording on hero, pricing, Terms, and FAQ. A drift guard blocks re-introduction of competing phrasings.
Cause: stale cache node served a pre-deploy response briefly after the new build went live. Purge resolved it inside two minutes. Zero merchant-facing impact. Root-cause note filed; deploy procedure updated to purge pre-emptively.
How this page works
Technical detail is kept off this page on purpose — a public log shouldn't double as a map for attackers. For full depth or our sub-processor list, email vadim@loomaru.com.