Overview
This Acceptable Use Policy ("AUP" or "Policy") governs your use of the PageLantern service operated by PageLantern LLC, a Texas limited liability company, doing business as PageLantern ("PageLantern," "we," "us," and "our"). It is incorporated into, and forms part of, our Terms of Service. Capitalized terms not defined here have the meaning given in the Terms of Service. If you use PageLantern on behalf of an organization, you are responsible for that organization's compliance with this Policy. Violating this Policy may result in the actions described in the Enforcement section, up to suspension or termination.
1. Purpose and Acceptance
PageLantern is an operational monitoring tool for websites, APIs, domains, TLS certificates, DNS, ports, heartbeats, and related signals. This Policy sets the rules that keep that monitoring lawful, safe, and considerate of the systems and people it touches.
By creating an account or using the service, you agree to this Policy. If any provision conflicts with your local law, do not take any action that would be unlawful, and contact us at security@pagelantern.com if you are unsure whether an intended use is permitted.
3. Prohibited Uses
You must not use PageLantern, or allow anyone using your account to use PageLantern, to:
- Access, probe, scan, or test any system, network, or account without authorization, or to bypass authentication, access controls, technical restrictions, or rate limits unlawfully.
- Conduct or facilitate denial-of-service (DoS or DDoS) activity, load or stress testing, or any monitoring configuration intended or reasonably likely to degrade, overload, or disrupt a target you do not own or are not authorized to test at that intensity.
- Collect, inspect, store, or transmit personal, confidential, or regulated data without a valid legal basis, or process data belonging to other people or organizations that you are not authorized to process.
- Send alerts, summaries, incident notices, or webhook traffic to recipients you are not authorized to contact, or use the service as a marketing, bulk-email, or spam platform.
- Engage in unlawful scraping, surveillance, stalking, harassment, or the collection of information about individuals without a lawful basis.
- Distribute or point the service at malware, phishing, or other malicious content, or use monitoring artifacts (such as screenshots or captured responses) to further an attack.
- Infringe intellectual property rights, misappropriate trade secrets, or violate privacy, publicity, export-control, or sanctions laws.
- Interfere with, disrupt, or attempt to gain unauthorized access to the PageLantern service, other customers' accounts or data, or the infrastructure that runs the service.
- Resell, sublicense, or provide the service to third parties except as expressly permitted by your plan and the Terms of Service, or evade plan limits, quotas, or fair-use controls through multiple accounts or automated means.
- Use the service for any activity that is illegal, that promotes illegal activity, or that is intended to harm us, our users, the systems you monitor, or the public.
4. Monitoring Conduct and Third-Party Targets
Because PageLantern issues requests to the targets you configure, you are responsible for the volume, frequency, and nature of that traffic. Configure check intervals, timeouts, and browser checks responsibly, and do not use short intervals, parallel monitors, or repeated ad-hoc runs to generate abusive load against any target.
You must not use PageLantern to reach internal-only, private, loopback, link-local, or cloud-metadata addresses of infrastructure you are not authorized to test, or to pivot into networks that are not your own. Our probe safeguards are a protective measure, not a license to attempt such access.
If a target's operator asks you to stop monitoring, or if monitoring would breach that target's terms, you must stop. Monitoring third-party services you merely depend on (for example, an upstream provider) is permitted only where that provider allows it.
5. Alerts, Email, and Webhooks
PageLantern sends operational notifications to the destinations you configure. You are responsible for obtaining any consent, authority, or lawful basis needed to contact those recipients, and for ensuring status-page subscribers, email recipients, and webhook endpoints are ones you are permitted to contact.
You must not use alerts, digests, status-page notifications, or webhooks to deliver unsolicited bulk messages, marketing, or other content unrelated to the monitoring you have configured.
6. Accounts, Credentials, and Fair Use
You must protect your account credentials, API keys, integration secrets, and configured destinations. Actions taken with your keys are treated as authorized by you until the key is revoked. Notify us promptly at security@pagelantern.com if you believe a credential or destination has been compromised.
You must not attempt to circumvent quotas, entitlements, or fair-use limits, and you must not use automated means to place abusive load on the service or to interfere with other customers' use of it.
7. Content and Data
You are responsible for the monitor configurations, request headers, request bodies, environment variables, destination addresses, webhooks, response checks, and any content or excerpts you submit or cause PageLantern to process. You represent that you have the rights and permissions necessary for PageLantern to process that data on your behalf.
Do not submit content that is unlawful, infringing, or that contains other people's personal or confidential data without a lawful basis. Do not intentionally cause the service to capture credentials or secrets belonging to systems you are not authorized to access.
8. Security Testing
Unauthorized security testing of the PageLantern service is prohibited by this Policy. Good-faith security research on PageLantern's own systems is welcome and is governed separately by our Security Policy and Vulnerability Disclosure Policy, which describes the scope, rules of engagement, and legal safe harbor for that research. Nothing in this Policy authorizes you to test systems that belong to other people or organizations.
9. Enforcement and Reporting Abuse
We may investigate suspected violations of this Policy and may take any action we consider appropriate, including warning you, throttling or rate-limiting activity, disabling specific monitors or destinations, suspending or terminating accounts, removing content, and cooperating with law enforcement. Where necessary to protect the service, third parties, or legal compliance, we may act without prior notice.
If you become aware of misuse of PageLantern, or of monitoring or alerts you believe are abusive or unauthorized, report it to security@pagelantern.com with enough detail for us to investigate.
10. Changes to This Policy
We may update this Policy prospectively. Material changes will be reflected by updating the date on this page and providing reasonable notice through the service. Your continued use of PageLantern after a change takes effect means you accept the updated Policy.
11. Contact and Related Policies
Use the details below to report abuse or to ask whether an intended use is permitted. This Policy should be read together with the related policies listed here.
- Report abuse or misuse
- security@pagelantern.com
- Terms of Service
- pagelantern.com/terms
- Privacy Notice
- pagelantern.com/privacy
- Security Policy
- pagelantern.com/security-policy
Abuse reports and acceptable-use questions can also be sent to abuse@pagelantern.com. Our postal address is PO Box 340351, Lakeway, TX 78734.
Important Note
We apply this Policy using judgment rather than mechanically. Where a violation looks accidental or is quickly corrected, we will normally raise it with you before taking any action that interrupts your monitoring. Where it is deliberate, is causing harm to a third party, or puts the service or other customers at risk, we will act first and explain afterwards. Nothing in this Policy limits any right or remedy we have under the Terms of Service or applicable law, and a decision not to enforce a provision on one occasion is not a waiver of it.
