InboxSquireInboxSquire

Trust & privacy

Privacy at InboxSquire

Email access is sensitive. Here is exactly how InboxSquire handles it during beta — and what it deliberately does not claim.

Last updated · May 31, 2026

What this covers

This page explains how InboxSquire handles email data during its private beta. It is written to be precise rather than reassuring. If something is not yet true, we do not claim it.

InboxSquire needs permission to analyze selected email content in order to classify and route messages. During beta, access is limited, transparent, and revocable. Do not connect sensitive inboxes unless you understand the current beta limitations.

What we access

When you choose to connect Gmail or Google Workspace, you grant access through Google's OAuth consent screen. You see and approve the specific scopes before anything connects.

During beta we favor read-first scopes. We avoid scopes that allow sending or deleting on your behalf until they are genuinely required and clearly disclosed.

How we use email content

Connected email content is processed to classify messages, score signal, summarize threads, suggest drafts, and route important items to your chosen agents.

Processing email content is necessary for the product to work. We are explicit about this rather than claiming your email is never read or never processed.

What we store and for how long

We aim to retain the minimum data needed to provide classification, routing, and your audit log. Retention is being made configurable, and we will document concrete defaults as the beta hardens.

We do not claim zero storage or zero processing. Where we can avoid retaining raw content, we will, and we will tell you what is kept.

What does not happen by default

No destructive actions are enabled by default. InboxSquire does not auto-delete, auto-archive in bulk, or send replies without your approval.

Drafts, routing, and SMS escalations are presented for human approval. Automation rules require you to explicitly configure and confirm them.

Sharing with the agent fleet

When you enable routing, structured events derived from your email may be passed to the agents you select — AltBot, Kane, Midas, MiniCFO, HAMR, or TextAlerts — so they can act on your behalf with your approval.

You control which agents are enabled and can disable routing at any time.

Your controls

You can disconnect a connected inbox at any time, which revokes ongoing access. You can request deletion of your account and associated data.

Your audit log records classification, routing, draft, approval, and completed-action events so you can see what happened.

Beta limitations

InboxSquire is beta software. Features, scopes, retention defaults, and integrations may change. We have not completed third-party security certifications and do not claim them.

Until Google OAuth verification and any required security assessment are complete, treat InboxSquire as a limited, opt-in beta — not a compliance-grade system for regulated data.

Contact

Questions about privacy or data handling can go to the InboxSquire team via the contact page. This document will be updated as the product and its data practices mature.