API Data Use, Caching & Attribution Policy

Effective Date: 2026

Last Updated: 2026

This API Data Use, Caching & Attribution Policy explains how developers, partners, businesses, creators, applications, websites, tools, integrations, and third-party services may access, use, display, cache, store, refresh, attribute, delete, and protect data obtained through Playflick APIs, widgets, feeds, exports, developer tools, or approved integrations on Playflick.com, operated by Playflick™ Media .ltd.

This policy should be read together with our Terms of Service, Privacy Policy, API & Developer Terms, API Keys, Webhooks & Developer Security Policy, Data Retention Policy, Cookie Policy, Third-Party Services Policy, Content Licensing & Distribution Policy, and Account Suspension & Termination Policy.

1. Who We Are

Operator: Playflick™ Media .ltd

Website: https://playflick.com

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

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

2. Purpose of This Policy

Playflick may provide API data, metadata, user-authorised data, content information, creator information, analytics, availability data, media links, or other platform data through developer tools. Developers must use this data responsibly and lawfully.

This policy explains:

How API data may be used
How caching and refreshing API data may work
What attribution may be required
How stale, incorrect, or removed data should be handled
How user data must be protected
What misuse of Playflick API data is prohibited

3. Feature Availability

API data access, metadata feeds, caching permissions, attribution tools, data export tools, deletion callbacks, refresh endpoints, analytics access, partner data feeds, and related developer features may not be available to every user, country, account type, creator, business, partner, plan, application, or integration.

Playflick may add, remove, restrict, redesign, suspend, or discontinue API data access, caching permissions, attribution requirements, or developer data features at any time.

4. Types of API Data

Playflick APIs or approved integrations may provide different types of data where available.

API data may include:

Title metadata
Series, season, and episode metadata
Trailer and video metadata
Creator or channel information
Person pages and filmography data
Availability and release information
Review, rating, or ranking data
User-authorised account data
Analytics or performance data where permitted
Webhook event data

5. Permitted Use

Developers may use Playflick API data only for approved, lawful, secure, and policy-compliant purposes.

Permitted uses may include:

Displaying Playflick title metadata
Building approved creator tools
Powering approved widgets or embeds
Supporting user-authorised integrations
Synchronising permitted account data
Displaying availability information
Providing analytics dashboards where authorised
Building accessibility, discovery, or workflow tools where permitted

6. Prohibited Use

Developers must not misuse Playflick API data.

Prohibited uses may include:

Building a competing database by bulk copying Playflick data without permission
Scraping or storing data beyond permitted access
Selling Playflick data without permission
Using API data for spam, phishing, scams, or fraud
Using user data without valid permission
Using data to harass, profile, or target people unlawfully
Using data to bypass Playflick restrictions
Combining data in ways that violate privacy or applicable law

7. Caching API Data

Developers may be allowed to cache API data where permitted by Playflick documentation, API terms, response headers, or written approval.

Caching may be limited by:

Data type
Cache duration
API endpoint
User consent
Rights restrictions
Privacy requirements
Attribution requirements
Deletion or refresh requirements

Developers must not cache data longer than permitted.

8. Refreshing Cached Data

Developers should refresh cached Playflick data at reasonable intervals and according to applicable documentation, headers, or developer terms.

Cached data may become stale because of:

Title metadata updates
Rights or availability changes
Creator edits
Content removals
Privacy changes
Account restrictions
Review or rating changes
Legal or safety requirements

9. Stale or Incorrect Data

Developers are responsible for handling stale, incorrect, expired, removed, or changed Playflick data appropriately.

Developers should not present outdated data as current where doing so would mislead users.

Playflick may require developers to refresh, correct, hide, delete, or stop displaying data that has changed or is no longer permitted for use.

10. Removed or Restricted Data

If content, metadata, user data, creator data, or API data is removed or restricted by Playflick, developers may be required to stop displaying or storing it.

Removal or restriction may happen because of:

Privacy requests
Copyright or trademark complaints
Content removal
Account deletion
Rights expiry
Safety concerns
Legal requirements
Policy violations

11. Attribution

Playflick may require attribution when API data, widgets, embeds, metadata, ratings, rankings, images, or other platform data is displayed.

Attribution may include:

Playflick name
Playflick logo where permitted
Links back to Playflick pages
Creator attribution
Rights holder attribution
Data source labels
Powered by Playflick notices

Developers must not remove, hide, alter, or misrepresent required attribution.

12. Branding Rules

Developers must follow Playflick branding requirements when using Playflick names, logos, marks, badges, screenshots, widgets, or attribution labels.

Developers must not:

Imply partnership without permission
Imply endorsement without permission
Use fake Playflick branding
Alter Playflick marks misleadingly
Use branding for scams or phishing
Confuse users about who operates the application

13. User-Authorised Data

Some API data may be available only with user permission or account authorisation.

Developers using user-authorised data must:

Request only necessary access
Use data only for authorised purposes
Provide clear explanations where required
Respect user revocation
Delete or stop using data when required
Protect user data with reasonable security
Comply with privacy and data protection laws

14. Personal Data and Privacy

Developers must handle personal data lawfully, fairly, securely, and transparently.

Developers must not:

Collect unnecessary personal data
Sell personal data without lawful basis
Use data for unrelated purposes
Expose private account information
Share user data with unauthorised third parties
Use data for unlawful profiling or discrimination
Ignore deletion or access requests where legally required

