Your sessions are yours.

The plugin: local state, no RetroPair cloud account

RetroPair 0.2.0 keeps configuration, sanitized log copies, review history and reports in .retropair/ in your project. A registry and shared defaults live in ~/.retropair/. The plugin has no RetroPair server, account or telemetry. You control retention and report sharing.

Analysis uses your configured model provider

Collector, judge and critic agents run through your Claude Code account. Sanitized log context, relevant facts, open recommendations and a limited profile slice can reach that provider under its terms. This is not an entirely offline workflow. Review your organization's policy before using work sessions.

Sanitization reduces exposure; it is not a guarantee

Rule-based sanitization replaces supported secrets, contact details, home-directory logins, configured names and custom patterns before copies are analyzed. Original session logs are not modified. Rules cannot reliably identify every confidential passage or name; inspect sanitized copies and configure additional rules when needed.

Approval and report separation

In team and course modes, feedback requires reviewer approval. Personal report data is built from allowed fields and excludes reviewer notes, draft feedback and other people's records. The group report can include approved feedback from everyone; do not send it as if it were a personal file.

This website: pilot requests

When enabled, the form sends your request through the site server to self-hosted n8n, then through a dedicated Telegram bot to the project creator’s private inbox. The recipient can read the fields you submit, submission time, limited campaign attribution, landing path and referrer origin. Telegram processes the message under its own policies. Do not submit credentials, session logs or confidential code. No full referring URL is needed. A deployment may alternatively use the documented Supabase storage adapter.

Abuse prevention and retention

The n8n delivery workflow stores hashed abuse-prevention and deduplication identifiers, delivery status and a Telegram message identifier, rather than form content in its database. It disables saved execution payloads. Delivery metadata older than 24 hours is pruned on authenticated requests; cleanup does not run while there are no requests. The Telegram inbox is managed by the creator: message deletion is manual, with no promised automatic expiration. If Supabase is selected instead, its documented 180-day lead cleanup and 24-hour rate-limit cleanup must be configured by the operator.

Optional website analytics

When configured, Yandex.Metrika measures page visits, clicks, control changes and product-interest events. Google Analytics 4 is optional; Vercel measures page visits and performance, without custom conversion events. All load only after your analytics consent; withdrawing consent stops new events. Event data uses bounded interface identifiers and limited campaign attribution, never your email or form responses. Webvisor and automatic form recording are disabled. Analytics providers can receive your IP address and device information and may use cookies under their policies. Retention depends on provider settings. Change your choice in the footer. Plugin privacy is separate from website analytics.

Questions or deletion requests

The project creator operates this site under the Prodfeat.ai brand. For a question or deletion request, use the contact form and identify the email used for your application. You can also follow the creator link to Prodfeat.ai in the footer. If submission is unavailable, the site displays that state and does not claim to accept or store an application.

← Back to product Inspect the workflow →