Legal
Developer Agreement
Document details
Version: 2.0 (draft). Effective date: none — this draft is not yet in effect, and nothing in it is in force. Last updated: 30 August 2026. Responsible entity: [SPHEROMNI RESPONSIBLE ENTITY — TBD]. Governing law and jurisdiction: [PRIMARY JURISDICTION — TBD]. Contact: [PRIVACY CONTACT — TBD].
Change history:
- Version 2.0 — put into force for acceptance records only, when the acceptance flow §11 required and the submission surface it gates were built. The document remains a draft prepared for counsel; the payment section stays inactive.
- Version 1.0 — first draft, written at Milestone 19 ahead of any third-party submission route existing. Not in effect, and nobody has accepted it.
1. What accepting this means today
Spheromni now has a developer enrollment flow: your account can accept this agreement, the acceptance is recorded — which version, and when — and that record is what lets you create, edit and submit store entries of your own. Until you accept, the submission surface refuses you and says why. Accepting an older version than the one shown here is refused rather than silently recorded against the current one.
Be equally clear about the limits. This document is in force for acceptance records only: the platform asks for your acceptance and keeps the record, but the text has not been reviewed by counsel, and the sections below marked activates with third-party submission state intended terms whose obligations neither side should yet rely on as a contract. Review is performed by the same single administrator role that publishes Spheromni's own applications, and nothing anywhere in the product involves payment.
Seller onboarding remains separate: a verified seller can neither list anything nor be paid anything (see the Seller Agreement), and being one does not make you a developer under this document.
2. What an application is
An application is a listing in the Spheromni store with a manifest: a slug, a name, a summary, a version, a category, and the list of permissions it declares. It may be a first-party application built into the product, or — the kind you can submit — an external site or progressive web app that Spheromni loads in a sandboxed frame.
3. Declaring permissions honestly
Every application declares the permissions it needs from this closed list, and the user is shown that list before installing:
files.read— Read your filesfiles.write— Change your filessharing.manage— Share files with people you invitecommunity.participate— Take part in the community as your profileaccount.read— See your accountaccount.settings— Sync its settings to your accountdrive.manage— Manage the Google Drive connectionbrowser.storage— Store settings in this browserdevice.microphone— Use the microphone (push-to-talk)apps.manage— Manage installed apps
Declare the least you need and declare all of it. Declaring a permission you do not use is a dishonest disclosure; using a capability you did not declare is worse.
Be clear about what this list is, because a developer agreement that overstated it would be the wrong place to be optimistic: declared permissions are enforced server-side at call time, as capability grants the user can revoke individually. A request your application makes against a capability it did not declare, was never granted, or that the user has revoked is refused. And since the local application runtime landed, an application run as a runtime tenant executes inside a sandboxed frame whose only channel to Spheromni is a bridge that names operations, never routes — so for those tenants the statement of which application a request comes from is enforced by isolation, and a declaration that does not match behaviour fails rather than merely breaching this document. An external site or progressive web app you submit is framed separately and gets no bridge at all.
4. Rights in what you submit
Activates with third-party submission. You keep ownership of your application. You grant Spheromni the licence needed to list, display, distribute and run it inside the product, for as long as it is listed. Spheromni claims no ownership of your work, will not sell or sublicense it, and will not use it to train any model — there is no model in the product to train.
You warrant that you made the application or are licensed and authorised to distribute it, including every asset in it, and including any external site or progressive web app it points at.
5. Review
Activates with third-party submission. Applications are reviewed against the Application Review Guidelines, which describe the lifecycle a submission actually moves through in this codebase, and what a reviewer may and may not do to it. Review is performed by a person; there is no automated review of any kind.
6. What you must not submit
The Acceptable Use Policy applies in full. In addition: nothing that misrepresents what it does, nothing that impersonates Spheromni or another publisher, nothing that collects user data beyond what its declared permissions describe, nothing that loads or executes code from a source it did not disclose, and nothing that tries to escape the frame it is given.
7. Your users' data
Activates with third-party submission. If your application processes user data, you are its controller for that processing and you need your own privacy notice. Spheromni is not your processor and will not act as one. You may not sell user data, use it for advertising, or transfer it to a data broker — consistent with the platform's own position, which is the same.
8. Money
Activates with payment, after commercial and legal review, and with third-party submission. Prices, currencies, checkout, the commission rate, payouts, taxes and refunds are all inactive. Payment is not activated in this product, no billing provider is configured, and no money has ever moved. Nothing in this section is a present commitment about revenue share or payment.
9. Support and liability
Activates with third-party submission. You are responsible for supporting your application and for claims arising from it. Spheromni provides the store as-is, with no uptime commitment and no guarantee of distribution, discovery or placement.
10. Removal and termination
Activates with third-party submission. Spheromni may delist an application that breaches this agreement or the review guidelines, with a written reason, recorded in the audit trail. You may withdraw an application at any time. Existing installations of a withdrawn or delisted application are handled per the review guidelines.
11. Changes
Changes are recorded as a new version in the change history above. The acceptance flow this section once required now exists, and it is version-aware: your acceptance names the version you read, a new version requires a fresh acceptance before you can keep submitting, and the record of what you accepted earlier is kept rather than overwritten. What still does not exist is any notice of a change — Spheromni sends nothing outside the product, so a changed version is discovered by reading this page or by the submission surface asking you to accept again.
12. Contact
[PRIVACY CONTACT — TBD].