Data Ethics Policy
Effective date: March 5, 2026.
This page explains how jsonscraper approaches ethical public-data collection and responsible API usage.
1. Public-data only scope
Our products are designed for collecting publicly accessible information only. We do not offer features intended to bypass private account visibility, authentication controls, or paywalls.
2. Responsible access approach
Collection workflows must use reasonable request patterns, respect technical limits, and avoid harmful load on source platforms. We recommend caching, retries, and backoff instead of aggressive polling.
3. Compliance-first usage
Customers are responsible for using data in compliance with applicable laws, platform terms, and internal governance policies in their jurisdiction.
4. No deceptive collection
Use cases involving impersonation, identity fraud, social engineering, or unauthorized access attempts are prohibited.
5. Sensitive data caution
Do not use the service to target sensitive personal data categories or to build workflows that can harm individuals or protected groups.
6. Data minimization
Collect only what is necessary for your use case. Keep retention windows short and remove data that no longer serves a legitimate business purpose.
7. Internal controls
Teams should implement role-based access control, key management, request logging, and approval processes for high-impact data projects.
8. Abuse monitoring
We may investigate suspicious traffic patterns and restrict service access where abuse, legal risk, or platform safety concerns are identified.
9. AI and automation guardrails
If you use AI agents, validate outputs and enforce policy constraints before automated downstream actions.
10. Questions and escalation
If you need a compliance review of a workflow, contact us via the Contacts page or site chat before scaling.