Privacy & data

# What stays local

Rift captures supported coding sessions in your project and serves Recall locally. Installing the alpha does not automatically upload code, prompts, session history, token usage, or savings reports to us. We do not receive an analytics feed from the CLI.

The local record can include prompts, tool activity, recorded edits, token counts, and checkpoints. Treat it as project data, especially when a task contains private source or customer information. Local storage still needs appropriate permissions and backup handling.

# Review capture settings

Open rift, select the project, and press s for Settings. Review capture, Recall, integration status, and raw-transcript settings before using Rift on sensitive work.

Redaction reduces the chance that recognised secrets enter captured records; it cannot guarantee detection of every secret. Raw transcripts may retain sensitive source and prompts. Review that setting rather than assuming every stored artifact is safe to share.

Saved summaries and file outlines use project-specific encryption. Keep project keys safe, and follow any key-related findings from rift doctor. Encryption of those artifacts does not mean that every file associated with a project is encrypted.

# When the network is used

• Installation and updates: downloads and update checks contact release hosting. Those requests are separate from project capture and do not submit your session history.
• Your coding agent: its model requests, authentication, and data handling follow its provider's policies. Rift does not change those policies.
• This website: website analytics and waitlist handling are covered by the site privacy policy. The website's GitHub stars button requests the repository's public star count from GitHub.
• Actions you take: posting an issue, sharing a file, or pushing project data to a remote has the sharing consequences of that action.

See updates if you want to turn off automatic update checks.

# Share on your terms

The alpha helps us find issues, prioritise features, and learn from real use. There is no automatic reporting of your results. You can choose to send a bug report, a feature request, or an observation, and you can use Rift without sending anything.

rift doctor --report

This read-only command produces a report for you to review. It includes counts, states, and versions, replacing paths, names, and messages with lengths. Nothing is submitted until you share it yourself. Avoid private source, prompts, credentials, and customer data in public feedback.

# Keep or remove local data

Disabling an integration keeps captured history. Uninstalling also preserves it by default. If you want to remove local caches and settings as well, read the uninstall guide first: a local purge still preserves captured Git records and repository policy files.