API Rate Limits & Fair Use Policy

Effective Date: 2026

Last Updated: 2026

This API Rate Limits & Fair Use Policy explains how Playflick™ Media .ltd may manage API usage, developer access, request limits, fair use, automation, scraping, integrations, app access, abuse prevention, security controls, and system protection for Playflick.com.

This policy should be read together with our Terms of Service, API & Developer Terms, Privacy Policy, Security Policy & Responsible Disclosure, Anti-Spam & Platform Manipulation Policy, User Generated Content Policy, External Links Policy, Embed Policy, Platform Availability & Service Changes Policy, and Data Retention Policy.


1. Who We Are

Operator: Playflick™ Media .ltd

Website: https://playflick.com

Business Address:
41 Norman Avenue
London
N22 5ES
United Kingdom

Developer Contact Email: hello@playflick.com
Contact Page: https://playflick.com/contact-us


2. Purpose of This Policy

Playflick may provide APIs, developer tools, app integrations, widgets, embeds, tokens, webhooks, mobile app connections, or other technical interfaces. These tools must be used responsibly.

Rate limits and fair use rules help protect:

  • Platform stability
  • User privacy
  • Account security
  • Creator content
  • Payment and payout systems
  • Advertising systems
  • Search and recommendation systems
  • Playflick infrastructure
  • Other users and developers

3. What Counts as API or Developer Use?

API or developer use may include accessing, sending, receiving, automating, integrating, embedding, syncing, or processing Playflick data or services through technical methods.

This may include:

  • Official Playflick APIs
  • Developer apps
  • Access tokens
  • API keys
  • Webhooks
  • Embeds
  • Mobile app integrations
  • Third-party integrations
  • Automated uploads where permitted
  • Automated account or content management tools where permitted
  • Analytics integrations where permitted
  • Advertising or campaign integrations where permitted

4. Fair Use Requirement

Developers and users must use Playflick APIs and technical systems fairly, lawfully, securely, and in a way that does not harm Playflick, users, creators, advertisers, payment systems, or platform performance.

Fair use means you must not:

  • Overload Playflick systems
  • Bypass rate limits
  • Scrape data without permission
  • Harvest personal data
  • Create fake engagement
  • Automate spam
  • Bypass privacy settings
  • Bypass paid content restrictions
  • Bypass age restrictions
  • Bypass security controls
  • Use APIs for malware, phishing, fraud, or abuse

5. Rate Limits

Playflick may apply rate limits to API requests, developer tools, embeds, webhooks, login attempts, uploads, comments, search requests, analytics requests, advertising requests, or other technical activity.

Rate limits may be based on:

  • API key
  • Access token
  • App ID
  • User account
  • IP address
  • Device
  • Endpoint
  • Request type
  • Account status
  • Developer status
  • Security risk
  • Platform load

Playflick may change rate limits at any time for security, performance, abuse prevention, legal, technical, or business reasons.


6. No Right to Unlimited Access

API access is not unlimited unless Playflick expressly states otherwise in writing.

Playflick may limit, throttle, delay, reject, queue, suspend, or block API requests where needed to protect the platform or enforce this policy.


7. Prohibited Rate Limit Evasion

You must not attempt to bypass or evade API limits.

Prohibited evasion includes:

  • Rotating API keys to avoid limits
  • Rotating accounts to avoid limits
  • Rotating IP addresses to avoid limits
  • Using proxies, VPNs, botnets, or distributed systems to bypass controls
  • Splitting traffic across multiple apps to hide usage
  • Creating duplicate developer accounts
  • Using stolen, leaked, shared, or unauthorised tokens
  • Ignoring retry instructions or error responses
  • Reverse engineering private endpoints

8. API Keys and Tokens

API keys, access tokens, refresh tokens, secrets, webhook secrets, and developer credentials must be kept secure.

You must not:

  • Share API secrets publicly
  • Commit API keys to public repositories
  • Expose tokens in client-side code where unsafe
  • Sell, rent, or transfer API access without permission
  • Use someone else’s API key without permission
  • Use leaked, stolen, or compromised credentials
  • Continue using credentials after access has been revoked

If you believe an API key or token has been compromised, you should rotate or revoke it immediately where possible and contact Playflick if needed.


9. Scraping and Data Harvesting

You must not scrape, crawl, harvest, copy, archive, mass-download, or extract Playflick data without permission.

Prohibited scraping may include collecting:

  • User profiles
  • Email addresses
  • Comments
  • Videos
  • Thumbnails
  • Creator data
  • Analytics data
  • Search results
  • Recommendations
  • Private or restricted content
  • Paid content
  • API responses at scale beyond permitted use

Public availability of content does not mean it may be scraped, copied, trained on, sold, republished, or reused without permission.


10. Automation Rules

Automation may be allowed only where Playflick expressly permits it and where it follows all applicable rules, rate limits, permissions, and user consent requirements.

You must not automate:

  • Fake views
  • Fake likes
  • Fake comments
  • Fake subscribers
  • Fake shares
  • Fake reports
  • Spam uploads
  • Mass account creation
  • Ad clicks or ad impressions
  • Paid content access abuse
  • Credential testing
  • Security probing outside responsible disclosure rules

11. Upload and Content API Use

If Playflick provides upload, content management, or creator API tools, you must use them responsibly.

