Privacy Policy

Customers are businesses and people who sign up for Vistrow Voice. For their account, team and billing data we decide why and how the data is used (in DPDP Act terms, we are the data fiduciary).

Callers are people who speak or chat with an AI agent that a Customer set up, by phone or through a website widget. The Customer decides who is called, what the agent asks, what is captured, whether the call is recorded, and how long it is kept. For that call data we act as the Customer's processor and follow their configuration. If you are a Caller and have a question about a specific call, contact that business first.

Our contact details are in section 15. This policy does not cover other tools a Customer connects to Vistrow Voice; those have their own policies.

Calls handled by Vistrow Voice are conducted by AI. To do that, call audio and text are sent to AI model and speech providers (section 6) that turn speech into text, generate the agent's replies, and turn replies back into speech. After a call, the transcript can also be sent to a language model to produce a summary, sentiment, outcome and follow-up suggestions.

AI responses can be wrong. Our Terms make Customers responsible for telling callers they are speaking to an AI where the law requires it. We do not sell call content or use it to advertise. What each provider may do with data it receives is governed by our agreement with it and its own terms.

As controller (Customers and visitors to our own site)

• Account data - name, email, optional phone number, password (stored only as a salted hash), role, workspace name, and how you heard about us. If you sign in with Google, GitHub or Slack we receive your verified email and name from them.
• Team data - names, emails and roles of teammates you invite.
• Acceptance records - which version of the Terms and Privacy Policy you accepted, and when.
• Sign-in and security data - the devices and browsers signed in to your account (browser user agent, last-seen time) and security events such as sign-ins and sign-outs. We use IP addresses to rate-limit sign-in and sign-up requests. When you accept the Terms and this policy at sign-up, we record the time, the version you accepted, your IP address and browser user agent, and your confirmation that you are 18 or older and authorised to act for the business, as evidence of that acceptance.
• Billing data - legal name, GSTIN, billing address and email, invoices, and payment and subscription identifiers from Razorpay. Card details are entered with Razorpay and are not stored by us.
• Support data - tickets and messages you send, the page you were on, and attachments, which we delete 14 days after a ticket is resolved.
• Usage and error data - API requests, error logs, and the actions the in-app AI assistant proposes and you approve.
• API keys - only a one-way hash and a short prefix; the full key is shown once.
• Demo and contact requests - details you submit on our website forms, which we email to our team.

As processor (on behalf of a Customer)

• Call data - call audio (only if the Customer turns recording on), live transcripts, call details (time, duration, channel, language), and the caller's phone number for phone calls.
• Details captured in the call - fields the Customer's agent is set up to collect, such as name, phone, email, company, budget, location, timeline and appointment details.
• Call intelligence - an AI-generated summary, sentiment, outcome, quality score and action items for a call.
• Caller memory - if a Customer turns it on for a phone agent, a short summary kept against the caller's phone number so the agent can recognise a returning caller.
• Contacts and campaigns - contact lists the Customer uploads or enters (including extra CSV columns), tags, notes, Do-Not-Call entries and outbound campaign progress.
• Website widget visitors - the name, phone and email the visitor types, chat messages or voice, the page path (not the full address), and a record that the visitor accepted the voice-call notice.
• Knowledge bases - documents, text and web pages the Customer gives the agent.

• To run the service: answer and place calls, run agents, show your dashboard, deliver leads to your connected tools, and book appointments in your Vistrow Voice calendar.
• To keep it secure and reliable: sign-in checks, abuse prevention, debugging, monitoring, and measuring how the product is used.
• To bill: invoices, tax records and payment reconciliation.
• To support you: answer tickets and, where needed, open a support session in your workspace (section 10).
• To communicate: service emails (verification, password reset, invites, receipts, alerts) and, only if you switch them on in your preferences, product updates.
• To comply with law and enforce our Terms.

We do not sell personal data and we do not use it for third-party advertising.

Call recording is off by default. A Customer must turn on "Record calls" in their Compliance settings. Transcripts are produced for calls so the agent can respond and the Customer can review them in the dashboard. Recordings are stored in private object storage and played back in the dashboard through short-lived links. Links a Customer shares with a connected tool (such as a CRM or spreadsheet) last longer and work for anyone who holds them, until they expire (90 days after the call by default; the Customer can choose 7, 30 or 90 days or no expiry), the Customer revokes them, or the recording or call is deleted. Links sent before link expiry was introduced in October 2026 do not expire until the Customer revokes them.

