TSE-Assistant

Privacy Notice

Last updated: 1 October 2026

1. Who we are

TSE-Assistant is operated by TSE IT SOLUTIONS LIMITED ("we", "us"), a company registered in England and Wales, company number 15419504, VAT number GB476282561, registered office 25 Waterfield Way, Clipstone Village, Mansfield, NG21 9FD. We provide developer tools for Microsoft Dynamics 365 Finance & Operations installed on your machines, a company dashboard, and Sofia, an AI assistant available in the installed app, in the dashboard, in Microsoft Teams and in Slack. Contact: support@tse-assistant.com; for anything about your personal data, privacy@tse-assistant.com (section 9).

1a. Our roles

We are the controller for: your account, plan, seats and billing records; the operational records (machine check-ins, audit rows kept for our own security, security events, service logs, the mails we send); and this website.

For company accounts, we process on your company's behalf, as its processor: the content your company puts into the Service — the published index, Sofia's conversations, memories and documents, and the value-free audit records your admins read. Your company is the controller of that content, our Data Processing Agreement governs how we handle it, and requests about it go to your company first (section 9).

Individual plans: what the tools read stays on your machine; we are the controller for your account.

1b. Where the data comes from

Most of it comes from you. When your company invites you, your company's admin gives us your e-mail address and, optionally, your name. When you sign in with Microsoft, it sends us your name, e-mail address and account id; when you sign in with GitHub, we use only your GitHub username and account id.

2. What we collect

Account data. When you sign in we receive your identity from your chosen provider — Microsoft (name, e-mail, directory and account identifiers) or GitHub (username, account id). We use it to create and secure your account. We never see your passwords.

Subscription and billing data. Your plan and add-ons, trial and licence state, and activation history. Payments are taken by Paddle, our merchant of record; we do not store card numbers.

Team administration data (company plans). Seat assignments, roles and tiers, registration-token issuance, and the configuration and instruction packs that admins write for their own teams.

Machine check-ins. Each company installation reports its host name, Windows user name and machine id, its agent version and its index status. We use them to show your admins which machines serve which environment, and to flag one credential used on several machines. Individual installations send one-way hashes of their machine identifiers instead. We keep such a hash, with the account, so that one machine cannot start repeated trials.

Audit fingerprints (company plans). Which tool ran, when, by which seat, with a fingerprint of the arguments and — for change-making tools — the names of the objects and models changed. These records never contain source code, query results or business data. Reads are kept 90 days, changes 180.

Security events. When we refuse a request, or see a tamper signal such as a modified agent bundle, we record the time, the kind, the account, the machine and the IP address it came from.

Published indexes (company plans). The metadata and label texts described on the Security & Data Handling page.

Sofia in the dashboard, in Microsoft Teams and in Slack (when your admin has switched it on). Your messages, including the text of files you attach; Sofia's answers; the memories she saves at your request; the documents she writes; your choice of model; and the link between a Teams chat, or a Slack thread, and its conversation. For Slack we also hold your workspace's id and name, the bot token your admin granted (encrypted) and, once you have signed in with your Microsoft work account from the chat, your Slack user id against your seat - the messages themselves pass through Slack, Inc., your workspace's own provider, as Teams messages pass through Microsoft. When your admin has also switched on live data in Teams, Slack and the Chat tab, your messages and Sofia's answers on those surfaces are not stored: they are held in the service's memory for the conversation only (the last 20 turns, gone after 30 minutes of quiet or an update of the service), Sofia reads records from your environment under your own Dynamics 365 permissions with a token Microsoft issues for you — held in memory, never written to disk — a consultant seat's proposed record changes and operations run under the same permissions only when that person confirms them (we keep a value-free audit record of each: the entity or action and the outcome), and your company's stored conversations are deleted when that switch goes on. The memories, the documents, your model choice and the Teams chat or Slack thread link are kept as before.

Model usage. For each call to TSE's LLM: the seat, the model, the number of tokens and the cost. Never the prompt.

