ATAWAIRL4By ATAWAI
Sign inInstall RL4

Effective date: 2026-01-01

Privacy Policy & Terms of Use

This page covers RL4 Snapshot as distributed for Cursor and VS Code (VSIX), optional MCP usage, and the RL4 dashboard when you use it. Legal fields not yet fixed in the repo are marked TO COMPLETE.

Publisher / Controller

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

Terms of Use — RL4 Snapshot (Cursor / VS Code)

Effective date: 2026-01-01

These Terms govern the use of RL4 Snapshot as installed from the VSIX for Cursor or VS Code, including optional MCP configuration and, when you sign in, the RL4 web dashboard.

1) Purpose

RL4 helps you capture AI-assisted development activity into a local, project-scoped .rl4/ store — evidence, timeline, and decisions — so you can resume work and query history across tools without re-briefing every model.

2) Service description (derived from the repo)

Cursor / VS Code extension (VSIX)

  • Reads IDE-local sources (e.g. workspace storage, chat-related logs) when present.
  • Writes append-only evidence under .rl4/ in your repository.
  • May install or update RL4 rule files under .cursor/rules when configured.
  • Exposes project history to compatible agents via MCP when you enable it.

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 IDEs and LLM providers you use.

4) Prohibited uses

  • Capturing or sharing data you do not have rights to.
  • Bypassing provider or employer access controls.
  • Misrepresenting the integrity or provenance of evidence.

5) Security and integrity scope

  • Hashes and chains in .rl4/ help detect tampering locally.
  • No guarantee that a third-party LLM output is correct — RL4 records what happened, not universal truth.

6) User responsibility

  • You control what you export and where you paste it.
  • You choose whether to enable team sync or cloud-backed features.

7) Disclaimer

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

8) Limitation of liability

To the extent permitted by applicable law (France), ATAWAI is not liable for losses arising from use of RL4, third-party LLMs, or loss of local data.

9) Changes

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

Privacy Policy — RL4 Snapshot

Effective date: 2026-01-01

  • Local-first by default: evidence stays local under .rl4/ in your repo.
  • Cloud features are optional: when you authenticate an RL4 account or enable dashboard/team features, selected account/workspace telemetry and sync payloads may transit through RL4 infrastructure (including Supabase and rl4.ai services). TO COMPLETE: precise data categories, DPA, retention, and region details.

A) Data handled — VSIX (Cursor / VS Code)

IDE-local sources

  • May read local IDE databases/logs (e.g. workspace/global storage, generation logs) when present.
  • Scan scope can include additional local sources depending on enabled connectors and detected tools (e.g. Claude Code, Codex, Copilot VS Code, JSON exports).

Project evidence

  • File hashes, file events, chat capture, decisions — under your repo's .rl4/ folder.
  • Integrity in this Cursor/VS Code SKU is based on SHA-256 checksums and local Merkle-style chaining.

Local configuration

  • Extension UI state in workspace / global storage.
  • Optional MCP and dashboard credentials when you configure them.
  • May merge .cursor/hooks.json to capture agent edits, shell commands, MCP tool activity, and session-stop signals used by RL4 workflows.
  • May install/update these rule files in .cursor/rules/: RL4-Core.mdc, Rl4-Skills.mdc, RL4-Snapshot.mdc, RL4-ProofContract.mdc, RL4-Mode-Ask.mdc, RL4-Mode-Plan.mdc, RL4-Mode-Debug.mdc, RL4-Mode-Discovery.mdc, RL4-Mode-Audit.mdc, RL4-Mode-Team.mdc, RL4-Mode-Next.mdc, RL4-Mode-Undone.mdc. Once created, Rl4-Skills.mdc is maintained incrementally, not reset wholesale on each run.

B) RL4 account & cloud services

RL4 can operate locally, but account-linked features use cloud services. When you sign in or activate dashboard/team sync, RL4 may call endpoints on rl4.ai and process account/workspace data through Supabase-backed services for authentication, workspace/team management, synchronization, operational metrics, and error telemetry. Local evidence files remain in .rl4/; cloud transfer scope depends on enabled features.

C) Dashboard & team sync (opt-in)

When you sign in to the RL4 dashboard or enable team workspace features, some account and workspace metadata may be processed on infrastructure that uses Supabase (TO COMPLETE: subprocessors, retention, EU hosting statements). Solo local use does not require this.

D) Storage, retention, deletion

  • Local: data remains until you delete .rl4/, clear IDE extension storage, or uninstall.
  • Cloud: governed by dashboard account controls TO COMPLETE.

E) Your rights

  • Access/export: you control local files; dashboard rights TO COMPLETE per GDPR.
  • Deletion: remove local .rl4/ and disconnect dashboard TO COMPLETE.

Third-party services

When you use LLMs inside Cursor, VS Code, Claude Code, or Codex, their providers' terms apply to those sessions. RL4 does not replace those terms.

  • Anthropic (Claude)
  • OpenAI (Codex / API tools you configure)
  • Other providers you attach via MCP or IDE
Back to home