Data retention

Last updated: March 28, 2026 · InboxPilot AI (Chrome extension) · eRevolutions India

InboxPilot AI stores most data locally in your browser via Chrome extension storage. There is no InboxPilot-operated server in the public release that centrally retains your mail content or extension database.

Local extension data

• Settings, categories, rules, encrypted API key (sync storage): Retained until you change or remove them, or until you uninstall the extension or clear extension data for InboxPilot in Chrome. If you use Chrome Sync, copies may exist on other signed-in devices per Google’s sync behavior.
• Device key material (local storage): Retained until cleared with extension data or uninstall. Needed to decrypt your stored API key.
• Classification cache (local storage): Short-lived by design (on the order of tens of minutes) to avoid repeat AI calls for the same row context. Entries expire as implemented in the extension version you run.
• Behavior events and digest aggregates (local storage): Stored in capped structures; older entries may roll off as new events arrive.

AI provider retention

When you enable AI, snippets you send are processed by your chosen provider under their terms and retention practices. InboxPilot does not control provider logs. Revoke or rotate your API key with the provider if you need to limit future processing.

How to delete your data

• Disable AI in Options and remove your API key material from the extension.
• Clear InboxPilot’s storage: Chrome → Extensions → InboxPilot AI → Details → “Remove extension” or use Chrome’s site data / extension data tools as applicable.
• For provider-side logs or copies, use the provider’s account and support channels.

Updates

If a future version adds a backend or cloud sync operated by eRevolutions India, this retention page will be updated with specific retention periods, deletion workflows, and legal bases.

Related: Privacy policy · Data processing · Home