Mail. For the mails we send (invitations, credit alerts, receipts for data protection requests): the recipients, the subject and whether it was delivered.

3. What stays on your machine

Stays on the machine: your source code and PackagesLocalDirectory; the local index; your database credentials; the installed app's conversations, memories and local activity log; your own AI key.

Leaves the machine: what the tools find goes to the AI model the IDE or app uses — your own provider, or, on company seats using TSE's LLM, through our service to that model (section 4). On a machine with PackagesLocalDirectory that can include source code.

Never stored by us: source code, whichever way it travels. That includes the capability relay, which, when your admin switches it on, passes your own custom-model code through our service to your consultant's app for one request, in memory.

4. AI features and your AI provider

Two routes:

• Your own provider — your API key, or GitHub Copilot, Cursor or Claude in your IDE. The provider processes the prompts under the agreement you hold with it. That traffic does not pass through us, and those providers are not our sub-processors.
• TSE's LLM — available to company consultant and super-user seats when your admin switches it on, and always used by Sofia in the dashboard, Teams and Slack. Prompts pass through our service to Microsoft Azure OpenAI (gpt-4.1-mini, UK South) or, when your admin allows it, OpenAI (gpt-5.6-terra, United States), which act as our sub-processors. A new account's seats use gpt-4.1-mini until the admin allows the US model. We keep usage figures, not prompts.

We do not use your data to train AI models, and neither provider trains on it under our agreements. What the providers themselves keep:

• OpenAI keeps API inputs and outputs for up to 30 days to detect abuse, then deletes them.
• Microsoft checks Azure OpenAI prompts and outputs automatically for abuse, and may store them in the UK geography, where authorised Microsoft staff may review those flagged as possible abuse; it publishes no fixed period.

5. How we use data, and why the law lets us

