Privacy policy

Who we are

This website is operated as Open Banking Compare (“we”, “us”). We publish an independent directory and related content to help businesses evaluate open banking providers, and we operate a short quiz to capture matching requirements.

We do not publish a general contact mailbox on this page. If you need to reach the operator, use any channel we have provided elsewhere (for example a provider inquiry form) where appropriate.

What personal data we collect

• Quiz and lead forms. When you submit the buyer quiz or similar forms, we collect the fields you provide (for example work email, company name, industry, use cases, markets, volumes, timelines, and optional free-text context). We use this to qualify interest and, where applicable, to arrange introductions to providers.
• Provider and partner inquiries. If you submit the “for providers” contact form, we collect the details you enter so we can respond.
• Technical and security data. Our hosting platform and related infrastructure may process standard request metadata (such as IP address, user agent, timestamps, and routing information) to deliver the site and protect it from abuse.
• Optional product analytics. If you accept optional analytics in the cookie banner, we load PostHog (EU region) which may assign identifiers and record usage events. If you decline, PostHog is not loaded.
• Anonymous web analytics.We use Vercel Analytics for aggregate usage metrics as described in Vercel's documentation.

Why we use this data

We process personal data for the following purposes:

• To operate the directory, blog, and quiz, and to respond to enquiries you send us.
• To score and route buyer leads internally and, where agreed, to introduce you to suitable providers.
• To keep the service secure, debug issues, and enforce acceptable use.
• Where required, to evidence consent for optional analytics (PostHog) and to respect your choice if you decline.

Depending on your jurisdiction, our legal bases may include performance of a contract, legitimate interests in running a B2B information and introduction service, and consent for non-essential analytics. Your counsel can map this to GDPR or other frameworks.

Processors and service providers

We use carefully selected vendors as processors, including:

• Vercel — hosting and edge delivery of the site and server-side routes.
• Supabase — database and authentication for operator tools; lead rows are written server-side with strict access controls.
• Resend — transactional email (for example notifications when a lead is submitted).
• PostHog — optional analytics when you click Accept in the cookie banner (EU cloud configuration as deployed).

Each vendor processes data under its own terms and security practices. We configure our stack to keep buyer and lead data in the EU where we select EU regions for hosting and database, consistent with our deployment settings.

Retention

We retain lead and inquiry data for as long as needed to operate introductions, comply with law, resolve disputes, and maintain auditable business records. Technical logs may be retained for shorter security and reliability windows according to our vendors' defaults unless we configure otherwise.

Your rights

Depending on applicable law, you may have rights to access, rectify, erase, restrict, or object to certain processing, and to lodge a complaint with a supervisory authority. To exercise rights against Open Banking Compare, use the contact channel above if we have published one; otherwise use the same channel you used to reach us (for example your original inquiry).

International transfers

Where a vendor processes data outside your country, transfers may rely on standard contractual clauses or other mechanisms offered by that vendor. Review vendor documentation for details.

Children

This site is aimed at businesses and professionals. It is not directed at children, and we do not knowingly collect data from children.

Changes

We may update this policy from time to time. Material changes will be reflected by updating this page and, where appropriate, the “last updated” indication we add when we publish substantive edits.