You must not use API tools to:

  • Mass-upload spam
  • Upload illegal or infringing content
  • Bypass moderation
  • Bypass upload limits
  • Bypass file type or file size restrictions
  • Upload malware or harmful files
  • Generate duplicate or low-quality content at scale
  • Mislead users with automated metadata

12. Privacy and User Consent

Developers must respect user privacy and obtain any required consent before accessing, processing, storing, sharing, or displaying user data.

Developers must not:

  • Collect more data than necessary
  • Use user data for undisclosed purposes
  • Sell user data without lawful authority
  • Share user data with unauthorised third parties
  • Bypass privacy settings
  • Attempt to identify users from aggregated data where not permitted
  • Store data longer than necessary
  • Ignore deletion, revocation, or access removal requests where applicable

13. Paid Content, Subscriptions, and Access Controls

APIs and developer tools must not be used to bypass paid content, rentals, subscriptions, memberships, wallet features, creator paywalls, age restrictions, geographic restrictions, or account restrictions.

You must not use technical tools to:

  • Access paid content without payment
  • Share subscriber-only content with unauthorised users
  • Bypass rental windows
  • Extract direct video files
  • Copy or redistribute paid videos
  • Bypass creator download settings
  • Interfere with payment, billing, or access systems

14. Advertising API and Campaign Use

If advertising tools or campaign APIs are available, advertisers and developers must use them honestly and lawfully.

You must not use advertising integrations to:

  • Create misleading campaigns
  • Generate fake impressions or clicks
  • Bypass ad review
  • Promote prohibited products or services
  • Use hidden redirects or cloaking
  • Target users unlawfully
  • Collect personal data without required consent
  • Manipulate campaign performance or billing

15. Security Testing

Security testing must follow Playflick’s Security Policy & Responsible Disclosure.

API access must not be used for unauthorised security testing, exploitation, vulnerability scanning, credential attacks, denial-of-service testing, data extraction, or attempts to access non-public systems.

Responsible security reports should be submitted through the appropriate contact route and should avoid harm to users, data, creators, advertisers, or Playflick systems.


16. Caching and Storage

Developers may cache or store Playflick data only where permitted and only for as long as necessary for the authorised purpose.

Playflick may require developers to delete, refresh, update, or stop using stored data where:

  • User consent is withdrawn
  • Account access is revoked
  • Content is deleted
  • Content is restricted
  • A rights complaint is received
  • API access is terminated
  • Data is outdated or inaccurate
  • Legal or privacy requirements apply

17. AI Training and Dataset Restrictions

You must not use Playflick APIs, embeds, content, metadata, comments, profiles, transcripts, subtitles, thumbnails, audio, or video data to train, fine-tune, test, evaluate, or build AI systems without appropriate permission.

This includes AI systems for:

  • Video generation
  • Voice cloning
  • Image generation
  • Recommendation models
  • Facial recognition
  • Creator profiling
  • Sentiment analysis at scale
  • Automated scraping datasets
  • Large language models

18. Monitoring and Enforcement

Playflick may monitor API usage, developer activity, request patterns, error rates, abuse signals, security signals, token activity, upload behaviour, and integration behaviour to protect the platform.

Enforcement may include:

  • Rate limiting
  • Request throttling
  • Temporary blocking
  • API key suspension
  • Token revocation
  • Developer account suspension
  • App removal
  • Endpoint restriction
  • Data access reduction
  • Account suspension or termination
  • Legal action where appropriate

19. Emergency Restrictions

Playflick may immediately restrict, block, or disable API access without advance notice where necessary to protect users, creators, advertisers, payment systems, infrastructure, security, data, or legal compliance.

Emergency restrictions may apply where there is:

  • Security risk
  • Data breach risk
  • System overload
  • Spam or bot activity
  • Payment or payout fraud
  • Scraping or mass extraction
  • Copyright or legal emergency
  • Child-safety risk
  • Platform integrity risk

20. Appeals and Reviews

If your API access, developer app, token, integration, or account was restricted and you believe Playflick made a mistake, you may request a review under our Appeals Policy.

Contact:

Email: hello@playflick.com

Please include:

  • Your account email
  • Your developer app name or integration name
  • The API key or app reference, without exposing secrets publicly
  • The decision you are appealing
  • Why you believe the decision was incorrect
  • Any logs, timestamps, request IDs, or supporting technical context

21. No Service Level Guarantee

API access is provided subject to availability and may change over time.

Playflick does not guarantee that APIs, endpoints, rate limits, data fields, webhooks, tokens, embeds, integrations, or developer tools will always be available, uninterrupted, error-free, backwards compatible, or supported forever.


22. Changes to This Policy

We may update this API Rate Limits & Fair Use Policy from time to time.

Changes may reflect new API features, developer tools, abuse patterns, security needs, privacy requirements, platform changes, legal requirements, business decisions, or technical updates.

Your continued use of Playflick APIs, developer tools, embeds, or integrations after changes become effective means you agree to the updated policy.


23. Contact Us

For API access questions, rate limit issues, developer account concerns, integration problems, security reports, appeals, or policy enquiries, contact:

Playflick™ Media .ltd
41 Norman Avenue
London
N22 5ES
United Kingdom

Developer Contact Email: hello@playflick.com
Contact Page: https://playflick.com/contact-us
Website: https://playflick.com


24. Footer Notice

© 2026 Playflick™ Media .ltd. All rights reserved.
Playflick™ is a trademark of Playflick™ Media .ltd.