VIDEO CONSULTATIONS FUNCTION RULEBOOK

Legal Sandbox Georgia LLC

Document Type: Function Rulebook (Binding) Version: 1.0 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

PREAMBLE

This Video Consultations Function Rulebook ("Rulebook") establishes the rules governing video consultation sessions 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 participate in or facilitate video consultations. By initiating, joining, conducting, or otherwise interacting with a video consultation, You agree to be bound by this Rulebook.

This Rulebook is intentionally narrow in scope: it governs session mechanics, technical infrastructure, presence tracking, and Direct Consultations. It does NOT govern Inquiry intake, payment Capture, post-consultation appeals, or reviews — these are governed by their respective Function Rulebooks. Cross-references are provided throughout.

In the event of any conflict between this Rulebook and another Function Rulebook on a matter governed by that other Rulebook, the other Rulebook prevails. In the event of any conflict between this Rulebook and a Role T&C, this Rulebook prevails on session mechanics; the Role T&C prevails on role-specific obligations not addressed here.

ARTICLE 1: PURPOSE AND SCOPE

1.1 Purpose

1.1.1 This Rulebook provides a single authoritative source of truth governing the Video Consultation function on the Platform.

1.1.2 This Rulebook serves to:

(a) Define the two video consultation types (Service Inquiry Consultations and Direct Consultations);

(b) Establish session lifecycle, joining mechanics, and presence tracking;

(d) Define late-arrival, no-show, and reconnection rules;

(e) Govern Direct Consultation magic-link mechanics for Specialist-initiated follow-up;

(f) Specify multi-Specialist video session mechanics (Multi-Target Inquiry context);

(g) Allocate liability for technical and session-related matters;

(h) Define notification requirements;

(i) Define post-session artifact retention.

1.2 Scope

1.2.1 This Rulebook applies to:

(a) All video consultation sessions on the Platform, regardless of how initiated;

(b) Participants in video sessions: Specialists, Clients (registered or guest), and Multi-Specialist team members;

1.2.2 This Rulebook does NOT govern:

(a) Inquiry intake, Quote, payment, and Capture — governed by the Inquiries & Messaging Function Rulebook;

(b) Post-consultation Appeals and Disputes — governed by the Inquiries & Messaging Function Rulebook Article 12;

(d) Phone, in-person, written, or other non-video communication formats — governed by the Inquiries & Messaging Function Rulebook;

(e) Cabinet (litigation/working) cases — governed by the Cabinet Function Rulebook (forthcoming);

(f) Recording of video sessions — recording is NOT supported in v1.0; this Rulebook expressly disclaims recording capability;

(g) Mid-Case Appeals during active consultation — deferred to v2.0; only post-consultation Appeals exist in v1.0.

1.3 Roles Affected

1.3.1 This Rulebook directly affects the following roles:

Role	Capability
Solo Specialist	May conduct video consultations and initiate Direct Consultations with prior-engagement Clients
Company Specialist	May conduct video consultations and initiate Direct Consultations with prior-engagement Clients
Trainer	May conduct video sessions in Trainer capacity (governed by Trainer T&C; this Rulebook applies where Trainer also operates as Specialist)
User (Client)	May join video consultation as registered Client
Guest Client	May join Direct Consultation via magic-link without account
Moderator	May review session metadata and presence ledger for Inquiries Rulebook §12 appeals
Author	Not affected — Authors do not conduct video consultations
Trainee	Not affected by this Rulebook (Trainee video sessions, if any, are governed by Trainer T&C)
Organisation	May permit Affiliated Members to conduct video consultations (no Organisation-specific provisions; Organisation is not a session participant)

ARTICLE 2: DEFINITIONS

2.1 Capitalized terms used but not defined in this Rulebook have the meanings given in the applicable Role Terms and Conditions or other Function Rulebooks where context makes clear.

2.2 For purposes of this Rulebook:

"Active Session" means a video consultation session in progress, with at least one participant connected.

"Call Segment Ledger" means the immutable record maintained by the Platform of presence events for each video session, comprising connection timestamps, disconnections, and durations per participant.

"Capture Eligibility" means the threshold at which a video session has met the conditions for Inquiry payment Capture per the Inquiries Rulebook §11.2.

"Direct Consultation" means a video consultation initiated by a Specialist with a prior-engagement Client, distinct from Inquiry-derived consultations, governed by Article 7.

"End Consultation Action" means a participant's affirmative click of the "End Consultation" button in the Platform interface, triggering Capture proceedings under the Inquiries Rulebook §11.3.

"Extended Access Window" means the 30-minute period after a session's scheduled end time during which the session room remains joinable for reconnection or completion.

"Guest Client" means a Client participating in a Direct Consultation via magic-link without a registered Platform account.

"Inquiries Rulebook" means the Inquiries & Messaging Function Rulebook v1.0 or successor.

"Join Window" means the period (5 minutes before scheduled start through 30 minutes after scheduled end) during which the session room is joinable.

"Lead Specialist" has the meaning given in the Inquiries Rulebook §4.4 (the designated lead in Multi-Target Inquiries).

"LiveKit" means the third-party WebRTC video conferencing infrastructure provider used by the Platform for video session technology.

"Magic Link" means a single-use authentication URL issued by the Platform for Direct Consultations, granting time-limited access to a video session, governed by Article 7.

"No-Show" means a participant's failure to join a video session within the applicable grace period under Article 5.

"Presence Event" means a logged occurrence of participant connection, heartbeat, or disconnection within a session.

