Skip to main content
Contact
English
  • English
  • EspañolSpanish
  • 简体中文Chinese (Simplified)
  • العربيةArabic
  • FrançaisFrench
  • PortuguêsPortuguese
  • 日本語Japanese
  • DeutschGerman
Get early access

Privacy Policy

Last updated: 10 October 2026

This policy explains what personal data we collect when you use our website and service, why we use it, who we share it with, how long we keep it, and the rights you have. It is published at orimetis.com/privacy, and it is linked from the waitlist form and from the footer of our website.

1. Who we are

The controller of your personal data is Havivah Limited, a company registered in England and Wales under company number 06895543, VAT number GB193319689, trading as Orimetis. "We", "us" and "our" mean Havivah Limited.

To contact us about privacy, or to use any of your rights, write to privacy@orimetis.com. For anything else, write to hello@orimetis.com. Report a security concern to security@orimetis.com.

2. Who this policy covers

  • people who join our waitlist;
  • people who create an account, buy a plan or buy a property report, and members of a customer's team;
  • affiliates who join our affiliate programme;
  • people who write to us through the contact form or by email;
  • people who use the public help chat;
  • people who visit our website; and
  • people who appear in the property records we use to build the service (section 13).

3. The personal data we collect, and where it is held

We collect personal data from you when you sign up, use the service, pay or contact us; from your browser when you visit; and from Google or Apple if you choose to sign in with them. The table names the record in our database where each category is held.

Category What it contains Where it is held
Waitlist Your email address, the language of the page you joined from, and the city you pick, if you pick one. Our email provider, Loops (section 5).
Account and sign-in Email address, full name, a hash of your password (not the password itself), whether your email is verified, whether the account is active, last sign-in time, and the dates the account was created and changed. If you sign in with Google: your Google account identifier and profile picture address. If you sign in with Apple: your Apple account identifier. users
Preferences Interface language, display currency and the persona you chose (investor or operator). users
Referral and attribution Your own referral code, how you came to us (for example "direct", "google" or "apple"), and the affiliate code you arrived with, if any. users
Plan and billing Your plan, Stripe customer and subscription identifiers, subscription status, currency, amount, billing interval, the start and end of the paid period, and the cancellation time. For a plan that covers one city, which city. subscriptions, subscription_cities
Purchases For each property report you buy: the property, city, Stripe checkout session, amount, currency, and how many times and when it was downloaded. purchased_reports
Checkout records When you buy as a consumer, the withdrawal sentence you were shown, that you ticked it, and the time. We store this with the purchase at Stripe. Stripe
Your work in the service Saved properties and your notes on them; saved searches (name, city, criteria); alerts and their criteria; alert decisions and your feedback on them; operator sites (name, concept, address, postcode, location, rent, floor area, weekly revenue, opening date, status, notes); shared links and the snapshot each one shows; feature usage counts. saved_properties, saved_searches, alerts, alert_decisions, operator_sites, shared_links, feature_usage
Teams Organisation name, owner, and for each member their account, role, and when they were invited and accepted. organizations, organization_members
API usage For each request to our API made while you are signed in: your user identifier, the endpoint, the method, the status code and the response time. api_usage
Enterprise API keys Customer name, contact email, a hash of the key, allowed website origins, Stripe identifiers and notes. Per-request usage records hold the key, endpoint, time, response time and status. enterprise_api_keys, enterprise_api_usage
Affiliates Email, a hash of the password, full name, affiliate code, language, display currency, Stripe Connect account identifier, country and readiness; conversions (referred account, plan, amounts, commission); payouts. affiliates, affiliate_conversions, affiliate_payouts
Affiliate link clicks When someone opens a registration link that carries an affiliate code: the code, the visitor's IP address, the browser's user-agent string, and the time. affiliate_clicks
Payment events The event messages Stripe sends us about checkouts, subscriptions, invoices, refunds and disputes, stored as received. These can include your email address, billing details and amounts. webhook_events
Reviewer access If we give you a reviewer access code: the email it was created for, and when and by which account it was used. reviewer_access_codes
Contact form Your name, email address, the topic you chose and your message. We receive these by email. Our inbox, through Postmark
Help chat and server logs See section 4.4. Server logs
Browser storage Cookies and similar storage on your device. See the Cookie notice. Your browser