15. Analytics Data

Analytics or performance data may be confidential, delayed, estimated, rounded, filtered, aggregated, or subject to access restrictions.

Developers must not misrepresent analytics data, publish private analytics without permission, or use analytics data to mislead advertisers, sponsors, investors, creators, or users.

More information is available in our Creator Analytics & Performance Metrics Policy.

16. Media Assets

API access to posters, thumbnails, stills, trailers, artwork, profile images, subtitles, captions, audio, or video assets may be subject to additional rights, caching, display, and attribution limits.

Developers must not download, store, modify, redistribute, or reuse media assets beyond permitted access.

Hotlink protection, signed URLs, or media access controls must not be bypassed.

17. Data Combination and Enrichment

Developers must be careful when combining Playflick data with third-party data, scraped data, public records, advertising data, social media data, or user-generated data.

Data combination must not:

Violate privacy rights
Create misleading profiles
Expose private information
Misrepresent Playflick data
Evade API restrictions
Support harassment, discrimination, or fraud

18. Data Deletion and Revocation

Developers may be required to delete, anonymise, refresh, or stop using Playflick data when access is revoked, authorisation ends, content is removed, a user deletes an account, a privacy request applies, or Playflick instructs deletion.

Developers should maintain processes to honour deletion and revocation requirements promptly.

19. Bulk Export and Replication

Developers must not bulk export, replicate, mirror, or rebuild substantial parts of Playflick’s database, metadata, content catalogue, user data, analytics, or creator data unless expressly permitted in writing.

Rate limits, pagination, API access, or public availability do not grant permission to create an unauthorised copy of Playflick data.

20. Machine Learning and AI Use

Developers must not use Playflick API data to train, fine-tune, evaluate, or operate machine learning models, AI systems, recommender systems, scraping tools, facial recognition systems, profiling systems, or automated decision systems unless permitted by Playflick and lawful for the data involved.

Developers must not use Playflick data to create harmful, deceptive, privacy-invasive, or rights-violating AI systems.

21. Child Safety

API data, cached data, developer tools, exports, and integrations must not be used to exploit, sexualise, identify, harass, groom, manipulate, or endanger children or young users.

Developers must not use Playflick data to expose child data unlawfully, bypass child-safety controls, or build tools that facilitate unsafe contact with children.

Serious child-safety concerns may result in immediate access restriction and reporting where appropriate or required.

22. Data Security

Developers must protect API data using reasonable security measures appropriate to the sensitivity of the data.

Security measures may include:

Access controls
Encryption where appropriate
Secure storage
Secure transmission
Audit logs
Data minimisation
Incident response processes
Staff access restrictions

23. Reports and Support

Users, developers, creators, security researchers, partners, rights holders, or viewers may contact Playflick about API data misuse, stale data, attribution problems, caching concerns, privacy concerns, unauthorised data replication, leaked data, or developer data security issues.

Contact:

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

Please include:

The app, API endpoint, data type, integration, developer account, domain, or URL involved
A clear explanation of the issue
Any screenshots, timestamps, logs with secrets removed, request IDs, or supporting context
Whether the issue involves child safety, personal data, rights, privacy, scraping, fraud, or legal concerns

Do not send passwords, full payment card numbers, API secrets, private keys, webhook signing secrets, parental PINs, or one-time login codes.

24. Enforcement

Playflick may take action where API data, cached data, exported data, attribution, integrations, applications, or related developer features are misused.

Enforcement may include:

Requiring data deletion
Requiring attribution changes
Restricting caching
Restricting API endpoints
Restricting developer apps
Revoking API keys or tokens
Throttling or blocking requests
Suspending developer accounts
Restricting accounts involved in misuse
Preserving records for legal, safety, fraud, rights, payment, developer, or security reasons

25. Appeals and Review Requests

If your API data access, caching permission, attribution approval, developer app, account, or related feature was removed or restricted and you believe Playflick made a mistake, you may request a review under our Appeals Policy where available.

Contact:

Email: hello@playflick.com

Please include:

Your developer account email where relevant
The app, API endpoint, data type, integration, attribution, or feature involved
The decision you are asking Playflick to review
Why you believe the decision was incorrect
Any supporting screenshots, timestamps, technical context, or relevant details

Do not send passwords, full payment card numbers, API secrets, private keys, webhook signing secrets, parental PINs, or one-time login codes.

26. Privacy and Data Retention

Playflick may process and retain API data access records, cache control records, attribution records, developer app records, request logs, data deletion records, integration records, support messages, review records, fraud signals, safety records, payment records, rights records, developer records, and enforcement records.

These records may be retained for platform operation, developer support, data governance, security, abuse prevention, child safety, payment protection, rights protection, legal compliance, moderation, appeals, audits, fraud prevention, and platform integrity.

More information is available in our Privacy Policy, Cookie Policy, Data Retention Policy, and Evidence Preservation Policy.

27. Changes to This Policy

We may update this API Data Use, Caching & Attribution Policy from time to time.

Changes may reflect new API tools, caching rules, attribution requirements, developer systems, data governance controls, privacy controls, rights controls, legal requirements, safety requirements, or platform updates.

Your continued use of Playflick API data, caching, attribution, or developer data features after changes become effective means you agree to the updated policy.

28. Contact Us

For API data questions, caching concerns, attribution issues, stale data reports, developer data use problems, review requests, or policy enquiries, contact:

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

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