Privacy policy
Last updated: October 17, 2026
Who we are
Botinto is operated by the Botinto service operator (legal details pending). Contact info@botinto.com about privacy or your data.
Information we process
We process account names, email addresses, password hashes, team memberships, workspace settings, customer chat messages, contact details voluntarily shared in the widget, approved knowledge text, AI usage, payment identifiers, and security activity. We use an essential session cookie to keep account holders signed in. The chat widget stores a random visitor token in the website visitor’s local storage to reconnect their conversation on that website.
Why we process it
We use this information to provide customer conversations, account access, verification emails, human handoff, billing, troubleshooting, and abuse prevention. Website visitors should contact the business they are chatting with to understand that business’s purposes and policies. Workspace owners decide what business and customer information to add and are responsible for appropriate notices and permissions.
Live visitor assistance and visit reports
When enabled by a workspace, the website widget records a random browser visitor identifier, a visit identifier, website origin, page paths and titles, visit times, approximate visible time, referring website host, browser/device category, language, and country code when available from the configured Cloudflare connection. Page URL queries and fragments are excluded. These reports do not contain raw IP addresses, precise location, keystrokes, form contents, screenshots, or session recordings. Page paths and titles can still contain personal information, so website owners should avoid tracking sensitive pages.
Visit tracking can start when the widget loads, before you open chat. The website’s team can view connected visitors and send a message beside the chat button. We record browser delivery, visible chat opening, and replies for these messages. Names and email addresses appear only when shared through chat or added to the customer record. The widget uses local storage for its random identifier and visit-privacy choice, and session storage to group page views. Select Visit privacy inside the chat to pause or allow visit activity. Chat remains available when visit tracking is paused. A workspace can require permission before recording visits and integrate this choice with its website’s consent tool. This tracking is separate from Google Analytics.
Optional website analytics
With your consent, we use Google Analytics (measurement ID G-151MGG7ZD0) to understand visits to public marketing pages. The analytics loader does not run on account, dashboard, or admin pages. We do not send chat content or account details to Analytics. You can accept, decline, or change your choice through Cookie preferences in the footer. Analytics may use cookies and process usage information through Google. Advertising storage, advertising user data, and ad personalization are disabled by this implementation.
Service providers
The service runs on shared hosting, with Cloudflare for domain, security, email routing and private R2 email storage. Brevo delivers account emails. When AI replies are enabled, relevant customer messages, recent conversation context, and selected approved knowledge are sent to the configured AI provider (Google Gemini, with an optional OpenAI fallback). Razorpay or PayPal handles checkout; Botinto does not store complete card numbers. Providers may process information in countries other than your own under their own contractual terms. Contact us to confirm the current providers and processing locations for your account.
Google sign-in
Google sign-in requests only your identity, name, and verified email. Google sign-in does not grant mailbox access. Separately, you can forward new Gmail or business emails to Botinto and configure SMTP sending.
Email inbox
Forwarding processes new arrivals addressed to your private Botinto receiving address. We store sender and recipient details, subjects, searchable message text, ticket state and encrypted sending credentials in the application database. Complete incoming emails and received attachments are stored in a private Cloudflare R2 bucket. Signed download links are issued after checking workspace access. AI reply drafts use relevant message context and approved knowledge; your team reviews and sends them. We do not send email-content alerts through WhatsApp or Telegram. Reading or moving a conversation to Botinto Trash does not change or delete the provider’s original. Configure forwarding to keep a provider copy. Sending uses your mailbox’s SMTP account; business Sent copies use a separate Sent-only connection.
Email Trash does not permanently erase cloud objects. R2 lifecycle rules and cloud-file deletion must be managed separately by the operator; database cleanup or workspace deletion does not automatically remove R2 objects. Contact the operator for email-file deletion requests.
Retention and deletion
The default retention for inactive conversations and audit history is 365 days, enforced by the scheduled worker. Visit records, page timelines, and associated outreach reporting expire after 90 days of inactivity by default; workspace owners can choose 7 to 365 days. Cleanup runs in batches. Visitor profiles are removed after the profile retention period when they have no remaining conversations or visits. Knowledge stays until deleted by a workspace administrator or the workspace is deleted. Owners can export workspace data and permanently delete the workspace in Settings. Payment providers may retain their own records. Backups follow the operator’s backup retention policy; contact us for the currently configured schedule.
Your choices and requests
Do not submit sensitive personal information through the chat widget. Request access, correction, export, or deletion through your workspace owner or info@botinto.com. We may need to verify your identity. Your rights depend on the law applicable to your circumstances.
Security and changes
We use access controls, encrypted transport when deployed with HTTPS, server-side secret storage, and tenant-scoped authorization. No service can guarantee absolute security. We will update this policy when the service changes.