bldhub

COOKIE POLICY

Learn how bldhub utilizes cookies and automated tracking technologies to protect, optimize, and deliver our construction bidding and design services.

Effective Date: October 20, 2026

1. INTRODUCTION & SCOPE

Meraki Architecture LLC (operating the platform "bldhub", and hereinafter referred to as "bldhub", "we", "us", or "our") operates the web-based software-as-a-service platform located at bldhub.us (the "Platform"), alongside all associated modules, services, databases, and visualization tools. This comprehensive Cookie Policy clarifies our utilization of operational cookies, local storage identifiers, pixel tags, and federated authorization tokens across the entire bldhub ecosystem.

This Cookie Policy applies strictly to all visitors, registered accounts, and unregistered participants of the Platform, regardless of their selected portal role or level of administrative privilege. This includes, without limitation, Property Owners, Developers and General Contractors (collectively, "Contractors"), and Subcontractors.

This policy must be read in direct conjunction with our separate, comprehensive Privacy Policy and terms of service. Bldhub, as a neutral technology gateway registered in Texas, USA, is committed to full transparency and compliance with applicable regional privacy frameworks, including the Texas Data Privacy and Security Act (TDPSA), the California Consumer Privacy Act (CCPA), and global structures such as the General Data Protection Regulation (GDPR) and the ePrivacy Directive.

By continuing to access, register with, or navigate bldhub.us, you acknowledge our structured use of tracking cookies to preserve cybersecurity, process transactional data, and provide stable digital rendering services as explained in this document.

2. WHAT ARE COOKIES

Cookies are small, encrypted text files containing alphanumeric strings that are automatically downloaded to and stored on a user's web browser, computing station, tablet, or cellular device when visiting a digital platform. Cookies allow websites to securely identify specific browsers, remember credentials, preserve local shopping baskets or form drafts, and analyze overall site health.

Our platform utilizes cookies in the following configurations:

  • First-Party Cookies: Set and governed directly by bldhub.us to handle core platform operations, maintain active user sessions, and store dashboard selections.
  • Third-Party Cookies: Set and governed by external, integrated enterprise partners such as Google and Stripe to facilitate secure federated integrations, process cloud payments, and carry out fraud audits.
  • Session Cookies: Temporary files that reside in cache directories only during your active platform session. These are wiped automatically the moment your browser program is terminated.
  • Persistent Cookies: Semi-permanent files that remain on your terminal hardware for established, pre-allocated time spans or until manually expunged by the user. These remember returning accounts and preserve portal preferences.

Please note that this Cookie Policy also applies directly to other tracking technologies with parallel applications, including HTML5 local storage tokens, ephemeral session storage matrices, pixel beacons, and secured authentication web tokens such as Google Firebase Auth JSON Web Tokens (JWTs).

3. CATEGORIES OF COOKIES WE USE

We employ five distinct classes of cookies and storage layers to balance operation, performance, and transaction security:

A) Strictly Necessary Cookies

These are fundamental technologies indispensable for operating bldhub.us's secure structural features. Core features including profile-restricted portal navigation, database lookups, and secure contract bidding cannot exist without them:

  • Firebase Authentication Tokens: Used to securely maintain your verified logged-in state as you cross between active Property Owner, Developer, or Subcontractor dashboard modules.
  • Google OAuth Session Tokens: Enabled to authorize identities when logging in instantly using secure Google Sign-In mechanics.
  • Security & Anti-Forgery Cookies: Deployed to verify individual browser sessions, block cross-site request forgery (CSRF) attempts, and prevent unauthorized terminal insertions.

Note: These cookies cannot be manually deactivated as they form the basic fabric of platform stability and account isolation on the web.

B) Functional Cookies

Functional cookies allow our servers to organize visual setups and custom choices you select, preventing repetitive form-filling and providing customized experiences:

  • User Role and Dashboard Prefs: Stores the platform context inside client-side session variables to ensure returning professionals open directly onto the Contractor or Subcontractor modules rather than the basic Owner view.
  • Project Draft State Storage: Safely preserves project specifications, pricing estimates, and upload forms temporarily to ensure work is not lost during brief network interruptions.
  • UI Customizations: Remembers your light mode configurations, system font scale choices, search queries, and selected filters.
