Compliance

Location Permissions

HeavyCivilHelper accesses your device's location only when you choose to use a location-based feature, such as "My Location" on a project map. We do not access your location at app launch or while the app is running in the background.

You can deny or revoke location permission at any time through your browser or device settings. Some map features may not work without this permission.

Locations, map pins, and project boundaries that you intentionally add to a project are stored as project data and are separate from your device's location permission.

How Location Is Used

• Centering the map on the user's current position ("You Are Here" indicator)
• Placing a custom pin or record pin at the user's current location
• Pre-filling the starting point in the Route Planner

A single one-time position fix is retrieved for these features on mobile. On web, the position is watched continuously only while the "My Location" button is active, and stops immediately when deactivated or the page is closed.

Data Handling

• Not stored server-side automatically. Raw GPS coordinates are never logged or retained by HeavyCivilHelper servers except when a user explicitly saves a pin or record with a location they have chosen to attach. Those saved coordinates are stored as part of the user's project data.
• Not shared with third parties. Location data is not sold, rented, or shared with advertisers or analytics providers. Map tile imagery is fetched from OpenStreetMap, Esri, Mapbox, and similar providers; device coordinates are not transmitted to those providers as part of normal tile requests.
• No movement logging. The platform does not record location history, movement paths, or time-stamped position logs. Each position read is a discrete, on-demand operation with no persistence beyond the current session.

Revoking Permission

• Web: Open browser site settings for heavycivilhelper.com and set Location to "Blocked." Alternatively, tap the location button on the map to stop the active session.
• iOS: Settings → Privacy & Security → Location Services → HeavyCivilHelper → set to "Never."
• Android: Settings → Apps → HeavyCivilHelper → Permissions → Location → set to "Deny."

Revoking permission disables location-dependent features but does not affect access to any other part of the platform.

Our Commitment

HeavyCivilHelper is committed to making its platform accessible to users of all abilities, including those who rely on assistive technology such as screen readers, keyboard-only navigation, and voice control software. We believe construction project management tools should be usable by every member of a field team, regardless of disability.

We work toward conformance with the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA, published by the World Wide Web Consortium (W3C). WCAG 2.1 AA is the standard referenced by the Americans with Disabilities Act (ADA), Section 508 of the Rehabilitation Act, and most state and local government procurement requirements.

What We Have Done

• Implemented a "Skip to main content" link on every page so keyboard users can bypass navigation.
• Used semantic HTML landmarks — header, main, nav, footer — throughout the application.
• Labeled all navigation regions with aria-label attributes so screen readers can distinguish between navigation areas.
• Provided descriptive alt text on all meaningful images; decorative images are marked with empty alt attributes.
• Added scope="col" attributes to all data table headers so screen readers can associate columns with their headings.
• Made all interactive controls operable by keyboard, including table row selection via Enter and Space keys.
• Used Radix UI dialog primitives for all modal windows, which handle focus trapping, aria-modal, and focus restoration automatically.
• Added autocomplete attributes to all login, registration, and password recovery form fields.
• Supported both light and dark mode to accommodate users with light sensitivity or low-contrast needs.
• Used sufficient color contrast ratios across text and interactive elements.

Known Limitations

• Interactive map. The project map uses Leaflet, a pointer-based interactive mapping library. The map canvas cannot be fully navigated by keyboard alone. This is a known limitation of interactive web mapping technology. All data visible on the map — RFIs, directives, change orders, submittals, and survey requests — is fully accessible through the Records section, which is completely keyboard and screen reader accessible.
• Plan overlay viewer. The full-screen plan sheet viewer is a canvas-based interface for viewing and annotating PDF plan sheets. Navigation within a plan sheet requires pointer input. All records pinned to a plan sheet remain accessible through the Records section.

Reporting Accessibility Barriers

If you encounter an accessibility barrier while using HeavyCivilHelper, please contact us. We take all reports seriously and aim to respond within 5 business days.

Email: [email protected]

Please include a description of the barrier, the page or feature involved, and the assistive technology or browser you are using. This helps us reproduce and resolve the issue efficiently.