Responsible person: Shane Golden, Principal, BigDomain.ca, Kitsilano, Vancouver, BC. Use the website Contact button or your private portal to request access, correction or deletion, withdraw consent, or raise a privacy concern. Public mailing address: 1933 W Broadway, Vancouver, BC V6J 1Z3.
Information and purposes
BigDomain processes business/contact details, relevant public research sources, website content/photos, ordering and billing references, domain registration/routing information, support messages and appointment names, contact emails and times. This information supports the agreed site, email and booking service, account security, reviewed support, verified billing and departure handover. Public listings are reviewed for outreach eligibility; a public listing alone does not authorize every message.
Square collects card details within its secure fields. BigDomain records payment/subscription references, consent and verification outcomes. It does not retain full card details or the submitted single-use card token. Ordinary intake does not request your inbox password. Any account connection or credential required for a selected service is handled separately with its purpose and access explained.
AI processes relevant supplied text and business details to prepare drafts and proposed updates. Shane reviews consequential requests. Processing may occur outside Canada. BigDomain does not promise Canadian-only storage, provider retention limits or exclusion from provider model training unless the actual account settings and provider terms support that claim.
Providers and access
Cloudflare hosts the public website, protected owner dashboard and scoped customer portal. Customer records are separated by the application. Shane's Windows PC runs Codex to prepare reviewed work. Google Workspace supports connected business mail and the verified email arrangements. Square supports ordering, recurring billing and notifications after their separate commercial activation. Registrars receive availability queries and, for authorized registrations, the necessary registrant information.
Shane can administer service records. Owner access, provider credentials and backups are excluded from public site exports. Exports containing booking or support information remain private. Google permissions may be wider than the software's selected message filters. Customer email access and provider changes require the agreed customer setup; they are not inferred from an ordinary support message.
Sessions and measurement
Sign-in cookies support access and authorization. The pilot has no email open-tracking pixel. Preview measurement counts qualified authenticated browser sessions using a one-way digest, excludes known bots and owner visits, and does not store an IP address or user-agent string in that measurement record. It measures sessions rather than unique people or email opens. Campaign, preview, order, checkout and service references support comparison of results. Internal rehearsals are separated from production activity and revenue.
Opt-outs stop pending follow-ups. BigDomain retains the minimum suppression evidence necessary to respect them. Ordinary marketing records are not retained indefinitely solely because an opt-out must be respected.
Approved retention plan
The following retention periods were approved on October 2, 2026. Implementation is in progress. This is not an active automatic deletion schedule or a claim that disposal across all providers has been completed. The 30-day departure export access period is approved; subsequent deletion controls still require completion and verification.
| Information | Approved period and trigger | Exceptions and intended disposal |
|---|---|---|
| Active site content, media, domain/email configuration and service records | While required for the active service; export access for 30 days after shutdown | Remove unnecessary service copies within seven days after the export window, once verified handover and any hold are resolved |
| Appointment records | Up to 12 months after the appointment while the service is active; include relevant records in the departure export | A customer's shorter schedule can be agreed. After shutdown, use the export/deletion window unless a documented obligation requires specific records |
| Routine support and received message bodies | 90 days after resolution or the last meaningful response | Retain only necessary extracts for an unresolved request, decision record, consent, dispute or accounting obligation |
| Unconverted prospect research and unreleased demos | 180 days since the last meaningful activity | Remove contact detail, captured content and unused demos unless a documented current purpose remains; keep minimal suppression evidence separately |
| Security and operational diagnostic logs | 30 days | Necessary incident evidence can be held separately until resolved; do not erase delivery/idempotency evidence needed to prevent duplicate actions |
| Required tax/accounting evidence and supporting transaction records | Normally six years after the end of the last tax year to which the record relates | Apply later-filing, dispute or other required extensions; retain only supporting records needed for that purpose |
| Information used for a decision directly affecting an individual | At least one year after its use for that decision, where B.C. PIPA section 35(1) applies | A longer specific obligation or unresolved hold can apply; do not retain unrelated data under this exception |
| Opt-out suppression and minimal delivery/idempotency evidence | While needed to avoid unwanted contact or duplicate operations | Restrict fields and access; review continued need annually. A digest is still treated as protected data, not declared anonymous |
| Encrypted Cloudflare recovery copies | Existing seven-day expiry | Expiry is not deletion of current service records, PC copies, Gmail messages or provider records. A restore must reapply recorded deletion decisions before processing resumes |
| Temporary exports, local working copies and downloaded service files | No longer than the corresponding purpose above | Inventory and verify disposal on the PC separately. A customer controls copies they have downloaded |
These operational periods are BigDomain's choices, not statutory durations for every category. B.C. PIPA requires at least one year's retention when personal information was used for a decision directly affecting an individual, and disposal when its purposes and legal/business need end. Required CRA records are generally retained for six years from the end of the last tax year they relate to, with exceptions. B.C. PIPA section 35 and CRA record retention were checked October 1, 2026.
Deletion requests are reviewed against identity, current service needs and specific record obligations. BigDomain explains what can be removed, what must be retained and why. A hold identifies its reason, scope and review date. Independent provider records follow that provider's controls and obligations; BigDomain does not claim they were deleted without confirmation.