Acceptable Use Policy
Last updated August 2, 2026
Presagon reads public business pages so you can follow what your competitors ship. This policy sets the boundary: what counts as an acceptable source, what must never be done with the service, how we fetch pages, and what happens when someone crosses the line.
1. Scope
This policy forms part of the Terms of Service and applies to everyone who uses Presagon, including anyone you add to your workspace and any third-party client you authorise to read it. Terms defined in the Terms of Service have the same meaning here. A breach of this policy is a breach of that agreement.
2. What the service is for
Presagon monitors the public pages of businesses so that you can follow what they ship and what they charge. It is built for competitive awareness. It is not a general-purpose scraper, not a surveillance tool, and not a way to observe individual people.
3. Sources you may monitor
A source is acceptable if all of the following are true.
- (a)It is published on the open web and reachable without signing in, without a paid subscription, and without defeating any access control.
- (b)It is a business page rather than a page about a private individual: a changelog, release notes, a what's-new page, a product or pricing page, a company blog.
- (c)You are not subject to an agreement, undertaking, or instruction that forbids you from monitoring it.
- (d)Its operator has not asked you or us to stop.
Adding a source is a statement by you that it meets those conditions. We may refuse or remove any source at our discretion, including where an operator asks us to.
4. What you must not do
- (a)Point the service at anything behind authentication, a paywall, an IP allowlist, or any other access control, or at anything you have no right to access.
- (b)Use the service to build a profile of an individual, to monitor an individual's personal pages or social accounts, or to collect personal data about individuals rather than the published activity of businesses.
- (c)Use it to harass, stalk, defame, or discriminate against anyone, or in furtherance of any unlawful purpose.
- (d)Circumvent, or attempt to circumvent, a rate limit, plan limit, quota, or any other technical restriction, including by creating multiple accounts or workspaces to obtain more of the service than your plan provides.
- (e)Probe, scan, load-test, or otherwise interfere with the service or its infrastructure, or attempt to gain access to any account, workspace, or data that is not yours.
- (f)Upload or transmit malware, or use the service to distribute anything harmful.
- (g)Resell, sublicense, or redistribute the service or its output as a product or dataset of your own, or use it to build a competing product.
- (h)Reverse engineer, decompile, or attempt to extract the source code, prompts, or model configuration of the service, except so far as that restriction is unenforceable by law.
- (i)Misrepresent an insight as anything other than automatically generated interpretation, or present it as our advice or endorsement.
5. How we fetch pages
We request only publicly accessible pages, identify our requests honestly, and keep request rates conservative so that monitoring a site imposes a negligible load on it. We do not attempt to defeat access controls, bot protection, or rate limits at a source. If a source blocks us, we treat that as a decision to be respected rather than an obstacle to route around, and the watch will report that the source is unreachable.
6. Limits
Each plan carries limits on watched competitors, sources per competitor, visible history, daily interpretations, and delivery and export features. The limits in force are shown on the pricing page and enforced in the product. The daily interpretation limit is an abuse ceiling set well above normal use of a plan, not a usage target. We may queue, delay, or decline work that exceeds a limit.
7. Third-party clients
If you authorise an AI assistant or another client to read your workspace, you remain responsible for what it does with that access under this policy. Authorise only clients you trust, and revoke access you no longer need. We may suspend or revoke a client's access where we believe it is being used abusively or is putting the service or its customers at risk.
8. Security research
We welcome good-faith security research and will not pursue a researcher who reports a vulnerability responsibly. Test only against your own account and workspace, do not access, modify, or retain anyone else's data, do not degrade the service for others, and give us a reasonable chance to fix an issue before disclosing it. Report findings to security@presagon.com; the security overview has more detail.
9. Enforcement
Where we believe this policy is being breached we may remove a source, limit or suspend access, or terminate the account, in each case as set out in the Terms of Service. We will give notice and prefer the least disruptive step that resolves the problem, unless the circumstances call for immediate action. Suspension for breach does not entitle you to a refund of the period affected.
10. Reporting abuse
If you operate a site and believe Presagon is monitoring it in a way it should not, or if you believe someone is using the service in breach of this policy, email hello@presagon.com. Tell us the pages involved and we will investigate. We will honour a site operator's request to stop monitoring their pages.
Related: Terms of Service · Security Overview