Lynx RelayDifferent games. One shared moment.

Legal

Terms of Service

Terms for using Lynx.

Terms of Service

Last updated: July 1, 2026

These Terms of Service govern your access to and use of Lynx, including the website, API, SDK, documentation, developer tools, early access program, and related services.

By accessing or using Lynx, you agree to these Terms.

If you do not agree to these Terms, do not use Lynx.

1. Who operates Lynx?

Lynx is operated by:

Ádám Kormos
Hungary
Email: adam.kormos34@gmail.com

For questions about these Terms, contact:

adam.kormos34@gmail.com

2. What Lynx is

Lynx is a lightweight community-event backend for indie games.

It allows games to contribute to shared community events, sync event progress, unlock shared milestones, and offer in-game rewards when shared goals are reached.

Lynx is primarily a developer-facing service. It is intended to be integrated by game developers into their own games.

3. Early access and experimental status

Lynx may currently be provided as an early access, beta, developer preview, prototype, or experimental service.

This means:

You should not rely on Lynx for critical game functionality without your own fallback systems.

4. Eligibility

You may use Lynx only if you are legally able to enter into these Terms.

If you use Lynx on behalf of a studio, company, team, client, or other organization, you represent that you have authority to accept these Terms on their behalf.

In that case, “you” refers both to you personally and to the organization you represent.

5. Developer responsibilities

If you integrate Lynx into a game, you are responsible for:

Lynx provides backend and SDK tools. You remain responsible for how those tools are used inside your game.

6. Player-facing disclosures

If your game uses Lynx, you should clearly explain to players:

You are responsible for making these disclosures in your own game, store page, privacy policy, terms, or other player-facing materials.

7. Accounts, keys, and credentials

Lynx may provide or use credentials such as:

You are responsible for keeping private credentials secure.

You must not:

If you believe a key or credential has been compromised, contact Lynx as soon as possible.

adam.kormos34@gmail.com

8. Game admin passwords and client-side use

Game admin passwords are private admin/developer credentials.

You must not include Game Admin Passwords in public game builds, client-side website code, public repositories, screenshots, logs, or public documentation.

Public game builds may use Game IDs, Game Keys, event IDs, and SDK-managed installation credentials. These should not be confused with Game Admin Passwords. Game Keys are runtime credentials and must not grant admin/developer actions.

Lynx may rotate, disable, or revoke credentials if necessary for security, abuse prevention, or service integrity.

9. Admin keys

Admin keys are sensitive credentials.

Admin keys are intended only for trusted administrative actions, such as managing games, relays, configuration, or access.

You must not include admin keys in:

Lynx may revoke or rotate admin keys if they are exposed or suspected to be compromised.

10. Acceptable use

You may use Lynx only for lawful, safe, and reasonable purposes.

You must not use Lynx to:

Lynx may suspend or revoke access if abuse is detected or reasonably suspected.

11. Prohibited data

You must not intentionally send the following types of data to Lynx unless specifically agreed in writing:

Lynx is designed to avoid direct player identity data.

12. Relays and shared events

Lynx may allow games to contribute to shared relays or events.

Relay behavior may depend on configuration such as:

Lynx may modify, pause, reset, or remove relays if needed for testing, security, abuse prevention, maintenance, early access changes, or product development.

13. Reward claims

Lynx may help determine when a shared event milestone has been reached and when a game may offer a reward claim.

However, the game developer is responsible for:

Lynx does not guarantee the value, availability, delivery, permanence, legality, or suitability of any in-game reward.

14. Reward availability is not a guarantee

A reward claim state returned by Lynx does not guarantee that a player will successfully receive a reward.

Reward delivery may fail because of:

You are responsible for implementing safe reward handling in your own game.

15. No player support obligation from Lynx

Unless separately agreed, Lynx does not provide direct support to players of third-party games.

Players should contact the developer or publisher of the game they are playing.

Developers are responsible for player-facing support related to:

16. API and SDK changes

Lynx may update the API, SDK, documentation, endpoints, request formats, response formats, authentication methods, or integration requirements.

Where reasonable, Lynx may try to communicate breaking changes to active early access developers.

However, during early access or beta development, breaking changes may happen.

You are responsible for testing updates before shipping them to players.

17. Availability and uptime

Lynx is provided on an “as is” and “as available” basis.

Lynx does not guarantee that the service will be:

Lynx may be unavailable due to maintenance, infrastructure issues, provider outages, abuse prevention, security incidents, development changes, or discontinuation.

18. Backups and fallback behavior

You are responsible for designing your game so that it behaves reasonably if Lynx is unavailable.

You should consider fallback handling for:

Do not make your game critically dependent on Lynx without appropriate fallback handling.

19. Rate limits and abuse prevention

Lynx may apply rate limits, request validation, abuse detection, idempotency checks, or other protective measures.

Requests may be rejected, delayed, limited, or blocked if they appear to be abusive, invalid, excessive, suspicious, or harmful.

Lynx may change rate limits or abuse-prevention rules at any time.

20. Suspension and termination

