Surfbots Inbox Privacy Policy

This policy explains how Surfbots Inbox handles information used to connect email, organize conversations and prepare owner-approved replies. It covers the Surfbots-hosted Inbox. If another organization hosts its own installation, ask that operator for its applicable policy.

Who operates the service

Surfbots Inbox is provided by Surfbots.ai, operated by Farid Shahlavi. Contact surfbotsinbox@gmail.com about privacy, account information or deletion. Effective date: September 27, 2026.

Information we access and store

Why email access is requested

Read permission supports importing and displaying conversations, classifying requests, preparing drafts and checking matching sent replies. Send permission supports replies explicitly reviewed and approved by a workspace owner. Optional Gmail modification permission supports managed labels and optional finished-email archiving. Optional Microsoft mail and mailbox-settings modification permissions support managed Outlook categories and finished-email archiving. Organizer does not delete email or change read status. Read-only connections do not send replies. Microsoft profile permission identifies the connected mailbox, and offline access allows background synchronization.

Availability depends on the installation. Outlook and shared-app features require provider configuration and mailbox authorization on the installation you use. We request permissions for enabled connection features, not access to every mailbox in an organization.

Optional calendar synchronization

With separate authorization and enablement, Inbox writes tracked response deadlines to a dedicated Google or Microsoft calendar. Google access uses the app-created calendar scope. Microsoft delegated calendar permission is broader, but Inbox manages only its dedicated calendar and linked events. Stored synchronization records include calendar and event identifiers, ownership markers, deadlines, settings and operational status.

Events contain a response deadline, status, conversation number and authenticated link to Inbox. Email subjects are included only when enabled; bodies and attachments are not exported. Events are marked private and available, have no attendees, and can have optional provider reminders. Visibility also depends on your provider’s calendar-sharing controls. Calendar edits do not change Inbox deadlines. Inbox removes linked events when requests are answered, resolved or no longer tracked. Pause leaves events and reminders in place. To remove them, use Stop and remove synced events while the account remains connected; revoking access or disconnecting prevents further updates and removal.

Local history cleanup

Owners can preview removing inactive finished conversation history from Surfbots without deleting provider email. Minimal hashed mailbox/message fingerprints remain to prevent reimport, alongside content-free accountability records. Backups retain removed content until their normal expiry. Unfinished work is protected by the cleanup flow.

AI processing

When configured, relevant email content, contact preferences, context guidance and conversation history are sent to the classification or generation service assigned to the workspace. Supported configurations include TypeSafe/Jev, local models, OpenAI-compatible services and Azure OpenAI. The services actually used depend on the installation’s configuration. Ask the operator which providers process your workspace’s messages before connecting. Drafts can be inaccurate and require human review.

Connected email data and content derived from it are not used to train AI models. AI processing is used to provide the configured classification, reply-assistance and optional image-advice features. This no-training policy applies to the services configured to process connected email.

Email formatting and remote images

Inbox stores a sanitized HTML version of imported email alongside plain text for display. Remote images are blocked by default. Choosing Load images, or explicitly allowing images from a sender, sends requests from your browser to the image host. Those requests may reveal your IP address and when you opened the message. Sender permissions are personal to your account within each workspace and can be removed in Manage trusted senders. Sender addresses can be shared or spoofed. Jev image advice uses the sender address and message text without fetching images or following links; it does not verify identity, guarantee safety, or enable image loading.

Who can access information

Members of a workspace can read its shared mailboxes according to their role. Connecting an account makes its imported conversations available to that workspace’s members. App configuration shared across workspaces does not share their mail or grant membership. Platform-owner application privileges alone do not provide business-mail access; authorized infrastructure operators can have administrative access needed to operate the service.

Hosting, identity, email and AI providers process information needed to supply their configured services. Any access by support personnel must be limited to the purpose and authorization applicable to the request. Legal or security disclosures may be necessary where applicable law requires or permits them.

Google user data and Limited Use

Surfbots Inbox uses Google API data to provide the email features described here. Use and transfer of that information adheres to the Google API Services User Data Policy, including its Limited Use requirements. Google user data is not sold, used for advertising or credit decisions, or used to train AI models.

See the Google API Services User Data Policy.

Retention, disconnecting and deletion

Disconnecting stops future use of the saved connection and removes its saved web sign-in credentials. An operation already in progress may finish. Disconnecting does not itself erase imported history, revoke provider-side consent, or delete messages from Google or Microsoft. You can also revoke access through your provider’s account settings.

Workspace owners can preview and clear imported email history in Data management. This removes applicable local message records and drafts while preserving connection settings and content-free audit records. Contacts and context profiles are separate records. Contact the operator for account deletion or information outside the history-clear function. Source mailbox messages are not deleted by clearing Inbox history.

Imported information remains in the active service until cleared or deleted on request. We honor deletion requests. After verifying the requester’s identity, authority and the data to delete, we remove the applicable data from active systems promptly and within 7 days. Email surfbotsinbox@gmail.com to request deletion. A dedicated in-app deletion-request button is planned; it is not yet available. Any information that must be retained by law will be identified when responding to the request. Backup copies containing the deleted data are removed within 30 days after the verified request. Until removal, those copies are restricted to disaster recovery and are not used for normal service processing. If a backup must be restored, the applicable deletions are reapplied before the restored data is made available. This backup period does not delay removal from active systems.

Security and session information

Hosted access uses HTTPS. Saved OAuth secrets are encrypted using an installation key. Membership and role checks restrict application access. Sign-in uses session cookies and request-forgery protections. These measures do not eliminate all security risk. Keep account credentials private and promptly report suspected misuse.

Workspace deletion and backup controls

Local and hosted Inbox provide platform-owner workspace deletion and automatic expiry of managed database backups. Workspace deletion removes the selected business’s Inbox records and connections, while preserving original provider emails, shared sign-in identities and a minimal administrative deletion record. Default workspace is protected. A separate recovery record prevents access to a deleted workspace restored from an older backup; operators must complete restore cleanup before resuming service. Copies outside the managed backup folder require separate handling. These controls do not replace the deletion-request process and retention commitments above.

Your choices and policy updates

You can choose read-only access, pause or disconnect accounts, ask your workspace owner about membership and history, and contact the operator about access, correction or deletion requests. Applicable rights depend on your location and relationship to the workspace. Material changes will be explained through the service or another appropriate notice; consent will be requested when required before a new use of provider data.