"Service Inquiry Consultation" means a video consultation derived from an Inquiry submitted through the Platform's Inquiry system, governed primarily by the Inquiries Rulebook with session mechanics governed by this Rulebook.

"Session" or "Video Session" means a video consultation conducted on the Platform, of any type within scope of Article 3.

ARTICLE 3: VIDEO CONSULTATION TYPES

3.1 Two Consultation Types

3.1.1 The Platform supports two types of video consultations:

(a) Service Inquiry Consultations — Client-initiated through the Inquiry system; Specialist-Client matched via Quote acceptance (Inquiries Rulebook Articles 4–10);

(b) Direct Consultations — Specialist-initiated via magic-link to prior-engagement Clients (Article 7 of this Rulebook).

3.1.2 Both types share the same session mechanics in Articles 4–6; differences in initiation, payment, and access are addressed in Articles 7 (for Direct) and the Inquiries Rulebook (for Service Inquiry).

3.2 Service Inquiry Consultations

3.2.1 Service Inquiry Consultations:

(a) Are derived from an accepted Inquiry Quote per Inquiries Rulebook §10.2;

(b) Use the Inquiry payment flow (preauth + Capture) per Inquiries Rulebook §10.3–10.4;

(c) Use the Communication Format selected at Inquiry stage (per Inquiries Rulebook §4.1.1(d)); only Inquiries with Video as the agreed format are governed by this Rulebook for session mechanics;

(d) Trigger 12% Platform commission on Capture per Inquiries Rulebook §10.4.1.

3.3 Direct Consultations

3.3.1 Direct Consultations:

(a) Are initiated by a Specialist via magic-link to a prior-engagement Client;

(b) Are limited to Clients with whom the Specialist has had a prior Engagement on the Platform;

(d) Are subject to the same 12% Platform commission as Service Inquiry Consultations;

(e) Are governed by Article 7 for initiation and access mechanics.

3.4 Excluded Consultation Types

3.4.1 The following are NOT video consultations within the scope of this Rulebook:

(a) Phone, in-person, or written consultations;

(b) Group sessions with Client invitees beyond the Multi-Specialist team (deferred to v2.0);

(d) Internal Specialist team meetings.

ARTICLE 4: SESSION LIFECYCLE

4.1 Lifecycle States

4.1.1 A video session moves through the following states:

State	Description
Scheduled	Session created with a scheduled start time; not yet joinable
Pending	Within Join Window (5 min before start through scheduled end); joinable
Active	At least one participant has joined; session in progress
Completed	Session ended (mutual End Consultation, auto-end, or natural conclusion)
Expired	Join Window passed without sufficient participation; treated as no-show per Article 5
Cancelled	Session terminated before completion (technical failure, mutual agreement, etc.)

4.2 Session Creation

4.2.1 A session is created:

(a) For Service Inquiry Consultations: automatically upon Inquiry transition to "Awaiting Payment" or "Consultation" state per Inquiries Rulebook §3;

(b) For Direct Consultations: by Specialist action through Platform interface or API per Article 7.

4.2.2 At creation, the system assigns:

(a) A unique session room identifier;

(b) Scheduled start time and duration;

(d) Access credentials (LiveKit JWT tokens for registered users; magic-link tokens for Guest Clients);

(e) An initial Call Segment Ledger entry recording the creation event.

4.3 Join Window

4.3.1 A session room becomes joinable 5 minutes before the scheduled start time.

4.3.2 The room remains joinable through the scheduled end time plus 30 minutes (the "Extended Access Window") for reconnection or completion purposes.

4.3.3 Outside the Join Window:

(a) Before 5 minutes prior: the room is not yet active; participants attempting to join receive a "session not yet open" message;

(b) After Extended Access Window: the room is closed; the session transitions to Completed (if any presence occurred) or Expired (if no presence occurred).

4.4 Active Session

4.4.1 A session enters Active state when the first participant connects.

4.4.2 While Active:

(a) Participants may join, leave, and rejoin within the Join Window;

(b) The Platform records Presence Events to the Call Segment Ledger;

(d) In-call chat is available per Article 8;

(e) Screen sharing is available per Article 9.

4.5 Session Completion

4.5.1 A session reaches Completed state through any of:

(a) Mutual End Consultation Action — both Client and Specialist click the "End Consultation" button per Inquiries Rulebook §11.3.1;

(b) 24-hour Auto-Capture — for Service Inquiry Consultations, if the session ends without a mutual End Consultation Action, the session is auto-completed 24 hours after the last presence event per Inquiries Rulebook §11.4;

4.5.2 Upon Completion:

(a) The Call Segment Ledger is finalised;

(b) Capture proceedings begin per Inquiries Rulebook §11.3 (for Service Inquiry) or per Article 7 (for Direct Consultations);

4.6 Maximum Session Duration

4.6.1 Maximum session duration is unlimited within paid time as set by the Specialist in the Quote (per Inquiries Rulebook §10.2) or in the Direct Consultation creation (per Article 7).

4.6.2 No hard cap on session duration is imposed by this Rulebook. Sessions may continue indefinitely while both parties remain present and the Specialist's Quote/duration permits.

4.7 Cancellation Before Active

4.7.1 A scheduled session may be cancelled before reaching Active state by:

(a) Mutual party agreement;

(b) Technical failure preventing the session from starting (governed by Article 6);

(c) Platform action for cause (e.g., Specialist account suspension, Client account suspension, Inquiry dispute opened pre-session).