We do not store your card number. Card details are entered on Stripe's payment page and held by Stripe.

4. How we use personal data, and our lawful bases

4.1 Purposes and lawful bases

Purpose Data used Lawful basis under UK GDPR
Telling you once when we open Waitlist Consent. You can withdraw it at any time (section 5).
Creating and running your account, and providing the service, saved work, alerts, reports, teams and the assistant Account, preferences, plan, your work, teams Contract: we need it to provide the service you asked for.
Taking payment, applying tax, issuing invoices, refunds and handling disputes Plan and billing, purchases, checkout records, payment events Contract; and legal obligation, for keeping tax and accounting records.
Recording your request to start immediately and your acknowledgement about the 14-day cancellation right Checkout records Legal obligation, and our legitimate interest in being able to show what you agreed.
Sending service emails: email verification, password reset, alert and saved-search matches, changes in the value of saved properties, payment confirmations, failed-payment notices, renewal reminders and plan changes Account, preferences, plan, your work Contract.
Sending you emails about getting started and about our plans after you sign up Account, preferences, plan Legitimate interests, in telling our users about the service they signed up to. You can object at any time (section 10).
Answering your messages and help chat questions Contact form, help chat Legitimate interests, in replying to you.
Keeping the service secure, preventing abuse and fraud, enforcing rate limits and plan limits, and diagnosing faults Account, API usage, server logs, error reports Legitimate interests, in running a secure and reliable service.
Measuring how the website is used Analytics (section 6) Consent, given through "Accept all" in the cookie bar.
Running the affiliate programme and attributing referrals Affiliates, affiliate link clicks, referral and attribution Contract, with the affiliate; legitimate interests, for attributing a sign-up to the link that produced it.
Building property and location information from public records Property records (section 13) Legitimate interests, in providing property information to the public and to our customers.
Complying with the law and dealing with legal claims Any of the above, as needed Legal obligation; legitimate interests.

Where we rely on legitimate interests, we have weighed our interests against yours. You can ask us for details, and you have the right to object (section 10).

4.2 We do not sell personal data

We do not sell personal data, and we do not use advertising cookies or advertising trackers.

4.3 Automated decisions

We do not make decisions about you that have legal or similarly significant effects based solely on automated processing. Estimated values, scores and alert decisions are automated outputs about properties and places, not decisions about you.

4.4 Help chat and server logs

When you use the public help chat, our server log records the help context, the plan you are on, the page, the city, your language, the first 200 characters of your question, and whether property details were attached. We do not store help chat conversations or workspace assistant conversations in our database. When the contact form cannot be sent by email, our server log records your email address and the topic instead. Server logs also record events such as sign-ups, sign-in failures, payment events and account deletion, and some of these log lines include your email address.

5. The waitlist

If you join the waitlist on orimetis.com, we collect your email address and the language of the page you joined from, so that we can write in your language. If you pick a city, we keep that too, so that we know where people want Orimetis to open.

We use your email address for one purpose only: to tell you, once, when we open. We do not use it for any other marketing, and we do not create an account for you.

Our lawful basis is your consent, which you give by submitting the form. The address is sent to Loops, the email service we use, and held there.

We keep your address in Loops until you ask us to remove it. To be removed at any time, write to privacy@orimetis.com from the address you signed up with, and we will delete it from Loops. Our emails have an unsubscribe link. It stops our emails but does not delete your address, so write to us if you want it deleted. If you later create an Orimetis account with the same address, the account uses the same record in Loops. Deleting your account deletes that record. Removing yourself does not affect anything we did before you asked.

6. Analytics and error reporting

