1. Acceptance
By using the Service, you agree to these Terms.
2. Operator
Persistly is operated by Northshore Labs LTD, 19 Mestnost Manastirski Rid, Veselina Tsankova str., Varna, Bulgaria. UIC/BULSTAT: 208665242. VAT ID: BG208665242.
3. Eligibility and authority
Persistly is intended for developers, studios, and companies building games. If you use the Service for a company or other organization, you represent that you have authority to bind that organization to these Terms.
4. Accounts
You are responsible for maintaining account security and for all activity under your account. Persistly uses Clerk for authentication.
You are responsible for dashboard access, organization membership, runtime keys, API tokens, project settings, and any client builds or backend services that use your Persistly credentials.
5. Service description
Persistly is a hosted cloud save persistence and sync product for games. It provides a runtime API, operator dashboard, documentation, and SDK surfaces tied to that save-sync contract.
Persistly is not a real-time multiplayer backend, matchmaking service, authoritative game logic server, analytics ingestion platform, or general-purpose backend platform.
6. Customer data and save data
You retain all rights to Customer Data, including game save data, player identifiers, save metadata, project configuration, and content transmitted through the Service.
You grant Northshore Labs LTD a limited right to host, process, transmit, store, back up, secure, troubleshoot, display, and otherwise handle Customer Data only as necessary to provide, maintain, secure, support, and improve the Service, and as otherwise permitted by the Privacy Policy and Data Processing Addendum.
Persistly does not claim ownership of your games, game content, player save data, or customer-controlled player data.
7. Payments
Payments are processed through Stripe. Subscriptions renew automatically unless cancelled. Refunds and failed payments are handled under the Billing Policy.
You must keep billing, company, VAT, and tax details accurate before invoices are finalized. Corrections to finalized invoices may require a credit note, reissued invoice, or accounting review.
8. Acceptable use
You must not use the Service for illegal activity, infrastructure abuse, unauthorized scanning or attacks, interference with service operation, or data you are not authorized to process.
You must not submit malware, illegal content, full payment card data, passwords, government IDs, health data, administrative secrets, private signing keys, or other credentials that do not belong in save data. You must not submit special category or sensitive personal data, children's personal data, or personal data without an appropriate legal basis unless explicitly agreed in writing and supported by appropriate controls.
API and runtime abuse includes syncing every frame, intentionally bypassing rate or quota limits, creating projects or environments to evade limits, using Persistly as analytics ingestion, file hosting, large binary blob storage, real-time multiplayer state, scraping or enumeration infrastructure, broad public lookup by player reference, or a general-purpose database for unrelated application data.
9. Customer responsibilities
Customers are responsible for game data, project configuration, runtime keys, public client usage patterns, user notices, and compliance with applicable laws.
You are responsible for securing API keys, separating stage and production environments, implementing client-side sync safely, backing up any local game state you need outside Persistly, and giving your players appropriate notices and choices.
If you enable Auth Bridge, you are responsible for configuring your identity provider correctly, maintaining a lawful basis and player notices for that authentication flow, and keeping provider secrets, client secrets, management API tokens, and private signing keys out of runtime clients, SDK examples, support logs, telemetry, and save payloads.
10. Plans, limits, and fair use
Plans may include request limits, rate limits, payload limits, feature limits, support levels, and operational restrictions. We may throttle, reject, or suspend traffic that exceeds limits, threatens service stability, or appears abusive.
Published limits are product limits, not permission to generate wasteful or harmful traffic. You should not sync every frame, store unbounded blobs, or use Persistly as a replacement for real-time multiplayer state.
11. Intellectual property, SDKs, and feedback
We retain all rights in Persistly, the hosted service, docs, dashboard, runtime API, branding, and non-open-source product code. You retain rights in your games, game content, and customer data. Public SDK repositories may have separate open-source licenses.
If you provide feedback, suggestions, or improvement ideas, we may use them without restriction or compensation.
12. Third-party services
Persistly uses third-party services for functions such as authentication, payments, hosting, storage, delivery, email, DNS, and security. Use of those services may be subject to their own terms. Current service providers are listed on the Subprocessors page where applicable.
Customer-configured identity providers used with Auth Bridge, such as Firebase, Supabase, or Auth0, are controlled by the customer and may be subject to the customer's separate agreements with those providers.
13. Service availability, changes, and beta features
Unless a separate written agreement says otherwise, Persistly is provided without a service level agreement. We may change, suspend, deprecate, or discontinue features, limits, or access policies as the product evolves. We will try to avoid unnecessary breaking changes to the published runtime API.
Some features may be beta, preview, experimental, early access, or otherwise not yet generally available. Beta features may change, break, have lower reliability, be limited, or be removed.
14. Suspension, termination, export, and deletion
We may suspend or terminate accounts for violation of these Terms, abuse, legal requirements, security risk, or operational risk.
After termination, access to projects, runtime keys, dashboard features, and stored save data may be disabled or deleted subject to the Privacy Policy, DPA, Billing Policy, backups, and legal retention obligations.
After cancellation or termination, Customer Data may be retained for a limited period to allow export, recovery, billing review, security review, or legal compliance, then deleted according to applicable retention schedules, backups, and the DPA. Export tooling may depend on the plan, account status, and technical availability.
15. Data
Use of the Service is also governed by the Privacy Policy, Cookie Policy, Data Processing Addendum, and SDK Terms where applicable.
16. International use
The Service may be accessed globally. Users are responsible for compliance with local laws that apply to their games, players, and use of Persistly, including export, sanctions, consumer protection, privacy, and child-safety laws where applicable.
17. Disclaimers
To the maximum extent permitted by law, Persistly is provided on an “as is” and “as available” basis without warranties of uninterrupted availability, error-free operation, or fitness for a particular purpose.
18. Limitation of liability
To the maximum extent permitted by law, we are not liable for lost profits, business interruption, data loss, or indirect damages. Our total liability is limited to the amount you paid for the Service in the last 12 months.
19. Indemnity
To the extent permitted by law, you will defend and indemnify Northshore Labs LTDfrom claims, damages, liabilities, costs, and expenses arising from your games, your Customer Data, your misuse of the Service, your violation of these Terms, or your violation of laws or third-party rights.
20. Governing law
These Terms are governed by the laws of Bulgaria.
21. Changes
We may update these Terms. Continued use after an update means acceptance.
22. Contact
Legal questions: legal@persistly.app. Abuse reports: abuse@persistly.app. Product support: support@persistly.app.