BidWise privacy

Your information. Your choices.

How BidWise handles personal information across our website, homeowner portal and contractor app.

Last updated .

About this notice

This notice explains how BidWise handles information through our website, homeowner portal, contractor mobile app, and support services. Contact support@bidwiseus.com with privacy questions or requests.

BidWise connects homeowners and contractors. Information you choose to put in a listing, bid, profile, or message may be visible to other participants in the marketplace. Avoid including sensitive information that is not needed for your project.

Information we collect

Account and contact information includes your account identifiers, name, sign-in email, role, contact email and phone number, company, trade, profile details, and account preferences. Clerk provides authentication and processes sign-in and session information.

Marketplace information includes job descriptions, addresses or service areas and ZIP codes, photos and portfolio images, bids and prices, project status, messages, ratings, reviews, and contact-sharing choices. Contractor records can include business listings, licensing information, and insurance documents you submit. Support and website contact requests include the information you send us. Safety records include reports, blocking choices, terms acceptance, moderation decisions and records of authorized staff access or actions.

Payment-related information includes Stripe customer, checkout, subscription and payment identifiers, payment status, accepted-bid fees, amounts, and billing history. Stripe processes payment details in its checkout services; BidWise uses payment metadata to apply fees and account benefits.

Device and usage information can include IP address, browser or device information, account or analytics identifiers, page and screen visits, interactions, timestamps, security logs, and notification tokens. Location supplied in jobs and profiles is used for local matching; the current app does not request background GPS tracking.

How we use information

We use information to create and secure accounts, display profiles and jobs, match local opportunities, deliver bids and messages, manage subscriptions and fees, provide notifications and support, prevent abuse, maintain records, and understand and improve the service.

If you opt into website updates or offers, we use your contact information for that purpose. You can ask support to stop those messages. Transactional and security communications are separate from marketing.

Access and service providers

Other users receive information needed for marketplace interactions, such as contractor profiles, job listings, bids, and messages. Homeowner contact sharing is a separate choice after bid acceptance, not automatic permission to publish all contact details. Information you put in free-text fields or photos may itself reveal contact details.

Service providers process information for authentication (Clerk), payments (Stripe), hosting, database and file storage (including Google Cloud-backed object storage), and mobile notifications (Expo and the platform delivery services, including Google on Android). Push delivery uses a device notification token and notification content; device settings control whether previews appear on your lock screen.

Google services support business-listing lookups and reCAPTCHA where enabled. A lookup can send a supplied business name, listing link, or place identifier to Google and return public business information. HeyCatch provides product analytics; optional Umami analytics is described below. Providers may process information in countries other than your own and have their own privacy notices.

Authorized operators and providers may access information to operate and support BidWise. Information may also be disclosed when needed to comply with legal obligations, investigate abuse, protect people or the service, or handle a business transfer. Do not interpret these uses as a guarantee that every contractor has been screened.

Analytics and browser storage

HeyCatch runs automatic product analytics on the public website, web portal, and native app, including page or screen views and eligible button or tap interactions. Signed-in identity properties can include your BidWise account ID, email, name, plan, and signup date. Requests may include device, browser, network and usage metadata.

Authenticated web and native content and the public contact form use no-capture boundaries to limit collection of private entered text. The explicit server outcome events are account_created, account_updated, and platform_fee_verified. Messages, photos, job descriptions and contact text are not intentionally included in explicit analytics event fields or identity properties. These protections do not stop page or screen views.

The public website's optional Umami events depend on accepting optional analytics. The Accept, Decline and Cookie Settings controls do not switch HeyCatch on or off. Essential sign-in, security and preference storage is also separate. See the Cookie Policy for browser controls. Contact support about analytics privacy requests; there is not a single in-app switch that disables all analytics.

Retention, account deletion and your choices

We retain information as needed to operate your account and marketplace activity, provide support, resolve disputes, prevent fraud, and meet applicable recordkeeping obligations. Different records and provider backups may have different retention periods; there is no single automatic expiration period for all information.

