← Browse homes

Privacy policy

This page explains the information used to run Real Country House and the ways to contact us about your information.

Last updated:

Operator: BURUCE LEE

Contact email: realcountryhouse@gmail.com

Information you provide

We process account identifiers and information supplied through your sign-in method, your language and country preferences, listings, photos, contact details, comments, favourites, enquiries and reports when you use those features.

Visits and technical information

Our own analytics record visits, pages viewed, referring pages, campaign parameters, browser and device information, IP addresses and approximate IP-based location. This helps us understand traffic, improve navigation and identify automated or abusive requests. IP-based location is an estimate, not a GPS reading.

Cookies and browser storage

Cookies support sign-in and visit measurement. The analytics_visitor_id cookie has a 365-day lifetime; analytics_session_id and analytics_tracking_code have 30-minute lifetimes when set. Cookies may be renewed. Browser storage also remembers interface preferences. You can clear or block storage in your browser; some features may stop working. Cookie expiry does not itself delete server-side records.

Use and visibility

We use information to operate accounts, publish and find properties, handle enquiries, protect the service and understand usage. Published descriptions, photos and comments can be seen by other visitors. Listing contact details are handled through the contact-access flow; information you place in a public description can also become public. Avoid adding sensitive information to public content.

Sources of information

Account, listing and enquiry information comes from you or your chosen sign-in service. We may also import publicly available property descriptions, photos, locations and contact information from external sites. If your information or material you hold rights to appears in a listing, send its URL to request correction or removal.

Providers and information shared

Vercel processes web requests and application execution. Supabase provides authentication and the database for accounts, listings, enquiries and visit records. Cloudflare R2 stores uploaded or imported photos and generated media. Current AI description editing, translation and SEO generation use OpenAI and send the listing material needed for the task. Google or Facebook participates when you choose its sign-in method. Messages sent to our contact email are received through Google Gmail.

International processing and locations

The production Supabase database is in Tokyo, Japan. Web execution is also configured for Tokyo, but this does not confine all Vercel delivery, caching, logs or provider operations to Tokyo. Cloudflare R2, OpenAI and sign-in and email services may process information outside your country according to their service settings. A specific-country storage guarantee for R2 or region-locked AI processing has not been verified. Contact the operator for information about the relevant processing and safeguards.

Account, property and enquiry retention

Account, draft, listing, comment, favourite, enquiry and report records support service functions and case histories. The app does not currently have a rule automatically erasing all these records after a fixed number of days. Draft expiry, signing out and removing public visibility do not erase every stored record. Deletion requests are handled after identifying the relevant information and account; if material must remain for security, disputes or applicable obligations, we explain the scope and reason.

Listing deletion, files and backups

When an administrator permanently deletes a listing, its publication and related database information, including contact details, precise location, comments, favourites and translations, are removed or cleared. Physical image deletion and backup handling are separate stages; immediate removal of every copy is not guaranteed. Copies held externally or in search engines may also require action by those services.

Visit records and your choices

As checked on 7 September 2026, human visit, page-view and IP analytics records have no automatic expiry, and automatic bot-record cleanup is disabled. Cookie lifetimes of 365 days or 30 minutes are different from server retention. Visit analytics currently run when the site is used; a separate prior-consent control is not provided. You can email questions or requests for deletion or restriction of processing.

AI data retention

OpenAI requests disable response storage. This does not mean that all provider logs are immediately deleted or that no data is retained. OpenAI’s default API abuse-monitoring logs may be retained for up to 30 days, with differences arising from legal obligations or account agreements. See the provider’s current data-processing information below.

Privacy rights and requests

Email the operator, BURUCE LEE, to request access, correction, deletion or restriction of processing. Depending on applicable law, you may also have rights to object, obtain portable data, withdraw consent and complain to your data-protection authority. Identity checks are limited to what is needed. If a request cannot be fulfilled, we explain the reason and available next steps. Email remains available when you cannot use member enquiries.

Advertising and changes

The app currently has no Google ad-display script or advertising consent-management integration. A publisher-verification meta tag is not ad display. If advertising is introduced or providers or retention practices change, we will first update the relevant notices and necessary consent mechanisms, and revise this page.

Provider privacy and data-processing information