4.7.2 Cancellation before Active state:

(a) Voids any payment preauthorization per Inquiries Rulebook §10.3;

(b) For Direct Consultations, voids the magic-link;

ARTICLE 5: PRESENCE, LATE ARRIVAL, AND NO-SHOW

5.1 Presence Tracking

5.1.1 The Platform records Presence Events for each participant in every session:

(a) Connection event — timestamp when participant joins;

(b) Heartbeat event — periodic confirmation of continued presence;

5.1.2 Presence Events form the Call Segment Ledger maintained per session per Article 11.

5.1.3 Presence Events are recorded automatically by the Platform's WebRTC infrastructure (LiveKit); no participant action is required.

5.2 Capture Eligibility Threshold

5.2.1 Capture eligibility under the Inquiries Rulebook §11.2 requires both Client and Specialist (or, for Multi-Specialist Inquiries, Lead Specialist and Client) present in the session for at least one (1) minute per the Capture timer.

5.2.2 The Capture timer:

(a) Starts when both required parties are simultaneously present;

(b) Pauses when either required party is disconnected;

(d) Reaches eligibility at one (1) minute total mutual presence (cumulative across reconnections).

5.2.3 This threshold is preserved from Inquiries Rulebook §11.2.2 and applies to all video consultations.

5.3 Late Arrival — Specialist

5.3.1 A Specialist is considered No-Show if they have not joined the session within fifteen (15) minutes after the scheduled start time.

5.3.2 Where Specialist No-Show is determined:

(a) The Inquiries Rulebook §12.6 (Specialist No-Show) provisions apply;

(b) The Client is offered automatic reschedule or refund per Inquiries Rulebook §12.6.2;

5.3.3 Where the Specialist joins after the 15-minute threshold but the Client is still waiting and willing to proceed:

(a) The session may proceed by mutual agreement;

(b) Capture timer starts upon Specialist's actual join;

(d) Late arrival may be raised in post-consultation appeal per Inquiries Rulebook §12.

5.4 Late Arrival — Client

5.4.1 A Client is considered No-Show if they have not joined the session within fifteen (15) minutes after the scheduled start time (same threshold as Specialist).

5.4.2 Where Client No-Show is determined:

(a) The Inquiries Rulebook §12.7 (Client No-Show) provisions apply;

(b) The Client forfeits payment per Inquiries Rulebook §12.7;

5.4.3 Where the Client joins after the 15-minute threshold but the Specialist is still waiting and willing to proceed, the session may proceed by mutual agreement, with Capture timer starting upon mutual presence.

5.5 Reconnection After Disconnect

5.5.1 Where a participant disconnects mid-session:

(a) The participant may rejoin within the Extended Access Window (until 30 minutes after scheduled end);

(b) Reconnection within the window does not constitute a new session;

(d) Disconnection events are logged in the Call Segment Ledger.

5.5.2 Where a participant fails to reconnect within the Extended Access Window:

(a) The session ends with the last recorded presence;

(b) If Capture eligibility was achieved (≥1 minute mutual presence), Capture proceedings apply per Inquiries Rulebook §11.2;

(c) If Capture eligibility was NOT achieved, the session is treated under Inquiries Rulebook §12.8 (Technical Failure) for reschedule consideration, where the failure is attributable to a party rather than to the Platform.

5.6 Mutual Late Arrival

5.6.1 Where both parties join late:

(a) The session may still proceed if both join within their respective 15-minute windows;

(b) The Capture timer starts upon mutual presence regardless of how late the joining occurred;

(c) The Specialist's Quote duration is the basis for session length, not the originally scheduled time, where the parties mutually agree to proceed.

ARTICLE 6: TECHNICAL FAILURE AND RECONNECTION

6.1 Technical Failure Categories

6.1.1 Technical failures are categorised as:

(a) Platform/LiveKit-side failure — the Platform's infrastructure is unavailable or malfunctions;

(b) Network/Connection-side failure — a participant's internet connection drops or quality degrades below usability;

(d) External service failure — third-party services Platform depends on (e.g., notification delivery, payment authorisation) fail.

6.2 Platform/LiveKit-Side Failure

6.2.1 Where the failure is attributable to the Platform's infrastructure:

(a) The session enters Cancelled state;

(b) Reschedule is offered to both parties at no additional charge per Inquiries Rulebook §12.8;

(c) Any payment preauthorization may be retained for the rescheduled session, or voided and re-authorised at the parties' option;

(d) The failure is logged with timestamp and cause description.

6.2.2 Repeated Platform-side failures affecting the same Inquiry are escalated to Platform support per operational policy.

6.3 Network/Connection-Side Failure (Party-Attributable)

6.3.1 Where a participant's connection fails or quality degrades:

(a) The participant may rejoin within the Extended Access Window per Section 5.5;

(b) Best-effort reconnection is attempted; the Platform does not guarantee successful reconnect on poor networks;

6.3.2 Where the failure is plainly attributable to one party's network or device:

(a) The other party is not penalised;

(b) The affected party may be considered No-Show if they cannot reconnect;

(c) Disputes about whether a failure was party-attributable or Platform-attributable are resolved in post-consultation Appeal per Inquiries Rulebook §12.

6.4 Connection Quality Monitoring

6.4.1 The Platform's WebRTC infrastructure (LiveKit) automatically adapts video quality to network conditions.

