Roll out to a team without a migration project
Both add-ins install from Microsoft AppSource or deploy centrally through Microsoft 365. Your templates and documents stay exactly where they are.
What runs locally, and what doesn't
This is usually the first question from IT, and it deserves a precise answer rather than a reassuring one. Our add-ins are listed on Microsoft Marketplace as able to send data over the internet. That is accurate, and it refers to the traffic in the right-hand column below — not to the contents of your documents.
| Function | On your device | Over the internet |
|---|---|---|
| Reading the document or template | ✓ | — |
| Detecting formatting and placeholder fields | ✓ | — |
| Filling fields and resolving conditional clauses | ✓ | — |
| Applying the tribunal colour key | ✓ | — |
| Writing changes back to the document | ✓ | — |
| Saving clips and profile fields | ✓ | — |
| Licence and subscription checks | — | ✓ |
| Payment processing (Stripe) | — | ✓ |
| Account name and email | — | ✓ |
| Website analytics | — | ✓ |
Full detail in the plain-English privacy explanation and the privacy policy.
How it's built
A high-level view for IT and security teams. The Security & Architecture page covers the same ground in a little more depth.
Office.js task pane
Standard Microsoft add-in architecture. The add-in runs in a sandboxed pane beside the document and can only touch the document the user has open, when the user asks it to.
No document store
We operate no repository of customer documents. There is nothing on our side to breach, subpoena or misconfigure, because your files never arrive.
Microsoft-certified distribution
Both add-ins are published through Microsoft AppSource and re-certified on each release, so you inherit Microsoft's review of the manifest and permissions.
Questions procurement and IT ask
How is licensing handled?
Both add-ins are free to install and free to use for their core function. Pro features are licensed per user. Licences are tied to the email address on the user profile, so a user keeps their licence across devices and across documents.
How does deployment work?
Two routes. Individuals install from Microsoft AppSource in under a minute. Organisations can deploy centrally through the Microsoft 365 admin centre, which pushes the add-in to chosen users or groups so it appears in the Word ribbon without anyone installing anything.
Does it require admin approval?
That depends on your tenant. Many organisations restrict user acquisition of Office add-ins, in which case an administrator either approves the add-in or deploys it centrally. Both add-ins are published on Microsoft AppSource and have passed Microsoft certification, which is generally what an approval process asks for.
What data leaves the organisation?
Not your document content. Scanning, filling, and colour-coding all happen on the user’s device inside Word. What does leave is licensing and account information — the user’s name and email, licence checks, and payment handling for Pro subscriptions — plus website analytics if the user visits this site.
Can templates be centrally managed?
Templates stay where they are today. Because Template Helper reads ordinary .docx files, you keep distributing templates through whatever you already use — SharePoint, a network share, or a document management system. There is no separate template repository to populate or keep in sync.
Does it work with Microsoft 365?
Yes. Both add-ins are Office.js task pane add-ins and run in Word on Windows, Mac and the web with a Microsoft 365 subscription. See the compatibility page for supported versions.
Can we control permissions?
The add-ins only act on the document the user has open, and only when the user clicks a button. They request no access to mailboxes, sites or directories. Central deployment controls who can see the add-in at all.
How does billing work?
Pro subscriptions are billed through Stripe. For volume or invoiced billing across a team, get in touch and we will arrange it directly rather than asking each user to subscribe individually.
What happens if someone leaves?
A Pro licence is tied to a user’s email address, so it can be released and reassigned. Clips and profile fields saved to a user profile travel with that user; anything saved to a specific document stays in the document.
Talk to us about a rollout
For volume licensing, invoiced billing, central deployment help, or a security questionnaire, get in touch and you'll speak to someone who works on the product.