Data Processing (MVP)

User, listing, document, and audit data are processed to operate the LANDSAGE pilot: authentication, listing verification, buyer-agent matching, document review, admin operations, and audit traceability.

• Account & contact: email, name, phone, LINE ID, company.
• Buyer briefs: budget, preferred use, size, location, timeline.
• Listings: location, deed information, utilities, zoning, photos.
• Documents: deeds, plot plans, supporting files uploaded by agents.
• Operational: audit logs, admin notes, verification status.

Access is enforced by role:

• Public — only approved listings with public fields; deed numbers and private documents are hidden.
• Buyers — their own briefs and matched listings; contact card is private.
• Agents — their own listings, matched briefs surfaced via the admin workflow.
• Admins — review queues, verification controls, audit log, with all actions recorded.

Data is stored in a managed Postgres database with row-level security policies. Document and image uploads are stored in private buckets and accessed via short-lived signed URLs. Service credentials are restricted to server-side functions and never exposed to the browser.

We do not sell user data. Information is shared only as needed for platform operation (e.g. an admin verifying a listing, or a buyer brief being routed to a relevant agent during the pilot).

This page describes current MVP processing practices and is provided for transparency during the pilot. A formal data processing addendum (DPA) will be issued and legally reviewed before commercial launch.