Privacy

Data-minimal by design for the first owner intake path.

This page is a staging legal placeholder. It explains the intended privacy posture for property-score requests before production legal review.

Data minimizationOwner lead intakeNo credentials requestedLegal review required

Production placeholders

Legal details still need confirmation before public production cutover.

The staging page should be transparent that final legal entity, contact and retention details must be reviewed before signaldeskhq.com is approved.

Legal entity name

Privacy contact email

Company registration number, if applicable

Business address, if applicable

Data collected

What the property score may collect.

The form is designed to request only enough information to understand the property and recommend a safe next step.

Owner name, email, phone and consent-to-contact status.
Property location, number of rooms or units, and current operating pain points.
Current public platform context such as Airbnb, Booking.com, LekkeSlaap, direct website or other public channels.
Public listing links and voluntary owner notes for review and follow-up.

Data not requested

Information the first score request should not collect.

These exclusions are part of the product boundary and should remain true when the Worker/D1 backend is connected.

Owner account passwords or OTA admin credentials.
Payment card information, bank details or financial account access.
Door codes, lockbox codes, alarm codes or private property-access secrets.
Sensitive guest personal data or private booking records.
Private platform admin links that are not publicly accessible.

Use of data

Why the information is used.

The purpose is limited to property review, owner follow-up, and controlled pilot preparation.

Review the property and prepare a score or pilot recommendation.
Contact the owner about SignalDeskHQ services and next steps.
Prepare an owner intake path if the owner requests a pilot.
Improve the service model without publishing personal or sensitive data.

Before production

Privacy work still required before signaldeskhq.com goes live.

These tasks should be completed before the production domain is attached or live lead collection begins.

Replace legal placeholders.
Confirm retention and deletion process.
Protect any admin export or CRM access.
Document processors and third-party tools.
Review privacy wording before production domain activation.

Next step

The safest lead form is the one that asks for less.

SignalDeskHQ should collect only the information required to assess the property and recommend the next owner-approved step.