6.4.2 The Platform does NOT impose minimum connection quality requirements; sessions may proceed at any quality level the parties find acceptable.

6.4.3 Quality concerns raised after the session are addressed through the Reviews & Ratings system per Reviews Rulebook, not through this Rulebook.

6.5 Reschedule Mechanism

6.5.1 Where reschedule is appropriate (Platform-side failure, mutual agreement on technical issues, etc.):

(a) The Specialist proposes a new time within fourteen (14) days;

(b) The Client accepts or proposes alternative;

(d) The original session room is closed; a new room with new credentials is created.

6.5.2 Where reschedule cannot be agreed:

(a) The Inquiry returns to "Quote Offered" or "In Discussion" state per Inquiries Rulebook §3;

(b) Refund of preauth applies per Inquiries Rulebook §10.3.4 (refund of preauth without capture).

ARTICLE 7: DIRECT CONSULTATIONS (MAGIC-LINK)

7.1 Eligibility — Prior-Engagement Clients Only

7.1.1 A Specialist may initiate a Direct Consultation only with a Client with whom the Specialist has had a prior Engagement on the Platform.

7.1.2 "Prior Engagement" means, with respect to a Client and Specialist:

(a) A previously completed Service Inquiry Consultation between them; OR

(b) A previously completed Cabinet Case where the Specialist served as Lead or Affiliated Specialist (when Cabinet Rulebook is in effect); OR

7.1.3 Direct Consultations to Clients without prior Engagement are PROHIBITED and may constitute cold outreach under Inquiries Rulebook §13.

7.2 Initiation

7.2.1 A Specialist initiates a Direct Consultation through the Platform interface or API by providing:

(a) Identification of the prior-engagement Client (verified against Engagement records);

(b) Scheduled start time;

(d) Quoted price (in GEL);

(e) Brief consultation purpose.

7.2.2 The Platform validates eligibility (prior Engagement) and rejects requests that do not satisfy Section 7.1.

7.3 Magic-Link Issuance and Delivery

7.3.1 Upon valid initiation, the Platform issues a Magic Link with the following properties:

(a) Cryptographically secure single-use authentication token;

(b) Lifetime of up to seven (7) calendar days from issuance;

(c) The Magic Link must be redeemed within seven (7) days, OR within the duration of the scheduled consultation, whichever is earlier;

(d) Sessions can therefore be scheduled only within seven (7) days of Magic Link issuance; Specialists scheduling further out must wait to issue the Magic Link until within the seven-day horizon.

7.3.2 The Magic Link is delivered to the Client via email at the address recorded in the prior Engagement; the Specialist does not select the delivery email.

7.3.3 The Platform logs Magic Link issuance, delivery success, and redemption.

7.4 Magic Link Single-Use vs. Reusable

7.4.1 Magic Link redemption follows a hybrid model:

(a) Single-use for payment — the Client follows the Magic Link, completes payment authorisation; this consumes the payment portion of the link;

(b) Reusable for session join — after payment, the Client may re-open the link multiple times to rejoin the same session room within the Join Window.

7.4.2 A Magic Link is invalidated upon any of:

(a) Seven-day expiry from issuance;

(b) Scheduled consultation end + Extended Access Window expiry;

(d) Voiding of the underlying payment preauthorization.

7.5 Direct Consultation Pricing

7.5.1 Pricing for Direct Consultations is set by the Specialist using the same Quote model as Service Inquiry Consultations per Inquiries Rulebook §10.2.

7.5.2 Direct Consultations may be priced at any amount, including zero.

7.5.3 Free Direct Consultations (priced at zero):

(a) Are subject to the 10 GEL Platform fee per Inquiries Rulebook §10.5;

(b) Charged to the Specialist on Capture, regardless of Specialist tier (per Subscriptions Rulebook §23.2.1).

7.6 Direct Consultation Payment Flow

7.6.1 Payment processing for Direct Consultations:

(a) Pre-paid — Client must complete payment authorisation before joining the session;

(b) Bank-side preauthorization is created upon Client's Magic Link redemption and acceptance of the price;

(d) 12% Platform commission applies per Inquiries Rulebook §10.4.1.

7.6.2 Where the Client does not complete payment:

(a) The session does not become joinable;

(b) The Magic Link expires per Section 7.4;

7.7 Guest Client Considerations

7.7.1 A Direct Consultation may proceed with the Client participating as a Guest Client (without registered Platform account):

(a) Magic Link authenticates the Guest;

(b) Guest provides email at point of payment (matching Specialist-recorded prior-Engagement email);

(d) Guest does NOT receive a registered Platform Account.

7.7.2 Guest Client limitations:

(a) Cannot file post-consultation Appeals through the standard interface (must contact Platform support);

(b) Cannot submit Reviews per Reviews Rulebook (Reviews require a registered Account);

7.7.3 A Guest Client may upgrade to a registered User account at any time per User T&C; prior session records may be associated with the new account upon verification.

7.8 Reuse of Direct Consultations

7.8.1 A Specialist may issue multiple Direct Consultations to the same prior-engagement Client over time, subject to:

(a) Reasonable frequency — Platform may impose anti-spam thresholds (e.g., maximum N Direct Consultations per Client per month) per operational policy;

(b) Client right to opt out per Section 7.9.

7.9 Client Opt-Out

7.9.1 A Client (registered or Guest) may opt out of further Direct Consultations from a specific Specialist:

(a) Per-session decline — Client ignores or declines the Magic Link; no future obligation;

