Legal

Privacy Policy

Draft placeholder. Not yet legally reviewed.

Draft: requires final legal review

This page is a placeholder. It has not been reviewed by a lawyer and must not be relied on as a finished policy. Final wording will be added before launch.

This is a working draft describing what the product actually collects and does today. It has not been reviewed by a lawyer, is not a finished policy, and is not legal advice.

Who is responsible for your data (the "data controller"). Property Potential is operated by Krish Kunalkumar Patel, trading as "Property Potential", as a UK sole trader — not a registered company. Krish Kunalkumar Patel is the data controller for the personal data described below. There is no company number or registered office to give (a sole trader has neither), and no VAT number is claimed here, as none has been registered. Postal/service address for data-protection correspondence: 1 Edenhall Close, Leicester, LE4 7ZU, United Kingdom. Reach us at Contact (support@propertypotential.uk).

1. What we collect

  • Account details: the email address and display name you give us when you create an account.
  • Property, scenario and report data: the properties, renovation budgets, scenarios and reports you choose to save. The demo property is a fixed example and is never saved to any account.
  • Files you upload: photos and documents you choose to attach to a property (for example an EPC or floorplan). These are private to your account and are not read or analysed by us.
  • Payment identifiers: when you buy a detailed report, Stripe (our payment processor) shares back a checkout/payment reference, the amount charged and the payment status (paid, refunded, disputed). We never receive or store your card details — Stripe collects those directly.
  • Technical and session information: your authentication session (so you stay signed in), and standard web request logs kept by our hosting provider, Netlify, as part of running the site. We do not currently run any analytics or advertising tracking.
  • Public property information: to build a report, we look up public data (for example planning records, postcode data and recorded sale prices) for the address and postcode you enter. This is information about the property and area, not about you, and the sources are listed in every report.

2. Why we use it, and on what basis

  • To provide the service (performing our contract with you): running your account, saving your properties and reports, processing a report purchase, and delivering the report you bought.
  • Security and abuse prevention (our legitimate interest, balanced against your rights): rate limiting, fraud and misuse prevention, and keeping the service reliable.
  • Legal and accounting obligations: keeping records of payments as required by tax and accounting law.

We do not currently send marketing communications, and we do not sell your personal data.

3. Who we share it with

We use a small number of service providers to run Property Potential. Each processes only what it needs to do its job:

  • Supabase — our database, authentication and file-storage provider. Your account, saved data and uploaded files are stored with Supabase.
  • Stripe — our payment processor for the one-time detailed report purchase. Stripe collects and holds your payment details directly; we only receive back the payment reference, amount charged and status described above.
  • Netlify — hosts the website and handles web traffic to it, which involves standard infrastructure-level request logs.
  • Public data sources named in each report (for example Postcodes.io, Planning Data (planning.data.gov.uk), HM Land Registry, and the Energy Performance of Buildings Register) — we send these services a postcode or address to look up; we do not send them your name, email or account details.

We don't share your personal data with anyone else, except where the law requires it.

4. Where data is processed

Supabase, Stripe and Netlify are international providers and may process data outside the UK as part of running their services. Where they do, they rely on their own data-transfer safeguards (such as the UK/EU Standard Contractual Clauses) — see each provider's own privacy policy for details. We haven't independently verified the specific hosting region for every provider at this draft stage; that should be confirmed as part of legal review.

5. How long we keep it

We keep your account and saved data for as long as your account is open. Purchase and payment records are kept as your record of that purchase and for as long as accounting and tax rules require, even if you later close your account. If you ask us to delete your account, we delete or anonymise what we can beyond what we're required to keep.

6. Security

Your saved data is protected by row-level security in our database, so it's only readable through your own authenticated account. We never see or store your password — Supabase's authentication service handles that. Card payment data is handled entirely by Stripe, which is built for PCI-DSS compliant card processing; we never see a full card number.

7. Your rights

Under UK data protection law you can ask to see the personal data we hold about you, ask us to correct it, ask us to delete your account and data, or object to certain uses of it. There isn't a self-service export or delete-account button in the product yet (account data export is marked "coming soon" in your account settings) — until there is, email Contact from the address on your account and we'll action it directly.

8. Cookies and similar technology

We use only the cookies/local storage strictly needed to keep you signed in and the app working. We don't currently use advertising or analytics cookies.

9. Complaints

If you're unhappy with how we've handled your data, contact us first. You also have the right to complain to the UK's data protection regulator, the Information Commissioner's Office (ICO), at ico.org.uk or 0303 123 1113.

10. Changes to this policy

We may update this policy as the service changes. Material changes will be reflected here with an updated review status.

11. Contact

Questions about this policy or your data: Contact.

Privacy · Terms · Disclaimer · Contact