Legal
Privacy
Version 2.4 · Effective 16 November 2026
Your data is held by Trustane, a micro enterprise registered in India, No 33, 1st Floor, 1st Main, Ganga Nagar, Gramatana, HMT Layout, CBI Main Rd, Bengaluru, Karnataka 560032, India. Questions: privacy@trustane.com or +1 (561) 960-0930 (from India +91 80 3193 1247).
1. What we collect
- Order details: company, name, email, optional Telegram handle, agent count, region, current host, and the description of your campaigns.
- Account details: phone number, business address and time zone, the use cases and markets you declare for your campaigns, and how you heard about us.
- Phone check: when you confirm your phone number, we text a code to it through Prelude, which receives the number, your internet address and your browser, to send the code and to check the request for fraud. Before the code is sent, we also ask Prelude what kind of line the number is, which carrier serves it, and whether it was moved from another carrier or is temporary; for this only the number is sent. An internet phone number or a temporary number cannot be used for the free trial. We keep each request (the number, its country, the time, the result, that answer and your internet address); for the number you confirm, the answer is also kept with your account.
- Calls and video meetings you book with us: your name, email address, the time you chose and your time zone, kept with our calendar entry and sent in the invitation. We confirm the email address with a code. If you booked from our website without an account, the record of that visit (the pages, the referring site and the campaign tags, section 1) is kept with the booking, so we know how you found us. During a meeting, audio and video go directly between the participants’ browsers, encrypted, or, when a direct path is not possible, through a relay run by Cloudflare, which passes the encrypted stream on without being able to see or hear it. We do not record meetings or keep the chat. Each browser also reports call-quality figures every 30 seconds (the kind of connection, delay, packet loss, bandwidth and video size; never your internet address or device), kept with the meeting so we can fix poor calls and track the relay’s cost.
- Sign-in records: the time, IP address and browser of each sign-in, and the network that address belongs to and its country, which we learn from a third-party lookup service (ipapi.is). Used to keep your account secure; kept for 180 days.
- Your agreement to our terms: when you agreed to the Terms of service and this policy, which version of each, and the internet address and browser you agreed from. It is kept with your account for as long as the account exists, as the record that you agreed.
- Verification documents: only when we ask for them: for example a company registration, proof of address, a director’s ID, a consent-record sample or a licence. Before we supply phone numbers or voice calling, the verification set out in section 6 of the Terms of service.
- Call records: only for phone numbers and voice calling we supply: for each call, the number called, the caller ID, the time, the duration and the cost. Used to bill you, to meet the carrier’s and the law’s requirements, and to check that the calling is manual and one-to-one.
- Account and billing records: balance, transactions, invoices, and the payment reference you used. For payments taken through a provider we also store that provider’s order and payment identifiers, so a payment can be traced to the transaction it settled. For each payment attempt we also keep its outcome, the reason the payment provider gave, and the card facts the provider reports: the network, the type, the issuing country and the last four digits. We do not receive or store card numbers.
- Support chat: what you write in the chat on our website or in the console, our replies, and, if you are not signed in, the name and email address you give us so we can answer you. An AI assistant answers first. When you are signed in, it reads your own account to answer: your servers, your balance and plan, recent top-ups, your payment attempts and the reason each one did not go through, and your bookings. It only reads; it changes nothing. If you ask for a person, the conversation goes to our staff, and their reply comes back in the chat or by email. We use the name and email only to answer you, never for marketing.
- Operational data: server metrics and system logs, used for monitoring, capacity planning and abuse detection.
- Web analytics: request logs including IP address and user agent, retained for 30 days. Separately, our own visit counter records the page, the referring site, campaign tags, country and device type, and, when the visit came from a click on one of our Google ads, Google’s click ID for that click. It uses no cookies. For each visit it also keeps your IP address, the city and region that address is in (as our network provider, Cloudflare, reads it), and the network that owns it (from the lookup service ipapi.is), so we can see where visitors come from and tell people from automated traffic. To count unique visitors, your IP address and browser are also combined with a random value that changes every day into a code that cannot be followed from one day to the next. Visit records are kept for 400 days. When you create an account, the referring site, campaign tags, that click ID and first page of that day’s visit are copied to your account, so we know how you found us. A browser that sends Global Privacy Control is not counted.
- Visit recordings: on our public pages and the sign-up page, the visit counter also records what you do on the page: the page as it looked, where you scroll, click and move the pointer, and which pages you open, so we can see where our site is hard to use. Everything you type, and the email address a sign-up code was sent to, is hidden in your browser before anything is sent. Your account, the console and the support chat are never recorded. A recording is kept with the visit record it belongs to for 30 days, then deleted. Like the visit counter, it uses no cookies and is not made when your browser sends Global Privacy Control or Do Not Track.
Signup checks for the free trial. So that one person cannot take the free trial again and again, we check each new account once, when its email address is confirmed. We look at the email’s domain (a disposable mailbox, a free mail provider, or a company domain with a working website); the internet address you signed up from, which we send to a third-party lookup service (ipapi.is) to learn whether it belongs to a datacenter, a VPN or proxy, or the Tor network, and which we compare with the Tor project’s public list; whether another trial was started from the same network in the last 30 days; how quickly the address was confirmed; and a device hash: a one-way code your browser computes from how it draws text, its graphics chip, screen, time zone, languages and platform. Only the hash reaches us, and we keep it in a keyed form that cannot be turned back into those details or matched against your browser by anyone else. The sign-up form also shows a Cloudflare Turnstile check; Cloudflare receives your address and browser details to tell people from scripts, and may set its own cookie from its own domain. While the free trial is offered, an address at a disposable mailbox cannot sign up. The result of these checks is a score that decides whether a trial can start at once or waits for one of us to look at it; a trial for a phone number from a country we do not start at once always waits for one of us. It is not used for advertising and is not shared with anyone else. These records are kept for 12 months and then deleted.
2. What we do not collect
Your dialer’s data (leads, call logs, recordings and your customers’ details) lives on your server. Our console reads and writes it for you, through the dialer’s own interfaces, to show your reports, Floor and recordings and to load the leads and do-not-call numbers you send us. We do not use it for anything else. Some of it leaves your server: a nightly backup of the dialer’s database in our storage in the EU (the last 14 are kept), lead files you upload (kept on our systems for 30 days), recording downloads you ask for (24 hours), and a record of each lead sent through the leads API (the time, the sending address, the outcome and the field names, with phone numbers cut to their last four digits; 90 days). Our staff open your server only when you ask us to, or when responding to a confirmed security incident, and that access is logged.
AI Agents are different: those calls run on our systems, not only on your server. Section 3 says what we process for them.
3. AI Agents and calls we make
When you use our AI Agents, an AI answers or places calls for you. To do that we process the calls themselves:
- What: the phone number and voice of the person on the call, what is said (a written transcript), a recording of the call, the details the agent collects (for example a name, an appointment time or the reason for the call), and an AI-written summary and score of the call.
- Why: to hold the conversation, to put the call through to your people when the agent should, to show you the call, its recording and its summary, to bill you for it, and to detect abuse. We do not use your calls for advertising, and we do not train AI models on them ourselves. Deepgram is set not to use the audio to improve its models on every call, and Microsoft’s terms say it does not train on customer data. The language models and voices reached through Deepgram are covered by Deepgram’s own terms with their makers.
- Who processes it for us: the providers that hear, think and speak during the call include Deepgram (speech recognition, voices and the agent, with language models from OpenAI or Anthropic), Microsoft Azure (speech-to-speech calls, some languages, call summaries and knowledge search), Ultravox (some customer agents) and Cartesia (which, through Deepgram, speaks the agent’s own words in an Indian English voice and never hears the caller); the phone carriers that connect the call; and our hosting providers, Hetzner for the call servers and Vultr for our application and its database. They may process the call outside the country you or the person on the call are in, and may keep what they process for a limited time under their own terms: Microsoft, for example, can keep text it processes for up to 30 days to check for abuse.
- Your role and ours: for calls with your callers and your leads, you decide why the calls are made, and we process them on your behalf. You are responsible for telling the people your agents call, or who call you, that they are speaking with an AI and that the call is recorded, wherever the law requires it, and for having the right to call them. Our Acceptable Use Policy sets out the rest.
- Calls we make to you: we may call you about your account or your setup, for example to help you finish it. These calls may use an AI voice assistant, are recorded, and are transcribed and summarised by the same providers. They never ask you for money. Tell us to stop, on the call or by email, and we will not call you again. Calls to help you set up: if you tick the box at sign-up, we may call the number you gave, with an AI voice assistant, when your setup stalls (for example, your phone is not confirmed or no server is running yet): at most one call and one retry each time, in daytime where you are. We keep the box’s wording, when you ticked it and the number. Say stop on a call, or untick it in your account, and we stop.
4. Why we collect it
To provision and operate your service, to bill you, to answer you when you write to us, to detect and stop abuse, and to respond to lawful requests. The use cases you declare and the description you give decide whether we accept an order, which verification documents we ask for, and protect the network reputation shared by all customers. Verification documents are used only to verify your business and are never shared except where the law compels it, or with the carrier that supplies phone numbers or voice calling you asked us for.
5. Who we share it with
- Infrastructure providers hosting your server, who necessarily process the traffic that passes over their network.
- Payment providers, who take the payment and receive only what that requires. They are named below.
- Prelude, which texts the code that confirms your phone number, and receives that number, your internet address, your browser and our reference for your account.
- Zoho Mail, which carries the email we send you and the email you send us.
- Telegram, if you link your account to it: the notices you chose to receive there. Telegram also carries a support chat you hand to a person to our staff’s phone, and their reply back to you.
- Microsoft Azure (its OpenAI service), which writes the assistant’s replies in the support chat. Like the AI Agents above, Microsoft can keep the text it processes for up to 30 days to check for abuse.
- Cloudflare, which carries the traffic to our website and console, and so sees your internet address and browser, and relays a meeting’s encrypted audio and video when the participants’ browsers cannot connect directly.
- ipapi.is, which receives internet addresses to tell us their network and country (section 1).
- Hetzner, which stores our encrypted backups and your server’s database backups in the EU.
- Carriers that supply phone numbers or voice calling you ask us for: your business details, your verification documents and the call records of that service, as the carrier or its regulator requires.
- Providers that run AI Agents, named in section 3, and only for the calls an AI handles.
- Google Ads: if you created your account after clicking one of our Google ads, the click ID Google put on that link and the times you signed up, started your free trial and first paid us, so Google can count what the ad led to. Nothing else about you is sent: not your name, email address, phone number or how much you paid.
- Law enforcement or regulators, where legally compelled. We tell you unless prohibited.
We do not sell personal data, and apart from the Google Ads click ID above, we do not share it for advertising.
6. Payment providers
Payments are taken by the providers below rather than by us, so your payment details are given to them and not to us. Each is an independent controller of what it collects, under its own privacy policy. They differ in what we pass them:
- Razorpay (card, UPI and netbanking) receives your name, email address, the amount and our payment reference, so the payment page can be pre-filled and the payment matched to your account. For a payment link, automatic top-up or bank-transfer account it also receives your company name and, for the first two, your phone number. Razorpay is based in India.
- PayPal receives the amount, a description and our payment reference. We do not pass it your name or email, because PayPal already holds the details of the account you sign in with. PayPal is based in the United States and operates through regional entities.
- NOWPayments (cryptocurrency) receives the amount, a description and our payment reference. We pass it no personal data at all.
Paying necessarily involves a transfer of information to these providers, which may be outside the country you are in. If you would rather not use any of them, ask us and we will arrange payment another way.
7. Paying with cryptocurrency
A chain payment is different from the others in a way worth stating plainly: it writes a permanent, public record. The transaction, the amounts and the wallet addresses involved are visible to anyone and cannot be deleted, by us or by anyone else, including in response to a deletion request. That record is on the network, not in our systems. We store only the provider’s payment identifier and the dollar amount credited.
8. Retention
- Web request logs: 14 days.
- Visit records of our own visit counter, with the IP address of each visit: 400 days.
- Recordings of visits to our public pages: 30 days.
- Operational and system logs: 90 days.
- Phone check requests: 90 days.
- Meeting bookings and their call-quality figures: until the meeting entry is deleted. Meeting rooms with no booking: 30 days after they close.
- Sign-in records: 180 days.
- Your server’s database backups in our storage: the last 14 nightly copies, while the server exists.
- Our own backups, which include account data and are encrypted: hourly copies for 48 hours, nightly copies for 30 days.
- Server metrics: 13 months.
- Account and order records: while your account exists. When you ask us to close it, we delete them, except invoices and billing records, which tax and accounting rules make us keep for 7 years.
- Verification documents: while your account exists, and deleted when you ask us to close it unless the law makes us keep them. A document you replace, or one we reject, is deleted on request.
- Call records of voice calling we supply: 2 years, or longer where a carrier or the law requires it.
- AI Agent calls (the recording, transcript, collected details and summary): kept until you ask us to delete them at privacy@trustane.com, when we delete the call with all of these. A note that it was deleted, with its phone numbers and time, stays in our audit log. They are not yet deleted automatically after a set period.
- Support chats: kept until you ask us to delete them at privacy@trustane.com. They are not yet deleted automatically after a set period.
- Support email threads, including a chat handed to email: kept until you ask us to delete them at privacy@trustane.com. They are not yet deleted automatically after a set period.
- Payment attempts that did not go through: 13 months. A payment that went through is part of your billing records.
- Customer data after termination: 7 days, then permanently destroyed.
9. Your rights
You may request a copy of the personal data we hold about you, ask us to correct it, or ask us to delete it where we are not legally required to keep it. Write to privacy@trustane.com. We respond within 30 days.
Grievance officer. A complaint about how we handle your data goes to our grievance officer, the proprietor of Trustane, at privacy@trustane.com, or by post to No 33, 1st Floor, 1st Main, Ganga Nagar, Gramatana, HMT Layout, CBI Main Rd, Bengaluru, Karnataka 560032, India. It is acknowledged within 48 hours and resolved within one month.
10. Cookies
This site sets no advertising or tracking cookies. Any cookie we set is strictly necessary to keep you signed in or to remember a form in progress.
The billing page loads payment scripts from PayPal and, when you choose to pay by card, from Razorpay. Those providers may set their own cookies from their own domains, which we neither control nor read. They load only on the billing page, and only for a signed-in customer, never on the public site. A video in our blog loads nothing from YouTube until you press Play. Then it plays from YouTube’s privacy-enhanced player, so Google receives your internet address and browser and may set its own cookies from its own domains.
11. Security
Verification documents are encrypted at rest with a key kept outside the data store; only our administrators can open one, and every opening is logged. Access to customer infrastructure is restricted, key-based and logged. We do not store payment card details: card entry happens on the provider’s own page, and what returns to us is a signed confirmation we verify, never the card. We will notify affected customers of any confirmed breach of their data without undue delay.