Privacy Policy

We process sign-in information, connected mail account metadata, product settings, individual subscription records, support messages, and usage information needed to operate BotNitro Email.

When you connect Gmail, Outlook, or iCloud Mail, we use the provider permissions or credentials you grant to synchronize, search, draft, and act on email. Providers remain authoritative for incoming mail bodies, threads, attachments, and mailbox state. BotNitro Email fetches that content when needed; its product database stores provider references, lightweight metadata, settings, source-linked Grok results, approvals, work state, operation receipts, and encrypted provider credentials.

Browsers and native apps cache mail content locally and preserve unsent edits separately from disposable caches. Browser unsent drafts are encrypted in local storage. Outgoing attachments may be staged in private BotNitro Email storage for provider upload and recovery; that staging is not automatically deleted based on age.

If you use features such as send, archive, trash, mark read or unread, flag, attachment download, or search, we may read, create, update, or transmit provider mail data through the connected provider account as needed to perform the action.

We use information to provide the product, authenticate users, synchronize mail accounts, maintain inbox configuration and work state, deliver notifications, troubleshoot issues, prevent abuse, and manage billing.

BotNitro Email processes relevant email content using Jev for classification and Grok 4.7 for summaries and draft preparation through Vercel AI Gateway. It stores derived message evidence and source-linked summaries to maintain your inbox. Your separately connected Grok Bot or compatible agent provides context, proposes bucket organization, and performs actions you approve. Webhook wakeups contain opaque identifiers rather than raw email.

BotNitro Email does not train models on connected email content, attachments, provider tokens, or derived email artifacts. Data retrieved by Grok is governed by your relationship with xAI and your Grok settings; BotNitro Email does not control that service's retention or model-training settings.

Your agent can read mail and handle related work only for the accounts you explicitly include in its disclosure grant. Connecting another mail account does not automatically grant agent access. Revoking the grant invalidates outstanding access and late responses; it cannot retract information already copied to an external service.

Grok-assisted output can be incomplete or wrong. The product is designed to support user review and explicit approval boundaries, not to make final legal, compliance, financial, medical, employment, or other regulated decisions for you.

Google, Microsoft, and Apple provide the mail services you choose to connect. BotNitro Email uses Clerk for sign-in and individual subscription management, Vercel for hosting, managed workflows, attachment staging and analytics, and Upstash for product state. Payment services involved in a purchase are identified through Clerk checkout.

Vercel AI Gateway routes hosted inference to TypeSafe AI and xAI. A separately connected Grok Bot or other agent may also have its own connectors and copied context. BotNitro Email permissions govern access through this product; they do not revoke independent external connectors or previously copied data.

We do not sell your personal information. We do not use connected email content for advertising.

We may update subprocessors as the product changes. Material updates will be reflected in this policy or another user-visible notice.

BotNitro Email retains account settings, derived results, unsent-work references and operation history to support recovery and avoid repeating uncertain actions. Unresolved work and unsent attachment staging do not expire solely because they are old. Personal-account deletion can be reviewed and requested from data settings. It requests immediate cancellation of the BotNitro Email subscription and remains pending until cancellation and any accepted external effects are verified.

Disconnecting a mail provider stops new BotNitro Email access for that connection and starts cleanup of cached mail metadata and dependent results. Requests already dispatched may still finish at the provider. Provider mail and provider drafts remain intact. BotNitro Email preserves unsent work, independent Bot tasks and operation history; disconnect is not full account deletion.

Your data settings provide exports of indexed BotNitro Email records and separately offer current-browser unsent-draft exports and staged attachment downloads. These exports are not a full mailbox backup or a point-in-time database backup. Provider draft bodies, older unindexed records and drafts stored only on another device may not be included.

Mac and iPhone settings can back up retained unsent drafts and available local attachment files as an unencrypted JSON file, limited to 1,000 drafts and 64 MiB of attachment bytes. Restore adds missing drafts to the same BotNitro Email account, preserves existing drafts, and requires status recovery for prior send attempts. A separate text-and-reference export remains available when attachment files cannot be read. These files exclude drafts stored only at a mail provider or on another device. Store downloaded files carefully; signing out of BotNitro Email does not remove a file you already saved.

Completed personal-account deletion covers live application records in Redis, account-owned files in BotNitro Email Blob storage, and the live Clerk sign-in identity. A minimal deletion receipt remains to block delayed work from recreating the account. Organization identities and older files without provable ownership require a separate review; deletion is not reported as complete while those checks are unresolved.

This cleanup does not erase vendor billing or audit records, managed Workflow histories, service logs, disaster-recovery backups, provider mail, or information already copied to an external agent. Those records follow the relevant provider's retention obligations and policies; this process does not claim they have been immediately erased. Contact us to clarify retention or request additional deletion or correction. Local unsent content and exported files require separate handling on the devices where they are stored.

We use technical and organizational safeguards intended to protect information, including OAuth-based provider access and encrypted secret storage where applicable. No internet service can guarantee absolute security.

Human access to connected provider data is limited to circumstances such as support you request, security investigation, legal compliance, or preventing abuse, and is restricted to personnel or subprocessors with a need to know.

Do not send secrets, passwords, or highly sensitive regulated information to the service unless your organization has approved that use.

You can choose which mail accounts to connect, disconnect providers, manage settings, export available data, and manage an individual subscription through Clerk Billing on the web. You can separately revoke the agent disclosure grant in Buckets and disconnect its callback routine in settings. Revocation blocks further scoped access through BotNitro Email, but cannot revoke independent Grok connectors.

Some requests may require identity verification and may be limited by security, legal, billing, or backup requirements.

Questions about privacy can be sent to info@tailoredai.solutions. We may update this policy as the product changes. The updated date shows the latest revision.