Product analytics (PostHog). Only after you choose "Accept all" in the cookie bar, and only when analytics is configured, your browser loads PostHog. It records page views, page leaves, and clicks and other interactions on the page. It is configured to keep its identifiers in memory rather than in a cookie or browser storage, and not to create a profile of you. We do not identify you to PostHog: we do not send it your name, email address or account identifier. Data is sent to PostHog's EU host, eu.i.posthog.com.

Error reports from your browser (Sentry). Only after "Accept all", and only when configured, your browser sends reports of errors to Sentry. Before a report is sent, cookies and the authorisation header are removed. If you are signed in, the report includes your account identifier and your plan. Performance traces are sampled at 10% of page loads. Session replay recording is not switched on in our setup.

Error reports from our servers (Sentry). When our servers are configured to use Sentry, errors on our servers are reported to Sentry whatever you chose in the cookie bar, because this is needed to keep the service working. These reports include the request address with any token, code, key or secret in it filtered out, the request headers without the authorisation, cookie and API key headers, and, if you are signed in, your account identifier and plan. They can include the body of the request, except for sign-in, registration and password-reset requests, whose body is removed. Sentry's option to send default personal data, such as your IP address, is turned off. By default, performance traces and profiles are sampled at 10% of requests.

7. Who receives personal data

We share personal data only with the service providers below, who act on our instructions, and where the law requires it. We do not share it with anyone for their own marketing.

