Aetherstars Developer Agreement

1. Introduction & Acceptance

1.1 This Developer Agreement ("Agreement") governs the submission, review, approval, hosting, distribution, operation, removal, and promotion of games through Aetherstars ("Aetherstars" or the "Service"). Aetherstars is a project operated within the Jullow ecosystem.

1.2 A person, developer, studio, company, organisation, or other entity that creates an Aetherstars Studio Account, submits a game, or uses Aetherstars developer features is referred to as a "Developer."

1.3 Aetherstars operates under the Jullow ecosystem's main Terms of Service, Privacy Policy, and Cookie Policy. These Jullow policies apply to Aetherstars and its users and remain the primary policies governing the Service. This Developer Agreement provides additional rules specifically relating to Developers, Studios, and submitted games.

1.4 The Jullow ecosystem policies are available at:

• Jullow Terms of Service: jullow.com/legal/terms
• Jullow Privacy Policy: jullow.com/legal/privacy
• Jullow Cookie Policy: jullow.com/legal/cookie

These documents may be accessed through the relevant links within Aetherstars and will open on the Jullow website.

1.5 This Agreement supplements the Jullow Terms of Service, Privacy Policy, and Cookie Policy. It does not replace them.

1.6 If a provision of this Agreement conflicts with an applicable Jullow ecosystem-wide policy, the Jullow policy takes precedence unless that policy expressly provides otherwise.

1.7 By creating an Aetherstars Studio Account or submitting a game, the Developer confirms that they have read, understood, and agree to this Agreement.

2. Eligibility & Aetherstars Accounts

2.1 Developers must be at least 16 years old to create an Aetherstars Account or use Aetherstars developer features.

2.2 Aetherstars currently uses its own Aetherstars Account system.

2.3 When creating an account, users may choose between:

• Player Account — for discovering, downloading, and playing games available through Aetherstars.
• Studio Account — for Developers who want to submit and manage games through Aetherstars.

2.4 A Studio Account may be used to:

• submit games;
• manage submitted games;
• manage the Studio profile;
• manage the Studio name;
• manage the Studio logo;
• manage the Studio description;
• manage the Studio's official website;
• test the Studio's own submitted games; and
• use other developer features made available by Aetherstars.

2.5 A Studio Account does not provide ordinary access to play games submitted by other Studios. A Studio may use Aetherstars' testing functionality to test its own submitted games.

2.6 Aetherstars may introduce Jullow ID in the future. When Jullow ID is introduced, Aetherstars Accounts may be connected to, migrated to, or integrated with Jullow ID. Additional information may then be required to complete the Jullow ID account.

2.7 The introduction of Jullow ID will not transfer ownership of a Developer's games to Jullow or Aetherstars.

3. Godot Engine Requirement

3.1 Aetherstars is a Godot-focused game platform. Games submitted to Aetherstars must be developed using the Godot Engine.

3.2 Aetherstars does not currently accept games developed using other game engines, including Unity, Unreal Engine, GameMaker, or other non-Godot engines.

3.3 The currently supported Godot Engine version for submissions is Godot Engine 4.7.1.

3.4 Aetherstars may change its supported Godot Engine version or technical requirements in the future. The currently supported version will be communicated through the submission interface or other official Aetherstars documentation.

3.5 A game created using an unsupported Godot version may need to be migrated, rebuilt, or otherwise updated before it can be accepted.

3.6 Meeting the Godot requirement does not guarantee publication. Every submitted game remains subject to Aetherstars' review process.

3.7 Developers are responsible for complying with the licenses applicable to Godot and to any third-party components, libraries, assets, fonts, audio, artwork, or other material included in their game.

4. Game Submission

4.1 Developers may submit games through the Aetherstars Studio interface.

4.2 A submission may require information including:

• game name;
• game description;
• game icon;
• screenshots;
• game category;
• intended audience;
• age or content rating information;
• supported platform;
• Godot Engine version;
• game export/build;
• Studio information;
• official website; and
• other information reasonably required by Aetherstars.

