Acceptable Use Policy

This policy applies to every customer account, collaborator, credential, automation, or integration that interacts with ScreenNabster—including API keys and embeddable access patterns.

Violation may result in throttling, feature removal, credential revocation, account suspension, or legal referral.

• Programmatic screenshots, renders, OG images, QA captures, dashboards, archiving, accessibility tooling—when lawful and compliant with target-site obligations.
• Security testing workflows limited to authorized systems and restrained request volume.
• Compliance with Privacy Policy disclosures about capture metadata and authenticated sessions.

• Malware, phishing, spoofing legitimate brands to harvest credentials or payment card data.
• Brute-force, credential stuffing, session hijacking, or bypass of authentication—not even “for testing” without proof of authorization.
• Attempted SSRF exploits, intrusion into RFC1918/metadata endpoints, scraping internal dashboards, bypassing quotas, or forging signed capture URLs.
• Large-scale volumetric denial-of-service against ScreenNabster, customers, or external sites.
• Harassment, stalking, or targeted surveillance inconsistent with privacy law.
• Activity violating sanctions, exporting controlled technology unlawfully, or supporting violent extremism.
• Mining regulated personal data via captures without lawful basis.
• Any use that knowingly violates contractual terms of target properties when those terms prohibit automated access.
• Hosting or distributing illicit content solely through renders when ScreenNabster becomes a conduit materially aiding that distribution.

We may classify traffic heuristically, consult threat intelligence feeds, review abuse tickets, cooperate with lawful process, preserve forensic records, alert payment partners, or publish aggregate statistics internally.

Technical mitigations—including IP blocks, WAF tuning, disabling bulk capture lanes, forcing review—do not waive other remedies.

Send abuse reports—including URLs showing misuse, offending API key prefixes where safe, timelines, logs, or law-enforcement referencing information—to support@screennabster.com.

Emergency security defects should route through Report a Security Issue instead of public channels.

• Terms of Service
• Privacy Policy
• Report a Security Issue