Terms of Use

Project creators and owner, hosting, and contact

Plaryn.com is the brand and project created, built and owned by the creators acting as Plaryn Team. Plaryn Team is a creative team designation, not a separately registered legal person. Hosting the website on Bomega infrastructure does not give Bomega ownership of the project or brand.

Technical hosting and support for Plaryn.com are provided by BOMEGA spółka z ograniczoną odpowiedzialnością (BOMEGA Sp. z o.o.), Długa 2B, 56-416 Twardogóra, Poland, KRS 0000841054, NIP 9112034523, REGON 386056613. Bomega hosts the service on its servers and performs related technical data operations. Hosting alone does not make it the project owner, the contractual service provider to users or the personal data controller.

Contact for hosting and technical assistance: [email protected]. Plaryn Team creates and owns the project, while Bomega provides hosting and technical operations.

Plaryn Team is the creative team designated by the owner as the creator and owner of the project and brand. Economic rights to particular works, software and games follow actual authorship, contracts and licences; users who submit games retain their lawful rights. Bomega does not acquire any rights to Plaryn.com, its brand, code or games merely by hosting them.

Detailed rules for the functions and rights covered by this document. The provisions distinguish currently available features from options not yet enabled for paid orders.

Scope, definitions and available services

Plaryn is an online platform for discovering games, presenting creators and projects, participating in Game Jams and using account-based community functions. A User is a visitor or registered member. A Creator develops or submits a game project. A Game Card publicly describes a title, and a Release identifies a particular approved package or version of that title. Separate functions may require an account, role-based permission and an enabled service. A catalogue presentation is not automatically a commercial offer.

Public browsing of Discover, game cards and general platform information normally does not require an account. Studio, account libraries, team administration, project submissions and some support or moderation operations require authentication. A visible preview of a planned feature is not proof that it is available. Demonstration and QA resources must be distinguished from approved releases meant for general players. The applicable access state depends on the specific screen, publication process and these Terms.

Current features and limits

Plaryn presents Discover, Studio, Teams, Game Jams, Marketplace, Trust Center and other public areas. Some currently provide information and previews rather than every advertised operation. Not every title can be launched in a browser, and a game card does not guarantee an enabled file download. A person should distinguish information about a future feature from a service actually available now and not treat an informational panel as a promise of permanent access.

The public Marketplace does not currently accept binding paid orders, although showcase assets may be viewed. Commerce-related interfaces do not change this. Browser Play, downloads and distribution may be subject to separate technical and entitlement controls. If a paid service becomes available, the real seller, price, product characteristics and relevant consumer information must be supplied before a person is obliged to pay.

Registration and accurate information

Accounts are created through the available registration process, including email verification where required. Members should provide information needed to operate their accounts and must not impersonate other people, studios or publishers. The permissions associated with an Account are limited to the relevant features. Applicable parental or guardian-consent requirements depend on the user's age, the activity and the law. Registration does not confer a right to distribute material that is prohibited by law or these Terms.

Passwords, reset links, verification codes and authenticated sessions must be protected. Sharing an Account creates risks for unpublished games, personal libraries and private reports. Someone who suspects unauthorised access should secure the associated email inbox, use the official recovery mechanism and notify support. Proportionate security checks, including re-authentication or temporarily limiting a sensitive operation, may be applied where there is a credible threat.

Public creator profiles and identity

A public Creator profile may display a chosen name, biography, image, published projects and links supplied for publication. Public display names need not match private sign-in identifiers or contact details. Creators must have permission for names, trademarks, photographs and other elements they choose to display. They must not falsely claim employment, ownership of another game or a partnership with an unrelated company.

Displaying a Creator publicly does not automatically disclose registration details, support requests, draft files or internal moderation records. A name, image or external link may permit a person to be identified, which should be considered before publishing. Members of a shared studio profile should agree how their contributions and rights will be represented. Profile changes do not by themselves amend future contractual seller details or legal ownership of particular works.

Discover, search and result ranking

Discover allows visitors to browse game cards and apply the categories, search terms and filters offered by the interface. Result ordering can reflect search relevance, selected parameters, publication status, metadata or other displayed factors. A listing position is a method of organising information, not a guarantee of quality, legality, availability or a right to preferential exposure. The visible catalogue can change following a new release, a description correction or a moderation decision.

