Data Contribution and Analytics Policy

1. Scope and principles

This policy applies when an agent, property developer, developer company, owner, organisation, technician, administrator or authorised integration contributes property, project, listing, location, capture or preference information to VeraSpace. It supplements the Terms and Conditions and Privacy Policy.

VeraSpace follows purpose limitation, data minimisation, source traceability, access control, accuracy review and separation between operational personal data and market-intelligence data.

2. Property and project contributions

• Contributions may include developer-company identity and registration information; project name, registration, licence or advertising-permit details; property type, address and locality, coordinates, floor, size, unit types, facilities, tenure, asking price, transaction type, availability, authorised photos, brochures, floor plans and capture metadata.
• Provide only facts and content you are lawfully authorised to submit and publish. Do not copy a third party’s protected brochure, database or media unless you have permission or another lawful basis.
• Supporting company and project verification material is used for review, security and audit purposes and is not made public unless the relevant item is expressly identified for publication and you are authorised to publish it.
• Do not place personal contact details, identity documents, financial documents or confidential owner information in property-description or mapping fields.

3. Contributor responsibility

The contributor confirms that the information is accurate to the best of their knowledge, that required owner, developer-company or organisational authority has been obtained, and that VeraSpace may request reasonable evidence. A contribution is a source submission, not automatically a verified fact, regulatory approval or valuation. VeraSpace company or project verification is a platform review and not government, LPPEH or REN approval.

4. Traceable master records

VeraSpace may standardise spelling and format, deduplicate matching submissions, geocode locations and link multiple sources to a property or project master record. We record source type, date, permitted-use basis, verification status and a limited factual snapshot so corrections can be traced.

A master record may show confidence or verification status and may remain private until it meets publication rules. VeraSpace may prefer a more authoritative or recent source where submissions conflict.

5. Permitted uses

• Operate listings, mapping, discovery, virtual tours, matching and service workflows.
• Verify, correct and enrich property or project records from permitted sources.
• Measure aggregated or de-identified supply, demand, enquiry, budget, price-range, location, property-type and engagement patterns.
• Develop market dashboards, matching features, fraud controls, product research and commercial insights that do not disclose raw personal data.
• Create derived taxonomies, confidence scores, trends and statistical models. Outputs are informational and are not a valuation, transaction promise or guarantee of market performance.

6. Personal-data boundary

• Raw names, phone numbers, email addresses and enquiry messages remain in the operational system and are not copied into the general market-intelligence dataset.
• Identity documents, private communications and full payment credentials are excluded from general property and demand analytics.
• A keyed pseudonymous identifier may be used to prevent duplicate counts. It remains access-controlled and is treated as personal data while re-linking is possible.
• Published or shared market insights use aggregation, anonymisation and minimum-group rules where appropriate.

7. Ownership and licensing boundary

Contributors keep ownership of their original content. The licence in the Terms permits VeraSpace to process authorised contributions for the uses above. VeraSpace owns its software, schemas, taxonomies, verification work and derived or aggregated analytics, but does not claim ownership of personal data, underlying third-party rights or a contributor’s original media.

8. Corrections, challenges and removal

You may report an inaccurate property record or dispute a source attribution through contact@veraspace.my or +60 19-944 9066. We may ask for evidence, preserve an audit record, restrict a disputed record while reviewing it, correct the master record or remove public display. Operational and legal records may be retained where reasonably required.

Withdrawal of consent affects future consent-based personal-data processing. It does not require deletion of lawfully anonymised statistics that can no longer identify a person.

9. Earlier records and policy changes

Records received before this policy’s effective date are not automatically assigned broader contributor rights. They remain limited to their documented permission, service purpose or other lawful basis until reviewed. Material changes will be dated and notified, and renewed acceptance will be requested where required.

10. Contact

Questions about a source record, permitted use, correction or data-right request may be sent to contact@veraspace.my or +60 19-944 9066.

11. Customer memory, matching and derived data

Customer memory can include declared requirements, sources, last-confirmed dates, private notes and provisional AI suggestions. Explicit statements and confirmed availability take priority over inferred interest. Matching uses requirement and listing attributes to suggest opportunities, with an explanation where available; it is not a decision about a person’s eligibility to buy or rent. Inferences and identifiers that can be linked to a person remain personal data.

Match-ready and contact-ready are separate. A requirement is private to its agent relationship unless an authorised user deliberately changes its permitted sharing scope. Team, agency or network opportunity summaries must exclude raw chats, private notes and buyer identity. Permission to contact a buyer does not itself allow disclosure to another agent. A data contribution does not give VeraSpace a blanket right to train a general-purpose AI model or reuse connected-chat information for unrelated customers.

12. Drafts, corrections and source rights

Imported text, screenshots and AI-generated material are drafts requiring review. Keep ownership, attribution, source and permission records, and do not upload protected content merely because it is publicly accessible. Property record updates must preserve the applicable source and permission history. Changing these policies does not upgrade old consent records or make a previous private submission public.

A rights or correction request should identify the original contribution and any derived customer requirement, summary or published item affected. We assess those linked records as part of the request; hiding the source alone is not confirmation that every derivative or external copy has been removed.