C) Analytics & Performance Cookies

These tools compile statistics, traffic trends, and computational bottlenecks to support the ongoing development of our product:

  • Usage Analytics: Gathers aggregate metadata regarding visitor counts, page loading sequences, tool click ratios, and bounce timelines.
  • Error and Crash Reporting: Pinpoints faulty script terminations and database lookup errors, providing real-time diagnostics to our engineering department.
  • Performance Indicators: Measures page delivery delays, API transmission speeds, and Google Gemini 3D visualizer rendering durations to target optimization strategies.
D) Third-Party Service Cookies

Bldhub works in close partnership with stable technology suppliers to authorize credentials, render neural models, and secure money flows:

i) Google / Firebase Infrastructure Cookies:Firebase Auth sets authentication, identification, and profile parameters. Google Sign-In records federated authentication cookies. Additionally, Google's Gemini API may assign ephemeral tokens during AI 3D visualization rendering sequences to control active query requests. These operations are governed entirely by Google's Privacy Policy which can be reviewed at policies.google.com/privacy.
ii) Stripe Payments Cookies:Stripe sets highly secure tracking tokens inside your checkout window to evaluate money laundering risks, verify transaction histories, validate certificates under PCI-DSS standards, and process contractor subscription packages. This includes dedicated transaction-specific risk evaluation tokens (e.g., __stripe_mid, __stripe_sid) dropped when interacting with purchase modules. These are governed by Stripe’s Privacy Policy which can be accessed at stripe.com/privacy.
E) Marketing & Promotional Cookies

From time to time, bldhub may employ tracking pixels to evaluate the reach of platform release campaigns. bldhub guarantees that we do NOT utilize advertising cookies to log user movements across unrelated domains, nor do we sell, lease, or distribute behavioral user models, cookie sheets, or profile metadata to external data brokers or advertising exchanges.

4. COOKIE DURATION REFERENCE TABLE

To maintain transparency, the following technical matrix lists representational tracking cookies and tokens utilized within our codebase:

Cookie Name / TypePurposeProviderDurationCategory
Firebase Auth TokenSession persistence and user authentication across portalsFirebase/GoogleSession or up to 1 yearStrictly Necessary
Google OAuth TokenThird-party federated identity verification and sign-inGoogleUp to 2 yearsStrictly Necessary
__stripe_midFraud detection, transactional security, and merchant protectionStripeUp to 1 yearStrictly Necessary (Third-Party)
__stripe_sidMaintaining active payment session and tokenized secure checkout flowStripeSessionStrictly Necessary (Third-Party)
Role Preference TokenDashboard state management (Property Owner, Developer, or Subcontractor view)bldhubSessionFunctional
Analytics TokenAggregate usage tracking, page navigate sequences, and platform optimizationbldhubUp to 13 monthsAnalytics
Performance MonitorError tracking, debug triggers, API call latency, and render speedsbldhubUp to 6 monthsAnalytics

5. HOW WE USE COOKIE DATA

We employ the data extracted through our tracking elements to handle distinct operational processes:

  • Authenticating identity and sustaining active digital sessions securely across Owner, Contractor, and Subcontractor portals.
  • Remembering your system roles, access parameters, and dashboard preferences during screen transitions.
  • Preserving unsaved layout inputs, 3D visualizer prompts, and draft project entries to prevent work loss.
  • Processing secure corporate credit packages, coin transactions, and billing ledgers securely via the Stripe checkout system.
  • Detecting, blocking, and auditing credential scams, fraudulent access attempts, licensing lies, and bidding violations.
  • Evaluating platform performance data to implement speed improvements, core visualizer updates, and feature updates.
  • Monitoring AI render pipelines and operational speeds to sustain stable response channels under intense workloads.

6. YOUR COOKIE CHOICES & CONTROLS

