Data roles (TempahHQ, shops, customers)

Last updated: 21 July 2026 · Version: 1.1

Multi-tenant booking is easier to understand if we separate three parties.

The three parties

┌─────────────┐     software      ┌─────────────┐
│  TempahHQ   │ ───────────────►  │    Shop     │
│  (platform) │                   │  (business) │
└─────────────┘                   └──────┬──────┘
                                         │ appointment
                                         ▼
                                  ┌─────────────┐
                                  │  Customer   │
                                  │  (booker)   │
                                  └─────────────┘

Party	Who	Example
TempahHQ	The software platform	Hosts `/book/demo-shop`, stores data, runs pay-to-confirm flow
Shop (tenant)	The business using TempahHQ	“Studio Ali”, “Demo Shop”
Customer	Person booking an appointment	Name + phone on the book form

Who decides what?

If you are a customer booking a shop

You are booking with that shop, not hiring TempahHQ as the stylist/photographer/consultant.
The shop needs your details to deliver the appointment.
TempahHQ stores those details so the shop can run calendar, payments, and reminders.
Questions about the appointment, refunds, or “please delete my number from this salon” → start with the shop.
Questions about the TempahHQ website or security of the platform → hello@tempahhq.com.

If you are a shop owner or staff

You decide which services you offer and how you use customer data for your business.
TempahHQ processes customer and booking data to provide the product to you (and to keep the multi-tenant system secure).
End-customer money settles via your Billplz account.
The one-time RM50 activation fee (if you self-serve) is paid to TempahHQ via TempahHQ’s Billplz account.
Contract-style processing terms for customer data: Data Processing Terms.
Vendors we use: Sub-processors.

TempahHQ as platform operator

For your login account, business settings, platform activation fee, and platform operations, TempahHQ determines how that account data is used to run the SaaS (security, support, and platform charges described in the Terms).

Customer records are per shop

Customer profiles on TempahHQ are stored per tenant (e.g. unique phone within one shop). The same person booking two different shops may appear as two separate customer records.

Deletion or correction is therefore usually scoped to the shop that collected the data.

Payments

Topic	Responsibility
End-customer merchant account / settlement	Shop’s Billplz
Platform activation fee (RM50)	TempahHQ’s Billplz — TempahHQ is merchant of record for this transaction only
Checkout page / card data	Billplz (and their policies)
Booking confirmed only after pay	Product rule enforced by TempahHQ + gateway webhooks
Service quality / attendance	Shop and customer

Quick links

Product drafts for early access — not a substitute for legal advice.