Search results may be paginated or exclude titles that are not available to the current User. Absence from one results page does not prove permanent deletion. Unauthorised bulk extraction of the catalogue or attempts to circumvent query restrictions are not permitted. If paid promotion affecting ranking is introduced, its commercial nature and the relevant ranking information must be disclosed in the manner required by applicable law.

Game cards and release descriptions

A Game Card can contain its title, description, screenshots, cover art, genre, Creator, supported languages, platform requirements, version details and accessibility or delivery information. The Creator is responsible for supplying accurate statements and securing rights to displayed materials. Unsupported compatibility or features must not be advertised as present. Before relying on a listing, Users should read its current release state and access labels.

Marketing screenshots may not show every feature of the latest Release. Material technical requirements and known limitations should be communicated where relevant. Plaryn can request correction of misleading information, limit exposure or pause a Release while investigating a credible problem. Approval of a Game Card is not a guarantee of universal device compatibility or a certification of every third-party licence used in the game.

Creator Studio and project control

Studio allows authorised Creators to manage supported project details, assets, versions and submission workflows. Available actions depend on account roles, the state of a project and the features actually enabled. Creating a Draft does not publish a game or grant players access to its files. Submitted information must describe a real project and respect applicable intellectual-property and privacy rights.

Draft builds, review submissions, approved packages and public Releases are separate stages. Creators should maintain independent copies of source code, media and licence records, because Plaryn is not the sole archive for a project. Team access should be limited to authorised tasks. Changes in team membership, rights disputes or safety concerns can justify reviewing a member's access to specific materials.

ZIP uploads and file safety reviews

When creator-upload functionality is enabled, packages may be subject to limits on size, file count, archive structure, accepted types and integrity checks. The platform may place uploads in a private staging area, verify checksums and scan files for security threats before any public delivery. Successful transfer or an upload reference does not mean that a file has been reviewed, approved or published.

Archives containing malicious code, unauthorised data collection, hidden credential theft or rights-infringing components are prohibited. Security scanning cannot guarantee detection of every threat and does not relieve Creators of responsibility for their products. An expired session, interrupted transfer, invalid archive or failed scan may require another submission through the official workflow. Such events do not silently authorise release of an earlier or rejected package.

Version history, review and publication

A project may have multiple Draft versions and Releases, each subject to the appropriate checks. Technical scanning, rights review and decisions about public availability are distinct steps. Approving one Release does not permit replacing its verified package with arbitrary new files. Publication history may preserve technical identifiers needed to determine which package was made available.

Creators should describe important changes and known defects. A Release may be withheld or withdrawn after discovering a security risk, licence issue or legal violation. Withdrawal does not necessarily eliminate records lawfully retained for disputes or security. An 'approved' status confirms completion of a particular process, not a guarantee that software is error-free, compatible with every computer or permanently available.

Browser-based Play

Where a Game and Account have an enabled browser runtime, Plaryn may issue limited access to approved assets and check the player's relevant entitlement. Browser Play may use short-lived session tickets and a separate resource origin. It depends on a compatible browser, JavaScript, an internet connection and a published package. Not every catalogue title currently supports public browser Play, and a preview button does not itself create an entitlement.

Creators must not use browser games to harvest passwords, access unrelated accounts or perform unauthorised operations. Players must not expose session tokens, evade restrictions or copy restricted packages through an access ticket. Performance depends on the browser, device, game files and connection. A malfunction can be reported with the game reference and general incident time rather than with private authentication credentials.

Downloads and device protection

Some games may provide an approved installable file or archive, but actual availability depends on publication state, technical feature gates and account permissions. A platform icon or download preview does not prove that a downloadable build currently exists for every system. Players should read the Creator's licence and requirements. Downloading does not transfer copyright in code, artwork or other game materials.

Users should obtain packages through authorised channels, observe operating-system warnings and keep appropriate device protection. The Service can stop distributing a damaged, unsafe or withdrawn file. Scanning performed by the platform does not replace basic security practices. Downloads must not be used to circumvent entitlement checks or share private builds with unauthorised people.

Personal libraries and entitlements

An Account Library can show followed games, saved selections and the status of particular access permissions. Adding a Game to a Library is not automatically a purchase, a transfer of intellectual property or an unlimited right to all download formats. Availability can change when a Release is withdrawn, account rights change or catalogue content is removed. Some selections can also be stored locally on the device.

Members should distinguish wish lists or saved items from paid purchase confirmations, which are not currently issued by the public checkout. A previously followed title may later be unavailable for legitimate security or licensing reasons. Library and entitlement errors can be reported through an authorised support channel. A person's private Library must not become visible to others merely because they follow the public Creator profile.