(b) Persistent block — Client may permanently block the Specialist from issuing Direct Consultations through Platform interface (registered Clients) or by contacting Platform support (Guest Clients).

7.9.2 Persistent blocks are permanent unless Client revokes them.

ARTICLE 8: IN-CALL CHAT

8.1 Chat Availability

8.1.1 A text chat sidebar is available within the active video session interface, allowing real-time text communication between participants.

8.1.2 The chat is governed by the Inquiries Rulebook §6 (Secure Messaging) for content rules, retention, and privilege.

8.1.3 Chat messages exchanged during the session are appended to the underlying Inquiry messaging thread and persist after the session ends.

8.2 Chat Functionality

8.2.1 In-call chat supports:

(a) Plain-text messages;

(b) Real-time delivery while session is Active;

(d) Visibility to all session participants.

8.3 In-Call File Upload — NOT Supported

8.3.1 File and document upload via Platform during an active video session is NOT supported in v1.0.

8.3.2 Participants who need to exchange documents during a video consultation must use external means (e.g., email).

8.3.3 File upload to the Inquiry thread resumes after the session ends (Inquiries Rulebook §6 applies).

8.3.4 This restriction reflects an operational and bandwidth choice; participants are advised to prepare and exchange documents before or after sessions through email or post-session Inquiry thread messaging.

8.4 Chat Moderation

8.4.1 The Platform may, through Moderators with appropriate authority, review or moderate in-call chat content:

(a) For violations of platform-wide content rules (per Inquiries Rulebook §6 and Posting Rulebook content rules);

(b) Where called upon to investigate post-consultation appeals per Inquiries Rulebook §12;

ARTICLE 9: SCREEN SHARING

9.1 Availability

9.1.1 Screen sharing is available in v1.0 through the Platform's WebRTC infrastructure (LiveKit).

9.1.2 Either participant (Specialist or Client) may initiate screen sharing during an active session, subject to mutual consent in practice (recipient may decline to view).

9.2 Screen Sharing Mechanics

9.2.1 Screen sharing operates as follows:

(a) The sharer's screen content is transmitted in real-time to other session participants;

(b) Screen content is NOT recorded by the Platform (consistent with Article 10 — no recording);

(d) Participants may request the sharer to stop sharing at any time.

9.3 Privilege and Confidentiality

9.3.1 Content shared via screen during a Specialist-Client video consultation is subject to the same attorney-client privilege protections as the underlying consultation per Inquiries Rulebook §13.

9.3.2 Participants are responsible for the appropriateness of shared content; the Platform exercises no control over what participants choose to share.

9.4 No Stored Output

9.4.1 No screenshot, recording, or persistent capture of shared screen content is performed by the Platform.

9.4.2 Participants who wish to retain shared content must capture it through their own means (subject to applicable privilege and confidentiality rules).

ARTICLE 10: NO RECORDING IN v1.0

10.1 No Recording

10.1.1 The Platform does NOT record audio or video of consultation sessions in v1.0.

10.1.2 The Platform stores only:

(a) Call Segment Ledger entries (presence events, durations, timestamps) per Article 11;

(b) Audit log entries (state transitions, payment events) per Article 11;

(d) Participant identities and join/leave times per Article 11.

10.1.3 No audio stream, video stream, screen share content, or chat message content is captured or stored as session "recording."

10.2 Privilege Protection by Non-Recording

10.2.1 The non-recording stance protects attorney-client privilege:

(a) No recording exists to be subpoenaed, leaked, or breached;

(b) Privilege is preserved without reliance on recording-protection measures;

10.3 Future Recording Feature

10.3.1 Recording is a feature contemplated for future Platform versions.

10.3.2 Where introduced, recording will be:

(a) Subject to explicit dual consent from both Specialist and Client;

(b) Subject to specific retention, access, and deletion rules to be defined in a future Rulebook amendment;

10.3.3 The Platform shall provide at least sixty (60) days' advance notice before introducing any recording feature, and re-consent from existing users shall be required.

10.4 User Self-Recording

10.4.1 Participants who wish to record their own video sessions through external means (e.g., screen recording on their device) bear sole responsibility for:

(a) Compliance with applicable laws on recording (consent, notification);

(b) Compliance with their own professional and ethical obligations;

(d) Any consequences of recording, including privilege waiver where applicable.

10.4.2 The Platform does not facilitate, condone, or oppose external recording by participants; it is a matter between the parties and applicable law.

ARTICLE 11: POST-SESSION ARTIFACTS

11.1 Artifacts Maintained

11.1.1 For each video session, the Platform maintains:

(a) Call Segment Ledger — presence events (connection, heartbeat, disconnection) with timestamps and durations per participant;

(b) Audit log entries — state transitions, payment events, system actions related to the session;

(d) Participant identities and join/leave times — who participated, identified by Platform Account ID, name, and role.

11.1.2 Quality metrics (network conditions, bandwidth, error rates) are NOT systematically retained as user-accessible artifacts in v1.0; they may be transiently logged for operational diagnostic purposes only.

11.2 Retention Period

11.2.1 Post-session artifacts are retained per the Platform's Privacy Policy retention schedule, typically aligned with legal/financial record retention requirements.

11.2.2 The Platform's standard retention is consistent with Georgian law requirements for transaction records and audit trails.

11.3 User Access to Own Artifacts

11.3.1 Participants may request artifacts pertaining to their own sessions:

(a) Specialists may request session metadata (Call Segment Ledger, audit log) for their own sessions through the Platform interface or by contacting support;

