Legal

Privacy Policy

Last updated: 10 October 2026

1. Who we are

Policy Compass is operated by Meet George Limited ("Meet George", "we", "us", "our"), a company registered in England and Wales under company number 15747538, with its registered office at 18 Albert Road, Bournemouth, Dorset, BH1 1BZ.

For the personal data described in this policy, Meet George Limited is the data controller, except where sections 2, 15 and 16 explain that we act as a processor on behalf of an organisation that uses Policy Compass. If you have any questions or want to exercise your rights, contact us at privacy@policycompass.co.uk.

2. What this policy covers

This policy explains how we handle personal data as a controller - for visitors to policycompass.co.uk, people who contact us or request a trial, and the administration of customer accounts.

It also covers the Policy Compass app for Microsoft Teams and the Policy Compass app for Slack. Section 15 and section 16 explain what personal data each app handles, why, who acts as controller and processor, and how long we keep it.

Separately, when we process personal data within the Policy Compass platform on behalf of a customer, we act as a processor, on the customer's instructions and under our agreement with it. That data is governed by the customer's own privacy notices and by our agreement with it, and by the controls described in our Trust Centre.

3. The personal data we collect

Information you give us

  • When you request a trial or use our contact form: your name, work email, company, company website, what your business does, and anything you include in your message.
  • When you correspond with us by email or otherwise.
  • Account information for users of the platform: name, work email, and role.
  • When you use the Policy Compass app for Microsoft Teams: the messages you send it and your Teams identifiers (see section 15).
  • When you use the Policy Compass app for Slack: the messages you send it, any files you attach to them and your Slack identifiers (see section 16).

Information collected automatically

  • Device and usage data, including IP address, collected through cookies and analytics - only where you have consented (see Cookies).
  • Technical and diagnostic data needed to operate and secure the website and service (with sensitive content and credentials removed from error reports).

We do not seek special category data, and the platform is intended for regulatory and business content rather than personal data.

4. How we use your data, and our legal bases

  • Responding to enquiries and setting up and running trials and accounts - to take steps at your request before entering a contract, and to perform a contract.
  • Providing, securing and improving the website and platform - our legitimate interests in running and protecting our service.
  • Analytics and measuring our marketing - your consent (managed through our cookie banner).
  • Meeting legal and regulatory obligations - compliance with applicable law.

We do not sell your personal data, and we do not use customer content (your questions, documents or chat history) to train AI models - by us or by our providers. See the Trust Centre for detail.

5. Marketing communications

Where you have asked to hear from us, or where we are otherwise permitted to, we may send you product updates and other marketing emails. You can opt out at any time using the unsubscribe link in any such email, or by emailing privacy@policycompass.co.uk. Service and account messages we need to send to run a trial or contract are not marketing and continue regardless.

6. Automated decision-making and profiling

Policy Compass is an AI research tool, but it does not make decisions about you. We do not use your personal data for solely automated decision-making that produces legal or similarly significant effects, and a human stays in control of how the platform is used. Where the Service analyses regulatory material, it does so to assist a person's research and judgement, not to make automated decisions about individuals.

7. Cookies and analytics

We use a consent banner to manage cookies. Strictly necessary cookies are always on; analytics and similar technologies (such as Google Analytics and Google Tag Manager) load only after you consent. You can review or change your choices at any time using the Cookies link in the website footer.

8. Who we share your data with

We share personal data with trusted service providers who process it on our instructions, including, for the website and enquiries: Airtable (storing form submissions), Resend (sending email), Vercel (website hosting), Google (analytics, with your consent), our consent-management provider (cookie consent), and Sentry (error monitoring, with prompt and response content removed).

For the Policy Compass platform, a list of our sub-processors, with each one's purpose and region, is available on request. We give active customers at least 30 days' notice before any material change. We do not sell personal data.

9. International transfers

