Skip to main content
You connect an assistant to your existing REalyse account. The data licence is the same one that covers REalyse Core and the API. This page describes what the connection adds: who writes the answer, what REalyse receives, where that data is processed, how long it is kept, which subprocessors handle it, and whether it is used to train a model. Read it with the terms that apply to your subscription. The standard documents on the REalyse website are the Terms & Conditions, the API Terms of Use and the privacy policy. Those documents do not describe an assistant connection. If your organisation has a signed agreement, that agreement applies to you.

​
What each document is for

​
Who writes the answer

The assistant you connect is the model. That might be Claude, ChatGPT, Microsoft Copilot Studio, Cursor, Visual Studio Code, or another MCP client. REalyse supplies the data lookups. The conversation stays in the assistant. REalyse does not receive the conversation text. When the assistant needs REalyse data, it sends a tool call. REalyse runs that lookup and returns the result. The assistant then writes the reply you see. The wording is the assistant’s, so two people can ask similar questions and get different write-ups. What that assistant stores or logs is covered by your agreement with its provider. REalyse is not a party to that agreement. If your organisation limits sending licensed data to a third party, set that with the assistant’s provider before you connect.

​
Model training

A direct tool call is a lookup against REalyse data. REalyse does not send that call to a model, and does not use the call or the result to train one. generate_data_report and paginate_data_report send the question and a place name to a separate analytical service, which writes the report. That service does not train its own models on the question, the place name or the report. It has opted out of training on the models it uses through Google Cloud and Amazon Web Services. Whether your assistant trains on the chat is covered by your agreement with its provider. If your organisation limits training on customer content, set that with the provider before you connect.

​
What REalyse keeps

REalyse receives the tool call, including the settings needed to run it, such as a place, a date range or a filter. The usage log records which tool ran. A log line can include your email, user id, team and company. It does not include the question text or those settings. REalyse also keeps:
  • The sign-in session that ties the assistant to your REalyse account. The assistant does not receive your password. See Sign-in and access.
  • Location tokens from resolve_location and resolve_radius_location. They are saved against your account so a later question can reuse the same area, and they do not expire. See Available tools.
  • Your monthly row allowance. See Usage limits.
  • A title-plan image, when the assistant asks for a map of a title boundary.

​
Where data is processed

REalyse MCP runs in Amazon Web Services in the EU, in Ireland (region eu-west-1). That covers the service, the admin database, title-plan images, CloudFront and CloudWatch logs. The analytical service behind generate_data_report and paginate_data_report runs in Europe. Sign-in is handled by Auth0 in the UK. Error reports are handled by Sentry in the USA. Both are listed under Subprocessors.

​
How long data is kept

​
Subprocessors

The REalyse API, the admin database and CloudFront run in REalyse’s own Amazon Web Services account in eu-west-1. They are not separate processors. Google and Microsoft see a social sign-in through Auth0. They do not see the property queries. When generate_data_report or paginate_data_report runs, the analytical service sends that call to these processors:

​
The data in the result

The tools are read-only. A lookup does not change your account, projects or saved work. Some results include personal data about other people, such as proprietor and director names on a land title. Demographics and crime tools return statistics for an area. Those figures describe the area. They are not a profile of you, and they are not a criminal record for a named person. The result goes back to your assistant so it can write the answer. Your data licence still applies to those figures, and to any summary the assistant writes from them. Publish or reuse them only within that licence. If the assistant’s provider can train on chat content, turn that off for REalyse results unless your agreement with REalyse allows it.

​
Analytical reports

Most tools call REalyse data directly. generate_data_report and paginate_data_report work differently. They send the question and a place name to a separate analytical service, which chooses and combines datasets and returns a report. They work from a place name rather than a location token. Where that service runs, how long it keeps the question and the report, and which subprocessors it uses are covered in Where data is processed, How long data is kept and Subprocessors. The report is still REalyse data. Ask the assistant to check get_dataset_update_dates when you need to know how current the figures are. Data coverage explains what that report cannot fill in.

​
Check the figures before you rely on them

Numbers in a tool result are REalyse data. The sentences around them are the assistant’s. Check the numbers in the tool result, or in REalyse Core, before you use them in a valuation, a credit paper or an investment note. Treat the assistant’s wording as a summary of the tool result. REalyse is not providing a valuation or other regulated advice through that summary.