Developer App Review & Approval Policy

Effective Date: 2026

Last Updated: 2026

This Developer App Review & Approval Policy explains how Playflick may review, approve, reject, restrict, suspend, re-review, or remove developer apps, integrations, API clients, OAuth apps, widgets, webhook integrations, partner tools, analytics tools, automation tools, third-party services, and related developer applications connected to 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, API Data Use, Caching & Attribution Policy, Third-Party Services Policy, Security Policy & Responsible Disclosure, 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 App Review Support Email: hello@playflick.com
Contact Page: https://playflick.com/contact-us

2. Purpose of This Policy

Developer apps may access Playflick APIs, user-authorised data, creator tools, analytics, webhooks, embeds, widgets, account features, or other platform systems. Playflick may review apps to protect users, creators, rights holders, developers, advertisers, and platform integrity.

This policy explains:

How developer apps may be submitted for review
What Playflick may check during app review
Why an app may be approved, rejected, restricted, or re-reviewed
How permissions, scopes, and sensitive access may be assessed
What developers must do after approval
How Playflick may enforce developer app requirements

3. Feature Availability

Developer app registration, app review, app approval, OAuth app review, restricted scope review, sandbox access, production access, partner review, app verification, security review, privacy review, and related developer features may not be available to every user, country, account type, business, creator, partner, plan, or integration.

Playflick may add, remove, restrict, redesign, suspend, or discontinue developer app review and approval features at any time.

4. Developer App Registration

Developers may need to register an app before using Playflick APIs, widgets, webhooks, OAuth flows, embeds, developer dashboards, or other integration tools.

Registration may require:

Developer account details
Business or organisation information
App name
App description
App website or domain
Privacy policy URL
Terms URL where required
Callback URLs or redirect URIs
Requested API scopes or permissions

5. App Review

Playflick may review developer apps before granting access to certain features, permissions, scopes, user data, production systems, webhooks, or API endpoints.

Review may include:

Security review
Privacy review
Branding review
Data use review
Permission review
Policy compliance review
User experience review
Fraud and abuse risk review

6. Information Playflick May Request

Playflick may request information to understand how the app works and how it uses Playflick data.

Requested information may include:

App purpose
Data flows
Requested permissions
Security controls
Data retention practices
User consent screens
Screenshots or demo videos
Test account access
Business verification documents where required
Privacy and legal compliance information

7. Permission and Scope Review

Apps should request only the permissions needed for their stated purpose.

Playflick may reject, reduce, or restrict requested scopes if the app requests unnecessary, excessive, sensitive, unclear, or high-risk access.

Sensitive permissions may require additional review, business verification, security documentation, or written approval.

8. Privacy Review

Developer apps must handle personal data lawfully, transparently, securely, and consistently with user permissions.

Privacy review may consider:

What data the app collects
Why the app needs the data
How users are informed
How data is stored
How long data is retained
Who data is shared with
How users may revoke access
How deletion requests are handled

9. Security Review

Developer apps must use reasonable security controls appropriate to the data and features accessed.

Security review may consider:

API key protection
Token storage
HTTPS usage
Webhook signature verification
Callback URL safety
Access controls
Logging practices
Incident response processes
Vulnerability management

10. User Experience Review

Playflick may review whether an app presents itself clearly and does not mislead users.

User experience review may consider whether the app:

Clearly identifies the developer
Explains requested permissions
Avoids fake Playflick branding
Does not impersonate Playflick
Does not hide important notices
Provides a working support contact
Provides clear account disconnect options where required

11. Branding and Attribution Review

Apps using Playflick names, logos, marks, badges, screenshots, widgets, or attribution labels must follow Playflick branding rules.

Apps must not imply that they are owned, operated, certified, endorsed, sponsored, or approved by Playflick unless Playflick expressly permits that claim.

12. Production Access

Playflick may provide sandbox, test, limited, or production access where available.

Production access may require:

Successful app review
Business verification where required
Security checks
Privacy checks
Valid support contact
Clear app documentation
Compliance with developer terms
Low fraud or abuse risk

13. Approval Is Not Permanent

Developer app approval may be temporary, conditional, limited, scope-specific, region-specific, feature-specific, or subject to ongoing review.

Playflick may re-review, restrict, suspend, or revoke approval if the app changes, violates policy, creates risk, receives complaints, or no longer meets requirements.

14. App Changes After Approval

Developers may need to notify Playflick or request re-review before making material changes.

Material changes may include:

New data use
New permissions or scopes
New user-facing features
New third-party data sharing
New payment or monetisation flows
Ownership or business changes
Security architecture changes
Callback URL or domain changes