Primary storage is in the UK, and the AI models that process customer data run in the EU. Some of our providers operate outside the UK and the EU. Where we transfer personal data outside the UK, we rely on UK adequacy regulations or on the safeguards our providers offer, such as the EU Standard Contractual Clauses with the International Data Transfer Addendum issued by the UK Information Commissioner. Our web search provider, which is based in the US, receives only search queries made from users' questions, never uploaded files or chat history, and does not retain them.

Microsoft provides the Azure Bot Service, which carries messages between Microsoft Teams and the Policy Compass app for Microsoft Teams (see section 15). It is a global service, so these messages may be processed outside the UK and the EU. Microsoft provides it to us as our processor under Microsoft's data protection terms, which apply the EU Standard Contractual Clauses and the UK International Data Transfer Addendum to transfers from the UK.

10. How long we keep your data

We keep personal data only as long as we need it for the purposes above: enquiry and lead data for as long as we are in contact and a reasonable period afterwards; account and service data for the term of the contract and a defined period after it ends, after which it is deleted. Configurable retention is available on enterprise contracts.

11. How we protect your data

Data is encrypted in transit (TLS 1.2+) and at rest (AES-256). Primary storage is in the UK, customer data is isolated per customer, and Meet George holds the UK government-backed Cyber Essentials certification. We notify affected customers of a personal-data breach affecting their data without undue delay, and no later than 72 hours after becoming aware of it. See the Trust Centre for the full picture.

12. Your rights

Under UK data-protection law you have the right to access, rectify, erase, restrict, and port your personal data, to object to certain processing, and to withdraw consent at any time. To exercise any of these, email privacy@policycompass.co.uk. Where we are the controller, we respond within 30 days. Where we hold your data on behalf of an organisation that uses Policy Compass (see sections 2, 15 and 16), that organisation is the controller: we will pass your request to it, help it respond and act on its instructions.

You also have the right to complain to the Information Commissioner's Office (ICO) at ico.org.uk or on 0303 123 1113, though we'd appreciate the chance to resolve any concern first.

13. Children

Policy Compass is a business-to-business service and is not directed at children. We do not knowingly collect personal data relating to children.

14. Third-party links

The Website and Service may link to third-party websites, such as Ofgem, DESNZ and industry code bodies. We are not responsible for their content or their privacy practices; their own privacy notices apply.

15. The Policy Compass app for Microsoft Teams

Policy Compass is available as an app for Microsoft Teams (the "Teams app"). People whose organisation has a Policy Compass account can use it to ask regulatory questions in Teams and get AI-generated answers that cite their sources. This section explains what personal data the Teams app handles, why, who it is shared with, how long we keep it, and how to disconnect or ask us to delete it. The rest of this policy also applies.

What the Teams app receives

The Teams app only receives messages that are sent to it: messages in a one-to-one chat with the app, and messages in a channel or group chat that @mention it. It cannot read other messages in your chats or channels, and it has no access to your mailbox, files, calendar or contacts. It does not open or keep files or images attached to a message. For each message sent to it, Microsoft passes us:

  • the text of the message, with the app's own @mention removed (if you @mention a colleague, their name stays in the text);
  • your Teams user ID and display name;
  • the ID of the Microsoft 365 tenant (Microsoft Entra ID) of the organisation that owns the chat or channel; and
  • technical details of the conversation, such as the conversation and message IDs, whether it is a one-to-one chat, a group chat or a channel, and the Microsoft service address we use to post the reply.

Microsoft also sends some details that the Teams app does not use or keep, such as your Microsoft Entra object ID, your language, country and time-zone settings, and the type of Teams client you are using.

To tell whether you are a member of the organisation that owns a chat or channel, one of its guests or a person from another organisation, the Teams app may also ask Microsoft for your membership details in that conversation. Microsoft's reply includes the Microsoft 365 tenant ID of your own organisation and whether you are a member or a guest, as well as details such as your name and email address. We hold the reply in memory for a short time and use it only to decide how to respond. We do not store the reply itself, we never store the email address in it, and we use the name in it only for the welcome message described below. The only things we may record from it are whether you are a member, a guest or from another organisation, in the log entry described below, and whether you are a member or a guest, with a connection code if one is issued to you.

