Legal
Privacy notice
Last updated:
In plain English: We collect the minimum we need to run this website, answer your enquiry and run the Tesylate service. We don’t run advertising, we don’t sell your details, and this site has no analytics trackers. Your business data inside Tesylate belongs to you — we only process it on your instructions. Everything below is the detail behind those sentences.
1. Who we are
Tesylate Ltd is the controller of the personal data described in this notice.
- Company: Tesylate Ltd, registered in England and Wales, company number 11281502
- Registered office: 22 Apollo Way, Hemel Hempstead, England, HP2 5QG
- Contact: support@tesylate.com · 01442 504667
We have no statutory requirement to appoint a Data Protection Officer and have not appointed one. Privacy questions go to support@tesylate.com and Adam Rowles, Founder, answers them.
2. The two hats we wear
In plain English: For this website and your dealings with us as a company, we decide what happens to your data — we’re the “controller”. For the business data you sync into the Tesylate platform, you decide — we’re the “processor” and act only on your instructions.
- Controller. When you visit tesylate.com, contact us, book a demo, become a customer or receive our invoices, Tesylate Ltd decides how and why your personal data is used. This notice covers that.
- Processor. When your organisation uses the Tesylate service, the data we sync from your business systems (which may contain personal data about your staff, customers and suppliers) is processed on your documented instructions under our Data Processing Addendum. Questions about that data go first to your organisation — it is the controller.
3. What we collect, why, and on what legal basis
In plain English: Website visits leave almost nothing with us. Fill in the contact form and we get what you typed. Become a customer and we hold what any supplier holds: contact, contract and billing details. Ring us and an AI assistant answers; we keep a transcript, not a recording.
3.1 Visiting tesylate.com
The site is static. We run no analytics and no advertising trackers. Our hosting provider (Microsoft Azure) records standard server logs — IP address, request URL, timestamp, user agent — to keep the site running and secure.
- Purpose: operating and securing the website.
- Legal basis: legitimate interests (Article 6(1)(f) UK GDPR) — running a working, secure website.
- Retention: typically 30–90 days.
3.2 Contacting us or filling in the contact form
The contact form posts into Tesylate’s own system — no third-party form provider. We receive what you type: typically your name, work email, company and message.
- Purpose: answering your enquiry and, where relevant, following up about Tesylate.
- Legal basis: legitimate interests (Article 6(1)(f)) — responding to a business enquiry you initiated.
- Retention: 24 months from last contact, then deleted.
3.3 Booking a demo
Demo bookings run through Calendly. If you book, Calendly collects your name, email and chosen slot and passes them to us. Calendly is its own controller for its booking pages — see Calendly’s privacy notice. Calendly is a US company; the transfer safeguard for booking data is described in section 6.
- Purpose: scheduling and holding the demo.
- Legal basis: legitimate interests (Article 6(1)(f)) — arranging a meeting you asked for.
3.4 Being a customer (or a customer’s named contact)
If your organisation takes a trial or subscription, we hold business contact details (name, role, work email, phone), contract and account records, support correspondence, and billing records.
- Purpose: delivering the service, support, invoicing and payment collection, and keeping the accounting records the law requires.
- Legal basis: performance of a contract (Article 6(1)(b)); legal obligation (Article 6(1)(c)) for tax and accounting records; legitimate interests (Article 6(1)(f)) for service and renewal correspondence with your named contacts.
- Retention: for the life of the contract, then accounting records for 6 years plus the current financial year as HMRC requires; other customer records for 24 months after contract end.
3.5 Email
We use Microsoft 365 for mailbox email, and Twilio SendGrid to send transactional service notifications (for example support-ticket status updates). We do not send marketing email to people who have not dealt with us.
3.6 Connecting an AI assistant, including Microsoft 365 Copilot
In plain English: your organisation can hook up an AI assistant, such as Microsoft 365 Copilot or Claude, to Tesylate. You sign in to it with your own Tesylate account and it can only see and change what your role in Tesylate allows. We keep a record of the connection and of each request, but not the data itself.
This applies to the Tesylate agent for Microsoft 365 Copilot, which is listed
as “Tesylate” in Microsoft’s agent store. It applies to the Tesylate connector
for Claude at https://app.tesylate.com/mcp/directory, whether you add it
from Anthropic’s Claude connector directory or as a custom connector. It also
applies to any other assistant your organisation connects through our MCP
connector, Microsoft Copilot Studio included.
Here’s what we hold once an assistant is connected:
- The connection - which assistant, whose account, which Tesylate tenant, what it was allowed to do and when it was set up.
- The sign-in tokens, stored only as one-way hashes. We can’t turn a hash back into a token.
- A log of every request - who, when, which action, whether it was allowed and whether it worked, with a hash of what was sent. The full request and whatever came back aren’t logged.
Anything the assistant reads from Tesylate goes to whoever provides the assistant. For Microsoft 365 Copilot that’s Microsoft, under your organisation’s own agreement with them, and what Microsoft keeps is outside our control. For Claude that’s Anthropic: your organisation always connects Claude with its own Claude account, under its own agreement with Anthropic, so Anthropic is not our sub-processor and what it keeps is outside our control.
The connection records and logs are part of your organisation’s use of Tesylate, so the Data Processing Addendum applies to them. They get deleted along with the rest of your data, as section 9 of the Addendum describes.
To disconnect, go to the MCP connectors page in your Tesylate settings. Every token on that connection stops working straight away. Connections use OAuth with PKCE over encrypted links and each request is checked against your Tesylate permissions.
If an assistant gives you something from Tesylate that’s wrong, inappropriate or harmful, email support@tesylate.com with what you asked and roughly when.
3.7 Phone calls
In plain English: Our phone line, 01442 504667, is answered by an AI assistant. It will tell you it’s an AI if you ask. It can put you through to Adam on weekdays, 08:00–19:00 UK time, or book you a meeting. We keep a written transcript of the call, not an audio recording. We also make some calls with the same assistant. Say “don’t contact me again” on any call and we stop.
Calls to and from our line run through Twilio, our telephone carrier, in its Ireland region. A voice server we run ourselves in the UK connects the call to the assistant. What you say is processed by xAI (Grok Voice) so the assistant can understand and answer you; if xAI is unavailable, OpenAI does the same job. If you ask something the assistant looks up on the web, your question goes to xAI’s web search. The assistant checks your number against our customer records so it knows who is calling.
After the call, a transcript and a summary go to our own mailbox (Microsoft 365). Calls are not recorded as audio. Twilio keeps its standard record of each call: the numbers, the time and how long it lasted.
We also call people with the assistant: a customer’s billing contact about an overdue invoice, and business contacts we have already written to, as a follow-up to that letter or email. If you tell the assistant you don’t want to be contacted again, it records that and we stop.
- Purpose: answering and running our business phone line, following up our own correspondence, and collecting what we are owed.
- Legal basis: legitimate interests (Article 6(1)(f)) — answering a call you made, following up correspondence we sent you, and collecting money owed to us.
- Retention: as for enquiries, 24 months from last contact, then deleted; calls with customers are kept as customer records (section 3.4).
4. What we don’t do
- No sale of personal data. Ever.
- No advertising or cross-site tracking.
- No analytics cookies on this site (see the cookie policy).
- No automated decisions about you with legal or similarly significant effects.
- No data about children — Tesylate is a business-to-business service.
5. Who we share personal data with
In plain English: A short, named list of suppliers who help us run the company — and nobody else, unless the law makes us.
- Microsoft — hosting (Azure, UK/EU regions), screening support tickets for unsafe instructions with Azure OpenAI in the UK, and mailbox email (Microsoft 365).
- Twilio SendGrid — transactional email delivery.
- Twilio — telephone calls to and from our phone line.
- xAI — the phone line’s AI assistant (speech and web look-ups).
- OpenAI — the phone line’s AI assistant when xAI is unavailable.
- Zoho — billing and invoicing (Zoho Books).
- GoCardless — Direct Debit payment collection.
- Calendly — demo scheduling, only if you book a demo.
- Professional advisers and authorities — accountants, insurers, legal advisers, and HMRC or other authorities where the law requires it.
The full, current list of suppliers who touch customer platform data, with locations and safeguards, is the sub-processor list.
6. International transfers
The service runs on Microsoft Azure in UK/EU regions. Some suppliers are US companies:
- Calendly (US) — the EU-US Data Privacy Framework, including its UK Extension.
- Twilio SendGrid (US parent) — Twilio’s data protection addendum, incorporating the UK Addendum / IDTA.
- Twilio phone calls (US parent; calls run in its Ireland region) — Twilio’s data protection addendum, including the EU-US Data Privacy Framework and its UK Extension.
- xAI (US) — xAI’s data processing addendum, incorporating the EU Standard Contractual Clauses with the UK Addendum.
- OpenAI (US) — OpenAI’s data processing addendum, incorporating the EU Standard Contractual Clauses with the UK Addendum.
Where a transfer outside the UK happens, we rely on a UK adequacy regulation (including the UK Extension to the EU-US Data Privacy Framework where the recipient is certified) or the ICO’s International Data Transfer Agreement / Addendum to the EU Standard Contractual Clauses.
7. Security
Access to systems holding personal data is restricted and credentialed, the service runs on Microsoft Azure infrastructure, and connections are encrypted in transit. We deliberately make no certification claims here (no ISO 27001 or SOC 2 badge) because we hold neither — if that changes, this notice will say so.
8. Your rights
You have the right to:
- access a copy of your personal data;
- rectify anything inaccurate;
- erase data we no longer need to hold;
- restrict or object to processing based on legitimate interests;
- portability of data you gave us, where processed by automated means under contract or consent;
- withdraw consent at any time, where consent is the basis (it rarely is — see section 3).
Email support@tesylate.com and we will respond within one month. You can also complain to the Information Commissioner’s Office at ico.org.uk or on 0303 123 1113 — though we would rather you told us first so we can fix it.
9. Changes to this notice
We will post changes here with a new “last updated” date, and tell customers directly about any material change.
Tesylate Ltd, registered in England and Wales, No. 11281502. Registered office: 22 Apollo Way, Hemel Hempstead, HP2 5QG.