4.3 Before submitting a game, the Developer must confirm:

I have read and agree to the Aetherstars Developer Agreement.

4.4 The Developer must confirm:

I confirm that this game was developed using Godot Engine 4.7.1 and meets Aetherstars' current technical requirements.

4.5 The Developer must confirm:

I confirm that I own this game or have all necessary rights and permissions to submit and distribute it through Aetherstars, including rights relating to its code, artwork, audio, music, characters, fonts, assets, libraries, and other included content.

4.6 The Developer must confirm:

I confirm that this submission does not intentionally contain tracking, analytics, advertising, hidden data collection, malware, spyware, payment systems, in-app purchases, or other prohibited functionality.

4.7 Aetherstars may record the version of this Agreement accepted by the Developer, together with the date and time of acceptance, for contractual and administrative purposes.

5. Ownership of Games

5.1 The Developer retains ownership of all intellectual property rights they own in their game.

5.2 Submitting a game to Aetherstars does not transfer ownership of the game to Aetherstars, Jullow, or any other party.

5.3 The Developer remains responsible for determining who owns the intellectual property contained in the game.

5.4 Where a Developer uses third-party content, the Developer is responsible for obtaining all permissions, licenses, and rights necessary to use and distribute that content through Aetherstars.

5.5 Developers must not submit games containing copyrighted, trademarked, licensed, or otherwise protected material that they do not have permission to use.

6. License Granted to Aetherstars

6.1 By submitting a game and accepting this Agreement, the Developer grants Aetherstars a non-exclusive, worldwide license to use the submitted game solely as necessary to review, operate, host, store, distribute, display, and promote the game through Aetherstars.

6.2 This license allows Aetherstars to:

• a) receive and store the submitted game;
• b) reproduce the game as technically necessary to operate the Service;
• c) create technical, security, caching, and backup copies;
• d) inspect, test, and scan the game;
• e) host the game on Aetherstars infrastructure;
• f) make the game available to Aetherstars users;
• g) distribute the game through supported Aetherstars platforms;
• h) display the game's name, icon, logo, description, screenshots, and other submitted information;
• i) use the Developer's Studio information;
• j) use submitted promotional materials to promote the game or Aetherstars; and
• k) identify the game as available on Aetherstars.

6.3 The license in this Section continues for as long as the game remains available through Aetherstars, unless the Developer and Aetherstars agree otherwise.

6.4 The license does not transfer ownership of the game to Aetherstars.

6.5 The license is non-exclusive. A Developer may publish or distribute the same game through other platforms, including Google Play, Steam, itch.io, the Developer's own website, or other services.

6.6 Aetherstars does not require exclusivity unless the Developer and Aetherstars separately agree to an exclusive arrangement in writing.

6.7 The license for active distribution ends when the game is removed from Aetherstars, subject to the provisions of this Agreement concerning account recovery, backups, technical copies, promotional materials, and legal retention requirements.

7. Hosting, Copies & Backups

7.1 Aetherstars may store copies of submitted games on its servers and other infrastructure used to operate the Service.

7.2 Aetherstars may create multiple technical copies of a submitted game for purposes including:

• redundancy;
• backup;
• disaster recovery;
• security;
• caching;
• distribution;
• testing;
• migration between infrastructure; and
• restoration of the Service.

7.3 These copies do not create additional ownership rights for Aetherstars.

7.4 Aetherstars will not sell or license a Developer's submitted game to an unrelated company for that company's independent commercial use.

7.5 When a game is removed, Aetherstars will remove it from active distribution and begin the applicable deletion process.

7.6 Technical copies may remain temporarily in backups, caches, disaster-recovery systems, or other technical infrastructure while normal deletion processes are completed.

7.7 Aetherstars will make reasonable efforts to permanently delete remaining copies in accordance with its applicable deletion and retention procedures.

8. No Developer Payments or Royalties

8.1 Aetherstars currently does not charge Developers to submit games.