Cloud Save and gameplay progress

Where a Game and the relevant Service support Cloud Save, stored progress can be linked to an Account, Game identifier, data-format version and save timestamp. The Service may impose size or record-count limits and verify the right to read, overwrite or remove data. Creators are responsible for compatibility of their save formats across game updates. Not every Game supports cloud saves, and changes on a device are not necessarily synchronised automatically.

Clearing browser cookies, signing out or removing a followed Game does not necessarily erase separate server-side saves. Users should review available export and deletion controls and protect their devices. Game-save fields must not be used as a vault for passwords, other people's files or unrelated private information. Compatibility problems can be reported without disclosing unnecessary personal data.

Game Jams and event conditions

The Game Jams section can display planned, completed or currently active events. A page may remain visible when no Jam is open for submissions. Eligibility, deadlines, categories and judging depend on the published rules of the particular event, its status and the participant's Account permissions. Submitting a Game does not guarantee a prize, public Release or special placement.

Organisers should publish relevant eligibility and assessment rules, including any prizes and rights needed to display entries, before accepting participation. Taking part does not automatically transfer the Creator's copyright to Plaryn or other entrants. Team members must organise ownership of their own contributions. A Jam result is not equivalent to completion of the technical security and publication process for a Game package.

Teams and collaborative projects

Teams supports public presentation of groups and collaboration opportunities and may provide authenticated tools for membership and project roles. Joining a Team does not automatically create an employment relationship, partnership or assignment of copyright. Collaborators must independently agree on contributions, remuneration, access and use of jointly created materials unless a separate valid agreement already governs those matters.

Team permissions should be limited to relevant tasks. Access controls must not be bypassed to read another member's private files, messages or unpublished code. Departure from a team may require changes to permissions but does not itself determine ownership of work already created. Plaryn is not a party to every private collaboration agreement and does not automatically resolve all authorship disputes among collaborators.

Marketplace showcases and assets

The Marketplace can show sample resources, creative assets and previews for game production. The current public experience does not operate a binding paid order flow, so opening a card, following a resource or comparing a preview does not purchase it. Descriptions may refer to possible future asset licences without presently granting those commercial rights. A resource displayed in the Marketplace is not automatically approved for redistribution or reuse in another product.

If purchases are introduced, the actual Seller, scope of licence, usable formats, total price, taxes, delivery process and applicable purchaser rights must be made clear before an order is binding. Asset Creators must hold the required rights to all components they offer. Viewing thumbnails and descriptions does not permit copying them to other platforms, removing mandatory attribution or reselling the underlying file.

Payments and unavailable checkout

Plaryn does not currently accept new paid Game or asset orders through a live public checkout. Commerce pages, prospective price displays and planned purchase flows do not themselves form a contract of sale. Accessing public catalogue pages or registering for an Account does not incur a payment obligation. Members should not provide card details to anyone claiming that an unexpected payment is necessary to activate ordinary catalogue browsing.

If paid digital services become available, Users must receive the actual Seller's identity, applicable currency, total price and taxes, payment arrangements, content or licence being supplied and any recurring charges before becoming bound to pay. Legal withdrawal and conformity rights remain governed by the relevant law and the separate Refund and Withdrawal Policy. Merely opening a product page cannot be treated as consent to lose a statutory withdrawal right.

Creator rights and limited operational licence

Creators retain copyright and other intellectual-property rights they lawfully own in Games, artwork, code, music, descriptions and related resources. Uploading a Game does not assign those rights to Plaryn Team or Bomega. To the extent necessary to provide the chosen platform functions, the Creator gives a non-exclusive permission to store, scan, technically process, review, display and deliver the submitted material in accordance with its publication status and enabled settings.

This permission is not an unlimited right to reuse the Creator's work in unrelated commercial products or sell its source code independently. Creators must have the licences, permissions and consents needed for third-party components. They should comply with open-source obligations, image licences, font permissions and other applicable restrictions. A credible co-author dispute or third-party claim can justify temporarily withholding a particular Release while the issue is assessed.

Player licence and access limits

Viewing a Game Card or gaining the ability to launch a Game does not transfer copyright or ownership of the product. Players may use it to the extent permitted by the enabled Plaryn functions and the actual Creator's licence. Where a title has separate licence terms, those should be available before the action they govern and must not remove statutory rights that cannot lawfully be waived.

