Privacy Policy
This is a courtesy translation. The Traditional Chinese version prevails.
Version Date: 2026-10-06 / Last Updated: 2026-10-06
Data We Collect
- Browsing this site does not require sign-in. LINE or Google sign-in is required only to use Rider Reports (see "Rider Reports and Sign-In" below). Otherwise, we do not collect names, email addresses, phone numbers, or location data.
- We use Google Analytics 4 to measure visitor counts, viewed pages, and device types to improve the site. Google processes and stores analytics data under its Privacy Policy. We view aggregated reports only and cannot identify individual visitors from them.
- Nearby: Your browser uses your location only on your device to calculate distances. It is not sent to or stored by this site. Only your selected distance (30/50/100 km) is saved.
Rider Reports and Sign-In
- Sign-In: After you authorize LINE or Google sign-in, we receive only an account identifier, convert it into a pseudonymous ID using cryptographic hashing, and store that ID. We do not receive or store your name, profile picture, email, or phone number. Signing in with LINE and Google creates two different IDs.
- Your pseudonymous ID, reputation score, and score change log (type and time) are kept until you delete them or are automatically deleted after 12 months of inactivity.
- Reports (category, details, coordinates, route and kilometer marker, time, confirmation count, and whether map marking was used) are deleted 7 days after closure. Other riders' +1/-1 confirmations are deleted with each report.
- Records of incorrect map-based reports are kept for 30 days. Three such reports within 30 days trigger a 5-day suspension of map marking. Suspension records are deleted when they expire.
- Publicly visible data includes report category, location, time, number of confirmations, and the reporter's reputation badge. Pseudonymous IDs and LINE/Google account details are not shown.
- Location: When submitting or confirming a report, your browser sends your current location to the server solely to verify distance (reports must be within 2 km of you, or 5 km for map-marked reports; confirmations within 5 km count as a full vote, while more distant confirmations or those without location count as partial votes). The location is not stored.
- Bot Verification: We use Cloudflare Turnstile when reports are submitted. Cloudflare processes verification data under its Privacy Policy.
- Deletion: From My Reports & Data, you can sign out or permanently delete your ID, reputation score, reports, and confirmation history. Deleted data cannot be recovered.
Road Condition Push Notifications
- When you enable "🔔 Notify Me" on a route page, we store the browser-provided push endpoint and encryption keys, your selected routes and event categories, and your nighttime alert preference. No sign-in is required, and this subscription is not linked to your Rider Reports ID.
- Notification content is encrypted and delivered to your device through your browser's push service (Google, Apple, Mozilla, or Microsoft).
- Select "Turn Off Alerts for This Route" or "Turn Off All Notifications" to delete subscriptions. They are also removed automatically if you disable notifications in browser/device settings or if the push endpoint expires.
Suggestions & Issue Reports
- When you submit a suggestion or issue report, we store the selected category and route, your message, the page you came from, and optional contact details. No sign-in is needed, and IP addresses are not recorded.
- Submissions are transferred to the site owner's private task list (a nonpublic GitHub Issue). Contact details are used only to respond. Database entries are deleted 30 days after transfer.
- "Request Status" displays only titles rewritten by the site owner and their progress, not your original message or contact details. To request deletion, email us the submission time and content.
Cookies & Browser Storage
- Google Analytics uses cookies beginning with _ga and an anonymous device identifier. To opt out, install the Google Analytics Opt-out Browser Add-on or block cookies in your browser. This does not affect site functions.
- After signing in for Rider Reports, we set a sign-in cookie (or_s, valid for 30 days). During sign-in, a temporary cookie (or_o, valid up to 10 minutes) prevents forged sign-ins and allows completion in the original screen after LINE verification opens another browser. Corresponding server-side temporary records are deleted within 1 hour. Signing out deletes the sign-in cookie.
- Favorite routes, recent pages, dark/light mode, travel direction and vehicle selections, acceptance of reporting terms, IDs of reports you've submitted or confirmed, routes with notifications enabled, and cached last-successful road-condition data are stored only in your browser's localStorage and not sent to this site. Previously viewed pages (up to about 40) may be cached for offline use. Clearing site data in your browser removes them.
Third-Party Content
- Your browser loads camera images and YouTube streams directly from their providers, which handle connection data under their own policies. YouTube embeds use privacy-enhanced mode (youtube-nocookie.com). Route map tiles load from OpenStreetMap only after you select "Show Map."
Policy Changes
- If we introduce advertising or change the collection or retention practices described above, we will update this page and its version date first.