Back
Zinkly Zinkly

Acceptable Use Policy

Last updated 2026-09-04

Last updated: 25 August 2026

This Acceptable Use Policy sets out technical and behavioural rules for using Zinkly, alongside our Community Guidelines (which cover content). Violating this policy can result in feature restrictions, suspension, or termination.

You must not

  • Access or attempt to access Zinkly by any means other than the interfaces and APIs we provide, including scraping the site;
  • Use automated means (bots, scripts) to create accounts, post content, or interact with the platform, except via our official Developer API with a registered application and appropriate authorisation;
  • Circumvent, disable, or interfere with security features, rate limits, or moderation systems;
  • Attempt to gain unauthorised access to any account, system, or network connected to Zinkly;
  • Introduce malware, viruses, or harmful code;
  • Interfere with the proper functioning of Zinkly (e.g. denial-of-service, excessive automated requests);
  • Reverse-engineer or attempt to extract the source code of Zinkly's software, except as permitted by law;
  • Use Zinkly's Developer API in violation of its scopes, rate limits, or the permissions a user actually granted your application;
  • Resell, sublicense, or redistribute access to Zinkly without our written permission;
  • Misrepresent your identity, age, or affiliation.

Developer API-specific rules

If you build on Zinkly's Developer API ("Login via Zinkly" and REST API), you must: only request the OAuth scopes your application actually needs; clearly identify your application to users during the authorisation flow; keep client secrets confidential; respect users' choice to revoke your application's access at any time; and comply with our Terms, this policy, and applicable data-protection law for any Zinkly user data your application accesses.

Enforcement

We may suspend API access, restrict account features, or terminate accounts that violate this policy, following the same notice-and-appeal process described in our Content Moderation Policy where applicable.