Without permission, Players must not redistribute copies, share restricted files, remove copyright notices or present an unofficial build as the Creator's authorised Release. Statutory rights concerning permitted uses, interoperability and other applicable exceptions remain intact. Access to an executable Game is not a promise that it will run on every present or future operating system.

Third-party libraries, brands and open source

Games may incorporate open-source components, external graphics, fonts, audio libraries and other licensed resources. Creators and Users must respect their actual licences, including obligations regarding attribution, licence notices and source access when applicable. Hosting a ZIP does not transfer those third-party rights to Plaryn. A Creator should keep sufficient records of materials used so that legitimate infringement concerns can be evaluated.

Names and marks must not misleadingly suggest that a Game is an official Release or endorsed by another publisher. A rights complaint should identify the specific work and the grounds of the claim. Removal or correction of an infringing file may be necessary before a new submission. A dispute does not itself give the complainant ownership of the Creator's entire project.

Reviews, comments and honest feedback

Where ratings, reviews or comments are enabled, members should describe their genuine experience or a reasoned view of the Game. Impersonation, fabricated reviews, harassment, phishing and publication of private information are prohibited. A User's review reflects that person's opinion rather than necessarily the official view of Plaryn or the Game Creator.

A report about a review may lead to moderation where it contains threats, spam, exposed personal data or other rule violations. Creators must not pressure Players for positive ratings or punish lawful criticism. The way reviews are sorted or checked must reflect the actual Service; a review should not be described as a verified paid purchase where the public checkout is not operational.

Community behaviour and collaboration

Plaryn community features require respect for others, their privacy and their works. Members must not use profiles, teams, comments or messages for threats, targeted harassment, unlawful discrimination, spam, fraud, unauthorised advertising or credential theft. Illegal exploitation material, particularly involving minors, and malicious software are prohibited. Discussion of a Game's quality can be critical without exposing its Creator's private details.

Collaboration offers should honestly describe skills, contributions and any proposed terms; they must not claim guaranteed employment or funding without evidence. Reported conduct can lead to proportionate action under the Community Guidelines. Legitimate differences of opinion or dissatisfaction with a Game do not, by themselves, justify an account ban or the disclosure of personal information.

Illegal-content and rights reports

Trust Center and relevant content tools allow reports about potentially illegal material, security threats and infringement of third-party rights. Reports should identify the precise URL, Game or file, the nature of the issue and information reasonably needed to review it. Complainants should not be required to supply unnecessary personal data or passwords; copyright claims may require information showing the protected work and relevant rights.

Reports are assessed according to the identified material, available evidence and the applicable duties of the feature. A notice is not automatic proof of illegality. Where Regulation (EU) 2022/2065 governs the relevant intermediary service, its applicable notice, statement-of-reasons and redress requirements must be observed. Immediate threats to life or safety must also be reported to the competent emergency authorities.

Moderation and proportional measures

Plaryn may limit a listing, withdraw a file, request correction or restrict publishing where there are appropriate legal, safety or rights-related grounds. Decisions should consider the nature and severity of the breach, context and whether a less restrictive measure is sufficient. A mistaken description and distribution of malicious code are not equivalent violations and need not lead to identical outcomes.

Where required by law, affected Users receive relevant reasons and information about available challenges. Removing material from a public page does not necessarily erase security or dispute records that may lawfully be retained. Creators may be asked to provide evidence of licences through a private channel without unnecessary disclosure of that information to other Players.

Appeals and reconsideration

A person affected by an Account or content restriction can use the relevant channel to submit an explanation and evidence. They should identify the decision, explain what is disputed and provide lawful supporting information such as ownership documents, licence terms or proof of a fix. Reconsideration does not guarantee reinstatement when a material violation remains.

Internal review does not eliminate statutory rights to judicial proceedings or other available out-of-court remedies, including those applicable under the DSA. Notices concerning illegal content should be distinguished from ordinary customer-support reports about software errors. Repeated bad-faith complaints intended to suppress competitors may themselves breach these Terms.

Private information and session security

Authentication records, private drafts, account support messages and moderation evidence should only be accessible to authorised people for legitimate purposes. Users must not attempt to access another person's data, tamper with session tokens, exploit security defects or expose someone else's private information publicly. A support report should not require sharing a password or complete identity-document number without a specific lawful necessity.

Following a suspected breach, the Service may invalidate sessions, limit particular operations and require re-authentication where appropriate. Personal-data requests are governed by the Privacy Notice. Security requirements apply even when a Game has not been released publicly, and creator teams should protect drafts and account permissions accordingly.