When the Teams app is added to or removed from a team, group chat or one-to-one chat, Microsoft tells us where: the Microsoft 365 tenant, team and conversation IDs. When it is added to a team or group chat, we also look up the name of the person who added it, in the same way as the membership details above, so that the app's welcome message can mention them. We use the name only to post that message and do not store it.

How we use it

  • Connecting your account. The Teams app only answers people whose Teams identity is connected to a Policy Compass account. If yours is not, the app replies in your one-to-one chat with a one-time code, which you enter in Policy Compass under Settings > Integrations while signed in. The code can be used once and expires 15 minutes after it is issued. To issue it, we store your Teams user ID, tenant ID and display name, whether you are a member or a guest in that tenant, and a reference to the chat so that we can confirm there once you have connected. When you connect, we keep a record of the link between your Teams identity and your Policy Compass account. The first person to connect from an organisation also links that organisation's Microsoft 365 tenant to its Policy Compass account, so that only people from that tenant can connect to it. Owners and admins of your organisation's Policy Compass account can see who has connected a Teams account. The app never posts a code in a channel or group chat; it asks you to message it directly instead.
  • Which organisation's account answers. In a one-to-one chat, the Teams app answers from the Policy Compass account your Teams account is connected to. In a channel or group chat, it always answers from the Policy Compass account of the organisation that owns the chat or channel (the organisation whose Microsoft 365 tenant hosts it), using that organisation's business profile, and it only answers people who have connected a Policy Compass account in that organisation. Guests that the organisation has invited into its Microsoft 365 tenant are treated as its users, so the app answers them only if that organisation has given them their own Policy Compass account.
  • People from other organisations. If you take part in a shared channel or group chat that another organisation owns, the Teams app does not connect you there, does not answer your questions there, and never uses your own organisation's Policy Compass account in that conversation. Instead it replies with a short note saying that Policy Compass in that chat or channel is set up for the organisation that owns it, and that you can use Policy Compass in a one-to-one chat in your own organisation's Teams if your organisation has it. The note links to this section of our privacy policy. We do not send your message to our AI models or keep its text; we keep only the log entry described below.
  • Answering your questions. Once you are connected, we use your message to produce an answer in the same way as Research in Policy Compass, taking account of the business profile described above. The answer is posted in the Teams conversation where you asked, with its sources and a link to open it in Policy Compass. In a channel or group chat, the reply mentions you by name, and everyone in that conversation can see your question and the answer. Your question and the answer are also saved to your Research history in Policy Compass, marked as asked from Teams, with a short AI-generated title.
  • Keeping the app secure and supporting it. We keep a log entry for each message the app receives: the IDs above, the time, and what happened (for example, that it was answered, that a code was sent or that a note was sent to someone from another organisation). For questions from connected users, the log entry also includes the question. We use this log to prevent misuse, investigate problems and support your organisation.

If you message the Teams app before you have connected an account, if you are from another organisation, or when the app is not available to your organisation, we do not keep the text of your message. We keep only what we need to issue a code, where one is issued, and the log entry.

What your organisation's owners and admins can see

Owners and admins of your organisation's Policy Compass account can see who has connected a Teams account, and can disconnect them. They cannot read the questions you ask the Teams app, or its answers, in Policy Compass, and they cannot see the log described above. A question you ask in a channel or group chat, and its answer, can be seen in Teams by everyone in that conversation.

Our role and legal basis

Connected users. For people who have connected a Policy Compass account, we act as a processor for the organisation whose Policy Compass account they are connected to, on its instructions and under our agreement with it (see section 2). This covers everything we hold about you as a connected user: your questions and the answers, the link between your Teams and Policy Compass accounts, the connection code you used to connect, and the log entries about your messages. That organisation is the controller: it decides how its people use Policy Compass, and it can instruct us to return or delete this data.

