Playbix

Developer Distribution Agreement

Last updated 11 August 2026

This is the contract between you and Playbix covering apps you publish on Playbix. It sits alongside the Terms of Service and the Content Policy, and it wins where the three disagree on a publishing question.

Draft — needs completion before launch

Details shown in square brackets are placeholders. Fill them in at src/lib/legal.ts, then have this document reviewed by a lawyer in your jurisdiction. Hosting third-party app files carries more liability than an ordinary website.

1. Accepting this agreement

You accept this agreement by submitting a developer application. If you are agreeing on behalf of a company, you confirm you have authority to bind it, and "you" means that company.

You must be legally able to enter a contract where you live, and you must not be barred from receiving software or services under applicable export or sanctions law.

2. Your account

  • One developer account per person or company. Operating multiple accounts to evade enforcement is itself a breach.
  • You must give and maintain accurate details: legal name, working contact email, country, and a government identity document. Applications are reviewed by a person and cannot be approved without verified identity.
  • You are responsible for everything done through your account, including by anyone you give access to. Tell us immediately at support@playbix.store if you suspect compromise.
  • We may re-verify your identity at any time, particularly if your apps request sensitive permissions, handle payments, or are the subject of reports.

3. Signing keys — read this one carefully

When your first version is approved we permanently record the SHA-256 fingerprint of the certificate it was signed with. Every later upload for that app must be signed with the same key. Our database rejects a differently-signed upload; it is not a setting we can toggle for you.

This has consequences you should plan for:

  • Back up your keystore and its passwords, off your development machine. If you lose the key you cannot update your app. Your only route is a new listing under a new package name, and your existing users will not be offered it as an update.
  • You must not transfer, sell or share your signing key. If you transfer your business, contact us before transferring apps.
  • If you believe your key is compromised, tell us immediately. We would rather unpublish an app than let a stolen key push an update.
  • We will reset a pinned certificate only after verifying your identity, and doing so is recorded in our audit log. We are deliberately unhelpful about this, because a differently-signed update is exactly what an attacker who took your account would ask for.

4. Your app and your rights

4.1 What you promise

For every app and every version you upload, you represent and warrant that:

  • you created it, or you hold all rights necessary to distribute it through us;
  • it is not a modified, cracked, re-signed, repackaged or "premium unlocked" version of anyone else's software;
  • it contains no malware, no spyware, no hidden functionality, and no undisclosed data collection;
  • it does not download and execute code that changes its behaviour after review — if your app can become something else after we approve it, we cannot vouch for it;
  • your listing accurately describes what it does, and its content rating is honest;
  • it complies with applicable law wherever you distribute it, including data protection, consumer and children's privacy law;
  • every permission it requests is necessary for a function a user would recognise, and you can justify each one if we ask.

4.2 Licence you grant us

You keep all ownership of your app. You grant Playbix a worldwide, non-exclusive, royalty-free licence to host, store, reproduce, distribute, publicly display and transmit your app and its listing assets — icon, banner, screenshots, description, release notes — for the purposes of operating, securing and promoting the store, including showing them in our Android client, in search results and in editorial collections.

The licence ends when you remove the app, with three exceptions: we may keep copies as needed for legal, security and backup purposes; users who already installed it keep their copy; and we may retain the version history required to answer questions about what was distributed.

4.3 Licence you grant users

You are responsible for the licence terms between you and your users. If you supply your own end-user licence agreement we will surface it; if you do not, users receive a standard non-exclusive right to use the app on their devices. We are not a party to that licence.

5. Review, publication and removal

  • Every app is scanned for malware and reviewed by a person before first publication. Passing review is not an endorsement and does not transfer responsibility for your app to us.
  • Each upload must carry a higher versionCode than the last.
  • A package name is permanent once published. It identifies your app on every device that installs it.
  • We may remove an app, refuse a version, unpublish a listing, or suspend or terminate your account if we believe it breaches this agreement, the Content Policy or the law, or presents a risk to users.
  • Where circumstances allow we will explain why and give you a chance to respond. Where an app appears to be actively harming users we act first and explain afterwards, and we may notify people who installed it.
  • Suspending a developer account also unpublishes that developer's live apps.

6. Fees

Developer registration is currently free. If we introduce a registration fee it will apply only to applications submitted after the change, the amount will be shown before you commit, and we will not retroactively charge existing developers. See Fees and refunds.

We do not currently process payments for paid apps or in-app purchases. If you charge users by any other means, that transaction is between you and them, and you are responsible for tax, consumer rights and refunds arising from it.

7. Data protection

Where your app processes personal data you are the controller of that data and we are not. You must:

  • publish an accurate privacy policy and keep the URL on your listing current;
  • disclose what you collect truthfully in your listing's data-safety information, which users see before installing;
  • comply with COPPA, the UK Age Appropriate Design Code and equivalent law if your app is directed at children;
  • not use permissions to collect data unrelated to a function the user asked for.

We process your own developer data as described in the Privacy Policy, including the specific handling of your identity document.

8. Security obligations

  • Sign with APK Signature Scheme v2 or later. We reject v1-only builds.
  • Do not ship debuggable builds. We reject them automatically.
  • Report a vulnerability in your own app that puts users at risk, so we can decide together whether to pull the version.
  • Do not attempt to bypass, probe or interfere with our review, scanning, signing-key or install-counting systems.

If you find a vulnerability in Playbix itself, please tell us under our security disclosure policy rather than publishing it.

9. Indemnity

You agree to indemnify and hold harmless Playbix, and its officers and staff, from any claim, demand, loss, liability or expense (including reasonable legal fees) arising from your app, your listing assets, your breach of this agreement, or any claim that your app infringes a third party's rights or damaged a user's device or data.

10. Disclaimers and liability

The store is provided to you "as is". We do not warrant any level of downloads, revenue, ranking, placement or availability, and we may change how the store ranks, features or presents apps at any time.

To the maximum extent permitted by law, our total liability to you for any claim relating to this agreement is limited to the greater of the fees you paid us in the twelve months before the claim, or US$50. We are not liable for indirect, incidental, special or consequential loss, or for lost profits or lost data.

11. Term and termination

This agreement runs until terminated. You may terminate by removing your apps and closing your developer account. We may terminate for breach, or on 30 days' notice if we discontinue the service.

On termination your licence to distribute through us ends, and we will unpublish your apps. Sections 4.1, 9, 10 and 12 survive termination, along with your obligations to users who already installed your app.

12. Changes, governing law and general

  • We may update this agreement. For material changes we will give at least 14 days' notice by email or an in-console notice. Continuing to publish afterwards accepts the new terms; if you do not accept them, remove your apps.
  • This agreement is governed by the laws of [Your country], and disputes will be heard in its courts, except that either party may seek injunctive relief where needed to protect its rights.
  • You may not assign this agreement without our written consent. We may assign it to a successor to our business.
  • If any provision is unenforceable, the rest stands. Our failure to enforce a provision is not a waiver of it.
  • Nothing here creates a partnership, agency or employment relationship.

13. Contact

Playbix
[Your business address]
Developer support: support@playbix.store
Abuse and security: abuse@playbix.store