LegalGEსარჩევი
Legal Sandbox Georgia LLC
Document Type: Function Rulebook (Binding) Version: 1.1 Effective Date: 13 May 2026 Document Language: English (Georgian version prevails in case of conflict) Status: Binding contract, incorporated by reference into all applicable Role Terms and Conditions
This Posting Function Rulebook ("Rulebook") establishes the rules governing the creation, submission, moderation, publication, modification, and removal of Posts on the legal.ge platform operated by Legal Sandbox Georgia LLC, Registration Number 405713768 (the "Platform").
This Rulebook is a binding part of the Terms and Conditions of every role permitted to create, moderate, or interact with Posts. By creating, submitting, publishing, reacting to, reporting, or otherwise interacting with any Post on the Platform, You agree to be bound by this Rulebook.
In the event of any conflict between this Rulebook and a specific Role Terms and Conditions document, the Role Terms and Conditions prevail with respect to that role's specific obligations not addressed in this Rulebook; this Rulebook prevails on matters of Posting workflow, permissions, and rules common to all roles.
1.1.1 This Rulebook provides a single authoritative source of truth governing the Posting function on the Platform.
1.1.2 This Rulebook serves to:
(a) Define the lifecycle of all Posts;
(b) Establish role-based permissions for creating, editing, moderating, and consuming Posts;
(c) Allocate ownership, intellectual property rights, and liability for Posts;
(d) Govern reader interactions including reactions and reports;
(e) Ensure consistency across all Role Terms and Conditions referencing Posting.
1.2.1 This Rulebook applies to:
(a) All Posts in any status (Draft, Pending, Published, Archived);
(b) All Users with permissions to create, moderate, or interact with Posts;
(c) All language versions of Posts (Georgian, English, Russian);
(d) All Platform surfaces where Posts are displayed (the /news blog page, organization news-feeds, search results, and external syndication).
1.2.2 This Rulebook does NOT govern:
(a) Comments or discussion features (none in v1.0; reserved for future);
(b) Internal visibility scopes for organizations (governed by separate document);
(c) Author donation features (reserved for future);
(d) Paid promotion or commercial featuring (reserved for future commercial strategy);
(e) Comments or feedback mechanisms outside the defined Reactions system.
1.3.1 This Rulebook directly affects the following roles:
| Role | Capability Type |
|---|---|
| Author | Creator (primary) |
| Solo Specialist | Creator |
| Company Specialist | Creator (with Company attribution) |
| Company | Creator (organizational) |
| Organization | Creator (limited scope — see Article 6) |
| Trainer | Creator (when also Author/Specialist) |
| Moderator | Reviewer / Enforcer |
| User | Reader / Reactor / Reporter |
1.3.2 Each affected Role's Terms and Conditions must reference this Rulebook by incorporation.
2.1 Capitalized terms used but not defined in this Rulebook have the meanings given in the applicable Role Terms and Conditions or in the Platform's master Terms and Conditions.
2.2 For purposes of this Rulebook:
"Archived" means a Post that has been removed from public visibility but remains in Platform records, recoverable subject to Article 9.
"Author" means any User with permissions to create Posts, including users holding the formal Author role and Specialists, Company Specialists, Companies, Organizations, and Trainers exercising posting permissions.
"Content Policy" means the Platform's internal standards governing what may and may not be published, as referenced in Article 10.
"Draft" means a Post that has been created but not submitted for review or directly published.
"Featured Position" means a prominent display position (numbered 1 through 10) on the /news page, assigned at the Platform's sole discretion.
"Function Rulebook" means a binding rules document, including this Rulebook, governing a specific Platform function and incorporated by reference into Role Terms and Conditions.
"News-Feed" means an Organization's dedicated content stream displayed on the Organization's profile, distinct from the public /news blog page.
"Pending" means a Post that has been submitted for moderation review but not yet approved.
"Post" means any blog post, article, news item, or news-feed entry created on the Platform, including all associated metadata, media, and translations.
"Published" means a Post that has been approved (or directly published by a Trusted Author or Organization news-feed creator) and is publicly visible.
"Reaction" means a reader's expression of feedback on a Post using one of the six defined reaction types in Article 7.
"Report" means a reader's formal complaint regarding a Post, submitted through the Platform's reporting mechanism, governed by Article 8.
"Trusted Author" means a User who has achieved the trust threshold defined in Article 5 and is permitted to publish directly without moderation review.
"Violation" means a confirmed breach of this Rulebook, the Content Policy, or applicable law, as determined by the Platform.
3.1.1 The following table defines what each role may do with respect to Posts. Detailed conditions are found in subsequent Articles.
| Capability | User | Author | Trusted Author | Solo Spec. | Co. Spec. | Company | Organization | Moderator |
|---|---|---|---|---|---|---|---|---|
| Create Draft | ❌ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | Platform-only |
| Submit for Review | ❌ | ✅ | N/A | ✅ | ✅ | ✅ | ✅ (blog only) | N/A |
| Publish Directly | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | ✅ (news-feed only) | ✅ |
| Edit own Draft | ❌ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | N/A |
| Edit own Pending | ❌ | ❌ | N/A | ❌ | ❌ | ❌ | ❌ | N/A |
| Edit own Published | ❌ | ✅ (→ Pending) | ✅ (stays Published) | ✅ (→ Pending) | ✅ (→ Pending) | ✅ (→ Pending) | ✅ | N/A |
| Delete own Draft | ❌ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | N/A |
| Delete own Pending | ❌ | ✅ | N/A | ✅ | ✅ | ✅ | ✅ | N/A |
| Delete own Published | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | N/A |
| Edit others' Posts | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | Metadata only |
| Approve / Reject | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ✅ |
| Edit body / title / excerpt | Self only | Self only | Self only | Self only | Self only | Self only | Self only | ❌ |
| Edit SEO / OG / slug | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ✅ |
| Assign category | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ✅ |
| Assign Featured Position | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ✅ |
| Archive any Post | ❌ | Own only | Own only | Own only | Own only | Own only | Own only | ✅ Any |
| Restore Archived | ❌ | Request only | Request only | Request only | Request only | Request only | Request only | ✅ |
| Use translation tool | ❌ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
| React to Posts | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
| Report Posts | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
3.1.2 "Moderator" in this table includes SUPER_ADMIN, who has identical capabilities for the Posting function.
3.1.3 Where multiple roles apply to the same person (e.g., a User who is also a Solo Specialist), the most permissive applicable capability governs, except that Trusted Author status, when held, governs all that person's posting activity across roles per Article 5.
4.1.1 Every Post moves through one or more of the following statuses:
DRAFT → PENDING → PUBLISHED → ARCHIVED
(skip if Trusted Author or Organization news-feed)
4.1.2 Status definitions:
| Status | Visibility | Description |
|---|---|---|
| Draft | Private (creator only) | Work in progress; not yet submitted |
| Pending | Private (creator + moderators) | Submitted, awaiting moderation |
| Published | Public | Live and visible to all readers |
| Archived | Hidden | Removed from public view; retained per Article 9 |
4.2.1 A Post enters Draft status when initially created.
4.2.2 While in Draft:
(a) Only the creator may view or edit the Post;
(b) The creator may save, edit, and delete freely;
(c) The Platform does not review Drafts;
(d) The Post is not visible to readers, moderators (except as noted), or other roles.
4.2.3 Drafts inactive for fourteen (14) consecutive days are subject to automatic deletion. Drafts permanently deleted under this provision are not recoverable.
4.3.1 A non-Trusted Author submitting a Draft moves the Post to Pending.
4.3.2 While in Pending:
(a) The creator may not edit the Post; editing is locked until moderation resolves;
(b) The creator may withdraw the submission, returning the Post to Draft;
(c) Moderators receive the Post in their review queue;
(d) Moderators target a review window of 24–48 hours for standard Posts; this is a target, not a contractual SLA owed to the creator;
(e) The Post is not publicly visible.
4.3.3 Moderator outcomes for Pending Posts:
(a) Approve → Published;
(b) Reject → Draft, with reason communicated to creator;
(c) Archive → Archived (used in exceptional cases, e.g., flagrant policy violation).
4.3.4 The Platform reserves the right to reject any submitted Post at its sole discretion. The Platform is not obligated to provide reasons in all cases, but moderators shall provide guidance where reasonably possible per the Moderator Terms and Conditions.
4.4.1 A Post becomes Published upon:
(a) Moderator approval (standard creators); or
(b) Direct publication by a Trusted Author (per Article 5); or
(c) Direct publication to an Organization News-Feed (per Article 6); or
(d) Moderator/SUPER_ADMIN direct publication (Platform-attributed Posts).
4.4.2 While Published:
(a) The Post is publicly visible across all language versions per Article 11;
(b) Readers may React, share, and Report the Post;
(c) The creator may edit the Post, with re-moderation consequences specified in Section 4.5;
(d) The creator may not delete the Post; only Moderators may remove a Published Post (via Archive).
4.5.1 When a non-Trusted creator edits a Published Post, the Post returns to Pending status and becomes invisible to readers until re-approved.
4.5.2 When a Trusted Author edits a Published Post, the Post remains Published; no re-moderation is triggered, subject to Section 5.4 (revocation).
4.5.3 When a Trusted Author who has lost Trusted status (per Section 5.4) edits a previously published Post, that Post returns to Draft status and must be resubmitted through standard moderation.
4.5.4 Moderators editing metadata of a Published Post (SEO, OG, slug, category, featured position) does not change the Post's status. Moderators shall not edit substantive content of any Post.
4.6.1 A Post enters Archived status when:
(a) The creator archives their own Post;
(b) A Moderator archives the Post (for any reason permitted by this Rulebook or the Moderator Terms and Conditions);
(c) A Post is unpublished as a consequence of enforcement action.
4.6.2 Archived Posts:
(a) Are not visible to readers in any form;
(b) Remain accessible to the creator and Moderators;
(c) Are subject to the retention rules in Article 9.
4.6.3 Restoration of an Archived Post:
(a) Moderator-initiated restore: Moderators and SUPER_ADMIN may restore any Archived Post to any prior status at their discretion;
(b) Author-initiated restore: The original creator may submit a restoration request through the Platform; the Moderator reviews and decides at their discretion. The Moderator's decision is final.
5.1.1 A Trusted Author is a User permitted to publish Posts directly (Draft → Published), bypassing Pending status and moderation review.
5.1.2 Trusted Author status applies to all Posts authored by that person across all roles they hold (Author, Solo Specialist, Company Specialist, Company, Organization, Trainer). The Author capacity is the leading capacity for posting purposes.
5.2.1 A User attains Trusted Author status by either of the following:
(a) Threshold path: Having ten (10) or more Posts that have been Published on the Platform (whether reached via standard moderation or direct publication); or
(b) Designation path: Being designated as a Trusted Author by a SUPER_ADMIN at the Platform's sole discretion.
5.2.2 Trusted Author status takes effect immediately upon meeting one of the foregoing conditions and is reflected in the User's account.
5.3.1 Trusted Author Posts:
(a) Move directly from Draft to Published upon submission;
(b) Are not held in Pending status;
(c) Are not pre-reviewed by Moderators;
(d) Remain subject to all post-publication rules, including Reports, Moderator unilateral archival, and the Content Policy.
5.3.2 The Platform retains the right to review, archive, edit metadata of, or otherwise act on any Trusted Author Post at any time after publication. Trusted status does not exempt Posts from compliance.
5.4.1 Trusted Author status may be revoked upon either of the following:
(a) Violation threshold: Three (3) confirmed Violations of this Rulebook, the Content Policy, or applicable law; or
(b) Administrative discretion: Decision by SUPER_ADMIN, with or without specific cause, including but not limited to suspected coordinated misconduct, reputational risk to the Platform, or pattern-of-behavior concerns falling short of the three-Violation threshold.
5.4.2 A Violation is "confirmed" when:
(a) A Moderator or SUPER_ADMIN has investigated a Report or Platform-detected issue; and
(b) Determined that the Post or related conduct breached this Rulebook, the Content Policy, or applicable law; and
(c) Recorded the determination in the Platform's enforcement log.
5.4.3 Effects of revocation:
(a) The User immediately loses direct-publication rights;
(b) Future Posts move through standard Draft → Pending → Published flow;
(c) Edits to previously Published Posts cause those Posts to return to Draft (per Section 4.5.3);
(d) Existing Published Posts remain Published unless separately archived.
5.4.4 Reinstatement of Trusted status, if any, is at the Platform's sole discretion. There is no automatic reinstatement on the basis of additional published Posts after revocation.
5.5.1 Granting and revocation of Trusted Author status are administrative decisions of the Platform and are not subject to formal appeal.
5.5.2 A User may submit a written request for reconsideration to the Platform. The Platform may, but is not obligated to, respond.
6.1.1 "Organisation" is a distinct role on the Platform, separate from the "Company" role. The full rights and obligations of the Organisation role are governed by the Organisation Terms and Conditions (forthcoming).
6.1.2 This Article governs only the Organisation's posting capabilities. All other Organisation-related matters are deferred to the Organisation Terms and Conditions.
6.2.1 Organisations may publish Posts to one or both of the following channels:
(a) Organisation News-Feed: The Organisation's dedicated content stream on the Organisation's profile page;
(b) Public Blog (/news): The general-readership blog page accessible to all Platform visitors.
6.2.2 At creation, the Organisation shall designate which channel(s) the Post is intended for.
6.2.5 Organisation publications classified as Statements under Organisation T&C Article 13 (Official Statements, Committee Statements, Member Statements) are subject to the Posting Rulebook for IP, license, and retention, but are subject to the Organisation T&C for approval workflow, attribution, immutability, and retraction. In the event of any conflict, the Organisation T&C prevails for matters of authorship, approval, and retraction.
6.3.1 Posts designated for News-Feed only:
(a) Are published directly upon submission, without moderation review;
(b) Skip Pending status;
(c) Are subject to all post-publication rules, including Reports, Moderator unilateral archival, and the Content Policy.
6.3.2 The Platform retains the right to archive, edit metadata of, or take enforcement action against News-Feed Posts at any time.
6.3.5 Where a News-Feed Post is configured for internal visibility scope per Organisation T&C Article 12 (e.g., members-only, committee-only):
(a) The Post remains a Post under this Rulebook for IP, license, and retention purposes;
(b) Visibility and access control are governed by Organisation T&C Article 12;
(c) Standard Posting Rulebook moderation does not apply to internal-scope Posts (which are inherently restricted-audience).
6.4.1 Posts designated for the Public Blog (/news), whether also appearing in the News-Feed or not, are subject to standard moderation review (Draft → Pending → Published).
6.4.2 Blog-channel Organisation Posts follow the same moderation rules as Posts by other non-Trusted creators.
6.5.1 An Organisation may not unilaterally promote a News-Feed-only Post to the Public Blog post-publication; the Post must be resubmitted via standard moderation.
6.5.2 Moderators may, at their discretion, archive an Organisation Post from any channel.
7.1.1 Six reaction types are available on every Published Post:
| Reaction | Polarity |
|---|---|
| Like | Positive |
| Applaud | Positive |
| Smart | Positive |
| Love | Positive |
| Hot | Positive |
| Dislike | Negative |
7.1.2 Positive reactions count toward the aggregated positive score; the Dislike reaction counts toward the negative score.
7.2.1 Only registered Users (including Authors, Specialists, Companies, Organizations, Trainers, and Moderators) may submit Reactions.
7.2.2 Anonymous and non-registered visitors may not React.
7.2.3 A creator may React to their own Post.
7.3.1 Each User may submit at most one Reaction per Post. Selecting a different Reaction replaces the prior selection.
7.3.2 Users may change or remove their Reaction at any time.
7.3.3 Reactor identity is not displayed publicly. Only aggregate Reaction counts are visible.
7.4.1 Each Post displays:
(a) The aggregate count of all positive Reactions, summed across the five positive types; and
(b) The aggregate count of Dislike Reactions, displayed separately.
7.4.2 Individual Reaction-type breakdowns may be visible to the Post creator in the creator's analytics view.
7.5.1 The creator of a Post may view:
(a) Total view count;
(b) Aggregate count of each positive Reaction type;
(c) Total Dislike count (numeric only — no identity disclosure).
7.5.2 The creator may not see who specifically Reacted, including who Disliked.
7.6.1 Coordinated manipulation of Reactions (organized voting rings, automated reactions, retaliatory mass-Disliking) is prohibited.
7.6.2 Detection and remediation of Reaction abuse is deferred to operational policy in v1.0. The Platform may implement detection systems and consequences without amendment to this Rulebook.
8.1.1 Only registered Users may submit Reports.
8.1.2 Anonymous and non-registered visitors may not Report.
8.2.1 Reporters select one or more of the following categories:
(a) Spam / Promotional;
(b) Defamatory / False statements;
(c) Copyright infringement;
(d) Hate speech / Discrimination;
(e) Obscene / Inappropriate;
(f) Misinformation;
(g) Privacy violation;
(h) Other (free text required).
8.3.1 Reports are routed to the moderation queue for review.
8.3.2 Moderators target a response window of 24 hours for Reports; this is a target, not a contractual SLA.
8.3.3 Moderator decisions on Reports are final; there is no formal appeal pathway for Reporters.
8.4.1 The Platform may implement automated thresholds for taking provisional action on heavily Reported Posts (such as temporary unpublishing pending review).
8.4.2 Specific thresholds, formulas, and parameters are set by operational policy and are not part of this Rulebook.
8.5.1 A "False Report" is a Report determined by a Moderator to be:
(a) Knowingly inaccurate; or
(b) Submitted in bad faith (for example, retaliation, competitive harassment, or harassment of the creator).
8.5.2 A User who submits three (3) confirmed False Reports is subject to account suspension. Suspension procedures are governed by the User Terms and Conditions and Moderator Terms and Conditions.
8.5.3 Determination of False Report status is at the Moderator's discretion. The determination is final and not subject to appeal.
9.1.1 Drafts are retained while actively edited.
9.1.2 Drafts inactive for fourteen (14) consecutive days are automatically and permanently deleted. The Platform does not recover automatically deleted Drafts.
9.2.1 Published Posts are retained without time limit while in Published status.
9.3.1 Retention of Archived Posts depends on the reason for archival:
(a) Voluntary archival by creator: The creator may, after archival, request permanent deletion of the Post. The Platform shall comply within a reasonable period, subject to overriding legal obligations.
(b) Platform-initiated archival for policy violation: The Post is retained for evidentiary purposes for as long as reasonably necessary to support enforcement action, dispute defense, or legal compliance. The Platform shall not be obligated to delete such Posts upon creator request.
(c) Platform-initiated archival for other reasons (such as legal obsolescence or factual error): The Post is retained per general Platform retention practices.
9.4.1 Reader-side data relating to Posts (read history, Reactions, Reports) is retained per the Platform's master Privacy Policy. No special retention rule applies under this Rulebook.
9.5.1 Notwithstanding the foregoing, the Platform may retain any Post or related data for any period required by applicable law, regulatory requirement, or pending legal proceeding.
10.1.1 All Posts must comply with:
(a) Applicable Georgian law;
(b) The Platform's Content Policy (maintained internally);
(c) The intellectual property rights of third parties;
(d) Applicable professional standards governing the creator (where any).
10.1.2 Compliance with applicable professional rules — including but not limited to the rules of the Georgian Bar Association for Licensed Attorneys — is the sole responsibility of the creator. The Platform does not interpret, enforce, or assume responsibility for the creator's compliance with such professional rules.
10.2.1 The following content categories are prohibited and subject to rejection or archival:
(a) Content violating applicable Georgian law;
(b) Defamatory statements regarding identifiable persons;
(c) Content infringing intellectual property rights of third parties;
(d) Hate speech or content promoting discrimination on protected grounds;
(e) Obscene, pornographic, or grossly inappropriate content;
(f) Content promoting illegal activities;
(g) Pure spam or unsolicited promotional content;
(h) Content violating individual privacy rights;
(i) Content containing malware or harmful code;
(j) Any other content prohibited by the Content Policy.
10.3.1 Authors may publish Posts that have appeared elsewhere prior. Prior publication does not preclude submission to the Platform.
10.3.2 By submitting any Post, the creator warrants that they hold all necessary rights to publish the Post on the Platform and to grant the license set forth in Article 11.
10.3.3 AI-generated content may be submitted without disclosure obligation. The creator remains fully responsible for accuracy, originality, and compliance.
10.3.4 Plagiarism — the submission of content meaningfully copied from a third party without authorization or proper attribution — is a Violation. Consequences:
(a) First confirmed instance: Immediate unpublishing of the affected Post and formal warning;
(b) Second confirmed instance: Termination of the creator's posting role and permanent loss of posting privileges, subject to procedures in the applicable Role Terms and Conditions.
10.4.1 Where a Published Post contains a material factual error or other defect requiring correction:
(a) The Moderator unpublishes the Post (returning to Draft);
(b) The creator corrects the Post and resubmits;
(c) The Post moves through standard moderation (Pending → Published).
10.4.2 Edit history is maintained internally by the Platform but is not displayed publicly to readers.
10.4.3 Where a third party disputes the content of a Post (for example, a person mentioned in the Post claims inaccuracy):
(a) The disputing party submits a Report through the standard reporting mechanism (Article 8);
(b) The Report is processed through ordinary Moderator review;
(c) No special "right of reply" or formal mediation is provided beyond the Report mechanism.
11.1.1 Posts are originally created in Georgian, English, or Russian, at the creator's choice.
11.2.1 The Platform provides a translation tool, currently powered by the Google Translate API, that creators and readers may invoke to produce additional language versions.
11.2.2 The Platform does not provide translations as a Platform service. The Platform provides only the possibility to translate through the tool.
11.2.3 Where a creator invokes the translation tool to produce a language version of their Post:
(a) The output is treated as the creator's own content;
(b) The creator is responsible for the accuracy, completeness, and quality of all language versions of their Post, including those produced via the tool;
(c) The creator may edit the tool output before publication.
11.3.1 If a Post exists only in a subset of supported languages (Georgian, English, Russian), and a reader visits a language version of the site for which no translation exists, the site falls back to the available language version of the Post.
11.3.2 No "auto-translated" label or disclaimer is displayed. Creators bear full responsibility for the quality of all language versions associated with their Post.
11.4.1 Archival, unpublishing, or restoration of a Post applies automatically to all language versions of that Post. Per-language partial removal is not supported.
11.5.1 Disputes regarding translation accuracy are handled through the standard Report mechanism (Article 8).
12.1.1 Subject to the license granted under this Article, the creator retains ownership of original Content they create and publish on the Platform.
12.1.2 Where a Role Terms and Conditions document specifies different ownership (such as Company-owned Content for Company Specialists), that Role T&C governs ownership; this Rulebook governs the license to the Platform regardless of who owns the Content.
12.2.1 By submitting any Post, the creator grants the Platform a worldwide, perpetual, irrevocable, non-exclusive, royalty-free, sublicensable license to:
(a) Display, store, host, and transmit the Post on the Platform;
(b) Reformat the Post for any technical display context (mobile, desktop, RSS, syndication, AMP, or other);
(c) Translate the Post and produce language versions, including via automated tools;
(d) Excerpt, quote, summarize, and adapt the Post for promotional purposes, including marketing of the Platform itself, marketing of the Post, and marketing of related Platform services;
(e) Distribute the Post and any excerpt, summary, or adaptation thereof through any social media platform, third-party publication, search engine, content syndication network, newsletter, advertisement, or other distribution channel for the purposes of promoting the Platform and/or the Post;
(f) Use the Post for internal Platform purposes including search, recommendation, ranking, and analytics;
(g) Sublicense any of the foregoing rights to service providers, syndication partners, social platforms, and other third parties as necessary or useful to exercise the foregoing rights.
12.2.2 The license is perpetual and irrevocable, surviving any termination of the creator's role, account closure, or removal of the Post from the Platform. The Platform may continue to use the Post and any derivatives thereof under the granted rights after such termination.
12.2.3 The license is non-exclusive: the creator may republish their Content elsewhere. When the creator republishes Content elsewhere that was originally published on legal.ge, the creator shall acknowledge legal.ge as the primary source.
12.3.1 By submitting a Post, the creator warrants and represents that:
(a) They are the rightful owner of the Content or have all necessary rights, licenses, and authorizations to publish it;
(b) The Content does not infringe any third party's intellectual property, privacy, publicity, or other rights;
(c) The grant of the license in Section 12.2 does not breach any obligation owed to a third party.
12.3.2 The creator shall indemnify the Platform against all third-party claims arising from breach of these warranties.
12.4.1 Posts created by Moderators on behalf of the Platform are owned entirely by the Platform per the Moderator Terms and Conditions. Such Posts are not subject to the creator-license framework above.
13.1.1 The creator of a Post is solely liable for:
(a) The content, accuracy, lawfulness, and originality of the Post;
(b) Any third-party claim arising from the Post (including defamation, infringement, privacy violation, professional misconduct, or factual misrepresentation);
(c) Compliance with all professional, regulatory, and legal obligations applicable to the creator;
(d) Any consequence of any reader relying on the Post.
13.2.1 The Platform does not endorse, verify, or vouch for the accuracy, completeness, or legality of any Post.
13.2.2 Publication does not constitute Platform approval of the views, opinions, or information contained in any Post.
13.2.3 The Platform's review of a Post during moderation is for compliance with Content Policy only and is not a substantive endorsement.
13.3.1 Readers independently assess Posts based on their own judgment. The Platform makes no representation regarding the suitability of any Post for any reader's particular purpose.
13.3.2 Posts shall not be construed as legal advice, professional advice, or a substitute for individualized professional consultation, even where authored by Licensed Attorneys or other professionals.
13.4.1 The creator shall defend, indemnify, and hold harmless the Platform from and against all claims, damages, losses, and expenses arising from:
(a) The Post;
(b) Breach of the creator's warranties under Section 12.3;
(c) Violation of this Rulebook, the Content Policy, or applicable law by the creator.
13.5.1 The Platform does not impose a mandatory disclaimer on individual Posts. Liability allocation is established through the master Terms and Conditions and this Rulebook, and is binding regardless of any individual Post-level language.
14.1.1 The /news page features ten (10) prominent display positions (numbered 1–10).
14.1.2 Featured Positions are assigned by Moderators or SUPER_ADMIN at the Platform's sole discretion.
14.1.3 Selection criteria are not publicly defined. The Platform reserves complete editorial discretion over Featured Position assignment.
14.2.1 No creator, role, or Post is entitled to a Featured Position. Featuring confers no right and creates no expectation.
14.3.1 As of v1.0 of this Rulebook, the Platform does not offer paid promotion or paid Featured Position. Any future paid-promotion mechanism shall be governed by separate terms.
15.1.1 The Platform does not guarantee transactional notifications regarding Post lifecycle events (submission, approval, rejection, archival, Reactions, Reports) in v1.0 of this Rulebook.
15.1.2 Notifications, where present, are best-effort and do not create reliance interests.
15.2.1 The Platform reserves the right to implement notification systems in future versions of this Rulebook, with associated rules.
16.1.1 The Platform may track readers' read history of Posts for personalization and recommendation purposes.
16.1.2 Such tracking is conditional on the reader's consent through the Platform's analytics consent mechanism, as governed by the Platform's master Cookies Policy and Privacy Policy.
16.2.1 Aggregate Reaction counts are publicly visible. Individual reactor identity is not disclosed.
16.2.2 Reaction data linked to a specific User is treated as personal data under the master Privacy Policy.
16.3.1 Creators may access analytics for their own Posts, including:
(a) Total view counts;
(b) Aggregate Reaction counts by type;
(c) Total Dislike counts (numeric).
16.3.2 Creators may not access reader demographic data, referral source data, or individual reactor identities.
17.1.1 Moderators and SUPER_ADMIN may, at their discretion:
(a) Reject Pending Posts;
(b) Archive Published Posts;
(c) Edit Post metadata (SEO, OG, slug, category, Featured Position);
(d) Restore Archived Posts;
(e) Determine Reports and False Reports;
(f) Confirm Violations.
17.2.1 Consequences scale with severity:
| Severity | Possible Consequences |
|---|---|
| Minor | Edit request to creator; metadata correction |
| Standard | Unpublish to Draft; warning |
| Serious | Permanent archival; Trusted status revocation (if applicable) |
| Severe | Account suspension; role termination |
17.2.2 Specific consequence application is at Moderator/SUPER_ADMIN discretion. Patterns of Violations escalate consequences.
17.3.1 Suspension and termination procedures are governed by the applicable Role Terms and Conditions and the User Terms and Conditions, not by this Rulebook.
17.4.1 Moderation decisions, including Post rejection, archival, unpublishing, Trusted status revocation, and False Report determinations, are final.
17.4.2 A creator may revise rejected content and resubmit. A creator may request restoration of an Archived Post. Both routes are at Moderator discretion.
17.4.3 No formal appeal, mediation, or arbitration process is provided for moderation decisions.
18.1.1 The Platform reserves the right to amend this Rulebook at any time, in its sole discretion, with immediate effect upon publication.
18.2.1 Upon publication of any amendment to this Rulebook, the Platform shall present a re-consent prompt to all affected Users on their next Platform login or on next interaction with the Posting function, whichever is earlier.
18.2.2 Continued use of the Posting function after publication of an amendment constitutes acceptance of the amended Rulebook.
18.2.3 A User who declines to re-consent shall lose posting privileges (creating, editing, reacting, reporting). Existing Published Posts remain Published unless the User separately elects to archive them or the Platform takes archival action.
18.3.1 Amendments take effect immediately upon publication. No grace period applies.
18.4.1 The Platform shall make reasonable efforts to surface material amendments via the Platform interface (such as a banner, modal, or in-app prompt). The Platform is not obligated to provide email or other out-of-band notification.
19.1.1 This Rulebook is governed by the laws of Georgia.
19.2.1 Any dispute arising out of or relating to this Rulebook that cannot be resolved through Platform mechanisms shall be subject to the exclusive jurisdiction of the courts of Tbilisi, Georgia, consistent with the Platform's master Terms and Conditions.
19.3.1 This Rulebook is published in English, Georgian, and Russian. In the event of any conflict between language versions, the Georgian version prevails.
20.1.1 This Rulebook is incorporated by reference into each of the following Role Terms and Conditions:
(a) User Terms and Conditions;
(b) Author Terms and Conditions;
(c) Solo Specialist Terms and Conditions;
(d) Company Specialist Terms and Conditions;
(e) Company Terms and Conditions;
(f) Organization Terms and Conditions (forthcoming);
(g) Trainer Terms and Conditions;
(h) Moderator Terms and Conditions.
20.2.1 Conflicts between this Rulebook and a Role Terms and Conditions document are resolved as follows:
(a) Matters specific to a single role (such as Moderator employment matters, Specialist licensing, Company subscription billing) are governed by the applicable Role T&C;
(b) Matters of Posting workflow, permissions, lifecycle, ownership-license framework, Reactions, Reports, and rules common across roles are governed by this Rulebook;
(c) In genuine ambiguity, the Role T&C prevails for that role.
20.3.1 The following existing Role T&Cs require amendment to reference this Rulebook:
| Role T&C | Required Action |
|---|---|
| Author T&C | Replace Articles 4–5 (publication workflow, ownership) with reference to this Rulebook; retain Author-specific provisions (Author Dashboard, Rich Text Editor, eligibility) |
| Moderator T&C | Replace Articles 4.1–4.5, 5.4 (post moderation, prohibitions) with reference to this Rulebook; retain Moderator-specific provisions (employment, NDA, escalation) |
| Solo Specialist T&C | Replace Article 6 (Content Creation) with reference to this Rulebook |
| Company Specialist T&C | Replace Article 6 (Content Creation) with reference to this Rulebook |
| Company T&C | Replace content-creation provisions with reference to this Rulebook |
| Trainer T&C | Add reference to this Rulebook for any Posting activities |
| User T&C | Add reference for Reactions, Reports, reading rights |
| Organization T&C (new) | Build with this Rulebook as primary posting reference |
21.1.1 If any provision of this Rulebook is held invalid, illegal, or unenforceable, the provision shall be modified to the minimum extent necessary to make it valid; if not possible, the provision shall be severed, and the remaining provisions shall continue in force.
21.2.1 This Rulebook, together with the master Terms and Conditions, Privacy Policy, Cookies Policy, Content Policy, and applicable Role Terms and Conditions, constitutes the entire agreement regarding the Posting function on the Platform.
21.3.1 The Platform's failure to enforce any provision shall not constitute a waiver. Any waiver must be in writing to be effective.
| Version | Date | Author | Description |
|---|---|---|---|
| 1.0 | 13 May 2026 | Legal Sandbox Georgia LLC | Initial publication |
This Schedule consolidates numerical and threshold parameters defined in this Rulebook for quick reference.
| Parameter | Value | Source |
|---|---|---|
| Trusted Author published-post threshold | 10 Posts | Art. 5.2.1 |
| Trusted Author Violation revocation threshold | 3 confirmed Violations | Art. 5.4.1 |
| Inactive Draft auto-deletion period | 14 days | Art. 4.2.3, 9.1.2 |
| Standard moderation review target | 24–48 hours | Art. 4.3.2 |
| Reports response target | 24 hours | Art. 8.3.2 |
| False Report suspension threshold | 3 confirmed False Reports | Art. 8.5.2 |
| Plagiarism two-strike threshold | 1st = unpublish + warn; 2nd = termination | Art. 10.3.4 |
Featured Positions on /news |
10 (positions 1–10) | Art. 14.1.1 |
| Reaction types | 6 (5 positive, 1 negative) | Art. 7.1.1 |
| Report categories | 8 (incl. "Other" free text) | Art. 8.2.1 |
| One Reaction per User per Post | Yes | Art. 7.3.1 |
| Reactor identity disclosure | None | Art. 7.3.3 |
| Translation tool | Google Translate API | Art. 11.2.1 |
| Auto-translation label | None | Art. 11.3.2 |
| Amendment grace period | None | Art. 18.3.1 |
END OF RULEBOOK
© 2026 LegalGE. ყველა უფლება დაცულია.