Privacy Policy

WitBacon may collect information needed to operate accounts, reports, paid access, contributor workflows, notifications, and administrative review systems.

• Account information such as name, email address, role, profile settings, and authentication records.
• Saved companies, collections, watchlist settings, notification preferences, and account activity.
• Report access records, order status, payment status, access grants, price, currency, and related timestamps.
• Contributor submissions, review outcomes, evidence notes, source descriptions, confidentiality levels, and contribution records.
• Technical information such as session cookies, login state, request logs, error logs, and security logs.

WitBacon stores account information needed for login, profile display, orders, report access, saved companies, collections, notifications, contributor workflows, and admin operations where applicable.

Users are responsible for keeping their account credentials secure and for notifying support if they suspect unauthorized access.

Report access may depend on order status, payment confirmation, administrator grants, or other approved access workflows. WitBacon may store report access records, order status, amount, currency, timestamps, and related operational information.

Where payment providers are used, payment processing may be handled by third-party services. WitBacon should not store sensitive payment card information unless it is implemented through secure and compliant providers.

Contributor submissions may include company information, source descriptions, evidence notes, confidentiality levels, review outcomes, credibility outcomes, contribution scoring factors, report contribution links, and revenue ledger records where applicable.

Private submission content, confidential source descriptions, and internal reviewer notes should not be shown publicly. Submissions may be retained for review, auditability, dispute resolution, access control, contributor governance, and product integrity.

Contributor profile settings may include display name, contributor type, organization, title, bio, expertise areas, anonymity preference, contributor status, and revenue share eligibility.

Public contributor identity should not be exposed unless the product supports it and the user has chosen that setting. Contributor earnings, revenue ledger entries, payout batch status, and related records should be visible only to the relevant contributor and authorized administrators.

• To operate accounts, authentication, sessions, and profile settings.
• To manage report access, orders, paid reports, and administrator grants.
• To review contributor submissions and maintain contributor trust and eligibility records.
• To calculate report contribution attribution, revenue ledger entries, and payout batch records where implemented.
• To send account, access, submission, or system notifications where enabled.
• To detect abuse, fraud, duplicate submissions, unauthorized access, or security issues.
• To improve product reliability, auditability, and user experience.

WitBacon may support different confidentiality levels for submitted information. As a general principle, private submissions, confidential source descriptions, internal reviewer notes, contributor earnings, and payout records should not be displayed publicly.

• Public company information may be shown publicly.
• Account data should remain account-only unless intentionally displayed by the user.
• Private submission content should remain within review and account workflows.
• Internal reviewer notes should remain admin-only.
• Contributor identity should not appear publicly unless supported by product settings and user preference.

• Session and account state may use cookies or equivalent browser storage.
• Cookies may be used to keep users logged in, protect account access, and support preferences.
• Notification preferences may control in-app and email notifications where implemented.
• Email provider behavior depends on deployment configuration.
• Analytics, if added, should be documented by the deployment operator.

WitBacon may use service providers for hosting, infrastructure, email delivery, payment processing, analytics, security, and operational support.

These providers should only receive information necessary for their role. Payment provider secrets, webhook secrets, and internal service credentials must remain private and should not appear in public pages or user-facing interfaces.

WitBacon should not sell personal information to advertisers. Information may be shared only where necessary for service operation, payment processing, email delivery, hosting, legal compliance, fraud prevention, security, authorized administrative review, or other product operations.

WitBacon may retain operational records such as accounts, orders, report access records, contributor submissions, review outcomes, score snapshots, audit records, revenue ledger records, and payout batch records.

Retention may be necessary for access control, auditability, contributor governance, dispute resolution, legal compliance, and product integrity. A complete retention schedule may be added as the product matures.

WitBacon should use reasonable administrative, technical, and organizational measures to protect account data, access records, contributor submissions, and operational records. No online service can guarantee perfect security.

Depending on implemented features, users may be able to update account profile information, manage notification preferences, remove saved companies or collections, review their own submissions, and view their own contributor earnings.

Additional data access, export, correction, or deletion workflows may be added as the product matures.

WitBacon may update this Privacy Policy as the platform evolves. Material changes should be reflected on this page. Continued use of WitBacon after changes means the updated policy applies to future use of the service.

For privacy questions, account data questions, contributor submission concerns, or access issues, please contact WitBacon through the available support or contact channels.