(b) Clients (registered) may request session metadata for their own sessions;

(c) Guest Clients may request artifacts for their Direct Consultations through Platform support upon identity verification.

11.3.2 Such requests shall be honored within reasonable timeframes consistent with the Platform's Privacy Policy.

11.4 Platform Use of Artifacts

11.4.1 The Platform may use post-session artifacts:

(a) To resolve post-consultation Appeals per Inquiries Rulebook §12;

(b) To investigate suspected violations of Platform terms;

(d) To comply with legal obligations.

11.4.2 The Platform shall NOT use artifacts:

(a) For purposes inconsistent with the Privacy Policy;

(b) For commercial purposes beyond Platform operation;

11.5 Court-Compelled Disclosure

11.5.1 Where the Platform receives a court order or legally binding directive compelling disclosure of session artifacts:

(a) The Platform shall notify affected participants before disclosure where legally permissible;

(b) The Platform shall comply with the order's scope only.

ARTICLE 12: MULTI-SPECIALIST VIDEO SESSIONS

12.1 Multi-Specialist Context

12.1.1 Where a Service Inquiry Consultation arises from a Multi-Target Inquiry per Inquiries Rulebook §4.4 with multiple Specialists assigned (Lead Specialist plus team), the video session may include all team members.

12.2 Lead Specialist's Role

12.2.1 The Lead Specialist designated per Inquiries Rulebook §4.4:

(a) Is the sole point of contact for End Consultation Action — only the Lead Specialist's "End Consultation" click triggers Capture proceedings;

(b) Coordinates the team's participation in the session;

(d) Assumes responsibility for session quality from the team's side.

12.3 Team Specialist Presence

12.3.1 Lead Specialist's presence is REQUIRED for Capture eligibility.

12.3.2 Capture timer (≥1 minute mutual presence under Section 5.2) requires:

(a) The Lead Specialist present in the session; AND

(b) The Client present in the session;

12.3.3 Where the Lead Specialist is absent and only team members are present with the Client, Capture eligibility is NOT met; the session may be subject to no-show rules under Section 5.3 (Specialist No-Show).

12.4 Commission Split Among Team

12.4.1 The 12% Platform commission per Inquiries Rulebook §10.4.1 is calculated on the gross Quote.

12.4.2 Specialist-side payment distribution among team members is off-Platform and not arbitrated by the Platform:

(a) The Platform pays the Specialist-side share to the Lead Specialist;

(b) The Lead Specialist is responsible for distributing payment among team members per their internal arrangement;

12.5 Team Composition Changes

12.5.1 A Specialist may not be added to a Multi-Specialist team after Inquiry Quote acceptance without re-Quote per Inquiries Rulebook §10.2 (Quotes are non-revisable post-acceptance).

12.5.2 A team Specialist may withdraw before session start; the Lead Specialist must:

(a) Inform the Client;

(b) Either proceed without the withdrawing Specialist (if Lead remains) or trigger reschedule per Article 6.5;

12.6 Multi-Specialist Recording Considerations

12.6.1 The non-recording stance under Article 10 applies fully to Multi-Specialist sessions; presence of multiple Specialists does not change the rule.

ARTICLE 13: TECHNICAL REQUIREMENTS

13.1 Operational Specification

13.1.1 Browser, device, and network requirements for video consultations are specified in the Platform's operational documentation, not in this Rulebook.

13.1.2 The Platform reserves the right to:

(a) Update technical requirements as third-party infrastructure (LiveKit, browser standards) evolves;

(b) Specify minimum supported browsers, operating systems, and connection bandwidth in operational documentation;

13.2 Mobile Device Support

13.2.1 The Platform supports mobile devices on a best-effort basis:

(a) Mobile browsers (iOS Safari, Android Chrome) are supported;

(b) Quality may vary based on device capabilities and network conditions;

13.3 User Responsibility for Technical Readiness

13.3.1 Each participant is responsible for technical readiness at session time, including:

(a) Compatible browser meeting Platform's specified requirements;

(b) Functioning camera, microphone, and speakers/headphones;

(d) Permitting browser access to camera/microphone;

(e) Ability to use a quiet, private environment;

(f) Updated browser security and operating system.

13.3.2 Failures attributable to a participant's technical setup are that participant's responsibility. The Platform is not liable for:

(a) Browser incompatibility;

(b) Insufficient bandwidth or connection drops;

(d) Firewall or proxy restrictions;

(e) Failure to permit browser camera/microphone access.

13.3.3 Where technical failure attributable to one party prevents session completion, the other party's rights and remedies are governed by Section 6.3 and Inquiries Rulebook §12.

13.4 Pre-Session Technical Test

13.4.1 The Platform may provide a pre-session test interface allowing participants to verify camera, microphone, and connection.

13.4.2 Use of the pre-session test is recommended but NOT required.

13.4.3 Failure to test before joining does not entitle the participant to special treatment if technical issues subsequently arise.

ARTICLE 14: PLATFORM LIABILITY AND DISCLAIMERS

14.1 Commercially Reasonable Infrastructure

14.1.1 The Platform commits to commercially reasonable video infrastructure consistent with industry standards for SaaS video conferencing platforms.

14.1.2 The Platform makes no specific warranty regarding:

(a) Uptime percentage;

(b) Specific bandwidth or quality thresholds;

(d) Compatibility with all browser/device combinations.

14.2 Third-Party Infrastructure Reliance

