Who and what this notice covers
HomeHub Club (HHC) is the brand used on this marketing website. The legal entity or proprietor responsible for personal information, its business address and its privacy and Information Officer contacts have not yet been confirmed for this notice. Those details must be published before live collection opens.
This notice concerns browsing the marketing website, future beta-interest preferences and contact enquiries. Future application accounts, marketplace transactions, contractor subscriptions and independent tools would need separate notices and agreements. HHC’s wider mission is to connect residents with local service providers across everyday community needs.
What happens on this website today
The beta and contact forms are local previews. Use example details only. Entries stay temporarily in the form’s memory while it remains loaded; closing and reopening a dialog can retain its draft. Clear example or a full page reload clears it. Leaving a standalone form page also clears that form’s draft. The previews do not transmit entries, register interest, save enquiries or send email.
The website currently displays light mode only and does not read or write a theme preference. A saved preference from an earlier preview may remain in your browser until you clear site data. The website includes no analytics or advertising tracking integration. Requests needed to deliver pages and assets expose technical connection information to the serving system; hosting logs, recipients and retention must be assessed before publication. Vercel is the intended website host, pending account, deployment and hosting-policy review.
Planned beta-interest information
If collection is approved, beta interest would require an email address, at least one audience choice (homeowner or resident, service provider, or property manager) and at least one email preference. Multiple audiences are allowed. A name, broad town or region, and service category for service-provider interest would be optional. Leaving optional details blank would not prevent a request.
The proposed purposes are managing the launch and beta updates you select, contacting you about chosen early-testing opportunities, and understanding interested audiences and broad areas. An audience choice would not create an account or verify occupation, property ownership or eligibility. Do not provide identity documents, exact home addresses, payment details or sensitive personal information.
Independent choices and email confirmation
The proposed update and early-testing choices are separate and unchecked by default. You could select either or both. Testing interest would not require subscribing to launch updates. Neither choice would guarantee a beta place or launch date.
A future verification email would ask you to confirm your requested choices. Only those choices would become active after an explicit confirmation. Opening an email link alone would not grant permission. Confirmation demonstrates access to that mailbox at that time, rather than proof of legal identity. No verification email is sent by the current preview.
Planned contact-enquiry handling
The proposed contact service would require your name, email, subject and message to receive, assess and respond to your enquiry. Avoid including another person’s information or sensitive details that are unnecessary for the question.
An enquiry would not subscribe you to updates or testing invitations. A receipt or reply would relate to that enquiry only. Contact processing and its legal basis need approval separately from optional marketing; acknowledging a privacy notice is not marketing consent. No monitored HHC contact channel is published in this draft, and the preview cannot receive a message.
Planned permission and delivery records
For a future live service, we propose to record each requested purpose, its exact approved wording and privacy-notice version, when and where the choice was made, and subsequent confirmation or withdrawal. Presentation of a notice would not prove it was read or that optional marketing was accepted.
Limited confirmation-token, delivery, failure and abuse-prevention records would support security and reliable handling. Routine logs should exclude form contents, raw email addresses and secret action links. Pseudonymous abuse or suppression identifiers would still be treated as personal information. These records and controls do not yet exist in the marketing preview.
Proposed retention and deletion
No lead-retention period is active because the previews do not save leads. Candidate rules for a future service are: remove unconfirmed requests within seven days; make confirmation links usable for 24 hours; review active preferences after 12 months and at beta-programme end; and delete closed enquiries after six months unless a justified hold applies. All periods await approval.
After withdrawal, proposed cleanup would remove unnecessary profile details while retaining only justified permission history and a minimal do-not-send record. The duration of that evidence, delivery diagnostics, backups and provider copies still needs approval. Deletion would cover providers and authorised exports as well as the primary database. Backup expiry and reapplication of deletions after restoration must be explained before activation.
Withdrawal and unsubscribe
The proposed live service would provide a free unsubscribe link in every update or testing invitation, without requiring an account. You could stop one purpose or all optional emails. Withdrawal would stop future eligible sends and cancel queued matching emails; an email already accepted for delivery might still arrive.
A minimal suppression record may be needed to honour a request not to be contacted. Unsubscribing would not prevent a reply to an independent enquiry you initiate. An unsubscribe workflow and monitored manual privacy channel must be operational before collection or sending opens; neither is available from these previews.
Access, correction, deletion and complaints
Subject to applicable law, you may request information about processing, access to your personal information, correction or deletion, object to processing, or withdraw consent. Limited information may need to be retained for an applicable legal obligation or justified dispute; any limit should be explained.
Before activation, HHC must publish a monitored privacy contact and request process, including proportionate identity checks, applicable response periods and escalation. The contact preview cannot receive a rights request. You may also raise a complaint with South Africa’s Information Regulator through its official channels.
Information Regulator: official website and complaint routes
Planned access controls and safeguards
Before live processing, proposed safeguards include encrypted transport, restricted staff access with individual accounts and multi-factor authentication, separate marketing storage, protected secrets, bounded retries, redacted logs and tested deletion and incident procedures. Marketing records would remain separate from core application accounts.
These are requirements to implement and verify, not a claim that a live backend has passed security acceptance. No website or email service can promise absolute security. An incident affecting personal information would need assessment and notification as required by applicable law.
Processors and international processing
Hosting, database and email providers for the future marketing service remain unselected. Vercel, a separate Supabase marketing project, Resend and Amazon SES are candidates under review; this is not a statement that they currently receive website leads.
Before activation, this notice must identify selected providers and relevant recipients, purposes, processing countries, retention and safeguards. A server or sending region would not by itself establish where support, logs, backups or all subprocessors operate. International transfers need an assessed lawful basis and appropriate agreements. No South Africa-only storage promise is made.
Policy changes and privacy contact
Each approved policy should have a version and effective date, with earlier approved versions retained as necessary for evidence. A material new purpose may require fresh permission; changing a notice would not silently expand an existing choice.
This document has a draft review date only, with no effective date. HHC’s legal identity, privacy contact and Information Officer details are awaiting confirmation. This draft must be completed and approved before public activation or live data collection.