Legal

Terms of service

The agreement between you and Pingoru. We've written it in plain English wherever the law lets us; the parts that have to be precise are still precise.

Effective: May 6, 2026

By creating an account, signing in, or using any part of Pingoru (the website, the dashboard, notifications, the public REST API, or the MCP endpoint), you agree to these terms. If you don't agree, please don't use the service.

Contents

  1. The service
  2. Your account
  3. Acceptable use
  4. API and MCP use
  5. Ownership of data
  6. Plans and billing
  7. Availability and SLA
  8. Termination
  9. Disclaimer of warranties
  10. Limitation of liability
  11. Indemnification
  12. Governing law
  13. Changes to these terms
  14. Contact

1. The service

Pingoru is a status-page aggregator: it polls public status pages for thousands of cloud and SaaS providers and surfaces the results through a dashboard, email and webhook notifications, a REST API, and an MCP endpoint for AI assistants. "Pingoru", "we", and "us" refer to the small independent team operating the service from Canada. "You" means the individual or organisation accessing the service.

2. Your account

  • You're responsible for keeping your password and API keys confidential. Activity originating from your account or your keys is treated as authorised by you.
  • You agree to provide a real, working email address and to keep it current — we use it to deliver alerts and account notices.
  • One natural person per account, unless you've signed up for a team plan that explicitly permits shared access. Don't share a single account across multiple people to avoid the per-account plan caps.
  • You must be at least 16 years old (or the age of digital consent in your jurisdiction, whichever is higher) to create an account.

3. Acceptable use

Use Pingoru like a normal person checking the status of services they care about. The list below is what we'd ask you not to do. Most of it is common sense; we're stating it plainly so there's no ambiguity later.

Don't:

  • Try to break, probe, or interfere with the service — no vulnerability scanning without prior written consent, no denial-of-service attempts, no attempts to bypass rate limits or plan caps.
  • Reverse-engineer, decompile, or otherwise try to derive the source code of the service, except to the extent applicable law expressly permits.
  • Use Pingoru to send spam, harass anyone, or distribute malicious content via the notification channels you configure (email, webhooks, etc.).
  • Misrepresent your identity or your relationship to a third party when configuring monitors, integrations, or contact addresses.
  • Use the service to monitor your own users on a service for which you don't have authorisation to do so, or in any way that violates a third party's terms of service.

4. API and MCP use

The REST API and MCP endpoint exist so that humans (and the AI assistants those humans drive) can ask focused questions about the status of services in their stack. They are not a wholesale data export channel. The following uses are not permitted:

  • Bulk harvesting or mirroring of Pingoru's incident database, component status, status update timelines, provider catalogue, or aggregated outage history — whether through the REST API, the MCP endpoint, the public website, or any other interface.
  • Building a competing service using data sourced from Pingoru. This includes, without limitation, status-page aggregators, outage trackers, AI status assistants, dashboards, embeddable widgets, or analytics products whose value substantially derives from Pingoru-collected data.
  • Republishing or redistributing incident timelines, component status snapshots, or provider catalogues sourced from Pingoru, except for the limited purpose of sharing a specific incident or status with people inside your own organisation.
  • Automated, unattended polling at a cadence or breadth that approximates Pingoru's own data collection. The MCP endpoint and API are sized for interactive, in-the-loop use by an AI assistant or a human-operated dashboard, not for background-job replication of our database.
  • Plan-cap circumvention, including but not limited to creating multiple Pingoru accounts to multiply the monthly call cap, the monitor cap, or the API-key cap; or sharing API keys across organisations to pool quota.

We monitor API and MCP usage for patterns consistent with the prohibited uses above (e.g. high distinct-vendor query counts, steady-state programmatic polling, cross-account quota pooling). When we detect them we may throttle, suspend, or terminate the account, with or without notice depending on severity.

5. Ownership of data

Status data, incident timelines, and the provider catalogue

The aggregated status data, incident timelines, component-state histories, derived analytics (uptime percentages, mean-time-to- resolve, etc.), and the curated provider catalogue exposed through Pingoru are original work product compiled by us from public sources. They are licensed to you, while your subscription is active, for the limited purpose of monitoring services that you, your employer, or your customers use. They remain our property and are not transferred to you.

Your account data

