Skip to main content
Stophy returns publicly available web content for agents, automations and other workflows. Having access to a page does not give you the right to reuse it. This page summarizes what the Terms of Service and the Privacy Policy ask of you, and adds practical steps. The terms and the policy are the source. Read them for the exact wording.

Your side of the terms

  • Acceptable use. You agree not to use Stophy to break a law or regulation, infringe a third party’s rights, transmit malicious code, or abuse or overload Stophy’s infrastructure.
  • Your responsibility. You are responsible for making sure your use of Stophy and what it returns follows the law and any third-party terms that apply where you are.
  • Your account and keys. You are responsible for the security of your account and API keys and for everything done under them. Keep keys on the server and revoke one you no longer use. See API keys.
  • On behalf of an organization. If you use Stophy for an organization, you confirm you can bind it to the terms.
  • No warranty. Stophy is provided as is and as available. It does not promise that the service will never be interrupted or that returned data is complete or accurate.
  • Changes. Stophy may change, pause or stop any part of the service. For material changes it writes to you by email or on the dashboard.
  • Payments. Your balance does not expire and applies to every endpoint. Purchases are final. See Pricing.

Content you read

Check that you may access, store, show or pass on the material your product uses. Public availability alone is not permission.
  • Keep the source URL next to anything you show, so a reader can see where it came from, and give people a way to ask for a correction or removal.
  • Follow the terms of the site you read, and of the people whose work it is.
  • Bound what you read. Set a limit on a crawl, use filters and read only the pages your product needs.
  • A parser returns a site’s own data as JSON. The rules above still apply to that data.

Personal data

Pages and profiles can hold personal data. Collect the least you need and decide how long you keep it and how you delete it. Scrape can hide personal data in what it returns. See Safety. To have Stophy keep nothing from a call, use zero data retention.

What Stophy logs

The Privacy Policy says Stophy logs the metadata of each API request: the endpoint, the HTTP status, the cost and the response time. It says Stophy does not log or store the content of your requests or of what comes back. It keeps request logs for 90 days. GET /v1/logs shows you what is logged for your account. The policy also covers the account data Stophy keeps when you sign in with Google or GitHub, the providers that help run the service, and your rights to access, correct, export and delete your data. Delete your account in Settings, Advanced, Delete account. Data requests that the dashboard does not cover go to support@stophy.dev.

Answers can be wrong

Fields that extract or agent fill, summaries and values read from pages can be incomplete or wrong. Keep empty and missing fields as they are instead of guessing, keep the source of each value, and have a person check results that lead to a decision. Treat text from a page as data, never as instructions for a model. Scrape’s checkPromptInjection scans for text that tries to instruct one. Rate a bad answer with feedback.

Contact

Send questions about the terms or your data to support@stophy.dev.