Does Miaowa GEO have an SLA, and what does it promise or not promise?
There is a public service-level statement at /legal/service-levels. It commits to a fixed cycle anchor, failure logging and denominator rules, verifiable evidence completeness, support response times, and incident and security notification. It explicitly does not promise a status page, an uptime percentage, service credits, cycle completion within a set number of hours, any mention-rate uplift or a guaranteed recommendation slot.
Version 1.1 · Last updatedMiaowa GEO does not carry a conventional SaaS SLA of the uptime-percentage-plus-service-credits kind. It has a public service-level statement instead, at /legal/service-levels, which turns what can be promised into verifiable rules and states plainly what cannot. That lets a buyer see before signing where acceptance terms can attach and where they cannot.
What is committed
- Cycle anchor: one cycle every 72 hours from the baseline batch, anchored when the baseline is created and never drifting with platform response times; no re-asking outside a closed cycle.
- Failure logging and denominator rules: failed, blocked and unknown tasks are recorded as such, excluded from business metrics and never presented as success; refusals and not-triggered AI Overviews are valid observations with their own status.
- Verifiable evidence completeness: the workspace monitoring log shows an evidence-completeness percentage and a runtime-exception rate per cycle, and every task drills down to answer text, screenshot, sources, timestamp and status.
- Support response: self-serve questions received on a business day get a first reply by the end of the next business day; project and managed response times are written into the contract.
- Incident and security notification: incidents affecting client data or multiple cycles are flagged in the workspace and emailed to the client contact; security incidents are notified within 72 hours under the DPA.
What is explicitly not promised
| Not promised | Why |
|---|---|
| A public status page or a single uptime percentage | Collection depends on the web entry points of six third-party platforms; availability is not under our sole control and a single figure would mislead. |
| Service credits or availability-based compensation | Self-serve plans are a fixed monthly fee; failed tasks do not consume quota and are not refunded per task. Project contracts can set an evidence-completeness threshold instead. |
| Completion of any cycle within a set number of hours | Collection speed depends on platform response and anti-automation behaviour; baseline results appear as tasks complete, and no hour count is stated. |
| A mention-rate or recommendation uplift | We monitor and keep evidence; we do not control what the AI answers. There is no guaranteed AI recommendation slot. |
Why it is written this way
A monitoring product is only worth buying if its numbers can be re-checked. An SLA that quotes an uptime percentage without publishing its denominator is harder to accept than a statement that lists its boundaries honestly. We limit commitments to what we control: a fixed basis, retained evidence, honest exception handling and timed responses. During contract negotiation, the four public documents at /legal/service-levels, /legal/dpa, /legal/subprocessors and /legal/refund-policy can be used as reference annexes.
- Can a project contract set a stricter SLA?
- Response times, an evidence-completeness threshold, cycle length and prompt count can all be agreed in the contract. A guaranteed mention-rate uplift or recommendation slot is not offered at any tier.
- What if a whole month produces no valid cycle?
- If a subscription month has no valid cycle for reasons on Miaowa's side, the self-serve plan is refunded in full; see /legal/refund-policy. That is a refund rule, not a service credit.
Last updated . The capabilities page and the pricing page are authoritative where they differ.
Help centre
Back to the index, or email contact@miaowageo.com.