8.2 Aetherstars currently does not charge Developers for hosting or distributing accepted games.

8.3 Developers are not paid for games hosted or distributed through Aetherstars.

8.4 Aetherstars does not currently provide royalties, revenue sharing, advertising revenue, sales commissions, or other monetary compensation for games distributed through the Service.

8.5 Players currently cannot purchase individual games through Aetherstars.

8.6 Aetherstars may introduce paid features, subscriptions, virtual items, coins, avatars, or other monetised features in the future. Any such features will be governed by applicable Jullow and Aetherstars terms provided to users when those features become available.

8.7 A Developer's game may be commercially available outside Aetherstars. Developers may sell premium versions, additional content, expansions, maps, quests, merchandise, subscriptions, or other products through their own websites or other platforms, subject to applicable law and those platforms' rules.

9. Payments & Monetization in the Aetherstars Version

9.1 The version of a game distributed through Aetherstars must be available to players without requiring payment.

9.2 Developers must not include payment or monetization functionality in the Aetherstars-distributed version of a game.

9.3 Prohibited functionality includes, without limitation:

• in-app purchases;
• paid upgrades;
• subscriptions;
• paid downloadable content;
• donations;
• tipping;
• paid virtual currency;
• paid items;
• paid lives or energy;
• paid unlocks;
• paid access to levels or maps;
• paid expansions;
• loot boxes or similar paid randomised items;
• payment processors;
• checkout systems;
• payment links;
• external payment forms; and
• other mechanisms designed to collect money from players through the Aetherstars version of a game.

9.4 Developers must not integrate payment services such as payment processors, digital wallets, or external checkout systems into the Aetherstars version of their game.

9.5 Developers must not use the Aetherstars version of a game to redirect players to an external website for the purpose of purchasing the game, premium content, merchandise, subscriptions, or other commercial products.

9.6 Developers may offer commercial products outside Aetherstars, including through their own website or other platforms, subject to applicable law and those platforms' rules.

9.7 The Aetherstars Studio Profile may include a link to a Developer's official website.

9.8 A player may voluntarily visit that website and independently purchase products or services there.

9.9 A Developer must not falsely state that a paid product, premium version, expansion, subscription, or other commercial offering is available through Aetherstars when it is not.

9.10 If a submitted game contains prohibited payment or monetization functionality, Aetherstars may reject the submission and require the Developer to remove the functionality before the game can be accepted or updated.

10. Advertising & Promotional Restrictions for Developers

10.1 Aetherstars does not currently provide advertising space inside the Service for Developers to purchase or use.

10.2 Developers must not place advertisements, promotional banners, commercial pop-ups, or third-party advertising systems inside the Aetherstars-distributed version of their game.

10.3 Developers must not use the Aetherstars version of a game to advertise:

• premium versions;
• paid expansions;
• merchandise;
• subscriptions;
• other games;
• third-party products; or
• other external commercial offerings.

10.4 Developers must not repeatedly direct players away from Aetherstars for commercial purposes.

10.5 Developers may maintain an official website. The Studio Profile on Aetherstars may include a link to that official website.

10.6 Players may voluntarily visit a Developer's official website through the Studio Profile. Once a player leaves Aetherstars and accesses the Developer's independent website or independently downloads the Developer's game elsewhere, that activity is outside Aetherstars.

10.7 Developers may publicly state that their game is available on Aetherstars.

11. Aetherstars Promotional Rights

11.1 By submitting a game, the Developer grants Aetherstars permission to use the game's: name; icon; logo; Studio name; Studio logo; screenshots; gameplay footage supplied to Aetherstars; description; public Studio information; and other promotional materials supplied by the Developer for the purpose of operating and promoting the game and Aetherstars.

11.2 Aetherstars may use these materials on:

• Aetherstars websites;
• the Aetherstars application;
• Aetherstars social media;
• Jullow websites;
• Jullow applications;
• Jullow social media;
• promotional graphics;
• announcements;
• newsletters;
• showcases; and
• other promotional channels operated by Aetherstars or within the Jullow ecosystem.