14.2.1 Video session technology is provided through LiveKit (or successor third-party WebRTC provider).

14.2.2 The Platform's video service availability depends on:

(a) LiveKit's service availability;

(b) Third-party network infrastructure (ISPs, internet backbone);

14.2.3 Failures in third-party infrastructure that affect video sessions are governed by Article 6 (technical failure / reschedule) where reasonably attributable to those infrastructure components.

14.3 Platform Liability Limitation

14.3.1 The Platform's liability for video session failures is limited to:

(a) Reschedule per Article 6 (no additional charge);

(b) Refund of payment preauthorization per Inquiries Rulebook where Capture has not occurred;

14.3.2 The Platform is NOT liable for:

(a) Loss of business opportunities arising from session failures;

(b) Loss of professional opportunity;

(d) Quality of legal advice provided in any session;

(e) Outcomes of legal matters discussed in sessions;

(f) Privilege waiver or breach attributable to participant conduct.

14.4 Specialist Liability for Service Quality

14.4.1 The Specialist remains solely responsible for:

(a) The quality of legal advice provided;

(b) Professional conduct during sessions;

(d) Privilege management in their professional capacity.

14.5 Client Conduct

14.5.1 Clients are responsible for:

(a) Truthful representation of their legal matter;

(b) Conduct during sessions consistent with Platform terms;

(d) Not abusing the Platform (e.g., recording without consent in violation of applicable law).

ARTICLE 15: NOTIFICATIONS

15.1 Mandatory Video-Specific Notifications

15.1.1 The Platform shall notify participants of the following video-session events:

(a) Consultation scheduled (confirmation to both parties);

(b) Reminder 24 hours before scheduled time (both parties);

(d) Magic Link issued (Direct Consultation; sent to Client email);

(e) Specialist joined (notification to Client when Specialist enters room);

(f) Client joined (notification to Specialist when Client enters room);

(g) Session ended (post-session summary to both parties);

