bariviews

Privacy

Understand what you share and who can see it.

This notice describes the information used to operate BariViews and the practical controls available to you.

Last updated: 28 October 2026

1. Information you provide

Account information can include your name, email, phone number, role and password hash. Depending on the features you use, we also receive profile details, saved searches, private notes, inspection records, enquiries, listings, reviews, replies and support messages.

Verification or ownership processes may request supporting documents. Use the designated private upload flow, not a public listing or contact message. Payment records can include transaction references, amounts and status; payment providers collect the payment credentials required by their checkout.

2. Public and private information

Published listings, listing contact details you choose to provide, approved contributions and owner replies are intended to be visible to other visitors. Public content may also appear in search engines. Do not include information there that you expect to remain confidential.

Private notes, account settings and documents submitted through private verification flows are access-controlled. Authorised staff may access relevant information for support, moderation, verification or security. When you send an enquiry or share contact details with an owner, that recipient receives the information needed for that interaction.

3. How information is used

We use information to provide accounts and features, deliver requested messages, manage listings and plans, review content, investigate misuse and keep the service running. Saved-search and notification preferences affect the messages you request.

Technical records may include request information, IP addresses, session or device information, security events and service errors. These help operate, diagnose and protect the platform.

4. Service providers and external features

Hosting, email, SMS, payment, mapping and anti-abuse providers may process the information needed to supply the configured feature. When Gmail SMTP is configured, outgoing messages pass through Google’s mail systems; the destination inbox provider also handles messages.

Optional AI-assisted features may send relevant input to the configured AI provider. Avoid submitting identity numbers, payment credentials or unrelated personal information in free text. Third-party processing and international routing depend on the services enabled; their own notices also apply.

5. Cookies and browser storage

The browser uses an authentication refresh cookie and session storage for signed-in access. Local storage can remember preferences such as theme, language or comparison selections. These mechanisms support site functionality.

Disabling or clearing browser storage can sign you out or reset preferences. External anti-abuse widgets and embedded services may use their own browser storage when enabled. A link to another site is governed by that site’s privacy practices.

6. What sharing looks like in different features

Saving a property or a private note is different from publishing a review. Before you submit, check whether you are using a public contribution field, a personal collection, an owner enquiry or a private document flow. A private file should never be linked in a public description.

Owner profiles and listings may include a phone number, WhatsApp contact or other contact channel supplied by the person managing the property. A visitor using those channels leaves the platform or shares information directly with the recipient. Check the recipient and channel before sending sensitive material.

7. Verification documents and uploaded media

Documents submitted through the private verification flow are kept separately from public listing media and require authorised access. Their purpose is to support the requested review process; uploading a document does not make it appropriate for public display.

Public photos are intentionally accessible to visitors. Before uploading, remove identity cards, letters, bills, screen notifications and identifiable bystanders unless sharing is appropriate and permitted. An image filename or a private caption does not make a public upload confidential.

8. How to make a clear privacy request

Tell us whether you want access, a correction, removal or help with an account control. Include the relevant account email or public page link and describe the information involved. Use an address you control so we can reply, but do not send a copy of your identity document unless an appropriate private verification step is arranged.

We may need to confirm that a request concerns your information and understand whether other people’s records are involved. We assess requests in light of the available controls, the reason a record is kept and applicable requirements. We do not promise deletion of every backup or an immediate removal from third-party search results.

9. Public copies and deleted accounts

When content has been public, another visitor or search engine may retain a copy outside our control. Removing it from BariViews does not automatically remove those external copies. If an external result persists, that service may have its own removal process.

Account deletion does not necessarily remove text within a historical review, a billing reference or a security record. If a contribution contains a personal detail you want removed, identify the content and detail in a separate request. Avoid reposting the sensitive information while reporting it.

10. Other people’s information

A listing, photo or review can include information about residents, visitors or members of your household. Share only what is necessary and appropriate for the feature, and obtain permission where needed. Do not publish children’s faces, routines, school details or other identifying information in a rental review.

If someone has posted your information without permission, use the contact form to identify the page and the type of information. You do not need to create a public rebuttal or upload more personal evidence to explain the concern.

11. Retention and security

Records are kept for the period needed to provide the relevant feature and address operational, security, accounting or dispute needs. There is no single retention period for every type of record. Backups and logs may persist after a change to the live account.

Access controls, password hashing and private-document protections help reduce risk, but no system can promise absolute security. Do not reuse passwords or share one-time codes. Report suspected exposure through Contact without sending the sensitive material again.

12. Your choices and requests

Use available profile and notification controls to update your information and preferences. Tenant account tools offer an export of selected account information and an account-deletion action. The export is a summary, not necessarily every technical record.

Deletion disables and de-identifies the account and removes some personal collections. Historical contributions or records may remain, and deleting an account does not automatically redact personal details you put inside public text. Contact us to request access, correction or removal beyond the available controls, including documents or public content. We may need to verify the request.

13. Updates and contact

The date on this page identifies this version. We may revise the notice when features or providers change. Review it before sharing information through a new feature.

For a privacy request, select the privacy topic on the Contact page and describe the record or page involved. Do not send passwords, identity documents or full payment details in the initial message.

Privacy | BariViews