What We Do With Your Information

TechState builds and operates AI voice agents and chatbots for businesses. This policy explains what we do with personal information on our own website and in the services we run for our clients.

We act in two different roles, and it matters which one applies. On this website, and when you contact us, we decide how your information is used, so we are the controller. When we run a bot for a client, the client decides who is called or messaged and why, so they are the controller and we process that information on their instructions.

From our website: the name, work email, company size and message you submit through the contact form, plus standard server and security logs such as IP address, browser type and the pages requested.

From calls our bots handle: the audio of the call, a transcript of what was said, the phone number and any lead details the client sent us with the call, the outcome of the call, and timing information such as when the call started, how long it lasted and how quickly the bot replied.

From chatbots on a client website: the messages exchanged, any contact details a visitor chooses to give, and technical information such as the page the conversation started on.

We do not ask for payment card details, government identifiers or health information, and our bots are not built to collect them. If a caller volunteers something of that kind in conversation, it may appear in a recording or transcript, which is one reason access to those is restricted.

Website enquiries are used to reply to you, to arrange a demonstration and to keep a record of our correspondence. We do not sell them and we do not add you to unrelated marketing.

Call and chat data is used to deliver the service the client asked for: understanding what the caller said, routing the conversation, recording the outcome, and reporting on it. Recordings and transcripts are also how a client reviews quality and how we diagnose faults.

We use aggregated, non-identifying figures such as call volumes, response times and recognition rates to keep the service running well and to improve it.

The call came from a business using our technology, not from us. That business chose the list, the script and the reason for the call, and it holds the relationship with you.

If you asked not to be called again, that request is recorded against your number at the moment you make it and is passed to the client’s dialling system. If you want to reach the business itself, ask the agent on the call, or contact us and we will identify who placed the call and pass your request on.

Our clients, for the calls and conversations we handle on their behalf.

Service providers who make the bots work: telephony and connectivity providers who carry the calls, speech recognition and speech synthesis providers who turn audio into text and back again, language model providers used in parts of the service, and cloud hosting and storage providers. They may process the content of a conversation only to provide that function, and are not permitted to use it for their own purposes.

Anyone we are legally required to share it with, such as a regulator or in response to a valid legal request.

We do not sell personal information.

Recordings and transcripts are kept for a retention period set per client, after which they are deleted automatically. A client can shorten that period, and can switch recording off entirely.

Where a call produced no speech from the caller at all, such as an answering machine or dead air, the audio can be discarded within the hour rather than kept for the full period.

Records of the calls themselves, such as the outcome and the timings, are kept longer than the audio, because they are what reporting and compliance questions are answered from.

Website enquiries are kept for as long as we are in contact with you and for a reasonable period afterwards.

Credentials and API keys belonging to clients are encrypted before they are stored. Access to recordings, transcripts and call records is controlled by role, so a login only reaches what that role needs, and an agent-level login sees only its own calls.

Each deployment has its own secrets, so a problem with one cannot be used to reach another. Traffic to our systems is restricted to sources a client has declared, and calls from anywhere else are refused.

Depending on where you live, you may have the right to ask for a copy of the personal information we hold about you, to have it corrected or deleted, to object to how it is used, and to complain to your local data protection authority.

Where we are processing on a client’s behalf, we will pass your request to that client and support them in answering it, because the decision is theirs to make.

This website uses only what is needed to serve and secure the pages. We do not use advertising cookies and we do not track you across other sites.

The contact page uses Google reCAPTCHA to stop automated spam. It looks at information about your browser and how you use the page, which is sent to Google and handled under Google’s privacy policy. It is only loaded on the contact page.

If we change this policy we will update the date shown above. Where a change materially affects how we handle personal information, we will make that clear rather than relying on the date alone.