← HostHub

Data Processing Addendum

Effective: October 9, 2026

For customers who need a signed processor agreement — typically anyone handling guests from the EEA or the UK. It takes effect automatically with the Terms of Service; no signature is required, but we will sign a copy on request.

  1. 1. Roles

    This addendum forms part of the Terms of Service between PLATINUM TRAVEL INC. ("Processor") and the Customer ("Controller"). It applies whenever we process personal data on the Customer's behalf, and prevails over the Terms of Service on that subject if the two conflict.

    The Controller determines the purposes and means of processing. The Processor processes only on documented instructions, which are: the Terms of Service, this addendum, and the Controller's use of the features in the product.

    If we believe an instruction breaches applicable data protection law, we will tell the Controller and may pause that processing.

  2. 2. Annex I — details of the processing

    • Subject matter: provision of the HostHub property management service.
    • Duration: for as long as the Controller's account is open, plus the 7 days between a request to close it and its permanent deletion.
    • Nature and purpose: storing, organising, transmitting, displaying, synchronising with connected channels, generating documents from, and deleting the data, in order to run the Controller's rental operation.
    • Categories of data subject: guests and tenants, prospective guests, the Controller's staff and cleaners, and owners in profit-sharing arrangements.
    • Categories of personal data: names, email addresses, phone numbers, messaging identifiers, stay dates and party size, payment and deposit amounts, free-text notes, identity-verification status, photographs, signed contracts and handwritten signature images, and message content.
    • Special category data: none is required by the product. If a Controller enters it in a free-text field, they do so on their own instruction and remain responsible for its lawfulness.
    • Frequency: continuous, for as long as the service is in use.
  3. 3. Confidentiality

    Everyone we authorise to access personal data is bound by a duty of confidentiality, and access is limited to those who need it to run or support the service.

  4. 4. Annex II — security measures

    • Encryption of data in transit (TLS) and at rest by our infrastructure providers.
    • Passwords stored only as bcrypt hashes; sessions carried in signed, http-only cookies; password reset and email verification tokens stored hashed, single-use and time-limited.
    • Tenant isolation: every query is scoped to the owning account, enforced by a central tenant map and verified by an automated suite that runs one tenant's requests against another's data and asserts they are refused.
    • Role-based access within an account, so staff accounts see only the pages the Controller grants them.
    • Error reports scrubbed of request bodies, cookies, query strings and sensitive headers before leaving our servers.
    • An in-account activity log of actions taken, and a recycle bin so a deletion can be reversed rather than being immediately final.
    • Managed, point-in-time-recoverable database backups held by our database provider.
  5. 5. Annex III — subprocessors

    The Controller authorises the following subprocessors. Those marked optional are engaged only if the Controller enables that feature.

    • Vercel Inc. — Application hosting and file storage (Vercel Blob). All data in transit; uploaded photos, documents and signed contract PDFs at rest.
    • Neon Inc. — Managed PostgreSQL database. All account, property, booking, guest and message records.
    • Stripe, Inc. — Subscription billing, and guest payments where the customer connects their own Stripe account. Billing contact and payment details. Card numbers are entered on Stripe's own forms and never reach our servers..
    • OpenRouter, Inc. (optional) — Routes requests from the AI features (assistant, drafting, translation, note parsing, pricing suggestions) to the model host below. Only the text sent to a given feature — typically a booking note, a guest message or a pricing question. Routed only to hosts in the United States, with data collection by them refused.
    • DeepInfra, Inc. and Together Computer, Inc. (optional) — Run the AI model that answers those requests, in the United States. The same text as above, processed to produce an answer and not used to train models.
    • Channex (channex.io) (optional) — Channel management: availability, prices and restrictions sent to Airbnb, Booking.com and other channels; reservations and guest messages received from them. Reservation and guest data, and guest messages, for the listings the customer connects.
    • PriceLabs, Inc. (pricelabs.co) (optional) — Dynamic pricing for the listings a customer switches to PriceLabs: nightly prices and stay restrictions set from market data. Listing details, availability, and reservation dates and amounts, for those listings only.
    • Hostex (optional) — Channel management: calendars, reservations and guest messages. Reservation and guest data for the customer's own Hostex account, using the customer's own API key.
    • Our outbound email provider (SMTP) — Outbound email: account mail (verification, password reset, closure), and contracts, invoices, reminders and confirmations the customer sends. Recipient address and message content, including attached PDFs.
    • OpenStreetMap geocoders (Photon by komoot, Nominatim) (optional) — Placing a property on the map, for listing pages and market research. The property's address only — no guest or account data.
    • Functional Software, Inc. (Sentry) (optional) — Error monitoring. Error reports with request bodies, cookies and query strings stripped, and the user reduced to an account id.

    We impose data protection obligations on each subprocessor no less protective than those in this addendum, and remain liable for their performance. We will give at least 30 days' notice before adding or replacing one; the Controller may object on reasonable data protection grounds, and if we cannot resolve the objection they may terminate the affected service without penalty for the unused period.

  6. 6. Assistance with data subject requests

    The product lets the Controller find, correct, export and delete records themselves, which is how most requests are answered. Where that is not enough, we will provide reasonable assistance, taking into account the nature of the processing.

    If a data subject contacts us directly, we will not respond on the Controller's behalf beyond telling them to contact the Controller, and we will forward the request.

    We will also assist, so far as we reasonably can, with data protection impact assessments and prior consultations relating to the service.

  7. 7. Personal data breaches

    We will notify the Controller without undue delay after becoming aware of a personal data breach affecting their data, and in any event within 72 hours, with the information we hold at the time and updates as we learn more.

    Notifying supervisory authorities and data subjects is the Controller's responsibility, since they hold the relationship. We will support it.

  8. 8. Return and deletion

    The Controller may export their data at any time while the account is open. A request to close the account locks it at once and deletes the data permanently 7 days later, so export comes first. After deletion we hold nothing other than backups that expire on their own cycle and anything we must retain by law.

  9. 9. Audits

    On reasonable written request, and no more than once a year unless a regulator requires otherwise, we will provide the information needed to demonstrate compliance with this addendum. On-site audits are by prior agreement, at the Controller's cost, and must not disrupt the service or expose another customer's data.

  10. 10. International transfers

    Where personal data originating in the EEA, the UK or Switzerland is transferred to a country without an adequacy decision, the parties agree the applicable Standard Contractual Clauses apply, with the Controller as data exporter and the Processor as data importer, and Annexes I to III above completing them.

  11. 11. Liability

    The limitations of liability in the Terms of Service apply to this addendum, except where applicable data protection law does not allow them to.

  12. 12. Contact

    Data protection enquiries: platinumtravelca@gmail.com. PLATINUM TRAVEL INC., 2980 Number 3 Rd, Richmond, BC V6X 2B3.

The English text is the governing version; translations are provided for convenience.
PLATINUM TRAVEL INC. · 2980 Number 3 Rd, Richmond, BC V6X 2B3 · platinumtravelca@gmail.com