15. Rejected Apps

Playflick may reject developer apps that do not meet review requirements.

Reasons for rejection may include:

Unclear app purpose
Excessive permissions
Missing privacy policy
Misleading branding
Weak security controls
Unsafe callback URLs
Suspicious data use
Fraud, spam, or abuse risk
Child-safety concerns
Violation of Playflick policies

16. Restricted Apps

Playflick may approve an app with restrictions.

Restrictions may include:

Limited API scopes
Lower rate limits
Limited user access
Sandbox-only access
Restricted webhooks
Domain restrictions
Additional attribution requirements
Additional privacy or security obligations

17. Suspended or Revoked Apps

Playflick may suspend or revoke developer app access where appropriate.

Reasons may include:

Security compromise
Leaked credentials
API abuse
Privacy violations
Misleading user flows
Policy violations
Fraud or spam
Unresolved user complaints
Legal or rights concerns
Failure to cooperate with review

18. Ongoing Compliance

Developers must maintain compliance after app approval.

Ongoing requirements may include:

Keeping contact details current
Keeping privacy notices current
Protecting API keys and tokens
Respecting user revocation
Deleting data when required
Maintaining secure systems
Following rate limits
Responding to Playflick review requests

19. Audits and Re-Reviews

Playflick may audit or re-review apps where appropriate.

Audits may be triggered by:

User reports
Security alerts
Credential leaks
High-risk data access
Unusual API activity
Ownership changes
Policy changes
Legal or regulatory requirements

20. Third-Party Services

Developer apps that connect Playflick to third-party services must ensure that those services are secure, lawful, and appropriate for the integration.

Developers remain responsible for third-party processors, vendors, hosts, analytics tools, payment tools, AI tools, and other services they use in connection with Playflick data.

21. Monetisation and Commercial Use

Apps that monetise Playflick data, integrations, widgets, analytics, automation, or platform access may require additional review or written permission.

Developers must not sell access to Playflick data, users, content, APIs, or restricted features unless permitted by Playflick.

22. Child Safety

Developer apps must not be used to exploit, sexualise, identify, harass, groom, manipulate, or endanger children or young users.

Playflick may apply stricter review, limited access, or immediate restrictions where an app involves children, young users, child profiles, parental controls, messaging, recommendations, or user-generated content.

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

23. Prohibited App Conduct

Developer apps must not be designed or used for harmful, deceptive, or unauthorised purposes.

Prohibited app conduct may include:

Fake Playflick login pages
Token theft
Credential harvesting
Spam automation
Unauthorised scraping
Bypassing paid access
Manipulating rankings or recommendations
Misusing user data
Building unsafe child-contact tools
Impersonating Playflick or Playflick staff

24. Reports and Support

Users, developers, creators, security researchers, partners, rights holders, or viewers may contact Playflick about app review issues, suspicious developer apps, fake integrations, unsafe permissions, app approval concerns, rejected apps, or developer compliance problems.

Contact:

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

Please include:

The app, developer account, integration, domain, permission, API feature, 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.

25. Enforcement

Playflick may take action where developer apps, app reviews, approvals, permissions, integrations, credentials, or related developer features are abused or fail to meet requirements.

Enforcement may include:

Rejecting app approval
Restricting requested scopes
Requiring app changes
Suspending developer apps
Revoking production access
Revoking API keys or tokens
Disabling webhooks
Restricting developer accounts
Requiring data deletion
Preserving records for legal, safety, fraud, rights, payment, developer, or security reasons

26. Appeals and Review Requests

If your developer app, app approval, requested scope, production access, developer account, or related feature was rejected 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, requested scope, integration, API feature, or review decision involved
The decision you are asking Playflick to review
Why you believe the decision was incorrect
Any supporting screenshots, technical context, privacy context, security 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.

27. Privacy and Data Retention

Playflick may process and retain app registration records, app review records, approval records, rejection records, requested scope records, developer account records, security review records, privacy review records, audit 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, app 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.

28. Changes to This Policy

We may update this Developer App Review & Approval Policy from time to time.

Changes may reflect new developer tools, app review systems, permission controls, privacy requirements, security requirements, rights controls, legal requirements, safety requirements, or platform updates.

Your continued use of Playflick developer app review, app approval, or developer integration features after changes become effective means you agree to the updated policy.

29. Contact Us

For developer app review questions, approval concerns, rejected app issues, scope review problems, developer compliance reports, review requests, or policy enquiries, contact:

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

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