Automation, crawling and APIs

Unauthorised mass collection of listings, copying protected assets, evading rate limits, overwhelming APIs, testing unrelated credentials or scanning infrastructure without permission are prohibited. Automation permitted by a documented interface must follow its stated purpose and limits. Public visibility of a Game Card does not imply consent to reconstruct the complete Service database.

Rate controls, session checks and other technical measures protect everyone using Plaryn. Credible abuse may lead to proportionate request restrictions. Security concerns should be reported through support without obtaining other people's data as evidence or publishing instructions that enable exploitation.

Availability, backups and loss of data

Access depends on networks, hosting, authentication services, security controls and some external integrations. Maintenance, outages and removal of unsafe files may temporarily affect a function. The Service seeks reasonable continuity but cannot guarantee permanent availability of every independently developed Game, third-party provider or User connection.

Creators should keep independent backups of source code and assets. Players should confirm that gameplay has been saved when they wish to resume later. Platform backups support service recovery and may not restore every unsaved action. Nothing in these Terms excludes liability or mandatory duties to the extent their exclusion is prohibited by law.

Account closure and records

Users may stop browsing public pages, sign out and use available privacy settings. A request to close an Account may require appropriate verification of the requester's authority, especially when it concerns Teams, published projects and moderation records. Ending access to Account features can affect private drafts, saved items and entitlements, subject to the actual function and applicable agreement.

Some records may lawfully remain for a limited period to meet legal obligations, protect legitimate claims or maintain security. Data-subject rights are explained in the Privacy Notice. Closing a Creator Account does not automatically assign copyright in existing Games to someone else or extinguish the rights of contributors and third-party owners.

Service complaints and support

Technical complaints may concern sign-in, catalogue visibility, personal libraries, Studio access, upload status, Game Saves and content decisions. A useful request identifies the affected feature, event time, URL, expected result and means of reply. Authenticated Support may require a valid Account; [email protected] is a technical contact and forwarding channel for the appropriate handling team.

Users should not send passwords, session tokens, other people's data or complete private packages unless specifically and lawfully required. Complaints are handled under applicable legal time limits and mandatory consumer protections. A complaint about Plaryn functionality is not necessarily a complaint against the separate Creator of an independent Game, unless the law or the relevant agreement establishes that relationship.

Consumer rights, amendments and disputes

These Terms do not exclude mandatory rights under consumer, digital-content, privacy or electronic-service law. If paid sales are introduced, withdrawal and conformity rights depend on the nature of the transaction and the real Seller. Public catalogue browsing alone does not turn a visitor into a buyer. No user is required to waive statutory rights merely to raise a genuine complaint about an Account or a Game.

Material changes to the Terms should be communicated in the manner required for the specific service and cannot retroactively extinguish acquired rights. Invalidity of one provision does not necessarily invalidate the remainder to the extent allowed by law. Legal disputes may be addressed through competent courts and any applicable out-of-court channels, respecting jurisdiction and mandatory consumer protection rules.

Following Creators and notifications

Following Games or Creators can help Members receive information about selected updates or changes in availability where the feature is enabled. Following is a choice that can be changed in the relevant settings. It does not grant access to private Creator drafts or every Team record. Notifications can require an active Account or the appropriate device permission.

Not receiving a notification does not prove that a Game was never updated. Delivery depends on account settings and technical availability. Functional messages about followed resources should be distinguished from unsolicited marketing. A private list of followed Games should not become publicly visible merely because the User chose to follow them.

Game bug reports and fixes

Where the relevant tool is available, Users can report problems with gameplay, browser launches, downloads or a particular Game description. Useful reports identify the version, approximate time, system and reproducible behaviour. Passwords and another person's private saves must not be included. Creators can receive information necessary to investigate the Game without unnecessary disclosure of the reporter's private data.

A planned fix is not a guarantee of delivery on a particular date. A corrective Release may require renewed security review and approval. Closing a technical report does not automatically settle a legal complaint about conformity with a paid contract, if such a contract is offered in the future.

Languages and accessibility

Catalogue information, Help and Creator documentation can be available in different language versions, including Polish and English. Individual Games may not offer identical translations, captions, controller support or accessibility features. Creators should accurately describe what their actual Release supports so Players can evaluate compatibility and their needs.

