Data Deletion
How to request removal of personal information associated with Build.
Review draft · 17 October 2026 · Effective date pending sign-off
1. Send a deletion request
Email privacy@build2day.org with the subject Build data deletion request. Identify the relevant Build account, organisation or workspace and describe the information concerned. Do not include passwords, login tokens or sensitive identity documents in the first email.
2. Acknowledgement and verification
BUILD 2DAY (PTY) LTD aims to acknowledge the request within two business days. The team may ask for reasonable information to verify identity and authority, including whether the requester acts for a customer organisation. Acknowledgement is not a guarantee that deletion has already occurred.
3. Review and completion
The request will be assessed for applicable rights, customer instructions, technical scope and lawful retention obligations. Eligible information will be removed through a managed operational process, or the requester will be told why some data cannot yet be removed. Valid requests will be handled as promptly as reasonably practicable and within applicable legal requirements. No universal completion period is promised.
4. Connected platforms and backups
Disconnecting a connected account does not necessarily delete audience data, posts or campaign information independently held by Meta or other services. For a cancelled account, Build will review workspace and uploaded audience data for removal, except records subject to lawful retention. For connected services, Build will assess whether it can remove data itself or must request action from the provider or customer. Data may remain temporarily in backups until the provider’s documented backup lifecycle expires. The actual deletion procedure, provider obligations and backup lifecycles still require verification. Any confirmed exceptions or retention requirements should be explained to the requester.
5. Contact and related policy
For a status update email privacy@build2day.org. Read the Privacy Policy. This document describes the intended managed request process and must be supported by an internal operating procedure before it is treated as a final public commitment.