Customers are responsible for telling callers that a call is with an AI, recorded or transcribed, and for having a lawful basis for calling them. When a Customer records calls, the agent's opening line says by default that the call is recorded and that the caller is speaking with an AI assistant; the Customer can change that wording or turn it off. Vistrow Voice also offers a setting that makes the agent ask for spoken consent at the start of a call, and a notice and consent screen in the website widget before the microphone is used, which says the call is recorded only when the Customer records calls. The Customer decides which settings to use.

We use the providers below to run the service. Some apply only when a Customer chooses a particular voice, model, tool or integration. Each handles data under its own contract or terms and our instructions.

We may also disclose data when the law requires it, or to protect rights, safety or the security of the service. The list changes as the product does; we update this page when it does.

We use Google in two ways, and request only these permissions:

• Sign in with Google - scopes openid, email and profile. We read your verified email address and name to find or create your Vistrow Voice account. We do not keep a Google access token from sign-in.
• Google Sheets integration (optional) - scope https://www.googleapis.com/auth/drive.file (plus openid email, to show which Google account is connected). This scope only lets Vistrow Voice see files it created itself, never the rest of your Drive. We create one spreadsheet called "Vistrow Voice - Leads" in your Drive, format it, and add a row for each lead your agent captures (date and time, name, phone, email, company, channel, agent, language, duration, details, page, a recording link and call ID). We store the access and refresh tokens Google gives us so we can keep adding rows. We do not read your other spreadsheets, files, contacts or calendar.

Vistrow Voice does not connect to Google Calendar. Appointments booked by your agents are kept in the calendar inside Vistrow Voice.

Vistrow Voice's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

In particular, for information received from Google APIs:

• We use it only to provide the user-facing features you asked for: signing you in and writing your leads to your own spreadsheet.
• We do not use it for advertising, including retargeting or interest-based ads, and we do not sell it.
• We do not allow people to read it, except with your consent for specific data, where needed for security (for example investigating abuse), to comply with law, or when it is aggregated and anonymised for internal operations.
• We do not transfer it to others except to provide these features, to follow the law, or as part of a merger or sale where you are notified. Leads written to your sheet go to your own Google account.
• We do not use it to develop, improve or train generalised AI or machine-learning models.

To disconnect, use the Integrations page in your dashboard: we ask Google to revoke our access and delete the stored tokens. You can also remove access in your Google Account permissions. Disconnecting does not delete the spreadsheet or rows already in your Drive; you can delete them yourself.

Facebook and Instagram Lead Ads (Meta)

If a Customer connects Facebook and Instagram Lead Ads (optional), the Customer signs in with Facebook in a pop-up window and chooses which Pages, ad accounts and Pixels to share. We request only these permissions: pages_show_list, business_management, pages_manage_metadata, pages_read_engagement, pages_manage_ads, leads_retrieval, ads_read and ads_management.

• What we read - the list of Pages you shared; each Page's lead forms and their questions; each new lead's answers (for example name, phone, email and any custom questions); the ad, ad set and campaign the lead came from, with their names; and the Facebook ID and name of the person who connected.
• What we do with it - subscribe the Pages you choose to new-lead notifications, save each lead as a contact in your workspace, and have the agent you assigned to that Page, form or ad call the lead. You see every lead and its outcome in your dashboard. We do not create, edit or pause your ads, and we do not post to your Pages.
• Tokens - the access tokens Meta gives us are stored encrypted and are never sent to your browser.
• Who sees it - only your workspace. Lead answers go to the voice and language providers in section 6 only as needed to make the call. We do not sell this data, use it for advertising, or use it to train AI models.

To disconnect, use the Integrations page in your dashboard: we unsubscribe your Pages and delete the stored tokens. You can also remove Vistrow Voice in your Facebook settings under Business Integrations; when you do, Meta tells us and we stop reading leads. If you ask Meta to delete your data, Meta sends us a deletion request and we erase the connecting person's tokens, Facebook ID and name; you get a confirmation code to check the status. Leads already saved stay in the Customer's workspace as the business's own records until the Customer deletes them (section 9). Our use of data from Meta follows the Meta Platform Terms.

Vistrow Voice is built for Indian businesses, but our providers process data in several countries. Our application database and hosting (Railway) and our recording and backup storage (Backblaze B2) are in the United States, and voice, speech and language providers process data in their own regions. This means account data, transcripts and recordings can be transferred outside India. The DPDP Act permits transfers except to countries the Government of India restricts, and we require each provider to protect data under its contract or terms. We do not currently offer India-only data residency.

