Privacy Policy

Depending on how HSS is used, the platform may process owner and Team account information; property information; guest contact information; reservation and agreement records; communications; property documents; guest issue reports and submitted issue photos; and operational or security history.

Reservation, agreement, communication and related operational records may remain associated with the historical stay after checkout, cancellation, account changes or property archive. HSS uses durable history so owners and HSS can understand what occurred during the reservation lifecycle.

Archiving a property is not the same as physically erasing its historical records. Property archive removes the property from normal active/public operation while preserving required history.

HSS uses first-party visitor and discovery session identifiers to understand how people arrive at HSS, move through Network discovery and reach property or booking experiences. These identifiers support traffic and booking-source attribution, including evidence that HSS generated business for a property owner.

HSS treats these anonymous visitor/session values as attribution identifiers rather than as guest identity by themselves. Current V1 analytics history is retained with durable property history, including when a property is archived. HSS does not silently run an automatic destructive analytics purge.

HSS may preserve communication threads, messages, delivery information and lifecycle communication evidence connected to a guest, reservation, property or account. Guest-facing experiences receive only information specifically permitted for guest visibility; internal owner records remain outside the guest response.

Property documents are managed through explicit lifecycle and retention controls. A document may have a retain-until date or may be held indefinitely when appropriate. Document archive does not silently erase historical versions.

Guest issue photos are stored as private operational files. Failed uploads or files that never become part of a successfully stored record may be removed as transaction cleanup.

HSS records security and privileged administrative events so sensitive actions can be reviewed. Security audit history is designed to be append-only rather than silently rewritten.

Some security data is intentionally short-lived. For example, rate-limit windows use keyed identifiers to detect abuse and are cleaned up after their operational purpose has passed.

HSS may preserve milestones showing that guest access was provisioned, communicated or revoked for a stay. The HSS guest-access lifecycle ledger is designed not to store plaintext door PIN or access-code material.

HSS does not apply one blanket deletion period to every record. Retention depends on the type and purpose of the information. Reservation history, agreements, audit evidence, communications, documents and analytics may require different lifecycle treatment.

Destructive privacy actions are deliberate HSS-controlled operations. They are not implemented as silent cascades from an owner clicking “Delete Property.”

Owners and guests may use the support or communication channels provided by Heaven Sent Stays to ask about information associated with their use of the platform, request correction of inaccurate information, or ask HSS to review a privacy request.

A request does not automatically require destruction of records that HSS or a property owner must reasonably preserve for reservation history, agreements, security, accounting, dispute resolution or other legitimate operational obligations.