People who are not connected. We are the controller only of the minimal records we keep about people who are not, or not yet, connected users of a Policy Compass organisation, and about messages we could not attribute to anyone:

  • connection codes that are never used;
  • log entries for messages sent while someone is not connected, including by people who never connect;
  • log entries for messages that failed before we could tell who sent them;
  • log entries for people from other organisations who receive the short note described above; and
  • the membership details we look up, and hold only in memory, to decide how to respond to someone who is not connected.

For these we rely on our legitimate interests in keeping the Teams app secure and preventing its misuse, including making sure that it only answers people who have a Policy Compass account in the organisation that owns the conversation.

Where the app has been added. Where a team or chat belongs to an organisation whose Microsoft 365 tenant is connected to a Policy Compass account, we hold the record of where the Teams app has been added there, and use the name of the person who added it for the welcome message, as a processor for that organisation. Otherwise we are the controller of that record and of that use of the name, and we rely on our legitimate interests in running the Teams app where it has been added.

Your right to object. Where we rely on our legitimate interests, as described above, you can object to this processing at any time by emailing privacy@policycompass.co.uk. If you do, we will delete the records about you that we hold on that basis, unless we need them for an open investigation into misuse of the app. To find them, we need your Teams or Slack user ID, or roughly when and where you messaged the app.

Who we share it with

Microsoft carries messages between Teams and the Teams app through its Azure Bot Service (Bot Framework), which handles them on our behalf under Microsoft's data protection terms. Microsoft is our processor for this service, or our sub-processor where we act for your organisation. It is a global service, so messages may be processed outside the UK and the EU; section 9 explains the safeguards. The messages you send the app, and its answers, also stay in Teams, where Microsoft stores them as part of your organisation's Microsoft 365 service under your organisation's agreement with Microsoft and the Microsoft Privacy Statement. Deleting data from Policy Compass does not delete messages in Teams.

To answer a question, we use the same sub-processors as the rest of the Policy Compass platform: the cloud services that run the Teams app and Research, our database, our AI model providers, the web search service Research uses to find its sources (which receives search queries, not your files), and error monitoring. They are listed, with each provider's purpose and region, in our Security & Data Handling overview, available on request (see section 8). We do not sell personal data.

Where it is stored

Primary storage is in the UK, and the AI models that answer your questions run in the EU. Some supporting services, including Microsoft's Azure Bot Service, operate outside the UK and EU; section 9 explains the safeguards we rely on. We don't use your questions or answers to train AI models, and the AI models that answer them don't keep them for training. Section 11 covers how we protect your data.

How long we keep it

  • Questions and answers in your Research history are kept as part of your organisation's Policy Compass data (see section 10) until they are deleted. If you delete a conversation in Policy Compass, we delete its messages and the related log entries, including the question.
  • While an answer is being prepared, we hold a short-lived copy of your question, your Teams identity and where to post the reply. We delete it once the reply has been posted, or once the answer has failed or been abandoned.
  • To stop the app answering the same message twice, we keep a marker for each message it receives, made up of the message's ID and the time we received it, but not its text. Markers more than 7 days old are deleted when you next message the app in the same chat or thread; we do not yet delete them automatically where you send no further messages there.
  • Connection codes expire 15 minutes after they are issued. We delete the record of each code 30 days after it expires, whether or not it was used.
  • Log entries are deleted no later than 12 months after they were created. Log entries for messages sent while you were not connected, including those for people who never connect and for people from other organisations, and those for messages that failed before we could tell who sent them, are deleted sooner, 90 days after they were created.
  • Log entries can also be deleted sooner: those for a conversation you delete in Policy Compass are deleted with it, your organisation can ask us to delete its log entries, and any that remain when your organisation's contract ends are deleted with the rest of its Policy Compass data, within the periods in section 10.
  • The record of the link between your Teams and Policy Compass accounts is kept, including after you disconnect (see below), until your own Policy Compass account or your organisation's Policy Compass account is deleted.
  • The record of where the Teams app has been added (the Microsoft 365 tenant, team and conversation IDs) is kept until Microsoft tells us that the app has been removed from that team or chat, or that the team or channel has been deleted.

