Legal
Public legal documents and compliance posture
SmartAPIs.net is built with legality, attribution, privacy filtering, and commercial-use review as release gates. These public pages are the launch-facing legal documents for the product and should be reviewed with counsel before broad paid availability.
Terms of Service
Account rules, acceptable use, anti-mirroring restrictions, billing posture, and the product limitations customers agree to when using SmartAPIs.net.
Read Terms of ServicePrivacy Policy
What account, operational, and security data SmartAPIs.net collects, why it is used, and how billing and infrastructure providers fit into the data flow.
Read Privacy PolicyAPI Data Usage License
The rules that let customers build on SmartAPIs.net while blocking mirror APIs, raw dataset resale, broad harvesting, and unlicensed model-training use.
Read API Data Usage LicenseCookie Policy
Current cookie posture, essential-cookie limits, and the conditions under which a consent banner becomes mandatory.
Read Cookie PolicyCore legal operating rules
- Only datasets that clear commercial-use and redistribution review can ship.
- Source attribution must stay intact wherever source licenses require it.
- Personal data should be filtered out unless there is a reviewed basis to keep it.
- Public developer discovery should not hide where the product is available.
- Paid fees are generally non-refundable once access is provisioned, except where required by law or approved for billing error, fraud, or material service failure.
Where legality appears in the product
- `GET /v1/attribution` exposes publisher and license metadata.
- `GET /v1/legal/datasets` exposes reviewed dataset records.
- Module payloads carry source and review metadata alongside usable data.
- Entitlements, quotas, and audit trails support contractual enforcement.