• Calls (recordings, transcripts, captured details, call intelligence) - kept until deleted. A Customer can set a retention period in days under Compliance settings; calls older than that are deleted automatically each day, together with their recordings, the integration delivery log entries for them, and any caller memory not refreshed by a call within that period. By default no period is set. A Customer can also delete a call's recording at any time.
• Contacts, notes, appointments and campaigns - kept until the Customer deletes them or the account is deleted. The retention setting above does not remove these.
• Account data - kept while the account is active and, after closure, for as long as needed to meet legal, tax and accounting obligations.
• Billing records - kept as long as tax and accounting law requires.
• Support attachments - deleted 14 days after the ticket is resolved. Ticket text is kept.
• Backups - we take a daily database backup and keep each for 30 days, so deleted data can remain in a backup for up to that long.

What we do today:

• Data in transit is encrypted with HTTPS/TLS, and our responses tell browsers to use HTTPS only.
• Passwords are stored as salted hashes. Sessions use signed tokens in HTTP-only cookies and expire. You can see the devices signed in to your account and sign out the others.
• Workspace data is scoped to the signed-in workspace, with owner, admin, member and viewer roles.
• API keys are stored hashed.
• Actions proposed by the in-app AI assistant need your approval before they run, and are logged.
• Support access: authorised Vistrow Voice staff can open a time-limited support session ("view as") in your workspace to investigate a problem. It lasts at most two hours, shows a banner, appears in your list of signed-in devices where you can end it, is recorded in an audit log, and cannot delete data or change billing, team or API keys.

No system is perfectly secure, and we do not currently claim any third-party security certification. See our Security page for the controls and the gaps. If a personal data breach affects data we hold, we will notify affected Customers without undue delay and as the law requires. To report a vulnerability, email support@vistrowvoice.com.

Under the Digital Personal Data Protection Act, 2023, and similar laws elsewhere, you may have the right to access your data, correct it, have it erased, nominate someone to act for you, and have your grievances addressed. Customers can:

• Export data - Settings has a data export that downloads your profile and, for owners and admins, workspace data (agents, calls, contacts, appointments, knowledge bases, billing summary).
• Correct data - edit your profile, contacts and agents in the dashboard.
• Request account deletion - Settings has a deletion request. We verify it is you, then review it within 2 business days of receiving it. You can cancel until we start processing it. We may keep what the law requires us to keep (section 9).
• Withdraw consent - turn off optional emails in your preferences, disconnect integrations, or stop using the service.

If you are a Caller, the business that called you or that runs the agent decides what happens to your call data. Ask that business first. If you contact us, we will pass the request to that business and help them act on it.

Grievances: if you have a concern about how we handle personal data, write to support@vistrowvoice.com with "Privacy" in the subject and enough detail for us to find your data. If we cannot resolve it, you may complain to the Data Protection Board of India once it is operational.

Essential. When you sign in we set HTTP-only cookies to keep you signed in (up to 30 days) and to recognise your device in your list of signed-in devices (up to a year), plus short-lived cookies while you connect Google, Slack or similar services. The dashboard also stores display preferences (theme, sidebar, table widths, time zone) in your browser's local storage. Without these the dashboard will not work properly.

Analytics. On our website and app we use Google Analytics, Microsoft Clarity and Vercel Web Analytics to understand how the product is used: pages viewed, clicks, scrolling and, on our public website, session replays and heatmaps. Text typed into form fields and the live demo's transcript are masked. Inside the app all on-screen text is masked, so call transcripts, contacts and leads are not captured; sessions are tagged only with a workspace ID. Microsoft processes Clarity data under the Microsoft Privacy Statement. Our cookie banner lets you choose Accept all, Necessary only, or Customize. Google Analytics loads only if you allow Analytics, and Microsoft Clarity loads only if you allow Session insights; if you choose Necessary only or do not answer, neither is loaded. We remember your choice in your browser's local storage; to change it, clear this site's data in your browser and choose again. Vercel Web Analytics does not use cookies or store anything in your browser, so it runs without that choice. We do not use advertising cookies.

Website widget. The widget on a Customer's site stores a note in your browser that you accepted the voice-call notice, and a flag that you dismissed its greeting for that tab. It sets no cookies. It sends the Customer's system the details you type into it. The Customer's own site can see the widget's events (for example that a call started or a form was submitted), but not the name, phone number or email you typed.

Vistrow Voice is a business tool and is not directed at children. We do not knowingly collect personal data from anyone under 18. If you think a child's data has reached us, contact us and we will delete it.

We update the date at the top of this page when we make changes, and for material changes we notify active Customers by email.

Vistrow Voice is operated by Vistrow Technologies Pvt. Ltd. Questions, requests and grievances about this policy: support@vistrowvoice.com. See also our Terms of Service and Security page.