(h) Reschedule requested (the other party's notification of proposed reschedule);

(i) Reschedule confirmed (both parties);

(j) Connection lost (mid-session, where reconnection is possible);

(k) No-show determination (where applicable);

(l) Session cancelled (both parties).

15.2 Notification Channels

15.2.1 Notifications are delivered via:

(a) In-app notification (mandatory for registered users);

(b) Email to address on file (mandatory);

15.3 Guest Client Notifications

15.3.1 For Guest Clients in Direct Consultations:

(a) Notifications are delivered exclusively via email (no Platform Account exists);

(b) The Magic Link email serves as both authentication and notification vehicle for major events.

15.4 Notification Failure

15.4.1 Notification delivery failures (bounced email, SMS failures) do NOT extend Join Windows, no-show grace periods, or Appeal Windows.

15.4.2 Participants are responsible for maintaining accurate contact information and reasonable monitoring of their email/Platform.

ARTICLE 16: PROHIBITED CONDUCT

16.1 Participant Prohibitions

16.1.1 Participants in video consultations shall NOT:

(a) Record or capture session audio/video without explicit consent of all participants and (where applicable) compliance with Georgian recording laws;

(b) Share session access (Magic Links, room URLs) with unauthorized third parties;

(d) Display obscene, illegal, or violating content during the session (including via screen sharing);

(e) Use sessions for purposes outside the legitimate consultation purpose (e.g., as a distribution mechanism for non-consultation content);

(f) Attempt to circumvent Platform technical controls (e.g., spoofing presence, manipulating Capture timer);

(g) Engage in any activity that would violate Inquiries Rulebook §13 (Communications Conduct), Posting Rulebook content rules, or other Platform terms.

16.2 Specialist-Specific Prohibitions

16.2.1 Specialists shall additionally NOT:

(a) Issue Direct Consultations to Clients without prior Engagement (cold outreach prohibition);

(b) Use Direct Consultations as a workaround to standard Inquiry flow for new clients;

16.3 Client-Specific Prohibitions

16.3.1 Clients shall NOT:

(a) Provide false information to obtain consultations (e.g., impersonating a different person);

(b) Use Direct Consultations to harass Specialists who have offered such consultations;

16.4 Consequences

16.4.1 Violations may result in:

Severity	Possible Consequences
Minor	Warning
Standard	Account flag; restricted Direct Consultation issuance
Serious	Account suspension; loss of Direct Consultation privileges
Severe	Account termination; permanent ban; legal action where warranted

16.4.2 Specific consequence application is at Platform discretion in coordination with Moderators per Moderator T&C.

ARTICLE 17: GOVERNING LAW AND DISPUTE RESOLUTION

17.1 Governing Law

17.1.1 This Rulebook is governed by the laws of Georgia.

17.2 Forum

17.2.1 Any dispute arising out of or relating to this Rulebook that cannot be resolved through Platform mechanisms (post-consultation Appeals per Inquiries Rulebook §12, or other Platform processes) shall be subject to the exclusive jurisdiction of the courts of Tbilisi, Georgia.

17.3 Language

17.3.1 This Rulebook is published in English, Georgian, and Russian. In the event of any conflict between language versions, the Georgian version prevails.

ARTICLE 18: AMENDMENTS AND RE-CONSENT

18.1 Right to Amend

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 Re-Consent

18.2.1 Upon publication of any amendment, the Platform shall present a re-consent prompt to affected users at the next login or interaction with the video consultation function.

18.2.2 Continued participation in video consultations after publication constitutes acceptance of the amended Rulebook.

18.3 Material Amendments

18.3.1 Material amendments (e.g., introduction of recording, change to Direct Consultation eligibility, change to Capture mechanics affecting sessions) shall be subject to:

(a) Affirmative re-consent for users wishing to continue using the video consultation function;

(b) At least sixty (60) days' advance notice for amendments introducing recording;

18.4 Right to Decline

18.4.1 Users who do not accept an amendment may decline; the consequence is loss of access to video consultation features. Other Platform features may remain accessible.

ARTICLE 19: CROSS-REFERENCES TO OTHER RULEBOOKS AND ROLE T&Cs

19.1 Primary Cross-References

19.1.1 This Rulebook coordinates with the following:

Topic	Where the Rules Live
Inquiry submission, Quote, payment Capture	Inquiries Rulebook Articles 4, 10, 11
Post-consultation Appeals	Inquiries Rulebook Article 12
Communications Conduct (chat content, privilege)	Inquiries Rulebook Article 13
Reviews	Reviews Rulebook
12% Platform commission	Inquiries Rulebook §10.4.1
10 GEL free-consultation Platform fee	Inquiries Rulebook §10.5
Subscription tier features and Card on File	Subscriptions Rulebook
Organisation membership of Specialists	Organisation T&C

19.2 Conflict Resolution

19.2.1 Conflicts between this Rulebook and other Function Rulebooks are resolved as follows:

(a) On matters of session mechanics, presence, technical handling, Direct Consultations — this Rulebook prevails;

(b) On matters of Inquiry lifecycle, Quote, payment, Capture, post-consultation Appeals — Inquiries Rulebook prevails;

(d) On matters of subscriptions and billing — Subscriptions Rulebook prevails;

(e) On matters of Organisation governance — Organisation T&C prevails;

(f) For matters not clearly within any single Rulebook's scope — interpreted to give effect to all and avoid conflict.

19.3 Required Cross-Reference Updates to Other Rulebooks

19.3.1 This Rulebook does NOT require modification of other Function Rulebooks; the existing Rulebooks anticipate the Video Consultations Rulebook through cross-references (e.g., Inquiries Rulebook §1.2.2(b) reserves video session quality matters to this Rulebook).

19.3.2 Role T&Cs may benefit from cross-reference updates noting the existence of this Rulebook; such updates are non-substantive (since session mechanics were already conducted) and may be applied through routine Role T&C updates.

ARTICLE 20: SEVERABILITY AND ENTIRE RULEBOOK

20.1 Severability

20.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.

20.2 Entire Rulebook

20.2.1 This Rulebook, together with the master Terms and Conditions, Privacy Policy, Cookie Policy, and applicable Function Rulebooks and Role Terms and Conditions, constitutes the entire agreement regarding the Video Consultations function on the Platform.

20.3 No Waiver

20.3.1 The Platform's failure to enforce any provision shall not constitute a waiver. Any waiver must be in writing to be effective.

ARTICLE 21: VERSION HISTORY

Version	Date	Author	Description
1.0	13 May 2026	Legal Sandbox Georgia LLC	Initial publication

SCHEDULE B: SUMMARY OF KEY OPERATIONAL PARAMETERS

Parameter	Value	Source
Consultation types	Service Inquiry / Direct Consultation	Art. 3
Join Window	5 min before scheduled start to 30 min after scheduled end	Art. 4.3
Capture eligibility threshold	≥1 minute mutual presence	Art. 5.2.1 (preserved from Inquiries §11.2.2)
Specialist no-show threshold	15 minutes after scheduled start	Art. 5.3.1
Client no-show threshold	15 minutes after scheduled start	Art. 5.4.1
Reconnection window	Until end of Extended Access Window (30 min after scheduled end)	Art. 5.5.1
Maximum session duration	Unlimited within paid time per Quote	Art. 4.6.1
Session-end mechanism	Mutual End Consultation OR 24h Auto-Capture	Art. 4.5.1 (per Inquiries §11)
Direct Consultation eligibility	Prior Engagement Clients only	Art. 7.1.1
Magic Link lifetime	7 days OR until session end + 30 min, whichever earlier	Art. 7.3.1
Magic Link redemption	Single-use payment, reusable session join	Art. 7.4
Direct Consultation pricing	Specialist sets via Quote model	Art. 7.5.1
Free Direct Consultations	Allowed; 10 GEL Platform fee per Inquiries §10.5	Art. 7.5.3
12% Platform commission	Applies to all video Capture	Art. 7.6.1(d)
Recording in v1.0	NOT supported	Art. 10
In-call chat	Supported (text only, persisted to Inquiry thread)	Art. 8
In-call file/document upload	NOT supported in v1.0	Art. 8.3
Screen sharing	Supported (no recording)	Art. 9
Browser/device requirements	Operationally specified, not contractually	Art. 13.1
Mobile support	Best-effort	Art. 13.2
User responsibility for technical readiness	Strict	Art. 13.3
Multi-Specialist — Lead presence required for Capture	Yes	Art. 12.3
Specialist-side payment to Lead, internal split off-Platform	Yes	Art. 12.4
Notifications	Full mandatory v1.0 system	Art. 15
Mid-Case Appeals	Deferred to v2.0	Art. 1.2.2(g)
Group sessions with Client invitees	Deferred to v2.0	Art. 3.4.1(b)
Cabinet case meetings	Deferred to Cabinet Rulebook	Art. 3.4.1(c)

END OF RULEBOOK