Data Retention and Account Deletion

Active accounts

We retain account, workspace, company, buyer-path, validation, application, and billing-status records while an account is active so the service can operate. Stripe retains payment and transaction records under its own policies.

Capability statements

Outerpath processes an uploaded capability-statement PDF and its extracted text only for the requested extraction. We do not retain the PDF or full document text. We retain limited source metadata, extracted claims, the private review draft, and the user’s claim decisions so Company Intelligence remains explainable and resumable.

Managed buyer-research inquiries

Managed-service inquiry information is retained while Outerpath reviews the request and, if accepted, while reasonably necessary to provide and administer the service. Closed or unqualified inquiries are reviewed for deletion after 12 months. Limited records may be retained longer when reasonably necessary for fraud prevention, dispute handling, legal obligations, or to honor a deletion or contact preference. The experiment stores a capability-statement link when supplied; it does not upload or copy the linked document into Outerpath storage.

AI BD assistant early-access requests

Early-access requests are retained while Outerpath evaluates the experiment and any related contact. Closed or unqualified requests are reviewed for deletion after 12 months. Limited records may be retained longer when reasonably necessary for abuse prevention, legal obligations, or to honor a deletion or contact preference. The waitlist does not create an account or product-access record.

Public-page chat

Visitor-initiated public-page conversations and any contact details voluntarily provided in them are stored by Tawk.to and remain available to Outerpath until deleted in the provider dashboard or through a completed deletion request, subject to applicable legal and provider requirements. Tawk.to may use a returning-visitor cookie for up to six months and session or local storage to operate chat after the visitor accepts the configured chat consent form. Clearing browser data removes local identifiers but does not automatically delete provider-held conversations. Do not submit classified information, controlled unclassified information, proprietary customer information, or other sensitive material through public chat.

Ask Outerpath conversations

When you use Ask Outerpath, Outerpath retains the Path-scoped conversation for up to 180 days so it can remain available across sessions. We also retain limited execution metadata such as model, token counts, latency, status, and a context fingerprint for cost, reliability, and security review. Ordinary execution logs do not duplicate the conversation or bounded Path context.

Public Advisor conversations

The public Advisor stores each anonymous conversation in a separate private research store for no more than 30 days. Message text is encrypted at the application layer. A short-lived, first-party, HTTP-only session token lets the same browser continue the conversation; only its one-way hash is stored. Outerpath also retains bounded research classifications and execution metadata such as provider, model, token counts, estimated cost, latency, status, controlled error code, sanitized campaign fields, and whether a conversion CTA was selected. These records are not joined to an authenticated account or sent to analytics. A daily retention job removes expired conversations and dependent records. You can delete the current conversation from the page; Support can process a verified request when enough information exists to locate it.

Federal Buyer Discovery pilot

Company website content, uploaded capability-statement PDFs, and full extracted text are processed transiently and are not retained by Outerpath. A bounded portion of extracted text and the optional desired-work description are sent to OpenAI for one structured search-plan interpretation. When the database-backed pilot is enabled, Outerpath retains the stated research focus, bounded capability categories and acquisition terms, model/token/cost/latency metadata, temporary public-record recommendation results and source links, coverage and operational fields, and salted one-way session and network hashes for no more than two hours. The source PDF, website body, and full extracted text are not included in that record.

A scheduled cleanup removes expired rows; reservation requests also remove expired rows before applying the pilot's quotas. An authorized operator may review the temporary recommendation results and bounded execution trace during that window. These records are not joined to an account or customer workspace. Public analytics receives only coarse lifecycle events and excludes submitted content, desired-work text, interpreted capabilities, search terms, and recommendation details; its separate retention is described under Analytics data.

Analytics data

Limited Vercel Web Analytics on approved public pages uses no analytics cookie or persistent browser identifier. Vercel derives an aggregated visitor hash from transient request data and rotates it after 24 hours. Its current Pro reporting window is 12 months, and Vercel states that analytics data may be retained longer under its service policies.

A separate PostHog public-web project records approved page views, exits, engagement, coarse scroll thresholds, calls to action, and demonstration engagement in cookieless mode. It does not store a PostHog identifier in cookies, local storage, or session storage, create person profiles, or join public activity to accounts, workspaces, Buyer Paths, or the separate consented product-analytics project. PostHog uses temporary server-side session linkage, so reports cannot reliably recognize the same browser across later visits. PostHog Cloud currently retains these event records for one year under Outerpath's free plan; the provider controls this plan-based period. The separate public Advisor conversation store is not analytics and retains its encrypted records for no more than 30 days as described above.

Aggregate account, company, and first-Buyer-Path totals are calculated from the service records already required to operate an active account; Outerpath does not create a separate visitor-level conversion history for those stages. Internal and test records are excluded from business reporting through a private operator control list. Optional product PostHog and Google Analytics data is collected only after consent and is retained under Outerpath's provider configuration and those providers' policies. Analytics preferences and Global Privacy Control stop future public PostHog capture; changing a browser preference does not automatically delete provider-held events collected earlier.

Deletion requests

Account and organization owners may delete an eligible single-member workspace from Account settings. Active paid subscriptions must end first. Workspaces with other members or deletion problems require Outerpath Support so ownership and identity can be verified.

Deletion timing

We aim to remove active workspace records within 30 days after a verified request. Limited records may remain longer in backups, security logs, billing records, dispute records, or where retention is reasonably necessary for legal, tax, fraud-prevention, or contractual obligations.

Public company records

Deleting a user account does not necessarily erase factual company information independently obtained from public sources. We will remove the deleted account’s private workspace data and claimed-profile management rights. Requests to correct or delist a public company record can be submitted separately.

Exports

Organization owners can download a JSON export of their workspace records from Account settings before deletion. Support can assist when a workspace cannot use the self-service process.

Browser data

Some legacy execution tools store information in browser localStorage or sessionStorage. Signing out or deleting a cloud account may not remove those local copies. Clear site data in each browser used to remove them.