1. Roles
The developer is responsible for their game, players, and end-user disclosures. For customer-controlled player data, the developer is the Data Controller and Northshore Labs LTD is the Data Processor.
2. Developer responsibilities
You must comply with applicable laws, obtain valid user consent where required, provide clear privacy disclosures to your users, and protect runtime keys and account access.
You must not ship secret admin tokens in clients. Runtime keys are intended for scoped client use, but you remain responsible for environment separation, key rotation, and abusive client behavior from your game.
3. Data restrictions
You must not send sensitive personal data unless explicitly allowed, illegal content, payment card data, passwords, government IDs, health data, administrative secrets, or data you are not authorized to process.
Client save payloads should contain only the player and game state needed for save, restore, and conflict resolution. Do not put private backend credentials, signing keys, dashboard tokens, or unrelated application data into save payloads or metadata.
4. Consent and opt-outs
You are responsible for collecting user consent and managing opt-outs where required.
5. Contract alignment
SDKs must follow the public OpenAPI contract, stable error schema, and published payload limits. They should not invent unsupported runtime operations such as broad public lookup by player reference.
Persistly may update SDKs, docs, and examples. Breaking runtime API changes should be handled through versioning, migration notes, or reasonable deprecation windows where practical.
SDK usage must respect plan limits and service boundaries. SDKs must not be modified or wrapped to bypass rate limits, create artificial traffic, enumerate player references, or use Persistly as analytics ingestion, file hosting, real-time multiplayer state, or a general-purpose backend.
6. SDK licenses
Public SDK repositories may include their own license files. Those licenses govern SDK source usage; these SDK Terms still govern access to the hosted Persistly service and runtime API.
7. Liability and termination
You are responsible for your use of the SDK and any data you transmit. We may revoke access if terms are violated or misuse is detected.
8. Changes
We may update SDK functionality and these terms.
9. Contact
Developer and security questions can be sent to legal@persistly.app.