Privacy Policy

This page describes how the Bright Bridge Web website handles information. The final wording is under attorney review; the structure and the verified facts behind it are shown below.

1. Scope

[LEGAL-COPY — attorney review required]

  • Counsel must identify the legal business entity behind Bright Bridge Web. The formal entity name has not been verified and must not be guessed.
  • Counsel must state which websites and properties this policy covers.
  • Effective date and last updated date are required before publication.

2. Information We Collect

Information visitors submit directly

[LEGAL-COPY — attorney review required]

Verified implementation facts for review

  • Fields actually deployed on the contact forms today: name, email, company/organization, project or service interest, and a free-form message.
  • The longer contact form additionally collects an existing website URL, timeline, and budget range.
  • No other fields (phone number, lead-magnet requests, file uploads) exist on the deployed forms today. Final language must match the fields live at launch.

Text-message consent

[LEGAL-COPY — attorney review required]

Verified implementation facts for review

  • No SMS consent checkbox exists on the deployed forms today, and no SMS functionality is enabled.
  • If texting is added, consent must be unchecked by default and must never be a condition of contacting Bright Bridge. Until then, no SMS language may be published.

Automatically collected technical information

[LEGAL-COPY — attorney review required]

Verified implementation facts for review

  • Site audit result: no analytics scripts, no cookie writes, and no local-storage writes are present in the application code today.
  • Hosting-level request logs (IP, referrer, user agent) may exist at the platform layer; the hosting provider's actual logging must be confirmed for counsel.
  • No advertising cookies, Google Ads remarketing, Meta Pixel, affiliate tracking, or behavioral advertising are deployed. None of these may be described in the policy unless they are actually added.

3. How Information Is Used

[LEGAL-COPY — attorney review required]

  • Counsel confirms which uses apply. Candidates limited to actual operations: responding to inquiries, preparing estimates and proposals, delivering requested resources, operating and improving the website, communicating about an active request, security and fraud prevention, and legal obligations.
  • No secondary marketing uses may be added unless they reflect real practice.

4. Service Providers / Data Processors

[LEGAL-COPY — attorney review required]

Verified implementation facts for review

  • Implementation check performed: the site has no Supabase (or other database) integration, and contact form submissions are not persisted or transmitted anywhere by the application today — the form is UI-only.
  • If form delivery, storage, or a CRM is enabled before launch, that processor must be added to counsel's review.
  • Vendors still to be confirmed and disclosed as applicable: hosting provider, email provider, analytics provider, CRM, SMS provider, form-processing provider. No vendor name may be published until verified.

5. Cookies & Analytics

[LEGAL-COPY — attorney review required]

Verified implementation facts for review

  • Cookie and storage inventory of the application code: zero cookies set, zero local-storage or session-storage items written, zero analytics scripts loaded.
  • There is therefore no non-essential tracking running before consent, and no consent-management system is required at present.
  • If only essential/session behavior and basic analytics are ever added, the final policy should describe that simpler reality rather than a generic tracking regime.

6. Email Practices

[LEGAL-COPY — attorney review required]

  • Transactional and request-related communication only, unless marketing email is actually operated.
  • No newsletter language may be published unless a newsletter genuinely exists. Unsubscribe mechanics apply only where legally and operationally relevant.

7. Data Retention

[LEGAL-COPY — retention practices must be confirmed]

8. Data Security

[LEGAL-COPY — attorney review required]

  • No absolute security promises. Language such as "your data is completely secure" or "we guarantee security" must not appear.

9. Privacy Rights

[LEGAL-COPY — applicable privacy rights and request process]

  • Counsel determines which privacy regimes actually apply. Do not assume Bright Bridge is subject to every state or international privacy law.

10. Children's Privacy

[LEGAL-COPY — attorney review required]

  • Age thresholds and compliance claims come from counsel, not from a template.

12. Changes to This Policy

[LEGAL-COPY — attorney review required]

  • Effective date: [PENDING]
  • Last updated: [PENDING]
10 Start here

What are you trying to build, fix, or hand off?

Choose the closest option. You don't need to know which Bright Bridge service you need — that's our job.

Step 1 of 2 · A few essentials
Your request stays with Bright Bridge so we can route it to the right person.

Powered by