You can request account deletion from the account controls or the public Account Deletion page without reinstalling the app. The public form accepts a request without sign-in and gives you a reference without revealing whether an account exists. Save the reference, sign in with your own matching verified email, return to the form and verify ownership. No verification email is sent. Staff can process the request only after that authenticated ownership check. If you cannot sign in, try sign-in recovery or contact support@bidwiseus.com for help; an email claim alone cannot authorize deletion. Deleting the app from your device does not delete your account or cancel a subscription.

Completed deletion removes your Clerk sign-in identity, personal profile and contact fields, owned avatar, portfolio and job uploads, insurance file, authored message text, job descriptions and location details, bid text and contact shares. Stripe subscription renewal is stopped. A minimal inactive pseudonymous account row, project and bid relationships, statuses and amounts, and payment/subscription identifiers and receipts remain for counterpart records and financial obligations. Payment processor transaction records and copies already received by other users are not erased by BidWise.

Deletion-request audit records retain timestamps, status and actor identifiers; the request email and Clerk ownership-proof identifier are removed on completion. Provider failures leave a request available for retry rather than marking it complete, and access may be locked while deletion finishes. Provider backups and other provider records may not disappear immediately.

Safety reports, moderation evidence and staff audit records may retain reported content, prior versions and action reasons even after content is removed from marketplace display or an account is deleted. Restricted administrative records for designated store-review accounts also retain their account identifiers, designated email, setup status and responsible staff identifier to prevent misuse of review access. We retain these records for safety, accountability, dispute handling and legal obligations as needed; removal from display is not a promise to erase all audit evidence. There is no fixed automatic deletion period for these financial and audit records.

You can update available profile fields, choose what to upload or share, and change notification or photo permissions in device settings. Contact support to request access, correction, deletion, or information about other privacy choices available under the laws that apply to you. We may verify your identity and explain any limits on a request.

Storage, security, children and changes

BidWise uses authentication, access checks and other technical safeguards to protect information in its databases, file storage and provider systems. No online service or transmission can be guaranteed completely secure. Protect your sign-in access and contact support if you suspect misuse.

BidWise is intended for adults, not children under 18. Please contact support if you believe a child has supplied personal information so we can review and address it.

We may update this notice as our services or practices change. The current notice is published here. Questions and privacy requests can be sent to support@bidwiseus.com.

Privacy and analytics

What BidWise analytics does

BidWise uses HeyCatch, an analytics SDK and service provider, for automatic product analytics across the public website, the customer web portal, and the native app. HeyCatch is separate from the optional Umami analytics choice on the marketing pages and is not turned on or off by the cookie banner's Accept or Decline choice.

Automatic collection describes product use, including web pages, native screens, and button or tap interactions. When you are signed in, BidWise may send your BidWise account ID and the available account properties email, name, plan, and signup date. The web portal marks its authenticated area as ph-no-capture, and the public contact form is marked the same way, to keep private user-entered content out of HeyCatch DOM autocapture while page views continue.

BidWise's server integration currently sends only these explicit HeyCatch outcome events: account_created, account_updated, and platform_fee_verified. Their limited context can include account role or the platform-fee event type. This integration does not send subscription or other payment-lifecycle events. Messages, job details, bids, contact or notification text, photos, and similar user-generated content are not used as HeyCatch identity properties or explicit event fields by this integration.

Questions and privacy requests: support@bidwiseus.com.

Your analytics choice

Optional analytics remains optional

Other analytics used on the public marketing pages, including the existing Umami events, remain optional and are sent only after you choose Accept in the cookie banner. Declining or later withdrawing that optional choice stops those other analytics events. It does not turn off HeyCatch automatic analytics.

The existing banner remembers the optional account choice in its cookie/local-storage state. That choice is for the optional analytics tools; it does not control HeyCatch's own analytics session or account identity. You can read the current product and pricing information without accepting optional analytics.

Account Deletion · Cookie Policy · Contact support