Venture Data Source + Correction / Removal Policy

Where Venture information comes from

Venture records on BCM may be created through different supported product workflows. The source of a Venture record does not by itself establish ownership, verification, endorsement, or accuracy.

• User-created Ventures may be submitted through supported self-service creation flows.
• Owner-created or owner-managed Ventures may later be edited by an authorized Venture owner under BCM's ownership rules.
• BCM administrators may create or manage Venture records where supported by administrative workflows.
• Discovery-created Ventures may originate from source-backed records supplied through BCM's approved discovery workflow after an authorized operator has confirmed that the source is permitted for BCM use.
• BCM does not describe a discovery-created Venture as owner-submitted unless an owner later establishes ownership through BCM's normal claim process.

Discovery provenance and internal review

The current Venture Discovery Engine stores source provenance and uses internal validation, deduplication, confidence scoring, and administrator review before an approved discovery candidate can be converted into a public Venture.

• Source provenance may include an internal source key, source reference, source URL, source metadata, discovery timestamp, and related review records.
• Current discovery ingestion uses an operator-supplied, source-backed record model rather than an automated public web-fetch source adapter.
• Validation checks structural data such as source references, URLs, location fields, coordinates, and stored source consistency where available.
• Deduplication evaluates deterministic signals such as normalized name, website/domain, location, coordinate proximity, source reference, and source URL.
• Confidence scoring combines internal validation, provenance, website/location completeness, coordinates, and deduplication signals. A confidence score is an internal workflow aid and is not a public endorsement, verification badge, quality rating, or guarantee of accuracy.
• Discovery provenance, confidence details, validation results, deduplication results, decision notes, and administrative review records are private operational information and are not ordinary public Venture profile content.

Approval and conversion of discovery candidates

A discovery candidate must be approved through BCM's discovery-review workflow before it can be converted into a Venture. Confirmed duplicate relationships must be resolved before conversion.

• Conversion creates a separate Venture record and preserves a discovery-conversion record linking the candidate to that Venture.
• A converted discovery Venture is published as unclaimed and unverified under the current workflow, with no owner automatically created.
• Discovery-created Ventures may therefore appear publicly before any owner has claimed or verified them.
• Publication of a discovered Venture does not mean BCM independently verified every source fact, that an owner submitted the information, or that the Venture is current, operating, legitimate, or complete.

Correcting Venture information

BCM provides several correction paths depending on the nature of the issue. Submitting a correction request, report, claim, dispute, or impersonation case does not guarantee a particular outcome or review time.

• An authorized Venture owner may edit supported public profile information after legitimate ownership has been established through BCM's ownership system.
• A person seeking control of an eligible unclaimed Venture may use the Venture claim process. A submitted or pending claim does not itself establish ownership.
• Ownership errors or conflicting control assertions may be handled through BCM's ownership-dispute and audited ownership-correction/transfer process.
• Users may report a published Venture for supported reasons including misleading information, suspected scams, duplicates, or a business that no longer exists.
• Identity or control concerns may be submitted through BCM's impersonation / ownership-issue reporting workflow.
• Authorized BCM administrators may review and correct Venture records or relationships through moderation, discovery-review, ownership, or other supported administrative workflows.

Reports and ownership issues do not automatically change a Venture

Reports, claims, ownership disputes, and impersonation cases create review records. They do not automatically remove a Venture, transfer ownership, verify a Venture, or establish that the submitted allegation is correct.

• BCM may dismiss or resolve a report without removing the Venture.
• An impersonation case may be dismissed, resolved, routed to ownership review, or result in an explicit moderation action.
• A dispute may be rejected or resolved without a transfer, or may be associated with an audited ownership transfer when BCM determines that correction is appropriate.
• Claim approval, ownership transfer, unpublishing, and archiving occur only through their respective BCM workflows.

Unpublishing and archiving

Authorized BCM administrators may explicitly unpublish or archive a Venture when supported moderation, reporting, impersonation, ownership-integrity, safety, legal, or platform-integrity review warrants that action.

• Unpublishing currently changes the Venture's publication state to paused and removes its published timestamp; it does not hard-delete the Venture record.
• Archiving changes the Venture to archived status, records an archive timestamp, and removes its published timestamp; it does not hard-delete the Venture record.
• Normal moderation/removal actions preserve the underlying Venture record and may preserve claim, verification, ownership, discovery, reporting, impersonation, moderation, relationship, and audit history where appropriate and lawful.
• BCM does not promise that removal of public visibility deletes every historical or internal record associated with the Venture.

Accuracy and source limitations

BCM uses the information available through its supported user, owner, administrative, and approved discovery workflows, but source information can be incomplete, stale, disputed, or incorrect.

• BCM does not guarantee that every source fact has been independently verified.
• BCM does not guarantee that every discovered Venture remains accurate, current, active, or claimable.
• Internal validation and confidence scoring measure specific workflow signals; they are not substitutes for owner verification or a legal determination of business identity.
• Users should independently confirm important information before relying on a Venture profile for employment, investment, partnership, purchasing, or other consequential decisions.

Privacy and historical records

Public Venture profiles contain only the public-facing information BCM chooses to display under its product rules. Internal provenance and review information remains subject to BCM's Privacy Policy and access controls.

• Source metadata and internal discovery evidence are not ordinary public profile content.
• Claim, verification, ownership-dispute, impersonation, moderation, and administrative audit records are handled as private operational records except where a limited public status is part of the product or disclosure is required or permitted by law.
• Correction, unpublishing, or archiving does not create a promise that all historical, security, integrity, transaction, or audit records will be deleted.

Relationship to other BCM terms

Claim, ownership, verification, dispute, and transfer details are governed by the Claim / Ownership / Verification Terms. General Venture conduct is governed by the Venture Terms. Paid presentation and Venture subscription terms are addressed separately. Analytics and referral-tracking disclosures are addressed separately where applicable.