Lynx may suspend, limit, or terminate your access if:

You may stop using Lynx at any time.

If your access is terminated, you must stop using Lynx credentials, API endpoints, SDK functionality, and related services unless otherwise permitted.

21. Developer content

You may provide Lynx with information about your game, such as:

You represent that you have the right to provide this content.

You grant Lynx permission to use this content as needed to:

Lynx will not claim ownership of your game, assets, trademarks, or original content.

22. Feedback

If you provide feedback, suggestions, ideas, bug reports, feature requests, or improvement proposals, Lynx may use them without obligation to compensate you.

This includes using feedback to improve the API, SDK, documentation, website, business model, or product design.

You should not send confidential or proprietary information unless you are comfortable with Lynx using it for product development.

23. Intellectual property

Lynx, including its name, website, backend design, documentation, SDK materials, branding, and related assets, is owned by its creator or licensed appropriately.

You may not copy, modify, distribute, sell, sublicense, or exploit Lynx materials except as allowed by these Terms, the applicable license, written permission, or normal use of the service.

Your game, assets, trademarks, code, and original content remain yours.

24. SDK license

The Lynx SDK may be provided under a separate license.

If a separate SDK license is included in the SDK repository, package, or documentation, that license applies to the SDK code.

If no separate license is provided, you may use the SDK only for integrating your game with Lynx and testing Lynx functionality.

You may not misrepresent the SDK as your own standalone service or resell Lynx functionality without permission.

25. Documentation

The Lynx documentation is provided for convenience and may be incomplete, outdated, or incorrect during early development.

You are responsible for testing your own integration.

Lynx may update documentation at any time.

26. Third-party services

Lynx may use or link to third-party services such as:

Those services are governed by their own terms and privacy policies.

Lynx is not responsible for third-party services, outages, data handling, content, or policies.

27. Payment and pricing

Lynx may currently be offered for free, as early access, or under special developer access terms.

Pricing, access conditions, free access, lifetime access, limits, quotas, or paid plans may change in the future.

If paid plans are introduced, additional terms may apply.

Any promise of free or lifetime access must be confirmed clearly in writing by Lynx.

28. Early access free lifetime access

If Lynx grants free lifetime access to an early access game, this means access under the conditions communicated at the time of acceptance.

Unless separately agreed, this does not guarantee:

Reasonable technical, security, and abuse-prevention limits may still apply.

29. Confidentiality

During early access, Lynx may share non-public technical information, roadmap information, private links, credentials, or documentation.

You should not publicly share private credentials, private admin endpoints, private roadmap details, or non-public technical details unless Lynx gives permission.

This does not prevent you from discussing your own game or publicly available Lynx materials.

30. Publicity

Unless you ask otherwise, Lynx may mention that your game or studio is testing or using Lynx if you have voluntarily joined early access or provided public information.

If you do not want your game or studio mentioned publicly, contact Lynx.

adam.kormos34@gmail.com

31. Privacy

Your use of Lynx is also subject to the Lynx Privacy Policy.

You are responsible for your own game’s privacy policy and for explaining your own data practices to your players.

Do not use Lynx to send unnecessary personal data.

32. Disclaimer of warranties

To the fullest extent permitted by law, Lynx is provided without warranties of any kind, whether express, implied, or statutory.

This includes, but is not limited to, warranties of:

You use Lynx at your own risk.

33. Limitation of liability

To the fullest extent permitted by law, Lynx and its creator will not be liable for indirect, incidental, special, consequential, exemplary, or punitive damages.

This includes damages related to:

This limitation applies even if Lynx has been advised of the possibility of such damages.

34. Maximum liability

To the fullest extent permitted by law, Lynx’s total liability for any claim related to the service will be limited to the amount you paid to Lynx for the service in the 3 months before the claim arose.

If you have not paid Lynx, Lynx’s total liability will be limited to the minimum amount permitted by applicable law.

35. Indemnity

You agree to defend, indemnify, and hold harmless Lynx and its creator from claims, damages, liabilities, losses, costs, and expenses arising from:

36. Changes to Lynx

Lynx may modify, suspend, limit, or discontinue any part of the service at any time.

This includes:

Lynx may do this with or without notice, depending on the situation.

37. Changes to these Terms

These Terms may be updated as Lynx develops.

The updated version will be posted on this page with a new “Last updated” date.

If you continue using Lynx after the Terms are updated, you accept the updated Terms.

38. Governing law

These Terms are governed by the laws of Hungary, unless mandatory law provides otherwise.

If a dispute arises, the parties should first try to resolve it informally by contacting:

adam.kormos34@gmail.com

39. Severability

If any part of these Terms is found to be invalid or unenforceable, the remaining parts will remain in effect.

The invalid or unenforceable part will be interpreted as closely as possible to the original intent, to the extent permitted by law.

40. Entire agreement

These Terms, together with the Privacy Policy and any separate written agreement or SDK license that applies, form the entire agreement between you and Lynx regarding use of the service.

41. Contact

For questions about these Terms, contact:

adam.kormos34@gmail.com