Privacy Policy
Effective date: 2026-11-17 | Version 3.40
Contents
1. Introduction
Mather Software Ltd (“we”, “us”, or “our”) is committed to protecting your personal data. This Privacy Policy explains how we collect, use, store, and share your information when you use our AI-powered property research service.
We are the data controller for the personal data we process, and we are based in the United Kingdom. Our contact email for privacy matters is support@mathersoftware.com.
- Mather Software Ltd
- Registered in England and Wales, company number 17443861
- View on Companies House (opens in a new tab)
2. Data We Collect
2.1 Account Information
- Email address (required for account creation)
- Name (if provided during registration)
- Authentication tokens (managed by Clerk)
2.2 Payment Information
- Payment card details (processed and stored by Stripe, not by us)
- Billing history and transaction records
- Subscription status and billing history
- For a subscription bought in the HomeThink app: which store it came from (App Store or Google Play), its status, renewal and expiry date, and its product — never your card or store account details (see 5C)
2.3 Usage Data
- The homes you check: the postcode and first line of the address you type, the purpose you choose and the details you confirm
- AI-generated property analyses and chat conversations
- User preferences (budget, property types, priorities, deal-breakers)
- Saved properties, favourites, and portfolio data
If you choose to give them to us, we also hold:
- Affordability settings: your income, your partner's income, your savings, your deposit, and the mortgage outstanding on a home you already own, along with related figures such as monthly outgoings and debts
- Household make-up: how many adults are in your household, your children's ages and your life stage
- Commute address: the postcode of a place you travel to regularly, such as work
We use these to do the affordability maths on a report (what a home would cost you each month, and how it compares with what you could borrow) and to tailor the analysis to your household and commute. The legal basis is contract: it is part of the service you asked for, and every one of these fields is optional. Our AI provider, Anthropic, receives your household make-up, your commute postcode, your budget and the affordability figures we derive from your settings (for example, the estimated monthly mortgage, what share of your income it is, the share of the price your deposit covers and the monthly headroom left over). It is not sent the income or savings figures you entered — though anything you type into a chat message is sent as you wrote it.
2.4 Technical Data
- Browser type and version
- Device information
- IP address (collected by authentication provider)
- Session cookies for authentication
- Security signals: when you use the address lookup, Vercel BotID (from our hosting provider) collects signals about your browser and device and sends them with the request, so we can tell a person from an automated script. This is used only to protect the service, which is why it does not need your consent (PECR reg. 6(4), strictly necessary), and relies on our legitimate interests in keeping the service secure (Article 6(1)(f)).
- The page on our site you first landed on during the visit in which you created your account, and the site that referred you to it — recorded as that site's address only (for example “google.com”), never the search terms you typed. It is written to your account once and never changed afterwards, and it tells us which of our pages actually bring people to HomeThink. We rely on our legitimate interests in understanding how people find the service (Article 6(1)(f)).
To hold that last item until you sign up, we keep it in your browser's session storage, which your browser clears when you close the tab. It is not a cookie, it is never read by anyone else, and if you do not create an account it is never sent to us at all.
2.5 Analytics Data
We use PostHog for product analytics, routed through our own domain, and Vercel Web Analytics for page-level traffic measurement. There are three separate streams, and they are governed differently.
Browser analytics (consent-gated)
Only collected once you accept analytics cookies. Nothing is sent from your browser before then, and accepting is entirely optional. This stream covers:
- Page views and navigation patterns
- Feature interactions (e.g., properties added, tabs viewed, valuations requested)
- An anonymous device identifier stored on your device
- For signed-in users: your account identifier, linked to analytics events. Your name and email address are not sent.
Traffic measurement (consent-gated)
Also only collected once you accept analytics cookies — the script is not loaded at all before then. Vercel Web Analytics records which pages are viewed, the referring site, and coarse device and country information. It is not linked to your account and we do not send it your name or email address.
Service telemetry (legitimate interests)
A small set of events is recorded on our servers when the underlying action happens, whether or not you have accepted analytics cookies. We rely on this to know that the service works, what it costs us to run, whether payments succeed, and how the website and the app are used so we can improve them — we could not operate the product reliably without it, and consent-gated data cannot answer those questions because it undercounts by an unknown amount.
- Analyses started, completed, and failed; free daily limits reached
- That you looked up a home (not which one), and whether your phone's location found the postcode (Around me)
- Subscription and billing lifecycle events (checkout started, started, cancelled, payment failed)
- When you are signed in and not subscribed, which Pro offers you were shown or pressed, counted once a day each and kept for 180 days
These records carry an internal account or session identifier and factual details of the action (such as which feature ran and whether it succeeded). Where you are not signed in, that identifier is the one generated for your visit; no IP address, and no value derived from one, is attached to these events. We do separately hold a hashed form of your IP address on the records that apply fair-use limits, and on a message you send us through the contact form, so we can stop abuse. That hash stays in those records — it is never sent to our analytics provider. They never include your name or email address, and we do not collect the content of any property, note, or message — though an error report may incidentally include the page or request that failed. This processing relies on our legitimate interests in operating, securing, improving and billing for the service (Article 6(1)(f) UK GDPR) rather than on consent. You have the right to object — see section 7.
See our Cookie Policy for full details of the browser stream.
2.6 Contact and Support Messages
When you write to us through the contact form or the in-app help, we hold your name, your email address, what you wrote and our replies, and a one-way hash of your IP address (to stop abuse of the form). We use them to answer you and keep a record of what was said. The legal basis is our legitimate interests in supporting our users, or contract where the message is about your account or subscription. We delete a conversation 24 months after its last message.
3. Legal Basis for Processing
We process your personal data under the following legal bases:
- Contract Performance: Processing your property research requests, delivering AI analysis, and managing your subscription
- Legitimate Interest: Improving our service, preventing fraud, ensuring platform security, and the server-side service telemetry described in section 2.5
- Consent: Optional browser analytics and functional storage. You can withdraw this at any time in Settings → Legal & Privacy → Cookie preferences, and withdrawing is as easy as giving it.
- Soft opt-in (PECR reg. 22(3)): Occasional email with product tips and offers about HomeThink and HomeThink Pro, a similar service to the one you signed up for or bought. When you create an account we tell you we will send these and give you a box to tick to refuse them; if you tick it, or have not been shown that notice, we send none. Every one of those messages carries a one-click unsubscribe link that works without signing in, and we record when and why we became entitled to send it. Receipts and “your report is ready” notices are not marketing and are covered by Contract Performance above — unsubscribing does not stop them.
- Legal Obligation: Complying with UK tax and financial regulations
4. How We Use Your Data
We use your personal data to:
- Create and manage your account
- Process property analysis requests using AI
- Facilitate payments and manage your subscription
- Provide customer support
- Send service-related notifications (e.g., subscription confirmations, renewal receipts)
- Improve the quality of our analysis and the service
- Understand how users interact with HomeThink and improve the experience (with your consent, via analytics)
- Record a small set of product events on our servers, without analytics cookies or consent, on our legitimate interests in running and improving the service (see 2.5)
- Detect and prevent fraudulent activity
- Comply with legal obligations
5. Third Parties and Public Registers
We share your data with third-party service providers who help us operate HomeThink. Those processors are contractually bound to protect your data and use it only for the purposes we specify.
Separately, building a report means looking a property up in public registers and open datasets. Those bodies are not our processors and we have no contract with them; what we send them is set out in 5.2 below, and it is a fact about the property rather than a fact about you.
5.1 Service Providers
- Clerk (US-based): Authentication and user management. Processes email addresses and authentication tokens. If you buy a single report without an account, we create one for you from the email address you give Stripe at checkout, or add the report to the account that email already has.
- Convex (US-based): Database and backend infrastructure. Stores all application data including properties, analyses, and user preferences.
- Stripe (US-based): Payment processing. Handles all payment card details (we never see your full card number). If you start a Pro trial, we keep the fingerprint Stripe gives that card, a code that cannot be turned back into the number, so a card can have only one trial. If you ask us to delete your account we remove your link to it and keep the code alone. For a single report bought without an account, Stripe collects your email at checkout and gives it to us to create your account.
- RevenueCat (US-based): Subscription status for Pro bought in the HomeThink app. Receives your account identifier and the App Store or Google Play purchase receipts, and tells us whether that subscription is active — see 5C.
- Expo (US-based): Delivers updates to the HomeThink app. Receives a random identifier for each installation, your IP address, your phone's operating system and the app's version — see 5C.
- Anthropic (US-based): The AI provider behind our analysis and AI tools. Receives the details of the home you check (the address you typed, the facts you confirmed and the public-record data we gathered for it), your stated preferences — including your household make-up, your commute postcode and the affordability figures we derive from your settings, but not the income or savings figures themselves (see 2.3) — and the questions you ask an AI tool. It is not sent any listing photographs; if you upload your own viewing photos (Pro), it receives those once, for the condition read. Anthropic does not train its models on data submitted through its business API. Per Anthropic's commercial terms at the time of writing, it deletes API inputs and outputs within 30 days, unless it must keep them longer to enforce its usage policy or to comply with the law.
- PostHog (US-based): Product analytics. When you consent to analytics cookies, PostHog receives page views, feature interactions, and for signed-in users your account identifier (never your name or email address), to help us understand user journeys and improve the service. Separately, and regardless of your cookie choices, we send PostHog a small set of pseudonymous server-side events recording actions taken in the product (for example: a report was generated, a subscription started). These carry your account identifier but not your name, email address or IP address, and we rely on legitimate interests for them — see section 2.5. You can object to this processing at any time by contacting us.
- Sentry (EU-based, Frankfurt): Error monitoring. Receives technical details of errors that occur while you use HomeThink, with your account identifier if you are signed in — not your name or email address — so we can understand a failure that affected you. We rely on legitimate interests in keeping the service working. Only if you have allowed analytics in the cookie banner may Sentry also record a masked replay of a browser session in which an error occurs — text content and media are obscured before leaving your device. Without that consent no replay is recorded and nothing is stored on your device for it.
- YourMail (UK-based): Email delivery. Receives your name and email address in order to deliver the emails you have asked for, or that we must send you about your account.
- Cloudflare (US-based): Bot protection on sign-in and sign-up. Our sign-in provider, Clerk, loads Cloudflare's bot check (Turnstile) on those forms; it receives your IP address and browser characteristics in order to distinguish you from automated traffic.
- Vercel (US-based): Website hosting and delivery. Processes the requests your browser makes to us, including your IP address, in order to serve the site.
- OpenRouteService (HeiGIT gGmbH, Germany): Travel-time calculation. Receives the start and end coordinates of a commute or travel-time area you ask us to calculate. It is not told who you are.
- Google (US-based, Google Maps Platform): Street View photos. Every report shows a street-level photo of the home, including one made without an account, and so does a link its owner shares. To find it, our servers send Google the home's address line and postcode, and the viewer's browser then loads the photo from Google directly, so Google also receives that viewer's IP address and browser details. Google is not told who anyone is. We keep only Google's photo reference and capture date, not the photo itself.
- Vercel Web Analytics (US-based): Page-level traffic measurement, loaded only if you accept analytics cookies. Receives the page you are viewing, the site that referred you, and coarse device and country information. It is not linked to your account — see section 2.5.
5.2 Public register and map lookups
To build a report we look a property up in a number of public registers and open datasets. Our servers make these requests; none of them is told who you are, and none receives your name, email address or account identifier. What each receives is the fact about the property that the lookup needs:
- Ministry of Housing, Communities and Local Government (UK), the EPC register: the property's postcode, to retrieve its energy performance certificates. The first line of the address you type is matched against those certificates on our servers, not sent.
- postcodes.io (UK): the property's postcode, to find where it is and which areas it falls in.
- HM Land Registry (UK): the property's postcode, or its outward code, to retrieve recorded sale prices.
- data.police.uk (UK): the property's approximate coordinates, to retrieve street-level crime counts.
- Environment Agency (UK): the property's approximate coordinates, for flood and noise data.
- planning.data.gov.uk (UK): the centre point of the property's postcode, to find conservation areas, Article 4 directions, tree preservation areas and green belt there.
- UK PlanIt (UK, a volunteer-run index of council planning registers): the centre point of the property's postcode, to find planning applications nearby. This is a third-party service, not a government one.
- Historic England (UK): a small bounding box around the property, for listed buildings.
- Ofsted (UK): the property's approximate coordinates, to find nearby schools and their ratings.
- Overpass API (community-run servers in the EU, querying OpenStreetMap data): the property's approximate coordinates, for nearby amenities. This is a third-party service, not a government one.
- Imperial College London air quality API (UK): the code of the nearest published monitoring station. It is not sent the property's address or coordinates.
- Bank of England and public news feeds (UK): nothing about you or your property — these are fetched on a schedule for market rates and property news.
Some parts of the site are drawn by your own browser, which contacts these parties directly. That means they see your IP address and the location you are looking at, and we cannot see or control what they log:
- OpenStreetMap Foundation (UK-based): the map tiles for the maps and map thumbnails, requested from openstreetmap.org.
- OpenFreeMap (a free, community-funded map tile service): the vector map styles and tiles used by the maps inside a report and by the maps on the address lookup, which show the postcode you entered or the area you move the map to; in the mobile app, the tiles for the Map tab, which show the area you look at (around you while Near me follows you).
- Environment Agency (UK): the flood-zone overlay drawn on top of a map.
- data.police.uk and postcodes.io (UK): crime and postcode lookups on the maps, on the address lookup and on some of the free tools, made from the page rather than from our servers. On the address lookup postcodes.io receives the postcode you type (to place it on the map) and, if you find the home on a map, the town or village name you type (to find the place) and the point you tap on the map, as a latitude and longitude (to find the postcodes nearest it). If you tap Around me and allow it, postcodes.io receives your approximate position, rounded to about 10 metres, to name the postcode there (section 5D).
5.3 International Transfers
Some of our service providers are located outside the UK, mostly in the United States. Where that is a restricted transfer under Article 44 and a data processing agreement is in force with the supplier, it is made under the UK Addendum to the EU Standard Contractual Clauses — the instrument the UK actually uses, alongside the International Data Transfer Agreement (IDTA). Where we have not yet confirmed that agreement, the register says so for that supplier. Not every supplier involves a transfer at all: some process in the EU (covered by the UK's adequacy regulations) and one in the UK.
The mechanism that applies to each individual supplier — and whether one is needed — is stated per supplier in the sub-processor register, rather than summarised here.
6. Data Retention
We retain your personal data for as long as necessary to provide our services:
- Account data: Retained while your account is active. When you delete your account we erase your personal data from our database (Convex) immediately rather than holding it for a recovery window, so deletion cannot be undone. At the same time we ask PostHog to delete your analytics person record and the events linked to it and, a few hours later (once any refund of a single report bought on Google Play has gone through it), RevenueCat to delete the purchase record it holds for your account if you used the app. Apple and Google keep their own purchase records under their terms. Error reports already held by Sentry are not deleted one by one; they age out under Sentry's retention, within 90 days. Expo's logs of the app's update checks are not linked to your account, so deleting it does not erase them; they age out under Expo's retention. Stripe keeps your customer and payment records for 7 years, for tax (see below). If you ever started a Pro trial we keep your card's fingerprint, with no link to you, for as long as we offer trials, so that the card cannot have a second one. If you bought a single report in the app we keep the store's id for that purchase, with no link to you, so that one purchase cannot buy a second report
- Property analyses and preferences: Retained while your account is active
- Transaction records: Retained for 7 years to comply with UK tax regulations, including the customer and payment records Stripe holds for us
- Contact and support messages: deleted 24 months after the last message in the conversation. If you delete your account, messages you sent while signed in are deleted with it
- Chat about a report and Agent conversations: both chats were withdrawn on 17 November 2026. Past conversations are no longer shown and are deleted by 31 December 2026; until then they are deleted with your account and included in your data export
- A report made without an account: deleted 30 days after you create it, unless you sign up and save it to your account, after which it is kept like any other property
- Analytics data: Retained by PostHog according to our project settings (currently up to 1 year). You can withdraw consent at any time, after which no new data is collected
After the retention period expires, we securely delete your personal data from our systems. HomeThink no longer takes content from property listings. Listing content captured before that change is being deleted, and in any case is kept no longer than the limits below, whether or not your account is still active. Each 7-day and 30-day limit counts from when the property was first added. Deletion runs once a day, so content can remain for up to a day after its limit.
- The raw page content a capture sent: deleted once the property is 7 days old.
- The listing's description, key features and the snapshot the extraction was read from: deleted once the property is 30 days old.
- The name of the estate agent, as the listing gives it: deleted once the property is 30 days old. It is read from the listing when we extract its details, is never shown on a shared report, and is not used in our analysis or chat after that.
- The web addresses of a listing's photographs, floorplan and EPC graphic: deleted 3 days after the capture, at the next daily clean-up. No longer collected or used.
- Viewing photos you upload (Pro): read once by our AI provider for a condition read, then deleted straight after the read. Photos you upload but never send are deleted within a day. We keep what the read found, with the property.
- Rankings of your homes: deleted after 90 days. They hold no photo link.
For as long as you keep a property, we keep its address, asking price and property facts (such as bedrooms, type, tenure and floor area), our analysis and scores, and your own notes and chat. These are deleted when you delete the property or your account.
We do not display any listing photograph, floorplan or EPC graphic on HomeThink, and we never download, copy or host the images themselves. We no longer record a “main photo” link for a property or a ranking. Short phrases quoted from the agent's wording are kept as part of the analysis itself and are not covered by these limits.
7. Your Rights Under UK GDPR
You have the following rights regarding your personal data:
- Right of Access: Request a copy of the personal data we hold about you
- Right to Rectification: Correct inaccurate or incomplete data
- Right to Erasure: Request deletion of your data (subject to legal retention requirements)
- Right to Data Portability: Receive your data in a structured, machine-readable format
- Right to Object: Object to processing based on legitimate interests
- Right to Restrict Processing: Limit how we use your data in certain circumstances
- Right to Withdraw Consent: Where we rely on your consent (for example optional analytics storage), withdraw it at any time, as easily as you gave it. Withdrawing does not affect processing that happened before
- Right to Complain: Complain to the Information Commissioner's Office (ICO) — see section 12
To exercise any of these rights, contact us at support@mathersoftware.com. We will respond within one month of receiving your request (extendable by up to two further months for complex or numerous requests, in which case we will tell you why within the first month).
8. Cookies and Tracking
We use essential cookies to operate HomeThink and optional analytics cookies (Vercel Web Analytics and PostHog) to understand how users interact with our service. Analytics cookies are only enabled with your explicit consent and can be withdrawn at any time via the cookie consent banner or Settings → Legal & Privacy → Manage Cookie Preferences.
For detailed information about the cookies we use and how to manage them, please see our Cookie Policy.
9. Data Security
We implement industry-standard security measures to protect your personal data, including:
- Encryption of data in transit (TLS/HTTPS)
- Encryption of sensitive data at rest
- Continuous error and availability monitoring
- A published security contact, so anyone who finds a problem can tell us: security.txt
- Access controls limiting who can view your data
- Secure authentication via Clerk
- Bot detection on the address lookup (Vercel BotID) and on sign-up (Cloudflare, via Clerk)
While we take reasonable precautions, no internet-based service can be 100% secure. You are responsible for maintaining the confidentiality of your account credentials.
If a personal data breach happens, we will notify the ICO within 72 hours of becoming aware of it where the law requires, and if it is likely to result in a high risk to you, we will tell you without undue delay.
10. Children's Privacy
HomeThink is not intended for users under the age of 18. We do not knowingly collect personal data from children. If you believe a child has provided us with personal data, please contact us immediately so we can delete it.
5A. Sub-processor register
The suppliers above are our processors under Article 28. The full register — what each one does, where it is, what it receives and the transfer mechanism — is maintained at /legal/sub-processors. If we add one, we will update that page before they begin processing.
5B. Data about homes and the people who live in them
A HomeThink report is about an address, and an address is someone's home. To build one we use public registers and open datasets about that address and the area around it — for example the energy performance certificate (EPC) register, HM Land Registry's price paid data, police-recorded crime and planning records. Some of that information may relate to the people who own or live in the home, even though they are not our users.
- The EPC register publishes each certificate with its address. We match the first line you type against those certificates on our servers, only to find the right home. We do not show that address text, store it or send it to anyone.
- The EPC rows for a postcode are cached on our servers for 24 hours, so that looking up a second home in the same postcode does not ask the register again.
- We do not try to find out who owns or lives at an address, and a report does not name them.
Our legal basis is legitimate interests (Article 6(1)(f) UK GDPR): helping people research a home they are thinking of buying or renting, using information the government has already published for that purpose. Because we cannot identify or contact the people living at an address we look up, we do not notify them individually; Article 14(5)(b) UK GDPR allows this where doing so would be impossible or involve disproportionate effort, and this section is how we make the information public instead. If you live at an address and want to ask about or object to this processing, contact support@mathersoftware.com.
5C. The HomeThink app
The HomeThink app for iPhone and Android uses the same account and the same data as the website, and everything else in this policy applies to it. In addition:
- Buying Pro in the app. A subscription bought in the app is sold by Apple (App Store) or Google (Google Play), who take the payment and hold your payment details. They act as independent controllers of that purchase under their own privacy policies, not as our processors; we never see your card or store account details. RevenueCat (US-based), our processor for this, receives your HomeThink account identifier and the purchase receipts Apple or Google issue, and tells us whether your subscription is active, renewing or expired. It is not sent your name or email address.
- Staying signed in. The app keeps your sign-in token in your device's secure storage (the iOS Keychain or Android Keystore) so you stay signed in. It is strictly necessary for the app to work, is never used for anything else, and is removed when you sign out.
- The Tools tab. The app remembers which groups of tools you left open, in the same secure storage on your phone, so the tab opens as you left it. It is only the names of those groups, is never sent to us, and is used for nothing else.
- Around me. If you tap “Around me” and allow location access, the app reads your phone's location once and asks your phone's own location service (Apple on iPhone, Google on Android, under their privacy terms) for the postcode there. Only that postcode reaches us, as if you had typed it, with a note that Around me found it so we can count how often it is used. We never receive or keep your phone's precise location, and the app never reads it in the background. Around me on our website's pages inside the app (such as the tools) works the same way: the app names the postcode on your phone and hands the page only that.
- Approximate location. A postcode is approximate location. One that Around me or a tap on the map names reaches us exactly as one you type: with the home you look up. Your phone's precise position never reaches us.
- Your name. If you sign in with Apple (Sign in with Apple) or Google, they share your name and email address with Clerk, our sign-in provider (section 5.1), which holds them for your account; we keep a copy of the name with your account (section 2.1). Apple lets you hide your email address, and we then receive Apple's relay address instead.
- The map. If you tap “Near me” on the Map tab and allow location access, the map shows and follows where you are on your phone only; your location is never sent to us, stored or logged. Tapping “Look up a home here” or “Check this postcode” on an area asks your phone's own location service (Apple on iPhone, Google on Android, under their privacy terms) for the postcode at the point you tapped, and only that postcode reaches us. For a postcode check our server then sends that postcode's centre (never your position) to Police UK and the Environment Agency, and the postcode to postcodes.io and HM Land Registry, as our website's free tools do. On Android this needs location access too, because Android's location service requires it; your position is still not read. The map's background tiles come from OpenFreeMap (section 5.2), which, like any map service, sees your IP address and the area the map shows, including the area around you while Near me follows you. The map's tiles and area figures are kept only as a cache in the app's own storage on your phone.
- Preferences and support. Your preferences open as a page of our website inside the app and are saved as they are on the website. A support message you send from the app is kept as one sent from the website (section 2.6), together with the app's version and your phone's operating system version, so we can reproduce a problem.
- Website tools, the sample report and setup. The Tools tab's other tools, the sample Full report and the setup questions a new account is offered open as pages of our website inside the app, and send us and our providers exactly what the same pages do on the website (sections 2 and 5). The tools and the sample open without signing you in; your setup answers are saved to your account as they are on the website.
- Crash and diagnostic data. If the app crashes or hits an error, Sentry (EU-based, Frankfurt) receives crash data: technical details of the error, the device and the app's versions, with performance details recorded alongside it (such as memory in use and how long the app had been running). It may receive your account identifier — never your name or email address — as on the website. We use it only to find and fix faults.
- How you use the app. When you use the app, our servers record the same events they record for the website (section 2.5), such as that you looked up a home (not which one, and whether Around me found it) or started a subscription. We use them for product analytics: to understand how the app is used and to improve it. They are linked to your account identifier — never your name or email address — and are recorded by our servers and sent to PostHog (section 5.1), not collected by any analytics tool inside the app. We never use them for advertising and never share them for tracking.
- No tracking. The app contains no analytics or advertising tools of its own and does not track you across other companies' apps or websites. Reports open as pages of our website inside the app, with no cookie banner, so no analytics cookies are set there.
- App updates. The app checks for and downloads updates to its own code from Expo (650 Industries, Inc., US-based), the service the app is built and updated with, acting as our processor. Each check sends Expo a random identifier the app creates for this installation, your IP address, your phone's operating system and the app's version, so it can send the right update. Expo is not told your name, email address or account. The identifier is kept on your phone until you delete the app; it is strictly necessary to deliver the updates and is used for nothing else.
- Deleting your account. You can delete your account from the Account tab in the app. It erases your data exactly as deleting it on the website does (see section 6). It does not cancel a subscription bought through the App Store or Google Play — cancel that in your store's subscription settings.
5D. Around me on the website
Wherever our website asks for a postcode to say where to look, you can tap “Around me” instead of typing it:
- Your browser asks first. Your browser asks your permission before it shares your location with the page, and reads it once, when you tap. You can refuse or withdraw that permission in your browser's settings at any time, and type the postcode instead.
- Only postcodes.io sees it. If you allow it, your browser sends your approximate position (rounded to about 10 metres) directly to postcodes.io (section 5.2) to find the nearest postcode, and puts that postcode in the box as if you had typed it. If you are clearly outside the UK, nothing is sent; close to the Irish border we cannot always tell, so the position may still go to postcodes.io.
- HomeThink never receives it. Your position is never sent to us, stored, logged or used for analytics. Only the postcode reaches us, when you go on to use it, exactly as a typed one would.
- In the HomeThink app, Around me on these pages uses the app's own location pick instead (section 5C): your phone names the postcode and nothing is sent to postcodes.io.
10A. Automated analysis and profiling
Almost everything HomeThink produces is automated. Two of those automated processes are about you rather than about a property, which is what data protection law calls profiling, so they are worth setting out plainly.
- Your preferences summary. We use AI to turn the preferences you enter — budget, areas, household, priorities — into a short written summary, so reports can be framed around what you told us matters.
- A fit score. Where you have given us preferences, a report can show how well a property matches them.
Neither produces a decision with a legal or similarly significant effect on you, so Articles 22A–22D UK GDPR (automated decision-making) do not apply: nothing here decides whether you get credit, a service, or a price. The property score is a different thing again — it is about the house, not about you.
How the property score is reached is deliberately open. It is calculated by a fixed formula rather than by the AI — the model is not permitted to output the score at all — and every report shows the weight of each category, what it contributed, and the evidence behind it. You can change the offer price on any report and watch the score recalculate.
You can object to profiling at any time by emailing support@mathersoftware.com, and you can clear the preferences it draws on from your account settings. If you think a report has something wrong, tell us — corrections you send are fed back into the analysis.
11. Changes to This Policy
We may update this Privacy Policy from time to time to reflect changes in our practices or for legal, operational, or regulatory reasons. Material changes will be communicated via email or prominent notice on our website.
Continued use of HomeThink after changes take effect constitutes acceptance of the updated policy.
12. Complaints
If you have concerns about how we handle your personal data, please contact us first at support@mathersoftware.com. We will acknowledge your complaint within 30 days and do our best to resolve it.
You also have the right to lodge a complaint with the UK's data protection authority:
Information Commissioner's Office (ICO)
Website: ico.org.uk/make-a-complaint
Helpline: 0303 123 1113
Our ICO registration number: ZC256628
13. Contact Us
For any questions about this Privacy Policy or how we handle your data, please contact us:
Email: support@mathersoftware.com
Data Controller: Mather Software Ltd