ReputoNode Terms of Service

Chapter 1

General provisions

§ 1. ReputoNode

1. ReputoNode is a multilingual social networking portal available at https://reputonode.com, hereinafter referred to as “ReputoNode” or the “Portal”.

2. ReputoNode enables, in particular:

   1. creating and maintaining an Account and a public Profile;
   2. publishing and viewing Posts;
   3. saving Drafts;
   4. publishing and viewing Comments and Replies;
   5. posting photos, videos, text, links and other materials supported by the Portal;
   6. assigning Posts to thematic Categories;
   7. specifying a Location and Publication Scope;
   8. following other Users;
   9. rating Content using R+ and R− Reactions;
   10. building and displaying Users’ Topic Reputation in individual Categories;
   11. reporting Content and conduct that may violate the law, the Terms or the Community Standards.

3. Reputation displayed in ReputoNode is assigned to individual Categories and results from Reactions to Content published by the User. ReputoNode is not intended to assign one overall rating to a person.

4. The detailed scope of services available in ReputoNode and the rules for using individual functions are set out in the further provisions of the Terms.

§ 2. Subject matter of the Terms

1. These Terms set out the rules for the provision of electronic services through ReputoNode, including:

   1. the types and scope of services provided;
   2. the technical conditions for using the Portal;
   3. the rules for creating, maintaining, securing and deleting an Account;
   4. the rights and obligations of Users and the Service Provider;
   5. the rules for publishing, storing, making available and deleting Content;
   6. the rules for using R+ and R− Reactions and the operation of Topic Reputation;
   7. the rules for moderating Content and Accounts;
   8. the procedure for reporting Illegal Content and other violations;
   9. the rules for making Moderation Decisions and appealing against such decisions;
   10. the rules governing the liability of the User and the Service Provider;
   11. the procedure for submitting and handling complaints;
   12. the rules for terminating the Agreement and ceasing use of the Portal;
   13. the rules for amending the Terms.

2. The Terms are made available free of charge before the Agreement is concluded, in a manner that enables them to be obtained, saved, reproduced and retained.

3. The User may review the current Terms at any time through the Portal.

4. Use of ReputoNode requires compliance with:

   1. applicable law;
   2. these Terms;
   3. the Community Standards;
   4. rules applicable to particular functions of the Portal, where such rules have been clearly made available to the User before the User uses the relevant function.

§ 3. Persons using the Portal

1. Public parts of ReputoNode may be viewed without creating an Account and without logging in.

2. A person using the Portal without being logged in may, in particular:

   1. access the Portal’s home page;

   2. view public Posts;

   3. open public User Profiles;

   4. read Comments and Replies;

   5. view information about Users’ Topic Reputation.

3. Use without logging in does not, in particular, allow a person to:

   1. publish Posts;

   2. save Drafts;

   3. publish Comments or Replies;

   4. submit R+ or R− Reactions;

   5. follow Users;

   6. use other functions intended exclusively for Account holders.

4. A person viewing public parts of the Portal without an Account must comply with those provisions of the Terms that relate to the manner of using the Portal, security, prohibited activities, rights to Content and liability.

5. Full use of ReputoNode’s social features requires creating an Account and logging in.

§ 4. Conclusion of the Agreement

1. The Agreement is concluded between the User and the Service Provider upon proper confirmation of the e-mail address and activation of the Account, after the User has first:

   1. provided the data required in the registration form;
   2. accepted the Terms;
   3. confirmed having read the Privacy Policy;
   4. made the required declarations;
   5. met the remaining registration requirements set out in the Terms.

2. Acceptance of the Terms is voluntary, but is necessary to complete registration, activate the Account, conclude the Agreement and use functions available to logged-in Users.

3. The User should read the Terms before accepting them.

4. By accepting the Terms, the User confirms that the User:

   1. has read their content;
   2. understands the rules for using ReputoNode;
   3. undertakes to comply with the Terms and the Community Standards.

5. Detailed rules concerning registration, e-mail address verification, Account maintenance and logging in are set out in the further Chapters of the Terms.

§ 5. Community Standards

1. The ReputoNode Community Standards form an integral part of the Terms.

2. The Community Standards specify, in particular:

   1. types of Content and conduct prohibited in ReputoNode;
   2. rules for responsible publication and rating of Content;
   3. rules for preventing harassment, violence, discrimination, fraud, spam and other abuses;
   4. rules for preventing manipulation of R+, R− Reactions and Topic Reputation;
   5. possible measures taken in the event of a breach of the Portal rules.

3. Acceptance of the Terms also covers the Community Standards in the version made available to the User before conclusion of the Agreement.

4. In the event of a conflict between the Terms and the Community Standards, the Terms prevail.

5. The Community Standards are made available free of charge in a manner that enables them to be saved, reproduced and retained.

§ 6. Privacy Policy

1. The rules governing the processing of personal data in connection with the use of ReputoNode are described in a separate Privacy Policy.

2. The Privacy Policy does not form an integral part of the Terms and is provided for information purposes.

3. Confirmation that the User has read the Privacy Policy does not constitute general consent to all personal-data processing operations.

4. Where a specific processing activity requires the User’s consent, such consent will be obtained separately in a manner enabling the User to make a voluntary and informed decision.

5. Refusal to grant, or withdrawal of, consent to personal-data processing based on consent does not prevent the use of the Portal’s basic functions, unless the relevant processing is necessary to provide a specific additional function selected by the User.

§ 7. Language versions

1. The Terms may be made available in different language versions.

2. The Polish version of the Terms is the source version.

3. Other language versions are translations of the Polish version and should preserve the same legal meaning.

4. In the event of discrepancies between the Polish version of the Terms and a translation, the Polish version forms the basis for interpretation, subject to mandatory provisions of law protecting the User, in particular provisions applicable to consumers.

5. The User may review the Terms in any language version made available in the Portal.

§ 8. Version and effective date of the Terms

1. The Terms apply from: <uzupełnij>[DATA WEJŚCIA W ŻYCIE REGULAMINU].

2. Version number of the Terms: 1.0.

3. The current version of the Terms is publicly available in the Portal free of charge.

4. The rules for amending the Terms, informing Users of changes and cases requiring renewed acceptance are set out in Chapter 21.

Chapter 2

Definitions

§ 9. Definitions

Whenever the following capitalised terms are used in the Terms, they have the meanings set out below:

1. ReputoNode or the Portal – the multilingual social networking portal available at https://reputonode.com through which the services described in the Terms are provided.

2. Service Provider – the entity operating ReputoNode and providing electronic services through it, whose full details are specified in Chapter 3.

3. Visitor – a person using the publicly available part of the Portal without having an Account or without being logged in to an Account.

4. User – a natural person, legal person or organisational unit for whom an Account has been created and who has concluded the Agreement with the Service Provider.

5. Where an Account is created or maintained on behalf of an entrepreneur, legal person, organisational unit, company, organisation, institution or other entity, the represented entity is the User, and activities relating to the Account are carried out on its behalf by an authorised natural person.

6. Account – a separate part of the Portal created for a User, enabling use of functions requiring registration and login, identified in particular by a username and authentication data.

7. Profile – the publicly available part of the Account through which information made available by the User is presented, in particular the User’s name, avatar, description, voluntarily provided Location, published Content and Topic Reputation.

8. Information placed by the User in the public part of the Profile is also available to Visitors. Contact details marked as non-public are not displayed in the public part of the Profile.

9. Username – the unique designation of the Account visible in the Portal. A Username may contain real data, a pseudonym, the name of a company or organisation, or another chosen designation, subject to the prohibition on impersonating other persons or entities and on violating the law, third-party rights, accepted standards of conduct and the Community Standards.

10. Content – any information or material posted, uploaded, saved or otherwise made available by a User through the Portal, including in particular:

    1. a Post;
    2. a Draft;
    3. a Comment;
    4. a Reply;
    5. Media;
    6. a link;
    7. a Username;
    8. an avatar;
    9. a description and other information included in the Profile;
    10. Location information;
    11. other data or materials made available using Portal functions.

11. Public Content – Content published in the Portal and available to Users and Visitors, in particular a Post, Comment, Reply or public Profile element.

12. Post – public Content published by a User, containing a title, Post Type, exactly one Category, a Location or the default global Publication Scope, and at least one element of substantive Content, in particular text, Media or a link.

13. Post Type – a designation indicating the nature of a published Post. ReputoNode uses the following Post Types:

    1. MAKES;
    2. SHARE;
    3. KNOW_HOW;
    4. VOICE.

    The meaning of individual Post Types and their possible impact on Topic Reputation are set out in the further provisions of the Terms.

14. Draft – unpublished Content saved in the User’s Account, visible only to that User and having no effect on Topic Reputation. A Draft may later be published as a Post, modified or deleted.

15. Comment – a public statement by a User posted directly under a Post.

16. Reply – a public statement by a User posted in reply to a Comment.

17. ReputoNode uses a two-level discussion structure. A User may reply to a Comment, but may not create another level of reply directly responding to a Reply.

18. Medium or Media – graphic, photographic, animated, audio, video or audiovisual material posted through the Portal, regardless of its technical format, provided that the format is supported by ReputoNode.

19. Audiovisual material remains video or audiovisual Media even where its visual layer is uniform, invisible or contains no material content and the essential part of the material is audio.

20. Thematic Category or Category – a subject area assigned to a Post, within which the effect of Reactions submitted on that Post and on related Comments and Replies is taken into account in the Topic Reputation of the authors of the rated Content.

21. Location – information voluntarily provided by the User about a place associated with a Profile or Post, which may indicate, in particular, an exact place, address, point, area, city, region, country or continent.

22. A Location included in a Profile or assigned to a published Post is public information and may also be visible to Visitors.

23. Publication Scope – a geographical level specified by the User in connection with a Post or Profile, indicating the area to which the Content relates or for which it may be particularly relevant.

24. Publication Scope may have one of the following levels:

    1. point;
    2. local;
    3. city;
    4. regional;
    5. national;
    6. continental;
    7. global.

25. If the User does not specify a Location or another limited Publication Scope, the Post or Profile is treated as global.

26. R+ Reaction – a positive Reaction submitted by a logged-in User on specific Content of another User.

27. R− Reaction – a negative Reaction submitted by a logged-in User on specific Content of another User.

28. R+ and R− Reactions may apply to Posts, Comments and Replies. A User may not submit Reactions to the User’s own Content.

29. Topic Reputation – a score calculated by ReputoNode and assigned to a User in a particular Category, affected by Reactions submitted on the User’s Posts assigned to that Category and on the User’s Comments and Replies posted under Posts assigned to that Category.

30. Topic Reputation is not a simple sum of the number of R+ and R− Reactions. Its calculation may take into account, in particular:

    1. the type and direction of the Reaction;
    2. the weight of the Reaction resulting from the Topic Reputation of the User submitting the Reaction;
    3. the Post Type, including the MAKES, SHARE, KNOW_HOW or VOICE designation;
    4. the type of Content being rated;
    5. mechanisms designed to detect and limit manipulation;
    6. other rules described in Chapter 12.

31. Topic Reputation does not constitute one overall rating of a person, confirmation of professional qualifications, or a guarantee of the truthfulness, reliability or correctness of all statements made by that person.

32. Following – a function enabling a User to follow another User, publicly disclose that relationship on the following list and filter Content published by followed persons. Following may in the future be taken into account in ordering, recommending or personalising Content in accordance with the Terms.

33. The list of Users followed by a given User is public. The Portal does not make available a public list of persons following a given User, nor separate counts of following and followers.

34. Report – information submitted to the Service Provider concerning Content, an Account or conduct that, in the reporting person’s opinion, may violate the law, the Terms or the Community Standards.

35. Reports concerning Illegal Content may be submitted using the electronic mechanism available in the Portal. Reports may also be submitted by e-mail to the relevant address indicated in the Terms, in accordance with the rules of Chapter 13.

36. Moderation – actions taken by the Service Provider to detect, identify, assess and address Illegal Content or information that does not comply with the Terms or the Community Standards, including actions affecting the availability or visibility of Content and the ability to use an Account.

37. Moderator – the Service Provider or a natural person expressly authorised by the Service Provider to conduct Moderation. As at the effective date of this version of the Terms, Moderation is conducted directly by the Service Provider.

38. Moderation Decision – a decision made by the Service Provider as a result of Moderation, which may include in particular:

    1. leaving Content unchanged;
    2. changing the Post Type or Post Category;
    3. removing part of Content, a link, Medium or the entire Content;
    4. limiting the visibility of Content;
    5. issuing a warning to the User;
    6. temporarily restricting specific Account functions;
    7. temporarily or permanently blocking the Account;
    8. correcting Reactions or Reputation;
    9. taking another proportionate measure provided for in the Terms.

39. The Service Provider may change the Post Type or its Category without the author’s prior consent if, on the basis of the content of the Post and the circumstances of the case, the Service Provider determines that the designation selected by the author does not correspond to the actual nature or main subject of the Post. The Post may remain published after such a change, and its author will be informed of the action taken.

40. Community Standards – a document setting out detailed rules for publishing Content and conduct in ReputoNode, types of prohibited Content and activities, rules for using R+ and R− Reactions, and possible measures taken in the event of violations. The Community Standards form an integral part of the Terms.

41. Privacy Policy – a separate document providing information about the rules governing the processing of personal data in connection with the use of ReputoNode. The Privacy Policy does not form an integral part of the Terms.

42. Terms – these terms governing the provision of electronic services through ReputoNode, including the Community Standards, which form an integral part of them.

43. Agreement – the agreement for the provision of electronic services concluded between the User and the Service Provider in accordance with the Terms.

44. Consumer – a natural person entering into a legal transaction with the Service Provider that is not directly related to that person’s business or professional activity, to the extent arising from applicable law.

45. Professional User – a User using ReputoNode in connection with business, professional, organisational or institutional activities, to the extent arising from the actual nature of the use of the Portal and applicable law.

46. Illegal Content – information that, in itself or by reference to an activity, including the sale of products or provision of services, is not in compliance with European Union law or the law of a Member State that is in compliance with European Union law, irrespective of the subject matter or nature of that law.

47. Terms not defined in this Chapter are to be understood in accordance with their meaning arising from the remaining provisions of the Terms, applicable law and the ordinary meaning of the relevant term.

Chapter 3

Service Provider details and contact

§ 10. Service Provider details

1. The Service Provider operating ReputoNode and providing electronic services through it is:

   Damian Urbański
   a natural person not conducting business activity.

2. Address details of the Service Provider required for publication:

   [[UZUPEŁNIJ: finalne dane adresowe Administratora / Usługodawcy wymagane do publikacji]]

3. The Service Provider’s place of residence and the country from which the Portal is operated is Poland.

4. The Service Provider’s primary e-mail address is: contact@reputonode.com.

5. The Service Provider’s current identification and contact details are available in the Portal in a manner that makes them easy to access directly.

§ 11. Contacting the Service Provider

1. The primary method of contacting the Service Provider is e-mail.

2. The following addresses are used for contact:

   1. contact@reputonode.com – general contact and complaints concerning the operation of the Portal;
   2. legal@reputonode.com – Reports, rights infringements, Moderation matters and appeals against Moderation Decisions;
   3. privacy@reputonode.com – questions, requests and demands concerning personal data;
   4. security@reputonode.com – Account or Portal security issues and vulnerability reports.

[[KONTROLA PRZED PUBLIKACJĄ: potwierdź aktywność i regularną obsługę adresów contact@reputonode.com, legal@reputonode.com, privacy@reputonode.com i security@reputonode.com; usuń ten znacznik po weryfikacji.]]

3. To facilitate message handling, a person contacting the Service Provider should indicate the type of matter in the message subject, in particular:

   1. “Contact”;
   2. “Complaint”;
   3. “Content report”;
   4. “Appeal against a decision”;
   5. “Personal data”;
   6. “Security”.

4. Failure to use the appropriate designation or sending the message to another of the listed addresses does not automatically result in the message being left unexamined, but may extend the time required to assign the matter correctly.

5. Messages addressed to the Service Provider should contain information sufficient to understand the matter and provide a response. Depending on the type of matter, additional data specified in further Chapters of the Terms may be required.

6. The Service Provider may ask the sender to supplement the information if, without it, consideration of the matter would be impossible or materially hindered.

7. Messages should be sent from an e-mail address that enables receipt of a response, unless the Terms or applicable law allow an anonymous report.

§ 12. Traditional correspondence

1. Correspondence in paper form may be sent to:

   Damian Urbański
   [[UZUPEŁNIJ: finalne dane adresowe Administratora / Usługodawcy wymagane do publikacji]]

2. Use of traditional correspondence is not required where the Terms allow the relevant matter to be handled by e-mail.

3. In traditional correspondence, the sender should provide an address to which a response can be sent or indicate an e-mail address to which the response may be sent.

4. Detailed rules for submitting complaints, Reports and appeals are set out in the relevant Chapters of the Terms.

§ 13. Electronic points of contact

1. The address legal@reputonode.com constitutes an electronic point of contact for Users, Visitors and other persons contacting the Service Provider in matters relating to the Terms, Moderation and Illegal Content.

2. The same address constitutes an electronic point of contact for communication with competent public authorities, the European Commission, the European Board for Digital Services and other authorised entities, unless applicable law requires the use of a separate communication channel.

3. Communication through the electronic point of contact may take place in Polish or English.

4. The Service Provider ensures regular monitoring of the indicated e-mail address.

5. The Service Provider may in the future create separate e-mail addresses for particular types of matters. A change in the organisation of contact addresses that does not limit the ability to contact the Service Provider does not in itself constitute a change to the terms of the Agreement.

6. Current contact addresses are always made available in the Portal.

§ 14. Contact regarding personal data

1. The Service Provider is the controller of personal data processed in connection with the operation of ReputoNode, to the extent specified in the Privacy Policy.

2. Questions, applications and requests concerning personal data may be sent to privacy@reputonode.com.

3. It is recommended to include the designation “Personal data” in the subject of the message.

4. The Service Provider may take reasonable measures to verify the identity of the person making a request where this is necessary to protect data against disclosure or alteration by an unauthorised person.

5. Detailed information on personal-data processing and the exercise of rights relating to such processing is provided in the Privacy Policy.

Chapter 4

Types and scope of ReputoNode services

§ 15. General scope of services

1. The Service Provider provides electronic services through ReputoNode consisting, in particular, of:

   1. making public Content posted in the Portal available;

   2. enabling the creation and maintenance of Accounts and public Profiles;

   3. enabling the publication of Posts, Comments and Replies;

   4. enabling Drafts to be saved;

   5. enabling Media and links supported by the Portal to be posted;

   6. organising Posts according to their type, Thematic Category, Location and Publication Scope;

   7. enabling R+ and R− Reactions to be submitted;

   8. calculating and publicly displaying Topic Reputation;

   9. enabling Users to follow other Users;

   10. providing mechanisms for searching, sorting and filtering public Content;

   11. making Content available in different language versions;

   12. enabling the reporting of Content, Accounts and conduct that may violate the law, the Terms or the Community Standards;

   13. enabling appeals against Moderation Decisions;

   14. enabling Account management, including requesting Account deletion and cancelling such a request within the prescribed period.

2. Detailed rules for using individual services and functions are set out in the further provisions of the Terms.

3. The scope of functions available at a given time may depend on:

   1. having an Account and being logged in;

   2. Account activation;

   3. the technical version of the Portal;

   4. the device, browser or operating system;

   5. the language selected by the person using the Portal;

   6. restrictions imposed on the Account in accordance with the Terms;

   7. temporary unavailability of a particular function.

§ 16. Services available without an Account

1. Public parts of ReputoNode are available without creating an Account and without logging in.

2. A Visitor may, in particular:

   1. open the Portal’s home page;

   2. browse the public Post feed;

   3. open and view public Posts;

   4. view public User Profiles;

   5. read public Comments and Replies;

   6. view Users’ public activity;

   7. view public Topic Reputation;

   8. view public information about followed Users to the extent made available by the Portal;

   9. use available search, filtering and sorting mechanisms;

   10. change the display language of the Portal and Content;

   11. review the Terms, Privacy Policy, Community Standards and other public information of the Portal;

   12. submit Reports to the Service Provider through the designated contact channel.

3. The search engine and filters for public Content operate under the same general rules for Visitors and logged-in Users, except for functions based on data from a specific Account, such as filtering Content originating from followed Users.

4. Use without an Account does not, in particular, allow a person to:

   1. publish Posts;

   2. save Drafts;

   3. publish Comments and Replies;

   4. submit R+ or R− Reactions;

   5. follow Users;

   6. maintain a Profile;

   7. use other functions requiring authentication.

§ 17. Services available to logged-in Users

1. A User with an active Account who is logged in to the Portal may, subject to restrictions arising from the Terms:

   1. maintain and update a public Profile;

   2. publish Posts;

   3. save and store Drafts;

   4. publish Comments under Posts;

   5. publish Replies to Comments;

   6. add Media and links supported by the Portal to Posts;

   7. select a Post Type and Thematic Category;

   8. specify a Location and Publication Scope;

   9. submit R+ and R− Reactions to Content of other Users;

   10. build Topic Reputation based on the reception of the User’s Content;

   11. follow other Users;

   12. use a filter allowing Content of followed Users to be displayed;

   13. delete the User’s own Posts;

   14. manage Account data and settings to the extent made available by the Portal;

   15. report Content, Accounts and conduct;

   16. appeal against Moderation Decisions concerning the User’s Account or Content;

   17. request deletion of the Account and cancel the request during the waiting period.

2. Creation of an Account does not depend on having prior Topic Reputation.

3. A User with zero Topic Reputation may publish Posts, Comments and Replies and use other functions unless access to them has been restricted in accordance with the Terms.

4. Account activation requires proper confirmation of the e-mail address in accordance with the registration process described in the Terms.

5. Posts, Comments and Replies are not normally subject to approval by the Service Provider before publication.

6. Content becomes public immediately after it has been properly published, unless:

   1. a technical error occurs;

   2. the Content is held or restricted for security reasons;

   3. the User’s Account is subject to a restriction;

   4. applicable law or a decision of an authorised authority requires otherwise.

7. The absence of pre-publication review does not limit the Service Provider’s right to conduct subsequent Moderation.

§ 18. Public Profile

1. The User’s Profile is public and may also be viewed by Visitors.

2. Depending on the information made available by the User and the functions available in the Portal, the Profile may display, in particular:

   1. display name;
   2. Username;
   3. avatar;
   4. voluntarily provided Location;
   5. date of joining the Portal;
   6. Content language or language selected by the User;
   7. Profile description;
   8. public contact details and links;
   9. activity statistics;
   10. published Posts;
   11. published Comments;
   12. published Replies;
   13. Topic Reputation in individual Categories;
   14. public information about followed Users;
   15. other public information made available as part of Profile functions.

3. The User may change, in particular:

   1. display name;
   2. avatar;
   3. Profile description;
   4. Profile Location;
   5. contact details and links.

4. The Username cannot be changed independently after the Account is created, except where the Service Provider changes it in accordance with the Terms.

5. Information about published Posts, Comments, Replies, Topic Reputation and followed Users reflects the current state of the Portal’s data and is not a freely editable description of the User.

6. Drafts are not visible to other Users or Visitors. If they are displayed to the author in the activity section of the author’s own Profile, they remain visible only to that author.

7. The User separately decides which of the contact details and links provided by the User are to be publicly visible, to the extent supported by the Portal settings.

8. By making contact details public, the User should be aware that they may be read and used by persons outside ReputoNode.

§ 19. Contact details and links in the Profile

1. A User may include supported contact details and links to external services in the Profile, in particular links to social and professional profiles.

2. The User independently decides whether a given contact detail or link will be made public.

3. ReputoNode does not normally verify whether the indicated account, profile, address or other contact channel actually belongs to the User.

4. The User is responsible for the accuracy, currency and lawfulness of the contact details and links made available.

5. The Service Provider is not responsible for:

   1. the availability or operation of an external service;

   2. content published in an external service;

   3. data-processing rules applied by the operator of an external service;

   4. actions taken by the User or another person outside ReputoNode.

6. The Service Provider may remove or block a public link if it leads to content that is illegal, dangerous, fraudulent, contrary to the Terms or Community Standards, or capable of endangering the security of Users or the Portal.

§ 20. Publishing and editing Content

1. The User independently decides whether to publish a Post, Comment or Reply.

2. Once published:

   1. a Post cannot be edited;

   2. a Comment cannot be edited;

   3. a Reply cannot be edited.

3. Before publishing Content, the User should check its content, accuracy, assigned Category, Post Type, Location, Publication Scope and attached Media and links.

4. The inability to edit published Content does not limit the Service Provider’s rights to:

   1. change the Category of a Post;

   2. change the Post Type;

   3. remove or restrict Content in accordance with the Terms;

   4. make technical changes that do not affect the substantive meaning of Content where necessary for its proper display or to secure the Portal.

§ 21. Deleting Posts, Comments and Replies

1. A User may independently delete the User’s own Post using the function available in the Portal.

2. A deleted Post:

   1. ceases to be visible in the public feed;

   2. is no longer presented as available Content of the author;

   3. cannot be read in its original form through the public Post page.

3. If Comments or Replies were published under a deleted Post, the Post page may remain available at its existing address in order to preserve the public discussion.

4. In place of the deleted Post Content, the Portal displays information that it was deleted by the author and may display the deletion date.

5. Comments and Replies posted under a deleted Post remain publicly available and continue to be attributed to their authors, unless they are removed or restricted by the Service Provider under applicable law, the Terms or the Community Standards.

6. A User cannot independently delete a published Comment or Reply using the Portal’s standard functions.

7. The absence of a function enabling the independent deletion of Comments and Replies does not exclude the possibility of:

   1. reporting Content that violates the law or the rights of an interested person;

   2. submitting a duly justified request to the Service Provider;

   3. exercising rights arising under personal-data protection law;

   4. removal or restriction of Content by the Service Provider as part of Moderation.

8. Deletion of an Account does not necessarily result in deletion of published Posts, Comments and Replies. Detailed rules concerning further storage and anonymisation of Content are set out in the Chapter concerning Account deletion.

§ 22. Drafts

1. A Draft is saved manually by the User.

2. ReputoNode does not provide automatic saving of Content being prepared before the User uses the save Draft function.

3. The User should save a Draft before leaving the Post creation form if the User wishes to retain the Content being prepared.

4. A Draft:

   1. is visible only to its author;

   2. does not constitute Public Content;

   3. is not subject to R+ or R− Reactions;

   4. does not affect Topic Reputation;

   5. may be modified before publication;

   6. may be published as a Post;

   7. may be manually deleted by the author.

5. A Draft is stored until it is published or deleted by the author, subject to:

   1. deletion of the Account;

   2. failure or loss of data;

   3. the need to delete data arising from applicable law;

   4. discontinuation of the relevant function in accordance with the Terms.

6. The Service Provider does not guarantee storage of Drafts as an archival service or the creation of a backup copy of the User’s materials.

§ 23. Media and supported formats

1. ReputoNode allows selected types of Media to be included in Posts in formats supported by the Portal.

2. As at the effective date of this version of the Terms, the Portal supports the following image formats:

   1. PNG;
   2. JPG;
   3. JPEG;
   4. WEBP.

3. The Portal supports the following video file formats:

   1. MP4;
   2. MOV;
   3. AVI;
   4. MKV;
   5. HEVC;
   6. WEBM.

4. A video file may contain video and audio, or primarily an audio track, provided that technically it remains a file in a supported video format.

5. ReputoNode does not currently provide a function for uploading standalone audio files or documents such as PDF files, unless the Portal interface clearly indicates otherwise.

6. The current catalogue of supported formats, file-size limits and other technical requirements may be indicated directly in the publishing form.

7. The Service Provider may change the catalogue of supported formats for technical, security, compliance or Portal-development reasons.

8. The Portal may technically process Media, in particular by converting, compressing, resizing, optimising or creating a thumbnail. The rules governing such operations are set out in particular in Chapters 10 and 11.

§ 24. Links in Content

1. A User may add an external link to a Post as an element of the Post Content.

2. A link added to a Post using the function provided for that purpose may be an active, clickable link.

3. A character string corresponding to an internet address may also be entered in other text fields, including a Comment or Reply.

4. An address entered in a field that does not support active links may be displayed only as plain text and may need to be copied manually by a person wishing to open the website.

5. Merely entering an internet address in a text field does not mean that ReputoNode:

   1. will check the destination website;

   2. will confirm its security;

   3. will guarantee its availability;

   4. will consider the website’s content compliant with applicable law or the Terms.

6. The rules governing liability for posted links and the possibility of their removal are set out in the further provisions of the Terms.

§ 25. Location and Publication Scope

1. The default Publication Scope of a Profile and Post is global.

2. The User may voluntarily indicate a more specific Location or Publication Scope, in particular a point, area, city, region, country or continent.

3. A Location may be assigned:

   1. to a Profile;

   2. to a Post of any type.

4. Indicating a Location does not restrict the public availability of a Post.

5. A Post marked as local, city-level, regional, national or continental may still be viewed by any User and Visitor regardless of where that person is located.

6. Location and Publication Scope are used primarily for:

   1. describing the geographical context of Content;

   2. filtering Posts by persons using the Portal;

   3. organising and searching Content.

7. Location does not currently automatically affect the order of Posts in the basic feed, except where the person using the Portal applies the relevant filter independently.

8. The Service Provider may in the future use Location as one of the parameters for ordering or recommending Content, provided that such a function is clearly described in advance and the rules set out in the Terms and Privacy Policy are respected.

§ 26. Feed, search and filtering

1. The basic ReputoNode feed presents Posts chronologically, starting with the newest.

2. As at the effective date of this version of the Terms, the basic feed does not use an advanced algorithm recommending Content on the basis of a User interest profile.

3. A User or Visitor may use available filters, in particular filters relating to:

   1. Category;
   2. Location or Publication Scope;
   3. Post Type;
   4. author Reputation;
   5. publication date;
   6. text appearing in the original Post title or in a stored translation of the title;
   7. other parameters made available in the Portal interface.

4. A logged-in User may apply a filter that displays Content published by followed Users.

5. The Portal does not currently provide a separate filter by Content language.

6. Following a User does not currently automatically give that User’s Content higher priority in the basic feed.

7. The Service Provider may in the future introduce additional ways of ordering or recommending Content. Material changes affecting the manner in which the Portal is used are introduced in accordance with the Terms.

§ 27. Translation of Content

1. ReputoNode is a multilingual Portal and may provide automatic translations of Posts, Comments, Replies and other textual Content.

2. Content is stored in the language in which it was published by the author as its original version.

3. After another language is selected, the Portal may:

   1. have the Content automatically translated by an external translation-service provider;
   2. perform the translation using a model or system operated by the Service Provider;
   3. retrieve a previously prepared language version from the database without performing the translation again.

4. Translated Content may be stored in the Portal database and made available again to persons selecting the same language.

5. A missing language version may be prepared while the Content is being displayed or later as part of periodic completion of translations.

6. Translation is performed automatically and does not constitute an authorised translation prepared or approved by the author of the Content.

7. Automatic translation may contain errors, simplifications or inaccuracies, or may fail to reflect correctly:

   1. the context of a statement;
   2. specialist terminology;
   3. irony, humour or wordplay;
   4. regional meanings of expressions;
   5. the author’s intention.

8. In the event of a discrepancy between the original Content and its automatic translation, the Content in the original language is regarded as the author’s proper statement.

9. A User should not base decisions that may materially affect health, safety, finances, rights or obligations solely on an automatic translation of Content.

10. The Service Provider does not guarantee that a translation will be error-free or fully consistent with the original version. This provision does not exclude the Service Provider’s liability to the extent that it cannot be excluded under applicable law.

11. The rules governing the transfer of Content to translation-service providers and the related processing of data are described in the Privacy Policy.

§ 28. Reactions and Topic Reputation

1. A logged-in User may submit an R+ or R− Reaction to a Post, Comment or Reply of another User.

2. A User may not submit Reactions to the User’s own Content.

3. A submitted Reaction cannot be withdrawn or changed using the Portal’s standard functions.

4. Before submitting a Reaction, the User should check its direction because the User’s choice will affect the Topic Reputation of the author of the Content.

5. Topic Reputation is calculated automatically and displayed publicly as a permanent element of ReputoNode.

6. A User may not:

   1. disable receipt of Reactions on the User’s public Content;

   2. hide the User’s Topic Reputation;

   3. opt out of the User’s published Content participating in the Topic Reputation system while keeping such Content publicly available in the Portal.

7. Detailed rules concerning Reactions, Topic Reputation and the prevention of manipulation are set out in further Chapters of the Terms.

§ 29. Following Users

1. A logged-in User may follow other Users and stop following them.

2. Following makes it possible, in particular, to apply a filter showing Content published by followed Users.

3. Following does not mean:

   1. establishing a formal relationship between Users;
   2. confirming the credibility of the followed User;
   3. endorsing all Content of that User;
   4. creating an obligation to follow each other.

4. The list of Accounts followed by a User is public. The Portal does not provide a public list of persons following a given User or separate counts of following and followers.

§ 30. No private messages and notifications

1. ReputoNode does not currently provide an internal messenger or private messaging function between Users.

2. Contact between Users may take place outside the Portal if a User has voluntarily made public contact details available in the User’s Profile.

3. ReputoNode is not a party to communications conducted outside the Portal and has no control over their content or course.

4. The Portal does not currently provide a notification system covering all new Comments, Replies, Reactions or followers.

5. The absence of a notification does not mean that no particular activity relating to Content or an Account has occurred.

6. The Service Provider may send messages necessary to:

   1. register or confirm an e-mail address;

   2. secure an Account;

   3. handle an Account-deletion request;

   4. inform about a Moderation Decision;

   5. fulfil a legal obligation;

   6. inform about material changes concerning the Agreement or the Portal.

§ 31. No public API and automation

1. ReputoNode does not currently provide a public API intended for the automatic publication, retrieval or processing of Content by external systems.

2. Use of bots, scripts, scrapers, automation programs or other similar tools requires the Service Provider’s prior express consent, unless applicable law provides otherwise.

3. In particular, the following automated activities are prohibited:

   1. creating Accounts;

   2. publishing Content;

   3. submitting Reactions;

   4. following Users;

   5. bulk downloading Content or Profile data;

   6. circumventing the Portal’s technical restrictions.

§ 32. Free services and no advertising

1. The services described in these Terms are provided free of charge.

2. As at the effective date of this version of the Terms, ReputoNode does not provide:

   1. paid Accounts or subscriptions;

   2. premium functions;

   3. paid highlighting or promotion of Posts;

   4. third-party advertisements;

   5. advertisements published by the Service Provider as part of an advertising system of the Portal.

3. The statement that the services are free of charge does not constitute an assurance that all functions that may be introduced in the future will always be free of charge.

4. Introduction of a paid service would require prior provision of clear information concerning, in particular:

   1. the scope of the service;

   2. the price and method of payment;

   3. the duration of the commitment;

   4. the rules for cancellation;

   5. consumer rights;

   6. a separate, express decision by the User to use the paid service.

5. Merely using a free Account cannot automatically create a payment obligation without the User’s prior express consent.

§ 33. Development and changes to the scope of services

1. The Service Provider may develop the Portal, add new functions, modify existing functions or withdraw functions, in particular for reasons relating to:

   1. technical matters;

   2. security;

   3. legal requirements;

   4. organisation;

   5. development of ReputoNode;

   6. low level of interest in a particular function;

   7. termination of cooperation with an external provider.

2. Purely technical, editorial or User-beneficial changes that do not restrict Users’ rights or increase their obligations may be introduced without amending the Terms.

3. If a change to a function materially affects the scope of the Agreement, the User’s rights, the manner of using Content or the operation of Topic Reputation, the Service Provider will provide information about the change in accordance with the rules for amending the Terms.

4. Introduction of a new function does not create an obligation to use it, unless it is technically necessary for the continued provision of the basic service and has been introduced in accordance with the Terms.

5. The Service Provider does not guarantee that every function of the Portal will be maintained indefinitely in an unchanged form.

Chapter 5

Technical requirements and safe use

§ 34. Technical requirements

1. ReputoNode is available through a web browser on devices with Internet access, in particular on:

   1. computers;

   2. tablets;

   3. phones.

2. ReputoNode does not require installation of a separate mobile application, unless the Service Provider makes such an application available in the future.

3. Proper use of the Portal requires at least:

   1. a device capable of using websites;

   2. an active Internet connection;

   3. a current version of a commonly used web browser;

   4. JavaScript enabled;

   5. technically necessary cookies and similar mechanisms enabled;

   6. the ability to use browser local storage where required by a specific Portal function;

   7. a functioning e-mail address – when creating and maintaining an Account.

4. The Service Provider does not guarantee proper operation of all Portal functions in:

   1. outdated browsers;

   2. browsers whose settings prevent JavaScript from running or necessary session mechanisms from being used;

   3. unusual or modified browser versions;

   4. systems and devices no longer supported by their manufacturers;

   5. configurations blocking elements necessary for the Portal to operate.

5. Disabling necessary cookies, session mechanisms or JavaScript may, in particular, make it impossible to:

   1. log in;

   2. maintain an Account session;

   3. submit a form;

   4. save a Draft;

   5. publish Content;

   6. remember the selected language;

   7. use other functions requiring authentication.

6. ReputoNode uses technically necessary cookies and similar mechanisms serving, in particular, to maintain sessions, secure forms and remember Portal settings.

7. ReputoNode does not currently use Google Analytics or other optional analytics cookies requiring the User’s consent.

8. The Portal does not currently provide a mechanism for managing consent to optional cookies because such cookies are not currently used. If technologies requiring consent are introduced in the future, an appropriate information mechanism and the ability to grant or refuse consent will be provided before they are launched.

9. Detailed information concerning the cookies and similar mechanisms used is provided in the Privacy Policy.

§ 35. Internet connection

1. A User or Visitor is responsible for providing, at the User’s or Visitor’s own expense:

   1. a device necessary to use the Portal;

   2. Internet access;

   3. an appropriate data-transmission package;

   4. software required to use websites.

2. The costs of Internet access and data transmission are borne by the person using the Portal in accordance with the agreement concluded with that person’s telecommunications service provider.

3. Uploading large files, in particular videos, may require a stable and sufficiently fast Internet connection.

4. Loss of connection, closing the browser, refreshing the page or device failure may result in:

   1. failure to upload a file;

   2. failure to publish Content;

   3. loss of unsaved text;

   4. loss of changes that were not saved as a Draft.

5. ReputoNode does not automatically save a Post being created. The User should manually save a Draft if the User wishes to retain prepared Content before publishing it.

§ 36. Secure connection

1. The publicly available version of ReputoNode uses an encrypted HTTPS connection.

2. Connections initiated using the unencrypted HTTP protocol are redirected to HTTPS where technically possible and permitted by the manner in which the connection is established.

3. When logging in, the User should check whether:

   1. the User is using the correct Portal address;
   2. the connection is marked as secure by the browser;
   3. the browser does not display a warning concerning the certificate or connection security.

4. The User should not provide login details on websites whose address differs from the official ReputoNode address.

§ 37. E-mail address

1. Creating and maintaining an Account requires a valid and functioning e-mail address to which the User has access.

2. The e-mail address may be used, in particular, to:

   1. confirm registration;

   2. activate the Account;

   3. reset the password;

   4. provide information concerning Account security;

   5. provide information concerning Account deletion;

   6. contact the User in matters required by law or the Terms.

3. The User is responsible for:

   1. providing a valid e-mail address;

   2. maintaining access to the indicated mailbox;

   3. securing the mailbox against unauthorised access;

   4. checking messages regularly, including the spam folder;

   5. promptly informing the Service Provider of loss of access to the mailbox where this may endanger the security of the Account.

4. ReputoNode does not currently allow the User to independently change the e-mail address assigned to the Account.

5. If the User loses access to the assigned e-mail address, the possibility of recovering the Account may depend on additional verification.

6. The Service Provider does not guarantee recovery of the Account if it is not possible to reliably confirm that the person making the request is entitled to control the Account.

§ 38. Password and login credentials

1. The User sets an Account password during registration.

2. The password should meet the security requirements indicated in the registration form.

3. Password requirements may be changed in order to improve security without the need to amend the Terms, provided that this does not infringe the User’s rights.

4. The User should use a password that is:

   1. difficult to guess;

   2. different from passwords used for other services;

   3. not based on readily available information about the User;

   4. protected against access by other persons.

5. The User may not:

   1. disclose the password to another person;

   2. send the password by e-mail or in public messages;

   3. enable other persons to use the Account with the User’s login details;

   4. store the password in a place easily accessible to unauthorised persons.

6. The Service Provider does not request the full Account password by e-mail or ordinary correspondence.

7. The User should not disclose the password to a person claiming to be the Service Provider or a Moderator.

8. The Service Provider applies technical and organisational measures to protect authentication data. Details of safeguards whose disclosure could reduce the Portal’s security level are not published in the Terms.

§ 39. Accounts maintained on behalf of entities

1. If an Account is maintained on behalf of a company, organisation, institution or other entity, that entity should designate one natural person responsible for access to the Account.

2. The person responsible for the Account:

   1. should be authorised to act on behalf of the relevant entity;

   2. is responsible for protecting login credentials;

   3. may not disclose the password to other persons;

   4. should promptly secure the Account if the authorisation is lost or cooperation with the entity ends.

3. The entity maintaining the Account is responsible for ensuring that only authorised persons have access to the Account.

4. A change of the person responsible for the Account should take place in a manner ensuring continuity of security, in particular by changing the password.

§ 40. Responsibility for Account security

1. The User is responsible for actions performed from the User’s Account to the extent that they result from:

   1. the User’s action;

   2. the User’s omission;

   3. deliberate disclosure of login credentials;

   4. failure to observe reasonable security rules;

   5. leaving a logged-in Account unattended on a device accessible to other persons.

2. The User is not automatically responsible for actions of an unauthorised person if they occurred despite the User observing appropriate security rules.

3. The User should exercise particular caution when using:

   1. public devices;

   2. shared devices;

   3. unsecured wireless networks;

   4. devices over which the User does not have full control.

4. After finishing use of the Account on a shared device, the User should log out.

5. The User should not:

   1. leave a logged-in Account unattended;

   2. save the password in an untrusted browser;

   3. allow the browser to automatically fill in login details on a device accessible to other persons.

§ 41. Changing and resetting the password

1. A logged-in User may change the password using the function available in the Account settings.

2. Changing the password may require entering the current password, re-authentication or another security action indicated by the Portal.

3. ReputoNode also allows password reset to be initiated using the e-mail address assigned to the Account.

4. A link or code used to reset the password:

   1. is intended for the owner of the relevant e-mail address;
   2. is valid for 30 minutes from generation;
   3. should not be disclosed to other persons;
   4. may be invalidated after use or for security reasons.

5. If the User receives a password-reset message despite not initiating the reset, the User should:

   1. not use the link provided;
   2. check the security of the User’s e-mail mailbox;
   3. contact the Service Provider if there is any suspicion of a threat.

6. Changing or resetting the password may terminate some or all active login sessions.

§ 42. Suspected Account takeover

1. If the User suspects that the Account may have been taken over or used without authorisation, the User should promptly:

   1. change the password in the Account settings or reset it using the e-mail address;
   2. change the password to, and secure, the e-mail mailbox assigned to the Account;
   3. terminate active sessions, if such a function is available;
   4. contact the Service Provider;
   5. indicate any irregularities noticed, in particular unknown publications, changes to data or actions performed without the User’s knowledge.

2. A report concerning Account security should be sent to security@reputonode.com.

3. It is recommended to include the designation “Account Security” in the subject of the message.

4. The Service Provider may request additional information necessary to confirm the identity of the person reporting the problem.

5. The Service Provider does not provide access to an Account to a person whose entitlement cannot be sufficiently confirmed.

§ 43. Login session

1. After a successful login, the Portal creates a session that enables the User to use the Account without entering the password again for every action.

2. If the User uses the stay-logged-in function, the session may be maintained after the browser is closed for a period determined by the Portal’s technical settings.

3. A session may be terminated, in particular:

   1. after the User logs out;

   2. after its validity period expires;

   3. after a longer period of inactivity;

   4. after the password is changed or reset;

   5. after security settings are changed;

   6. where unauthorised access is suspected;

   7. after the Account is restricted, suspended or deleted;

   8. as a result of technical work or failure.

4. The Service Provider may invalidate active Account sessions where justified by the security of the Account or the Portal.

§ 44. Temporary security blocking

1. The Service Provider may temporarily block access to an Account or specific functions where there are reasonable grounds to suspect:

   1. takeover of the Account;

   2. unusual or automated activity;

   3. distribution of spam;

   4. attempted fraud;

   5. use of the Account in a manner that endangers other persons;

   6. a breach of Portal security;

   7. circumvention of safeguards in place.

2. A security block may also be applied before the matter is fully clarified where delay could cause harm or further danger.

3. The scope and duration of the block should be proportionate to the nature of the threat.

4. The Service Provider will inform the User of the block and available courses of action, unless:

   1. providing the information could increase the threat;

   2. it would prevent the Account or evidence from being secured;

   3. it would be contrary to an instruction from an authorised authority;

   4. applicable law permits information to be temporarily restricted.

5. Unblocking the Account may require:

   1. changing the password;

   2. confirming the e-mail address;

   3. confirming entitlement to the Account;

   4. explaining unusual activity;

   5. taking other reasonable security measures.

§ 45. Files and technical threats

1. The User may not upload to the Portal:

   1. viruses;

   2. malicious software;

   3. code intended to take control of a device or data;

   4. files designed to exploit vulnerabilities;

   5. materials causing unauthorised actions in the system;

   6. files intentionally corrupted or misleading as to their format;

   7. other elements endangering the Portal, its Users or infrastructure.

2. ReputoNode does not currently use an automatic antivirus scanner for all uploaded files.

3. The absence of an automatic scanner does not limit the Service Provider’s right to:

   1. reject a file;

   2. stop its publication;

   3. delete the file;

   4. temporarily block the Account;

   5. take other action where a threat is suspected.

4. The Service Provider does not guarantee detection of every harmful file or threat.

5. A person using files or links posted by other Users should exercise appropriate caution.

§ 46. Technical limits

1. The Portal may apply technical limits concerning, in particular:

   1. avatar size;

   2. image or video size;

   3. length of textual Content;

   4. number of files uploaded;

   5. video duration;

   6. number of operations performed;

   7. frequency of publication or form submission.

2. Current limits may be indicated directly in the relevant Portal form or message.

3. A change to technical limits does not require an amendment to the Terms if:

   1. it results from justified technical, security or performance needs;

   2. it does not deprive the User of essential functionality arising from the Agreement;

   3. it has been clearly presented at the point where the relevant function is used.

4. The User may not circumvent technical limits by:

   1. modifying requests sent to the server;

   2. using multiple Accounts;

   3. using automated tools;

   4. changing a file extension;

   5. taking other actions contrary to the intended use of the function.

§ 47. Abuse-prevention mechanisms

1. The Portal uses technical mechanisms to counteract:

   1. automated Account creation;
   2. spam;
   3. mass form submission;
   4. password-guessing attempts;
   5. automated publication of Content;
   6. automated submission of Reactions;
   7. other forms of abuse.

2. These mechanisms may include, in particular:

   1. CAPTCHA or similar tests;
   2. request-rate limits;
   3. temporary blocking of operations;
   4. additional verification;
   5. analysis of technical connection parameters.

3. The use of a specific external solution and the related processing of data are described in the Privacy Policy where such a solution is used.

§ 48. Prohibited technical activities

1. Without the Service Provider’s prior express consent, it is prohibited to:

   1. test the Portal’s safeguards;

   2. scan for vulnerabilities;

   3. attempt to gain access to another person’s Account;

   4. intercept login credentials or sessions;

   5. circumvent safeguards and restrictions;

   6. inject code or data intended to alter the operation of the Portal;

   7. carry out denial-of-service attacks or other activities overloading the Portal;

   8. disrupt the operation of the server, database, network or application;

   9. download data in bulk;

   10. perform operations automatically;

   11. exploit errors beyond what is necessary to confirm their existence;

   12. gain access to data to which the person is not entitled;

   13. delete, alter or damage other persons’ data;

   14. hinder other persons’ use of the Portal.

2. The prohibition does not restrict activities of authorised authorities or activities expressly permitted by applicable law.

3. The Service Provider may block connections, IP addresses, sessions, Accounts or operations where necessary to protect the Portal.

§ 49. Reporting security vulnerabilities

1. A person who notices an error or potential security vulnerability may report it to the Service Provider at security@reputonode.com.

2. It is recommended to include the designation “Portal Security” in the subject of the message.

3. A report should, where possible, contain:

   1. a description of the problem observed;
   2. where it occurs;
   3. a method of reproducing the error without disclosing other persons’ data;
   4. possible consequences;
   5. technical information necessary for analysis.

4. A person reporting an error may not:

   1. download data of other Users;
   2. alter or delete data;
   3. retain more information than is necessary for the report;
   4. disrupt the operation of the Portal;
   5. publicly disclose a vulnerability before giving the Service Provider an opportunity to take action;
   6. exploit the error for personal gain or to cause harm.

5. Merely submitting a reliable report does not constitute consent to continue testing the system.

§ 50. Safeguards applied by the Service Provider

1. The Service Provider applies technical and organisational measures appropriate to:

   1. the nature of the Portal;

   2. the scope of services provided;

   3. the type of data processed;

   4. currently identified threats;

   5. the scale of ReputoNode’s operations.

2. These measures may include, in particular:

   1. encryption of transmissions;

   2. protection of authentication data;

   3. access control;

   4. logging of selected security events;

   5. abuse-limitation mechanisms;

   6. creation of backups;

   7. software updates;

   8. restriction of administrative access.

3. The Service Provider does not guarantee complete elimination of:

   1. failures;

   2. attempted attacks;

   3. software errors;

   4. loss of connection;

   5. actions of third parties;

   6. new, previously unknown vulnerabilities.

4. The absence of a guarantee of complete security does not release the Service Provider from the obligation to apply appropriate safeguards and respond to identified threats.

§ 51. No Account export function

1. ReputoNode does not currently provide an automatic function in Account settings for exporting all Content, Reactions and data associated with the Account.

2. The User should keep the User’s own copies of materials whose loss could be significant to the User.

3. The absence of a technical Account-export function does not limit rights arising from personal-data protection law, including the right of access to data and – where the relevant conditions apply – the right to data portability.

4. The rules for exercising personal-data rights are described in the Privacy Policy.

Chapter 6

Conditions for using the Portal and minimum age

§ 52. Persons entitled to use an Account

1. A ReputoNode Account may be created by:

   1. a natural person who is at least 18 years old;

   2. a natural person acting on behalf of a company, organisation, institution, public entity or other entity;

   3. a natural person maintaining an Account for a lawfully operating group, project or initiative without separate legal personality.

2. An Account may be maintained:

   1. by a natural person in that person’s own name;

   2. on behalf of an entrepreneur;

   3. on behalf of a legal person;

   4. on behalf of an organisational unit;

   5. on behalf of a foundation, association, institution, public entity, group or project.

3. A person creating or maintaining an Account on behalf of another entity declares that:

   1. the person is entitled to act on its behalf or has received appropriate authorisation;

   2. the information provided does not mislead as to the identity or nature of the Account;

   3. the person’s use of the entity’s name, designations and materials does not infringe third-party rights.

4. During standard registration, the Service Provider does not require a power of attorney, registry extract or other document confirming authorisation.

5. The Service Provider may request information or documents confirming entitlement to maintain the Account if:

   1. it receives a report concerning impersonation of another entity;

   2. a reasonable doubt arises as to the entitlement of the person maintaining the Account;

   3. a dispute over access to the Account arises between persons associated with the entity;

   4. this is necessary to protect the rights of the entity or a third party;

   5. the verification obligation arises from applicable law or a request from an authorised authority.

6. If entitlement to maintain the Account is not appropriately confirmed, the Service Provider may:

   1. temporarily restrict access to the Account;

   2. hide designations that may be misleading;

   3. require a change to the Profile name or data;

   4. block the Account;

   5. delete the Account in accordance with the rules set out in the Terms.

§ 53. Minimum age

1. A ReputoNode Account may be created and maintained only by a person who is at least 18 years old.

2. A person under 18 years of age may not create an Account or use another person’s Account, even with the consent of a parent, legal guardian or other representative.

3. The requirement to be at least 18 years old also applies to a natural person creating or operating an Account on behalf of a company, organisation, institution, group or other entity.

4. During registration, the person creating the Account declares that the person is at least 18 years old.

5. The declaration made during registration should read: “I declare that I am at least 18 years old.”

6. Making a false declaration concerning age constitutes a breach of the Terms.

7. The Service Provider does not normally require a scan of an identity card, passport or other identity document solely for the purpose of Account registration.

8. The absence of standard document verification does not constitute consent to the creation of Accounts by persons who do not meet the age requirement.

§ 54. Access by minors to public Content

1. The age restriction specified in § 53 applies to creating an Account and using functions that require login.

2. Public parts of ReputoNode may also be technically accessible without login to persons under 18 years of age.

3. Public availability of the Portal does not mean that ReputoNode is a service directed at children.

4. Minors should use publicly available Internet resources under the supervision of a parent, guardian or other responsible person, to an extent appropriate to their age and maturity.

5. The Service Provider may restrict the visibility of, or remove, Content that presents a particular risk to minors, in accordance with applicable law, the Terms and the Community Standards.

§ 55. Suspected use of an Account by a minor

1. If there are reasonable grounds to suspect that an Account is maintained by a person under 18 years of age, the Service Provider may temporarily restrict access to the Account.

2. Before permanently deleting the Account, the Service Provider may allow the person using the Account to explain the situation or demonstrate that the age requirement is met.

3. The method of confirming age should be proportionate to the circumstances and should not require disclosure of a broader scope of data than is necessary.

4. The Service Provider may permit age to be confirmed in a manner limiting the scope of disclosed data, in particular by allowing information not necessary to confirm the age and identity of the Account holder to be obscured on a copy of a document.

5. The Service Provider will not retain a document provided solely for age verification longer than necessary to complete the verification and document its result, subject to obligations arising from applicable law.

6. If it is confirmed that the Account is maintained by a person under 18 years of age, the Service Provider may:

   1. block the Account;

   2. terminate the Agreement;

   3. delete or anonymise Account data;

   4. deal with published Content in accordance with the Account-deletion rules, taking into account the protection of the minor’s rights.

7. Information about the action taken will be sent to the e-mail address assigned to the Account, unless this is impossible or not permitted by law.

§ 56. One personal Account

1. One natural person may maintain one personal Account in ReputoNode.

2. A person maintaining a personal Account may additionally be responsible for an Account of a company, organisation, institution, group, project or other entity if authorised to do so.

3. An Account maintained solely and clearly on behalf of another entity is not regarded as a separate personal Account.

4. Creating an additional personal Account for the purpose of the following is prohibited:

   1. submitting additional Reactions;

   2. increasing one’s own Topic Reputation;

   3. lowering the Reputation of another User;

   4. circumventing a block, restriction or Moderation Decision;

   5. creating the appearance of support from multiple independent persons;

   6. misleading other persons;

   7. conducting spam or coordinated activity.

5. The Service Provider may restrict or delete additional Accounts maintained in breach of this paragraph and correct the effects of actions performed using them.

§ 57. Username, display name and pseudonym

1. A User is not required to publicly use the User’s real first name and surname.

2. A natural person may use:

   1. the person’s real first name and surname;

   2. a pseudonym;

   3. another chosen designation compliant with the Terms.

3. An Account maintained on behalf of a company, organisation, institution, group or project may use its name, brand or other designation if the person maintaining the Account is entitled to do so.

4. A Username, display name or other Account designation may not:

   1. impersonate another person or entity;

   2. suggest an official relationship, authorisation or endorsement that does not exist;

   3. infringe rights to a business name, trademark, surname, pseudonym, likeness or other designations;

   4. infringe personal rights;

   5. be insulting, hateful, discriminatory or vulgar;

   6. mislead as to the nature or origin of the Account;

   7. violate applicable law, the Terms or the Community Standards.

5. The technical ability to register a particular name does not mean that the Service Provider confirms the User’s right to use it.

6. The Service Provider may require a name to be changed, change it technically, restrict the visibility of the Account or take another appropriate measure if the name violates the Terms or a third party’s rights.

§ 58. Parody and satire Accounts

1. An Account of a parody, satirical, fan or commentary nature is permitted if its nature is clearly and unambiguously indicated.

2. Such an Account may not mislead a reasonable recipient as to:

   1. the identity of the person maintaining the Account;

   2. the official nature of the Account;

   3. its relationship with the person, company, organisation or institution concerned;

   4. authorisation or endorsement by that person or entity.

3. Merely placing information about parody in a difficult-to-access location may be insufficient if the Account’s name, avatar or manner of operation still misleads recipients.

4. A parody or satirical Account is subject to the same rules concerning Content, harassment, protection of personal rights and liability as other Accounts.

§ 59. Accuracy of data associated with Account administration

1. The ability to use a pseudonym does not release the User from the obligation to provide correct data required for technical and legal administration of the Account.

2. The e-mail address assigned to the Account should:

   1. exist;

   2. remain under the lawful control of the User or the entity on whose behalf the Account is maintained;

   3. enable receipt of messages relating to the Account;

   4. not belong to a third party that has not consented to its use.

3. The User may not knowingly provide false data for the purpose of:

   1. taking over another person’s Account;

   2. circumventing restrictions;

   3. hindering contact;

   4. misleading the Service Provider or other persons;

   5. committing fraud or another violation of law.

§ 60. Refusal to register or activate an Account

1. The Service Provider may refuse to create or activate an Account if:

   1. the registration form is incomplete;

   2. the data provided is technically invalid;

   3. the e-mail address is already assigned to another Account;

   4. the Username is already taken;

   5. the selected name violates applicable law, the Terms or a third party’s rights;

   6. the person does not meet the age requirement;

   7. the current Terms have not been accepted;

   8. the person has not confirmed having read the Privacy Policy;

   9. the required e-mail address verification has not been completed;

   10. registration is automated or spam-related;

   11. the person is attempting to circumvent an earlier block or restriction;

   12. creation of the Account could endanger the security of the Portal or other persons;

   13. refusal is necessary to comply with a legal obligation.

2. Refusal of registration may not be based on unlawful discrimination.

3. Where permitted by security considerations and applicable law, the person attempting to create an Account will be informed of the basic reason for refusal.

§ 61. No right to a specific Account name

1. Earlier registration of a Username does not in itself confer a right to use it in violation of another person’s rights.

2. In particular, it is prohibited to:

   1. register another person’s surname, name or brand for the purpose of impersonation;

   2. block a name in order to demand payment or another benefit;

   3. suggest an official nature of an Account without authorisation;

   4. use a name in a manner infringing a trademark, business name or personal rights.

3. In a dispute concerning a name, the Service Provider may take into account, in particular:

   1. the rights held by the parties;

   2. the date and manner in which the designation has been used;

   3. the nature of the Account;

   4. the possibility of misleading recipients;

   5. documents and explanations provided;

   6. the interests of the Portal community.

4. The Service Provider does not finally resolve disputes concerning intellectual-property rights or personal rights that fall within the jurisdiction of courts or other authorised bodies.

§ 62. Territorial availability of ReputoNode

1. ReputoNode is operated by the Service Provider from Poland.

2. The Portal is directed primarily at adult Users located in Poland and other countries of the European Economic Area.

3. ReputoNode may also be technically accessible to persons located outside the European Economic Area.

4. Technical availability of the Portal in a particular country does not mean that the Service Provider:

   1. actively targets the service at residents of every country in the world;

   2. conducts business activity in every country from which the Portal can be opened;

   3. ensures compliance of all functions with the laws of every country outside the area at which the service is directed.

5. A person using the Portal outside Poland should ensure that use of ReputoNode complies with the law applicable in the place where the person is located.

6. The Service Provider may restrict or disable access to the Portal or specific functions in a given territory where necessary due to:

   1. applicable law;

   2. a decision of an authorised authority;

   3. international sanctions;

   4. security;

   5. inability to lawfully provide the service;

   6. technical or organisational limitations.

7. The choice of Polish law in the Terms does not deprive a consumer of protection granted by provisions that cannot be contractually excluded and that apply due to the consumer’s habitual residence.

§ 63. Temporary suspension of registration

1. The Service Provider may temporarily suspend the creation of new Accounts, in particular due to:

   1. technical work;

   2. failure;

   3. infrastructure overload;

   4. a security threat;

   5. intensified attempts at automated registration or spam;

   6. the need to adapt the Portal to applicable law;

   7. a test or limited stage of Portal operation;

   8. inability to ensure an appropriate level of service.

2. Temporary suspension of registration does not automatically affect the operation of existing Accounts.

3. Where possible, information about temporary suspension of registration will be published in the Portal.

4. The Service Provider does not guarantee uninterrupted availability of the ability to create a new Account.

Chapter 7

Registration and conclusion of the Agreement

§ 64. Conditions for creating an Account

1. Creating an Account requires proper completion of the registration process made available in the Portal.

2. During registration, the person creating the Account provides:

   1. a unique Username;

   2. a valid e-mail address;

   3. a password meeting the security requirements indicated in the registration form.

3. During registration, it is not required to provide:

   1. a display name;

   2. first name and surname;

   3. date of birth;

   4. Location;

   5. information as to whether the Account is maintained by a private individual, company, organisation or other entity.

4. The display name, Location, Profile description, avatar, contact details and other additional information may be completed after Account activation using the Profile-editing function.

5. The person registering an Account must provide data compliant with the requirements of the Terms and may not use data or designations in a manner that infringes the rights of other persons.

6. Account registration is free of charge.

§ 65. Declaration of being at least 18 years old

1. During registration, the person creating the Account makes a separate mandatory declaration that the person is at least 18 years old.

2. The declaration reads: “I declare that I am at least 18 years old.”

3. The age declaration is made using a separate checkbox that is unselected by default.

4. Failure to make the declaration prevents submission of the registration form and creation of the Account.

5. Making a false age declaration constitutes a breach of the Terms and may result in restriction or deletion of the Account in accordance with the rules set out in the Terms.

§ 66. Acceptance of the Terms and the Privacy Policy

1. Submission of the registration form is conditional on:

   1. acceptance of the Terms;

   2. confirmation that the person has read the Privacy Policy.

2. Both actions are performed using one mandatory checkbox that is unselected by default.

3. The checkbox text reads: “I accept the ReputoNode Terms of Service and confirm that I have read the Privacy Policy.”

4. The terms “ReputoNode Terms of Service” and “Privacy Policy” constitute separate links enabling the relevant document to be opened before the form is submitted.

5. The documents are available in a manner enabling them to be:

   1. read;

   2. saved;

   3. reproduced;

   4. retained.

6. Acceptance of the Terms also covers the Community Standards, which form an integral part of them.

7. Confirmation that the person has read the Privacy Policy:

   1. does not constitute general consent to all personal-data processing operations;

   2. confirms that the person registering the Account has received information concerning data processing;

   3. does not replace separate consent where specific processing requires such consent under applicable law.

8. Failure to select the checkbox referred to in section 2 prevents creation of the Account.

§ 67. Optional cookies and similar technologies

1. ReputoNode does not currently use Google Analytics or other optional analytics cookies requiring the User’s consent.

2. If, in the future, ReputoNode introduces cookies or similar technologies whose use requires consent under applicable law, such consent will not form part of:

   1. acceptance of the Terms;

   2. confirmation that the User has read the Privacy Policy;

   3. the declaration that the User is at least 18 years old;

   4. the process of concluding the Agreement.

3. Where consent is required for a specific technology, the User will be given the opportunity to grant, refuse and subsequently withdraw such consent in accordance with applicable law.

4. The introduction of optional technologies and the rules governing their operation will be appropriately described in the Privacy Policy or other information made available to the User before they are launched.

§ 68. Submission of the registration form

1. After correctly completing the form and meeting the registration requirements, the person creating the Account may submit the form to the Service Provider.

2. Submission of the form results in the creation of a technical, inactive Account and the sending of a message used to confirm the e-mail address.

3. Creation of an inactive Account alone does not yet constitute conclusion of the Agreement for maintaining an active Account.

4. Until activation, the Account is used solely to:

   1. store data necessary to complete registration;

   2. reserve the Username;

   3. carry out e-mail address verification;

   4. enable the activation message to be resent;

   5. handle other actions necessary to complete the registration process.

5. An inactive Account does not allow publication, commenting, replying, submitting Reactions or use of other functions requiring an active Account.

§ 69. E-mail address verification

1. Account activation requires confirmation of the e-mail address provided during registration.

2. After the registration form is submitted, the Service Provider sends a message to the indicated address containing a link or another mechanism for confirming the e-mail address.

3. The activation link is valid for 24 hours from the time it is generated. Information about the validity period is also provided in the message sent to the person registering the Account.

4. The activation link:

   1. is intended exclusively for the person who has access to the indicated mailbox;

   2. may be used only in the manner specified in the message;

   3. may expire after use or after the indicated period;

   4. should not be disclosed to another person.

5. If the message does not arrive or the link expires, the person registering the Account may use the function to resend the activation message.

6. The Service Provider may limit the number or frequency of resends in order to counteract spam and abuse.

7. A person who receives an activation message despite not attempting to create an Account should not use the link and may inform the Service Provider.

8. If the Account is not verified within 7 days of its creation, an unverified Account with no user activity may be automatically deleted together with data used solely for the incomplete registration. After such deletion, using ReputoNode again requires a new registration.

§ 70. Conclusion of the Agreement and Account activation

1. The Agreement is concluded when the e-mail address is properly confirmed and the Account is activated.

2. Account activation means that:

   1. the e-mail address has been confirmed;

   2. the registration process has been completed;

   3. the User may log in and use functions available to active Accounts;

   4. an Agreement is concluded between the User and the Service Provider on the terms set out in the accepted Terms.

3. After activation, the User may, among other things:

   1. complete the public Profile;

   2. add a display name;

   3. add an avatar and description;

   4. specify the Profile Location;

   5. add contact details and links;

   6. publish Posts;

   7. save Drafts;

   8. publish Comments and Replies;

   9. submit Reactions;

   10. follow other Users.

4. Conclusion of the Agreement does not grant the User the right to use the Portal in violation of applicable law, the Terms or the Community Standards.

§ 71. Inactive Account

1. Until the e-mail address is confirmed, the Account remains inactive.

2. An attempt to log in to an inactive Account results in information being displayed about the need to activate it.

3. An inactive Account does not allow use of the Portal’s social functions.

4. A person with an inactive Account may still, without logging in, view public Content under the rules applicable to Visitors.

5. The Username assigned to an inactive Account remains reserved until the Account is activated or deleted on another basis provided for in the Terms or applicable law.

6. Failure to confirm the e-mail address does not currently result in automatic deletion of the Account solely due to the passage of a specified period.

7. The Service Provider may delete or restrict an inactive Account where another basis specified in the Terms or applicable law exists, in particular abuse of the registration process, a security threat or a legal obligation.

§ 72. Public nature of the Profile

1. Every ReputoNode Account is associated with a public Profile.

2. ReputoNode does not provide an option to maintain a private or hidden Profile.

3. A User who activates an Account should expect that:

   1. the User’s Username will be public;

   2. information voluntarily included in the Profile will be public, except for data marked as non-public using available settings;

   3. the User’s Posts, Comments, Replies, activity and Topic Reputation will also be available to persons who are not logged in;

   4. the User’s Content may be available through direct internet addresses and the Portal search engine.

4. Before Account activation, the Profile may be technically created and available to a limited extent, including, in particular, the reserved Username and data automatically generated by the Portal.

5. An inactive Account may not publish Content or complete the Profile using functions available only after login.

6. Creation of an Account means choosing the public model of participation in ReputoNode. A User who does not wish to have a public Profile should not activate the Account.

§ 73. Uniqueness of Username and e-mail address

1. Each Username may be assigned to only one Account.

2. Each e-mail address may be assigned to only one Account.

3. Usernames differing only in letter case are treated as the same name.

4. A display name:

   1. is not provided during registration;
   2. may be added after Account activation;
   3. does not need to be unique;
   4. may be used by more than one User;
   5. is subject to the rules concerning impersonation, third-party rights and prohibited designations.

5. Incomplete registration does not result in conclusion of the Agreement, but creates a technical inactive Account necessary to complete the activation process.

6. If a Username or e-mail address is already taken, the Portal may display information that a User with the specified Username or e-mail address already exists.

7. The User should not treat information about the existence of an Account as a basis for attempting to gain access to it or contacting the owner of the address without an appropriate basis.

§ 74. Registration-form errors

1. The form may not be accepted, in particular, if:

   1. the Username is taken;

   2. the e-mail address is already assigned to an Account;

   3. the e-mail address has an invalid format;

   4. the password does not meet the requirements;

   5. the required document-acceptance checkbox has not been selected;

   6. the declaration of being at least 18 years old has not been made;

   7. the data contains prohibited characters or exceeds limits;

   8. the mechanism protecting against automated registration has not been completed correctly;

   9. a technical error or suspected abuse has been detected.

2. The Portal may indicate the cause of the error and allow it to be corrected.

3. Display of an error message does not guarantee creation of the Account after the error is corrected if another obstacle arising from the Terms or applicable law exists.

§ 75. Protection of the registration process

1. The registration process is protected using CAPTCHA, request-rate limits or other mechanisms counteracting automated Account creation.

2. After registration, the Service Provider may restrict or delete an Account if it turns out that the Account was created:

   1. automatically;
   2. for the purpose of distributing spam;
   3. using another person’s data without authorisation;
   4. for the purpose of circumventing a block;
   5. for the purpose of manipulating Reactions or Reputation;
   6. in another manner violating the Terms or Portal security.

3. The Service Provider may use additional mechanisms for detecting abuse, provided that they comply with applicable law and the related processing of data is appropriately described in the Privacy Policy.

§ 76. Registration of entity Accounts

1. During registration, no separate selection of a personal, company, organisational or institutional Account type is required.

2. The nature of an Account results, in particular, from:

   1. the Username;

   2. the display name;

   3. the Profile description;

   4. published information;

   5. the manner in which the Account is maintained.

3. A person maintaining an Account on behalf of an entity must comply with the rules concerning authorisation and the prohibition on impersonation set out in the Terms.

4. The absence of a separate Account-type designation does not release the person maintaining the Account from responsibility for ensuring that the information provided corresponds to the actual state of affairs.

§ 77. Recording acceptance of documents

1. The Service Provider records information necessary to demonstrate that the User accepted the Terms and confirmed having read the Privacy Policy.

2. Recorded information includes, in particular:

   1. Account identifier;

   2. date and time of acceptance;

   3. version of the Terms accepted;

   4. version of the Privacy Policy presented to the User.

3. The Service Provider does not record the language of the documents as separate information associated with acceptance, unless such a function is introduced in the future.

4. The Service Provider does not assume that the IP address will be recorded solely as evidence of acceptance of the documents.

5. Other technical data may be processed to the extent necessary for security, operation of the Portal or fulfilment of legal obligations, in accordance with the Privacy Policy.

6. Information concerning acceptance may be retained for the duration of the Agreement and, after its termination, for the period necessary to:

   1. demonstrate conclusion and content of the Agreement;

   2. handle claims;

   3. fulfil legal obligations;

   4. defend the rights of the Service Provider or the User.

§ 78. New versions of documents

1. The Portal compares the version of the Terms currently in force with the version accepted by the User.

2. If the versions differ and the nature of the change requires renewed acceptance, before continuing active use of the Account the User must:

   1. review the new version of the Terms;
   2. accept the new version of the Terms;
   3. confirm having read the current Privacy Policy if it is presented together with the new version of the documents.

3. Until the required action is completed, the User may remain technically logged in, but instead of ordinary Account functions receives access to a screen informing the User about the new version of the documents.

4. A User who does not accept the new version of the Terms may begin the Account-deletion procedure without first accepting it.

5. Failure to accept the new version does not restrict the possibility of viewing public Content as a Visitor.

6. Renewed confirmation that the User has read the Privacy Policy:

   1. is not required for every editorial change;
   2. may be required in order to document the provision of materially changed information;
   3. does not replace separate consent where new data processing requires consent.

7. Detailed rules for determining which changes require renewed acceptance are set out in Chapter 21.

§ 79. Confirmation of conclusion of the Agreement and welcome e-mail

1. After proper Account activation, the Service Provider sends the User a message confirming creation of the Account and conclusion of the Agreement.

2. Where required by applicable law, confirmation of conclusion of the Agreement is provided on a durable medium and includes information required by such law, unless it has already been provided to the User on a durable medium.

3. The confirmation may contain or attach, in particular:

   1. the number of the accepted version of the Terms;
   2. the Terms or a copy thereof in a form enabling storage and reproduction;
   3. the Community Standards or a copy thereof;
   4. information concerning the right to withdraw from the Agreement, if such a right is available to the User;
   5. other information required by applicable law.

4. The message may simultaneously serve as a welcome e-mail and contain, in particular:

   1. a brief explanation of the basic ReputoNode rules;
   2. information about R+ and R− Reactions;
   3. a link to the “Welcome to ReputoNode” guide;
   4. links to current ReputoNode documents;
   5. information concerning Account security.

5. The message is informational and related to Account administration.

6. The message is not a newsletter and does not constitute consent to receive marketing communications.

7. ReputoNode does not operate a newsletter. Introduction of a newsletter or other marketing communication requires separate rules and appropriate consent where required.

Chapter 8

Account, Profile and login

§ 80. Logging in to the Account

1. The User logs in to the Account using:

   1. the e-mail address assigned to the Account;

   2. the password set during registration or a later password reset.

2. The Username and display name are not used for logging in.

3. Access to functions requiring login is possible only after:

   1. Account activation;

   2. acceptance of the current version of the Terms, where renewed acceptance is required;

   3. confirmation that the User has read the current Privacy Policy, where such confirmation is required;

   4. correct entry of login credentials;

   5. absence of a block or other restriction preventing access to the Account.

4. An attempt to log in to an inactive Account results in information being displayed about the need to confirm the e-mail address.

5. If the User has not accepted a required new version of the Terms, access to Account functions may remain blocked until the required action is completed.

6. Inability to log in does not restrict access to public parts of the Portal under the rules applicable to Visitors.

§ 81. Resetting and changing the password

1. The User may change the password using the function available in the settings of a logged-in Account.

2. Changing the password may require entering the current password, re-authentication or another security action indicated by the Portal.

3. The User may also set a new password using the password-reset procedure available through the “Forgot password” function or a function of similar meaning.

4. The password-reset procedure requires access to the e-mail address assigned to the Account.

5. The User should change or reset the password in particular when:

   1. the User has forgotten the password;
   2. the User suspects that the password has been disclosed;
   3. the User has noticed unknown activity on the Account;
   4. the User wishes to replace the current password with a new one.

6. A password-reset link is valid for 30 minutes from generation, may be used only once and is invalidated after use.

7. The User may not disclose to other persons a link, code or message used to reset the password.

8. Changing or resetting the password may invalidate some or all active sessions.

§ 82. E-mail address assigned to the Account

1. The e-mail address provided during registration is assigned to the Account and is used, in particular, for:

   1. logging in;

   2. Account activation;

   3. password reset;

   4. providing security information;

   5. providing information required by the Terms or applicable law.

2. The User cannot independently change the e-mail address assigned to the Account using the Portal’s standard functions.

3. In an exceptional situation, the Service Provider may manually change the e-mail address assigned to the Account if:

   1. the User submits a duly justified request;

   2. the User’s entitlement to the Account can be reliably confirmed;

   3. the change will not endanger Account security or the rights of other persons;

   4. there is no legal or technical obstacle to making the change.

4. The Service Provider may request information or documents necessary to confirm entitlement to the Account.

5. The scope of information required should be proportionate to the risk associated with changing the e-mail address.

6. The Service Provider may refuse to change the e-mail address if:

   1. the entitlement of the person making the request cannot be reliably confirmed;

   2. there is a dispute concerning the Account;

   3. the new address is already assigned to another Account;

   4. an attempted Account takeover is suspected;

   5. the change would violate applicable law, the Terms or Portal security.

7. The User should promptly contact the Service Provider if the User loses access to the e-mail address assigned to the Account.

§ 83. Username

1. The Username is a unique Account designation selected during registration.

2. The Username:

   1. is public;

   2. is used to identify the User in the Portal;

   3. may form part of the Profile’s internet address;

   4. is not used for logging in.

3. The User cannot independently change the Username after the Account is created.

4. The Username may be changed by the Service Provider only in justified cases, in particular where it:

   1. violates applicable law;

   2. infringes the rights of a third party;

   3. constitutes impersonation of another person or entity;

   4. is insulting, hateful, discriminatory or misleading;

   5. must be changed for technical or security reasons;

   6. is used in violation of the Terms or Community Standards.

5. Changing the Username may change the Profile’s internet address and make earlier links unavailable.

6. The User does not acquire ownership of the Username or a right to use it beyond the scope arising from the Agreement and applicable law.

§ 84. Display name

1. The User may add a display name after Account activation.

2. The display name:

   1. is public;

   2. does not need to be unique;

   3. may be the same as a name used by other Users;

   4. may be left blank if the Portal permits it;

   5. may be changed any number of times using the Profile-editing function.

3. Changing the display name does not change the Username or the e-mail address assigned to the Account.

4. The display name is subject to the rules concerning the prohibition on impersonation, protection of third-party rights and prohibited Content.

5. The Service Provider may remove or change a display name if it violates applicable law, the Terms or the Community Standards.

§ 85. Avatar

1. The User may:

   1. add an avatar;

   2. change the avatar;

   3. remove the avatar and return to the default image or another designation used by the Portal.

2. The avatar is a public element of the Profile.

3. The avatar must meet the technical requirements indicated in the file-upload form.

4. The User is responsible for holding the rights and consents necessary for public use of the avatar.

5. The avatar may not:

   1. infringe copyright;

   2. infringe image rights;

   3. infringe personal rights;

   4. impersonate another person or entity;

   5. contain prohibited Content;

   6. violate applicable law, the Terms or the Community Standards.

6. The Service Provider may remove an avatar that violates Portal rules or threatens security.

§ 86. Profile description and its translations

1. The User may include a public description on the Profile, hereinafter referred to as the bio.

2. The User prepares the bio in a language selected by the User.

3. ReputoNode may automatically:

   1. detect the language of the bio;

   2. prepare translations of it into languages supported by the Portal;

   3. store prepared translations in the database;

   4. display the translation corresponding to the language selected by the person viewing the Profile.

4. The original version of the bio remains the version prepared by the User.

5. Automatic translation of the bio may contain errors, simplifications or inaccuracies.

6. In the event of a discrepancy between the original bio and its automatic translation, the original version is regarded as the proper Content of the User.

7. The User may change the bio using the Profile-editing function.

8. Changing the bio may result in its translations being prepared again.

9. The bio is subject to all rules applicable to Content published in the Portal.

§ 87. Profile Location

1. The default scope of a Profile is global.

2. The User may voluntarily assign a more specific Location to the Profile.

3. The Profile Location may indicate, in particular:

   1. an exact place;

   2. an area;

   3. a city;

   4. a region;

   5. a country;

   6. a continent;

   7. global scope.

4. The Location assigned to the Profile is public.

5. The User may change the Profile Location at any time.

6. The Portal does not provide a separate function for deleting the Location, but the User may set the scope to global again.

7. After global scope is set, the more specific Location is no longer presented as the current Profile Location.

8. The Portal does not provide a public history of previous Profile Locations.

9. The User should consider the risk associated with publicly disclosing an exact place of residence, stay or activity.

§ 88. Public contact details and links

1. The User may supplement the Profile with contact details and links supported by the Portal, including in particular:

   1. e-mail address;

   2. LinkedIn;

   3. GitHub;

   4. Discord;

   5. Telegram;

   6. other contact fields made available in the future.

2. For each contact detail or link, the User may specify whether it is to be publicly visible if the Portal provides the relevant setting.

3. Data marked as public may be visible to all Users and Visitors.

4. Data marked as non-public is not displayed on the public Profile.

5. The User is responsible for:

   1. the accuracy of contact details;

   2. the lawfulness of their publication;

   3. holding the right to indicate the relevant contact detail;

   4. the consequences of voluntarily making data public.

6. ReputoNode does not normally verify whether an external account or contact address actually belongs to the User.

7. The Service Provider may remove contact details or a link if they:

   1. violate applicable law;

   2. lead to illegal, dangerous or fraudulent Content;

   3. are used for impersonation;

   4. threaten security;

   5. violate the Terms or the Community Standards.

§ 89. Public User activity

1. The Profile displays the User’s public activity to the extent made available by the Portal.

2. Public activity may include, in particular:

   1. Posts;

   2. Comments;

   3. Replies;

   4. publication dates;

   5. Content or a fragment of Content;

   6. the title or designation of the Post under which a Comment or Reply was published;

   7. the Thematic Category of the Post;

   8. a link to the relevant place in the discussion.

3. Activity information is also available to Visitors.

4. User activity reflects the actual state of Content stored in the Portal.

5. Drafts are not part of public activity.

6. Drafts may be displayed to the Account owner in the owner’s own Profile view, but remain invisible to other persons.

7. Deletion of a Post may change the way related activity information is presented, while Comments and Replies may remain available in accordance with the Terms.

§ 90. Followed Users

1. A User’s Profile publicly displays the list of Users followed by that User.

2. The following list may be viewed by Users and Visitors.

3. The Portal does not currently display a separate public count of followed Users.

4. The number of followed Users may be inferred from the number of items visible on the public list.

5. The Profile does not display a public list of persons following a given User.

6. The Portal does not currently display a public count of persons following a given User.

7. Following or unfollowing may result in a corresponding change to the public following list.

§ 91. Topic Reputation on the Profile

1. The Profile publicly displays the User’s current Topic Reputation in individual Categories.

2. Reputation is calculated automatically on the basis of the rules set out in the Terms.

3. The User cannot hide Topic Reputation or disable its display on the Profile.

4. The Portal does not currently display a public history of changes in Topic Reputation.

5. The score visible on the Profile presents the current state calculated by the Portal system.

6. A change in Reactions taken into account by the system, deletion of Content, deletion of a voting Account, detection of manipulation or a change in calculation rules may affect the current score.

§ 92. Public nature of the Account

1. Every active Account has a public Profile.

2. The User may not:

   1. set the entire Profile as private;

   2. restrict Profile visibility only to logged-in Users;

   3. hide all of the User’s public activity;

   4. hide Topic Reputation;

   5. disable public display of published Posts, Comments and Replies.

3. The User may decide on the visibility of selected contact details if the Portal provides such a setting.

4. A User who does not wish to have a public Profile may stop using the Account and begin the Account-deletion procedure.

5. Ceasing to log in without requesting Account deletion does not automatically hide the Profile or Content or terminate the Agreement.

§ 93. Moderation intervention in the Profile

1. The Service Provider may remove, change, hide or restrict a public Profile element if this is necessary due to:

   1. a violation of applicable law;

   2. infringement of a third party’s rights;

   3. a breach of the Terms;

   4. a breach of the Community Standards;

   5. impersonation of another person or entity;

   6. a security threat;

   7. the need to comply with a decision of an authorised authority;

   8. a technical error requiring correction.

2. The Service Provider’s action may concern, in particular:

   1. the avatar;

   2. the Username;

   3. the display name;

   4. the bio;

   5. the Location;

   6. contact details;

   7. links;

   8. other public Profile elements.

3. If the Service Provider removes, changes or restricts a public Profile element because of a breach of the rules, the Service Provider will inform the User about:

   1. the action taken;

   2. the basic reason for the action;

   3. the rule breached, where it can be identified;

   4. the possibility of appeal, where available.

4. Information may not be provided or its scope may be limited if:

   1. applicable law or a decision of an authorised authority prohibits providing the information;

   2. providing the information could endanger the security of the Portal or other persons;

   3. it could hinder the prevention of fraud, abuse or another violation;

   4. the User does not have an active contact channel;

   5. another exception provided for in the Terms or applicable law applies.

5. The Service Provider is not required to obtain the User’s prior consent for a moderation action.

§ 94. Simultaneous login and sessions

1. The User may be logged in to the same Account simultaneously on more than one device or in more than one browser.

2. The Portal does not currently provide:

   1. a list of all active sessions;

   2. a list of devices logged in to the Account;

   3. a “log out from all devices” function.

3. The User should take particular care to protect access to devices on which the User remains logged in.

4. If unauthorised access is suspected, the User should:

   1. reset the password;

   2. secure the e-mail mailbox;

   3. contact the Service Provider.

5. The Service Provider may technically invalidate selected or all Account sessions where necessary for security, Moderation or data-protection reasons.

6. A login session may expire without a specific period being stated, in particular as a result of:

   1. inactivity;

   2. expiry of the validity period;

   3. changing or resetting the password;

   4. technical work;

   5. logging out;

   6. an Account restriction;

   7. operation of Portal safeguards.

§ 95. Service Provider access to Account data

1. The Service Provider may access Account data to the extent necessary to:

   1. provide services;

   2. handle reports and complaints;

   3. assist the User;

   4. recover or secure the Account;

   5. conduct Moderation;

   6. prevent abuse;

   7. correct technical errors;

   8. ensure security;

   9. fulfil a legal obligation;

   10. protect the rights of the Service Provider, User or a third party.

2. Administrative access should be limited to the scope necessary in the relevant matter.

3. The Service Provider may, in particular:

   1. view Account data stored in the system;

   2. change or remove public Profile elements in cases provided for in the Terms;

   3. change the e-mail address after appropriate verification;

   4. block or restrict the Account;

   5. reset or invalidate sessions;

   6. perform other actions necessary to operate the Portal.

4. The Service Provider’s access to the Account does not mean that the Service Provider has the right to use the Account as its owner or publish Content on behalf of the User without an appropriate basis.

5. The rules governing data processing in connection with administrative access are described in the Privacy Policy.

§ 96. No temporary Account deactivation

1. ReputoNode does not currently provide a function for temporary deactivation, hiding or suspension of an Account at the User’s request.

2. A User who wishes to temporarily stop using the Portal may:

   1. log out;

   2. stop publishing and engaging in other activity;

   3. delete selected own Posts;

   4. begin the Account-deletion procedure.

3. Merely ceasing to use the Portal does not hide the Profile, Content or Reputation.

4. A temporary Account restriction or suspension may be applied by the Service Provider under the rules set out in the Terms.

§ 97. Prohibition on selling and transferring an Account

1. Without the Service Provider’s consent, the User may not:

   1. sell the Account;

   2. transfer the Account to another person for payment or free of charge;

   3. rent out the Account;

   4. make the Account available for operation by an unauthorised person;

   5. transfer Topic Reputation to another person or entity;

   6. present the Account as belonging to a person other than its actual owner or the entity on whose behalf it is maintained.

2. Topic Reputation is associated with the activity of a specific Account and may not be sold, inherited, exchanged or transferred between Accounts.

3. In the case of an Account maintained on behalf of a company, organisation, institution, group or project, the person responsible for the Account may be changed if:

   1. the new person is properly authorised;

   2. login credentials are properly secured;

   3. the change is not intended to circumvent the prohibition on selling an Account or to manipulate Reputation;

   4. an appropriate explanation or confirmation of entitlement is provided at the Service Provider’s request.

4. Breach of the prohibition on selling or transferring an Account may result in restriction or blocking of the Account.

§ 98. Death of a User or loss of ability to manage the Account

1. A report concerning the death of a User or the User’s permanent loss of the ability to manage the Account is considered individually.

2. The person making the report may be asked to provide reliable documents confirming:

   1. the User’s death;

   2. the reporting person’s identity;

   3. the relationship with the User;

   4. authority to act;

   5. other circumstances relevant to consideration of the matter.

3. The Service Provider may limit the scope of required documents to information necessary to assess the report.

4. Depending on the circumstances, applicable law and documents provided, the Service Provider may:

   1. secure the Account;

   2. temporarily block the ability to log in;

   3. restrict public visibility of selected data;

   4. begin the Account-deletion procedure;

   5. refuse to transfer access to the Account;

   6. take another action required by law.

5. The Service Provider does not provide a third party with the Account password or login-enabling data solely on the basis of a claim of kinship or acquaintance with the User.

6. Topic Reputation is not inherited or transferred to another person’s Account.

Chapter 9

Publishing Posts, Comments and Replies

§ 99. Entitlement to publish Content

1. Posts, Comments and Replies may be published only by a User who:

   1. has an active Account;

   2. is logged in to the Account;

   3. has access to the relevant Portal function;

   4. has an Account that is not subject to a restriction preventing publication;

   5. has not requested Account deletion or has cancelled such a request before the waiting period expires.

2. Publishing Content means a conscious decision by the User to make it publicly available.

3. Posts, Comments and Replies are publicly available also to Visitors.

4. ReputoNode does not provide the ability to publish Posts, Comments or Replies visible only to selected Users.

5. The author is responsible for the Content in its original wording and for the decision to publish it.

§ 100. Elements of a Post

1. Publishing a Post requires:

   1. providing a title;

   2. selecting one Post Type;

   3. assigning the Post to exactly one Thematic Category;

   4. specifying a Location or leaving the default global Publication Scope;

   5. including at least one element of substantive Content.

2. Substantive Post Content may consist, in particular, of:

   1. text;

   2. a link;

   3. a photo;

   4. a video;

   5. a combination of several supported elements.

3. A Post may consist solely of one supported element, in particular text only, a link only, a photo only or a video only.

4. A Post completely devoid of substantive Content cannot be published.

5. The title is a separate element from the main Post Content.

6. The User should give the Post a title corresponding to its actual content and not misleading recipients.

7. Current technical requirements of the publication form may be indicated directly in the Portal interface.

§ 101. Post Types

1. Before publishing a Post, the User selects one of the following types:

   1. MAKES;

   2. SHARE;

   3. KNOW_HOW;

   4. VOICE.

2. The MAKES type is used for publishing Content in which the User presents something that the User created, built, made or achieved.

3. The SHARE type is used for sharing something that the User saw, found, learned about or created and wishes to make available to the community.

4. The KNOW_HOW type is used for explaining issues, sharing knowledge, teaching, presenting instructions, methods or practical ways of doing something.

5. The VOICE type is used for asking questions, commenting, presenting opinions, positions or reflections, or starting a discussion.

6. The User independently selects the Post Type.

7. The Portal does not assign the Post Type automatically and does not guarantee that the author’s choice is correct.

8. The Post Type may affect the manner in which Topic Reputation is calculated.

9. The User should select the type that best corresponds to the actual nature of the Post.

§ 102. Incorrect Post Type designation

1. The Service Provider may change the Post Type if the designation selected by the author does not correspond to its actual content, including where Reactions have already been recorded on the Post, its Comments or Replies.

2. An ordinary mistake in selecting the Post Type may be corrected without an additional sanction.

3. A breach of the Terms may include, in particular:

   1. deliberately selecting an incorrect Post Type;
   2. repeatedly mislabelling Posts despite earlier information or warnings;
   3. selecting a Post Type in order to obtain a more favourable Reputation result;
   4. using an incorrect type to mislead recipients;
   5. deliberately circumventing rules applicable to individual Post Types.

4. A Post may remain published after its type is changed.

5. The author will be informed about the change made and its basic reason in accordance with the rules concerning Moderation Decisions.

6. If Reactions were recorded before the Post Type was changed, the Portal recalculates their effect on Reputation using the multiplier applicable to the new Post Type. The historical weight of each vote determined when the Reaction was submitted remains unchanged.

§ 103. Thematic Categories

1. Every Post must be assigned to exactly one Thematic Category.

2. It is not possible to:

   1. publish a Post without selecting a Category;

   2. assign one Post to several Categories at the same time.

3. The current list of Categories is available in the Post publication form.

4. Categories available as at the effective date of this version of the Terms include:

   1. Digital & IT;

   2. Science & Discoveries;

   3. Home & Everyday Life;

   4. Art & Aesthetics;

   5. Business & Career;

   6. Technology & Engineering;

   7. Style & Beauty;

   8. People & Health;

   9. Entertainment & Pop Culture;

   10. Society & Media;

   11. Facts & Events;

   12. Travel & Places;

   13. Nature & Planet;

   14. History & Biographies;

   15. Philosophy & Religion;

   16. Food & Drinks.

5. The User should select the Category that best corresponds to the main subject of the Post.

6. If a Post concerns several areas, the author should select the Category corresponding to its dominant content or main purpose of publication.

7. Assignment to a Category affects, in particular:

   1. organisation and filtering of Content;

   2. the manner in which the Post is presented;

   3. the Category in which Reactions affect the Reputation of the author of the Post, Comments and Replies.

8. The Service Provider may develop, merge, rename or withdraw Categories in accordance with the rules concerning development of the Portal.

§ 104. Incorrect Category assignment

1. The Service Provider may change the Category of a Post if the Category selected by the author does not correspond to the main content of the Post, including where Reactions have already been recorded on the Post, its Comments or Replies.

2. An ordinary mistake may be corrected without an additional sanction.

3. A breach of the Terms may include, in particular:

   1. deliberately publishing Posts in incorrect Categories;
   2. repeating incorrect assignments despite earlier information or warnings;
   3. using an inappropriate Category to increase visibility;
   4. using an inappropriate Category to affect Reputation;
   5. mass-publishing the same Content in different Categories.

4. A Post may remain published after the Category is changed.

5. The author will be informed about the change made and its basic reason in accordance with the rules concerning Moderation Decisions.

6. Reactions from other Users may reflect their assessment of whether a Post has been correctly categorised, but submitting an R− Reaction does not replace Moderation or reporting a violation.

7. If Reactions were recorded before the Category was changed, the Portal reassigns the historical Reactions to the new Category and recalculates their effect on Reputation. The historical weight of each vote determined when the Reaction was submitted remains unchanged, and current Reputation values in the affected Categories are rebuilt from the updated history.

§ 105. Post Location

1. The default Publication Scope of a Post is global.

2. The User may leave the global scope or voluntarily assign a more specific Location to the Post.

3. The Post Location may be specified:

   1. using a “Here and now” function or a function of similar meaning;

   2. by searching for a place using an entered phrase;

   3. by indicating a place on a map;

   4. using other mechanisms available in the publication form.

4. The “Here and now” function may use the device’s location only after it has been consciously activated by the User.

5. Access to the device’s location requires appropriate permission granted through the browser, operating system or device.

6. The Portal does not automatically obtain the device’s exact location each time the page is accessed.

7. A Location detected using the device may, before publication, be:

   1. accepted;

   2. changed;

   3. replaced with another place;

   4. generalised to the level of an area, city, region, country or continent;

   5. replaced with Global Scope.

8. The User should check the Location before publication because automatic location determination may be inaccurate.

9. A published Location is a public part of the Post.

10. Indicating a Location does not restrict access to the Post by persons outside the relevant area.

11. The User should exercise particular caution when publishing the exact Location of:

12. a place of residence;

13. a current place of stay;

14. a place where other persons are staying;

15. protected facilities or places whose disclosure could create a risk.

§ 106. Original language of Content

1. The language of a Post, Comment and Reply is automatically detected by the Portal.

2. The User does not manually select the original language before publication.

3. The Portal does not currently provide a function for independently correcting the language designation before or after publication.

4. Automatic language detection may be inaccurate, in particular where the Content:

   1. is very short;

   2. contains words occurring in several languages;

   3. contains proper names, abbreviations or specialist designations;

   4. combines several languages;

   5. consists mainly of numbers, symbols or links.

5. The User may include elements in several languages within one Content item.

6. In the case of multilingual Content, the Portal may assign one principal language.

7. Automatic translation of multilingual Content may be less accurate or may not correctly cover all fragments.

8. Incorrect language detection does not change the author’s responsibility for the original Content.

§ 107. Text and formatting

1. Text fields in Posts, Comments and Replies support plain text.

2. Content may contain, in particular:

   1. letters;

   2. numbers;

   3. punctuation marks;

   4. paragraphs;

   5. emoji;

   6. character strings corresponding to internet addresses.

3. The Portal does not allow the User to execute custom HTML, JavaScript or other programming code in Content.

4. Entering code, markup or commands does not create an obligation for the Portal to execute or format them.

5. The Portal may technically sanitise, encode or restrict entered text in order to protect security and ensure proper display of Content.

6. Forms may be subject to technical limits indicated directly in the Portal interface.

7. As at the effective date of this version of the Terms, the Terms do not specify a fixed length limit for a title, Post, Comment or Reply.

§ 108. Publication and no prior approval

1. A Post, Comment or Reply becomes public immediately after it has been correctly submitted and saved by the Portal.

2. Content is not normally reviewed or approved by the Service Provider before publication.

3. The absence of prior approval does not mean that Content:

   1. complies with applicable law;

   2. complies with the Terms or the Community Standards;

   3. has been verified by the Service Provider;

   4. is true, correct, safe or complete;

   5. has been accepted or endorsed by the Service Provider.

4. The Service Provider may conduct Moderation after publication, in particular after:

   1. independently noticing the Content;

   2. receiving a Report;

   3. receiving information from an authorised authority;

   4. obtaining reliable information about a possible violation.

§ 109. No possibility to edit Content

1. Once published:

   1. a Post cannot be edited;

   2. a Comment cannot be edited;

   3. a Reply cannot be edited.

2. Before publication, the User should check, in particular:

   1. the title;

   2. the text;

   3. the Post Type;

   4. the Category;

   5. the Location;

   6. Media;

   7. links;

   8. personal data contained in the Content;

   9. the correctness and meaning of the statement.

3. The absence of an additional warning in the interface does not release the User from the obligation to check Content before publication.

4. The Service Provider may change the Post Type, Category or an element of Content in cases provided for in the Terms.

5. Technical correction of the way Content is displayed may not be used to make an unauthorised substantive change to the meaning of the author’s statement.

§ 110. Comments

1. Any logged-in User with an active and unrestricted Account may publish a Comment under an available Post.

2. Commenting does not require the consent of the Post author.

3. The author of a Post may not:

   1. disable commenting on the author’s own Post;

   2. determine which Users may comment;

   3. independently delete Comments of other Users.

4. An Account in the 30-day waiting period for deletion may not publish new Comments.

5. Posts published before Account deletion was requested may continue to be commented on by other active Users.

6. A Comment should remain related to the Post or the discussion taking place under it.

7. Publishing off-topic, mass, repetitive Comments or Comments without a legitimate purpose may be regarded as spam or abuse.

§ 111. Replies

1. A Reply may be published only under a Comment.

2. It is not possible to create another level of Reply directly responding to an earlier Reply.

3. All Replies in a given thread are assigned to the main Comment.

4. The author of a Comment may not:

   1. disable the possibility of replying;

   2. determine which Users may reply;

   3. independently delete Replies of other Users.

5. A Reply should remain related to the Comment, Post or ongoing discussion.

6. A User who wishes to address a specific Reply may do so within another Reply assigned to the same Comment, appropriately indicating its addressee or the quoted fragment.

§ 112. Order of Comments and Replies

1. Root Comments are currently ordered primarily by the Topic Reputation of their author in the Category assigned to the Post, from higher to lower. Where the Reputation value is equal, publication time is taken into account.

2. Replies assigned to a given Comment are displayed chronologically according to publication time.

3. The Portal may in the future change the way discussions are ordered or provide additional sorting settings, taking into account transparent parameters such as publication time, Topic Reputation, Reactions or a setting selected by the person viewing the Content.

4. Changing the order of presentation does not change the author, publication time or original meaning of the Content.

5. Basic information about any material method of ordering discussions is made available to persons using the Portal in the Terms, the interface or other informational materials.

§ 113. Deletion of a Post

1. The author may independently delete the author’s own Post.

2. After a Post is deleted:

   1. its title, text, Media, links and other substantive Content cease to be available;

   2. the Post is not displayed in the main feed;

   3. a Reaction cannot be submitted to the deleted Post itself;

   4. the Post page may remain available at its existing address;

   5. information is displayed that the Post was deleted by the author;

   6. the deletion date may be displayed;

   7. existing Comments and Replies remain visible.

3. Under the page of a deleted Post, active Users may continue to:

   1. publish new Comments;

   2. publish Replies;

   3. submit R+ and R− Reactions to existing and new Comments and Replies.

4. Comments and Replies remaining under a deleted Post continue to affect the Reputation of their authors in the Category previously assigned to the Post.

5. Deletion of a Post by its author does not automatically delete statements of other Users.

§ 114. No independent deletion of Comments and Replies

1. A User may not independently delete a published Comment or Reply using the Portal’s standard functions.

2. Comments and Replies remain public also after:

   1. deletion of the Post by its author;

   2. cessation of activity by their author;

   3. submission by the author of an Account-deletion request;

   4. final deletion of the Account, subject to the anonymisation rules.

3. A User may ask the Service Provider by e-mail to delete the User’s own Comment or Reply.

4. The request should, where possible, contain:

   1. identification of the author’s Account;

   2. a link to the Content;

   3. a description of the Content;

   4. the reason for requesting deletion;

   5. information enabling authorship to be confirmed.

5. Each request is considered individually.

6. The mere fact of authorship does not guarantee deletion of a Comment or Reply.

7. The Service Provider may grant the request, in particular where:

   1. the Content contains personal data whose continued publication is not justified;

   2. the Content was published as a result of an obvious mistake;

   3. continued availability of the Content could cause material harm;

   4. the Content violates applicable law, the Terms or the Community Standards;

   5. deletion is required in order to exercise a right of the person concerned;

   6. there is another important and duly justified reason.

8. The Service Provider may refuse deletion if:

   1. authorship cannot be reliably confirmed;

   2. retaining the Content is justified by protection of the rights of other persons;

   3. the Content is needed to establish, pursue or defend claims;

   4. there is a legal obligation to retain it;

   5. the request is manifestly unfounded or constitutes abuse.

§ 115. Responsibility of the Content author

1. The User is responsible for Posts, Comments and Replies published by the User.

2. Before publication, the author should ensure that the Content:

   1. complies with applicable law;

   2. does not infringe the rights of other persons;

   3. complies with the Terms and Community Standards;

   4. does not contain information that the author is not entitled to make public;

   5. does not create an unjustified risk to other persons;

   6. does not mislead recipients in an unlawful or harmful manner.

3. The User is responsible for the User’s statements, opinions, allegations, instructions, recommendations and materials.

4. Publication of Content in ReputoNode does not mean that it has been approved, confirmed or assumed as the responsibility of the Service Provider.

5. The author should distinguish:

   1. fact from opinion;

   2. personal experience from verified information;

   3. an assumption from a certain statement;

   4. advertising from an independent recommendation;

   5. automatically generated Content from authentic material where lack of a designation could mislead recipients.

§ 116. Truthfulness and reliability of Content

1. ReputoNode does not normally verify the truthfulness, completeness or currency of Content published by Users.

2. Content available in the Portal may contain:

   1. errors;

   2. outdated information;

   3. subjective opinions;

   4. incomplete data;

   5. incorrect conclusions;

   6. materials generated or modified automatically.

3. Reactions and Topic Reputation do not constitute a guarantee that Content is true.

4. A person using information should verify it using appropriate reliable sources, especially before making an important decision.

5. The Service Provider may moderate misleading Content if it violates applicable law, the Terms or the Community Standards.

§ 117. Specialist Content and advice

1. Content published in ReputoNode may concern, in particular:

   1. health;

   2. law;

   3. finance;

   4. safety;

   5. technology;

   6. other fields requiring specialist knowledge.

2. Content published by Users does not replace individual advice provided by a person with appropriate qualifications and knowledge of the recipient’s specific situation.

3. An author publishing specialist Content should:

   1. avoid presenting uncertain information as undisputed fact;

   2. clearly indicate material limitations and risks;

   3. not claim qualifications the author does not possess;

   4. provide sources where they are relevant to assessing the credibility of the statement;

   5. clearly distinguish general information from individual advice.

4. The User should not make decisions that may seriously affect the User’s health, life, safety, legal situation or finances solely on the basis of Content posted in the Portal.

5. The author’s Reputation in a given Category does not constitute formal confirmation of education, professional authorisations or qualifications.

§ 118. Personal data and privacy of other persons

1. The User may not publish another person’s personal data without an appropriate legal basis or consent where required.

2. Particular caution should be exercised when publishing:

   1. a residential address;

   2. an exact place of stay;

   3. a telephone number;

   4. a private e-mail address;

   5. document numbers;

   6. financial data;

   7. health data;

   8. data concerning private life;

   9. private correspondence;

   10. information about minors;

   11. other data that could expose a person to harm, fraud, harassment or danger.

3. The fact that data is known to the author or available elsewhere does not always mean that the author has the right to further disseminate it publicly.

4. When publishing a screenshot, document, message or photograph, the User should remove or obscure data whose disclosure is not necessary.

5. Publishing data for the purpose of the following is prohibited:

   1. intimidation;

   2. harassment;

   3. revenge;

   4. exerting pressure;

   5. encouraging other persons to attack;

   6. causing harm.

§ 119. Image, voice and recordings of other persons

1. The User is responsible for holding the rights, consents or other basis permitting public disclosure of:

   1. another person’s image;

   2. that person’s voice;

   3. a recording of a conversation;

   4. a video or photograph depicting that person;

   5. other materials allowing that person to be identified.

2. The User should take into account, in particular:

   1. the right to one’s image;

   2. the right to privacy;

   3. personal rights;

   4. personal-data protection;

   5. confidentiality of communications;

   6. protection of minors.

3. A person’s mere participation in an event or conversation does not always constitute consent to public publication of a recording.

4. Publishing materials made or obtained unlawfully is prohibited.

5. Materials depicting minors require particular caution and may not expose them to harm, ridicule, sexualisation, identification of their location or another risk.

§ 120. Quotation

1. The User may quote fragments of other persons’ statements to the extent permitted by law.

2. The Portal does not currently provide an automatic quotation function.

3. A User quoting another person’s statement should:

   1. independently copy the relevant fragment;

   2. clearly mark the fragment as a quotation;

   3. where possible, identify the author and source;

   4. not distort the meaning of the statement;

   5. not omit context in a misleading manner;

   6. limit the scope of the quotation to the justified purpose.

4. Quotation may not be used to circumvent copyright or appropriate the essential part of another person’s Content.

5. The User is responsible for ensuring that the quotation and the manner in which it is used comply with applicable law.

§ 121. Promotional Content concerning the User’s own activity

1. A User may publish Content concerning the User’s own products, services, activity, project, company or organisation.

2. Such Content is permitted if:

   1. it has been assigned to the appropriate Category;

   2. it is consistent with the nature of the selected Post Type;

   3. it does not constitute spam;

   4. it is not duplicated on a mass scale;

   5. it does not mislead recipients;

   6. it does not violate provisions concerning advertising, competition or consumer protection;

   7. it does not promote goods or services whose advertising or offering is prohibited.

3. The User may not use the Portal solely for mass and repetitive publication of promotional materials that provide no value to the community.

4. The Service Provider may restrict or remove promotional Content constituting spam or violating Portal rules.

§ 122. Sponsored Content and benefits received by the author

1. A User may publish Content for which the User has received or is to receive a benefit.

2. A benefit includes, in particular:

   1. payment;

   2. a free product or service;

   3. a discount;

   4. commission;

   5. a share in revenue;

   6. the ability to keep a tested product;

   7. another financial or personal benefit connected with publication.

3. Content connected with a benefit must clearly inform recipients from the outset of its advertising, sponsored or commercial nature.

4. The designation should be:

   1. visible;

   2. understandable;

   3. placed in the Content or its direct designation;

   4. worded appropriately for the language of publication.

5. The designation may, in particular, take the form of:

   1. “advertisement”;

   2. “sponsored material”;

   3. “advertising cooperation”;

   4. another equally unambiguous message.

6. A designation that is unclear, hidden, placed only at the end of lengthy Content or understandable only to some recipients is not sufficient.

7. The author is responsible for complying with legal obligations concerning advertising, sponsorship, recommendations and commercial information.

§ 123. Duplication of Content and spam

1. Mass or repetitive publication of the same or nearly identical Content is prohibited:

   1. on one Account;

   2. on several Accounts;

   3. in several Categories;

   4. under multiple Posts;

   5. in the form of Posts, Comments or Replies.

2. Spam may include, in particular:

   1. publishing repetitive advertisements;

   2. posting many unrelated links;

   3. publishing serial Comments unrelated to the discussion;

   4. automated publication;

   5. mass promotion of one’s own products or services;

   6. repeating Content to increase its visibility;

   7. publishing apparently different Content with essentially identical messaging.

3. Republishing similar Content does not in itself constitute a violation if justified by a new context, update, continuation or another genuine purpose.

4. Assessment of whether an action constitutes spam may take into account:

   1. frequency;

   2. number of publications;

   3. similarity of Content;

   4. relation to the Category and discussion;

   5. impact on other Users;

   6. intention to circumvent restrictions.

§ 124. Valueless and artificially increased activity

1. Publishing Content solely for the purpose of artificially increasing Account activity, visibility or Reputation is prohibited.

2. A violation may include, in particular, serial publication of:

   1. Posts devoid of meaningful content;

   2. single characters or random text strings;

   3. repetitive Comments;

   4. Replies unrelated to the discussion;

   5. Content intended solely to provoke Reactions;

   6. artificial questions or statements serving the exchange of ratings.

3. The mere fact that Content is short, simple or has received few Reactions does not automatically mean that it is valueless.

4. Context, frequency, repetition and the actual purpose of the action are taken into account in the assessment.

§ 125. Content created or modified by artificial intelligence

1. A User may publish Content generated or materially modified using artificial intelligence or other automated tools.

2. The author remains responsible for such Content under the same rules as for Content prepared independently.

3. Before publication, the User should check, in particular:

   1. the truthfulness of information;

   2. the possibility of infringing third-party rights;

   3. the presence of personal data;

   4. compliance with applicable law and the Community Standards;

   5. the possibility of misleading recipients;

   6. correct attribution of authorship.

4. Content should be clearly designated as generated or materially modified by artificial intelligence where lack of such a designation could mislead recipients.

5. The designation obligation applies in particular to material presenting a realistic but inauthentic:

   1. image of a person;

   2. voice of a person;

   3. course of an event;

   4. document;

   5. statement attributed to a specific person;

   6. proof that a particular action was performed;

   7. specialist material suggesting human or expert authorship.

6. Artificial intelligence may not be used for:

   1. impersonation;

   2. fraud;

   3. creating false evidence;

   4. infringing the rights of other persons;

   5. automated publication without the Service Provider’s consent;

   6. manipulating Reactions or Reputation;

   7. creating prohibited Content.

7. Designating the use of artificial intelligence does not release the author from responsibility.

§ 126. Automatic translations of Content

1. The author is responsible for the original Content published by the author.

2. ReputoNode may automatically translate Posts, Comments and Replies in accordance with the rules set out in the Terms.

3. An automatic translation may differ from the original Content and contain errors, simplifications or inaccuracies.

4. The author is not responsible for an error introduced solely by ReputoNode’s translation mechanism if the error was not present in the original Content.

5. If the author notices that an automatic translation may cause a material risk, infringement of rights or serious misleading of recipients, the author may inform the Service Provider.

6. In the event of a discrepancy, the Content in the original language is regarded as the author’s statement.

7. ReputoNode does not guarantee the full accuracy, completeness or consistency of an automatic translation with the author’s intention.

Chapter 10

Photos, videos, links and other materials

§ 127. Media in Posts

1. The User may add Media supported by the Portal to Posts, including in particular:

   1. photos;

   2. graphics;

   3. videos;

   4. other supported visual or audiovisual materials.

2. One Post may contain any number of Media, subject to the Portal’s technical limitations.

3. Media may be combined in one Post with:

   1. text;

   2. links;

   3. other supported Content elements.

4. A Post may consist solely of one Medium if it meets the remaining Post-publication requirements.

5. Current types of supported files, their maximum size and other technical requirements may be indicated directly in the Portal interface.

6. The Service Provider may change supported formats, limits and technical requirements where justified by Portal development, security, performance or technical compatibility.

7. A change to technical file-upload parameters that does not materially restrict the Portal’s basic functions does not require an amendment to the Terms each time.

§ 128. Uploading files to ReputoNode

1. Media may be uploaded directly to ReputoNode infrastructure using functions made available in the Post-creation form.

2. An uploaded file may first be stored temporarily and then moved to a location intended for storage of Media associated with the Post.

3. A temporary file may be deleted if:

   1. the User removes it from the Post being created;

   2. publication of the Post is not completed;

   3. the file is corrupted;

   4. processing ends with an error;

   5. the file violates technical or security requirements;

   6. its technical retention period expires.

4. After a Draft is saved or a Post is published, Media may be moved from temporary storage to the target storage area.

5. The Service Provider may assign new technical names to uploaded files independently of the names given by the User.

6. The file name used in the system does not need to correspond to the name previously used for the file on the User’s device.

§ 129. Technical processing of files

1. The User acknowledges that uploaded Media may be technically processed in order to ensure:

   1. the ability to save them;

   2. compatibility with formats supported by the Portal;

   3. proper display;

   4. playback on different devices;

   5. performance;

   6. security;

   7. reduced disk-space and data-transfer usage.

2. Technical processing may include, in particular:

   1. changing the file format;

   2. changing the codec;

   3. changing the bitrate;

   4. changing compression parameters;

   5. changing resolution;

   6. changing dimensions;

   7. file optimisation;

   8. creating a thumbnail;

   9. creating a version intended for display in the Portal;

   10. other technical operations necessary for operation of the Portal.

3. Uploaded videos may be automatically converted to a format and codecs supported by ReputoNode.

4. As a result of processing, the original file may be replaced with a processed version.

5. ReputoNode does not guarantee retention of an uploaded file in its original technical form.

6. Processing may change:

   1. file size;

   2. image parameters;

   3. audio parameters;

   4. quality;

   5. technical properties;

   6. metadata.

7. A minor loss of quality resulting from the normal technical file-processing process does not constitute improper performance of the service.

§ 130. File metadata

1. Uploaded Media may contain metadata previously recorded by the device, application or software used by the User.

2. Metadata may include, in particular:

   1. the file-creation date;

   2. the device model;

   3. technical parameters;

   4. software information;

   5. location data;

   6. other information stored in the file structure.

3. ReputoNode does not guarantee automatic removal of all metadata from every uploaded file.

4. Before uploading a file, the User should check whether it contains data that the User does not wish to disclose or transmit to the Portal.

5. The Service Provider may in the future introduce automatic removal or limitation of certain types of metadata.

6. The mere fact that metadata is not displayed in the Portal interface does not mean that it is not contained in the uploaded file or its technical version.

§ 131. External videos and embedded materials

1. A User may add to a Post a link leading to material located on an external service.

2. If the external service allows the relevant material to be embedded, the Portal may display it directly within the Post.

3. The ability to embed material depends on:

   1. the settings of the external service;

   2. the settings of the specific material;

   3. availability of the external service;

   4. technical configuration;

   5. the decision of the owner or operator of the external service.

4. In particular, a link to a video hosted on YouTube may be displayed as embedded material if YouTube allows that video to be embedded.

5. ReputoNode does not guarantee that external material:

   1. can be embedded;

   2. will remain available;

   3. will play without interruption;

   4. will not be changed or removed by its owner or the operator of the external service.

6. External material remains stored and made available by the relevant external service unless the User additionally uploaded a copy of it to ReputoNode.

§ 132. External links

1. A User may include links in Posts leading to external websites and services.

2. The User is responsible for knowingly publishing a link and for whether, at the time of publication, its use complies with applicable law, the Terms and the Community Standards.

3. The User is not responsible for a later change to the content of the destination website made without the User’s participation by the owner or operator of that website.

4. If, after publication, the User learns that a link posted by the User leads to unlawful, dangerous or fraudulent Content, the User should inform the Service Provider.

5. ReputoNode is not responsible for:

   1. availability of an external website;

   2. content published by its operator;

   3. subsequent changes to its content;

   4. security of the external service;

   5. its privacy policy;

   6. the manner in which data is processed by the third party;

   7. transactions concluded outside ReputoNode.

6. Accessing an external website may be subject to separate terms and privacy rules of that entity.

§ 133. Automatic link preview

1. The Portal may automatically retrieve publicly available information about the website indicated by the User in order to prepare a link preview.

2. The preview may include, in particular:

   1. the page title;

   2. description;

   3. image;

   4. domain or service name;

   5. destination address.

3. Information used for the preview may come from metadata of the external website.

4. ReputoNode does not guarantee:

   1. accuracy of retrieved information;

   2. completeness of the preview;

   3. consistency of the image with the current content of the website;

   4. the ability to create a preview for every link.

5. The absence of a preview does not mean that the link is invalid.

6. Creation of a link preview by ReputoNode does not constitute a recommendation, approval or verification of the destination website.

§ 134. Dangerous and prohibited links

1. Publishing links leading in particular to the following is prohibited:

   1. malicious software;

   2. phishing;

   3. websites used to obtain data fraudulently;

   4. fraud;

   5. Illegal Content;

   6. Content infringing third-party rights;

   7. websites used to circumvent safeguards;

   8. unlawfully distributed works;

   9. other resources endangering Users or the Portal.

2. The Service Provider may:

   1. remove the link;

   2. block the possibility of opening it;

   3. remove the link preview;

   4. restrict visibility of the Post;

   5. remove the entire Post;

   6. take other moderation measures provided for in the Terms.

3. The Service Provider may also block specific domains or addresses where justified by security or repeated violations.

§ 135. Rights to published Media

1. The User may publish only Media to which the User holds the appropriate rights or another legal basis permitting their use in the Portal.

2. The User may, in particular, publish:

   1. materials created independently by the User;

   2. materials to which the User holds the appropriate rights;

   3. materials made available under an appropriate licence;

   4. materials for which the owner has granted appropriate consent;

   5. third-party materials used within the limits permitted by law.

3. The mere fact of finding a photo, video, graphic or other material on the Internet does not mean that the User has the right to further publicly distribute it.

4. The User is responsible for correctly identifying the author or source where required by applicable law, licence terms or the manner in which the material is used.

5. The User may not remove, conceal or alter authorship designations, watermarks or rights information in order to mislead recipients.

6. Detailed rules concerning intellectual-property rights may be set out in further provisions of the Terms.

§ 136. Protected elements contained in a recording

1. The User’s responsibility also covers elements contained within an uploaded photo, video or recording.

2. This applies, in particular, to:

   1. music;

   2. sound recordings;

   3. films;

   4. television programmes;

   5. graphics;

   6. photographs;

   7. works of visual art;

   8. graphic marks;

   9. texts;

   10. other protected materials.

3. The User should have an appropriate basis for using such elements unless their use falls within the limits permitted by law.

4. The fact that protected material was accidentally or automatically recorded by the User’s device does not always mean that it may be publicly distributed without restriction.

§ 137. Images of other persons

1. The User is responsible for having the right to disseminate the image of a person depicted in a published photo, video or other material.

2. Where applicable law requires the consent of the person depicted, the User should obtain it before publication.

3. The User should also take into account cases where applicable law permits dissemination of an image without consent.

4. ReputoNode does not normally verify before publication whether the User has obtained the required consents.

5. Publication of an image may not infringe:

   1. applicable law;

   2. privacy;

   3. personal rights;

   4. personal-data protection;

   5. the safety of the person depicted.

6. Use of an image for impersonation, fraud, harassment, humiliation or causing harm is prohibited.

§ 138. Voice, conversations and recordings of other persons

1. A User may publish a recording of another person’s voice, conversation or statement only where the User has an appropriate legal basis to do so.

2. The User should take into account, in particular:

   1. the right to privacy;

   2. personal rights;

   3. personal-data protection;

   4. confidentiality of communications;

   5. copyright or related rights;

   6. the reasonable expectation of confidentiality of the conversation.

3. The mere fact that the User participated in a conversation does not automatically mean that the User has the right to distribute it publicly.

4. Publishing recordings obtained or used unlawfully is prohibited.

§ 139. Materials depicting minors

1. Although a ReputoNode Account may be held only by an adult, published Media may depict minors.

2. Publishing materials depicting minors requires particular caution.

3. A User may not publish material that:

   1. sexualises a minor;

   2. depicts the minor in a pornographic context;

   3. humiliates or ridicules the minor in a manner capable of causing harm;

   4. infringes the minor’s privacy;

   5. discloses data that may expose the minor to danger;

   6. without justification reveals the minor’s exact location;

   7. encourages violence, exploitation or abuse;

   8. infringes the minor’s personal rights or other rights.

4. The User is responsible for having the consents or other grounds required for publication of material depicting a minor.

5. The Service Provider may apply a particularly cautious moderation approach to materials depicting minors, guided by protection of their safety and rights.

§ 140. Pornographic materials

1. Publishing pornography in ReputoNode is prohibited.

2. The prohibition includes, in particular:

   1. materials depicting sexual acts in a pornographic manner;

   2. materials created primarily to cause sexual arousal through explicit depiction of genitals or sexual acts;

   3. pornographic photographs;

   4. pornographic videos;

   5. pornographic animations;

   6. pornographic materials generated or modified by artificial intelligence.

3. Any sexual or pornographic material depicting minors or persons appearing to be minors is strictly prohibited.

4. The prohibition on pornography does not automatically prohibit every material containing nudity.

§ 141. Nudity in materials

1. Material containing nudity may be permitted if its nature, context and manner of presentation are not pornographic.

2. A permissible context may include, in particular:

   1. education;

   2. medicine;

   3. science;

   4. history;

   5. documentation;

   6. art;

   7. social information;

   8. other justified lawful purposes.

3. Materials containing visible intimate body parts should be appropriately censored, covered, blurred or cropped to the extent necessary to comply with Portal rules.

4. In particular, uncensored exposure of genitals or other clearly sexual elements of an image is not permitted unless necessary due to an exceptional lawful and justified context.

5. Merely designating material as artistic, educational or medical does not determine its permissibility.

6. The Service Provider assesses material taking into account:

   1. its dominant nature;

   2. the manner of presentation;

   3. context;

   4. purpose of publication;

   5. risk to persons depicted;

   6. the possibility of access to the Portal by persons without an Account.

7. ReputoNode is intended for adult Users, but the public nature of the Portal means that Content should be published taking into account the possibility of incidental access by minors.

§ 142. Graphic materials

1. Materials depicting violence, serious injury, blood, death, corpses, consequences of accidents, warfare or other graphic events may be permitted where there is a justified context for publication.

2. A justified context may include, in particular:

   1. information about current events;
   2. education;
   3. science;
   4. history;
   5. documentation;
   6. warnings about danger;
   7. social analysis.

3. Graphic materials published primarily for the purpose of the following are prohibited:

   1. sensationalising suffering;
   2. humiliating a victim;
   3. glorifying violence;
   4. encouraging violence;
   5. intimidation;
   6. harassment;
   7. promoting unlawful conduct.

4. The Service Provider may remove, restrict or appropriately designate material if its form is disproportionate to the justified purpose of publication.

5. Detailed rules concerning graphic materials may be set out in the Community Standards.

§ 143. Materials generated or modified by artificial intelligence

1. Photos, videos and other Media generated or materially modified using artificial intelligence are subject to the rules concerning AI-generated Content.

2. The User should designate material if its synthetic or modified nature is not obvious and lack of a designation could mislead recipients.

3. This applies, in particular, to:

   1. deepfakes;

   2. realistic fake recordings;

   3. a synthetic image of a real person;

   4. a synthetic voice of a real person;

   5. material depicting an event that did not take place;

   6. a modified document;

   7. false evidentiary material.

4. Use of artificial intelligence does not release the User from the obligation to hold rights to the materials used or from responsibility for the result of publication.

§ 144. Illegal copies and infringement of rights to materials

1. Publishing, making available or knowingly linking to materials distributed in infringement of intellectual-property rights is prohibited.

2. The prohibition includes, in particular:

   1. illegal copies of films;

   2. illegal streams;

   3. illegal copies of music;

   4. illegal copies of books;

   5. illegal copies of computer programs;

   6. cracks;

   7. illegal licence keys;

   8. tools used to unlawfully circumvent safeguards;

   9. other materials distributed without the required rights.

3. Publication of information, discussions, analyses or quotations concerning such materials is permitted if the manner of use complies with applicable law and is not intended to facilitate infringement.

§ 145. Corrupted materials or materials threatening the Portal

1. ReputoNode may refuse to accept, process or publish a file if:

   1. it is corrupted;

   2. it cannot be read correctly;

   3. it cannot be processed correctly;

   4. it does not correspond to a supported format;

   5. it exceeds technical limitations;

   6. it contains malicious code;

   7. it may pose a security threat;

   8. it may disrupt operation of the Portal;

   9. processing it would require disproportionate resources.

2. The Service Provider may delete such a file even after it has previously been saved if the threat or technical problem is detected later.

3. ReputoNode does not guarantee that every file matching a supported extension can be processed correctly.

4. ReputoNode does not guarantee full antivirus scanning of every uploaded file.

§ 146. Reporting infringements concerning Media

1. A person who believes that published Media infringes that person’s rights may report the matter using the Report mechanism available in the Portal or at legal@reputonode.com.

2. A Report may concern, in particular:

   1. unlawful use of an image;
   2. unlawful use of a voice;
   3. infringement of privacy;
   4. infringement of personal-data rights;
   5. copyright infringement;
   6. infringement of personal rights;
   7. publication without required consent;
   8. another violation of law.

3. A Report should, where possible, contain:

   1. a link to the material;
   2. identification of the element concerned;
   3. a description of the infringement;
   4. information about the right or interest of the reporting person;
   5. contact details;
   6. available information allowing the merits of the Report to be assessed.

4. The Service Provider considers such Reports individually.

5. The Service Provider may request additional information or documents where necessary to reliably establish the circumstances.

6. A Report from a person depicted in a photo or video may also be considered where that person does not have a ReputoNode Account.

7. After analysing the matter, the Service Provider may, in particular:

   1. leave the material unchanged;
   2. remove the Medium;
   3. remove the entire Post;
   4. restrict access;
   5. request additional explanations from the author;
   6. take another action required by applicable law or the Terms.

§ 147. Deletion of Media from a Draft

1. The User may remove Media from a Draft while editing it.

2. If Media is removed from a Draft, the corresponding file may be physically deleted from the Portal infrastructure.

3. The file may not be deleted if it is still used by other Content or retention is necessary for technical, security or legal reasons.

4. Deletion of the entire Draft may result in deletion of the associated Media if they are not needed elsewhere.

§ 148. Media after deletion of a published Post

1. After a published Post is deleted, its photos, videos and other Media cease to be publicly presented as Content of that Post.

2. Deletion of a Post does not necessarily mean immediate physical deletion of every associated file from ReputoNode’s technical infrastructure.

3. Files may be temporarily retained after Post deletion where necessary, in particular for:

   1. performance of technical and housekeeping operations;

   2. periodic deletion of unused files;

   3. ensuring security;

   4. incident handling;

   5. protection against abuse;

   6. establishment, pursuit or defence of claims;

   7. compliance with a legal obligation;

   8. handling backups.

4. Once the purpose of further retention ceases, Media should be deleted in accordance with the adopted retention rules and operation of the Portal infrastructure.

5. The Service Provider may use an automatic or periodic mechanism for deleting files that are no longer associated with active Content.

6. The Terms do not guarantee a specific time for physical deletion of a file after deletion of the Post.

7. The rules concerning processing of personal data contained in Media are also set out in the Privacy Policy.

§ 149. Media after Account deletion

1. If the User does not delete the User’s published Posts before final Account deletion, those Posts may remain public after anonymisation of the author in accordance with the Account-deletion rules.

2. Media contained in such Posts also remain publicly available unless removed or restricted under the Terms or applicable law.

3. This applies, in particular, to:

   1. photos;
   2. graphics;
   3. videos;
   4. other materials stored within the structure of the remaining Post.

4. A User who does not want specific Media to remain in the Portal after Account deletion should delete the Posts containing those Media before beginning the Account-deletion procedure. After requesting Account deletion, the User may for this purpose cancel the request, delete the relevant Posts and then begin the procedure again.

5. Mere deletion or anonymisation of the Account does not guarantee removal of an image, voice, captions, watermarks or other information contained within a Medium.

6. The User should take the above rule into account before beginning the Account-deletion procedure.

7. Independently of the above, an interested person may submit a separate request concerning a specific Medium where that person has a legal basis or another justified basis provided for in the Terms.

§ 150. ReputoNode is not a backup-storage service

1. ReputoNode is not intended for creating backups or long-term archiving of the User’s private files.

2. The User should independently keep original copies of photos, videos and other materials that the User wishes to retain independently of the Portal.

3. The Service Provider does not guarantee the ability to download from the Portal a file in its original technical form.

4. Media may be:

   1. processed;

   2. compressed;

   3. converted;

   4. deleted together with Content;

   5. deleted for technical reasons;

   6. deleted as a result of Moderation;

   7. lost as a result of failure despite appropriate protective measures being applied.

5. The User should not treat ReputoNode as the only place to store important or irreplaceable materials.

§ 151. No guarantee of continuous availability of Media

1. The Service Provider does not guarantee uninterrupted availability of every photo, video, link or external material.

2. Media may be periodically unavailable, in particular due to:

   1. failure;

   2. technical work;

   3. conversion;

   4. network problems;

   5. file corruption;

   6. problems with an external service;

   7. a change to an external link;

   8. moderation measures;

   9. the need to ensure security.

3. ReputoNode may reprocess Media where necessary for compatibility with newer technical infrastructure.

4. A technical change to the method of storing or delivering a file does not change authorship or rights to the published material.

Chapter 11

Copyright, licence and intellectual property

§ 152. User rights to Content

1. The User retains rights to Content published in ReputoNode to the extent that such rights belong to the User.

2. Publishing Content in ReputoNode does not transfer to the Service Provider the User’s economic copyrights or other intellectual-property rights.

3. The User may continue to use the User’s Content outside ReputoNode, in particular by:

   1. publishing it on other services;

   2. making it available to other persons;

   3. licensing it;

   4. using it commercially;

   5. disposing of the rights held by the User in accordance with applicable law.

4. ReputoNode does not acquire exclusivity to use User Content.

5. The User may grant ReputoNode only such rights as the User can lawfully dispose of.

6. If Content is not protected by copyright or the User does not hold certain exclusive rights to it, the provisions of this Chapter apply to the appropriate extent.

§ 153. User declaration concerning rights to Content

1. By publishing Content, the User declares that:

   1. the User is its creator or holds appropriate rights to use it;

   2. the User has the consents, licences, authorisations or other legal grounds required for publication;

   3. the User is entitled to grant ReputoNode the licence specified in the Terms;

   4. publication and use of the Content in accordance with the Terms do not infringe third-party rights.

2. The User should take into account, in particular:

   1. copyright;

   2. related rights;

   3. image rights;

   4. personal rights;

   5. trademark rights;

   6. design rights;

   7. database rights;

   8. trade secrets;

   9. other intellectual-property rights or rights protected by law.

3. If Content was created jointly by several persons, the User is responsible for having the right to publish it and grant a licence to the extent required by the Terms.

4. If the User publishes Content on behalf of a company, organisation, institution, group or other entity, the User is responsible for having appropriate authority to do so.

§ 154. Licence granted to ReputoNode

1. Upon publishing Content, or saving it in ReputoNode to the extent requiring technical processing, the User grants the Service Provider a non-exclusive, royalty-free licence to use the Content to the extent necessary to provide ReputoNode services.

2. The licence is granted without territorial limitation.

3. The licence does not restrict the User’s right to use the Content or grant rights to it to other entities.

4. The licence does not entitle the Service Provider to use User Content for purposes unrelated to operating, providing, securing, moderating or developing ReputoNode, unless the User gives separate consent or another legal basis exists.

5. In particular, acceptance of the Terms alone does not authorise the Service Provider to use User Content in external advertising or promotional materials for ReputoNode.

§ 155. Scope of the licence

1. The licence covers use of Content to the extent necessary for operation of the Portal, in particular by:

   1. fixation;

   2. storage in information systems;

   3. technical reproduction;

   4. storage;

   5. creation of backups;

   6. transmission between systems or servers;

   7. making it available to the public in such a way that persons using the Portal may access the Content at a place and time individually chosen by them;

   8. displaying it in the Portal;

   9. transmission over telecommunications networks;

   10. technical adaptation to devices, browsers and methods of presentation;

   11. compression;

   12. conversion;

   13. changing technical file parameters;

   14. creating thumbnails and preview versions;

   15. technical cropping or scaling;

   16. creating and storing translations;

   17. presenting automatic translations;

   18. performing other technical operations necessary to provide services in accordance with the Terms.

2. Use of Content under the licence should remain connected with the operation of ReputoNode.

3. Under this licence, the Service Provider is not entitled to freely edit, change the meaning of or present Content as the Service Provider’s own statement.

§ 156. Automatic translations

1. The licence includes the right to create automatic translations of Content where the Portal provides such a function.

2. Translation may apply, in particular, to:

   1. Posts;

   2. Comments;

   3. Replies;

   4. Profile bio;

   5. other supported text elements.

3. ReputoNode may:

   1. transmit Content to a tool or service used to perform the translation;

   2. save the resulting translation;

   3. store the translation in the database;

   4. publicly display the translation to persons using the relevant language version of the Portal;

   5. replace or regenerate the translation where technically necessary.

4. Automatic translation does not transfer rights to the original Content to the Service Provider.

5. The original version of the Content remains the version constituting the author’s statement.

§ 157. Technical and moderation modifications

1. The Service Provider may make technical changes to Content where necessary for its storage, security, display, processing or availability.

2. Technical changes should not result in an unjustified substantive alteration of the meaning of the User’s statement.

3. Independently of technical changes, the Service Provider may carry out moderation intervention provided for in the Terms.

4. Moderation intervention may include, in particular:

   1. changing the Post Category;

   2. changing the Post Type;

   3. removing a link;

   4. removing a Medium;

   5. limiting visibility;

   6. removing a specific fragment of Content;

   7. removing the entire Content.

5. The Service Provider may remove only a specific fragment of Content if this is sufficient to remedy the violation and there is no need to remove the entire publication.

6. This applies, in particular, to a fragment containing:

   1. unlawfully published personal data;

   2. particularly protected data;

   3. private contact details;

   4. information infringing personal rights;

   5. material infringing intellectual-property rights;

   6. other Content whose continued public availability is impermissible.

7. When removing a fragment of Content, the Service Provider should, where possible, limit the intervention to the part requiring removal.

8. Such action constitutes Moderation and does not mean that the Service Provider assumes authorship of the remaining part of the Content.

§ 158. Duration of the licence

1. The licence applies for the period during which the relevant Content is stored or made available in ReputoNode.

2. In the case of Content remaining in the Portal after Account deletion, the licence remains effective to the extent necessary for continued storage and availability of such Content in accordance with the Terms.

3. This applies, in particular, to the following remaining after anonymisation:

   1. Posts;

   2. Comments;

   3. Replies;

   4. Media contained in remaining Posts.

4. If Content is deleted, the licence expires to the extent that further use of the Content is no longer necessary.

5. The licence may, however, remain effective for the period necessary to:

   1. complete the technical deletion process;

   2. delete technical copies;

   3. handle backups;

   4. preserve evidence of a violation;

   5. fulfil a legal obligation;

   6. establish, pursue or defend claims;

   7. ensure Portal security.

6. When the basis for continued storage of the Content ceases, the licence expires to the extent that there is no other legal basis for continued use.

§ 159. Deletion of a Post and the licence

1. Deletion of a Post by the author ends its public availability to the extent specified in the Terms.

2. The licence concerning a deleted Post remains effective only to the extent and for the period necessary to:

   1. carry out the technical deletion process;

   2. temporarily retain Media;

   3. maintain backups;

   4. secure systems;

   5. handle reports and disputes;

   6. fulfil legal obligations;

   7. protect or pursue claims.

3. Deletion of a Post does not cause expiry of the licence concerning Comments and Replies of other Users that remain public in accordance with the Terms.

§ 160. Comments and Replies

1. The licence concerning a Comment or Reply remains in force for as long as the relevant Content is stored or made available in ReputoNode.

2. Final deletion of the author’s Account does not automatically cause expiry of the licence to Comments and Replies remaining in the Portal after anonymisation.

3. If a Comment or Reply is permanently deleted, the licence expires subject to necessary technical, legal and security retention.

§ 161. No consent to external promotional use

1. Public publication of Content in ReputoNode does not mean that the author consents to the Service Provider using that Content in external advertising or promotional activities.

2. Without a separate basis, the Service Provider does not use User Content, in particular:

   1. in paid ReputoNode advertisements;

   2. on external ReputoNode social-media profiles;

   3. in promotional materials;

   4. in promotional press materials;

   5. in graphic, video or printed advertisements.

3. Use of public Content for such a purpose may take place with the author’s consent or on another basis provided for by law.

4. The provisions of this paragraph do not restrict the possibility of:

   1. displaying Content within the Portal itself;

   2. generating a preview of a public link;

   3. indexing public pages by independent search engines;

   4. technically making Content available as necessary for ReputoNode to operate.

§ 162. Indexing by search engines

1. Public Content, Profiles and ReputoNode pages may be accessible to Internet search engines.

2. Independent search engines may, in particular:

   1. index public pages;

   2. display their titles;

   3. present Content excerpts;

   4. present public graphics or thumbnails;

   5. store technical copies or cached versions in accordance with the operator’s rules.

3. ReputoNode does not guarantee immediate removal of information from the results of an independent search engine after Content is deleted or changed in the Portal.

4. The Service Provider is not responsible for the operation of independent search engines, subject to obligations arising from applicable law.

§ 163. Sharing public links

1. Any person may share with other persons a link leading to a public Post, Profile or another public ReputoNode page.

2. Sharing a link does not transfer rights to the Content.

3. A person sharing a link does not acquire the right to:

   1. copy the entire Content;

   2. claim authorship of it;

   3. use it commercially without an appropriate basis;

   4. distribute Media separately from the Portal where this would require the rights holder’s consent.

4. A link may be shared in other services, messages, documents and publications in accordance with applicable law.

§ 164. Public nature of Content and intellectual-property rights

1. Making Content publicly available does not mean that its author waives any rights.

2. Another User or Visitor does not, solely because Content is public, acquire the right to:

   1. copy it in full;

   2. republish it as that person’s own;

   3. remove authorship designations;

   4. sell it;

   5. create derivative works;

   6. use it for advertising;

   7. distribute Media beyond the scope permitted by law.

3. Use of another person’s Content requires an appropriate legal basis unless the relevant use falls within the limits permitted by law.

§ 165. SHARE Post Type

1. Designating a Post as SHARE does not automatically grant the right to copy or further distribute third-party works.

2. A User using the SHARE type may, in particular:

   1. share the User’s own Content;

   2. post links;

   3. provide information about third-party materials;

   4. quote fragments within the limits of the law;

   5. publish materials to which the User holds appropriate rights or consents.

3. The SHARE type does not remove the obligation to comply with copyright and other intellectual-property rights.

§ 166. Author designation

1. Content published by an active User is, as a rule, presented together with the author designation used in the Portal.

2. The author designation may include, in particular:

   1. the Username;

   2. the display name;

   3. the avatar;

   4. a link to the Profile.

3. Changes to Profile data may result in corresponding changes to the author designation displayed with earlier Content.

4. In the event of final anonymisation of the Account, the author designation may be removed or replaced with a neutral designation.

5. Anonymisation of the Account does not cause the Service Provider to assume authorship of the Content.

§ 167. Accounts of companies, organisations and other entities

1. A person publishing Content from an Account maintained on behalf of a company, organisation, institution, project or other entity is responsible for having appropriate authorisation.

2. The User should be able to grant ReputoNode the licence required to use the Content.

3. If rights to Content belong to an employer, client, organisation, co-author or another entity, before publication the User should ensure that the User has the right to make it available in this manner.

§ 168. Trademarks, logos and designations

1. Without an appropriate basis, the User may not use the following in a manner infringing third-party rights:

   1. trademarks;

   2. logos;

   3. trade names;

   4. company names;

   5. organisation designations;

   6. designs;

   7. other protected designations.

2. Mere presentation of another person’s mark or logo is not automatically prohibited if the manner of use complies with applicable law.

3. In particular, a mark or logo may appear in Content in a justified informational, opinion, comparative, documentary or other lawful context.

4. It is prohibited to use another person’s designation in a manner that may unlawfully suggest:

   1. an official relationship;

   2. authorisation;

   3. sponsorship;

   4. partnership;

   5. that the Content or Account originates from another entity.

5. The rules concerning impersonation of other persons or entities apply independently of this paragraph.

§ 169. Reporting an infringement of intellectual-property rights

1. A person who believes that Content available in ReputoNode infringes that person’s intellectual-property rights may submit a Report to the Service Provider.

2. A Report should, where possible, contain:

   1. contact details for the reporting person;

   2. identification of the right concerned;

   3. a description of the protected work, designation or other subject matter of the right;

   4. a link or other precise identification of the Content located in ReputoNode;

   5. a description of the manner of infringement;

   6. information allowing assessment that the reporting person is entitled to make the Report;

   7. available evidence or information supporting the claim.

3. The Report should be prepared in a manner enabling the Service Provider to identify the Content and assess the alleged infringement.

4. The Service Provider may request additional information where necessary to consider the matter.

§ 170. Action following an infringement report

1. After receiving a credible report, the Service Provider may take appropriate action in relation to the Content.

2. Depending on the circumstances, the Service Provider may, in particular:

   1. leave the Content unchanged;

   2. temporarily restrict its availability;

   3. hide a Medium;

   4. remove a fragment of Content;

   5. remove the entire Post, Comment or Reply;

   6. ask the author for explanations;

   7. request identification of the legal basis for using the material;

   8. take another action provided for in the Terms or applicable law.

3. The Service Provider’s action should be adapted to the nature of the report and the information available.

4. Temporary restriction of Content while a matter is being clarified does not prejudge a final finding of infringement.

§ 171. Verification of the author’s rights

1. In the event of a credible report or reasonable doubt, the Service Provider may ask the author of Content to demonstrate the basis for its use.

2. Depending on the situation, the author may be asked, in particular, to:

   1. identify the source;

   2. identify the author;

   3. indicate the type of licence;

   4. provide consent;

   5. provide an agreement;

   6. demonstrate authorship;

   7. indicate a basis for permitted use;

   8. provide other information relevant to the matter.

3. The Service Provider is not required to request a document in every matter where the circumstances can be established reliably in another way.

4. The scope of information requested should be appropriate to the nature and complexity of the matter.

§ 172. No explanation from the author

1. If the author does not respond to a justified request from the Service Provider to explain the basis for using Content, the Service Provider may keep the Content hidden or removed.

2. Such action may be taken, in particular, where:

   1. the infringement report is credible;

   2. available information indicates a probable infringement;

   3. the author has not provided any basis for use;

   4. continued availability could increase the scale of infringement.

3. Later submission of credible explanations may be taken into account in a renewed assessment of the matter.

§ 173. False and abusive reports

1. Knowingly submitting false reports of intellectual-property infringement is prohibited.

2. It is prohibited, in particular, to:

   1. report Content in relation to which the reporting person knowingly does not hold the rights claimed;

   2. submit false documents;

   3. deliberately provide false information;

   4. use the reporting procedure to silence criticism;

   5. submit reports to harass the author;

   6. submit manifestly unfounded reports on a mass scale.

3. Deliberate abuse of the reporting procedure may result in measures provided for in the Terms.

4. The mere fact that a report is ultimately not upheld does not mean that it was false or abusive.

§ 174. Content generated by artificial intelligence

1. A User publishing Content generated or materially modified using artificial intelligence is responsible for ensuring that it may be used lawfully.

2. ReputoNode does not guarantee that Content generated by an artificial-intelligence tool:

   1. is protected by copyright;

   2. may be subject to the User’s exclusive rights;

   3. does not infringe third-party rights;

   4. may be used commercially;

   5. was generated in accordance with the terms of the provider of the relevant tool.

3. The User should independently check the terms of use of the AI tool and the rights to input and output materials.

4. If AI Content uses or reproduces protected elements belonging to another person, the User is responsible for the lawfulness of publication.

5. A licence to ReputoNode for AI-generated Content is granted only to the extent that the User can effectively grant such an authorisation.

§ 175. Technical providers and limited downstream rights

1. In order to provide ReputoNode services, the Service Provider may use services of technical entities, in particular providers of:

   1. server infrastructure;

   2. hosting;

   3. backups;

   4. content-delivery networks;

   5. translation;

   6. security;

   7. other technical services necessary for operation of the Portal.

2. The User authorises the Service Provider to enable such entities to use Content only to the extent necessary to perform services entrusted to them.

3. The authorisation referred to in section 2 may not be used to grant third parties the right to independently commercially exploit User Content outside the scope necessary to provide services to ReputoNode.

4. Use of external entities does not transfer the User’s copyright to them.

5. The rules governing personal-data processing by technical service providers are set out in the Privacy Policy.

§ 176. Rights to ReputoNode elements

1. Rights to elements of the Portal that have not been published by Users or other third parties belong to the Service Provider or the relevant entitled entities to the extent arising from applicable law.

2. Protection may include, in particular:

   1. the ReputoNode name;

   2. the logo, graphic designations and visual identity;

   3. the layout and organisation of the Portal interface to the extent that they have an individual and creative character;

   4. graphic elements, iconography, composition and manner of presenting functions;

   5. source code and object code of the software;

   6. system texts, descriptions, messages, documentation and information materials;

   7. database structure and databases to the extent covered by legal protection;

   8. distinctive designations and terminology used in the Portal;

   9. the manner of compiling, presenting and organising Portal elements where it meets statutory requirements for protection;

   10. other ReputoNode elements protected by copyright, industrial-property law, database-protection law, unfair-competition law or other applicable provisions.

3. Distinctive organisational and functional elements of ReputoNode include, in particular:

   1. the system of Post Types designated as: a) MAKES, b) SHARE, c) KNOW_HOW, d) VOICE;

   2. the method of assigning Posts to Thematic Categories;

   3. the structure and set of Categories used in the Portal;

   4. the Topic Reputation system;

   5. the manner of presenting Reputation in individual Categories;

   6. the connection between Reactions and Topic Reputation;

   7. the manner of organising Posts, Comments, Replies, Profiles and User activity;

   8. the visual and functional arrangement of the above elements.

4. Section 3 does not mean that the Service Provider holds an exclusive right to ideas, methods of operation, rules, functions, thematic categories or the concept of a social networking service as such where those elements are not protected under applicable law.

5. Protection applies, however, to the specific manner of expression, development, compilation, presentation, terminology or technical implementation of ReputoNode elements to the extent that it meets statutory requirements for legal protection.

6. Use of the Portal does not transfer to the User any rights to ReputoNode elements beyond the right to use them to the extent necessary for normal use of the Portal in accordance with the Terms.

7. Without an appropriate legal basis or the Service Provider’s consent, it is prohibited, in particular, to:

   1. copy Portal code;

   2. copy protected texts, graphics, documentation and materials;

   3. copy or reproduce ReputoNode’s visual identity in a manner infringing the Service Provider’s rights;

   4. copy a protected layout, compilation or manner of presenting Portal elements;

   5. remove or alter copyright notices or other rights notices;

   6. create a service impersonating ReputoNode;

   7. use the ReputoNode name, logo or other designations in a manner capable of misleading recipients as to affiliation, authorisation, origin or partnership;

   8. mass copy, download or reproduce the contents of Portal databases to an extent infringing the Service Provider’s rights;

   9. use protected ReputoNode elements to create an imitation of the Portal where such use infringes intellectual-property rights, database rights, rights to designations or unfair-competition provisions.

8. Merely creating another service using a similar general idea, function or operating model does not constitute a breach of this paragraph where no specific rights of the Service Provider or other entitled entities are infringed.

9. The Service Provider may seek protection of its rights, in particular in cases of unlawful copying of protected ReputoNode elements, impersonation of the Portal, unlawful use of its designations, copying of protected databases or other actions infringing intellectual-property rights or fair-competition rules.

Chapter 12

R+ and R− Reactions and Topic Reputation

§ 177. Nature of Reactions

1. ReputoNode enables Users to evaluate Content by means of Reactions:

   1. R+ — meaning a positive evaluation of Content;

   2. R− — meaning a negative evaluation of Content.

2. A Reaction is submitted directly in relation to specific Content.

3. A Reaction may be submitted in relation to:

   1. a Post;

   2. a Comment;

   3. a Reply.

4. A Reaction concerns the evaluation of the Content to which it was submitted.

5. The effect of a Reaction on Reputation is attributed to the author of the evaluated Content in the Category of the Post with which that Content is associated.

6. In the case of:

   1. a Reaction to a Post — the effect concerns the Reputation of the Post author in the Category of that Post;

   2. a Reaction to a Comment — the effect concerns the Reputation of the Comment author in the Category of the Post under which the Comment was published;

   3. a Reaction to a Reply — the effect concerns the Reputation of the Reply author in the Category of the Post under which the relevant discussion is taking place.

7. A Comment or Reply does not have its own independent Category for Reputation purposes.

8. A Reaction does not constitute an official evaluation by the Service Provider or confirmation of the truthfulness, legality or quality of Content.

§ 178. Conditions for submitting a Reaction

1. A Reaction may be submitted only by a logged-in User who has an active Account and access to the Reaction function.

2. A User may submit only one Reaction in relation to given Content.

3. A User may not submit a Reaction in relation to:

   1. their own Post;

   2. their own Comment;

   3. their own Reply.

4. Circumventing the prohibition referred to in paragraph 3 is prohibited, in particular by using an additional Account or another person's Account.

5. An Account that is in the waiting period for deletion may not submit new Reactions.

§ 179. Irreversibility of Reactions

1. Once a Reaction has been correctly recorded, the User may not independently:

   1. delete it;

   2. withdraw it;

   3. change it from R+ to R−;

   4. change it from R− to R+.

2. Before submitting a Reaction, the User should make sure that it reflects their actual evaluation of the Content.

3. The Portal may visually mark a Reaction submitted by a logged-in User, in particular by changing the appearance of the relevant button.

4. The marking referred to in paragraph 3 is visible to the User who submitted the Reaction and serves to indicate that the relevant Content has already been evaluated by that User.

5. The inability to independently change a Reaction does not exclude the possibility of reporting a technical error to the Service Provider.

§ 180. Meaning of R+ and R− Reactions

1. R+ means a positive evaluation of specific Content.

2. R− means a negative evaluation of specific Content.

3. R− may be submitted for any reason resulting from the User's evaluation, in particular where the User considers the Content to be:

   1. of little value;

   2. incorrect;

   3. not useful;

   4. poorly substantiated;

   5. unreliable;

   6. inappropriate for the Category;

   7. inconsistent with the User's substantive assessment.

4. The User is not required to justify a Reaction they have submitted.

5. R− is not a Report of a violation.

6. If a User considers that Content violates the law, the Terms or the Community Standards, the User should use the appropriate Reporting procedure regardless of whether they also submit an R−.

7. R+ does not mean that the User confirms the truthfulness of all information contained in the Content.

§ 181. Effect of Reactions on Topic Reputation

1. Reactions affect the Topic Reputation of the author of the evaluated Content.

2. As a rule, R+ increases the Reputation of the author of the evaluated Content in the relevant Category.

3. As a rule, R− decreases the Reputation of the author of the evaluated Content in the relevant Category.

4. The relevant Category is always the Category of the parent Post.

5. If a Reaction concerns a Comment or Reply, its effect on Reputation is not attributed to a separate comment category but to the Category of the Post under which the relevant discussion appears.

6. Merely publishing a Post, Comment or Reply does not automatically increase Reputation.

7. Reputation is built primarily on the basis of Reactions received by the author's Content.

8. The number of Content items published does not in itself guarantee higher Reputation.

§ 182. Topic Reputation

1. Reputation is determined separately for each Category.

2. A User may have different Reputation in different Categories.

3. High Reputation in one Category does not automatically result in high Reputation in other Categories.

4. ReputoNode does not calculate one public overall User rating covering all Categories.

5. Reputation is intended to reflect, in particular, how the User's Content is evaluated by other Users within a specific thematic area.

6. Reputation is the result of the Portal system and does not constitute a proprietary right of the User.

§ 183. Reaction weight

1. The effect of a Reaction on Reputation may depend on the Topic Reputation of the person submitting the Reaction in the same Category.

2. A Reaction submitted by a person with higher Reputation in a given Category may have a greater effect on the Reputation of the author of the evaluated Content than a Reaction submitted by a person with lower Reputation in that Category.

3. A Reaction submitted by a User whose Reputation in a given Category is 0.00 also affects the Reputation system.

4. The weight of a Reaction submitted by a person with low or zero Reputation may be lower than the weight of a Reaction submitted by a person with higher Reputation.

5. Having no Reputation in a given Category does not deprive the User of the right to evaluate Content.

6. The exact Reaction weight values do not form part of the Terms.

§ 184. Significance of Post Type

1. Post Type may affect the strength of a Reaction's effect on Reputation.

2. As a rule, Reactions concerning Content associated with KNOW_HOW Posts have the greatest effect on Reputation.

3. Next in terms of impact are, in order:

   1. MAKES;

   2. VOICE;

   3. SHARE.

4. The exact multipliers assigned to individual Post Types do not form part of the Terms.

5. The Service Provider may change the multiplier values and the manner in which they are applied as part of the development of the Reputation system.

6. A change in the multipliers does not change the meaning of individual Post Types defined in the Terms.

§ 185. Reputation algorithm

1. Topic Reputation is calculated automatically by the ReputoNode system.

2. The calculation of Reputation may take into account, in particular:

   1. the type of Reaction;

   2. the Topic Reputation of the person submitting the Reaction;

   3. the Post Category;

   4. the Post Type;

   5. the type of evaluated Content;

   6. previous events affecting Reputation;

   7. corrections related to Moderation;

   8. mechanisms counteracting manipulation of Reputation;

   9. other technical parameters of the system.

3. The exact mathematical formula, values of weights, multipliers and other algorithm parameters do not form part of the Terms.

4. The Service Provider may develop, change and adjust the Reputation algorithm.

5. Changes may be introduced in particular in order to:

   1. improve the quality of the system's operation;

   2. increase resistance to manipulation;

   3. limit abuse;

   4. improve the way in which the substantive value of Content is reflected;

   5. improve the stability of results;

   6. remove errors;

   7. adapt the system to the development of the Portal.

6. A change to the algorithm may result in recalculation of existing results.

7. Recalculation may also apply to Reactions submitted before the change was introduced.

8. The Service Provider does not guarantee preservation of the previous Reputation value following a change to the algorithm.

§ 186. Internal Reputation value

1. The system may store an internal Reputation value that differs from the result presented publicly.

2. The internal Reputation value may be positive or zero and may not be lower than 0. An R− Reaction may reduce this value to 0, but not below 0.

3. The internal value may be used in particular for:

   1. calculating the public score;

   2. determining Reaction weight;

   3. making corrections;

   4. recalculating results;

   5. protecting the system against manipulation.

4. The internal Reputation value is not publicly displayed.

5. The User does not have the right to demand display of the raw technical value merely because it relates to their Account.

§ 187. Public Reputation score

1. Public Topic Reputation is presented on a scale from 0.00 to 10.00.

2. The score is presented separately for individual Categories.

3. The public score may not be lower than 0.00 or higher than 10.00.

4. A User may also have a score of 0.00 even if they publish Content in a given Category.

5. The mere fact of publishing Content does not result in the award of a minimum positive Reputation.

6. The public score is a transformation of data used internally by the system and does not directly represent raw Reputation points.

188. Logarithmic and dynamic nature of Reputation

1. The public Reputation score is calculated on the basis of a non-negative internal Reputation value using a logarithmic transformation or another mechanism specified by the Portal's current algorithm.

2. The public Reputation score does not currently depend directly on the scores of other Users and does not change solely because another person's Reputation has changed.

3. A User's public Reputation may change in particular as a result of:

   1. receiving a new Reaction;

   2. correction of an error;

   3. invalidation of a Reaction;

   4. Moderation;

   5. a change to the algorithm;

   6. recalculation of the score.

4. The highest-rated User in a Category does not have to have a score of exactly 10.00.

5. Several Users may have the same Reputation score.

6. Reputation is a dynamic score and may change over time.

§ 189. Scope of publicly displayed information

1. The Topic Reputation score is displayed publicly to the extent made available by the Portal.

2. ReputoNode does not publicly display:

   1. the raw number of Reputation points;

   2. the number of R+ Reactions received;

   3. the number of R− Reactions received;

   4. the number of Reactions taken into account for a given score;

   5. detailed Reputation history;

   6. the effect of an individual Reaction on the score;

   7. the exact algorithm formula;

   8. the individual weights of particular Reactions.

3. The Content author does not receive additional information concerning Reactions received solely because they are the owner of the evaluated Content.

4. In principle, the author sees the same public information about their Reputation that is available to other persons.

§ 190. No public information about the author of a Reaction

1. The Content author does not see which User submitted a specific R+ or R− Reaction.

2. Other Users and Visitors also do not see public information about the author of a specific Reaction.

3. Information about who submitted a Reaction may be stored by the system to the extent necessary for:

   1. correct operation of Reactions;

   2. preventing multiple voting;

   3. calculating Reputation;

   4. counteracting manipulation;

   5. Moderation;

   6. security;

   7. compliance with legal obligations.

4. A Reaction is therefore not anonymous to the ReputoNode system, even if its author is not disclosed publicly.

§ 191. Reactions to a deleted Post

1. Deletion of a Post by its author does not currently automatically reverse the effect of Reactions previously submitted in relation to that Post.

2. The effect of such Reactions may continue to be taken into account in the author's Reputation.

3. Once a Post has been deleted, no new Reactions may be submitted in relation to the deleted Post itself.

4. Reactions may continue to be submitted in relation to Comments and Replies remaining under the deleted Post in accordance with the Terms.

5. The Service Provider may in the future change the way Reactions to deleted Posts are treated.

6. A change may include in particular:

   1. retaining the previous effect;

   2. partial reversal of the effect;

   3. complete reversal of the effect;

   4. recalculation of Reputation.

7. A change may also be applied to Reactions submitted previously where this is necessary to maintain consistency of the system.

§ 192. Content removed or restricted as a result of Moderation

1. If a Post, Comment or Reply is removed, hidden or restricted as a result of Moderation, the effect of Reactions associated with it may:

   1. remain in place;

   2. be partially reversed;

   3. be completely reversed;

   4. be recalculated.

2. The manner in which Reactions are treated may depend in particular on:

   1. the reason for Moderation;

   2. the nature of the violation;

   3. the Content's effect on Reputation;

   4. identified manipulation;

   5. a technical error;

   6. the need to maintain consistency of the system.

3. A correction may be made manually or automatically.

4. The Service Provider is not required to treat all types of Moderation identically for Reputation purposes.

§ 193. Reactions submitted by an Account that is later deleted

1. Final deletion of a User's Account does not automatically withdraw Reactions previously submitted by that Account.

2. Such Reactions may continue to affect the Reputation of other Users.

3. The Service Provider may, however, invalidate or recalculate such Reactions where there is a justified reason.

4. This applies in particular where:

   1. the Account was created for the purpose of manipulating Reputation;

   2. the Reactions formed part of organised abuse;

   3. automated voting was detected;

   4. a technical error occurred;

   5. the Reputation algorithm changed;

   6. invalidation is necessary to maintain the integrity of the system.

§ 194. Deletion of the Account of the author of evaluated Content

1. Final deletion of the Account of the Content author does not require reversal of the previous effect of Reactions merely because the Account is anonymised.

2. Content remaining after Account deletion may continue to be associated with historical Reputation events to the extent technically necessary.

3. The Reputation of the deleted Account is no longer presented as that person's current public Reputation.

4. Deletion of an Account does not automatically result in recalculation of the Reputation of other Users.

§ 195. Prohibition on manipulating Reputation

1. It is prohibited to take actions aimed at artificially increasing or decreasing one's own Reputation or the Reputation of other Users.

2. In particular, it is prohibited to:

   1. agree to mutually submit R+ Reactions;

   2. organise group submission of R− Reactions against a specific User;

   3. create additional Accounts for the purpose of submitting Reactions;

   4. use other persons' Accounts for voting;

   5. buy Reactions;

   6. sell Reactions;

   7. offer money in exchange for a specified Reaction;

   8. offer products, services, discounts or other benefits in exchange for a specified Reaction;

   9. vote automatically;

   10. use bots, scripts or other tools to submit Reactions;

   11. organise mass voting intended to artificially increase or decrease a score;

   12. agree to exchange R+ Reactions;

   13. exert pressure on other Users in order to obtain a specified Reaction;

   14. take other actions intended to circumvent the rules of the Reputation system.

3. The prohibition covers both actions intended to increase one's own Reputation and actions intended to unjustifiably lower the Reputation of another User.

§ 196. Request to evaluate Content

1. A User may ask other persons to review and evaluate their Content.

2. Such a request is permitted if it:

   1. is not connected with offering a benefit;

   2. does not require submission of a particular Reaction;

   3. does not form part of an agreement for reciprocal voting;

   4. is not intended as organised manipulation of the system.

3. In particular, a User may ask others for an honest evaluation of a Post without indicating whether they should submit R+ or R−.

§ 197. Measures against manipulation

1. If the Service Provider identifies or reasonably suspects manipulation of Reputation, it may take measures necessary to protect the integrity of the system.

2. In particular, the Service Provider may:

   1. analyse Reaction history;

   2. invalidate individual Reactions;

   3. invalidate a group of Reactions;

   4. invalidate all Reactions of a specified Account;

   5. recalculate Reputation;

   6. manually correct a score resulting from abuse;

   7. restrict the ability to submit new Reactions;

   8. temporarily restrict an Account;

   9. block an Account;

   10. apply other measures provided for in the Terms.

3. When assessing abuse, the Service Provider may take into account in particular:

   1. the number of Reactions;

   2. voting frequency;

   3. links between Accounts;

   4. repetition of patterns;

   5. the timing of Reactions;

   6. the effect on Reputation;

   7. previous violations;

   8. other available information indicating manipulation.

4. A correction may be made manually or automatically.

§ 198. No automatic Moderation based on the number of Reactions

1. A large number of R− Reactions does not currently automatically result in:

   1. removal of Content;

   2. hiding of Content;

   3. blocking the author;

   4. initiation of an automatic sanction.

2. R− remains an evaluation of Content and does not replace a Report.

3. A large number of R+ Reactions does not currently automatically grant Content a special status or guarantee increased visibility.

4. ReputoNode may in the future use Reactions for additional functions related to presenting, ordering or recommending Content.

§ 199. Use of Reputation within the Portal

1. Reputation may affect the operation of selected Portal functions.

2. Reputation may be used in particular for:

   1. displaying a User's score in individual Categories;

   2. indicating the best Category on a Profile;

   3. filtering Content according to the author's Reputation;

   4. sorting Content according to the author's Reputation;

   5. ordering Comments;

   6. determining Reaction weight;

   7. other functions related to substantive evaluation of Content.

3. Not all functions listed in paragraph 2 have to be available at the same time.

4. The Service Provider may develop the manner in which Reputation is used as the Portal develops.

5. Reputation does not guarantee a specific position of Content in the feed or search results.

§ 200. Reputation and User qualifications

1. Topic Reputation does not constitute formal confirmation of:

   1. education;

   2. professional qualifications;

   3. professional experience;

   4. professional authorisations;

   5. a licence;

   6. a certificate;

   7. membership in a professional organisation;

   8. expert status granted by a public or professional authority.

2. High Reputation means only the result produced by the ReputoNode system in a given Category.

3. A person using Content should independently assess whether the author has the qualifications required in the relevant field.

4. Reputation should not be treated as the sole criterion when making decisions concerning health, law, finances, safety or other important matters.

§ 201. Changes to the Reputation system

1. The Service Provider may change:

   1. the Reputation algorithm;

   2. Reaction weights;

   3. Post Type multipliers;

   4. the method of normalising scores;

   5. the manner in which the score is displayed;

   6. mechanisms preventing manipulation;

   7. the manner in which deleted or moderated Content is taken into account;

   8. other technical parameters of the system.

2. A change to the system may result in a change to existing scores.

3. The Service Provider may recalculate all or part of Reputation after introducing a change.

4. The User does not acquire the right to retain any particular previous Reputation value.

5. Changes may not be used to arbitrarily assign a particular person a score unrelated to the operation of the system, except for justified corrections resulting from an error, Moderation or abuse.

§ 202. Error corrections

1. Where a technical error is identified, the Service Provider may correct Reputation or Reactions.

2. A correction may include in particular:

   1. recalculation of the score;

   2. removal of an incorrectly recorded Reaction;

   3. taking a valid Reaction into account again;

   4. changing the Category in which the effect of a Reaction was taken into account;

   5. remedying the effects of incorrect operation of the algorithm.

3. A correction may be made manually or automatically.

4. Correcting an error does not constitute an infringement of the User's right to retain a previous Reputation value.

§ 203. Reporting Reputation errors

1. A User may report to the Service Provider a suspected error concerning:

   1. a Reaction;

   2. Reputation;

   3. assignment of a Reaction's effect to an incorrect Category;

   4. incorrect calculation of a score;

   5. another technical problem concerning the Reputation system.

2. A report may be sent to the Service Provider's email address.

3. Where possible, the report should contain:

   1. the username;

   2. identification of the Content;

   3. a description of the problem identified;

   4. information facilitating its reproduction.

4. The Service Provider may examine the report and make an appropriate correction if it identifies an error.

5. The mere fact that a User disagrees with the level of their Reputation does not mean that there is an error in the system.

6. The Service Provider does not guarantee a change to the score solely because the User is dissatisfied with its value.

§ 204. No right to a specific score

1. The User is not guaranteed:

   1. to obtain a specific Reputation;

   2. to retain a specific Reputation;

   3. to achieve a score higher than another User;

   4. to retain their current position in a given Category;

   5. to obtain a specific influence of their Reactions.

2. Reputation may increase or decrease as a result of operation of the system described in the Terms.

3. A Reputation score does not constitute an obligation of the Service Provider to provide the User with specific visibility or positioning within the Portal.

§ 205. Reputation is assigned to an Account

1. Topic Reputation is assigned to a specific User Account.

2. Reputation may not be:

   1. sold;

   2. gifted;

   3. transferred;

   4. combined with the Reputation of another Account;

   5. exchanged between Accounts.

3. The prohibition also applies where several Accounts belong or belonged to the same person.

4. Creating a new Account does not transfer Reputation from a previous Account.

5. The Service Provider is not required to combine Reputation scores between Accounts.

Chapter 13

Moderation, reporting violations and actions of the Service Provider

§ 206. Moderation rules

1. Content published on ReputoNode is subject to Moderation in accordance with the rules set out in the Terms and the Community Standards.

2. Moderation serves in particular to:

   1. respond to Illegal Content;

   2. enforce the Terms and the Community Standards;

   3. protect the rights of Users and other persons;

   4. protect the security of the Portal;

   5. counteract fraud, impersonation, spam and other abuse;

   6. ensure correct operation of the Reputation system;

   7. comply with obligations arising from applicable law.

3. Moderation is currently carried out manually by the Service Provider or a person authorised by the Service Provider.

4. ReputoNode does not currently use a mechanism for automatically removing Content solely on the basis of the number of R+ or R− Reactions.

5. The Service Provider may in the future use tools supporting Moderation, provided that applicable law and the rules set out in the Terms are complied with.

§ 207. Initiating Moderation without a Report

1. The Service Provider may initiate Moderation:

   1. after receiving a Report;

   2. after independently noticing a possible violation;

   3. after receiving information from a third party;

   4. after receiving information from a competent authority;

   5. as a result of detecting a technical problem or security threat;

   6. in other cases requiring action in accordance with the law or the Terms.

2. Initiating Moderation does not require a prior Report by a User.

3. The Service Provider is not required to continuously and manually monitor all Content published on the Portal.

§ 208. Persons entitled to submit a Report

1. A Report may be submitted by any person or entity, regardless of whether they have an Account on ReputoNode.

2. Reports may be submitted in particular by:

   1. Users;

   2. Visitors;

   3. persons whose rights may be infringed;

   4. rights holders;

   5. representatives of persons or entities;

   6. organisations;

   7. public bodies.

3. Having an Account is not a condition for a Report to be considered.

§ 209. Reporting channel

1. Reports may be submitted electronically to legal@reputonode.com.

2. ReputoNode also provides an easily accessible “Report” mechanism next to Posts, Comments and Replies. This mechanism is used to report specific Content available on the Portal.

3. Matters concerning an entire Account, Profile, avatar, username, User behaviour or another element for which the Portal does not provide a direct “Report” button may be reported to the address indicated in paragraph 1.

4. The mechanism for reporting Illegal Content is also available to persons who do not have an Account and enables the information required by applicable law to be provided.

5. The reporting mechanism should be user-friendly and enable a sufficiently precise and adequately substantiated Report to be submitted electronically.

6. The email address indicated in paragraph 1 may also be used for other contact with the Service Provider, unless the Portal indicates a separate channel for a specific type of matter.

7. The Service Provider may make additional electronic Reporting channels available.

§ 210. Subject matter of a Report

1. A Report may concern in particular:

   1. a Post;

   2. a Comment;

   3. a Reply;

   4. an Account;

   5. a Profile;

   6. an avatar;

   7. a username;

   8. a display name;

   9. a bio;

   10. contact details;

   11. a link;

   12. a photograph;

   13. a video;

   14. another Medium;

   15. a User's conduct;

   16. another element available on ReputoNode.

2. An entire Account may be reported, in particular where there is suspicion of:

   1. impersonation;

   2. spam;

   3. repeated violations of the rules;

   4. fraud;

   5. manipulation of Reputation;

   6. other repeated abuse.

§ 211. One matter per Report

1. One Report should concern one coherent problem, event, Account or chain of violations.

2. Multiple Content elements may be indicated in one Report if they concern the same problem.

3. In particular, a Report concerning impersonation by one User may simultaneously indicate:

   1. use of another person's photograph as an avatar;

   2. use of a person's first and last name as the display name;

   3. publication of Posts using another person's image;

   4. other elements forming part of the same case of impersonation.

4. Independent violations concerning other Users or other unrelated matters should be reported separately.

5. The Service Provider may split one Report into several matters if this is necessary for their proper consideration.

§ 212. Content of a Report

1. A Report should be sufficiently precise to enable the problem to be identified and assessed.

2. Where possible, a Report should contain:

   1. an exact link to the reported Content, Profile or other element;

   2. an indication of what the Report concerns;

   3. a description of the alleged violation;

   4. justification;

   5. identification of the relevant fragments or elements;

   6. available evidence;

   7. other information that may assist in assessing the matter;

   8. the reporter's contact details where required or where the reporter wishes to receive information about the matter.

3. The Service Provider may ask the reporter for additional information necessary to consider the matter.

4. The absence of all information does not automatically result in rejection of a Report if the available data is sufficient to assess it.

§ 213. Reports of Illegal Content

1. In the case of a Report concerning Content which the reporter considers illegal, the Reporting mechanism enables the information required by applicable law to be provided.

2. Such a Report should make it possible to provide in particular:

   1. an adequately substantiated explanation of the reasons why the reporter considers the specified information to constitute Illegal Content;

   2. the exact electronic location of the Content, in particular the exact URL or URLs;

   3. where necessary, other information enabling the Content to be identified;

   4. the first and last name or name of the reporter;

   5. the reporter's email address;

   6. a statement confirming that the reporter acts in good faith and believes that the information and allegations contained in the Report are correct and complete.

3. In cases where applicable law permits a Report without providing the data referred to in paragraph 2 points 4 and 5, such data is not required.

4. ReputoNode does not make the ability to report Illegal Content conditional on having an Account.

§ 214. Anonymous Reports

1. An ordinary Report concerning a possible violation of the Terms or the Community Standards may be submitted anonymously, unless provisions applicable to the particular type of Report require specific data to be provided.

2. The Service Provider may consider an anonymous Report if it contains information sufficient to assess the matter.

3. The Service Provider may leave a Report without further consideration if:

   1. it does not contain information enabling the problem to be identified;

   2. it is not possible to obtain necessary supplementary information from the reporter;

   3. the absence of contact makes a reliable assessment of the allegations impossible;

   4. the Report is manifestly unfounded;

   5. the Report is incomprehensible;

   6. there is a justified suspicion of abuse of the procedure.

4. The absence of contact details may make it impossible to provide the reporter with information about acceptance, progress or outcome of the matter.

§ 215. Confirmation of receipt of a Report of Illegal Content

1. If a Report of Illegal Content submitted using the mechanism referred to in § 213 contains the reporter's electronic contact details, the Service Provider sends confirmation of its receipt without undue delay.

2. The confirmation may be sent automatically or manually.

3. Confirmation of receipt does not mean that the Report has been considered well-founded.

§ 216. Manner of considering Reports

1. Reports are considered in a manner appropriate to the nature of the matter.

2. The Service Provider does not guarantee a specific time for considering every Report.

3. Reports should be considered without undue delay, taking into account:

   1. the complexity of the matter;

   2. the availability of required information;

   3. the need to obtain additional explanations;

   4. the nature of the potential violation;

   5. the risk to other persons;

   6. the number of matters currently under consideration;

   7. the organisational capabilities of the Service Provider.

4. The absence of a guaranteed response time does not limit obligations of the Service Provider arising from mandatorily applicable law.

5. Decisions concerning Reports should not be made arbitrarily.

§ 217. Priority matters

1. The Service Provider may give priority to certain Reports due to the nature of the risk.

2. Priority may be given in particular to Reports concerning:

   1. an immediate threat to life or health;

   2. a person's safety;

   3. sexual exploitation of minors;

   4. material depicting child sexual abuse;

   5. serious fraud;

   6. impersonation creating a material threat;

   7. disclosure of particularly dangerous data;

   8. serious cybersecurity threats;

   9. other situations requiring an urgent response.

3. Priority consideration of one Report may result in later consideration of less urgent matters.

§ 218. Possible Moderation measures

1. After analysing the matter, the Service Provider may apply an appropriate Moderation measure.

2. Depending on the circumstances, the measure may include in particular:

   1. taking no action;

   2. issuing a warning;

   3. changing the Post Category;

   4. changing the Post Type;

   5. removing a specified part of Content;

   6. removing personal data or other information requiring removal;

   7. removing a link;

   8. removing a Medium;

   9. hiding Content;

   10. restricting Content visibility;

   11. removing the entire Content;

   12. restricting the ability to publish;

   13. restricting the ability to submit Reactions;

   14. restricting other Account functions;

   15. temporarily blocking an Account;

   16. permanently blocking an Account;

   17. correcting Reputation or Reactions;

   18. preserving relevant information;

   19. other action required by law or necessary to protect the Portal and its Users.

3. A measure may concern an individual element or an entire Account.

§ 219. Proportionality of Moderation

1. A Moderation measure should be appropriate to the nature and circumstances of the matter.

2. When making a decision, the following may be taken into account in particular:

   1. the nature of the violation;

   2. its seriousness;

   3. its scale;

   4. its duration;

   5. repetition;

   6. intentionality;

   7. previous violations;

   8. actual or potential harm;

   9. risk to other persons;

   10. an attempt to circumvent a previous sanction;

   11. the User's response to previous warnings;

   12. the possibility of remedying the violation using a less restrictive measure.

3. A single minor violation may be resolved through a correction or warning without imposing additional restrictions.

4. The Service Provider is not required to issue a warning before every other Moderation measure.

§ 220. Serious violations

1. In the case of a particularly serious violation, the Service Provider may restrict or permanently block an Account without prior warning.

2. This applies in particular where continued access to the Portal:

   1. creates a material threat;

   2. is used for serious fraud;

   3. is used for criminal activity;

   4. involves a serious infringement of the rights of other persons;

   5. is used for systematic manipulation of the Portal;

   6. poses a serious threat to infrastructure;

   7. constitutes an attempt to circumvent a previous permanent sanction;

   8. requires an immediate response for another important reason.

3. A first violation may result in permanent blocking of an Account if its nature is sufficiently serious.

§ 221. Temporary restriction while a matter is being clarified

1. The Service Provider may temporarily hide Content or restrict an Account while a matter is being clarified if there is a justified need to secure the situation before a final decision is made.

2. Temporary action may be taken in particular where:

   1. there is a credible suspicion of a serious violation;

   2. continued availability of Content may cause material harm;

   3. additional documents need to be obtained;

   4. there is a dispute concerning rights to Content;

   5. there is a security threat.

3. A temporary restriction does not automatically constitute a final finding of a violation.

4. After the matter has been clarified, the Service Provider may:

   1. remove the restriction;

   2. restore the Content;

   3. maintain the restriction;

   4. apply another Moderation measure.

§ 222. Unfounded Report

1. The mere receipt of a Report does not establish that a violation has occurred.

2. If, after analysis, no basis for action is found, the Content may remain unchanged.

3. If the Content was previously temporarily restricted, it may be restored.

4. Rejection of a Report does not automatically mean that the reporter acted in bad faith.

§ 223. Informing the author about a Moderation Decision

1. If the Service Provider imposes a restriction on a User because information provided by that User has been considered Illegal Content or information inconsistent with the Terms or the Community Standards, the Service Provider provides the User with a clear and specific statement of reasons, provided that it knows the User's relevant electronic contact details and applicable law does not provide for an exception.

2. The statement of reasons is provided no later than on the day the restriction is imposed and, as appropriate to the circumstances, contains at least:

   1. an indication of the measure applied, in particular removal of Content, disabling access to it, restricting its visibility, restricting specified functions, suspending provision of the service, or temporarily or permanently blocking the Account;
   2. where applicable, the territorial scope of the decision and the period for which it applies;
   3. the facts and circumstances on the basis of which the decision was taken, including information as to whether the decision was taken on the basis of a Report, checks carried out on the Service Provider's own initiative or information originating from a competent authority;
   4. information about the use of automated means to detect Content or make the decision, if such means were used;
   5. if the decision concerns potentially Illegal Content — an indication of the legal basis and an explanation of the reasons for considering the information illegal;
   6. if the decision results from non-compliance with the Terms or the Community Standards — an indication of the relevant contractual basis and an explanation of the reasons for considering the information inconsistent with that basis;
   7. clear information about the available possibilities for challenging the decision.

3. The identity of the person submitting a Report may be disclosed to the User only where this is strictly necessary and lawful.

4. The statement of reasons should be comprehensible and as precise and detailed as may reasonably be expected in the circumstances, in order to enable the User to make effective use of the available means of appeal.

5. In the case of a User who has an Account, the primary channel for providing the statement of reasons is the email address assigned to the Account, unless applicable provisions or the mechanism used provide for another appropriate electronic channel.

§ 224. Exceptions to providing information

1. The obligation to provide a statement of reasons for a Moderation Decision does not apply, or may be fulfilled to a limited extent, only in cases provided for by applicable law.

2. This applies in particular where:

   1. the Service Provider does not know the User's relevant electronic contact details;
   2. the restriction results from a legally binding order to which separate information rules apply;
   3. the information constitutes high-volume misleading commercial content and applicable law excludes the obligation to provide a statement of reasons;
   4. provision of specified information is prohibited by law or by a legally binding decision of a competent authority;
   5. another explicit exception provided for by applicable law applies.

3. If a restriction concerns only part of the information and providing the remaining part of the statement of reasons is legally permissible, the Service Provider provides the statement of reasons to the extent possible.

4. Exceptions are not applied for the purpose of arbitrarily depriving a User of information about Moderation or the ability to effectively challenge a decision.

§ 225. Information for the reporter

1. If the reporter provided electronic contact details as part of a Report of Illegal Content made in accordance with the mechanism provided for by applicable law, the Service Provider informs the reporter without undue delay of the decision concerning the reported information and of the available possibilities of appeal or other legal remedies.

2. In the case of other types of Reports, the Service Provider may inform the reporter of the outcome of the matter, but is not required to provide detailed information unless such an obligation arises from law.

3. The scope of information may be limited due to:

   1. the User's privacy;

   2. personal-data protection;

   3. security;

   4. legally protected confidentiality;

   5. protection of ongoing proceedings;

   6. other legal obligations.

4. The reporter does not acquire the right to obtain complete Moderation documentation or private data of the Content author.

§ 226. Confidentiality of reporter data

1. The data of the person submitting a Report is not normally disclosed to the author of the reported Content.

2. The author may receive information concerning the allegations and circumstances of the matter to the extent necessary to present their position or understand the Moderation Decision.

3. The reporter's data may be disclosed if:

   1. required by law;

   2. requested by a competent authority;

   3. necessary in legal proceedings;

   4. another appropriate legal basis exists.

4. The reporter is not provided with private data of the Content author beyond publicly available information, unless an appropriate legal basis exists.

§ 227. Appeal against a Moderation Decision

1. A User may request that the Service Provider reconsider a Moderation Decision.

2. An appeal may be sent to legal@reputonode.com.

3. An appeal does not require the use of a separate technical system on the Portal.

4. An appeal may concern in particular:

   1. removal of Content;
   2. hiding or restricting Content;
   3. removal of a Medium;
   4. change of Category;
   5. change of Post Type;
   6. restriction of Account functions;
   7. temporary blocking of an Account;
   8. permanent blocking of an Account;
   9. another Moderation Decision directly concerning the User.

5. A person who submitted a Report may request reconsideration of the decision concerning that Report if they have justified grounds for challenging it.

6. The Terms do not specify a fixed time limit for lodging an appeal, subject to time limits arising from mandatorily applicable law.

§ 228. Consideration of appeals

1. An appeal is considered by the Service Provider or a person authorised by the Service Provider.

2. The Service Provider may entrust consideration of specified matters to other appropriately authorised persons.

3. On reconsideration, the following may be taken into account:

   1. the User's arguments;

   2. the original Report;

   3. the Content subject to Moderation;

   4. available evidence;

   5. previous decisions;

   6. additional information obtained after the decision was issued;

   7. applicable law.

4. After consideration of an appeal, the decision may be:

   1. upheld;

   2. changed;

   3. partially reversed;

   4. fully reversed.

5. If the previous decision was incorrect, the Service Provider may in particular:

   1. restore Content;

   2. restore Account functions;

   3. remove a block;

   4. correct Reputation;

   5. make another appropriate correction.

6. The Terms do not establish a guaranteed time for considering an appeal, subject to time limits arising from applicable law.

§ 229. Abuse of the Reporting system

1. Knowingly abusing the Reporting mechanism is prohibited.

2. Abuse may include in particular:

   1. knowingly submitting false Reports;

   2. deliberately providing false information;

   3. mass-reporting compliant Content in order to harass the author;

   4. using Reports to exert pressure;

   5. repeatedly submitting the same manifestly unfounded Report;

   6. automatically sending Reports;

   7. attempting to overload the system or the Service Provider;

   8. using the procedure to conduct a dispute unrelated to an actual violation.

3. The mere fact that a Report is not upheld does not mean that the reporter committed abuse.

4. Establishing abuse requires the circumstances of the matter to be taken into account, in particular the repetitive nature and character of the conduct.

§ 230. Restrictions on persons abusing Reports

1. In the event of repeated or serious abuse, the Service Provider may restrict the ability of a given Account or User to submit Reports.

2. In the case of a person who does not have an Account, the Service Provider may apply technical measures limiting abuse if they are proportionate and lawful.

3. The Service Provider may in particular:

   1. filter obvious spam;

   2. limit automated Reports;

   3. ignore repeated identical Reports;

   4. block technical sources used for mass abuse of the mechanism.

4. These measures should not prevent submission of valid reports of Illegal Content to the extent required by law.

§ 231. Prohibition on circumventing an Account block

1. A User whose Account has been permanently blocked may not create or use another Account in order to circumvent the sanction imposed.

2. The prohibition includes in particular:

   1. creation of a new Account by the same person;

   2. use of another person's Account;

   3. creation of an Account using different details;

   4. use of an organisation's Account to continue activities covered by the block.

3. The Service Provider may block an Account used to circumvent a previous permanent block.

4. The technical ability to detect all cases of circumvention of a block is not guaranteed.

§ 232. Cooperation with competent authorities

1. The Service Provider complies with obligations arising from legally effective orders, decisions and other actions of competent authorities.

2. Where appropriate, the Service Provider may:

   1. preserve specified data;
   2. retain information needed for proceedings;
   3. restrict or remove Content;
   4. restrict an Account;
   5. provide information to the competent authority;
   6. take other actions required by law.

3. Data is provided to authorities only on an appropriate legal basis and to the extent required or permitted by law.

4. If the Service Provider becomes aware of information giving rise to suspicion that a criminal offence threatening the life or safety of a person or persons has been committed, is being committed or is likely to be committed, it promptly informs the competent law-enforcement or judicial authorities and provides the available information in accordance with applicable law.

5. If the Member State of the European Union concerned cannot be identified with sufficient certainty, the Service Provider makes the notification in accordance with the rules laid down by applicable law, in particular to the appropriate authorities in Poland or to Europol.

6. In other cases where commission of a prohibited act is suspected, the Service Provider may or is required to take actions provided for by applicable law.

7. Compliance with a legally binding order of a competent authority does not require that the order be consistent with the Service Provider's previous Moderation assessment.

§ 233. Restoration of Content and correction of an erroneous decision

1. The Service Provider may change a previous Moderation Decision if:

   1. it was made on the basis of incomplete information;

   2. new evidence has emerged;

   3. an error has been identified;

   4. the basis for the restriction has ceased to exist;

   5. applicable law requires it;

   6. another justified reason exists.

2. In particular, the Service Provider may restore previously removed or hidden Content if technically possible.

3. If restoration is not technically possible, the Service Provider is not required to recreate the Content from other sources unless such an obligation arises from law.

4. Correction of an erroneous decision may also include an appropriate correction of Reputation or Reactions.

§ 234. Moderation history

1. The Service Provider may store internal information concerning Moderation to the extent necessary for:

   1. documenting actions taken;

   2. considering appeals;

   3. detecting repeated violations;

   4. counteracting abuse;

   5. protecting security;

   6. complying with legal obligations;

   7. establishing, pursuing or defending claims.

2. Moderation history does not have to be publicly available.

3. The scope and period of processing personal data related to Moderation are specified in the Privacy Policy and applicable law.

§ 235. Development of Reporting and Moderation mechanisms

1. The Service Provider may develop technical Reporting and Moderation mechanisms without changing the basic rules set out in the Terms.

2. In particular, the Portal may introduce:

   1. Report buttons next to Content;

   2. contextual forms;

   3. automatic attachment of the address of the reported Content;

   4. selection of the type of violation;

   5. the ability to add evidence;

   6. a system for confirming receipt of a Report;

   7. a panel showing the history of one's own Reports;

   8. other functions facilitating proper use of the procedure.

3. Introduction of a technical mechanism implementing existing obligations or procedures does not require amendment of the Terms if it does not result in a material change to the User's rights or obligations.

4. Regardless of technical development, ReputoNode provides the mechanisms required by mandatorily applicable law.

Chapter 14

User obligations and prohibited use of the Portal

§ 236. Basic User obligations

1. The User is required to use ReputoNode in accordance with:

   1. applicable law;

   2. the Terms;

   3. the Community Standards;

   4. security rules;

   5. instructions of the Service Provider concerning security or remedying a violation, provided that they are consistent with the Terms.

2. The User may not provide unlawful Content through ReputoNode or use the Portal to carry out activities contrary to law.

3. It is also prohibited to use lawful functions in a manner intended to circumvent the Terms, the Community Standards, Moderation or Portal safeguards.

4. Before publishing Content, the User should independently assess whether they have the right to publish it and whether publication does not violate applicable law or the rights of third parties.

5. ReputoNode does not provide the User with individual legal advice regarding the legality of a planned publication before it is posted.

§ 237. Terms and Community Standards

1. The Terms define the basic and overriding rules for using ReputoNode.

2. The Community Standards elaborate on the rules set out in the Terms and may contain more detailed examples of prohibited Content and conduct.

3. The Community Standards form an integral part of the Terms.

4. In the event of a conflict between the Terms and the Community Standards, the Terms prevail.

5. The catalogue of prohibited conduct and Content set out in the Terms and the Community Standards is not exhaustive.

6. Conduct not expressly listed may be considered prohibited if it:

   1. is contrary to law;

   2. infringes the rights of other persons;

   3. constitutes circumvention of Portal rules;

   4. creates a material security risk;

   5. constitutes abuse of Portal functions;

   6. is manifestly harmful to the Portal or its Users.

§ 238. Violence, threats and incitement to crime

1. It is prohibited to publish Content:

   1. inciting violence against a specific person or group of persons;

   2. containing unlawful threats;

   3. encouraging the commission of a criminal offence;

   4. praising the commission of a serious criminal offence in a manner capable of encouraging others to act similarly;

   5. used to organise or facilitate criminal activity.

2. It is prohibited to use ReputoNode to plan, coordinate or commission violence or other criminal offences.

3. Assessment of Content may take its context into account, in particular educational, documentary, historical, scientific, artistic or informational context.

4. Merely invoking such context does not make Content permissible if, in the circumstances, it remains unlawful.

§ 239. Harassment and intimidation

1. It is prohibited to use the Portal for:

   1. harassment;

   2. persistent stalking;

   3. intimidation;

   4. making threats;

   5. organised targeting of a specified person;

   6. encouraging other persons to harass or intimidate.

2. Criticism, debate, a negative opinion or a dispute do not in themselves constitute harassment if they remain within the limits of law and Portal rules.

3. When assessing conduct, its frequency, intensity, context, purpose and effect on the person concerned may be taken into account in particular.

§ 240. Hatred and discrimination

1. It is prohibited to publish Content inciting hatred, violence or unlawful discrimination against a person or group of persons on grounds including in particular:

   1. race;

   2. skin colour;

   3. national or ethnic origin;

   4. nationality;

   5. religion or lack of religious belief;

   6. sex;

   7. sexual orientation;

   8. disability;

   9. other legally protected characteristics.

2. It is prohibited to dehumanise persons or groups and to portray them as requiring physical elimination, violence or persecution because of the characteristics referred to in paragraph 1.

3. Lawful criticism of views, conduct, ideologies, organisations, political parties, institutions and other social phenomena remains permitted.

§ 241. Religion and beliefs

1. Criticism is permitted of:

   1. religions;

   2. religious doctrines;

   3. beliefs;

   4. religious institutions;

   5. activities of clergy;

   6. religious practices and customs.

2. Criticism may be forceful, polemical, satirical or negative if it remains lawful and consistent with the other Portal rules.

3. In particular, the following unlawful conduct is prohibited:

   1. threats;

   2. incitement to violence;

   3. harassment of persons on grounds of religion;

   4. incitement to hatred;

   5. conduct consisting in publicly insulting an object of religious worship or a place intended for the public performance of religious rites where the elements of a prohibited act are met.

4. The mere fact that a statement is offensive, controversial or contrary to another person's beliefs does not automatically establish a violation of the Terms.

§ 242. Terrorism and extremist activity

1. It is prohibited to use ReputoNode to support terrorist activity.

2. In particular, it is prohibited to:

   1. incite the commission of a terrorist act;

   2. organise terrorist activity;

   3. recruit for a terrorist organisation;

   4. raise funds for terrorist activity;

   5. publish material intended directly to facilitate the commission of a terrorist act;

   6. promote terrorist organisations in a manner intended to support them or recruit for them.

3. Content concerning terrorism may be permitted where published for purposes that are:

   1. informational;

   2. journalistic;

   3. historical;

   4. research-related;

   5. educational;

   6. critical;

   7. documentary,

4. provided that its actual purpose is not to support terrorist activity.

§ 243. Instructions concerning criminal offences

1. It is prohibited to publish instructions whose actual purpose is to enable or materially facilitate the commission of a serious criminal offence.

2. The prohibition may include in particular instructions concerning:

   1. committing fraud;

   2. theft;

   3. burglary;

   4. bypassing safeguards in order to obtain unauthorised access;

   5. manufacturing explosives for the purpose of causing harm;

   6. concealing or laundering proceeds of crime;

   7. other serious unlawful activities.

3. The prohibition does not automatically cover materials that are:

   1. educational;

   2. scientific;

   3. historical;

   4. journalistic;

   5. related to cybersecurity;

   6. warning about criminal methods,

4. if their nature and context do not indicate actual facilitation of crime.

§ 244. Protection of minors against sexual exploitation

1. ReputoNode applies an absolute prohibition on Content depicting the sexual exploitation of minors.

2. In particular, it is prohibited to:

   1. publish, transmit or distribute such material;

   2. provide links leading to such material;

   3. search for such material using Portal functions;

   4. sexualise minors;

   5. encourage other persons to sexually exploit minors;

   6. offer or request such material.

3. It is prohibited to use the Portal for grooming or other activities aimed at the sexual exploitation of a minor.

4. In particular, it is prohibited to:

   1. induce a minor to engage in sexual activity;

   2. induce a minor to send nude or sexual material;

   3. arrange a meeting for a sexual purpose;

   4. make sexual propositions to a minor for the purpose of exploiting them.

5. The prohibitions set out in this paragraph apply irrespective of the fact that opening an Account on ReputoNode is intended exclusively for adults.

§ 245. Pornography and sexual services

1. Publishing pornography on ReputoNode is prohibited.

2. It is also prohibited to:

   1. publish links leading directly to pornographic material;

   2. promote paid sexual services;

   3. offer sexual services;

   4. seek clients for such services;

   5. act as an intermediary in providing such services;

   6. use the Portal primarily to direct recipients to pornographic content.

3. Rules concerning permitted material containing nudity in a medical, scientific, educational, artistic, historical or similar context are also set out in other provisions of the Terms and the Community Standards.

§ 246. Intimate Content without consent

1. It is prohibited to publish or distribute intimate photographs, videos or other material concerning a person without an appropriate legal basis or the required consent of that person.

2. The prohibition also covers material:

   1. originally obtained with consent where that consent did not cover further distribution;

   2. obtained unlawfully;

   3. manipulated;

   4. generated using artificial intelligence;

   5. constituting a deepfake;

   6. credibly depicting a person in a sexual or intimate situation that did not in fact occur.

§ 247. Suicide and self-harm

1. It is prohibited to use ReputoNode to encourage a specific person to commit suicide or self-harm.

2. Content may also be prohibited where its principal purpose is to:

   1. promote suicide;

   2. encourage self-harm;

   3. pressure a person to harm themselves;

   4. present suicide as an action the recipient should pursue.

3. Lawful Content concerning the following is permitted in particular:

   1. mental health;

   2. personal experiences;

   3. prevention;

   4. seeking help;

   5. supporting other persons;

   6. education and research,

4. provided that it is not intended to promote or facilitate self-harm.

§ 248. Illegal trade in goods and services

1. It is prohibited to use the Portal to sell, buy, offer, advertise or act as an intermediary in the trade of goods and services whose trade is prohibited by law.

2. The prohibition includes in particular cases concerning:

   1. illegal drugs and other prohibited substances;

   2. unlawfully offered weapons;

   3. explosives;

   4. stolen goods;

   5. documents or data used for fraud;

   6. other goods and services whose offering is unlawful.

3. ReputoNode may be used to lawfully present, promote or advertise products and services.

4. The User is responsible for ensuring that their offer or advertisement complies with law.

5. ReputoNode is not currently a specialised platform intermediating in the conclusion of contracts between clients and contractors, nor a classified-advertising service, even if User Content may lead to business contact being established.

§ 249. Fraud and data theft

1. It is prohibited to use the Portal for fraud or attempted fraud.

2. In particular, the following is prohibited:

   1. phishing;

   2. obtaining login credentials by deception;

   3. obtaining financial data by deception;

   4. fraudulent fundraising;

   5. fraudulent investments;

   6. pyramid schemes;

   7. impersonation for the purpose of obtaining money or data;

   8. knowingly directing Users to websites used for fraud;

   9. other activities aimed at unlawfully obtaining a benefit.

§ 250. False information and manipulation

1. An ordinary mistake, incorrect opinion or dispute as to facts does not in itself constitute a violation of the Terms.

2. However, knowingly disseminating false information is prohibited where, in the circumstances, this constitutes unlawful conduct, fraud or may cause material actual harm.

3. In particular, it is prohibited to present the following as authentic for the purpose of misleading others:

   1. forged documents;

   2. fabricated evidence;

   3. manipulated recordings;

   4. false communications from institutions;

   5. artificially generated material depicting events that did not occur.

4. Use of manipulated or generated material for satirical, artistic, educational or demonstrative purposes may be permitted if the context does not unlawfully mislead recipients.

§ 251. Access credentials and information enabling unauthorised access

1. It is prohibited to publish, without an appropriate legal basis:

   1. another person's passwords;

   2. login credentials;

   3. authentication tokens;

   4. private keys;

   5. API keys;

   6. access codes;

   7. data enabling unauthorised takeover of an Account;

   8. other data intended to obtain unauthorised access to a system, Account or data.

2. The prohibition does not apply to lawful publication of one's own sample or test data that does not enable unauthorised access.

§ 252. Doxxing and disclosure of third-party data

1. It is prohibited to publish another person's personal data or location information for the purpose of:

   1. intimidation;

   2. harassment;

   3. persecution;

   4. creating a threat;

   5. enabling other persons to cause harm.

2. Publishing an excessive scope of a third party's private data without an appropriate legal basis may also be prohibited, even if it is not accompanied by a direct threat.

3. The User should exercise particular caution when publishing:

   1. residential addresses;

   2. private telephone numbers;

   3. private email addresses;

   4. the precise current location of other persons;

   5. documents containing personal data;

   6. other information capable of infringing privacy or security.

§ 253. Confidential information

1. The User may not publish information which they are not authorised to disclose.

2. The prohibition may concern in particular:

   1. trade secrets;

   2. confidential documents;

   3. professional secrets;

   4. information subject to a confidentiality obligation;

   5. data covered by legally protected secrecy.

3. The User is responsible for determining whether they have the right to disclose specified information.

§ 254. Criticism of persons, companies and institutions

1. ReputoNode permits lawful criticism of:

   1. persons;

   2. businesses;

   3. products and services;

   4. employers;

   5. institutions;

   6. organisations;

   7. public figures;

   8. public authorities;

   9. other entities.

2. Criticism may be negative, forceful and polemical.

3. The User should distinguish their own opinions from statements presented as facts.

4. The right to criticise does not authorise unlawful conduct, in particular threats, harassment, fraud or infringement of other third-party rights.

§ 255. Impersonation

1. It is prohibited to impersonate:

   1. another person;

   2. a business;

   3. an organisation;

   4. an institution;

   5. an authority;

   6. a project;

   7. a brand;

   8. another entity,

2. in a manner capable of misleading recipients as to the Account's actual identity or affiliation.

3. The prohibition also covers the combined use of elements such as:

   1. username;

   2. display name;

   3. avatar;

   4. bio;

   5. photographs;

   6. manner of communication;

   7. published Content.

4. Fan, satirical or parody Accounts may be permitted if their nature is presented sufficiently clearly and they do not mislead recipients as to their authenticity.

§ 256. False claims of qualifications

1. It is prohibited to falsely present oneself as a representative of a profession, function or status that the User does not actually hold where this may mislead others.

2. The prohibition applies in particular to falsely presenting oneself as a person holding:

   1. medical qualifications;

   2. legal qualifications;

   3. a professional licence;

   4. technical authorisations;

   5. a certificate or professional title;

   6. a public office.

3. The User may describe their experience, interests and knowledge provided that they do not present qualifications they do not hold as actually possessed.

§ 257. Spam and mass activity

1. It is prohibited to use ReputoNode for spam.

2. In particular, the following may be prohibited:

   1. repeatedly publishing the same or almost identical Content;

   2. mass-publishing Content with no real value for recipients;

   3. mass-posting advertising links;

   4. automated publishing without the Service Provider's consent;

   5. mass creation of Accounts;

   6. mass commenting for promotion unrelated to the discussion;

   7. artificially generating activity;

   8. activities disrupting normal use of the Portal.

3. Lawful promotion of one's own products or services does not in itself constitute spam if its manner and frequency comply with Portal rules.

§ 258. Automated data collection

1. Without the Service Provider's consent, it is prohibited to use bots, scripts, crawlers, scrapers or other automated tools for mass:

   1. downloading Content;

   2. copying Profiles;

   3. copying User data;

   4. reconstructing databases;

   5. performing actions on the Portal;

   6. circumventing technical restrictions.

2. The prohibition does not apply to normal indexing of publicly available pages by commonly used internet search engines if the crawler:

   1. does not circumvent safeguards;

   2. respects technical restrictions of the Portal;

   3. does not cause excessive load on the infrastructure.

3. The Service Provider may technically restrict or block automated access that creates a risk or excessive load.

§ 259. System security

1. It is prohibited, without an appropriate legal basis, to undertake actions aimed at compromising the security of ReputoNode.

2. In particular, it is prohibited to:

   1. obtain unauthorised access;

   2. attempt to take over other persons' Accounts;

   3. circumvent authentication mechanisms;

   4. exploit vulnerabilities in order to cause harm;

   5. inject malicious code;

   6. manipulate requests in order to obtain unauthorised access;

   7. deliberately overload servers;

   8. carry out DoS or DDoS attacks;

   9. bypass safeguards;

   10. interfere with data integrity;

   11. make unauthorised modifications to the operation of the Portal.

3. Scanning, testing or examining security without consent may be considered a violation, in particular where it creates a risk, loads the infrastructure or leads to unauthorised access.

§ 260. Responsible vulnerability reporting

1. A person who accidentally notices a vulnerability or security error may report it to the Service Provider.

2. Merely reporting a vulnerability does not constitute a violation of the Terms.

3. The reporting person should:

   1. not exploit the vulnerability for gain;

   2. not access other persons' data beyond the scope accidentally exposed;

   3. not modify or delete other persons' data;

   4. not disrupt operation of the Portal;

   5. not disclose information in a manner that increases the threat before allowing the Service Provider to respond.

4. The Service Provider may assess the circumstances individually.

§ 261. Reverse engineering and circumvention of safeguards

1. Circumventing the Portal's technical safeguards is prohibited.

2. Decompilation, reverse engineering, analysis or other similar activities are prohibited only to the extent that restricting them is permitted by mandatorily applicable law.

3. These Terms do not exclude rights of which the User cannot effectively be deprived under applicable law.

§ 262. Disrupting operation of the Portal

1. It is prohibited to use ReputoNode in a manner that causes or is intended to cause:

   1. destabilisation of the Portal;

   2. excessive load on infrastructure;

   3. obstruction of use by other Users;

   4. disruption of the operation of APIs or internal services;

   5. unauthorised interference with data;

   6. disruption of communication between system components.

2. The Service Provider may apply technical measures restricting such activities.

§ 263. Malware and harmful materials

1. It is prohibited to transmit, publish, distribute or provide links to material intended to infect, damage, take over or disrupt the operation of a device or system.

2. The prohibition includes in particular:

   1. viruses;

   2. trojans;

   3. ransomware;

   4. spyware;

   5. credential stealers;

   6. malicious scripts;

   7. other malicious software.

3. Discussion of malware for educational, research or cybersecurity purposes may be permitted if the Content is not intended for an actual attack or distribution of malicious software.

§ 264. Voluntary sharing of login credentials

1. The User should keep the login credentials for their Account confidential.

2. The User should not voluntarily disclose their password or other data enabling access to the Account to third parties.

3. If the User voluntarily provides login credentials to another person, the User is responsible vis-à-vis the Service Provider for actions performed by that person using the Account to the extent that such liability is permitted by law.

4. The User may not rely solely on the fact that a particular action was performed by a person whom the User voluntarily enabled to use the Account.

5. The provisions of this paragraph do not apply to unauthorised takeover of an Account without the User's knowledge and consent.

§ 265. Unauthorised Account takeover

1. If a User suspects that their Account has been taken over by an unauthorised person, they should inform the Service Provider as soon as reasonably possible.

2. Cases of unauthorised Account takeover are assessed individually.

3. The Service Provider does not automatically assume that all actions performed from a compromised Account were carried out by its rightful User.

4. In order to secure the Account, the Service Provider may:

   1. temporarily restrict access;

   2. require an access-recovery procedure;

   3. invalidate specified sessions;

   4. remove or restrict Content published by the unauthorised person;

   5. make corrections to Reputation or Reactions;

   6. take other appropriate security measures.

§ 266. Circumvention of Moderation and restrictions

1. Deliberate circumvention of Moderation measures is prohibited.

2. The prohibition includes in particular:

   1. republishing Content removed because of a violation without remedying the cause of the violation;

   2. creating a new Account in order to circumvent a block;

   3. using another person's Account in order to circumvent a restriction;

   4. publishing the same prohibited Content in a modified form solely to avoid detection;

   5. circumventing restrictions concerning Reactions;

   6. circumventing blocks on domains, links or other technical safeguards.

3. Republishing Content may be permitted if it has been appropriately modified so that the reason for the previous violation no longer exists.

§ 267. Instructions concerning security and remedying violations

1. The Service Provider may request that the User take a specified action if this is necessary to:

   1. remedy a violation;

   2. secure an Account;

   3. protect other persons;

   4. secure infrastructure;

   5. clarify a serious suspicion of abuse.

2. The instruction should be related to use of the Portal and remain consistent with the Terms and the law.

3. The User should comply, within a reasonable scope, with an instruction that is consistent with the Terms.

4. Failure to cooperate may result in further Moderation action if justified by the nature of the matter.

§ 268. Commercial material and advertising

1. A User may publish Content concerning their lawful products, services, professional or business activity.

2. Such material may not:

   1. constitute spam;

   2. mislead recipients;

   3. promote unlawful activity;

   4. infringe third-party rights;

   5. circumvent rules concerning disclosure of sponsored Content.

3. If the User receives remuneration, a product, service or other benefit for publishing Content, they should clearly disclose the commercial or sponsored nature of the publication to the extent required by law and Portal rules.

§ 269. Educational, documentary, scientific, artistic and satirical context

1. Moderation may take into account the context of Content, in particular where it is:

   1. educational;

   2. scientific;

   3. historical;

   4. journalistic;

   5. documentary;

   6. artistic;

   7. satirical;

   8. critical;

   9. warning-oriented.

2. Content that in another context could be considered prohibited may be permissible if its actual purpose, manner of presentation and scope justify its publication.

3. Context does not, however, make lawful Content whose publication is prohibited by mandatorily applicable law.

4. When assessing Content, the Service Provider may also take into account whether only the scope of material necessary to achieve a lawful informational, educational or documentary purpose was published.

§ 270. User responsibility for published Content

1. The User is responsible for Content published through their Account to the extent resulting from applicable law.

2. In particular, the User should have an appropriate basis for:

   1. publishing works belonging to other persons;

   2. using the image of other persons;

   3. publishing personal data;

   4. disclosing confidential information;

   5. using designations, marks and other protected elements;

   6. publishing material received from third parties.

3. The technical possibility of publishing specified Content on the Portal does not mean that the Service Provider confirms that publication is lawful.

4. The absence of prior Moderation does not mean that the Content has been approved by the Service Provider.

§ 271. Development of rules concerning prohibited conduct

1. The Service Provider may develop the Community Standards in order to:

   1. explain existing rules more precisely;

   2. provide examples;

   3. respond to new types of abuse;

   4. adapt rules to the development of Portal functions;

   5. increase User safety.

2. Changes that are solely clarifying or organisational may be introduced without changing the basic rules of the Terms.

3. Material changes increasing User obligations or restricting the manner of using the services are introduced in accordance with the rules for amending documents applicable on ReputoNode.

4. When applying restrictions concerning User Content and conduct, the Service Provider should act diligently, objectively and proportionately and take into account the nature and context of the relevant matter.

Chapter 15

Following Users, feed, search and presentation of Content

§ 272. Following Users

1. A User with an active Account may follow other active public Accounts available on ReputoNode.

2. A User may not follow their own Account.

3. Following does not require the consent of the person being followed.

4. A User may stop following another person at any time.

5. Following does not automatically create a reciprocal relationship between Accounts.

6. Following a User does not directly affect that User's Reputation.

7. The mere fact of following a particular Account does not mean support for Content published by that Account or confirmation of its truthfulness.

§ 273. Information about following

1. ReputoNode does not currently automatically inform a User that another Account has started following them.

2. A User does not receive a direct list of persons who follow them.

3. ReputoNode does not publicly display the number of persons following a given Account.

4. ReputoNode does not publicly display a separate counter of persons followed by a given Account.

5. A list of Accounts that a User follows may, however, be available on that User's public Profile.

6. From the list referred to in paragraph 5, other persons may indirectly determine that a specified User follows a given Account.

7. The list of followed Accounts is public and cannot currently be hidden by the Profile owner.

§ 274. No function for blocking followers

1. ReputoNode does not currently provide a function enabling an individual person to be blocked solely in order to prevent that person from following an Account.

2. The absence of such a function does not limit the possibility of reporting a violation or applying Moderation in accordance with the Terms.

3. The Service Provider may in the future introduce mechanisms for blocking or restricting relationships between Users.

§ 275. Removal of a following relationship

1. A following relationship may be ended by the User by unfollowing the relevant Account.

2. Following relationships may also be removed in connection with:

   1. deletion of an Account;

   2. permanent blocking of an Account;

   3. technical operations;

   4. correction of an error;

   5. Moderation;

   6. another justified need related to correct operation of the Portal.

3. The Service Provider may make a technical correction to following relationships without User involvement if this is necessary to maintain data consistency.

§ 276. Basic feed

1. ReputoNode provides a feed used to present public Posts.

2. In its basic mode, the feed may present Posts chronologically, from newest to oldest.

3. As a rule, every active public Post may be displayed in the feed regardless of whether its author is followed by a given User.

4. Following the author of a Post does not currently automatically increase the position of that Post in the basic feed.

5. A Post deleted by its author is not presented in the ordinary feed.

6. A Post removed, hidden or excluded from public presentation as a result of Moderation may also be excluded from the feed.

7. A Draft is not presented in the public feed.

§ 277. Feed filtering

1. ReputoNode may enable Posts to be filtered according to specified parameters.

2. Filters may include in particular:

   1. Category;

   2. Post Type;

   3. authors followed by the User;

   4. location or geographical scope;

   5. the author's Reputation;

   6. publication date;

   7. occurrence of specified text in the title;

   8. other parameters available on the Portal at a given time.

3. Filtering by date may enable, in particular, specification that a Post is to be:

   1. older than a specified date;

   2. newer than a specified date.

4. Text search within filters may include:

   1. the original Post title;

   2. an available translation of the title if it has previously been created and saved in the system.

5. ReputoNode is not required to provide a filter by Content language.

6. The range of available filters may change as the Portal develops.

§ 278. Location and Post visibility

1. A Location assigned to a Post may be used for filtering or organising Content.

2. A Location does not in itself restrict the public visibility of a Post.

3. A Post may be presented to a User regardless of the User's actual or declared location.

4. This applies both to Posts assigned to a specific place and to Posts marked with Global scope.

5. The Service Provider may in the future use Location as one of the parameters for sorting or matching Content.

§ 279. Development of feed sorting

1. Chronological ordering of Posts does not have to be the only way of organising the feed.

2. The Service Provider may in the future introduce other methods of sorting or presenting Content.

3. The following may be used in particular when determining the order of Posts:

   1. the author's Reputation;

   2. freshness of Content;

   3. Reactions;

   4. Category;

   5. Post Type;

   6. following relationship;

   7. relevance to interests;

   8. User activity;

   9. Content quality;

   10. other parameters related to presentation of Content.

4. The exact sorting algorithm does not form part of the Terms.

5. The Service Provider does not guarantee continued use of one particular algorithm for ordering Posts.

§ 280. Possible feed modes

1. ReputoNode may provide different feed modes.

2. In the future, modes may be introduced such as:

   1. newest Content;

   2. Content from followed persons;

   3. recommended Content;

   4. Content whose author has high Reputation;

   5. thematically matched Content;

   6. other presentation methods.

3. The Service Provider does not undertake to permanently maintain a chronological feed mode or any other particular mode.

4. Individual modes may be added, changed or removed as part of Portal development.

§ 281. Reputation and Content visibility

1. Reputation may be used as one of the parameters for presenting Content.

2. In the future, the author's Reputation may affect in particular:

   1. the position of a Post in the feed;

   2. the position of a Comment;

   3. filtering results;

   4. Content recommendations;

   5. other presentation methods.

3. The number and type of Reactions may be used as internal system signals even if their number is not displayed publicly.

4. The effect of Reputation on Content presentation does not guarantee a specific position.

§ 282. Content personalisation

1. ReputoNode may in the future personalise the way Content is presented to individual Users.

2. Personalisation may take into account in particular:

   1. followed Accounts;

   2. Categories used by the User;

   3. Content viewed by the User;

   4. Reactions submitted by the User;

   5. the User's own Reputation in individual Categories;

   6. activity on the Portal;

   7. Content Location;

   8. other signals related to use of the Portal.

3. A User's Reputation in a given Category may be one of the signals indicating that the User is particularly interested in Content from that area.

4. In such a case, the Portal may present a greater amount of Content from that Category.

5. The exact personalisation rules may change as the Portal develops.

6. Introduction of personalisation does not guarantee that the User will see only Content consistent with their previous activity.

§ 283. Portal search engine

1. ReputoNode may provide a search engine for public Content and Accounts.

2. The search engine may be available both to logged-in Users and persons who do not have an Account.

3. Persons who are not logged in may in principle access the same public results as logged-in Users, except for functions requiring an Account.

4. Search may cover in particular:

   1. Users;

   2. usernames;

   3. display names;

   4. Posts;

   5. Post titles;

   6. Post Content;

   7. tags;

   8. Categories;

   9. dates;

   10. other public information available on the Portal.

5. The scope of searchable data may change.

§ 284. Matching search results

1. The search engine may use:

   1. exact matching;

   2. partial matching;

   3. searching for name fragments;

   4. searching for title fragments;

   5. other matching methods.

2. Search may cover both the original Post title and an available saved translation of the title.

3. The absence of a result for a specified query does not mean that the relevant Content does not exist.

4. The Service Provider does not guarantee identical search results for all Users or at all times.

§ 285. Exclusion of Content from search

1. Drafts are not presented in public search results.

2. Deleted Content should not be presented in public Portal search results.

3. Content hidden or excluded from public presentation as a result of Moderation may be removed from search results.

4. The Service Provider may temporarily restrict indexing of specified Content, in particular for technical, security or Moderation reasons.

§ 286. Sorting search results

1. ReputoNode may determine the order of search results using its own technical mechanisms.

2. The order may take into account in particular:

   1. relevance to the query;

   2. date;

   3. the author's Reputation;

   4. Category;

   5. Content type;

   6. other technical parameters.

3. The method of sorting results may be changed without preserving the previous algorithm.

4. The User has no right to a specified position of:

   1. their Profile;

   2. their Post;

   3. their Content;

   4. other published information

5. in search results.

§ 287. Public addresses of Posts and Profiles

1. A public Post may have a direct address enabling it to be opened without prior login, provided that its status permits public display.

2. A public Profile may be available without logging in.

3. Direct links to public Content may be shared by third parties.

4. The fact that a direct link is shared does not change the rules concerning rights to Content set out in the Terms.

§ 288. Indexing by external search engines

1. Public ReputoNode pages may be indexed by external internet search engines.

2. Indexing may include in particular:

   1. public Profiles;

   2. public Posts;

   3. public fragments of Content;

   4. titles;

   5. other information available without logging in.

3. An external search engine may store its own information concerning a previously indexed page.

4. Deletion or modification of Content on ReputoNode does not guarantee its immediate removal from external search-engine results.

5. For some time, an external search engine may display in particular:

   1. an old title;

   2. a text snippet;

   3. an outdated description;

   4. a previously indexed address;

   5. a copy or data from its own cache,

6. to the extent resulting from operation of the relevant external service.

7. The Service Provider does not directly control the speed at which indexes of external search engines are updated.

§ 289. Moderation and visibility

1. Moderation measures may affect Content visibility on the Portal.

2. In particular, Content may be:

   1. excluded from the feed;

   2. excluded from search results;

   3. restricted in a specified part of the Portal;

   4. hidden;

   5. removed.

3. Visibility restrictions imposed as a Moderation measure are subject to the rules set out in the Chapter concerning Moderation.

4. ReputoNode does not currently use a mechanism involving deliberate, hidden restriction of Account visibility solely so that the User does not know that their Content is being restricted.

5. The Service Provider may, however, apply visible restrictions or restrictions resulting from normal operation of the system in accordance with the Terms.

§ 290. No guarantee of visibility

1. Publication of a Post does not guarantee:

   1. a specified number of views;

   2. display to all Users;

   3. a specified position in the feed;

   4. a specified position in search results;

   5. receipt of Reactions;

   6. appearance in recommended Content.

2. Visibility may depend on:

   1. filters applied;

   2. User settings;

   3. the sorting algorithm;

   4. Reputation;

   5. Moderation;

   6. search parameters;

   7. technical parameters of the Portal;

   8. other Content-presentation mechanisms.

§ 291. Temporary unavailability of functions

1. Individual functions related to the feed, filtering, search or presentation of Content may be temporarily unavailable.

2. Reasons may include in particular:

   1. technical work;

   2. an update;

   3. a failure;

   4. correction of an error;

   5. security protection;

   6. infrastructure change;

   7. testing of new functions.

3. The Service Provider does not guarantee uninterrupted availability of every particular filter, sorting method or result-presentation method.

4. Temporary disabling of one auxiliary function does not automatically mean that the entire Portal is unavailable.

§ 292. Development of the Content-presentation system

1. ReputoNode may develop mechanisms for:

   1. the feed;

   2. sorting;

   3. filtering;

   4. search;

   5. recommendation;

   6. personalisation;

   7. presentation of Content.

2. Technical changes may include in particular introduction of new parameters, new feed modes and new methods of determining Content order.

3. Introduction or modification of a technical mechanism does not require amendment of the Terms if it does not result in a material change to the User's rights or obligations.

4. The Service Provider does not guarantee preservation of the previous appearance or manner of operation of individual functions related to Content presentation.

Chapter 16

Translations and multilingual operation of the Portal

§ 293. Multilingual ReputoNode

1. ReputoNode may be available in multiple language versions.

2. The number and scope of supported languages may change as the Portal develops.

3. The Terms do not specify a closed list of languages supported by ReputoNode.

4. Adding a new language version of the Portal or discontinuing support for a specified language does not require amendment of the Terms if it does not result in a material change to the User's rights or obligations.

5. The language of the Portal interface may be independent of the language in which Content was originally published.

§ 294. Original language of Content

1. Content published by Users has an original language determined by the ReputoNode system.

2. The original language may be determined automatically on the basis of the Content.

3. Automatic language detection may concern in particular:

   1. Posts;

   2. Comments;

   3. Replies;

   4. Profile bios;

   5. other textual Content supported by the translation mechanism.

4. The system does not guarantee error-free language detection.

5. Content containing several languages may be technically assigned to one language considered by the system to be the primary or dominant language.

6. A User may publish Content containing more than one language; however, ReputoNode does not guarantee correct detection or translation of such Content.

7. A User currently cannot independently change the language automatically assigned to published Content.

8. The Service Provider may in the future enable manual correction or reporting of an incorrectly detected language.

§ 295. Preservation of the original version

1. ReputoNode preserves the original version of User Content regardless of translations created later.

2. The original version is associated with the language in which the Content was originally published or which was determined for it by the system.

3. If the User uses the Portal in a language corresponding to the original language of the Content, the Portal may present its original version.

4. A translation does not replace the original Content for the purpose of determining what the User actually published.

5. Deleting a translation does not result in deletion of the original version of the Content.

§ 296. Automatic translation of Content

1. ReputoNode may automatically translate User Content into the language corresponding to the currently selected language version of the Portal interface.

2. Translation may include in particular:

   1. the Post title;

   2. textual blocks of a Post;

   3. Comments;

   4. Replies;

   5. Profile bios.

3. Automatic translation may be performed:

   1. using an external provider of translation technology;

   2. using the Service Provider's own technical solutions;

   3. using language models;

   4. using other automatic translation tools.

4. The Service Provider may change the technology and provider used to translate Content.

5. The name of a particular translation-technology provider does not form part of the Terms.

§ 297. Creation and storage of translations

1. If a translation of specified Content into the required language already exists, ReputoNode may use the previously stored translation.

2. If a translation does not yet exist, the Portal may create it automatically when there is a first need to display the Content in the relevant language.

3. A created translation may be stored in the system and used repeatedly.

4. ReputoNode is not required to translate Content again each time it is displayed.

5. A change of translation technology does not automatically result in regeneration of existing translations.

6. New technology may be applied only to:

   1. new Content;

   2. Content that has not yet been translated into the relevant language;

   3. Content selected by the Service Provider for retranslation.

§ 298. Retranslation

1. The Service Provider may delete an existing automatic translation and generate it again.

2. Retranslation may take place in particular where:

   1. a material translation error has been detected;

   2. the translation changes the meaning of the original statement;

   3. the User has reported a justified problem;

   4. a broader problem concerning a specified translation mechanism has been identified;

   5. a change of technology may materially improve translation quality;

   6. this is necessary for technical or Moderation reasons.

3. The Service Provider is not required to automatically retranslate all previously translated Content after every change of technology.

4. The Service Provider may carry out broader retranslation of specified Content if it identifies a justified need.

§ 299. Elements not subject to automatic translation

1. The automatic translation mechanism does not have to cover all elements published on ReputoNode.

2. In particular, tags added by Users are not automatically translated.

3. ReputoNode does not automatically translate text contained within:

   1. photographs;

   2. graphics;

   3. videos;

   4. other multimedia files.

4. ReputoNode does not automatically translate the content of external websites to which links posted by Users lead.

5. An external website may have its own language mechanisms independent of ReputoNode.

§ 300. Interface language and the way Content is displayed

1. ReputoNode may seek to present textual Content in the language corresponding to the currently selected language version of the interface.

2. If the original language of Content corresponds to the interface language, the Portal may display the original version.

3. If the original language of Content differs from the interface language, the Portal may:

   1. display a previously stored translation;

   2. automatically create a missing translation;

   3. display the original Content if a translation is unavailable.

4. The absence of a translation does not automatically result in the Content being hidden.

5. The interface language does not restrict the public visibility of Posts published in other languages.

6. All public Content may be presented regardless of its original language, subject to the other provisions of the Terms.

§ 301. Information about the original language

1. ReputoNode may display an indication next to Content identifying its original language.

2. The indication may in particular take the form of a flag corresponding to the language of the Content.

3. If the indication of the original language differs from the current language version of the Portal, this means that the displayed textual Content may be an automatically translated version.

4. The Portal does not have to display an additional separate “automatically translated” notice next to every Content item if the original-language indication makes it possible to recognise that the User is using a translated version.

5. The graphical manner of indicating language may change as the Portal develops.

§ 302. Access to original Content

1. A User may access the original version of Content by changing the Portal interface language to the language corresponding to the original language of the Content, provided that the relevant Portal language version is available.

2. ReputoNode is not required to provide a separate “Show original” button.

3. The method of accessing the original version may change as the Portal develops.

4. If a specified original language is not available as an interface language version, the ability to display the original may depend on the Portal's current technical functions.

§ 303. Inaccuracy of automatic translations

1. Automatic translations are auxiliary in nature.

2. A translation may contain in particular:

   1. errors;

   2. inaccuracies;

   3. simplifications;

   4. incorrectly selected meanings of words;

   5. omissions;

   6. context-related errors;

   7. incorrect translation of colloquial language;

   8. incorrect translation of irony, humour or sarcasm;

   9. a change in the nuance of a statement.

3. The risk of errors may be greater in the case of Content that is:

   1. multilingual;

   2. specialist;

   3. contains abbreviations;

   4. contains slang;

   5. contains language errors;

   6. deliberately ambiguous.

4. ReputoNode does not guarantee complete correctness, completeness or consistency of an automatic translation with the author's intention.

§ 304. Priority of the original version

1. In the event of a discrepancy between a User's original Content and its automatic translation, the original version prevails.

2. Automatic translation does not change the legal meaning or authorship of the original statement.

3. If a translation incorrectly changes the meaning of a statement, the User is not responsible for content that they did not actually publish in the original version, subject to applicable law.

4. When determining the actual content of a statement, its original version should be taken into account first.

§ 305. Reactions to translated Content

1. A User may submit an R+ or R− Reaction to Content presented to them in an automatically translated version.

2. Such a Reaction affects Reputation in accordance with the rules set out in Chapter 12.

3. The Content author does not receive information enabling them to determine in which language version a particular person reviewed the Content before submitting a Reaction.

4. In particular, on the basis of publicly available data the author cannot determine whether an R− was submitted after reviewing the original or the translation.

§ 306. Incorrect translation and Reputation

1. A User may report to the Service Provider that an automatic translation of their Content materially changes its meaning.

2. A report may be sent to contact@reputonode.com.

3. The Service Provider may verify:

   1. the original Content;
   2. the automatic translation;
   3. differences in meaning;
   4. the possible effect of the error on how the Content is perceived;
   5. the effect on the author's Reputation.

4. If the Service Provider determines that an incorrect translation may have materially contributed to a negative evaluation of the Content, it may:

   1. delete the incorrect translation;
   2. generate a new translation;
   3. invalidate a selected Reaction;
   4. correct the effect of a specified Reaction on Reputation;
   5. recalculate the relevant part of Reputation;
   6. apply another appropriate technical solution.

5. The mere assertion by the author that a translation is unfavourable or that the author received an R− does not automatically result in a correction.

6. A correction may be made following an individual assessment by the Service Provider.

§ 307. Translations and Moderation

1. When making a Moderation Decision concerning the meaning of textual Content, the Service Provider should, where possible, take its original version into account.

2. Automatic translation may be used as an auxiliary tool.

3. In doubtful cases, the Service Provider may use:

   1. more than one automatic translator;

   2. different language tools;

   3. additional available contextual information;

   4. explanations from the author or the reporting person.

4. The Service Provider is not required to use a sworn translator for Moderation of ordinary Portal Content unless such an obligation arises from law or the specific situation.

5. If a material doubt concerning the meaning of Content cannot be reliably resolved on the basis of available information, that circumstance may be taken into account when making the decision.

§ 308. Translations after Content deletion

1. If original Content ceases to be publicly available as a result of its deletion, automatic translations associated with it should also cease to be publicly available.

2. Translations may be stored technically for a specified period to the same extent that deleted Content may be stored under the Terms, the Privacy Policy or applicable law.

3. Deletion of a translation does not cause additional effects on Reputation beyond the cases specified in the Terms.

§ 309. Translations after Account deletion

1. If Content remains publicly available after final deletion and anonymisation of its author's Account, existing translations of that Content may also remain publicly available.

2. A translation remains associated with the anonymously retained Content and not with the former author's active Profile.

3. The mere deletion of an Account does not create an obligation to retranslate remaining Content.

§ 310. Authorship and rights to translations

1. Automatic translation of Content does not create a new author Account or change information about the Content author.

2. The author of Content presented in translation remains the author of the original Content to the extent resulting from the nature and legal status of the relevant Content.

3. Rights to Content and its automatically generated language versions are determined in accordance with applicable law and the provisions of the Terms concerning copyright and licences.

4. ReputoNode does not require the User to waive rights that may vest in them in an automatically translated version of their Content.

5. Regardless of paragraph 4, the Service Provider may use a translation to the extent necessary to provide ReputoNode services in accordance with the licence specified in the Terms.

§ 311. Translation as an auxiliary function

1. The automatic translation mechanism is an auxiliary ReputoNode function.

2. ReputoNode does not provide professional or certified translation services.

3. Automatic translation should not be treated as:

   1. a sworn translation;

   2. an official translation;

   3. a professional linguistic opinion;

   4. a guaranteed interpretation of a statement.

4. A User should not base a decision requiring particular accuracy solely on an automatic ReputoNode translation.

5. This applies in particular to:

   1. legal documents;

   2. contracts;

   3. medical information;

   4. financial information;

   5. safety-related instructions;

   6. other information whose incorrect translation may have material consequences.

§ 312. Unavailability of the translation mechanism

1. Automatic translations may be temporarily unavailable.

2. Reasons may include in particular:

   1. failure of an external provider;

   2. technical work;

   3. lack of access to the relevant service;

   4. exceeding technical limitations;

   5. network problems;

   6. failure of the ReputoNode system;

   7. change of translation technology.

3. If a translation cannot be created, the Portal may display the Content in its original version.

4. Temporary unavailability of translation does not automatically mean that the basic function of publishing or browsing Content is unavailable.

5. The Service Provider does not guarantee that every Content item will be available in every language supported by the Portal at all times.

§ 313. External translation providers

1. If ReputoNode uses an external provider of translation technology, content requiring translation may be transmitted to that provider to the extent necessary to perform the service.

2. The scope, basis and rules for processing personal data related to use of such providers are set out in the Privacy Policy.

3. The Service Provider may replace an external solution with a locally operating system or another mechanism that does not require Content to be transmitted to an external provider.

4. The technical manner of implementing translations may change without amendment of the Terms if it does not result in a material change to the User's rights or obligations.

§ 314. Development of language mechanisms

1. ReputoNode may develop mechanisms for:

   1. language detection;

   2. automatic translation;

   3. storing translations;

   4. correcting incorrect translations;

   5. language selection;

   6. presenting the original version;

   7. supporting multilingual Content.

2. In particular, the Service Provider may:

   1. change language models;

   2. change providers;

   3. use its own models;

   4. use different technologies for different languages;

   5. add new languages;

   6. change the method of language detection.

3. The Service Provider does not guarantee that translation quality will be identical between all languages.

§ 315. Language versions of ReputoNode documents

1. The Terms, Privacy Policy, Community Standards and other ReputoNode documents may be made available in different language versions.

2. Translations of ReputoNode documents are intended to facilitate use of the Portal by persons using different languages.

3. The Polish version of the Terms is the source version and is used to interpret its provisions in the event of discrepancies between language versions.

4. Paragraph 3 does not limit User rights arising from mandatorily applicable law whose application cannot be excluded by choosing a language version of the Terms.

5. If a discrepancy is detected between a translation of a document and its Polish version, the Service Provider may correct the translation accordingly.

Chapter 17

Account deletion and consequences of ending use of the Portal

§ 316. Request to delete an Account

1. A User may submit a request to delete their Account using the function available on the Portal.

2. Submission of an Account deletion request starts the procedure for ending use of ReputoNode.

3. Submission of the request does not result in immediate deletion of the Account.

4. From the moment the request is submitted, a 30-day waiting period begins before final deletion of the Account.

5. During the period referred to in paragraph 4, the User may cancel the Account deletion request in accordance with the Terms.

§ 317. Account status during the waiting period

1. During the waiting period before deletion, the Account continues to exist.

2. During that period the User may still log in to the Account.

3. In particular, the User may:

   1. browse public parts of the Portal;
   2. view their own Profile and previously published Content;
   3. review information concerning the planned deletion;
   4. contact the Service Provider;
   5. delete their own existing Drafts;
   6. delete their own previously published Posts;
   7. unfollow Accounts they previously followed;
   8. cancel the Account deletion request.

4. During the waiting period the User may not:

   1. publish new Posts;
   2. publish new Comments;
   3. publish new Replies;
   4. submit new R+ or R− Reactions;
   5. save, edit or publish Drafts, while deletion of Drafts remains permitted;
   6. edit the Profile, bio, avatar, Location or contact details;
   7. start following new Accounts, while ending an existing following relationship remains permitted;
   8. use other write functions that create or increase Content, data or relationships and are available exclusively to an active Account.

5. Deleting a Draft or a published Post, or ending a following relationship during the waiting period, is effective and is not automatically reversed if the User later cancels the Account deletion request.

6. If the User wishes to change the Profile or perform another operation blocked during the waiting period, the User should cancel the deletion request, perform the required action and then — if the User still wishes to delete the Account — start the Account deletion procedure again.

§ 318. Duration of the Agreement during the waiting period

1. Submission of an Account deletion request does not result in immediate termination of the Agreement.

2. During the 30-day period, the Agreement remains in force, but the range of available Account functions is restricted in accordance with the Terms.

3. The Account deletion request should be treated as commencement of the procedure leading to termination of the Agreement.

4. Final termination of the Agreement occurs upon final deletion and anonymisation of the Account.

5. Provisions which by their nature are intended to continue to apply after termination of the Agreement remain effective after its termination to the extent provided for by law and the Terms.

§ 319. Cancellation of an Account deletion request

1. A User may cancel an Account deletion request before the Account is finally deleted.

2. Cancellation ends the Account deletion procedure.

3. After cancellation, the Account regains its normal range of functions, subject to other restrictions arising from the Terms.

4. Cancellation of the request does not result in loss of:

   1. existing Reputation;

   2. remaining Content;

   3. existing following relationships that the User did not previously end;

   4. Profile data;

   5. other information associated with the Account that the User did not previously delete themselves.

5. Content deleted by the User and following relationships ended by the User during the waiting period are not automatically restored after cancellation of the procedure.

§ 320. Time of final Account deletion

1. Final Account deletion takes place after expiry of the 30-day waiting period if the User has not previously cancelled the request.

2. The Service Provider does not guarantee deletion of the Account at an exact hour after the 30-day period expires.

3. Final deletion may be carried out by periodic technical processes or maintenance tasks.

4. The Account should be deleted as part of a process carried out after expiry of the waiting period, without a guarantee as to the specific hour of deletion.

5. A minor technical delay resulting from the deletion-process schedule does not mean that the User's request has been cancelled.

§ 321. Consequences of final Account deletion

1. After final deletion of the Account, the User loses the ability to log in to it.

2. The Account cannot be restored.

3. The User's Profile ceases to function as an active Profile.

4. Data enabling normal use of the Account is deleted or anonymised in accordance with the rules set out in the Terms, the Privacy Policy and applicable law.

5. Final Account deletion results in termination of the Agreement.

§ 322. Data deleted or anonymised

1. As part of final Account deletion, the following in particular is deleted or anonymised:

   1. the email address used for the Account;

   2. authentication data;

   3. the password or its technical representation;

   4. Profile data;

   5. display name;

   6. bio;

   7. contact details;

   8. avatar;

   9. information concerning Profile Location;

   10. other data used to identify the active owner of the Account.

2. The scope of anonymisation may depend on the Portal's technical structure and applicable law.

3. The purpose of the process is to break the ordinary link between remaining Content and the User's active Account and Profile.

§ 323. Username after Account deletion

1. After final Account deletion, the previous username does not have to remain reserved.

2. The username may be made available again for registration by another person.

3. A person who registers the same username in the future does not become the owner of previous Content, Reputation or history of the former Account.

4. Reuse of a username does not mean restoration of the former Account.

5. The Service Provider may technically block reuse of a specified name where this results from Moderation, security, protection of the rights of other persons or other justified reasons.

§ 324. Technical data and internal identifiers

1. Final Account deletion does not mean that every technical identifier must be physically removed from every system structure if retaining it is necessary for:

   1. preserving database integrity;

   2. maintaining links with remaining Content;

   3. documenting Reputation events;

   4. security;

   5. system accountability;

   6. compliance with legal obligations.

2. A technical identifier may remain in particular in historical structures, logs or database relationships.

3. Retention of a technical identifier does not mean that an active Account or public Profile continues to exist.

§ 325. Remaining Posts

1. Deletion of an Account does not automatically result in deletion of Posts previously published by the User.

2. Posts which the User did not delete before final Account deletion remain publicly available unless they are removed or restricted under the Terms or the law.

3. Remaining Posts are presented without an active author Profile.

4. The Portal may identify the author of such a Post in a manner indicating that the Account has been deleted or anonymised.

5. A remaining Post may continue to:

   1. be displayed;

   2. have a direct address;

   3. receive Comments if the commenting function is available for it;

   4. contain remaining Media;

   5. have stored translations.

6. Account deletion does not automatically change the status of remaining Posts to deleted.

§ 326. Comments and Replies after Account deletion

1. Comments and Replies published by a User remain publicly available after final deletion of their Account unless they are removed or restricted under the Terms or the law.

2. The author of such Content is anonymised to the extent resulting from the Account deletion process.

3. Remaining Comments and Replies are not attributed to a new User even if someone registers the same username in the future.

4. Remaining Comments and Replies may continue to form part of an existing discussion.

§ 327. Media after Account deletion

1. Media forming part of a Post that remains publicly available after Account deletion remain available together with that Post unless they are removed or restricted under the Terms or the law.

2. This applies in particular to photographs and videos forming part of published Content.

3. Account deletion does not automatically remove Media from a Post that remains available.

4. If a Post was deleted before final Account deletion, associated Media should ultimately be deleted in accordance with the rules for technical data storage.

5. Media deletion may occur with a technical delay resulting from data-cleaning processes, backups or other system processes.

§ 328. Drafts after Account deletion

1. Drafts do not remain publicly available after final Account deletion.

2. Drafts should be deleted as part of the Account deletion process.

3. Media used exclusively in Drafts should be deleted if they are not used by other Content remaining on the Portal.

4. The Service Provider may use technical processes for periodic deletion of unused files.

§ 329. Translations after Account deletion

1. If an original Post, Comment or Reply remains available after final Account deletion, translations of it created previously may also remain available.

2. A translation remains associated with anonymously retained Content.

3. Account deletion does not automatically result in regeneration or deletion of translations of remaining Content.

4. If the original Content is later deleted, translations associated with it should cease to be publicly available in accordance with the rules set out in the Terms.

§ 330. Reputation after Account deletion

1. After final Account deletion, its Reputation is no longer presented as the User's current public Reputation.

2. A deleted Account does not retain a public competence Profile.

3. The historical effect of Content and Reactions associated with the Account may remain in the system to the extent necessary to preserve consistency of the Reputation mechanism.

4. Account deletion does not automatically reverse the effect of Reactions previously submitted by that User in relation to other Content.

5. Such Reactions may continue to affect the Reputation of other Users in accordance with Chapter 12.

6. Reactions previously received by the deleted User's Content may also remain technically recorded if necessary to preserve consistency of the system.

§ 331. Following relationships

1. Upon final Account deletion, following relationships associated with that Account are removed as part of the technical process.

2. This applies both to:

   1. Accounts followed by the User whose Account is being deleted;

   2. relationships in which other Accounts followed the Account being deleted.

3. Removal of such relationships may take place as part of the technical Account deletion process.

4. The Service Provider may carry out additional technical cleanup of following relationships after final Account deletion.

§ 332. Profile after Account deletion

1. After final Account deletion, its public Profile ceases to be active.

2. The address corresponding to the former Profile may:

   1. lead to information that the Profile does not exist;

   2. lead to information that the Account has been deleted;

   3. later be used by another Account if the same username is registered again.

3. A new User who has the same username does not obtain access to data, Content or history of the previous Account.

§ 333. Direct links to remaining Content

1. Account deletion does not automatically invalidate direct URLs to Posts that remain publicly available.

2. A direct link to a remaining Post may continue to work after deletion of its original author's Account.

3. In such a case, the Content is presented without an active link to the former User's Profile.

§ 334. Deleting Posts before Account deletion

1. A User who does not want their Posts to remain publicly available after final Account deletion should delete them before starting the Account deletion procedure.

2. After an Account is submitted for deletion, the User may still delete their own previously published Posts during the 30-day waiting period. A deletion performed during that period remains effective and is not automatically reversed if the User later cancels the Account deletion request.

3. Final Account deletion does not constitute an automatic request to delete all Content previously published.

4. Before starting the procedure, the User should check which Posts they want to retain and which they want to delete.

§ 335. Request to delete Content after Account deletion

1. A person whose Account has been finally deleted may later request that the Service Provider delete specific Content that the person previously published.

2. The request may be sent to legal@reputonode.com.

3. The person submitting the request must credibly demonstrate that they were the author of the Content or are a person entitled to request its deletion.

4. The Service Provider may request information or evidence allowing authorship or authority to act to be confirmed.

5. After authorship or authority has been credibly confirmed, the Service Provider will delete the specified Content.

6. The Terms do not specify a guaranteed time for carrying out such deletion.

7. The Service Provider may retain specified information if an obligation to retain it arises from law or another legally justified basis for continued storage exists.

§ 336. Account cannot be restored

1. After the final deletion process is completed, the Account cannot be restored.

2. Cancellation of deletion is possible only before the final process is carried out.

3. After final deletion, the Service Provider is not required to:

   1. recreate the Profile;

   2. recover Reputation;

   3. recreate following relationships;

   4. restore Drafts;

   5. recreate other Account data.

§ 337. Creating a new Account after deletion of the previous Account

1. A person whose Account was deleted at their request may create a new Account if there are no other obstacles arising from the Terms.

2. A new Account may be created using the same email address if that address is no longer assigned to another Account and the Portal's current technical rules allow it.

3. The new Account is a separate Account.

4. The new Account does not automatically recover:

   1. previous Reputation;

   2. previous Content;

   3. Comments;

   4. Replies;

   5. Reactions;

   6. followed Accounts;

   7. Moderation history;

   8. other data of the previous Account.

5. Remaining anonymous Content from the old Account does not automatically become Content of the new Account.

§ 338. Circumvention of a permanent block

1. Deletion of an Account does not entitle the User to circumvent a permanent block or another Moderation sanction.

2. A person subject to a prohibition on creating a new Account may not effectively circumvent that prohibition by:

   1. deleting the Account beforehand;

   2. using another email address;

   3. using another username;

   4. using another person's Account.

3. The technical ability to create a new Account does not mean that its creation complies with the Terms.

4. An Account created to circumvent a permanent block may be blocked again.

§ 339. Death or permanent incapacity of a User

1. If the Service Provider receives credible information about the death of a User or the User's permanent inability to use the Account, the Service Provider may consider the matter individually.

2. The Service Provider may request documents or other credible information confirming the circumstances of the matter and the reporting person's authority.

3. An Account is not automatically transferred to an heir or another person.

4. The Service Provider may take appropriate action concerning the Account or Content in accordance with the law and the circumstances of the matter.

§ 340. No automatic Account deletion due to inactivity

1. ReputoNode does not delete Accounts solely because of long-term inactivity.

2. An Account may remain inactive for an indefinite period unless another basis for restricting or deleting it applies.

3. The mere absence of login activity does not automatically start the Account deletion procedure.

§ 341. Retention of data required by law

1. Final Account deletion does not exclude the possibility of retaining specified data if this is required or permitted by applicable law.

2. Data may be retained in particular where necessary to:

   1. comply with a legal obligation;

   2. comply with a legally binding request of a competent authority;

   3. establish, pursue or defend claims;

   4. ensure Portal security;

   5. counteract fraud or abuse;

   6. document serious violations;

   7. preserve the technical integrity of the system.

3. Data retained under paragraph 2 should not be used to continue normal provision of the service to the deleted User.

4. The scope and period of further processing should be limited to the purpose justifying retention of the data.

5. Detailed information concerning processing of personal data after Account deletion is set out in the Privacy Policy.

§ 342. Backups

1. Data of a deleted Account may for a limited period be present in technical backups created before it was deleted from the production system.

2. Data from backups may be deleted through:

   1. backup rotation;

   2. overwriting;

   3. expiry of the retention period;

   4. another technical process used.

3. The Terms do not specify a fixed retention period for every backup.

4. Data located exclusively in a backup should not be reused for normal operation of a deleted Account.

5. If restoration of a backup technically restores data that was previously deleted, the Service Provider may reapply the process of deleting or anonymising that data.

§ 343. Consequences of termination of the Agreement

1. Final Account deletion results in termination of the Agreement between the User and the Service Provider.

2. After termination of the Agreement, the User loses the right to use functions requiring the deleted Account.

3. Termination of the Agreement does not automatically cause provisions concerning the following to cease to apply:

   1. remaining Content;

   2. the licence necessary for continued storage and presentation of remaining Content;

   3. intellectual-property rights;

   4. effects of previous Reactions;

   5. security;

   6. Moderation of historical violations;

   7. liability;

   8. claims;

   9. other obligations which by their nature apply also after termination of the Agreement.

4. Termination of the Agreement does not affect rights or obligations that arose before its termination.

Chapter 18

Suspension, restriction and termination of services by the Service Provider

§ 344. Technical interruptions

1. ReputoNode may be temporarily unavailable in whole or in part for technical, organisational or security reasons.

2. Temporary unavailability may result in particular from:

   1. maintenance work;

   2. updates;

   3. error correction;

   4. data migration;

   5. infrastructure changes;

   6. failures;

   7. cybersecurity activities;

   8. problems on the part of external service providers;

   9. other events affecting proper operation of the Portal.

3. The Service Provider may temporarily disable the entire Portal or only specified functions.

4. Temporary disabling may concern in particular:

   1. login;

   2. registration;

   3. publishing;

   4. commenting;

   5. submitting Reactions;

   6. search;

   7. filtering;

   8. automatic translations;

   9. uploading photographs or videos;

   10. other Portal functions.

§ 345. Information about technical work

1. The Service Provider does not guarantee advance notice of every technical interruption.

2. If planned work may cause longer or material unavailability of the Portal, the Service Provider may, where possible, inform Users before the work begins.

3. Information may be provided in particular:

   1. on the Portal;

   2. by means of a technical notice;

   3. by email;

   4. in another appropriate manner.

4. Failures, security incidents and other sudden events may cause unavailability without prior notice.

5. The Service Provider is not required to send an individual email about every failure or technical interruption.

§ 346. Restrictions for security reasons

1. The Service Provider may temporarily restrict operation of the Portal where justified by the security of the system, data, Users or third parties.

2. A restriction may be introduced in particular in the event of:

   1. a cyberattack;

   2. suspected intrusion;

   3. detection of a vulnerability;

   4. risk of unauthorised access to data;

   5. risk of data loss or corruption;

   6. detection of malicious software;

   7. excessive infrastructure load;

   8. another material technical threat.

3. Where necessary, the Service Provider may temporarily block login for all Users.

4. The Service Provider may also temporarily disable registration of new Accounts.

5. Restrictions may remain in place for the time necessary to remove or reduce the threat.

§ 347. Restriction of file uploads

1. The Service Provider may temporarily restrict or disable the ability to upload photographs, videos or other supported files.

2. A restriction may be applied in particular in the event of:

   1. upload-security problems;

   2. failure of the file-processing mechanism;

   3. disk-space problems;

   4. video-processing problems;

   5. detection of a vulnerability;

   6. the need to change supported formats;

   7. other technical problems.

3. Temporary disabling of uploads does not automatically mean that existing Content is unavailable.

§ 348. Development and changes to the Portal

1. ReputoNode is a service under development and its appearance, functions and manner of operation may change over time.

2. The Service Provider may change in particular:

   1. the appearance of the interface;

   2. page structure;

   3. placement of elements;

   4. navigation methods;

   5. the manner of presenting Content;

   6. search mechanisms;

   7. filtering mechanisms;

   8. recommendation mechanisms;

   9. technical solutions;

   10. the scope of additional functions.

3. Changes may result in particular from:

   1. Portal development;

   2. usability improvements;

   3. security;

   4. technological changes;

   5. the need to correct errors;

   6. legal changes;

   7. organisational decisions.

§ 349. Adding, changing and removing functions

1. The Service Provider may add new functions without amending the Terms if they do not result in a material change to the User's rights or obligations.

2. The Service Provider may change, replace or remove auxiliary or additional functions.

3. The Service Provider may discontinue a specified function without closing the entire Portal.

4. This applies in particular to functions such as:

   1. a specified sorting method;

   2. a specified filter;

   3. automatic translations;

   4. a specified feed-presentation method;

   5. a specified integration with an external service;

   6. another additional function.

5. If permanent disabling of a function is materially significant to the manner in which the Portal is used, the Service Provider may inform Users where circumstances allow.

6. The Service Provider does not guarantee that every function will remain unchanged throughout the duration of the Agreement.

§ 350. No guarantee of a fixed functional form

1. The User acknowledges that ReputoNode may be developed and rebuilt.

2. The Service Provider does not guarantee that:

   1. every current function will remain available indefinitely;

   2. every function will always operate in an identical manner;

   3. the interface appearance will remain unchanged;

   4. all integrations with external services will remain available indefinitely;

   5. all current filtering, search or presentation methods will remain unchanged.

3. A technical change may not deprive the User of rights that cannot effectively be limited under applicable law.

§ 351. Testing new functions

1. The Service Provider may conduct tests of new functions, technical solutions or ways of presenting the Portal.

2. Tests may be available only to some Users.

3. During tests, different Users may see:

   1. different versions of the interface;

   2. different sorting methods;

   3. different functions;

   4. different variants of operation of specified Portal elements.

4. A test function may be:

   1. changed;

   2. expanded;

   3. restricted;

   4. temporarily disabled;

   5. completely withdrawn.

5. Tests may affect the manner of operation or scope of functions available to individual Users.

6. Tests do not limit User rights that cannot be excluded or restricted under the Terms or applicable law.

§ 352. Change of technical infrastructure

1. The Service Provider may change the infrastructure used to operate ReputoNode.

2. Changes may include in particular:

   1. changing hosting;

   2. changing servers;

   3. changing the email provider;

   4. changing the translation provider;

   5. changing the map provider;

   6. changing data-storage services;

   7. changing security providers;

   8. changing other technical providers.

3. A change of technical provider does not require amendment of the Terms if it does not result in a material change to the User's rights or obligations.

4. Rules for processing personal data by the relevant providers are set out in the Privacy Policy to the extent required by law.

§ 353. Data migration and conversion

1. The Service Provider may migrate data to new systems, databases, servers or technical formats.

2. Such activities may involve:

   1. restructuring the database;

   2. changing the format in which information is stored;

   3. converting files;

   4. changing the manner in which Media are encoded;

   5. transferring data between systems;

   6. other technical activities.

3. The Service Provider should seek to preserve the meaning and functional significance of Content to an extent appropriate to the relevant migration.

4. Migration may cause temporary unavailability of part of the Portal.

5. The Service Provider does not guarantee that every technical element will be preserved in identical form if changing it does not materially alter the meaning of Content or User rights.

§ 354. Change of domain and addresses

1. The Service Provider may change the ReputoNode internet domain.

2. The Service Provider may also change URL structures.

3. Where possible, the Service Provider may use redirects from old addresses to new ones.

4. The Service Provider does not guarantee indefinite operation of all historical URLs.

5. A domain change does not in itself terminate the Agreement.

§ 355. Geographical restrictions

1. ReputoNode does not guarantee availability from every country or territory in the world.

2. The Service Provider may restrict access to all or part of the Portal from a specified country, region or area where justified in particular by:

   1. applicable law;

   2. a decision of a competent authority;

   3. security;

   4. sanctions;

   5. technical limitations;

   6. risk of abuse;

   7. another justified reason.

3. Restricting geographical availability does not automatically mean deletion of Accounts of Users from the relevant area unless necessary.

§ 356. Change of supported languages

1. The Service Provider may add or remove language versions of the ReputoNode interface.

2. Discontinuation of support for a specified interface language does not automatically result in deletion of Content previously published in that language.

3. Content may remain on the Portal in accordance with the Terms.

4. Access to translations of such Content may depend on the Portal's current language mechanisms.

§ 357. Backups and system restoration

1. The Service Provider may create backups of Portal data.

2. Backups may serve in particular to:

   1. restore the system after a failure;

   2. limit the effects of data corruption;

   3. restore infrastructure operation;

   4. respond to security incidents.

3. The Service Provider may restore the system from an available backup where technically justified.

4. In exceptional circumstances, restoring the system from an earlier backup may result in loss of data created after that backup was made.

5. The Service Provider takes reasonable measures to protect data and limit the risk of its loss; however, it does not guarantee the absolute impossibility of data loss in the event of a serious failure, infrastructure damage or another technical event.

6. Paragraph 5 does not exclude the Service Provider's liability to the extent that exclusion or limitation of such liability is not permitted under mandatorily applicable law.

§ 358. No guaranteed availability level

1. ReputoNode is not provided with a percentage-based guaranteed availability level.

2. The Service Provider does not guarantee:

   1. Portal availability 24 hours a day, 7 days a week, without any interruptions;

   2. a specified percentage availability level;

   3. immediate removal of every failure;

   4. a specified technical response time;

   5. uninterrupted operation of all external services;

   6. complete absence of technical errors.

3. Temporary interruptions may also occur during normal operation of the Portal.

4. The absence of a guaranteed availability level does not release the Service Provider from obligations arising from mandatorily applicable law.

§ 359. External services

1. Some ReputoNode functions may depend on services provided by third parties.

2. This applies in particular to services related to:

   1. hosting;

   2. email;

   3. automatic translations;

   4. maps and geolocation;

   5. external materials embedded in Posts;

   6. other infrastructure elements.

3. Failure or restricted operation of an external service may cause temporary unavailability of the associated ReputoNode function.

4. In such a situation, the Service Provider may:

   1. temporarily disable the function;

   2. use a substitute solution;

   3. change the provider;

   4. disable the function until the problem is resolved.

5. The provisions of this paragraph do not exclude User rights arising from mandatorily applicable law.

§ 360. Complete discontinuation of ReputoNode

1. The Service Provider may decide to permanently discontinue ReputoNode.

2. The decision may result in particular from:

   1. organisational reasons;

   2. technical reasons;

   3. financial reasons;

   4. legal reasons;

   5. security reasons;

   6. inability to continue operating the Portal;

   7. other reasons.

3. The Service Provider is not required to maintain ReputoNode for a specified minimum period.

4. Where circumstances allow, the Service Provider may inform Users in advance of the planned discontinuation of the Portal.

5. The Terms do not establish a fixed minimum advance-notice period for such information.

6. The scope and timing of information may depend on the circumstances of the particular discontinuation.

7. In the event of sudden legal, technical or security events or other circumstances making continued operation impossible, the Portal may be disabled without prior notice.

8. This paragraph applies subject to User rights arising from mandatorily applicable law.

§ 361. Consequences of complete closure of the Portal

1. Permanent discontinuation of ReputoNode results in termination of services provided through the Portal.

2. After closure of the Portal, public Posts, Comments, Replies, Profiles and other Content cease to be available on ReputoNode.

3. The Service Provider may delete data from the production system as part of the Portal closure process.

4. Closure of the Portal may also include deletion of:

   1. Accounts;

   2. Profiles;

   3. Posts;

   4. Comments;

   5. Replies;

   6. Media;

   7. Drafts;

   8. Reactions;

   9. Reputation data;

   10. translations;

   11. other data related to provision of services.

5. The Service Provider does not envisage an obligation to provide a special technical function for complete export of all data solely for the purposes of closing the Portal, subject to User rights arising from applicable law.

§ 362. Data retained after closure of the Portal

1. Despite closure of ReputoNode, specified data may be retained if required or permitted by law.

2. Data may be stored in particular for the purpose of:

   1. complying with a legal obligation;

   2. complying with a request of a competent authority;

   3. establishing, pursuing or defending claims;

   4. documenting security incidents;

   5. counteracting fraud;

   6. other lawful purposes.

3. Data retained after closure is no longer used for ordinary provision of the ReputoNode service.

4. Detailed rules concerning personal data are set out in the Privacy Policy.

§ 363. Backups after closure of the Portal

1. After permanent closure of ReputoNode, data may remain for some time in existing backups.

2. Such backups may be deleted through their normal rotation cycle, overwriting or another technical process used.

3. The Terms do not specify a fixed retention period for all backups.

4. Data existing exclusively in backups is not used to restart User Accounts unless system restoration is necessary for technical or legal reasons before completion of the winding-down process.

§ 364. No absolute guarantee of correct operation

1. The Service Provider takes measures aimed at maintaining the Portal in a condition enabling proper use of its functions.

2. Due to the nature of internet services, the Service Provider cannot guarantee the complete absence of:

   1. failures;

   2. errors;

   3. interruptions;

   4. delays;

   5. loss of individual data as a result of a serious technical incident;

   6. problems resulting from third-party services.

3. The User should keep their own copies of Content whose loss would be materially significant to them.

4. ReputoNode should not be treated as the sole storage location for important or irreplaceable material.

5. The provisions of this paragraph do not exclude or limit the Service Provider's liability to the extent that such exclusion or limitation would be impermissible under mandatorily applicable law.

Chapter 19

Complaints and contact with the Service Provider

§ 365. Right to submit a complaint

1. A User and another person using public ReputoNode functions may submit a complaint concerning the manner in which services are provided by the Service Provider if the matter concerns them.

2. A complaint may concern in particular:

   1. problems with Account registration;

   2. login problems;

   3. incorrect operation of an Account or Profile;

   4. incorrect operation of publishing functions;

   5. problems with Posts, Comments or Replies resulting from operation of the Portal;

   6. incorrect operation of Reactions;

   7. a suspected error in the Reputation system;

   8. problems with automatic translations;

   9. problems with the Account deletion process;

   10. unavailability or incorrect operation of a specified function;

   11. other problems concerning provision of ReputoNode services.

3. The complaints procedure is not intended for reporting Illegal Content, violations of the Terms or Community Standards, or appeals against Moderation Decisions.

4. Matters referred to in paragraph 3 are considered in accordance with the rules set out in Chapter 13.

§ 366. How to submit a complaint

1. A complaint may be sent by email to contact@reputonode.com.

2. A complaint may also be sent by post to the Service Provider's address indicated in Chapter 3.

3. Email is the primary and recommended channel for submitting complaints.

4. The Service Provider does not currently provide a separate electronic complaints panel on the Portal.

5. Introduction of an additional complaints mechanism in the future does not require amendment of the Terms if it does not restrict User rights.

§ 367. Content of a complaint

1. A complaint should make it possible to determine what the problem concerns and, where possible, reproduce it.

2. Depending on the nature of the matter, a complaint should contain in particular:

   1. an email address enabling contact;

   2. the username if the matter concerns an Account;

   3. a description of the problem;

   4. the date or approximate time when the problem occurred;

   5. identification of the function concerned;

   6. a direct link to Content if relevant to the matter;

   7. an error message if one was displayed;

   8. a screenshot or other supporting material if it may facilitate diagnostics;

   9. a description of the expected way of resolving the matter if the complainant wishes to indicate one.

3. The absence of some of the information listed in paragraph 2 does not automatically result in rejection of the complaint.

4. If the available information allows the matter to be considered, the Service Provider may consider the complaint without requesting supplementation.

§ 368. Supplementing a complaint

1. If the information contained in a complaint is insufficient for its consideration, the Service Provider may ask the complainant to supplement it.

2. The request may concern in particular:

   1. a more detailed description of the problem;

   2. identification of the Account;

   3. providing the address of specific Content;

   4. indicating the time when the problem occurred;

   5. providing technical information;

   6. sending a screenshot;

   7. providing other information necessary to examine the matter.

3. The Service Provider should request only information reasonably necessary to consider the complaint.

4. Inability to obtain information necessary to examine the problem may make full consideration of the matter impossible.

§ 369. Anonymous complaints

1. A complaint may be submitted without providing a first and last name if the nature of the matter permits it to be considered.

2. A complaint submitted without any contact channel may remain unanswered.

3. The Service Provider may leave an anonymous complaint without further consideration if:

   1. it is not possible to determine what it concerns;

   2. necessary additional information cannot be obtained;

   3. it is not possible to confirm authority to act in a matter concerning a specific Account;

   4. it is not possible to provide a response;

   5. the complaint is manifestly unfounded or incomprehensible.

4. Failure to provide a first and last name does not in itself constitute grounds for rejecting a complaint if it can be properly considered on the basis of other information.

§ 370. Consideration of complaints

1. Complaints are considered by the Service Provider or a person authorised by the Service Provider.

2. The Service Provider does not set in the Terms a shorter voluntary period for considering complaints than the period required by applicable law.

3. If applicable law specifies a period for considering a complaint or providing a response in a given matter, the Service Provider applies that period.

4. In other cases, a complaint is considered without undue delay, taking into account the nature and complexity of the matter.

5. The time required may depend in particular on:

   1. the ability to reproduce the error;

   2. the need to analyse technical data;

   3. the need to obtain additional information;

   4. dependence on an external provider;

   5. the nature and scale of the problem.

§ 371. Response to a complaint

1. A response to a complaint is generally sent to the email address indicated by the complainant or assigned to the Account if the complaint was submitted in connection with that Account.

2. In the case of a complaint sent by post, the response may be provided in a form appropriate to the method of contact and the available data.

3. In its response, the Service Provider may:

   1. uphold the complaint;

   2. uphold it in part;

   3. decline to uphold it;

   4. inform about a correction made;

   5. inform about planned remedial action;

   6. indicate that no irregularity on the part of ReputoNode was identified;

   7. provide other information concerning the outcome of the analysis.

4. Where possible, the response should enable the complainant to understand the outcome of the matter.

§ 372. Possible ways of resolving a problem

1. If a complaint is justified, the Service Provider may apply a solution appropriate to the nature of the problem.

2. This may include in particular:

   1. correcting an error;

   2. correcting data;

   3. restoring correct operation of a function;

   4. correcting Reactions;

   5. correcting Reputation;

   6. repeating a technical operation;

   7. correcting a translation;

   8. restoring data if technically possible and justified;

   9. applying a substitute solution;

   10. other appropriate action.

3. Upholding a complaint does not mean that the Service Provider must apply exactly the solution indicated by the complainant if another proper way of resolving the problem exists.

4. The Service Provider is not required to apply a technically impossible solution, subject to rights available to the User under mandatorily applicable law.

§ 373. Complaints concerning Reputation

1. A User may submit a complaint if they suspect that their Reputation was determined incorrectly due to:

   1. a technical error;

   2. incorrect assignment of a Reaction;

   3. manipulation of the system;

   4. an incorrect translation affecting Reactions;

   5. another irregularity in system operation.

2. Mere dissatisfaction with the level of Reputation does not constitute grounds for manually increasing the score.

3. The Service Provider may examine the relevant technical data and history of events affecting Reputation.

4. If no irregularity is identified, the score may remain unchanged.

5. If an error is confirmed, the Service Provider may make a correction in accordance with the Terms.

§ 374. Problems on the User's side

1. Not every problem with using ReputoNode means that the Portal is operating incorrectly.

2. A problem may result in particular from:

   1. the User's device;

   2. the operating system;

   3. the browser;

   4. browser extensions;

   5. privacy settings;

   6. JavaScript being blocked;

   7. cookie settings;

   8. the internet connection;

   9. network configuration;

   10. other software on the User's side.

3. If the analysis does not indicate a problem on the part of ReputoNode, the Service Provider may inform the complainant accordingly.

4. The Service Provider may provide basic information helpful in diagnostics, but does not provide a mandatory individual servicing service for the User's devices or software.

§ 375. Technical data needed for diagnostics

1. For the purpose of considering a complaint, the Service Provider may request a reasonable scope of technical information.

2. Information may include in particular:

   1. device type;

   2. operating system;

   3. browser name and version;

   4. error message;

   5. screenshot;

   6. approximate time when the problem occurred;

   7. description of steps leading to the error.

3. The Service Provider should not require the User to provide the Account password for the purpose of considering a complaint.

4. The User should not send their password to the Service Provider.

5. If a person claiming to represent ReputoNode requests that the password be sent, the User should treat the situation as a potential threat and report it to the Service Provider.

§ 376. Resubmitting a problem

1. A User may contact the Service Provider again in the same matter if:

   1. new information has emerged;

   2. the problem persists;

   3. the solution applied did not resolve the problem;

   4. there is new evidence indicating an irregularity.

2. Resubmission does not automatically change the previous position.

3. The Service Provider may take new circumstances into account in a renewed analysis.

§ 377. Distinguishing complaints from Reports and Moderation

1. A complaint concerning operation of the service is separate from:

   1. a Report of Illegal Content;

   2. a Report of a violation of the Terms;

   3. a Report of a violation of the Community Standards;

   4. an appeal against a Moderation Decision.

2. If a message was sent as a complaint but its content indicates that it actually concerns a Moderation matter, the Service Provider may consider it under the procedure appropriate to such a matter.

3. Incorrectly naming a message a “complaint”, “report” or “appeal” does not automatically result in its rejection if its actual nature can be determined from its content.

§ 378. No fees for considering complaints

1. Submission and consideration of a complaint by ReputoNode is free of charge.

2. ReputoNode does not charge the User a fee for reporting a problem or for responding to a complaint.

3. The User may bear ordinary costs of using their own internet connection or postal correspondence.

§ 379. Free nature of the Portal and remedies

1. ReputoNode is currently a free service.

2. For this reason, the standard complaints procedure does not include refund of a price paid for using the Portal, because the User does not pay a price for basic use of the services.

3. The free nature of the Portal does not limit User rights arising from mandatorily applicable law.

4. If applicable law grants the User a specified remedy regardless of the absence of payment of a price, the Terms do not exclude that right.

§ 380. Complaints concerning business results

1. The ability to publish information about activities, products or services on ReputoNode does not mean that the Service Provider undertakes to provide the User with a specified business result.

2. In particular, ReputoNode does not guarantee:

   1. acquisition of clients;

   2. receipt of requests for quotations;

   3. conclusion of contracts;

   4. generation of revenue;

   5. generation of profit;

   6. a specified number of views of promotional materials;

   7. a specified advertising effectiveness;

   8. continuous visibility of Content without any technical interruptions.

3. The mere fact that a User conducts business activity and uses ReputoNode to promote it does not mean that the Service Provider assumes responsibility for the success of that activity.

4. Temporary unavailability of the Portal does not automatically give the User the right to demand compensation for anticipated, potential or unproven business benefits.

5. The Service Provider's liability for any damage or lost profits is subject to the rules set out in the Terms and applicable law.

§ 381. No guarantee of a specific complaint outcome

1. Submission of a complaint does not automatically mean that the complainant's position is accepted as correct.

2. The Service Provider may decline to uphold a complaint if:

   1. it identifies no irregularity;

   2. the problem does not result from operation of ReputoNode;

   3. the request is contrary to the Terms or law;

   4. the request is technically impossible and the law does not require its fulfilment;

   5. the complainant has not demonstrated circumstances necessary for action to be taken;

   6. another justified basis exists.

3. Refusal to uphold a complaint does not limit the User's ability to use other remedies provided by law.

§ 382. Statutory User rights

1. The complaints procedure set out in the Terms does not exclude or limit rights available to the User under mandatorily applicable law.

2. In particular, the provisions of the Terms do not limit the rights of consumers or other persons benefiting from protection provided by applicable law.

3. If a provision of the Terms conflicts with a mandatorily applicable provision of law, the relevant provision of law applies.

4. Use of the complaints procedure does not deprive the User of the possibility of pursuing claims by other legally permissible means.

§ 383. Data related to complaints

1. The Service Provider may store information related to a complaint to the extent necessary for:

   1. considering it;

   2. documenting the course of the matter;

   3. implementing the decision taken;

   4. preventing abuse;

   5. ensuring security;

   6. establishing, pursuing or defending claims;

   7. complying with legal obligations.

2. Data related to a complaint should not be stored longer than justified by the relevant purpose or required by law.

3. Detailed information concerning processing of personal data in connection with complaints is set out in the Privacy Policy.

Chapter 20

Liability of the Service Provider and the User

§ 384. General liability rules

1. Liability of the Service Provider and the User connected with use of ReputoNode is determined on the basis of the Terms and applicable law.

2. No provision of the Terms excludes or limits liability to the extent that such exclusion or limitation is impermissible under mandatorily applicable law.

3. In particular, the Terms do not limit rights available to a consumer or another person benefiting from protection provided by mandatorily applicable law.

4. With respect to Users using ReputoNode in connection with business, professional, organisational or institutional activity, the Service Provider's liability may be limited to a broader extent where permitted by applicable law.

§ 385. No guarantee of business results

1. ReputoNode does not guarantee that the User will achieve any specified business, professional or organisational result.

2. In particular, the Service Provider does not guarantee:

   1. acquisition of clients;

   2. receipt of requests for quotations;

   3. acquisition of assignments;

   4. conclusion of a contract;

   5. completion of a sale;

   6. generation of revenue;

   7. generation of profit;

   8. increased recognition of an activity;

   9. obtaining a specified number of contacts;

   10. achieving a specified number of Content views;

   11. a specified position of Content in the feed or search engine.

3. The ability to publish information about activities, products or services is a Portal function and does not constitute a guaranteed advertising service ensuring specified business effectiveness.

4. The mere fact of using ReputoNode in business or professional activity does not mean that the Service Provider assumes the User's business risk.

§ 386. Use of the Portal in business activity

1. A User using ReputoNode to promote or conduct business or professional activity should provide themselves with appropriate alternative channels for:

   1. contact with clients;

   2. presenting an offer;

   3. accepting orders;

   4. storing data;

   5. conducting the activity.

2. The User should not make the ability to conduct their activity depend exclusively on the availability of ReputoNode.

3. ReputoNode is not a tool guaranteeing continuity of business operations.

4. A Professional User should independently assess the business risk connected with using the Portal as one of the channels of promotion or communication.

§ 387. Lost profits and indirect damage

1. With respect to Users using ReputoNode in connection with business, professional, organisational or institutional activity, to the maximum extent permitted by law, the Service Provider is not liable for lost profits resulting from temporary unavailability, an error or a restriction of the Portal.

2. The exclusion referred to in paragraph 1 may include in particular:

   1. lost profit;

   2. lost clients;

   3. missed sales opportunities;

   4. contracts not concluded;

   5. lost orders;

   6. lost business opportunities;

   7. expected revenue;

   8. other indirect business consequences.

3. To the extent permitted by law, the Service Provider is also not liable to Professional Users for indirect or consequential damage resulting solely from inability to use the Portal.

4. The provisions of this paragraph do not apply to the extent that liability cannot effectively be excluded or limited.

§ 388. No liability for User Content

1. Content published by Users originates from those Users.

2. ReputoNode does not automatically confirm:

   1. the truthfulness of Content;

   2. the completeness of Content;

   3. the currency of information;

   4. the author's qualifications;

   5. the legality of every publication;

   6. the quality of presented products or services.

3. The mere technical availability of Content on ReputoNode does not mean that the Service Provider has approved it.

4. The absence of prior Moderation of Content does not mean that the Service Provider considered it correct, lawful or compliant with the Terms.

5. The Service Provider's liability for information stored at the request of Users is subject to the rules arising from applicable law concerning intermediary and hosting services.

§ 389. Use of information published by others

1. The User independently assesses the usefulness and reliability of information published by other Users.

2. The author's Reputation may be one factor helpful in assessing Content, but does not guarantee its truthfulness.

3. Particular caution should be exercised when using Content concerning in particular:

   1. health;

   2. law;

   3. finances;

   4. investments;

   5. safety;

   6. technical work;

   7. other fields in which an incorrect decision may have material consequences.

4. Content published on ReputoNode does not replace individual advice from an appropriately qualified specialist.

5. The User makes decisions on the basis of other persons' Content at their own responsibility, subject to liability that cannot be excluded by law.

§ 390. Products and services offered by Users

1. ReputoNode may enable Users to publish information about products or services they offer.

2. ReputoNode is not a party to a contract concluded directly between Users or between a User and a third party as a result of contact established through the Portal.

3. The Service Provider is not responsible for:

   1. the quality of the offered product;

   2. the quality of the service performed;

   3. conformity of the product with its description;

   4. the time of performance;

   5. the manner in which the contract is performed;

   6. payment;

   7. non-payment;

   8. guarantees;

   9. statutory warranty;

   10. other obligations arising between the parties to such a contract.

4. Parties concluding a contract outside ReputoNode are independently responsible for determining its terms and performing it.

5. If ReputoNode in the future begins providing a separate intermediation service for concluding or performing such contracts, appropriate rules may be specified separately.

§ 391. Links and external Content

1. Users may publish links leading to external websites and services in accordance with the Terms.

2. The Service Provider does not continuously control the content or operation of all external websites.

3. ReputoNode is not responsible for the content of an external website solely because a User posted a link to it.

4. Mere technical display of a link preview does not constitute a recommendation of the website, product, service or information available under that link.

5. The User should exercise caution before leaving ReputoNode and using an external service.

§ 392. Embedded external materials

1. ReputoNode may enable display of materials originating from external services.

2. The mere embedding of external material does not mean that the Service Provider:

   1. is its author;

   2. approves its content;

   3. guarantees its truthfulness;

   4. guarantees its availability;

   5. is responsible for actions of the external provider.

3. Availability of embedded material may depend on the decision of its owner or the external service.

§ 393. Services of external providers

1. Some ReputoNode functions may depend on services provided by third parties.

2. To the extent that a problem remains outside the Service Provider's reasonable control, the Service Provider is not liable for irregularities resulting exclusively from operation or unavailability of such an external provider, subject to mandatorily applicable law.

3. This applies in particular to services related to:

   1. hosting;

   2. email;

   3. translations;

   4. maps;

   5. embedded materials;

   6. network infrastructure;

   7. other technical services.

4. The Service Provider may take action to limit the consequences of the problem, including temporarily disabling a function or changing the provider.

§ 394. User liability for their actions

1. The User is responsible for their own actions undertaken on ReputoNode in accordance with applicable law.

2. The User may be liable for damage caused in particular by:

   1. publishing unlawful Content;

   2. infringement of intellectual-property rights;

   3. infringement of image rights;

   4. unlawful disclosure of personal data;

   5. breach of confidentiality;

   6. impersonation;

   7. fraud;

   8. manipulation of Reputation;

   9. an attack on Portal infrastructure;

   10. other actions contrary to law or the Terms.

3. Moderation of Content does not release the User from liability arising from their own actions.

§ 395. Third-party claims

1. If a User's action infringes the rights of a third party and causes liability or damage on the part of the Service Provider, the Service Provider may pursue claims against the User provided for by applicable law.

2. This applies in particular to cases of unlawful use of:

   1. another person's work;

   2. image;

   3. personal data;

   4. a trademark;

   5. a business designation;

   6. confidential information;

   7. other legally protected elements.

3. The Service Provider's claim may include compensation for damage or reimbursement of justified costs to the extent resulting from applicable law.

4. The Terms do not establish an automatic obligation to reimburse all costs incurred by the Service Provider regardless of the circumstances of the matter.

§ 396. Security of login credentials

1. The User is required to appropriately protect access to their Account.

2. In particular, the User should:

   1. keep the password confidential;

   2. not provide the password to third parties;

   3. appropriately secure their email account;

   4. secure the telephone, computer and other devices used for login;

   5. use reasonable safeguards for their own network;

   6. respond to suspected Account takeover.

3. Voluntary provision of login credentials to a third party is subject to the rules set out in the Terms.

4. The Service Provider may take into account the manner in which the User secured the Account when assessing the circumstances of a security incident.

§ 397. Unauthorised Account takeover

1. The User is not automatically liable for every action performed from their Account if it is taken over without the User's knowledge and consent.

2. The circumstances of such an event are assessed individually.

3. The assessment may take into account in particular:

   1. the manner in which the password was secured;

   2. security of the email account;

   3. security of the device;

   4. the User's conduct after detecting the incident;

   5. any voluntary disclosure of login credentials;

   6. other circumstances related to Account security.

4. The User should report suspected unauthorised access as soon as reasonably possible.

§ 398. User device, network and software

1. The Service Provider is not liable for inability to properly use ReputoNode where the problem results exclusively from circumstances on the User's side and the Portal is operating correctly.

2. This applies in particular to problems resulting from:

   1. a malfunctioning device;

   2. an unsupported or malfunctioning browser;

   3. operating-system configuration;

   4. blocking required browser functions;

   5. the internet connection;

   6. operation of the User's internet provider;

   7. malicious software on the User's device;

   8. incorrect network configuration.

3. The provisions of this paragraph do not exclude liability for an irregularity that actually results from ReputoNode.

§ 399. Actions performed by the User

1. The Service Provider is not liable for the consequence of correctly carrying out an instruction knowingly given by the User if the system operated in accordance with that instruction.

2. This applies in particular to:

   1. deletion of a Post;

   2. deletion of a Draft;

   3. change of Profile;

   4. change of followed Accounts;

   5. other operations performed at the User's request.

3. The User should exercise caution before performing an operation whose consequences may be irreversible.

§ 400. Incorrect data entered by the User

1. The User is responsible for data and choices made by the User while using the Portal.

2. This applies in particular to:

   1. selection of a Category;

   2. selection of a Post Type;

   3. indication of a Location;

   4. entering contact details;

   5. selecting the wrong material for publication;

   6. an incorrect description;

   7. other information provided independently by the User.

3. The Service Provider may correct specified elements as part of Moderation or handling a report, but is not automatically liable for a consequence resulting exclusively from the User's incorrect action.

§ 401. Automatic translations

1. Liability related to automatic translations is subject to the rules set out in Chapter 16.

2. Automatic translation is an auxiliary function and is not covered by a guarantee of complete correctness.

3. If a material error is identified, the Service Provider may:

   1. correct the translation;

   2. generate it again;

   3. correct Reactions or Reputation if the conditions set out in the Terms are met.

4. The original version of Content takes priority when determining its actual meaning.

§ 402. Reputation errors

1. Reputation is the result of operation of the mechanism described in the Terms and may be subject to changes and recalculations.

2. The mere fact that a Reputation score was for a certain period lower than the User considers correct does not automatically create a right to compensation.

3. The User may report a suspected error and request verification in accordance with the procedures set out in the Terms.

4. If an error is identified, the Service Provider may appropriately correct the system, Reactions or Reputation.

5. The provisions of this paragraph do not exclude rights arising in a specific situation from mandatorily applicable law.

§ 403. Moderation and liability for Content

1. The Service Provider does not guarantee detection of every Content item violating the law, the Terms or the Community Standards immediately after publication.

2. ReputoNode does not conduct continuous manual verification of every published Content item before making it available.

3. Failure to detect Content earlier does not mean that it has been approved.

4. After obtaining information requiring action, the Service Provider acts in accordance with applicable law and the procedures set out in the Terms.

5. The Service Provider benefits from exclusions and limitations of liability available to providers of intermediary and hosting services to the extent that the conditions arising from applicable law are met.

6. The Terms do not modify or expand the Service Provider's liability beyond the scope arising from applicable law.

§ 404. Events beyond the Service Provider's reasonable control

1. To the extent permitted by law, the Service Provider is not liable for failure to perform or delay in providing the service caused by an event beyond its reasonable control.

2. This applies in particular to:

   1. widespread failures of telecommunications infrastructure;

   2. power-grid failures;

   3. natural disasters;

   4. fire;

   5. war;

   6. riots;

   7. actions of public authorities;

   8. sudden legal changes making provision of the service impossible;

   9. other extraordinary events independent of the Service Provider.

3. The provisions of this paragraph apply only to the extent that the relevant event actually prevents or materially impedes proper provision of services.

§ 405. Duty to mitigate damage

1. The User should take reasonable actions aimed at limiting damage if they become aware of a problem related to use of ReputoNode.

2. The User should not knowingly continue conduct that obviously increases the extent of avoidable damage.

3. When assessing liability, actions taken by each party to prevent damage or limit its extent may be taken into account in accordance with applicable law.

§ 406. Nature of ReputoNode

1. ReputoNode is a social portal enabling publication, exchange and evaluation of Content.

2. ReputoNode is not intended as a professional system for:

   1. data archiving;

   2. accounting;

   3. medical services;

   4. financial services;

   5. ensuring safety of life or health;

   6. critical infrastructure;

   7. guaranteeing business continuity.

3. The User should not use ReputoNode as the sole tool for carrying out processes whose interruption could cause serious harm.

§ 407. Copies of important materials

1. The User should keep their own copies of materials whose loss would be materially significant to them.

2. ReputoNode should not be treated as the sole storage location for:

   1. important documents;

   2. original photographs;

   3. videos;

   4. professional materials;

   5. business data;

   6. other irreplaceable information.

3. Rules concerning backups on the Service Provider's side are also set out in Chapter 18.

§ 408. Disputes between Users

1. ReputoNode does not become a party to a dispute solely because Users established contact using the Portal.

2. Users are directly responsible to one another for their own obligations and actions in accordance with applicable law.

3. This applies in particular to disputes concerning:

   1. performance of services;

   2. sale of products;

   3. payments;

   4. quality of performance;

   5. infringement of personal rights;

   6. copyright;

   7. other relationships between Users.

4. The Service Provider may undertake Moderation to the extent concerning operation of the Portal, but this does not automatically mean that it assumes responsibility for resolving the entire civil dispute between the parties.

§ 409. Claims concerning damage

1. A person asserting a claim concerning damage related to ReputoNode should provide information enabling the matter to be assessed.

2. Information may concern in particular:

   1. the event alleged to have caused the damage;

   2. the time when the event occurred;

   3. the nature of the damage;

   4. the amount of the claim asserted;

   5. the link between an action or omission of ReputoNode and the alleged damage;

   6. other circumstances relevant to the matter.

3. Claims are assessed in accordance with the rules arising from applicable law.

4. The Terms do not establish a separate rule of evidence replacing rules provided by law.

5. Merely stating a specified amount of damage does not automatically mean that the Service Provider accepts it.

§ 410. Professional Users

1. Use of ReputoNode in connection with business, professional, organisational or institutional activity means use whose nature indicates that the Portal is used to pursue the objectives of such activity.

2. This applies in particular to Accounts used for:

   1. promoting business activity;

   2. presenting a company's offer;

   3. acquiring clients or counterparties;

   4. representing an organisation or institution;

   5. carrying out professional activity.

3. The mere fact that the Account owner is a natural person does not determine the consumer nature of a particular manner of using the Portal.

4. The User's status is assessed in accordance with applicable law and the actual nature of use of the service.

5. If under applicable law a person benefits from protection provided to consumers or persons covered by similar protection, the Terms do not deprive that person of such protection.

§ 411. Liability to consumers

1. In relation to consumers, the Service Provider's liability is determined taking into account mandatorily applicable consumer law.

2. The provisions of the Terms should not be interpreted as:

   1. excluding the Service Provider's statutory liability;

   2. limiting remedies available to a consumer;

   3. transferring to a consumer risk which under law cannot be transferred to them;

   4. depriving a consumer of the right to pursue claims.

3. If a limitation of liability provided for in the Terms is ineffective in relation to a consumer, the relevant provisions of law apply.

§ 412. Overriding limit on liability restrictions

1. All limitations, exclusions and reservations concerning liability contained in the Terms apply only to the extent permitted by applicable law.

2. The Terms do not exclude or limit the Service Provider's liability:

   1. in cases where the law prohibits such exclusion;

   2. for actions for which liability must be borne under mandatorily applicable law;

   3. to any other extent in which a limitation would be invalid or ineffective.

3. If a specified limitation of liability proves impermissible only in part, the remaining provisions of the Terms remain effective to the extent permitted by law.

Chapter 21

Amendments to the Terms and other documents

§ 413. Versioning of the Terms

1. The Terms are identified by a version number.

2. An effective date may be specified for each version of the Terms.

3. The current version of the Terms is publicly available on the Portal.

4. Information about the currently effective version of the Terms is maintained by the ReputoNode system.

5. The Service Provider may use a technical mechanism allowing it to determine which version of the Terms the User accepted.

§ 414. Archived versions of the Terms

1. The Service Provider is not required to provide a public archive of all previous versions of the Terms on the Portal, unless such an obligation results from law.

2. The Service Provider may retain earlier versions of documents internally to the extent necessary for:

   1. demonstrating the content that applied at a given time;

   2. resolving disputes;

   3. fulfilling legal obligations;

   4. organizational or technical purposes.

3. The absence of a public archive does not affect the obligation to make the current version of the Terms available.

§ 415. Changes not requiring renewed acceptance

1. Renewed acceptance of the Terms is not required for changes that do not cause a material change to the User's rights or obligations.

2. This applies in particular to:

   1. correcting typographical errors;

   2. correcting linguistic errors;

   3. formatting changes;

   4. numbering corrections;

   5. correcting cross-references between sections;

   6. stylistic changes;

   7. clarifying an existing rule without changing its meaning;

   8. other changes of a technical or editorial nature.

3. The Service Provider may assign a new document version number to such a change without requiring renewed acceptance if the nature of the change does not require it.

§ 416. Changes requiring renewed acceptance

1. The Service Provider may require the User to accept a new version of the Terms if the change has a material impact on rights, obligations, or the manner of using the Portal.

2. Renewed acceptance may be required in particular in the event of:

   1. introducing new material obligations for the User;

   2. introducing new material restrictions;

   3. changing the rules for providing core services;

   4. a material change to the rules concerning Content;

   5. a material change to the Moderation rules;

   6. changing the basic rules for using the Account;

   7. other changes justifying renewed acceptance.

3. Whether a given version requires renewed acceptance may be determined by the legal-document configuration used by ReputoNode.

§ 417. Mechanism for requiring new acceptance

1. ReputoNode may compare the version of the Terms accepted by the User with the version currently required.

2. If the User has not accepted the required current version, after logging in the User may be redirected to a screen informing them about the new Terms.

3. Until the required version is accepted, the User's access to ordinary Account functions may be restricted.

4. In such a case, the User may remain technically logged in, but instead of the ordinary feed or other Portal functions may be given access only to functions necessary to make a decision concerning the new version of the document.

5. The restriction referred to in paragraph 4 does not constitute deletion of the Account.

§ 418. Functions available without accepting the new version

1. The User who has not accepted the required new version of the Terms has the opportunity to review the document.

2. To the extent technically available, the User may also:

   1. log out;

   2. contact the Service Provider;

   3. initiate the Account deletion procedure;

   4. take other actions necessary to exercise their rights.

3. The User may also use public ReputoNode functions available to persons who are not logged in, if those functions do not require acceptance of the new version of the Terms.

§ 419. Failure to accept the new version

1. The User is not required to accept a new version of the Terms.

2. Failure to accept it may, however, prevent further active use of functions requiring an Account.

3. Failure to accept it does not result in automatic immediate deletion of the Account.

4. A User who does not wish to accept the new version may stop using ReputoNode and use the Account deletion procedure.

5. Until the Account deletion procedure is completed, the relevant provisions of the Terms concerning Account deletion apply.

§ 420. Information about amendments to the Terms

1. ReputoNode informs the User about the need to accept a new required version of the Terms through a mechanism available after login.

2. The Service Provider may additionally provide information about changes:

   1. by email;

   2. through a notice on the Portal;

   3. on the legal documents page;

   4. through other appropriate channels.

3. The Service Provider does not undertake to send an email about every amendment to the Terms unless the obligation to use a particular information channel results from law.

4. In the event of a material change to the terms of use, the Service Provider provides information about the change to the extent and in the manner required by applicable law.

§ 421. Effective date of changes

1. The Terms do not establish one fixed advance-notice period for all types of changes.

2. The effective date of a new version may depend on:

   1. the nature of the change;

   2. its impact on Users;

   3. obligations resulting from law;

   4. the reason for introducing the change;

   5. security considerations.

3. If the law requires information to be provided to the User with a specified or appropriate advance notice, the Service Provider applies the required rules.

§ 422. Changes requiring urgent entry into force

1. In justified cases, a change may be introduced without the standard period preceding its application or with shorter advance notice, if permitted by law.

2. This applies in particular to changes necessary due to:

   1. a change in applicable law;

   2. a legally binding order of an authority;

   3. a security threat;

   4. the need to remediate a vulnerability;

   5. preventing serious abuse;

   6. the need to prevent circumvention of safeguards;

   7. other urgent circumstances requiring a rapid response.

3. The urgent nature of a change does not exclude the User's rights arising from mandatory provisions of law.

§ 423. Reasons for amending the Terms

1. The Service Provider may amend the Terms for justified reasons.

2. A reason for a change may include, in particular:

   1. a change in law;

   2. a change in the manner in which applicable provisions are interpreted or applied;

   3. development of ReputoNode;

   4. adding new functions;

   5. changing existing functions;

   6. discontinuing specified functions;

   7. a change in technology;

   8. a change in infrastructure;

   9. increasing security;

   10. preventing abuse;

   11. a change in Moderation processes;

   12. a change in the Reputation system;

   13. an organizational change;

   14. the need to remove ambiguities or inconsistencies;

   15. adapting the document to the actual manner in which the services are provided;

   16. another justified reason connected with the operation of ReputoNode.

3. The list of reasons indicated in paragraph 2 is not exhaustive.

4. An amendment to the Terms may not be made in a manner contrary to mandatory provisions of law.

§ 424. Effects of new provisions

1. A new version of the Terms applies from its effective date.

2. As a rule, the new provisions apply to use of the Portal from the moment they enter into force.

3. Actions taken by the User before the new version enters into force are assessed under the rules applicable at the time they were taken, unless the nature of the change, applicable law, or other rules of the Terms provide otherwise.

4. An amendment to the Terms may not deprive the User of vested rights in a manner contrary to mandatory provisions of law.

§ 425. Changes to mechanisms operating on existing data

1. A change to a particular technical mechanism may also affect data or results generated earlier if this follows from the nature of that mechanism and the Terms permit it.

2. This applies in particular to:

   1. recalculation of Reputation;

   2. changes to the manner in which results are presented;

   3. changes to sorting mechanisms;

   4. Moderation changes;

   5. changes resulting from bug fixes;

   6. other mechanisms whose operation covers existing data.

3. Applying a new mechanism to existing data does not automatically mean that conduct of the User that occurred earlier is assessed as a violation under rules that were not in force at that time.

§ 426. Recording acceptance

1. ReputoNode may store information allowing it to demonstrate that the User accepted a particular version of a document.

2. Such information may include at least:

   1. the User identifier;

   2. the document type;

   3. the document version number;

   4. the date and time of acceptance.

3. ReputoNode does not require an IP address to be recorded solely as evidence of acceptance of a document.

4. ReputoNode also does not require recording the language in which the User reviewed the document solely as evidence of acceptance.

5. Detailed rules for processing data connected with document acceptance are set out in the Privacy Policy.

§ 427. Community Standards

1. The Community Standards have separate versioning.

2. The Community Standards form an integral part of the Terms.

3. A material amendment to the Community Standards that introduces new obligations, prohibitions, or restrictions of material significance to the User may require renewed acceptance of the relevant version of the documents.

4. A change that merely:

   1. adds an example;

   2. expands the description of an existing prohibition;

   3. improves the language;

   4. clarifies an already applicable rule,

5. does not have to require renewed acceptance if it does not materially change the User's rights or obligations.

6. Whether renewed acceptance is required may be determined by the legal-document configuration used in ReputoNode.

§ 428. Privacy Policy

1. The Privacy Policy is versioned separately from the Terms.

2. A new version of the Privacy Policy does not automatically mean that the User has given a new consent to the processing of personal data.

3. The Privacy Policy is informational to the extent specified by the applicable data-protection provisions.

4. If particular processing requires the User's consent, the consent is obtained separately in the manner required by law.

5. In justified cases, the Service Provider may require the User to confirm that they have reviewed a new version of the Privacy Policy.

6. Confirmation that the User has reviewed the Privacy Policy is not equivalent to consent to all processing operations described in it.

§ 429. Optional consents

1. Consents that, under the law, require a separate voluntary decision by the User are not given solely by accepting the Terms.

2. This applies in particular to consents for analytics solutions or other technologies if their use requires consent.

3. Refusal to give an optional consent may not be treated as refusal to accept the Terms.

4. The User should be able to manage optional consents in accordance with applicable law and the relevant Portal mechanisms.

§ 430. Welcome Guide and informational materials

1. The Welcome Guide and other informational materials may have their own versioning.

2. Informational materials may be changed without requiring renewed acceptance by the User if they do not independently establish new obligations or restrictions for the User.

3. Informational material may not amend the Terms or the Community Standards in a manner that does not result from the proper procedure for amending those documents.

4. In the event of a conflict between informational material and the Terms, the Terms prevail.

§ 431. Language versions of amended documents

1. ReputoNode legal documents may be made available in different language versions.

2. The Polish version of the Terms remains the source and interpretative version in accordance with the rules set out in the Terms.

3. Translations should reflect the meaning of the Polish version as faithfully as possible.

4. In the event of discrepancies between versions, the rules concerning priority of the Polish version apply, subject to the User's mandatory rights.

5. A translation error may be corrected without changing the meaning of the Polish version of the document.

§ 432. Changes to the digital service and consumer rights

1. The Service Provider may develop and modify ReputoNode in accordance with the Terms and applicable law.

2. If a change to the digital service materially and adversely affects the consumer's access to or use of the service, the Service Provider applies the information obligations and other protective measures required by applicable law.

3. The Terms do not limit the consumer's statutory rights connected with changes to the digital service.

4. The Service Provider does not establish one rigid mechanism in the Terms for all future changes if the scope of required actions depends on the law applicable at the relevant time and the nature of the specific change.

§ 433. Priority of mandatory provisions

1. An amendment to the Terms or another ReputoNode document may not effectively exclude rights of which the User may not be deprived under applicable law.

2. If the manner of introducing a particular change is subject to specific legal requirements, those requirements take precedence over the general rules set out in this Chapter.

3. The provisions of this Chapter should be interpreted taking into account mandatory provisions concerning, in particular, digital services, intermediary services, consumer protection, and personal-data protection.

Chapter 22

Duration and termination of the Agreement

§ 434. Conclusion and duration of the Agreement

1. The Agreement between the User and the Service Provider is concluded after successful completion of the Account registration and activation process in accordance with the rules set out in the Terms.

2. Merely submitting the registration form and creating a technically inactive Account does not yet constitute conclusion of the Agreement.

3. The Agreement is concluded after successful confirmation of the email address and activation of the Account.

4. The Agreement is concluded for an indefinite period.

5. Use of public Portal functions available without an Account does not in itself result in conclusion of an Agreement concerning maintenance of an Account.

§ 435. Termination of the Agreement by the User

1. The User may at any time and without giving a reason initiate the ordinary procedure for terminating the Agreement by submitting a request to delete the Account.

2. No additional notice period applies to ordinary termination of the Agreement by the User beyond the 30-day waiting period provided for the Account deletion procedure.

3. During the waiting period, the Agreement remains in force to the limited extent specified in Chapter 17.

4. The User may cancel the Account deletion procedure before final deletion is carried out.

5. If the procedure is successfully cancelled, the Agreement remains in force without the need to conclude it again.

6. If the procedure is not cancelled, the Agreement is terminated upon final deletion and anonymization of the Account.

7. Paragraphs 1–6 concern ordinary termination of the Agreement by the User and do not limit the Consumer's statutory right to withdraw from the Agreement if such a right is available under the applicable provisions.

8. A Consumer who has a statutory right to withdraw from a distance Agreement may withdraw from it within 14 days from the date of conclusion of the Agreement, without giving a reason, by making an unequivocal statement:

   1. by email to contact@reputonode.com; or
   2. by correspondence to the Service Provider's address indicated in Chapter 3.

9. The time limit is met if the statement is sent before it expires. The Consumer may use the model form constituting Appendix No. 1 to the Terms, but this is not mandatory.

10. Effective statutory withdrawal from the Agreement is independent of the ordinary 30-day Account deletion procedure and has the effects specified by applicable law.

11. After receiving an effective statement of withdrawal, the Service Provider may immediately block access to the Account and handles Content, data, and other Account elements in accordance with the applicable provisions. The rules for ordinary Account deletion apply only to the extent consistent with the effects of statutory withdrawal.

12. If the Consumer submits a statement of withdrawal using an electronic mechanism made available by the Portal, the Service Provider sends confirmation of its receipt on a durable medium if required by law.

13. The provisions concerning the statutory right of withdrawal apply only where, in the specific relationship, the User has Consumer status, the Service Provider acts as a trader, and the applicable provisions do not exclude application of that right.

§ 436. No obligation to give a reason

1. The User is not required to justify the decision to stop using ReputoNode.

2. The Service Provider may not make initiation of the ordinary Account deletion procedure conditional on the User providing a reason for leaving.

3. The User may voluntarily provide information about the reasons for leaving if the Portal provides such an option.

§ 437. Termination of the Agreement by the Service Provider due to a violation

1. The Service Provider may terminate the Agreement with the User in the event of serious or repeated violation of:

   1. the Terms;

   2. the Community Standards;

   3. applicable law;

   4. Portal security rules.

2. The Agreement may be terminated in particular where the User:

   1. repeatedly publishes prohibited Content;

   2. commits serious abuse;

   3. manipulates the Reputation system;

   4. uses the Portal for fraud;

   5. impersonates other persons or entities;

   6. seriously infringes the rights of other persons;

   7. attacks the Portal infrastructure;

   8. uses the Account for unlawful activity;

   9. circumvents previous restrictions or blocks;

   10. otherwise materially violates the terms of use of ReputoNode.

3. Termination of the Agreement for Moderation-related reasons is one of the possible Moderation measures.

§ 438. Particularly serious violation

1. In the event of a particularly serious violation, the Service Provider may terminate the Agreement with immediate effect.

2. A prior warning is not required if the nature of the violation justifies immediate action.

3. This applies in particular to cases involving:

   1. a serious criminal offence;

   2. a direct threat to the safety of persons;

   3. sexual exploitation of minors;

   4. serious fraud;

   5. terrorist activity;

   6. an attack on the Portal infrastructure;

   7. a serious data-security breach;

   8. deliberate circumvention of a permanent ban;

   9. another violation whose nature makes continued provision of the service reasonably impossible.

§ 439. Less serious and repeated violations

1. In the case of less serious violations, the Service Provider may apply a less severe Moderation measure before terminating the Agreement.

2. Such a measure may include in particular:

   1. a warning;

   2. removal or restriction of Content;

   3. temporary restriction of Account functions;

   4. a temporary suspension;

   5. another proportionate action.

3. The Service Provider is not required to issue a specified number of warnings before terminating the Agreement.

4. When selecting a measure, the Moderation rules set out in Chapter 13 are taken into account.

§ 440. Impossibility of continuing to provide the service

1. The Service Provider may also terminate the Agreement with a particular User where continued provision of the service to that User is impossible or impermissible.

2. A reason may include in particular:

   1. a legally binding order or decision of a competent authority;

   2. an obligation resulting from law;

   3. a permanent technical impossibility of providing the service to that User;

   4. the need to protect the security of the Portal or other persons;

   5. another situation in which continued maintenance of the Account would be unlawful or objectively impossible.

3. Where circumstances permit, the Service Provider informs the User of the reason for termination of the Agreement in accordance with applicable law.

§ 441. Permanent Account ban and termination of the Agreement

1. A permanent Account ban imposed by the Service Provider means the end of the ability to continue using that Account and may lead to termination of the Agreement.

2. A permanent ban and termination of the Agreement are not treated as two separate mandatory stages of proceedings.

3. If a Moderation Decision provides for permanent termination of access to the Account, the Service Provider may simultaneously terminate the Agreement.

4. The User has no right to create a new Account in order to circumvent such termination if the ban includes a prohibition on using the Portal again.

§ 442. No 30-day period upon termination due to a violation

1. If the Agreement is terminated by the Service Provider due to a violation of the Terms, the User is not automatically entitled to the 30-day cancellation period provided for voluntary Account deletion.

2. The Account may be restricted or blocked before final deletion or anonymization of data.

3. The timing of technical deletion or anonymization of the Account may depend on:

   1. the nature of the violation;

   2. ongoing Moderation proceedings;

   3. an appeal;

   4. the need to preserve evidence;

   5. legal obligations;

   6. security needs;

   7. technical processes.

4. Termination of the Agreement does not mean that all data must immediately be physically deleted from every technical system.

§ 443. Content after termination of the Agreement by the Service Provider

1. The manner in which the User's Content is handled after termination of the Agreement by the Service Provider depends on the reason for termination and the nature of the individual Content.

2. Content may in particular:

   1. remain publicly available after anonymization of the author;

   2. be partially removed;

   3. be hidden;

   4. be completely removed.

3. The Service Provider may in particular remove Content that:

   1. violates the law;

   2. violates the Terms or the Community Standards;

   3. forms part of abuse;

   4. creates a threat;

   5. should be removed for another justified reason.

4. The mere fact that the Agreement with the User has been terminated does not necessarily result in automatic removal of all of the User's earlier lawful Content.

5. The provisions concerning anonymization, licensing, copyright, and Reputation apply accordingly to Content that remains.

§ 444. Information about termination of the Agreement by the Service Provider

1. If the Service Provider terminates the Agreement or permanently bans the Account in connection with the User's Content or a violation of the terms of use, it informs the User about the decision and its basic reasons to the extent required by applicable law.

2. The information may include in particular:

   1. identification of the measure applied;

   2. the basis for the decision;

   3. identification of the violation;

   4. the scope of consequences for the Account;

   5. information about the available appeal procedure.

3. As a rule, the information is sent to the email address associated with the Account or by another available electronic means.

4. The information may not be provided, or its scope may be limited, in cases specified by law or by the security rules described in Chapter 13.

§ 445. Appeal against termination of the Agreement for Moderation-related reasons

1. The User may challenge termination of the Agreement resulting from a Moderation Decision under the rules set out in Chapter 13.

2. Following reconsideration of the matter, the decision may be:

   1. upheld;

   2. changed;

   3. revoked.

3. If termination is revoked before irreversible technical processes are carried out, the Service Provider may restore the Account or its functions to the appropriate extent.

4. The technical possibility of restoring particular data depends on the state of the system at the time the decision is changed.

§ 446. No ordinary termination by the Service Provider without cause

1. ReputoNode is operated with the intention of enabling Users to use the Portal on a long-term basis.

2. The Service Provider does not envisage routinely terminating individual Agreements with active Users without a justified reason.

3. The Terms do not establish a general fixed notice period for termination of the Agreement by the Service Provider.

4. Paragraph 2 does not limit the possibility of terminating the Agreement in the cases specified in the Terms, in particular:

   1. due to violations;

   2. due to the impossibility of continuing to provide the service;

   3. due to legal requirements;

   4. due to termination of operation of the entire Portal.

5. The User's rights arising from mandatory provisions remain unaffected.

§ 447. Complete termination of ReputoNode operations

1. Complete and permanent termination of ReputoNode operations results in termination of Agreements with Users in connection with discontinuation of the services.

2. The rules concerning technical closure of the Portal and deletion of data are set out in Chapter 18.

3. In the event of complete closure of ReputoNode, the Service Provider may delete Accounts and Content in accordance with the rules set out in the Terms and applicable law.

4. The Service Provider is not required to continue maintaining Public Content after complete termination of the Portal's operation.

§ 448. Data after termination of the Agreement

1. Termination of the Agreement does not impose an obligation on the Service Provider to continue storing the User's data unless:

   1. such an obligation results from law;

   2. retention of the data is necessary to comply with a legally binding request from an authority;

   3. there is another legally justified basis for retaining it.

2. The Service Provider may delete or anonymize data after termination of the Agreement in accordance with the Terms, the Privacy Policy, and applicable law.

3. Data retained on a specific legal basis may be stored only to the extent and for the period justified by that basis.

4. The mere fact that an Account previously existed does not constitute a basis for indefinitely retaining all User data.

§ 449. Provisions applicable after termination of the Agreement

1. Termination of the Agreement does not automatically cause the expiry of provisions that, by their nature, should also apply after the User has stopped using the Portal.

2. This applies in particular to provisions concerning:

   1. Content that remains;

   2. the license necessary to use Content that remains;

   3. intellectual property rights;

   4. liability for earlier actions;

   5. existing claims;

   6. effects of Reactions;

   7. Moderation history;

   8. security;

   9. handling of ongoing disputes and Reports.

3. These provisions remain applicable only to the extent justified by their nature and by applicable law.

4. This section does not create an obligation to retain data for which there is no appropriate basis for further storage.

§ 450. Prohibition on transfer of the Account and Agreement by the User

1. The User may not transfer their Account to another person.

2. The User may not, without the Service Provider's consent, transfer to another person their status as a User arising from the Agreement.

3. In particular, it is prohibited to:

   1. sell the Account;

   2. transfer the Account to another person;

   3. transfer Reputation by transferring the Account;

   4. transfer access to the Account, for consideration or free of charge, for the purpose of changing its actual owner.

4. This rule does not exclude use of an entity's Account by a person duly authorized to represent that entity.

§ 451. Change of the entity operating ReputoNode

1. In the future, ReputoNode may be operated by an entity other than the current Service Provider.

2. Such a change may occur in particular in connection with:

   1. commencement of business activity by the Service Provider;

   2. establishment of a company;

   3. contribution of the Portal to another entity;

   4. reorganization of the activity;

   5. sale or other lawful transfer of the activity connected with ReputoNode.

3. In the event of a change of the entity operating the Portal, rights and obligations connected with the Agreements may be transferred to the new entity only to the extent and in the manner permitted by applicable law.

4. The change of entity may not result in depriving the User of rights that cannot lawfully be excluded or limited.

5. If the change requires Users to be informed, a particular consent to be obtained, the Terms to be amended, information concerning the data controller to be provided, or other legal obligations to be fulfilled, the Service Provider fulfills those obligations before or in connection with the change.

6. The new entity may become the Service Provider of ReputoNode after meeting the requirements arising from applicable law.

§ 452. Continuity of Accounts after a change of Service Provider

1. If the change of the entity operating ReputoNode is carried out in accordance with law, Users' Accounts may continue to function without the need to recreate them technically from the beginning.

2. In such a case, the following may in particular be retained:

   1. Profiles;

   2. Posts;

   3. Comments;

   4. Replies;

   5. Reputation;

   6. Reactions;

   7. Following relationships;

   8. other data necessary to maintain continuity of the service.

3. Retention of data and any transfer of it to the new entity requires an appropriate legal basis.

4. Information concerning the processing of personal data in connection with a change of the entity operating the Portal is provided in accordance with the applicable provisions and the Privacy Policy.

§ 453. Priority of law

1. The provisions concerning termination, ending, or transfer of the Agreement apply only to the extent consistent with applicable law.

2. The Terms do not limit consumer rights or other User rights that cannot effectively be excluded.

3. If the law requires an additional procedure, information, time limit, or consent for a particular method of terminating or transferring the Agreement, the relevant provisions of law apply.

Chapter 23

Governing law, consumers, and dispute resolution

§ 454. Governing law

1. Polish law applies to the Terms, the Agreement, and legal relationships connected with use of ReputoNode, subject to mandatory provisions of law applicable in a given situation.

2. The choice of Polish law does not deprive a consumer of protection granted by provisions that cannot be excluded by agreement and that would apply under the applicable rules of private international law.

3. The rule set out in paragraph 1 also applies to Users using ReputoNode in connection with business, professional, organizational, or institutional activity, unless applicable law provides otherwise.

4. The provisions of this section should not be interpreted as excluding application of mandatory provisions applicable to a particular User or a particular legal relationship.

§ 455. Consumer protection

1. A Consumer enjoys the rights granted by mandatory provisions of law.

2. The Terms are not intended to limit or exclude consumer rights that cannot effectively be limited or excluded by agreement.

3. If a particular provision of the Terms provides the Consumer with less protection than a mandatory provision applicable in the Consumer's situation, the relevant provision of law applies.

4. Application of a provision affording the Consumer greater protection does not in itself render the remaining provisions of the Terms invalid.

§ 456. Amicable resolution of disputes

1. If a dispute arises between the User and the Service Provider, the parties may attempt to resolve it amicably.

2. Before referring the matter to court, the User may contact the Service Provider at the address indicated in Chapter 3 and present the circumstances of the matter and the expected manner of resolving it.

3. The Service Provider may attempt to clarify the matter and find a solution acceptable to the parties.

4. An attempt at amicable dispute resolution is not a mandatory condition for referring the matter to court unless a specific obligation results from mandatory provisions of law.

5. Use of the complaint procedure or an attempt at amicable dispute resolution does not deprive the User of the right to use other legal remedies.

§ 457. Out-of-court resolution of consumer disputes

1. A Consumer may use mechanisms for out-of-court resolution of consumer disputes available under applicable law.

2. The possibility of using a particular procedure, the jurisdiction of the entity conducting such a procedure, and the conditions for initiating it result from applicable law.

3. The Service Provider does not declare in the Terms a standing and unconditional consent to participate in all voluntary proceedings concerning out-of-court resolution of consumer disputes.

4. If the law applicable to a particular matter requires the Service Provider to state its position regarding participation in such proceedings, the Service Provider provides the required position in accordance with those provisions.

5. If the Service Provider decides to participate in a particular proceeding or its participation is required by law, it provides the Consumer with the required information concerning the competent authorized entity.

6. The absence of a general declaration of participation in out-of-court proceedings does not limit the Consumer's rights arising from applicable law.

§ 458. Position after an unresolved consumer complaint

1. If, after a Consumer complaint has been considered, the dispute remains unresolved and applicable law requires information concerning out-of-court dispute resolution to be provided to the Consumer, the Service Provider fulfills that obligation in the required form.

2. In such a case, the Service Provider may, in accordance with applicable law:

   1. agree to participate in the relevant out-of-court proceeding;

   2. declare an intention to submit the relevant application;

   3. refuse to participate in voluntary proceedings where the law permits such refusal.

3. The decision referred to in paragraph 2 may be made individually for a particular dispute.

4. If the law requires identification of the competent entity authorized to conduct the proceeding, such information is provided to the Consumer in accordance with applicable law.

§ 459. No designation of a single permanent out-of-court entity

1. The Terms do not designate one entity competent for all possible consumer disputes concerning ReputoNode.

2. The competent out-of-court dispute-resolution entity may depend on:

   1. the nature of the dispute;

   2. the status of the parties;

   3. the scope of competence of individual entities;

   4. the provisions in force when the dispute arises.

3. If identification of a particular entity is required by law, the Service Provider provides the relevant information to the extent required in the particular matter.

§ 460. Assistance available to the Consumer

1. A Consumer may use the assistance of institutions and entities dealing with consumer-rights protection to the extent provided by applicable law.

2. This may include in particular assistance from:

   1. a municipal or district consumer ombudsman;

   2. competent public-administration authorities;

   3. consumer organizations;

   4. entities authorized to conduct out-of-court dispute resolution;

   5. other institutions competent in view of the subject matter of the case.

3. The Terms do not limit the Consumer's right to seek independent legal assistance.

§ 461. Right of access to a court

1. The User has the right to pursue claims before the competent court under the rules laid down by applicable law.

2. Use of:

   1. a complaint;

   2. contact with the Service Provider;

   3. an attempt at amicable dispute resolution;

   4. an out-of-court method of dispute resolution

3. does not exclude the right to refer the matter to court unless applicable law provides otherwise with respect to a specific mechanism voluntarily selected after the dispute has arisen.

4. The Terms do not establish mandatory arbitration or mandatory out-of-court dispute resolution as a condition for access to a court.

§ 462. Court jurisdiction in consumer matters

1. In matters concerning consumers, court jurisdiction is determined in accordance with applicable national law and, where relevant, European Union law.

2. The Terms do not impose on the Consumer the exclusive jurisdiction of the court of the Service Provider's place of residence if this would conflict with the jurisdiction rules available to the Consumer.

3. If, under applicable law, the Consumer may pursue claims before the court of the Consumer's place of residence or another competent court, the Terms do not limit that right.

4. The Service Provider pursues claims against a Consumer before the court competent under applicable law.

§ 463. Court jurisdiction in relation to Professional Users

1. In disputes with a User using ReputoNode in connection with business, professional, organizational, or institutional activity, insofar as applicable law permits such an agreement to be made effectively, the court with territorial jurisdiction is the court competent for the Service Provider's place of residence or registered office.

2. Paragraph 1 does not apply if:

   1. specific provisions provide for different jurisdiction that the parties may not alter;

   2. the User benefits from protection that excludes application of such a provision;

   3. the agreement on court jurisdiction would be ineffective for another reason.

3. The User's status and the possibility of applying paragraph 1 are assessed according to the actual nature of the legal relationship and the applicable provisions, not solely on the basis of the Account name.

§ 464. Disputes between Users

1. The Service Provider is not a court, arbitrator, or authority appointed to resolve private disputes between Users.

2. Users may independently attempt to resolve a dispute amicably.

3. In the event of a dispute between Users, the Service Provider may take actions concerning the operation of ReputoNode, in particular as part of:

   1. Moderation;

   2. security;

   3. enforcement of the Terms;

   4. performance of obligations resulting from law.

4. A Moderation action taken by the Service Provider does not constitute resolution of all civil, criminal, administrative, or other claims existing between the persons concerned.

5. Likewise, the absence of a Moderation action does not determine that one person bears no liability toward another under applicable law.

§ 465. Disputes concerning third-party rights

1. Moderation carried out by ReputoNode does not replace a determination by a competent court or authority.

2. This applies in particular to disputes concerning:

   1. copyright;

   2. trademarks;

   3. image rights;

   4. personal rights;

   5. personal data;

   6. trade secrets;

   7. ownership;

   8. performance of agreements;

   9. other third-party rights.

3. The Service Provider may take a Moderation action before a dispute is finally resolved by a court or authority if this is justified by the Terms, security, or applicable law.

4. A Moderation Decision concerns the operation of Content or an Account within ReputoNode and does not in itself determine the ultimate existence or scope of the parties' rights outside the Portal.

§ 466. Court judgments and decisions of authorities

1. The Service Provider complies with legally binding judgments, decisions, orders, and other determinations of competent courts or authorities to the extent required by applicable law.

2. Compliance with such a determination may include in particular:

   1. removal of Content;

   2. restriction of access to Content;

   3. preservation of data;

   4. provision of information to an authorized authority;

   5. restriction of an Account;

   6. another action required by the content of the binding determination.

3. The Service Provider is not required to comply with a request from a private person solely because that person claims to hold a particular right if the request has no appropriate basis in the Terms or applicable law.

§ 467. Decisions concerning personal data

1. Matters concerning personal-data protection are governed by the applicable data-protection provisions and the rules set out in the Privacy Policy.

2. Use of procedures provided for in the Terms does not limit the data subject's right to use the remedies provided by applicable law.

3. If a competent data-protection authority issues a binding decision or order against the Service Provider, the Service Provider complies with it to the extent required by law.

§ 468. Invalidity or ineffectiveness of part of the Terms

1. If a particular provision of the Terms proves invalid, ineffective, or unenforceable, this does not automatically make the entire Terms invalid or ineffective.

2. The remaining provisions remain in force to the extent that they may continue to apply in accordance with law.

3. The relevant provisions of applicable law apply in place of a provision that cannot be effectively applied.

4. If only part of a particular provision is ineffective, the remaining part may be applied to the extent permitted by law, provided its lawful meaning can be preserved.

§ 469. Priority of mandatory User rights

1. No provision of the Terms may be interpreted as depriving the User of a right that, under applicable law, cannot effectively be excluded or limited.

2. If an applicable provision grants a Consumer or another protected User a right more favorable than that resulting from the Terms, the relevant provision of law applies.

3. Application of such a provision does not automatically render the remaining provisions of the Terms ineffective.

§ 470. Overriding principles of dispute resolution

1. The parties should, where reasonable in the circumstances of the case, seek to clarify the dispute without unnecessary escalation.

2. Voluntary resolution of a dispute may not, however, result in depriving the User of rights arising from mandatory provisions.

3. No provision of this Chapter:

   1. limits the statutory right of access to a court;

   2. establishes mandatory arbitration;

   3. requires a Consumer to waive jurisdiction rules available to them;

   4. deprives a Consumer of protection arising from the law applicable under mandatory provisions;

   5. obliges the Service Provider to participate in every voluntary out-of-court proceeding unless such an obligation results from law or from a decision made by the Service Provider in the particular matter.

4. Matters not regulated by the Terms are governed by the applicable provisions of law.

Chapter 24

Final provisions

§ 471. Entry into force of the Terms

1. The Terms enter into force on: <uzupełnij>[DATA WEJŚCIA W ŻYCIE REGULAMINU].

2. The current version of the Terms is identified by a version number and an effective date.

3. The effective date corresponds to the actual moment from which a given version of the Terms applies to the provision of services covered by the Terms.

§ 472. Availability of the Terms

1. The Terms are made publicly available free of charge on ReputoNode.

2. The Terms are made available before conclusion of the Agreement in a manner enabling the User to review their content.

3. The Terms should be available in a manner that allows the User to obtain, store, and subsequently reproduce them using the ordinary functions of the ICT system used by the User.

4. ReputoNode does not have to provide a separate button for downloading the Terms in PDF format if the manner in which they are made available allows the User to save their content using standard device or browser capabilities.

5. The User may retain their own copy of the Terms.

§ 473. ReputoNode documents

1. The basic rules for using ReputoNode are set out in:

   1. the Terms;

   2. the Community Standards, which form an integral part of the Terms.

2. The Privacy Policy is a separate informational document concerning, in particular, the rules for processing personal data.

3. The Welcome Guide and other informational or supporting materials are intended to make it easier to use ReputoNode and understand its functions.

4. Informational materials may not independently change rights or obligations arising from the Terms.

§ 474. Hierarchy of rules

1. The following hierarchy applies to use of ReputoNode:

   1. mandatory provisions of law;

   2. the Terms;

   3. the Community Standards;

   4. the Welcome Guide and other informational or supporting materials.

2. In the event of a conflict between the Terms and the Community Standards, the Terms prevail.

3. The Community Standards expand upon and clarify the rules set out in the Terms, in particular those concerning Content and User conduct.

4. Neither the Welcome Guide nor any other supporting material may limit rights arising from the Terms.

§ 475. Privacy Policy and the Terms

1. The Privacy Policy is not a document subordinate to the Terms in the same way as supporting materials because it concerns a separate legal area connected with the processing of personal data.

2. The rules for processing personal data should be assessed in accordance with the Privacy Policy and the applicable provisions on personal-data protection.

3. The Terms and the Privacy Policy should be interpreted in a manner that allows them to be applied consistently.

4. No provision of the Terms may limit data-subject rights arising from mandatory provisions on personal-data protection.

§ 476. Meaning of headings and structure

1. Chapter titles, section headings, and other structural elements of the Terms are primarily intended to facilitate reading and use of the document.

2. A title or heading alone should not be interpreted in a manner that changes the meaning of the content of a particular provision.

3. The meaning of a provision is determined primarily on the basis of its content, context, and applicable law.

§ 477. No waiver of rights

1. Failure by the Service Provider to exercise a particular right in a specific situation does not automatically constitute a waiver of that right for the future.

2. Failure to apply a particular measure to one violation does not mean that such conduct becomes permitted.

3. Application of a less severe measure in a particular matter does not oblige the Service Provider to apply an identical measure in every later matter.

4. Each situation may be assessed taking into account its individual circumstances, the principles of proportionality, and applicable law.

5. The provisions of this section do not entitle the Service Provider to act unlawfully or to engage in prohibited unequal treatment of Users.

§ 478. Individual exceptions

1. Granting an individual User an exception from a particular rule does not automatically create a right to the same exception for other Users.

2. An exception may result in particular from:

   1. special circumstances of the matter;

   2. technical reasons;

   3. security considerations;

   4. the need to fulfill a legal obligation;

   5. correcting an earlier error;

   6. other justified circumstances.

3. An individual exception does not amend the Terms for all Users unless the Service Provider makes an appropriate amendment to the Terms.

§ 479. New ReputoNode functions

1. ReputoNode may be developed by adding new functions and services.

2. A new function may be covered by the current Terms from the moment it is made available if its nature falls within the existing rules and does not require introduction of new material rights or obligations for the User.

3. Merely indicating in the Terms the possibility of introducing a particular function in the future does not constitute an obligation of the Service Provider to launch it.

4. The Service Provider may:

   1. abandon a planned function;

   2. change its scope before launch;

   3. replace it with another solution;

   4. launch it only for some Users;

   5. conduct tests of it;

   6. postpone its implementation.

5. The User does not acquire a right to a future function solely because the possibility of introducing it was described in the Terms or another ReputoNode material.

§ 480. Additional terms for new services

1. If the nature of a new service or function requires additional rules to be specified, the Service Provider may introduce specific terms, additional conditions, or another appropriate document.

2. Additional rules may concern in particular future:

   1. paid services;

   2. advertising systems;

   3. a marketplace;

   4. intermediation services;

   5. APIs;

   6. tools for businesses;

   7. other functions not fully covered by the current Terms.

3. Introduction of additional terms does not mean that the Service Provider is obliged to launch any of the services listed in paragraph 2.

§ 481. Relationship between the main Terms and specific terms

1. If specific terms or additional conditions are introduced for a particular function or service, they apply together with these Terms.

2. Specific terms take precedence over these Terms only with respect to matters concerning the particular function or service that they regulate differently.

3. In all other respects, these Terms apply.

4. Specific terms may not effectively exclude User rights arising from mandatory provisions of law.

§ 482. Non-exhaustive lists

1. Where the Terms use expressions such as:

   1. “in particular”;

   2. “among other things”;

   3. “may include”;

   4. “including”;

   5. other expressions indicating that a list is illustrative,

2. the relevant list is not exhaustive unless the wording of the provision expressly indicates otherwise.

3. The non-exhaustive nature of a list should not be interpreted as authorizing expansion of the User's obligations in a manner contrary to the essence of the Terms, their other provisions, or applicable law.

§ 483. Matters not regulated

1. Matters not regulated by the Terms are governed by the applicable provisions of law.

2. The absence of detailed regulation of a particular situation in the Terms does not mean that the following cease to apply:

   1. applicable provisions of law;

   2. rules resulting from the nature of the relevant service;

   3. applicable provisions of other parts of the Terms.

3. The provisions of the Terms should be interpreted as a whole, taking into account the interrelationships between individual Chapters.

§ 484. Source version of the Terms

1. The Polish version of the Terms is the source and interpretative version.

2. ReputoNode may also make the Terms available in other language versions.

3. Translations are intended to enable Users to review the Terms in other languages.

4. In the event of discrepancies between a translation and the Polish version, the rules set out earlier in the Terms concerning language versions and mandatory provisions protecting the User apply.

§ 485. Information about the version of the Terms

1. Each effective version of the Terms has an identifier allowing it to be identified.

2. Information concerning this version:

   Terms version: 1.0
   Effective date: <uzupełnij>[DATA WEJŚCIA W ŻYCIE REGULAMINU]

3. The rules for amending and versioning the Terms are set out in Chapter 21.

4. The indicated date is the effective date of the relevant version, not merely the date on which the file was technically created or last edited.

Appendix No. 1

Model withdrawal form

This form should be completed and sent only if the User has a statutory right to withdraw from the Agreement and wishes to exercise that right.

Addressee:
Damian Urbański
[[UZUPEŁNIJ: finalne dane adresowe Administratora / Usługodawcy wymagane do publikacji]]
contact@reputonode.com

I/We hereby give notice that I/We withdraw from the Agreement for the provision of ReputoNode services connected with maintenance of the Account.

• Username: ........................................................
• Email address assigned to the Account: ........................................................
• Date of conclusion of the Agreement / Account activation: ........................................................
• Consumer's full name: ........................................................
• Consumer's address: ........................................................
• Date: ........................................................
• Consumer's signature – only if this form is submitted on paper: ........................................................