Accessibility barriers can be reported through the available support channel with the relevant page, device or interaction method. Applicable legal accessibility requirements remain relevant. Planned features must not be presented as fully available solutions to people who depend on them now.

Age classifications and sensitive content

Games can contain violence, strong visual effects, mature themes or other content that needs appropriate notices or access restrictions. Creators are responsible for accurate classification and should not conceal significant content characteristics. The Service may review content labels where justified by safety or legal duties.

Guardians should consider the available age and content information. A User declaration is not always equivalent to independent age verification. Unlawful material, especially exploitation of children, is prohibited regardless of age classification. Where stronger checks are legally required, actual access controls must meet those obligations.

Public comments and Creator responses

Where enabled, comments and replies on Game Cards or profiles become public to the extent indicated by the interface. Users must not disclose passwords, private addresses, confidential project code or unrelated personal information. Removing a comment can change its public visibility without necessarily deleting lawfully retained security or reporting records.

Creators may answer legitimate criticism and explain Game behaviour but must not threaten Players or expose their data to suppress lawful reviews. Spam and fabricated interactions can be restricted. Honest discussion of bugs and accessibility should not automatically be treated as abusive conduct.

Team administrators and project access

A Team administrator exercises only the permissions provided by Plaryn and legitimately agreed with collaborators. The role does not automatically assign another Contributor's copyright or justify demanding their personal password. A role change can allow access to particular resources but must remain within the person's actual authority.

Credible ownership disputes can justify temporarily restricting high-risk operations to protect a project, but that does not decide the underlying private contract. Contributors should document rights to their shared files. Technical support is not a substitute for professional legal resolution of authorship agreements.

Withdrawn Releases and older links

A Creator or authorised reviewer can withdraw a Release for legitimate reasons such as a security vulnerability, rights dispute or serious defect. Historical URLs may then display a withdrawal notice, redirect or become unavailable. The continued presence of an older card in an outside search engine does not establish an entitlement to obtain a withdrawn package.

Restoring availability may require a new submission and independent review. Users must not reuse archived tickets or unofficial mirrors to bypass a safety decision. Limited withdrawal history can be retained for process integrity and lawful claims.

External websites and Game integrations

Game Cards and Creator profiles can link to social platforms, project websites or third-party documentation. Following an external link generally places the User under the separate provider's terms. Plaryn is not automatically responsible for every action on unrelated websites, without excluding non-waivable statutory duties.

Creators must not use outbound links to direct Players to fraudulent payments or credential-collection sites. Reports about unsafe links should identify the relevant card and URL. Where an integration involves data sharing, the actual scope and legal basis must be assessed and communicated under applicable law.

Game safety and Creator responsibilities

Creators are responsible for the legal and licensed status of code and assets they submit and for accurate product information. Packages must not contain undisclosed data harvesting, hidden advertising or unauthorised device operations. Submission for review does not remove the Creator's own duty to build software responsibly.

Plaryn can restrict unsafe Releases and verify file integrity, but approval is not a guarantee that every vulnerability has been discovered. Players should keep their devices updated and observe system warnings. Mandatory legal rules governing actual services take precedence over general statements about software risks.

Creator marketing and disclosure of advertising

Creators may use covers, trailers and previews for which they have suitable rights. They must not advertise nonexistent features as completed, misuse another party's brand or conceal paid advertising where disclosure is required. Marketing assets must not be used to bypass technical publication restrictions.

Prominent catalogue placement is not automatically proof of paid promotion. If commercial ranking features are introduced, important ranking information and the promotional nature of paid exposure should be explained appropriately. Functional recommendations should not be confused with undisclosed advertising.

Account data after leaving a Team or removing a Game

Removing a visible Game, followed title or Team membership can affect access to functions, but does not necessarily erase every Account record. Retention depends on the purpose, other people's rights and justified legal or security obligations connected with publication history.

Members can use supported privacy controls and GDPR channels to request applicable action. Creators should retain their own source copies before ending collaboration. Threats to delete an Account must not be used to unlawfully appropriate a Game or coerce Contributors into a decision.

Release changes and informing Users

Plaryn can update interface features, Account systems and publishing requirements in response to security, legal or service needs. Material changes affecting existing contractual rights should be communicated as required for the relevant service. Deploying a new feature does not mean every Account automatically receives permission to use it.

These Terms should remain available in a form Users can save and reproduce. The Polish and English versions describe the same material service conditions, and editorial differences do not remove mandatory rights. Any future paid-order terms must be provided before a binding purchase rather than only after a policy update.