Venture Analytics / Referral / Tracking Disclosure

Venture interaction analytics

BCM records supported Venture interaction events to operate, measure, protect, and improve Venture features. Depending on the event, privacy preferences, and whether the user is signed in, records may be identified, anonymous, aggregated, deduplicated, or classified for traffic-quality purposes.

• The current Venture event taxonomy includes Venture profile views, shares, outbound website clicks, claim starts, claim submissions, verification submissions, Venture creation, Explore My Area opens, mini-map opens, badge/embed interactions, map interactions, Open To changes, and We’re Hiring changes.
• Analytics records may include a user identifier or anonymous session identifier where permitted, a Venture identifier, event type, route or source surface, timestamp, referrer/traffic source, device or traffic classification, and limited event-specific metadata.
• BCM applies event deduplication windows and traffic classification so repeated or suspicious activity can be treated differently from meaningful interaction counts.
• Not every interaction is personally identifiable. For non-essential analytics events, BCM's product-analytics preference may cause user and anonymous-session identifiers to be omitted.

Owner-facing Venture analytics

Authorized active Venture owners may receive aggregate Venture analytics for supported time ranges. Current owner analytics are count-based and do not provide a list of individual visitors.

• Current owner metrics include profile views, shares, outbound website clicks, Explore My Area opens, mini-map opens, badge/embed interactions, claim starts, claim submissions, and verification submissions.
• Owner-facing analytics do not expose a user's exact private Home coordinates, private Watch / Save state, private claim or verification evidence, reports, impersonation evidence, or administrative moderation/audit history.
• BCM does not represent aggregate owner analytics as proof that a particular identified person viewed, shared, claimed, or otherwise interacted with a Venture unless a separate product workflow expressly provides that identity.

Referral identifiers and landing attribution

BCM can generate Venture referral links containing a deterministic referral identifier. When an eligible referral link is opened, BCM may create a referral-attribution record linking that landing to the referring Venture and, where applicable, the referring owner context.

• A referral landing may store an attribution identifier, referral identifier, referring Venture, referring owner context where available, and landing time.
• BCM may store the referral attribution context locally for a limited period so a later qualifying Venture/user conversion can be connected to the earlier referral landing.
• Referral attribution does not guarantee that the visitor registers, creates a Venture, becomes an owner, or otherwise converts.
• A referral landing is not itself a conversion and does not automatically create Contribution credit.

Qualified referral rewards

Contribution credit for referrals is awarded only when BCM's qualified-referral rules are satisfied and a qualifying conversion is actually recorded.

• When a valid attribution is connected to a later referred user and referred Venture conversion, BCM may create a qualified_referral Contribution event for the referring Venture.
• The referring owner must still be available as an active Venture owner for the reward path that requires owner attribution.
• Self-referrals are excluded, including cases where the referred user is the referring owner or is already an active owner of the referring Venture.
• Duplicate or already-converted attribution records do not create an additional qualified-referral reward.
• Sharing a Venture by itself does not guarantee Contribution credit or a referral reward.

Return Engine Venture signals

BCM's Return Engine can use Venture activity and saved/watched state to generate supported retention signals for users who have the applicable retention-email preference enabled and a recorded consent state.

• Current Venture Return signals include new published Ventures near a user's eligible Home location and state changes for watched Ventures, such as stage changes, becoming open to employees, becoming open to a first hire, or recently launching.
• Nearby Venture signals use the user's stored Home coordinates and configured Venture-return radius to determine eligibility. Exact private Home coordinates are not exposed to Venture owners through this process.
• Watched Venture state and Watch / Save relationships remain private to the user.
• A Venture Return signal is eligible only when retention messaging is enabled, consent has been recorded, and the user has not unsubscribed.
• Unsubscribe and suppression rules apply to Return Engine messaging, including the existing one-click unsubscribe mechanism and stored retention preference state.

Queued, delivered, and returned are different states

BCM may record that a Venture Return Engine event was queued and, where applicable, delivered to the downstream messaging system. Those operational states are not the same as a user opening the message or returning to BCM.

• A queued event means BCM created an eligible Return Engine event for processing.
• A delivered event means the Return Engine outbox recorded delivery according to the applicable delivery workflow.
• Neither queued nor delivered status guarantees that the user saw the message, clicked it, returned to BCM, or took any action.
• BCM does not guarantee Return Engine delivery, user return, referral conversion, or any resulting business outcome.

Private operational data is separate from behavioral analytics

Behavioral analytics are separate from BCM's private trust, ownership, moderation, and administrative records.

• Private claim evidence, verification evidence, Venture reports, impersonation evidence, and ownership-dispute evidence are not ordinary Venture behavioral analytics content.
• Administrative moderation and audit history is maintained for platform operations and integrity, not as ordinary owner-facing behavioral analytics.
• Source provenance and internal discovery-review evidence remain governed by the Venture Data Source + Correction / Removal Policy and Privacy Policy rather than being treated as ordinary interaction analytics.

Privacy choices and measurement limits

BCM applies privacy and consent controls to analytics and retention systems. Some operational or security events may be handled differently from optional product analytics where necessary to operate, secure, or bill the service.

• Analytics can use user/session identifiers where permitted, but BCM does not claim that every Venture interaction is personally identifiable.
• Retention-email consent is separate from ordinary Venture browsing and can be disabled or unsubscribed through BCM's supported preference and unsubscribe flows.
• Analytics, referral attribution, and Return Engine records are measurements of product activity and system state; they do not guarantee accuracy about a person's intent or future behavior.

Relationship to other BCM policies

General data handling remains governed by BCM's Privacy Policy. Venture source/provenance and correction/removal rules are addressed in the Venture Data Source + Correction / Removal Policy. Venture ownership and verification evidence remain governed by the Claim / Ownership / Verification Terms.