Wholesale Control, operated by TJ and G Property Solutions
Security contact: [email protected]
Version 1.0 — Effective November 21, 2026
⚠ ATTORNEY REVIEW REQUIRED before this document is treated as final. This policy describes measures *actually implemented* in this codebase — it does not claim certification to any security standard, and does not claim the Service is unbreachable. No software is.
account_id throughout the application and database; the Service has repeatedly been audited (see this repository's own HANDOFF-ACCOUNT-ISOLATION-*.md history) and corrected when cross-account leakage was found, including in background/unattended jobs.We do not claim Wholesale Control is certified to SOC 2, ISO 27001, PCI-DSS (we never handle raw card data — that is Stripe's responsibility, by design), or any other formal security standard, unless and until such certification is actually obtained and this document is updated to reflect it. We do not claim the Service is immune to compromise — no system is — only that the measures above are genuinely in place today.
If we detect or are notified of a potential security incident (unauthorized access, data exposure, account compromise, suspected cross-account leakage, lost/compromised credentials, or a vendor incident affecting our subprocessors), we follow this process:
1. Investigation and containment: identify the scope (which accounts/data, how it happened), contain it (e.g., revoke affected sessions/tokens, patch the vulnerability, rotate affected credentials), and stop ongoing exposure as quickly as possible.
2. Evidence preservation: preserve relevant logs and records needed to understand the incident and support any required notifications, rather than overwriting or deleting them prematurely.
3. Customer notification: notify affected account Owners without undue delay once we have confirmed the incident and its scope, describing what happened, what data was involved, and what we are doing about it, through the account's registered email and, where appropriate, an in-app notice.
4. Legal/regulatory notification: where applicable law requires notifying a regulator or affected individuals within a specific timeframe (for example, under applicable state breach-notification statutes), we will meet that timeframe. [ATTORNEY REVIEW: confirm the specific breach-notification statute(s) and timing applicable given where your customers and their leads are located — commonly Texas Business & Commerce Code Chapter 521's breach-notification provisions, and potentially other states'.]
5. Recovery: restore affected systems/accounts to a secure state.
6. Post-incident review: review what happened and what changed afterward to reduce the chance of recurrence; the resulting fix is documented internally (this repository's own handoff-note convention already does this for every security fix made to date).
If you discover a security vulnerability or suspect a compromise, email [email protected] with details. We will acknowledge receipt and investigate promptly.
You are responsible for keeping your own login credentials confidential, using a strong password, and promptly reporting suspected unauthorized access to your account.