Data Ethics Policy
Effective date: September 22, 2026.
This page explains how jsonscraper approaches ethical public-data collection and responsible API usage.
1. Public-data only scope
Our products focus on public-data workflows. We do not intentionally provide private-account content or circumvent privacy controls. Customers do not need to provide social-platform credentials.
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.
11. Human impact and proportionality
Before launching a large data workflow, evaluate potential impact on people and communities. Prefer proportional collection scope and avoid building processes that can enable discrimination, harassment, or reputational harm.
12. Review process for sensitive projects
For higher-risk scenarios, teams should implement internal review checkpoints, document decision criteria, and ensure legal/compliance stakeholders are involved before production rollout.
13. Enforcement and restrictions
If we identify usage that conflicts with this policy, we may request remediation, limit traffic, suspend access, or terminate service for repeated or severe violations.
14. Contact and accountability
For ethics-related concerns or clarification requests, contact [email protected] or use Contacts. Include enough implementation context so we can provide actionable guidance.
Public Data
Public Data means information associated with accounts, content or resources that are designated or made available for public viewing by the relevant source service and that jsonscraper does not intentionally obtain by circumventing privacy settings or access restrictions applicable to private content.
Responsible service delivery
We prohibit abusive and unlawful use and support responsible privacy requests. We may use independent third-party infrastructure to provide API responses.
Acceptable Use Policy