The monitors, notification groups, recipients, webhook URLs, and preferences you configure remain yours. You can export them from the dashboard or by contacting support, and you can delete your account at any time (see the privacy policy for retention timelines).

Logos and trademarks

Provider logos and names displayed on Pingoru remain the property of their respective owners. We display them under nominative-fair-use principles to identify the services being monitored. "Pingoru" and the Pingoru kangaroo logo are our trademarks; please don't use them in a way that suggests endorsement without our permission.

6. Plans and billing

  • Pingoru has a free plan and one paid plan ("Pro", currently $15 USD/month). Up-to-date prices and plan inclusions live on the pricing page.
  • Paid plans are billed monthly in advance through Stripe. Your card data is handled by Stripe under their terms; we never store full card numbers.
  • You can cancel at any time from Settings → Plan. Cancellation stops future charges; the current paid period continues to its end and is not pro-rated.
  • We don't offer routine refunds, but if a charge feels wrong — accidental upgrade, double-charge, you forgot to cancel — email us and we'll do the right thing.
  • If a payment fails, we'll retry over a few days and let you know by email. Failure to pay after the grace period downgrades you to the free plan; no data is deleted automatically as part of that downgrade.
  • Tax (where applicable) is collected by Stripe based on your billing location and added on top of the listed price.

7. Availability and SLA

We work to keep Pingoru highly available, but we don't offer a contractual uptime SLA on any plan. The status-page polling cadence (currently ~60 seconds), the freshness guarantees, and the time-to-notification you see in marketing materials are best-effort targets, not promises.

We post live operational status at /health and rely on a third-party monitor for our own uptime tracking. If you have an incident or a performance question, write to [email protected].

8. Termination

By you

Delete your account from Settings → Account → Delete account or email us. Deletions are processed within 72 hours; backups containing residual data roll off within 30 days.

By us

We may suspend or terminate an account, with or without notice, if we have reasonable grounds to believe it has materially violated section 3 (acceptable use) or section 4 (API and MCP use), or if continued provision of the service exposes us or other users to legal, security, or operational risk. For non-egregious cases we'll typically reach out by email first.

If we terminate without cause (e.g. we discontinue the service or a particular plan), we'll provide reasonable notice and refund any unused, prepaid portion of your subscription.

9. Disclaimer of warranties

Pingoru is provided "as is" and "as available". To the maximum extent permitted by law, we disclaim all warranties, express or implied, including merchantability, fitness for a particular purpose, accuracy, and non-infringement. We do not guarantee that the service will be uninterrupted, error-free, or that the status data presented through it is complete or correct in every detail. Don't rely on Pingoru as the sole signal for safety- critical decisions; always cross-reference the upstream vendor's status page when making operational calls that have real consequences.

10. Limitation of liability

To the maximum extent permitted by law, our total aggregate liability arising out of or related to your use of Pingoru, on any theory of liability, is limited to the greater of (a) the amount you paid us for the service in the 12 months preceding the event giving rise to the claim, or (b) USD $100. We are not liable for any indirect, incidental, special, consequential, exemplary, or punitive damages, including lost profits, lost revenue, lost data, or business interruption, even if we've been advised of the possibility.

Some jurisdictions do not allow these limitations; in those jurisdictions the limits apply only to the extent the law allows.

11. Indemnification

You agree to defend and indemnify us against third-party claims arising out of (a) your violation of these terms, (b) your violation of any third party's rights, or (c) your misuse of the service in a way that causes us to incur costs or damages. This includes claims by a service provider whose status page you monitor, or whose data you redistribute in violation of section 4.

12. Governing law

These terms are governed by the laws of the Province of British Columbia, Canada, and the federal laws of Canada applicable therein, without regard to conflict-of-law principles. The parties agree to the exclusive jurisdiction of the courts of British Columbia for any dispute that cannot be resolved informally.

Nothing in this section deprives you of any mandatory consumer protections that apply in your country of residence.

13. Changes to these terms

We may update these terms from time to time. Material changes (anything that meaningfully affects your rights or obligations) will be announced by email to active account holders at least 14 days before they take effect. Minor clarifications and editorial fixes are published with an updated Effective date above. Continued use of the service after changes take effect constitutes acceptance.

14. Contact

Questions, concerns, or anything that needs a human: [email protected]. We aim to respond within 48 hours (business days only).