11.3 Aetherstars may identify a game as: "Available on Aetherstars."

11.4 Aetherstars may promote a game even if the Developer also distributes that game through other platforms.

11.5 The Developer does not grant Aetherstars ownership of the Developer's trademarks, branding, logos, or other intellectual property by providing promotional materials.

11.6 If a game is removed from Aetherstars, Aetherstars will stop actively promoting the game as currently available through Aetherstars.

11.7 Previously published promotional material may remain available after removal where it forms part of a previously published post, announcement, article, showcase, archive, or other historical material.

11.8 Aetherstars is not required to delete every previously published promotional material solely because the associated game has been removed.

12. Privacy & Player Data

12.1 Privacy is a fundamental requirement of Aetherstars.

12.2 A Developer must not use an Aetherstars-distributed version of a game to collect player data outside the data flows permitted by Aetherstars.

12.3 Developers must not intentionally include:

• analytics;
• advertising trackers;
• behavioral tracking;
• click tracking;
• session recording;
• advertising identifiers;
• hidden telemetry;
• fingerprinting;
• location tracking;
• third-party tracking SDKs;
• data brokers;
• hidden data collection;
• undisclosed network communications; or
• similar tracking technologies

in a game distributed through Aetherstars.

12.4 Developers must not attempt to determine or collect through independent tracking:

• which buttons a player presses;
• which menus a player opens;
• how long a player plays;
• what levels a player completes;
• what items a player views;
• what choices a player makes;
• what advertisements a player interacts with;
• device information for tracking purposes; or
• other behavioral information about players.

12.5 Aetherstars will not provide Developers with individual player analytics or behavioral data generated through gameplay within Aetherstars.

12.6 Developers must not attempt to bypass, disable, or circumvent Aetherstars' privacy protections.

12.7 Developers must not require players to create a separate Developer-controlled account in order to play the Aetherstars version of a game.

12.8 The Aetherstars Account is the account used by the player while using Aetherstars.

12.9 A Developer may allow a player to choose an in-game display name or other game-specific customisation where supported, but this does not create a separate Developer-controlled account.

12.10 Developers must not transmit Aetherstars player account information to external services unless Aetherstars expressly permits that functionality.

12.11 If Aetherstars discovers prohibited tracking or data collection in a submitted game, the game may be rejected or removed.

13. Game Networking & Multiplayer

13.1 Games distributed through Aetherstars may only communicate with external servers or services where such communication is permitted by Aetherstars.

13.2 Single-player games should not require unnecessary external network communication.

13.3 Aetherstars may support multiplayer games in the future.

13.4 Where Aetherstars provides approved multiplayer infrastructure, Developers may be required to use that infrastructure according to Aetherstars' technical requirements.

13.5 Aetherstars may require multiplayer games to use Aetherstars-controlled or Aetherstars-approved infrastructure where necessary to protect player privacy and security.

13.6 Aetherstars may reject a multiplayer game if its architecture requires prohibited tracking, uncontrolled third-party data collection, payment functionality, or other functionality inconsistent with Aetherstars' requirements.

13.7 Aetherstars does not guarantee that every multiplayer architecture or feature will be supported.

14. Security, Malware & Technical Review

14.1 Every submitted game is manually reviewed before publication.

14.2 Aetherstars may inspect, test, execute, scan, and analyse submitted games for purposes including:

• malware detection;
• security;
• compatibility;
• prohibited network communications;
• tracking;
• analytics;
• privacy compliance;
• payment or monetization compliance;
• harmful functionality;
• inappropriate content;
• intellectual-property concerns;
• licensing concerns; and
• compliance with this Agreement.

14.3 Aetherstars may use automated security and technical tools in addition to human review.

14.4 Aetherstars may inspect the game and its files for security and compliance purposes without acquiring ownership of the game.

14.5 Aetherstars will not intentionally change a game's creative content or gameplay design merely because it prefers a different design.

