Useful route information. Fewer personal details.

What a report contains.

A report stores the selected site and pathway segment, a barrier category, your plain-text description, a generated reference, a timestamp, and its review status. A moderator can add internal review notes and a review timestamp.

Report descriptions and statuses may be displayed publicly. Moderator notes and authentication secrets are not part of the public report view. Do not submit names, contact details, diagnoses, home addresses, school IDs, or information about another person.

Location is your choice.

GPS permission is requested only when you choose a location or live-guidance button. Camera, microphone and photo uploads are not requested. The demo uses a schematic map with no external tile requests. There is no advertising tracker or visitor analytics integration in the application.

The hosting provider may process request and infrastructure logs under its own policies. This app’s report and rate-limit records do not store visitor IP addresses or device identifiers.

When you start live guidance.

Your browser supplies position and accuracy while the page is open. The moving position stays in this tab, is not recorded as location history, and tracking stops when you press Stop, leave the planner, or close the page. If you enable automatic recalculation, an off-route point and destination are sent to AccessPath and the routing service, at most once every 45 seconds. Low-accuracy or stale fixes do not trigger automatic rerouting. Browser and phone restrictions can suspend guidance in the background.

Access-aware routing sends a bounded map area to the Private.coffee Overpass service (terms and privacy) to read OpenStreetMap pathway tags. The downloaded map is temporarily cached for up to ten minutes; no travel history is stored. Map tiles reveal the viewed area to the tile provider. Optional spoken prompts use your browser or operating system’s voice service.

Real-place obstacle reports are public.

Before submitting, you must confirm that the selected obstacle coordinates and description will be public. The report stores its category, radius, timestamp, review status and seven-day expiry. Report public pathways only; do not include a person, medical information, contact details or a private address. Only reviewed, active reports affect access-aware street routing. Pending observations remain unverified. Expiry removes a report from active map avoidance, not automatically from database retention.

When you use real-world routing.

The real-world planner loads street tiles from OpenStreetMap, which receives your network request and the map area being viewed. Pressing Search sends the entered place name or address through this server to Photon. Calculating a walking route sends the two selected coordinates to FOSSGIS’s routing server. Wheelchair planning sends the endpoints and reviewed obstacle-avoidance areas to HeiGIT/openrouteservice; its key stays server-side. These providers can log requests under their own policies.

Searches are sent only when submitted, with no automatic search-as-you-type requests. This application uses bounded temporary server-memory caches (up to ten minutes for place results and five minutes for routes), but does not save your search text or journey in the reports database. Shared quota records store only provider names and counters. Server and provider infrastructure logs are separate from these application records.

Opening the Google Maps link shares the selected endpoints with Google, which calculates its own walking directions. Google is not contacted by that link until you open it. No Google account, paid API key, or GPS access is required by AccessPath.

Photon service information · FOSSGIS routing and privacy information · OpenStreetMap Foundation privacy policy

Your saved maps and routes.

Saving a route stores its name, tags, favorite status and endpoints in this browser’s local storage. Street routes also keep a dated copy of their line and written directions; campus routes keep the chosen scenario and filters. These saved journeys are not uploaded to the reports database or synced across devices.

Anyone using the same browser profile may see them. You can remove individual routes from Saved routes; clearing site data removes the whole library. Opening a saved street map still requests online map tiles. Recalculating deliberately sends the endpoints to the routing provider again. Saved routes do not establish current conditions or verified accessibility.

Storage and review.

Local development stores reports in a SQLite database. A serverless deployment needs configured remote persistent storage. If storage is unavailable, the app must say the report was not saved rather than give a false confirmation.

Anonymous reports start pending. Administrator review uses a server-checked session cookie; this cookie is required only for moderation. Approving a report is not a complete accessibility verification.

The prototype has no automatic report-deletion schedule or public deletion portal. Reports remain until the operator removes them from the database. Before collecting real community reports, the operator needs a published contact and retention/removal process. The current environment is for synthetic demonstration reports.

Check what the prototype actually knows.

Our evidence record separates synthetic pathway data and stored reports from real surveys or impact research. Real campus data is not yet supplied.