Bldhub respects user control over tracking elements. We provide multiple routes to configure, limit, or remove tracking details:

A) Browser-Level Controls

Web browsers permit users to inspect active cookie registries, selectively block third-party trackers, or clear browser data. You may customize these parameters in the configuration panel of your browser:

  • Google Chrome: Access "Settings" > "Privacy and security" > "Third-party cookies".
  • Mozilla Firefox: Access "Settings" > "Privacy & Security" > "Enhanced Tracking Protection".
  • Apple Safari: Access "Settings" > "Privacy" > "Prevent Cross-Site Tracking".
  • Microsoft Edge: Access "Settings" > "Privacy, search, and services" > "Tracking prevention".
  • Mobile Browsers (iOS/Android): Adjust cookie settings inside global OS application options or browser preferences.

Warning: Restricting strictly necessary cookies will instantly break login sessions, block secure portal displays, and prevent proposal bidding or checkout submissions.

B) Opt-Out of Analytics

You may disable analytical tracking variables through specialized browser add-ons or by refusing analytical cookies at the introductory prompt. Opting out from analytics has no negative impact on user profiles or dashboard performance.

C) Third-Party Opt-Outs

Our enterprise partners provide distinct control dashboards to adjust data settings independently:

D) Do Not Track (DNT)

Many contemporary web browsers offer a "Do Not Track" ("DNT") feature to indicate online tracking opt-outs. Because of the lack of industry-wide technical standards, bldhub.us does not change its background operations in response to active DNT browser flags. This stance is reviewed systematically as international regulations develop.

E) Consent for Non-Essential Cookies

Upon opening bldhub.us, your terminal receives a clear legal notice explaining that strictly necessary cookies require no consent. Non-essential tracking mechanisms (such as functional presets and analytical collectors) are disabled until the user consents or continues navigating the Platform. You may retract active consents at any time by clearing your browser cache.

7. INTERNATIONAL USERS & GDPR AWARENESS

Bldhub is organized, maintained, and served out of offices located in Austin, Texas, USA. Users accessing our databases and rendering tools from jurisdictions such as the European Union (EU), the European Economic Area (EEA), or the United Kingdom (UK) must recognize that tracking cookies will be evaluated under the GDPR and ePrivacy Directive frameworks.

Under GDPR guidelines, our lawful bases for tracking are:

  • Legitimate Interests & Contractual Performance: Applies to strictly necessary cookies to protect logins, authenticate sessions, and track payment checks.
  • Explicit User Consent: Applies to performance metrics and analytical cookies, which are disabled by default until the user gives consent.

International visitors have the right to request comprehensive data summaries, challenge tracking profiles, and request the complete erasure of stored cookie records. For GDPR inquiries and official data requests, please write to our technical counsel at legal@bldhub.us.

8. CHILDREN & COOKIES

Bldhub is designed for industry professionals, developers, and adult property owners. We do not knowingly compile cookie registries, active device details, or biographical indicators from individuals under eighteen (18) years of age.

If our system administrators become aware that a minor under 18 has established an account or left persistent tracking logs on our server, we will act immediately to disable the profile and clear all associated cookie data. Parents or guardians who observe unauthorized profile creation are requested to email legal@bldhub.us instantly.

9. UPDATES TO THIS COOKIE POLICY

Meraki Architecture LLC retains the right to modify or adjust this Cookie Policy at our discretion to keep pace with changing privacy laws, browser configurations, and platform layouts.

If material updates are compiled into this policy, our team will deliver a notice via introductory banners or emails. All revisions require a minimum of fourteen (14) calendar days of notice before going into effect. Your subsequent use of bldhub.us following the effective date confirms your consent to the revised terms.

10. CONTACT

If you have questions regarding this Cookie Policy or wish to assert statutory privacy privileges under the TDPSA or GDPR, please contact our legal team:

  • Legal Team Representative: legal@bldhub.us
  • General Support Services: support@bldhub.us
  • Corporate Address: Meraki Architecture LLC, 5900 Balcones Drive, Ste 100, Austin, TX 78731