Privacy & Deletion
Account deletion, data-retention summaries, and data-rights framing for questionnaires—including scopes, grace periods, and org-owned deals.
This page summarizes account-level deletion and retention at a glance. For tenant isolation, row security, publishable links, and AI handling, see Data isolation and AI Trust and Safety.
EQUIRE distinguishes between your user account (identity, memberships, credentials) and organization-owned records (deals, documents, valuations, workflows). Closing your account affects the first; deal-level data stays with the organization unless admins take separate org-level actions.
Organization-Owned Deal Data
Deals and their contents belong to your organization, not to an individual login. Removing a person's access does not delete historical deal artifacts the org still needs for compliance or continuity — other members with appropriate roles keep working normally.
That means:
- Leaving or losing access to EQUIRE typically removes your ability to view and act, not necessarily every row of business history the org retains.
- Org admins manage membership; they can remove a member without deleting deals or documents.
If you believe data should be purged beyond these defaults, escalate through your organization's administrator or formal data-rights request channels per your agreements with Agentic Assets.
Removing a Member
An organization administrator can revoke a user's membership at any time. That user's session loses access to the org immediately. This action does not delete the organization's deals, documents, or audit history.
EQUIRE-Only Account Deletion
EQUIRE-only deletion is designed for situations where someone should stop using EQUIRE altogether while the organization keeps operating.
What it does (plain language):
- Removes your memberships and profile from EQUIRE for your account.
- Does not delete organizational deal rooms, uploads, valuations, IC memos, deliverables, or similar org-scoped artifacts.
- Does not necessarily remove identifiers from every historical diagnostic row everywhere in the tenant database where engineering audit patterns apply — product surfaces are rebuilt so you cannot return under the same linkage.
This path completes promptly once confirmed — there is no grace period for EQUIRE-only deletion.
Depending on tenancy rules at the moment you request deletion, you cannot use this option if doing so would leave an organization without a valid administrator pathway; the product prompts you to transfer responsibilities or resolve the organization before continuing.
Full Account Deletion
Full deletion aligns with broader identity erasure: your ability to authenticate is removed from the coordinated stack, alongside controlled cleanup tied to our cross-platform deletion program (shared identity plane with sibling products).
What to expect:
- Scheduling and grace period. When you confirm a full deletion request, the product queues the work behind a multi-day grace window during which you remain able to cancel. The grace applies here, not twice across platforms initiating the handshake.
- After the window. The pipeline removes access and scrubs linkage according to shipped deletion logic — still subject to organizational ownership rules below.
- Org-owned assets persist. As with EQUIRE-only removal, deal rooms and attachments remain with the organization where your contract and product design treat those as organizational records unless your master agreement spells out an exception.
If you initiate from EQUIRE while another linked profile has conflicting admin constraints, routing may halt with remediation instructions — analogous checks exist on reciprocal platforms.
What This Page Does Not Cover
Operational details intended for engineers — cryptographic service authentication between platforms, webhook contracts, exhaustive table maps, and remediation runbooks — live in internal documentation and are typically shared under NDA for diligence.
Related
- Data isolation — tenancy, share links, audits
- Subprocessors & AI — AI routing and contractual posture
- AI Trust & Safety — human checkpoints for AI-mediated outcomes
Last updated on
Data Isolation
How organization-level data isolation is enforced for EQUIRE tenants—database row security plus API checks—and where deliberate exceptions apply (sharing, platform operations).
Subprocessors & AI
Procurement-oriented summary of how EQUIRE sends data for AI inference—the Vercel AI Gateway vs. direct-provider paths, subprocessors at a glance, and where contracts govern specifics.