RL4 Snapshot
Get RL4 for Cursor

Effective date: 2026-01-01

Privacy Policy & Terms of Use

This page covers RL4 Snapshot (Chrome Extension) and RL4 Snapshot for Cursor (Cursor/VSIX extension). It is derived from the repository behavior and documentation. Legal fields that are not present in the repository are explicitly marked TO COMPLETE.

Publisher / Controller

  • Publisher / Data controller: RLabs
  • Contact email: valentin@rl4.ai
  • Governing law / jurisdiction: France

Terms of Use — RL4 Snapshot (Chrome + Cursor)

Effective date: 2026-01-01

These Terms govern the use of: RL4 Snapshot — Chrome Extension (capture and export of LLM conversations in RCEP™ formats) and RL4 Snapshot for Cursor (Cursor/VSIX extension).

1) Purpose

RL4 Snapshot helps you capture context from supported tools and generate portable RCEP™ snapshots (and related “RL4 Blocks” handoff formats) so you can transfer context across LLMs and workflows.

2) Service description (derived from the repo)

Chrome extension

  • Captures LLM conversations on supported web providers (Claude, ChatGPT, Gemini, Perplexity, Copilot).
  • Generates RCEP™ snapshots (Compact / Ultra / Ultra+ / Transcript).
  • Computes SHA-256 checksums; may generate a device-only integrity seal (ECDSA P-256) when enabled.
  • Provides RL4 Blocks outputs for cross-LLM handoff / finalization.
  • Stores transcripts locally (IndexedDB / chrome.storage.local).

Cursor extension

  • Reads Cursor local history sources (e.g., workspace/global storage databases or generation logs) when present.
  • Generates RCEP™ snapshots.
  • Archives transcripts locally using chunked, content-addressed storage.
  • Records local evidence (file hashes, file events, editor context, diagnostics/lints).
  • May install an RL4 rule under .cursor/rules if missing.

3) Access and eligibility

  • You must have the rights to access and export the content you capture.
  • You are responsible for complying with the terms of the LLM platforms you use.

4) Prohibited uses

  • Capturing or sharing data you do not have rights to.
  • Bypassing provider access controls or using third-party sessions.
  • Claiming a snapshot is “verified” or “sealed” when it is not.

5) Security and integrity scope

  • SHA-256 checksum helps detect modifications.
  • Device-only integrity seal indicates continuity of a local key, but does not prove a person’s identity.
  • No semantic validation is guaranteed for lossy modes (Ultra / Ultra+).

6) User responsibility

  • You control what you export and where you paste it.
  • Snapshot accuracy is not guaranteed, especially without transcript mode.

7) Technical limitations

  • Captures can be partial due to UI virtualization, pagination, or API limits.
  • Ultra / Ultra+ modes are lossy by design.

8) Disclaimer

The software is provided “as is”, without warranties of accuracy, availability, or fitness for a particular purpose.

9) Limitation of liability

To the extent permitted by applicable law (France), the publisher is not liable for losses or damages arising from snapshot usage, third-party sharing (external LLMs), or local data loss.

10) Changes

These Terms may evolve. Material changes should be documented and reflected on this page.

Privacy Policy — RL4 Snapshot (Chrome + Cursor)

Effective date: 2026-01-01

  • No RL4 backend by default: data remains local.
  • Any transfer to third parties happens only through explicit user action (copy/paste or export).

A) Data handled — Chrome extension

Conversation content

  • User/assistant messages, roles, timestamps, and conversation identifiers (when available in the provider UI/API).
  • Captured via DOM and/or same-origin requests on supported providers.

Technical metadata

  • Detected provider, capture strategy, completeness/pagination signals.
  • SHA-256 checksum, transcript fingerprint, and optional device-only signature (when enabled).

UI/session state

  • Last snapshot, last prompt, capture progress, RL4 Blocks status, etc.

Page storage access (ChatGPT only, best-effort)

May read limited page storage values (e.g., device/session tokens) to improve same-origin conversation fetch reliability. (TO VERIFY / ensure this matches the shipped code path.)

Chrome permissions (why they’re needed)

activeTab

Reads the active LLM tab only when you click the extension to capture the conversation currently visible.

clipboardWrite

Copies the generated snapshot to your clipboard so you can paste it into another LLM (user-initiated).

storage

Stores snapshots and transcripts locally on your device (chrome.storage.local and IndexedDB).

sidePanel

Provides the extension UI in Chrome’s side panel for snapshot generation and management.

declarativeContent

Enables the extension UI only on supported LLM pages to avoid activating on unrelated sites.

Host permissions scope

Host permissions are restricted to supported LLM web apps so RL4 can read the conversation DOM and generate a snapshot:

chat.openai.comclaude.aigemini.google.comperplexity.aicopilot.microsoft.com

B) Data handled — Cursor extension

Cursor history (local)

  • May read local Cursor databases (e.g., workspaceStorage/globalStorage state DBs) when present.
  • May read local generation logs (e.g., cursor-aiService.generations.json) when present.

Local transcript archive

  • Chunked, content-addressed transcript storage (e.g., under extension globalStorage).
  • Indexes and metadata such as root hash, message count, and size.

Local evidence / proof logging

  • SHA-256 hashes for eligible files (non-binary, within budget).
  • File events: save / create / delete / rename.
  • Editor context snapshots (e.g., open files, focus, diagnostics count) on a periodic schedule.

Local configuration

  • UI state and snapshots stored in extension workspace state.
  • May write .cursor/rules/RL4.Cursor.Extension.mdc into the workspace if missing.

C) Storage, retention, deletion

  • Chrome: local storage via chrome.storage.local and IndexedDB.
  • Cursor: local storage via extension globalStorage/storageUri.
  • Data is retained locally until you delete it (extension controls, browser/IDE storage clearing, or uninstall).

D) Security

  • SHA-256 checksum provides integrity detection.
  • Optional device-only integrity seal (ECDSA P-256) provides local key continuity.
  • No automatic encryption of local data beyond OS-level protections.

E) Your rights

  • Access/export: you can copy/export snapshots you generated.
  • Deletion: you can delete local data from browser/extension storage (Chrome) or extension folders (Cursor).

Third-party services

When capturing or when you paste a snapshot elsewhere, you may interact with third-party LLM providers. You are subject to their policies and terms when using their services.

  • Claude
  • ChatGPT
  • Gemini
  • Perplexity
  • Copilot
Back to home