14.6 Aetherstars may perform technical processing reasonably necessary to operate, secure, package, store, distribute, and support a game.

14.7 If a game contains an apparent accidental issue that violates an Aetherstars requirement, Aetherstars may notify the Developer and request a corrected submission.

14.8 For example, if a Developer accidentally leaves an analytics library in a submission, Aetherstars may request its removal and a corrected build.

14.9 Where Aetherstars reasonably believes a Developer intentionally included malware, spyware, prohibited tracking, hidden data collection, payment systems, or other malicious or prohibited functionality, Aetherstars may reject the game immediately.

14.10 Serious or intentional violations may result in suspension or termination of the Studio Account.

15. Content Requirements

15.1 Games submitted to Aetherstars must comply with the Jullow Terms of Service and this Agreement.

15.2 Aetherstars may reject games containing content that is:

• illegal;
• exploitative;
• excessively or gratuitously violent;
• sexually explicit;
• pornographic;
• hateful;
• abusive;
• intended to facilitate criminal activity;
• harmful to minors;
• malicious;
• fraudulent;
• deceptive; or
• otherwise incompatible with Aetherstars' safety and content standards.

15.3 Aetherstars may consider age ratings and content classifications when reviewing games.

15.4 Developers must provide accurate information about the intended audience and content of their games when requested.

15.5 Aetherstars does not reject games merely because of:

• artistic style;
• pixel-art style;
• colour choices;
• genre;
• difficulty;
• visual direction; or
• other subjective creative characteristics.

15.6 Aetherstars may nevertheless reject content that violates the requirements of this Agreement regardless of artistic style.

16. Copyright, Intellectual Property & Third-Party Rights

16.1 Developers must not submit games that infringe another person's intellectual-property rights.

16.2 This includes, without limitation:

• artwork;
• music;
• sound effects;
• source code;
• characters;
• stories;
• fonts;
• models;
• textures;
• logos;
• trademarks;
• videos;
• photographs; and
• other protected materials.

16.3 Developers may use third-party materials where they have valid permission or a license allowing the use and distribution required by Aetherstars.

16.4 Developers are responsible for complying with applicable license conditions, including attribution requirements.

16.5 Developers must not represent third-party material as their own when they do not have the necessary rights.

16.6 If Aetherstars receives a credible copyright or intellectual-property complaint concerning a game, Aetherstars may investigate.

16.7 Aetherstars may temporarily restrict or remove the affected game while a serious or credible claim is investigated.

16.8 If Aetherstars determines that a game infringes another person's rights, the game may be removed.

16.9 Repeated or intentional infringement may result in restrictions or termination of the Developer's Studio Account.

17. Reporting & Complaints

17.1 Aetherstars may provide reporting tools allowing users to report games or other content.

17.2 Reports may include:

• copyright;
• intellectual property;
• malware or security concerns;
• privacy or tracking;
• inappropriate content;
• illegal content;
• misleading information;
• abuse;
• technical problems; and
• other policy concerns.

17.3 A report does not automatically result in removal.

17.4 Aetherstars may investigate reports and make a decision based on the available information.

17.5 Aetherstars may request additional information from the Developer when reasonably necessary.

17.6 Aetherstars may remove or restrict content where required by law or where reasonably necessary to protect users, the Service, or the rights of others.

18. Approval, Rejection & Resubmission

18.1 Submission of a game does not guarantee acceptance.

18.2 Aetherstars may approve, reject, request changes to, or delay a submission.

18.3 Aetherstars may request that a Developer correct an issue before approval.

18.4 A Developer may resubmit a corrected version of a rejected game.

18.5 Aetherstars may provide the general reason for rejection where reasonably possible.

18.6 Aetherstars is not required to disclose confidential security information that could allow a Developer to bypass security systems.

18.7 Aetherstars may reject a game if it determines that the game does not meet its technical, privacy, security, payment, monetization, content, licensing, or other requirements.

