Account and API access
You are responsible for information submitted through your account and for activity performed with credentials issued to you. API keys and admin tokens must not be shared publicly or used outside their intended scope.
These terms provide a clear baseline for account access, API credentials, acceptable use, service limits, and developer responsibilities.
You are responsible for information submitted through your account and for activity performed with credentials issued to you. API keys and admin tokens must not be shared publicly or used outside their intended scope.
You may not use the service to disrupt infrastructure, bypass access controls or rate limits, probe unrelated systems, automate abusive traffic, or use credentials that you are not authorized to possess.
Access plans may include monthly request quotas, rate limits, API-key limits, feature permissions, validity periods, and subscription pricing. API access requires an active subscription.
Some workflows may depend on third-party providers or media sources. Availability, accuracy, and continued access can depend on those providers and on rights applicable to the content or integration.
Features, endpoints, limits, data structures, and operational policies may evolve. Material changes should be communicated through documentation or the service interface when practical.
You must use reasonable care to protect credentials and account access. Revoke or rotate credentials promptly if you suspect compromise.
This template is intended as a practical publishing baseline and is not a substitute for jurisdiction-specific legal advice. Before commercial launch, have the final terms reviewed for your business model, content rights, location, and regulatory obligations.
Publishing baselineExplore how we handle your information, or reach out with a question about the platform.