Provider What it is for What it receives
Stripe Payments, tax calculation, invoices, the billing portal, and affiliate payouts through Stripe Connect. Your email address, billing address, payment details (entered directly on Stripe's page), tax number if you give one, the plan or report bought, the city for a single-city plan, the property for a report, your account identifier, any referral code, and for consumer purchases the withdrawal sentence you ticked and the time. For affiliates, the details Stripe asks for to set up payouts.
Loops Lifecycle and service email, and the waitlist. Waitlist: email address, language and, if you picked one, city. Account holders: email address, first and last name, account identifier, plan, language, display currency, how you came to us, and last sign-in time; and event details for the emails it sends, such as your plan, receipt link, renewal date, alert city and criteria, and counts of matches or value changes.
Postmark Sending email verification, password reset and alert emails, and forwarding contact form messages to our inbox. Your email address and the content of the message, including verification or reset links; for the contact form, your name, email address, topic and message.
Anthropic Generating answers in the public help chat and the workspace assistant, and explanations for alerts. What you type, recent turns of the conversation that your browser sends with it, the page and city, and property information shown on screen. For alert explanations, your alert criteria and the listing details, without your name or email address.
Sentry Error reporting (section 6). As described in section 6.
PostHog Product analytics, only after "Accept all" (section 6). As described in section 6.
Google Sign-in with Google, if you choose it. Google tells us your email address, name, Google account identifier and profile picture address.
Apple Sign in with Apple, if you choose it. Apple tells us your email address, your Apple account identifier and, the first time you sign in, your name.
Hetzner Hosting our servers, databases and backups. All of the data we hold in our database and logs, which it stores for us.
GitHub (protomaps.github.io) Supplying the fonts and icons used to draw the map. Your browser requests these files directly, which shares your IP address and browser details with that host. Map tiles themselves are served from our own servers.

Our website fonts are served from our own servers, not from Google.

We may also disclose personal data if the law requires it, to protect our rights or the safety of others, or to a buyer if our business is sold, in which case this policy continues to apply.

8. International transfers

Our servers, databases and backups are hosted with Hetzner in its EU central network zone. PostHog analytics data is sent to PostHog's EU host. Some of our other providers may process personal data outside the UK. Where personal data is transferred outside the UK, we make sure it is protected by UK adequacy regulations or by the International Data Transfer Agreement or the International Data Transfer Addendum issued by the Information Commissioner. You can ask us for a copy of the relevant safeguards at privacy@orimetis.com.

9. How long we keep personal data

Data How long we keep it
Waitlist Until you ask us to remove it, or until you delete an account you created with the same address (section 5).
Account, preferences, plan and your work While your account is open. When you delete your account, your email address is replaced with a placeholder, your name is replaced with "Deleted User", and your password is removed at once. 30 days later, the account and everything linked to it are deleted. If payment, purchase or tax records are linked to it, a record of the account with no contact details is kept with them until they are deleted.
Signed-in session Your sign-in cookie lasts 30 minutes and is renewed while you use the service. Your session refresh cookie lasts 30 days.
Email verification and password reset links A verification link expires after 24 hours. A password reset link expires after one hour.
Short-lived security records Records used to block a signed-out session last until that session would have expired. Sign-in with Google or Apple uses a check that lasts two minutes and a one-time code that lasts one minute. Limits on repeat verification and reset emails last five minutes. Rate-limit counters last for the length of the rate-limit window.
Payment, purchase and tax records, and payment events Kept for 7 years, because tax and accounting law requires us to keep records of sales, then deleted. For a subscription, the 7 years start when it ends. Stripe also keeps its own records of your payments and invoices.
API usage and affiliate link clicks Kept for 12 months. They are then reduced to daily counts with no account, API key, IP address or browser details, and deleted. When you delete your account, your API usage is reduced to those counts when the account is deleted.
Backups Each day our customer database is backed up on the server it runs on, and those backups are deleted automatically after 90 days. Each night the backups are also copied off that server to a Hetzner Storage Box, encrypted with Borg. That copy keeps the last 30 daily, 12 weekly and 24 monthly copies, and each copy holds up to 90 days of backups, so data you delete can remain in it for up to about 27 months. Data you delete stays in older backups until those backups are deleted.

What deleting your account does

You can delete your account from the account panel in the workspace. When you do, straight away:

  • if you have any subscription that can still be billed, we cancel it at Stripe;
  • your account is deactivated and marked as deleted, with the date;
  • your email address is replaced with a placeholder, your name is replaced with "Deleted User", and your password is removed so the account cannot be signed into;
  • your profile picture address, your referral code, how you came to us, and your Google or Apple identifier are removed;
  • your plan is set back to a free account;
  • every session you have open is signed out; and
  • your contact is deleted from Loops, so lifecycle emails stop.

On the day you delete your account, these are kept, not removed:

  • the deactivated account record itself, which keeps your language, display currency, persona, last sign-in time, the dates it was created and changed, any affiliate code you arrived with, and any organisation link;
  • your saved properties and notes, saved searches, alerts and alert decisions, operator sites, shared links, feature usage counts and team memberships, which stay linked to the deactivated account record;
  • your API usage records;
  • your subscription and purchase records, and the payment events Stripe sent us;
  • the records Stripe holds about you, including your customer record, payment methods, invoices and receipts; and
  • server logs and backups, until they are deleted.

After that, our retention job removes what we hold on this schedule. It does not touch the records Stripe holds, server logs or backups.

  • Account, preferences, plan and your work. The deactivated account record and everything linked to it are deleted 30 days after you delete your account. If payment, purchase or tax records are linked to it, the account record stays with them, with your contact details, last sign-in time, persona and organisation link removed, until those records are deleted.
  • API usage and affiliate link clicks. Your API usage records are reduced to daily counts with no account, API key, IP address or browser details, and deleted, 30 days after you delete your account.
  • Payment, purchase and tax records, and payment events. Kept for 7 years, for a subscription counted from when it ends, then deleted. Deleting your account does not shorten this.

If you would like any of the records in the first list deleted sooner, write to privacy@orimetis.com and we will delete those we are not required to keep.

10. Your rights

Under UK data protection law you have the right to:

  • access your personal data and receive a copy of it;
  • rectification, to have inaccurate data corrected or incomplete data completed. You can change your name, language and display currency in the account panel;
  • erasure, to have your data deleted in some circumstances. You can delete your account yourself (section 9);
  • restriction, to ask us to limit how we use your data in some circumstances;
  • data portability, to receive data you gave us in a structured, machine-readable format, or have it sent to another organisation. We can give you an export of your profile, subscriptions, saved properties, alerts and Enterprise API usage in JSON format;
  • object to our use of your data where we rely on legitimate interests, including to the emails we send about getting started and our plans. If you object to those emails, we will stop them; and
  • withdraw consent at any time where we rely on consent, for the waitlist and for analytics, without affecting what we did before.

To use any of these rights, write to privacy@orimetis.com from the email address on your account. We may need to confirm your identity. We will reply within one month. We may extend that by up to two further months for complex requests, and if we do we will tell you why.

11. Complaints

If you are unhappy with how we have handled your personal data, please tell us first at privacy@orimetis.com. You also have the right to complain to the Information Commissioner's Office, the UK regulator for data protection: ico.org.uk/make-a-complaint, or telephone 0303 123 1113.

12. How we protect personal data

  • Passwords are hashed with bcrypt, after a SHA-256 step, and are never stored in readable form. Enterprise API keys are stored only as hashes.
  • Sign-in cookies are HttpOnly, so scripts on the page cannot read them, and are Secure in production, so they are only sent over HTTPS. The session refresh cookie is SameSite=Strict and is sent only to the address that refreshes a session.
  • The token your browser uses for each request is held in memory, not in browser storage, and expires after 30 minutes. Signing out, and deleting your account, revoke your sessions on our server.
  • Our website only accepts HTTPS using TLS 1.2 or 1.3, and tells browsers to use HTTPS only. A content security policy limits which scripts can run and which sites the page can contact, and our pages cannot be framed by other sites.
  • Our live database accepts connections only from our private network, and server ports are firewalled.
  • Requests are rate limited, and request bodies are limited in size.
  • Error reports are filtered before they are sent (section 6).

13. Property records and people in public data

The service is built from public records, such as HM Land Registry price paid data, energy performance certificates, planning data and their equivalents in the other markets we cover. These records describe properties and transactions: addresses, prices, dates and property characteristics. Some records, such as title data, can name the owner of a property. When an owner is an individual, we do not show their name in the service. Company owners' names are shown.

We use these records on the basis of our legitimate interests, under the licences their publishers grant. Where a publisher restricts re-identification of individuals, we respect that restriction, and our terms forbid customers from using the service to identify or target individuals. If you think a record we use is about you, you have the rights in section 10, and you can write to privacy@orimetis.com.

Partners who display our estimates on their own listing pages may send us the listing's location, asking price, currency and features, which we store with a label for the partner. We do not store the listing address. Our widget does not set or read cookies on the partner's page.

14. Cookies

We use cookies and similar browser storage. Our Cookie notice lists each one, what it does, how long it lasts, and how to change your choice.

15. Children

The service is not directed at children, and you must be 18 or over to create an account. We do not knowingly collect personal data from children. If you believe a child has given us personal data, write to privacy@orimetis.com and we will delete it.

16. Personal data breaches

If a personal data breach occurs, we will notify the Information Commissioner's Office within 72 hours of becoming aware of it where the law requires, and we will tell you without undue delay if the breach is likely to result in a high risk to you.

17. Changes to this policy

We may update this policy when our service or the law changes. We will change the date at the top. If a change is significant, we will tell account holders by email before it takes effect. A change to this policy does not reduce your rights under data protection law.

Know the market. Anywhere.

In development.

  • Contact
  • Privacy
  • Terms
  • hello@orimetis.com
  • enterprise@orimetis.com
  • privacy@orimetis.com

Orimetis is a product of Havivah Limited, company number 06895543, registered in England and Wales.

Havivah Limited
71-75 Shelton Street
Covent Garden
London
WC2H 9JQ

  • English
  • Español
  • 简体中文
  • العربية
  • Français
  • Português
  • 日本語
  • Deutsch