18.8 Aetherstars may reject a game even if the game is technically functional.

19. Game Updates & New Versions

19.1 Developers may submit updates to accepted games through their Studio Account.

19.2 Updated versions may be reviewed before being published.

19.3 Aetherstars may require a new review when an update significantly changes:

• gameplay;
• networking;
• data collection;
• external services;
• monetisation;
• payment functionality;
• content;
• age rating;
• permissions;
• technical requirements; or
• other important functionality.

19.4 Aetherstars may continue distributing an earlier approved version temporarily while an update is under review where technically possible.

19.5 Aetherstars may require a Developer to update a game if an older version becomes incompatible, insecure, or non-compliant.

20. Developer Removal of an Individual Game

20.1 A Developer may request removal of any individual game through their Studio Account or by contacting Aetherstars.

20.2 Removing an individual game does not automatically delete the Developer's Studio Account.

20.3 Once an individual-game removal request is processed, Aetherstars will remove the game from active distribution.

20.4 Aetherstars will make reasonable efforts to remove the game from active hosting and distribution systems.

20.5 Removal may take some time to propagate across caches, storage systems, backups, and other technical infrastructure.

20.6 The game will not continue to be offered to players as an actively available Aetherstars game after removal has taken effect.

20.7 Previously published promotional materials may remain available as described in Section 11.

21. Studio Account Deletion

21.1 A Developer may request deletion of its Aetherstars Studio Account.

21.2 Deleting a Studio Account begins the Aetherstars account recovery and deletion process.

21.3 The Studio Account will enter a 30-day recovery period, consistent with the Jullow ecosystem's account deletion approach.

21.4 During the 30-day recovery period:

• a) the Studio Account will be inaccessible or restricted as applicable;
• b) games associated with the Studio Account will be removed from active Aetherstars distribution;
• c) players will no longer be able to obtain the removed games as normally available Aetherstars downloads; and
• d) Aetherstars may retain the account and game data necessary to restore the Studio Account if the Developer cancels the deletion during the recovery period.

21.5 If the Developer restores the Studio Account within the 30-day recovery period, the Developer may be able to restore its associated Aetherstars information and games, subject to technical availability and any changes to Aetherstars requirements.

21.6 If the 30-day recovery period expires without restoration, the Studio Account deletion becomes permanent.

21.7 After the 30-day recovery period, Aetherstars will permanently delete the Studio Account's personal and account data from active systems in accordance with the applicable Jullow Privacy Policy and Aetherstars deletion procedures.

21.8 Aetherstars will also begin the permanent deletion of the Studio's game files and associated technical copies from active systems and backups according to its normal deletion processes.

21.9 Because backups, caches, redundancy systems, and disaster-recovery systems may retain data temporarily, complete removal from every technical copy may take additional time.

21.10 Aetherstars will not intentionally continue distributing the Studio's games after the Studio Account deletion has taken effect.

21.11 Previously published promotional materials may remain available as described in Section 11 unless removal is required by law or Aetherstars otherwise chooses to remove them.

22. Aetherstars Removal of a Game

22.1 Aetherstars may remove or suspend a game where it reasonably believes that:

• the game violates this Agreement;
• the game violates the Jullow Terms of Service;
• the game contains malware;
• the game contains prohibited tracking;
• the game contains undisclosed data collection;
• the game contains prohibited payment or monetization functionality;
• the game infringes third-party rights;
• the Developer does not have necessary rights to distribute the game;
• the game creates a significant security risk;
• the game contains prohibited content;
• the Developer provided materially false information;
• the game no longer meets technical requirements;
• removal is required by law; or
• removal is otherwise reasonably necessary to protect Aetherstars or its users.

22.2 Where the issue appears to be an honest or accidental mistake, Aetherstars may give the Developer an opportunity to correct the issue and resubmit the game.

22.3 Where Aetherstars reasonably believes that a violation was intentional, malicious, fraudulent, or designed to circumvent Aetherstars' privacy, security, payment, or other protections, Aetherstars may immediately reject or remove the game.

