This site uses cookies for analytics and to improve your experience. By clicking Accept, you consent to our use of cookies. Learn more in our privacy policy.

LEGAL

Acceptable Use Policy

This policy sets out how PingMyThing may and may not be used. It is intended to protect the Service, other users, and the integrity of PMT’s signal model.

Last updated: 9 June 2026

This Acceptable Use Policy (“AUP”) applies to your use of PingMyThing (“PMT” or the “Service”), operated by Roy K Hills trading as Sendacom UK (“we”, “us” or “our”).

This AUP forms part of, and should be read together with, our Terms of Service and Privacy Policy. By using PMT, you agree to comply with this AUP.

1. Purpose of this policy

PMT is a lightweight signal ingestion and visibility service. It accepts small signals from checks, scripts, jobs, applications, websites, devices and operational processes, and makes selected received states visible where possible.

This policy exists to protect the Service, other users, and the integrity of PMT’s signal model. PMT is designed for selected operational signals. It is not designed for bulk telemetry, log storage, remote control, system discovery, compliance archiving, or safety-critical use.

2. Intended use

You may use PMT to send and view selected operational signals, provided that your use is lawful, authorised, reasonable, and consistent with your service plan.

You are responsible for:

  • deciding what each signal means;
  • ensuring that your scripts, checks, systems and devices send correct signals;
  • choosing a suitable signal cadence;
  • monitoring signal freshness and absence where relevant;
  • keeping independent controls for critical systems;
  • ensuring that you have the right to send any data submitted to PMT.

PMT must not be used as your sole mechanism for detecting, preventing, proving or responding to failure.

3. Prohibited use

You must not use PMT to:

  • break the law or assist unlawful activity;
  • send, store or transmit material that is unlawful, harmful, malicious or unauthorised;
  • interfere with, disrupt, overload or degrade PMT or its infrastructure;
  • attempt to gain unauthorised access to PMT, other user accounts, tokens, projects, data, systems or infrastructure;
  • probe, scan, penetration test, load test, stress test or benchmark the Service without our prior written consent;
  • introduce malware, exploit payloads, hostile code or intentionally malformed data;
  • bypass, avoid or undermine authentication, token controls, PIN checks, rate limits, usage limits or security controls;
  • use PMT for bulk log ingestion, broad telemetry collection, scraping, data harvesting or high-volume metric streaming unless this has been expressly agreed;
  • impersonate another person or organisation;
  • resell, sublicense or share access to the Service unless your plan or written agreement allows it;
  • use PMT in safety-critical, life-critical, emergency-response, financial transaction validation, legal evidence, compliance archive or regulatory recordkeeping contexts where guaranteed accuracy, completeness or delivery is required.

4. Data and payload restrictions

PMT is designed for small operational signals, not rich data storage.

You must not send:

  • passwords, API keys, private keys, access credentials or authentication secrets;
  • confidential file contents, logs, messages or documents;
  • payment card data or financial transaction records;
  • medical, health, biometric or other highly sensitive personal data;
  • personal data that is unnecessary for the signal purpose;
  • precise location data unless your token and use case allow it and you have the right to send it.

Station names, tags, signal labels and values should be kept minimal. Use opaque identifiers where practical. Do not place sensitive customer, user, system or security information in PMT payload fields unless appropriate safeguards are in place and your use is authorised.

5. Credentials and access control

You are responsible for protecting all PMT credentials and access mechanisms, including tokens, PINs, magic links, exported configuration files, API URLs and any other access details.

You must not:

  • publish tokens, PINs or access links in public repositories, public websites, screenshots, documentation, client-side code or support tickets;
  • share credentials with people who do not need access;
  • use shared credentials where individual or scoped access is required;
  • continue using credentials that you know or suspect have been exposed.

If you believe a token, PIN or access link has been lost, disclosed, copied or misused, you must revoke or rotate it where possible and notify us promptly where there is a material risk.

Subject to our Terms of Service and applicable law, you are responsible for activity carried out using your credentials, including activity caused by your failure to secure them.

6. Fair usage and service limits

You must keep your use within the limits of your plan and within reasonable operational use of the Service.

You must not generate excessive traffic, excessive API calls, excessive data volume, repeated failed authentication attempts, or automated request patterns that place an unreasonable burden on the Service or other users.

Where we consider usage to be excessive, abusive, unsafe, inconsistent with the intended use of PMT, or harmful to the Service, we may take action including:

  • rejecting requests;
  • rate-limiting or throttling traffic;
  • limiting features or access;
  • suspending or revoking tokens;
  • suspending or terminating an account;
  • requiring a plan change or written agreement before use continues.

Additional charges will only apply where they are set out in your plan, order, agreement or applicable terms.

7. Security testing and vulnerability reports

You must not perform security testing, vulnerability scanning, penetration testing, automated probing or load testing against PMT without prior written permission.

If you believe you have found a security issue, please report it to us without exploiting it, accessing data that is not yours, disrupting the Service, or disclosing the issue publicly before we have had a reasonable opportunity to investigate.

8. Monitoring and enforcement

We may monitor use of the Service for security, abuse prevention, operational integrity, billing, troubleshooting and enforcement of this AUP. This may include request volumes, request rates, authentication failures, token usage patterns, source information, payload characteristics and system logs.

If we believe this AUP has been breached, or that continued access may harm PMT, other users, or the integrity of the Service, we may take corrective action with or without notice, depending on the urgency and severity of the issue.

Our response may include warning, throttling, request rejection, token revocation, account suspension, termination, or legal action where appropriate.

9. Changes to this policy

We may update this AUP from time to time. Changes are effective when posted on our website unless stated otherwise. Continued use of PMT after changes are posted means you accept the updated AUP.

10. Contact

Questions about this AUP should be sent to:

Email: info@pingmything.com
Registered Address: Sendacom, Unit A, 82 James Carter Road, Mildenhall, IP28 7DE, UK