Last updated
November 16, 2026.
This page is written for product transparency and describes how the service accesses, uses, stores, and shares personal information.
Data we collect
- Account details such as name, email, password hash, email verification status, session version, and authentication events.
- Sign in records: each time a workspace user signs in, the IP address the sign in came from, the country read from it with a database held on our own servers, the browser, operating system and device type, how they signed in, and when. The same address and country are kept on the session and on the workspace audit log entries for changes the user makes. A user sees their own sign ins in Account settings, workspace members who manage members see the sign ins of that workspace's members, and OrhanAI staff can see them to support the account and protect the platform.
- Workspace details such as workspace name, slug, owner, members, roles, settings, subscription status, and team seat usage.
- AI Agent configuration such as assistant name, goal, website setup answers, behavior, fallback message, suggested questions, lead capture settings, widget theme, domain allowlist, publish status, and runtime flow.
- Training data such as website URLs, sitemap pages, PDF, DOCX, TXT, CSV, images, audio, video, manual Q&A, plain text, file metadata, extracted chunks, embeddings, processing status, errors, and source counts.
- Widget conversation data such as visitor messages, assistant replies, source references, answer classification, response timing, flow state, handoff status, and timestamps.
- Phone call data when a workspace uses the Voice Agent, such as the caller's number, the number called, a forwarding number the workspace saves, call times and length, a transcript of what was said, a summary, a message the caller leaves, and whether the call was transferred. Call audio is passed to the AI provider live so the AI Agent can answer, and it is not recorded or stored.
- Outbound call campaign data when a workspace calls a list of contacts, such as the phone numbers, names and other columns the workspace uploads or picks from its contacts, the script and voicemail message, each call's outcome, transcript and summary, and the numbers on the workspace's Do Not Call list, including those added when a person asks not to be called again. Call audio is not recorded or stored.
- Phone numbers a carrier reports as not in service on one of our outbound calls, with the carrier's reason and when it was seen. They are kept on a list for the whole platform, after the workspace that called them is gone, so they are not dialled or added as contacts again, until OrhanAI staff take a number off once it is in service.
- Data about a call a workspace's team member places from their browser, such as the number called, the number shown, who placed it, its times, length and outcome. The call's audio passes through our telephony provider so the two people can talk. It is not recorded or stored, no AI hears it, and there is no transcript.
- Lead and contact data such as name, email, phone, company, message, source URL, visitor identifier, and related conversation.
- Visitor context used for analytics, such as page URL, the titles of the pages a visitor opens and when, how long a visit lasts (kept for 90 days), referrer, domain, country (read from the IP address with a database held on our own servers; the address itself is not stored), device type, browser, operating system, language, timezone, screen, viewport, visitor ID, and session ID.
- Billing records needed to connect a workspace with Stripe checkout, subscriptions, invoices, customer portal sessions, AI credit balances, and extra credit purchases.
- Support and notification data such as support chat messages, ticket category, subject, description, status, unread counts, admin broadcasts, in app notifications, and browser push subscription data when enabled.
Google user data
OrhanAI uses Google OAuth only when a workspace user chooses Google Sign In or connects Google Calendar for appointment booking. We request only the Google scopes needed for features selected by the user.
The Google OAuth permissions currently used by OrhanAI are openid, email, profile, https://www.googleapis.com/auth/calendar.freebusy, and https://www.googleapis.com/auth/calendar.events.
Data accessed
- Google Sign In: Google account ID, email address, email verification status, display name, and profile picture from the openid, email, and profile scopes.
- Google Calendar appointments: connected Google account email and name, OAuth access and refresh tokens, selected calendar ID, free and busy time blocks, and booking event data needed to create appointments, including event time, summary, attendee name, attendee email, optional phone, optional notes, Google event ID, and event link when returned.
Data usage
- Use Google account profile data to authenticate users, create or link accounts, enforce verified email access, and display the connected account in the dashboard.
- Use Google Calendar free and busy data to show available appointment times, and use Google Calendar event access to create appointments only after a visitor submits a booking through an enabled AI Agent flow.
- Store encrypted OAuth tokens so connected Google Calendar features continue working until the user disconnects the integration or revokes access in their Google Account.
Storage, sharing, and limits
- Google user data is stored only as needed to provide the connected feature, such as account login, integration connection status, appointment availability, and appointment booking records.
- When a visitor books an appointment, the appointment details entered by the visitor are sent to Google Calendar to create the calendar event.
- We do not sell Google user data, use it for advertising, transfer it to advertising platforms or data brokers, use it for credit decisions, or use Google Workspace API data to train generalized AI or ML models.
OrhanAI use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Users can disconnect Google account access in account settings, remove connected Google Calendar integrations in the dashboard, or revoke access from their Google Account permissions. Booking records are retained according to the product workflow, workspace deletion controls, and the retention terms described below.
How we use data
- Provide authentication, workspace access, dashboard pages, AI Agent configuration, and admin tools.
- Process training sources, generate chunks and embeddings, and retrieve approved business knowledge for the specific workspace and AI Agent that owns it.
- Serve the embedded widget, validate publish status and allowed domains, maintain visitor sessions, rate limit abuse, and count AI credits against the plan allowance.
- Generate AI Agent responses using relevant trained sources and bounded recent conversation context.
- Show conversations, source references, contacts, leads, analytics, usage, billing state, support tickets, and notifications to authorized users.
- Send verification, password reset, billing, service, support, and notification emails or push notifications when configured.
- Protect the service, debug failures, prevent fraud or abuse, and comply with legal obligations.
AI, training, and visitor conversations
OrhanAI is designed to answer from trained business knowledge first. Retrieval is scoped by workspace and AI Agent. When knowledge is missing or weak, the AI Agent can use the configured fallback instead of inventing an unsupported answer.
Visitor conversation history may be used as bounded recent context so the AI Agent can understand follow up questions. Internal prompts, service credentials, and private server configuration are not intentionally exposed through the public widget.
Answers are written by OrhanAI's default model, which is a Google Gemini or OpenAI GPT model, with Gemini as the backup. When a workspace sets an AI Agent to answer with a Claude or GPT model, the conversation it answers and the trained knowledge retrieved for it are sent to Anthropic or OpenAI to write the reply. When the workspace uses its own API key for that provider, the request is made with that key.
Service subprocessors
OrhanAI may rely on infrastructure and service vendors for database hosting, object storage, answer processing, payments, email delivery, hosting, push notifications, security, logging, and analytics. Exact vendors depend on the deployment configuration.
Payment card details are handled by Stripe. OrhanAI stores the identifiers needed to connect customers, subscriptions, invoices, and checkout or portal sessions to the correct workspace.
Your responsibilities when embedding the widget
- Disclose AI Agent conversation collection and lead capture to your website visitors.
- Do not upload training data that you are not allowed to process or expose through AI Agent answers.
- Keep domain allowlists accurate before publishing an AI Agent.
- Review answers, fallbacks, source references, suggested questions, lead forms, and handoff flows before relying on the AI Agent in production.
- Avoid collecting sensitive information through the widget unless you have the required legal basis, notices, and safeguards.
Security and retention
The app uses HTTP only signed cookies, email verification, session version invalidation, role aware workspace access, tenant scoped database queries, domain allowlists, server side validation, rate limits, prompt leakage blocking, and isolated widget styles. Production deployments should also configure HTTPS, monitoring, access controls, least privilege service credentials, and secret rotation.
Data is retained while needed to provide the service, enforce plan limits, maintain billing records, resolve disputes, protect the platform, or meet legal obligations. Deleting training sources or workspaces should remove related stored training objects and generated chunks according to the product workflow and subprocessor retention limits.
Sign in records, with their IP addresses, are deleted automatically 90 days after the sign in. A session keeps its address until it expires, 14 days after the sign in, and an audit log entry keeps it for as long as the workspace keeps its audit log.
Choices and rights
Depending on location and role, users or visitors may have rights to access, correct, export, delete, object to, or restrict processing of personal information. Workspace owners are responsible for responding to visitor requests connected to AI Agents they embed on their own websites.
Account users can manage profile and workspace settings in the dashboard. Other privacy requests can be sent to links@orhanai.com.
Children, changes, and contact
OrhanAI is intended for business use and is not directed to children. Do not knowingly collect data from children through public AI Agents unless you have the required rights, notices, and controls in place.
This notice may be updated as the product, subprocessors, deployment model, or legal requirements change. The date above shows the latest version.
Questions about this notice can be sent to links@orhanai.com.

