TempahHQ
How it worksProductPricingSign inStart free setup

Legal

OverviewPrivacy PolicyTerms of ServiceCancellation & refundsCookies & sessionsData rolesData Processing TermsSub-processors

Legal

Last updated 2026-07-21 · Version 1.1

Sub-processors

Last updated: 21 July 2026 · Version: 1.1

TempahHQ uses the following categories of third parties to operate the Service. Names and regions should be kept accurate as production infrastructure is fixed.

This list supports the Privacy Policy and Data Processing Terms.

Current and planned processors

Sub-processor / categoryPurposeData typically involvedNotes
Cloud application host (e.g. Vercel or equivalent)Host the web appRequest data, logsProduction host TBD at deploy time
Cloud API / compute hostRun the TempahHQ APIAccount, booking, and operational dataProduction host TBD
Managed PostgreSQL (or equivalent database provider)Primary datastoreAll application data including personal dataEncrypted at rest where offered by provider
BillplzOnline payments (per-tenant merchant for bookings; platform merchant for activation fee)Customer name/email/phone as sent to create bills; payment references; webhook payloads; shop owner details for activation fee billsSettlement for end-customer charges under your Billplz account. Also used by TempahHQ directly for platform activation fee collection (TempahHQ’s own merchant account). See Billplz policies
Auth0 (optional)SSO / IdP when AUTH_MODE uses Auth0Identity assertions, email, org mappingOnly if enabled for your environment
Email / SMS / WhatsApp providers (optional)Transactional confirmations and remindersRecipient address/phone, message contentConnected when those channels go live; not all channels may be active in early access
Error / uptime monitoring (optional)ReliabilityTechnical logs; minimise PIIAdded only if configured

Local development

Local Docker Postgres and mock payment mode process data only on developer machines and are not production sub-processors.

Billplz (important)

End-customer card data is handled by Billplz’s checkout, not stored as full PAN in TempahHQ. Shops configure their own API keys and collection IDs. TempahHQ does not act as merchant of record for end-customer booking payments.

Separately, TempahHQ may use Billplz under TempahHQ’s own merchant account to collect the one-time platform activation fee from shop owners. For that fee only, TempahHQ is the merchant of record.

Updates

We will update this page when we add or replace material sub-processors. Check the version date above.

Questions: hello@tempahhq.com

Related: Privacy · DPA · Terms

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

PrivacyTermsCancellationPoliciesContact

© 2026 TempahHQ