Terms of Service

1. What the Service does

The Service lets Waze Map Editors submit downlock, uplock, imagery, and permissions-request (PUR) requests from inside the Waze Map Editor via a browser userscript, view and track those requests on a dashboard, and — for admins — route them to configured notification channels (Slack, Discord, Telegram, email, and others; see our Privacy Policy for the full list).

2. Accounts

• Dashboard accounts are provisioned or invited by an existing admin — there's no public sign-up.
• You're responsible for keeping your login credentials confidential and for all activity under your account.
• If you configure a notification channel with your own third-party credentials (a webhook URL, bot token, service-account key, or email credential), you're responsible for that credential's validity, scope, and compliance with the relevant third party's own terms.
• We may suspend or remove an account that violates these terms or is used to abuse the Service.

3. Acceptable use

You agree not to:

• Submit false, misleading, or spam requests, or otherwise abuse the request-submission endpoint.
• Attempt to bypass or defeat bot-verification (Cloudflare Turnstile) or rate limits.
• Use the Service to harass, defame, or collect data about other editors beyond what it's designed to show.
• Attempt to gain unauthorized access to accounts, data, or infrastructure of the Service.
• Use the Service in a way that violates Waze's or Google's own terms of service.

4. Content you submit

When you submit a request (including any notes, screenshot, or permalink), you grant the Service a license to store, process, and forward that content to the notification channels an admin has configured for the relevant country or region, and to display it on the dashboard and public request feed/RSS. You're responsible for making sure content you submit doesn't infringe anyone else's rights or violate applicable law.

Request records are automatically and permanently deleted 24 hours after submission. Any decision or notification you want to keep a record of should be captured elsewhere (e.g. the notification channel it was routed to) before that window closes.

5. Third-party services

The Service runs on Cloudflare (Workers, D1, R2, Turnstile) and uses PostHog for analytics; admins may additionally connect Slack, Discord, Telegram, Google, Postmark, Mailgun, SMTP, ntfy, or Gotify. Your use of any such integration is also subject to that third party's own terms — we don't control, and aren't responsible for, their availability, content, or practices. See our Privacy Policy for details on what's shared with each.

6. Availability and disclaimer

The Service is provided "as is" and "as available," without warranties of any kind, express or implied, including fitness for a particular purpose or uninterrupted availability. We don't guarantee that a notification will be delivered successfully by a third-party channel, or that the Service will always be available or error-free.

7. Limitation of liability

To the fullest extent permitted by law, the Service and its operator won't be liable for any indirect, incidental, or consequential damages arising from your use of, or inability to use, the Service — including missed or delayed notifications, lost data, or map-editing decisions made based on information shown by the Service.

8. Changes

We may update these terms or the Service itself at any time. Material changes will be reflected by updating the effective date above. Continuing to use the Service after a change means you accept the updated terms.

9. Contact

For questions about these terms, email wazer@wazetools.com.