22.4 Removal of one game does not automatically terminate the Developer's entire Studio Account.

22.5 Aetherstars may take additional action against the Studio Account where violations are repeated or serious.

23. Studio Account Enforcement

23.1 Aetherstars may take action against a Studio Account for violations of this Agreement.

23.2 Depending on severity and circumstances, enforcement may include:

1. warning;
2. request for correction;
3. rejection of a submission;
4. temporary restriction;
5. removal of one or more games;
6. suspension of submission privileges;
7. suspension of the Studio Account; or
8. permanent termination of the Studio Account.

23.3 Aetherstars may skip intermediate steps where a violation is sufficiently serious.

23.4 A single rejected game does not automatically mean that the Studio Account will be terminated.

23.5 Repeated serious or intentional violations may result in permanent termination.

23.6 A Developer whose Studio Account has been permanently terminated may not create another Studio Account to evade the termination.

24. Studio Profile

24.1 A Studio may have a public Studio Profile on Aetherstars.

24.2 A Studio Profile may contain:

• Studio name;
• Studio logo;
• Studio description;
• official website;
• games available through Aetherstars; and
• other public information supported by Aetherstars.

24.3 Developers are responsible for ensuring that Studio Profile information is accurate and does not impersonate another organisation or person.

24.4 Aetherstars may remove or restrict profile information that violates this Agreement.

24.5 A Studio may update its profile through its Studio Account where the functionality is available.

25. No Exclusivity

25.1 Submitting a game to Aetherstars does not require the Developer to publish the game exclusively through Aetherstars.

25.2 Developers may distribute the same game through other platforms.

25.3 Developers may publish through platforms including:

• Google Play;
• Steam;
• the Developer's own website;
• other game stores;
• other app stores; and
• other distribution services.

25.4 Developers may choose to make a particular game exclusive to Aetherstars if they separately wish to do so and Aetherstars agrees.

25.5 No exclusivity exists unless expressly agreed in writing.

26. Developer Promotion Outside Aetherstars

26.1 Developers remain free to promote their games outside Aetherstars.

26.2 Developers may advertise or sell their games through their own websites and other platforms, subject to applicable laws and those platforms' rules.

26.3 Developers may offer premium versions, expansions, additional maps, quests, merchandise, subscriptions, or other products outside Aetherstars.

26.4 Developers may state that their game is available on Aetherstars.

26.5 Developers must not falsely state that Aetherstars provides a product, premium version, feature, or service that it does not provide.

27. Player Accounts & Developer Access to Players

27.1 Players use their Aetherstars Account to access games through Aetherstars.

27.2 A Developer does not receive direct access to a player's Aetherstars Account.

27.3 Developers do not receive player email addresses, phone numbers, account identifiers, or other personal account information merely because a player plays their game.

27.4 Developers do not receive a list of players who have played their game.

27.5 Developers do not receive player gameplay analytics from Aetherstars.

27.6 Aetherstars may maintain technical information necessary to provide player accounts, game progress, security, and other Aetherstars features in accordance with the Jullow Privacy Policy and applicable policies.

28. Game Saves, Progress & Player Data

28.1 Where Aetherstars provides game-save or progress functionality, that functionality may use Aetherstars infrastructure or other infrastructure approved by Aetherstars.

28.2 A Developer must not independently export or collect player progress from Aetherstars users unless expressly permitted by Aetherstars.

28.3 Aetherstars may store game-related progress or technical information necessary to provide Service features.

28.4 Developers may design gameplay systems that store local or Aetherstars-supported game data, subject to Aetherstars' technical requirements.

29. Security & Privacy Requirements May Change

29.1 Aetherstars may introduce additional security, privacy, payment, monetization, or technical requirements as the Service develops.

29.2 Developers may be required to update existing games to comply with new requirements.

29.3 Aetherstars may temporarily restrict a game while the Developer updates it.

