Data notice

What Replumo records

Replumo records editing actions so a viewer can watch a writing process. It does not produce an AI-detection score or an authorship verdict.

Drafts in your browser

Before publication, draft text, titles, editing events and the local replay-management capability are stored in this browser using IndexedDB and local storage. Clearing browser data can remove them. Backups contain the same private capability, so store backup files securely.

Public replays

Creating a replay sends the final text and the recorded editing sequence to the server. The sequence can include text later deleted, pasted, dropped or replaced. Anyone with the public link can view it. Review the writing for sensitive information before publishing.

Disabling a replay

A signed-in owner or the browser holding the local writing capability can disable a replay. Replumo then makes the link unavailable and removes the stored event-log file. Minimal database metadata may remain to record that the replay was disabled and to prevent accidental re-publication.

Accounts and operations

Accounts store an email address, display name, password hash, verification state and session records. Operational logs contain request and error metadata; the logger is configured to redact passwords, tokens, final text and event content.

Your responsibility

Only publish material you are allowed to share. A replay reflects actions reported by the editor and should be interpreted as context—not conclusive proof about who wrote a text or which tools were used outside the editor.