Introduction And Scope
This Privacy Policy explains how BridgeWatch collects, uses, discloses, retains, and otherwise processes information when you access or use the BridgeWatch website, mobile application, account system, bridge-status services, camera views, notifications, donation or subscription flows, and related features, content, and support interactions.
This policy applies to information BridgeWatch processes directly through its own website, application, APIs, databases, and backend systems. Third-party platforms and vendors such as app stores, payment processors, camera-feed operators, mapping providers, hosting providers, notification delivery providers, and telecommunications carriers may also process information under their own terms and privacy notices.
This Privacy Policy is intended to describe BridgeWatch’s current data practices based on the product functionality reflected in the available codebase and related service flows as of June 12, 2026. If BridgeWatch later adds materially different data practices, this policy may be updated accordingly.
Categories Of Information We Collect
BridgeWatch may collect identifiers and account data that you provide or that are generated in connection with your use of the service, including name, email address, account identifier, authentication records, hashed password credentials, profile updates, and associated account timestamps such as creation or last-login dates.
BridgeWatch may collect device and notification configuration data such as push notification token, device name, platform, timezone, selected bridges, alert timing preferences, sound and vibration settings, bridge-specific notification settings, nearby-alert preferences, and device registration timestamps.
If you enable location-aware features, BridgeWatch may process geolocation data, including latitude, longitude, and configured proximity radius values, to determine whether a device is near a monitored bridge and whether a requested alert should be delivered.
BridgeWatch may collect transactional and service-interaction information, including log-in events, refresh and revocation token records, notification delivery records, bridge alert events, bridge status history, support communications, product configuration values, and similar operational records necessary to run, secure, maintain, and improve the service.
BridgeWatch may also receive limited payment-related context from third-party billing or checkout providers, such as whether a donation or subscription checkout was initiated or linked to a user account, but BridgeWatch does not state that it stores full payment card numbers because payment processing may be handled by third-party providers rather than directly by BridgeWatch.
Sources Of Information
BridgeWatch collects information directly from you when you create an account, update your profile, sign in, configure alerts, enable notifications, enable or disable location permissions, contact BridgeWatch, or otherwise interact with the website or app.
BridgeWatch also receives information automatically from your device, browser, application instance, or hosting environment, such as authentication events, push token registrations, service logs, request metadata, and technical events generated as part of normal service operation.
BridgeWatch may receive information from third-party partners or service providers, such as app stores, payment providers, hosting platforms, traffic-camera or bridge-data sources, notification providers, and similar vendors that support the service.
How We Use Information
BridgeWatch uses information to create and administer accounts, authenticate users, provide bridge-status information, operate live-feed and camera-related features, send requested alerts, support bridge-specific and proximity-based notification logic, manage optional donation or subscription flows, and respond to support requests, legal requests, and security incidents.
BridgeWatch uses information to maintain service quality, troubleshoot technical problems, improve bridge prediction quality, prevent abuse, monitor reliability, enforce applicable terms, verify user requests, and maintain accurate operational records.
Where location-aware alerts are enabled, BridgeWatch uses location data to determine whether you are near a selected bridge and to reduce notifications that may be irrelevant based on your configured proximity settings.
BridgeWatch may use aggregated, anonymized, or de-identified information for analytics, testing, service monitoring, research, and product improvement, provided that BridgeWatch does not attempt to reidentify properly de-identified information except as permitted by law.
Legal Bases For Processing
BridgeWatch processes information when necessary to provide requested services, perform a contract or pre-contractual relationship with users, comply with applicable legal obligations, protect the security and integrity of the service, pursue legitimate operational interests such as maintenance and product improvement, and, where required by law, based on your consent or device-level permissions.
Examples of consent-based or permission-based processing may include enabling push notifications, authorizing location access, or initiating certain third-party payment or checkout flows. You can generally manage these permissions through your device settings, account settings, or the applicable third-party platform.
Disclosures And Sharing Of Information
BridgeWatch may disclose information to service providers, processors, contractors, and infrastructure partners that perform services on BridgeWatch’s behalf, such as hosting, database administration, authentication support, notification delivery, payment processing, email handling, security operations, and customer support administration.
BridgeWatch may disclose information to third-party platforms or providers when you choose to use features that depend on them, such as app-store purchases, third-party payment providers, map providers, or public camera and data sources.
BridgeWatch may disclose information to regulators, courts, law enforcement, government authorities, or other parties when BridgeWatch believes disclosure is reasonably necessary to comply with law, protect rights or safety, investigate fraud or misuse, respond to legal process, or enforce this Privacy Policy or related agreements.
BridgeWatch may disclose or transfer information in connection with a proposed or actual merger, acquisition, financing, restructuring, bankruptcy, sale of assets, or similar corporate transaction, subject to applicable confidentiality and legal requirements.
Sale, Sharing, Advertising, And Sensitive Data
Based on the data practices reflected in the current codebase and known service configuration, BridgeWatch does not state that it sells personal information for money and does not state that it shares personal information for cross-context behavioral advertising.
BridgeWatch may process sensitive data, including precise geolocation information, when users choose to enable nearby-bridge alerts or similar location-aware functionality. BridgeWatch uses that information for limited service purposes tied to the requested feature and not for unrelated profiling or advertising purposes as reflected in the current codebase.
If BridgeWatch’s advertising, sharing, or sensitive-data practices materially change in the future, BridgeWatch may provide any additional notices, choice mechanisms, or rights disclosures required by applicable law at that time.
Cookies, Similar Technologies, And Automated Technical Data
BridgeWatch may use browser storage, app storage, session technologies, API tokens, or similar technical mechanisms that are reasonably necessary to keep the website or application functioning, maintain authenticated sessions, remember settings, support security controls, and deliver requested features.
Like most online services, BridgeWatch and its hosting or delivery infrastructure may automatically receive technical information such as IP address, browser or device type, request timestamps, request paths, referrer data, crash data, and similar diagnostic or server-log information when users access the service.
This policy does not claim that BridgeWatch currently uses third-party advertising cookies or web-based behavioral tracking tools unless and until such tools are actually implemented and disclosed in an updated notice.
Retention Of Information
BridgeWatch retains personal information for as long as reasonably necessary for the purposes described in this Privacy Policy, including to provide the service, preserve security records, troubleshoot incidents, comply with law, maintain business and tax records, enforce agreements, and resolve disputes.
Different categories of information may be retained for different periods. For example, authentication records, account records, push registration records, alert settings, notification logs, and bridge-status operational records may be retained for periods that differ based on operational need, legal obligations, backup cycles, and security requirements.
When BridgeWatch no longer reasonably needs personal information for the purposes described in this Privacy Policy, BridgeWatch may delete, aggregate, anonymize, or de-identify the information, unless retention is otherwise required or permitted by law.
Security
BridgeWatch uses measures intended to protect information against unauthorized access, disclosure, alteration, and destruction. These measures may include access controls, credential protections, role-based restrictions, token revocation mechanisms, logging, vendor security features, and other administrative, technical, and organizational safeguards that BridgeWatch considers reasonable in light of the nature of the information processed.
No security program is perfect, and BridgeWatch cannot guarantee absolute security or uninterrupted confidentiality. Users are responsible for safeguarding their devices, protecting credentials, using secure networks where appropriate, and notifying BridgeWatch if they believe their account or device has been compromised.
Your Rights And Choices
Depending on where you live and subject to applicable law, you may have rights to request access to personal information, request deletion, request correction of inaccurate data, request a portable copy of certain data, request information about categories of data collected or disclosed, opt out of certain sales or sharing if such practices occur, limit certain uses of sensitive personal information, appeal a denied request, or withdraw consent where BridgeWatch relies on consent.
BridgeWatch may take reasonable steps to verify your identity before fulfilling a privacy request and may decline or limit requests where permitted by law, including where an exception applies, where the request cannot be verified, where fulfilling the request would adversely affect the rights of others, or where the information is required for security, legal, tax, compliance, fraud-prevention, or other protected purposes.
You may also manage certain data practices directly through product settings or device controls, including updating account details, disabling notifications, revoking location permissions, changing alert radius settings, removing a device registration, or discontinuing use of the service.
U.S. State Privacy Notices
For residents of states with comprehensive privacy laws, including California and other applicable U.S. states, BridgeWatch intends this Privacy Policy to serve as a general notice of collection and privacy practices. BridgeWatch may collect categories of information that include identifiers, account credentials, device data, precise geolocation when enabled, internet or network activity records, and other operational records described above.
As reflected in official California privacy guidance, consumers may have rights to know the categories and specific pieces of personal information collected, the categories of sources, the business or commercial purposes for collection, the categories of recipients, the right to request deletion, the right to request correction, the right to limit certain uses of sensitive personal information, and the right not to be discriminated against for exercising protected privacy rights.
If BridgeWatch becomes subject to additional state-specific disclosure, response, or opt-out requirements beyond what is reflected in the current product configuration, BridgeWatch may supplement this policy with additional notices or request procedures.
Children’s Privacy
BridgeWatch is not directed to children under 13 and is not intended to knowingly collect personal information from children under 13. The Federal Trade Commission enforces the Children’s Online Privacy Protection Act, which places parents in control of personal information collected from children under 13.
If BridgeWatch learns that it has knowingly collected personal information from a child under 13 without legally sufficient authorization, BridgeWatch will take commercially reasonable steps to delete that information as required or permitted by law. Parents or guardians who believe a child has provided information to BridgeWatch may contact BridgeWatch using the information below.
International And Cross-Border Processing
BridgeWatch is based in the United States, and information may be stored or processed in the United States or other jurisdictions where BridgeWatch, its vendors, or its service providers maintain operations. Data-protection laws in those jurisdictions may differ from the laws of your place of residence.
By using BridgeWatch where permitted by law, you acknowledge that information may be transferred to and processed in jurisdictions outside your state, province, or country, subject to applicable legal safeguards.
Changes To This Privacy Policy
BridgeWatch may update this Privacy Policy from time to time to reflect changes in the law, the service, product features, data practices, or business operations. The version posted on this page is the current version unless a later effective date is stated.
Material changes may be communicated by posting the updated notice on the website, updating the effective date, or using another method that BridgeWatch believes is reasonably appropriate under the circumstances.
Contact Information
Privacy requests, legal notices relating to privacy, and policy questions may be sent to legal@charlestonbridgewatch.live.
Requests should include enough information for BridgeWatch to identify the relevant account, device, or request context and to verify the requester’s authority where necessary.
