Testlie

Acceptable use policy

Effective 17 October 2026

This policy describes what you may and may not do with Testlie (the "Service"), provided by Carrier Grade Inc.. It is part of our terms of service and applies to everyone who uses the Service, including people you invite and systems that use your credentials. Words defined in the terms have the same meaning here.

Testlie exists so teams can test what their applications send and how they sign users in, without reaching real people. Use it for that, with test data, and you will not run into this policy.

1. No spam, phishing or malware

You must not use the Service to create, store, host, send, forward or distribute:

  • unsolicited bulk or commercial messages (spam), or content intended to promote spam;
  • phishing pages or messages, or anything designed to trick people into revealing passwords, one-time codes, payment details or other personal data;
  • malware, viruses, ransomware, cryptominers or other harmful code, other than inert test samples clearly used to test your own security controls;
  • links to any of the above.

This includes request bin responses, mock identity provider login pages and anything else the Service serves on your behalf.

2. No relaying to real recipients

The Service is not an email, SMS, WhatsApp, push or voice delivery service. You must not:

  • try to use any sandbox to deliver messages, notifications or calls to real people, phone numbers, devices or carriers;
  • use forwarding to send mail to people who have not asked for it, or to get around the requirement that forwarding addresses confirm by email;
  • use webhooks, inbound deliveries, SCIM runs, voice callbacks or request bins to send messages or requests to systems you do not own or are not authorised to test;
  • use inbound addresses, bins or other public endpoints to collect messages from people who do not know they are writing to a test service.

3. No impersonation beyond testing

Mock identity providers, including the Google, GitHub, Apple and Microsoft social sign-in presets, imitate real login screens so that you can test your own application's sign-in. You may use them only for that purpose. You must not:

  • show a mock login page, request bin page or captured message to anyone who might mistake it for the real provider, or use it to collect real credentials;
  • use the Service to impersonate a real person, company or brand, other than your own organisation and the providers whose interfaces you are testing your integration with;
  • use mock identity providers to sign real users in to production systems, or to protect production data.

4. No abuse of the Service

You must not:

  • load test, stress test or benchmark the Service, or send traffic far beyond what your tests need, without our prior written agreement;
  • attack, probe, scan or test the security of the Service except under the responsible disclosure rules on our security page;
  • interfere with or disrupt the Service, its infrastructure or other customers, or try to access another team's data;
  • circumvent plan limits, rate limits, quotas or access controls, including by creating multiple accounts or teams to multiply free allowances or trials;
  • use the Service's servers as a proxy, an open relay, or to make requests to third parties that you are not authorised to make;
  • resell the Service or provide it to third parties as a hosted service, unless we have agreed to this in writing.

5. No unlawful or harmful content

You must not use the Service to store, process or transmit content or data that:

  • is illegal, or that you have no right to process, including content that infringes intellectual property or privacy rights;
  • sexually exploits or endangers children, promotes terrorism or violent extremism, or harasses, threatens or incites violence against anyone;
  • is obtained or used in breach of export control or sanctions laws.

We recommend that you do not put real customers' personal data, payment card data or health data into the Service at all; it is a test environment.

6. Rate limits and fair use

Every plan has limits on messages, requests, inboxes and sandboxes, and the Service applies rate limits to sign-in, SMTP and SMPP connections, failed logins and selected API operations to protect the Service and other customers. When you reach a limit, the Service refuses further requests with an error; it does not queue them. Limits may change as we protect the Service. If you need higher limits for legitimate testing, contact hello@testlie.com.

7. Reporting abuse

If you believe someone is using Testlie in breach of this policy, for example a phishing page served from one of our domains, email abuse@testlie.com with the URL or message and any details you have. Report security vulnerabilities to security@testlie.com as described on our security page.

8. Enforcement

We may investigate suspected breaches of this policy. If we believe this policy has been breached, we may, at our discretion and without liability:

  • remove or disable access to the content concerned, such as a request bin, a mock identity provider or a forwarding rule;
  • rate limit, suspend or close the account or team involved, immediately where the breach is serious or puts the Service or others at risk;
  • report the matter to law enforcement or other authorities, and cooperate with them as the law requires.

Where practical we will tell you what we found and give you a chance to fix it. Fees are not refunded for suspensions or terminations caused by a breach of this policy. We may update this policy as described in the terms of service.