Legal

PDPA & Data Handling

How the native intake, Apps Script bridge, operational metadata and secure report delivery handle customer data.

What the native intake collects

The PropScrut intake collects the exact property, purchaser, transaction, financial-resilience, reflection, optional-document and consent information shown in the form. The Free intake does not add an email question.

How the commercial layer handles it

The browser submits to a protected WordPress endpoint. WordPress validates the approved contract and relays it over HTTPS to the authenticated Apps Script bridge. WordPress does not retain the answers or uploaded documents; it keeps only operational identifiers and status values needed for UAT and support.

Google processing boundary

The approved bridge places the submission into the existing controlled Google Sheets and Apps Script workflow. Supporting documents are held in the configured restricted Google Drive location. Access, sharing, retention and deletion must follow the approved operating policy.

Payment and report data

ToyyibPay processes payment information. PropScrut verifies payment server-side and does not treat the return page as proof. Completed reports are accessed through opaque, expiring tokens and are not exposed at predictable public PDF addresses.

Rights and contact

Subject to applicable law, a data subject may request access or correction and may raise questions about processing through the approved privacy contact. Identity verification may be required before protected information is disclosed or changed.

Required launch details

The operating entity, address, privacy contact, retention periods, Google account ownership, cross-border position and processor terms require Founder and legal approval before public launch.