29.4 Aetherstars will make reasonable efforts to communicate significant changes to Developers.

30. Service Availability

30.1 Aetherstars will make reasonable efforts to keep the Service available but does not guarantee uninterrupted availability.

30.2 The Service may experience:

• maintenance;
• technical failures;
• server outages;
• security incidents;
• infrastructure changes;
• compatibility problems; or
• other interruptions.

30.3 Aetherstars may temporarily disable a game where necessary for maintenance, security, compatibility, or legal reasons.

31. Disclaimer

31.1 Aetherstars does not guarantee that a submitted game will generate downloads, users, revenue, publicity, or other benefits.

31.2 Aetherstars does not guarantee that a game will remain available indefinitely.

31.3 Aetherstars does not guarantee compatibility with every device or future version of an operating system or Godot Engine.

31.4 Aetherstars is not responsible for the creative content, code, assets, claims, representations, or functionality of a Developer's game except to the extent required by applicable law.

31.5 The Developer remains responsible for the game they submit.

32. Developer Responsibility & Indemnification

32.1 The Developer is responsible for ensuring that the game:

• complies with applicable law;
• complies with this Agreement;
• complies with applicable Jullow policies;
• uses properly licensed content;
• does not infringe third-party rights;
• does not intentionally contain malware;
• does not intentionally track Aetherstars users;
• does not contain prohibited payment or monetization functionality;
• does not contain prohibited advertising;
• does not contain prohibited functionality; and
• accurately represents its content and functionality.

32.2 To the maximum extent permitted by applicable law, the Developer agrees to indemnify and hold harmless the person or entity lawfully operating Aetherstars from claims, damages, losses, liabilities, and reasonable expenses arising from:

• the Developer's breach of this Agreement;
• infringement caused by the Developer's game;
• unlawful content contained in the game;
• the Developer's lack of rights to distribute the game; or
• intentional misuse of Aetherstars.

32.3 This provision does not exclude liability that cannot legally be excluded.

33. Changes to This Agreement

33.1 Aetherstars may update this Agreement as the Service develops.

33.2 The revised Agreement will be published with a new effective date.

33.3 Where appropriate, Developers may be notified through their Aetherstars Studio Account or the email address associated with the account.

33.4 Aetherstars may require Developers to accept an updated version of this Agreement before submitting additional games or updates.

33.5 Previously accepted versions may be retained for record-keeping purposes.

34. Relationship With Jullow

34.1 Aetherstars is currently a project operated within the Jullow ecosystem.

34.2 Jullow's ecosystem-wide Terms of Service, Privacy Policy, and Cookie Policy apply to Aetherstars.

34.3 This Developer Agreement provides additional rules specific to Aetherstars Developers and Studios.

34.4 The organisational structure of the Jullow ecosystem may change in the future.

34.5 Such changes may include the creation of separate legal entities, companies, subsidiaries, or other organisational structures.

34.6 Aetherstars may update this Agreement and related policies when such changes occur.

35. Governing Law & Dispute Resolution

35.1 This Agreement is governed by the laws of the Hellenic Republic (Greece) and applicable European Union law.

35.2 Developers and Aetherstars submit to the non-exclusive jurisdiction of the courts of Greece for disputes arising under this Agreement, subject to any mandatory rights provided by applicable law.

35.3 Nothing in this Agreement removes any mandatory legal rights or protections that cannot lawfully be excluded.

36. Severability

36.1 If any provision of this Agreement is found to be invalid or unenforceable, the remaining provisions will continue to apply to the maximum extent permitted by law.

37. Entire Agreement

37.1 This Developer Agreement, together with the applicable Jullow Terms of Service, Privacy Policy, and Cookie Policy, constitutes the applicable agreement governing the Developer's use of Aetherstars developer features.

37.2 The Developer's ownership of their game is not transferred to Aetherstars by this Agreement.

38. Contact

For developer submissions, developer support, copyright reports, privacy concerns, security reports, or questions regarding this Agreement:

info@aetherstars.com