• To provide the Service and bill for it — accounts, seats, licences, Sofia's answers, metering model usage against your company's Sofia credit, invoices: performance of our contract with you (individual plans), and our legitimate interests in providing what your company bought (people using a company's seats).
• To keep the Service secure and prevent abuse — security events, machine check-ins, trial checks, service logs: our legitimate interests.
• To keep accounting and tax records: legal obligation.
• To tell business contacts about the Service, when we do: our legitimate interests, with a way to opt out in every message.

We do not sell personal data, and we do not serve advertising. We make no decisions about you by automated means that have legal or similarly significant effects. Account details are needed to provide the Service; without them we cannot open an account.

6. Who receives personal data

Our processors act on our instructions under their data processing terms. The current list, with what each one does and where, is on the sub-processors page. In short:

• Microsoft Azure — hosting, database, storage and logs (UK South), and e-mail delivery (Azure Communication Services, UK data location; Microsoft says such data may transit or be processed in other geographies);
• Microsoft Azure OpenAI — TSE's LLM, gpt-4.1-mini (UK South);
• OpenAI — TSE's LLM, gpt-5.6-terra (United States; only when your admin allows it);
• Microsoft Azure AI Bot Service — Sofia in Microsoft Teams (a global service, which may process data outside the UK);
• Cloudflare — our domain's DNS and the routing of e-mail sent to our addresses;
• Google (Gmail) — receives the e-mail sent to our addresses (support@, privacy@, security@, innovation@, admin@), until we move them to a business mailbox.

Independent controllers: Paddle (Paddle.com Market Ltd; Paddle.com Inc. for buyers in the US, Paddle.com (Canada) Ltd in Canada) — merchant of record for payments, invoices and tax, under its own privacy notice; Microsoft and GitHub — when you sign in with their accounts.

The AI providers you configure yourself act under your own agreement with them, not as our sub-processors. Otherwise, we disclose personal data only where the law requires it.

6a. Transfers outside the UK

• OpenAI (United States): we rely on the EU Standard Contractual Clauses with the UK Addendum, which OpenAI's Data Processing Addendum puts in place and its Services Agreement incorporates for our use of its API, together with our own transfer risk assessment. A new account's seats do not use OpenAI until its admin allows it.
• Microsoft services that may process outside the UK (the Bot Service, e-mail delivery): Microsoft's Data Protection Addendum, which includes the UK Addendum to the Standard Contractual Clauses.
• Paddle: Paddle's own safeguards, as an independent controller.

A copy of a safeguard is available from privacy@tse-assistant.com.

7. Retention and deletion

The retention schedule — every record, what it holds and how long we keep it — is section 6 of the Security & Data Handling page. In short: a daily sweep deletes each record when its period ends; Sofia's conversations go 12 months after the last message or when you delete them — and are not stored at all while your admin has live data in Teams, Slack and the Chat tab switched on; you can delete Sofia's documents and memories yourself; your account owner can delete all of your company's Sofia data at once from the dashboard; when an account closes, its data is deleted 90 days later, except what accounting law requires us to keep. Your account owner — or you, on an individual plan — may ask us to close the account through privacy@tse-assistant.com at any time.

Our service logs are kept 30 days, and a deleted record leaves our database backups within 7 days. Local data on your machines is yours to delete. Uninstalling the agent deliberately keeps its state folder (%USERPROFILE%\.tse-assistant: licence, registration, memories), so that a reinstall recovers the seat. Delete that folder to remove them, and ask your admin to revoke the machine.

8. Security

Transport encryption (TLS) everywhere, secrets held in managed stores, the database and storage encrypted at rest, per-account isolation, single-use registration tokens (15 minutes) and activation codes (24 hours), and signed licences. A record deleted from our database leaves the backups within 7 days. The local agent encrypts its backups and credential store on your machine. The details are on the Security & Data Handling page.

9. Your rights and complaints

Your rights. You have the right to access your personal data and to have it corrected or erased; to restrict or object to its use; to receive it in a portable form; and to withdraw consent where we rely on consent.

How to use them. Write to privacy@tse-assistant.com, use the data protection form on the Contact page, or write to the registered office. We answer within one month, which the law lets us extend in some cases, and we search for your data in a reasonable and proportionate way. We may ask you to confirm who you are first. For content your company put into the Service, we pass the request to your company and help it answer.

Complaints. You can complain to us first, through the same contact: we acknowledge a complaint within 30 days and tell you the outcome. You can also complain to the UK regulator, the Information Commission (the Information Commissioner's Office until 30 September 2026), at ico.org.uk.

9a. Cookies and similar technologies

Cookies that keep you signed in. They are strictly necessary for the service you asked for, so they need no consent. All are HttpOnly and Secure:

• d365fo_session — your company dashboard session; 12 hours.
• tse_individual — an individual's session on the account pages; 1 hour.
• d365fo_pending_reg — a company registration in progress; 30 minutes.
• tse_login_microsoft, tse_login_github, tse_login_entra — a sign-in in progress with that provider; 30 minutes.

A session-affinity cookie (acaAffinity) set by our hosting, Azure Container Apps, so your requests reach the same instance while you browse; it lasts for the browser session.

Two small entries in your browser's local storage (tse.updateBannerDismissed, tse.creditBannerDismissed) remember a banner you dismissed on the dashboard, so it does not come back until there is something new. They hold a version or a period key, nothing about you. To object, do not dismiss the banners, or clear this site's data in your browser - the entries are gone and the banners return.

Paddle's checkout script loads only when you choose to buy ("Buy now", "Continue to checkout", a top-up) or when you open a Paddle payment link that lands on our pages. It may then set Paddle's own cookies for payment and fraud prevention, under Paddle's privacy notice. A plain visit to any page loads no third-party script.

We use no analytics, advertising or tracking cookies.

9b. Children

The Service is for professionals and is not directed at children.

10. Changes

We will post any changes to this notice on this page and update the date above. Material changes will be highlighted on the website or by e-mail to the account owner.