Account and authentication
Bidwicket stores the account name and email address, authentication records, and session data used to sign in and keep the account active. Session records can include the session token, sign-in IP address, and browser user-agent when recorded by the authentication system.
Matching preferences
The account can store a trade, service area, and business-size preference. Bidwicket uses those values to match configured public opportunities and prepare daily email digests.
Purchases, verification, and access
Bidwicket stores purchase and checkout references, payment-verification results and timestamps, subscription status, and account entitlements. These records are used to verify the purchase and determine whether the matching account can access current opportunities and digest history.
Digest history and access reports
Bidwicket stores daily digest results, snapshots of matched public notices, email send status, and related message and sent-time details. Notice snapshots can include titles, agencies, scopes, locations, deadlines, estimated values, summaries, trade tags, and links to the original public posting. These records support account history and show what was matched or sent.
An access report is stored with the buyer account and exact purchase it concerns. It includes the selected issue, short description, report outcome, and timestamps so verified staff can review the request.
Services used
Stripe provides hosted checkout and subscription billing. Better Auth provides account authentication and sessions. Polsia email delivery sends daily digests and access messages. When deployment analytics is enabled, a random browser visitor ID is stored in local storage and sent with the Bidwicket deployment slug to Polsia's page-view analytics beacon.