Disconnecting and deletion

  • You can disconnect your Teams account at any time: type disconnect in a one-to-one chat with the Teams app, or go to Settings > Integrations in Policy Compass. Owners and admins can disconnect anyone in their organisation, and can switch the Teams app off for the whole organisation. The app stops answering you as soon as you are disconnected, until you connect again.
  • When you disconnect, we delete the display name stored with your connection and any connection codes issued to you. We keep the IDs that record that your Teams account was connected and then disconnected, your Research history, and your organisation's log entries until they are deleted as described above, as part of your organisation's Policy Compass records, so that your earlier Teams conversations continue if you connect again.
  • Removing the app from Teams stops you sending it messages, but does not by itself delete the data we hold.
  • To delete a conversation, delete it from your Research history in Policy Compass. To ask us to delete your Teams connection records, or anything else we hold about you, email privacy@policycompass.co.uk. Where we hold the data on behalf of your organisation, we will pass your request to your organisation and act on its instructions.

Questions about the Teams app and your data: privacy@policycompass.co.uk. Help with using the app: hello@policycompass.co.uk.

Policy Compass and Meet George Limited are not affiliated with, or endorsed by, Microsoft. Microsoft and Microsoft Teams are trademarks of the Microsoft group of companies.

16. The Policy Compass app for Slack

Policy Compass is also available as an app for Slack (the "Slack app"). Someone in an organisation that has a Policy Compass account adds it to that organisation's Slack workspace from Policy Compass, and each person then connects their own Slack account with a one-time code, as for the Teams app. Section 15 applies to the Slack app in the same way - including what we use messages for, our role and legal basis, what owners and admins can see, how long we keep data, and deletion - with these differences:

  • What it receives. The Slack app only receives messages in a one-to-one chat with it and messages in a channel that @mention it. For each message, Slack passes us the text, with the app's own @mention removed; your Slack user ID; the IDs of your Slack workspace (or Enterprise Grid organisation), the channel and the message; and details of any files attached to it. The Slack app does not use or keep any other details Slack sends with a message, and it does not look up your name, email address or membership.
  • Files. If you are connected and attach a file to a message, we download it from Slack, save it as a private document in your Policy Compass account and use it to answer your question, in the same way as a file you attach in Research. It is kept until you delete it from your documents in Policy Compass, or with the rest of your organisation's Policy Compass data (see section 10). If you are not connected, we do not download your files.
  • Connecting and disconnecting. To issue a connection code, we store your Slack user ID, your workspace ID and a reference to your one-to-one chat with the app. Each Policy Compass organisation connects to one Slack workspace or Enterprise Grid organisation. To disconnect, go to Settings > Integrations in Policy Compass.
  • The installation record. When the Slack app is added to a workspace, we keep a record of the installation: the workspace ID, the Policy Compass user who added it, and the access token Slack issues for the workspace, which we store encrypted. We hold it as a processor for the organisation whose Policy Compass account it belongs to. If the app is removed from Slack, we mark the record as removed. It is deleted with that organisation's Policy Compass account.
  • Who we share it with. Slack delivers your messages to the Slack app, and the messages you send it and its answers stay in Slack, where Slack stores them as part of your organisation's Slack service under your organisation's agreement with Slack. Deleting data from Policy Compass does not delete messages in Slack.
  • What does not apply. The parts of section 15 about Microsoft, the Azure Bot Service, membership and name lookups, guests, which organisation's account answers in a shared conversation, the note for people from other organisations, and the record of where the Teams app has been added apply only to the Teams app. In Slack, the app answers from the Policy Compass account you are connected to, in the Slack workspace connected to that account.

Policy Compass and Meet George Limited are not affiliated with, or endorsed by, Slack.

17. Changes to this policy

We may update this policy from time to time. The "last updated" date above shows when it last changed, and we will notify active customers of any material change.

18. Contact

Meet George Limited, 18 Albert Road, Bournemouth, Dorset, BH1 1BZ. Data and privacy enquiries: privacy@policycompass.co.uk. General enquiries: hello@policycompass.co.uk.