PRIVACY
Simple tools. Simple data practices.
BidSimp does not require an account to use the estimating calculators or play Arcade games. This page explains optional account authentication, saved-work sync, public Arcade leaderboards, local browser storage, site analytics, contact and feedback forms, and advertising.
Calculator and PDF inputs
Values entered into the BidSimp calculators and optional PDF / Print Details fields are used in your browser to calculate results and build the printout. The calculator code does not intentionally send those entered quantities, project names, supplier names, labor rates, prices, notes, or PDF fields to BidSimp analytics.
Accounts and authentication
If you choose to create a BidSimp account, your email address, account identifier, authentication status, and related session information are processed by Supabase to create and secure the account. Authentication emails such as signup confirmation and password recovery are delivered through Resend from a BidSimp sending address. BidSimp does not store your plaintext password; credential handling is provided by Supabase.
If you choose to sign in with Google, Google provides BidSimp's authentication provider, Supabase, with basic account information such as your email address, name, and profile picture when available so Supabase can authenticate you to BidSimp. BidSimp does not request access to your Gmail, Google Drive, Google Contacts, Google Calendar, or other Google services.
When you are signed in, BidSimp stores a local copy of Projects and Saved Estimates for fast access and also synchronizes those records to Supabase so they can be available with your account on another device. Synced records can include project names, project numbers, project or delivery addresses, company and preparer details, supplier account references, planned calculator types, saved-estimate names, calculator type and version information, project assignment, and the calculator data saved inside each estimate. Existing logged-out guest saves are copied into the first BidSimp account used to sync saved work on that browser without deleting the original guest copy.
Blueprint Sketcher also keeps a local working copy in your browser. If you choose to save a named drawing while signed in, BidSimp synchronizes the drawing name and the drawing data needed to recreate that plan to Supabase under your account. Saved drawing records are intended to be accessible only to the signed-in user who owns them.
When you are logged out, Projects and Saved Estimates remain local to that browser and are not intentionally uploaded to a BidSimp account. Deleting a Project does not delete its Saved Estimates; those estimates are kept and become unassigned. Clearing browser site data can remove local copies, but signed-in records that already synchronized to Supabase may remain available from the account.
Optional My Learning records
If you choose Enable My Learning after signing in, BidSimp saves new activity attempts, quiz and challenge answers and results, assessment drafts, confirmed XP, earned ranks, and learning preferences with your account in Supabase. Earlier guest activity is not imported. Free activities remain available without enabling tracking. Games and trainers report participation; reading completion is self-reported. Learning ranks are not professional credentials.
Your browser can keep account-scoped pending learning saves for retry when a connection returns. Confirmed progress comes from your account. Hiding or minimizing the Learning Mode display does not turn off enrolled XP tracking. Public rank display is off by default; if you enable it, eligible Arcade leaderboard entries can show an earned rank beside your chosen public name. Your private answers and account-wide XP are not shown on that leaderboard.
In My Learning, you can export your learning records or confirm their deletion. Deletion removes your live learning history, XP, ranks, drafts and learning preferences, without deleting your account, purchased courses, certificates, projects, estimates or existing Arcade scores. No automatic expiry is currently configured for learning records; they remain until deleted. Database backup retention is separate from deletion of live records. Contact BidSimp for account, backup or privacy questions. Individual answers and learning records are not sent to general marketing analytics by this feature.
Paid LEARN HARD courses
Free calculators and tools can be used without an account. Paid courses require a BidSimp account. Supabase stores enrollment and access records, lesson progress, written exercise responses, assessment answers and results, attempt history, resume position, and certificate records associated with your account. Course responses are synchronized to your account; they are not browser-only.
Your browser also keeps account-scoped course backups and pending save/retry records when storage is available. Dashboard can retry pending saves. Work that has not reached the account may remain only on that browser; if storage is unavailable it may exist only in the open tab. Do not clear site data to resolve a saving problem. Contact BidSimp support for help with account records or privacy requests.
Stripe processes payments. BidSimp stores order and Checkout references, purchase mode, Price and course identifiers, payment status, verified payment/tax totals, currency information, refund outcomes and dispute status for enrollment and support. BidSimp does not receive your full payment-card number. Where Managed Payments is enabled for a transaction, Stripe/Link also provides merchant-of-record transaction support under its applicable terms.
Public certificate verification by Certificate ID displays the issued learner name, course title, completion date, Certificate ID and validity status. It does not display your email, account ID, payment information or assessment responses, and there is no public learner directory. Refund processing preserves progress and existing certificate records.
Public Arcade leaderboards
Arcade games can be played, scored, and shared without an account. If you choose to post an official leaderboard score, BidSimp stores the public display name you choose and a compact leaderboard record for that Arcade game in Supabase. The record keeps your all-time best score and current-month best score, with server timestamps used for ranking. BidSimp does not intentionally store every game run or a detailed score history for the Phase 1 leaderboard.
Your email address is not displayed on the public leaderboard. If you begin posting a score while logged out, BidSimp may temporarily keep that pending game ID and score in local browser storage so it can be claimed after you sign in or create an account. The temporary pending score expires automatically and is removed after a successful claim.
Optional course analytics
With your permission, optional analytics connect course views and campaign labels to registration, purchases and course progress. A first-party cookie remembers the browser's consent record and, when allowed, connects these events. The cookie expires after 30 days. We store account consent on the server after verified sign-in; an existing account's withdrawal is not overridden by another browser's saved preference. Permission expires after 180 days unless you explicitly allow analytics again.
Use the controls below to allow or withdraw permission. While signed in, withdrawal applies to your account across devices and stops subsequent optional events, including events generated by the database. While signed out, withdrawal applies to this browser and any account still bound to its consent cookie; sign in to confirm withdrawal for your account. If confirmation fails, browser tracking stops immediately and the control asks you to retry the server withdrawal. Signing out does not itself withdraw account consent. Withdrawal does not delete previously collected events. The cleanup routine removes analytics events and attribution older than 90 days when it runs; this is not a guaranteed deletion deadline. Account consent decisions are retained until account deletion so that an earlier withdrawal remains effective; browser consent records become eligible for cleanup after 180 days. Existing account, payment and course records have their own retention requirements.
We do not send passwords, authentication tokens, card details, exercise answers or full referring URLs to analytics. Administrators can see aggregate reports. Do Not Track and Global Privacy Control stop browser measurement and request account withdrawal when you visit while signed in. Declining analytics or an analytics failure does not affect signup, purchases, access or progress saving.
During signup, this open tab may keep your password in memory for up to 10 minutes to attempt secure sign-in after you confirm your email on another device. Closing or reloading the tab discards it.
Website analytics
BidSimp uses Vercel Web Analytics to understand basic site usage such as pages visited, referral source, device or browser information, and general geographic information. BidSimp also tracks a small number of feature interactions such as whether a calculator was used, Show the Math was opened, a PDF button was clicked, or feedback was submitted. Custom analytics events do not include the values you type into calculator fields or the text of your feedback.
Contact and feedback forms
If you choose to use the Contact page, your name, email address, subject, message, and the Contact page URL are submitted through FormSubmit so the message can be delivered by email. If you use the site-wide Feedback form, the category, message, page you were viewing, and any email address you voluntarily provide are submitted through FormSubmit for the same purpose. The Contact form requires an email address so BidSimp can reply; the Feedback form email field remains optional.
Advertising and Google AdSense
BidSimp may use Google AdSense to display advertising. When advertising is enabled, third-party vendors, including Google, may use cookies to serve ads based on a user's prior visits to BidSimp or other websites. Google's use of advertising cookies enables Google and its partners to serve ads based on visits to BidSimp and other sites on the Internet.
You can opt out of personalized advertising through Google Ads Settings. You can also learn about choices from participating third-party advertising vendors at AboutAds. Depending on your location and applicable requirements, BidSimp may present a consent message before advertising cookies are used.
Third-party services
BidSimp currently relies on Vercel for website hosting and analytics, Stripe/Link for course payments and related transaction services, Supabase for account authentication, course records, signed-in Project / Saved Estimate and Blueprint Sketcher drawing storage, and Arcade leaderboard records, Resend for authentication-email delivery, jsDelivr for delivery of the Supabase browser library, and FormSubmit for contact- and feedback-form delivery. BidSimp may also use Google AdSense for advertising. These services process information under their own terms and privacy practices.
Changes
BidSimp's privacy practices may be updated as the site, its features, or the services it uses change. If the way BidSimp collects, uses, or shares information changes materially, this page will be updated to reflect the current practices.
Optional AI connections
When you connect an assistant, BidSimp returns the project, estimate, material and linked field records requested by that assistant within your account permissions. Those responses are processed by your chosen AI provider under its own policies. Read permission does not permit changes. Where enabled, separate change permission allows supported changes only after you review the specific preview in BidSimp.
BidSimp stores connection metadata and hashes of connection credentials, together with approval records that may contain project inputs, proposed values and saved results. Operation records older than 90 days are removed when the operation service next runs; this is not a guaranteed deletion deadline. Connection metadata can remain after expiry or disconnection. Hosting logs record endpoint status, tool names, timing and error categories without intentionally recording tool arguments or credentials. Hosting-provider log retention is separate.
Manage access at AI Connections. Removing change access preserves reads. Disconnect stops that connection; it does not remove data already received by your assistant or delete saved business records. Connections also depend on active PRO entitlement and a valid BidSimp sign-in. For access or deletion questions, contact BidSimp.
This page describes BidSimp's current privacy practices and is provided for general informational purposes. These disclosures may be updated as features, service providers, advertising practices, or applicable requirements change.