Safety

Plain-language safety principles for a real enthusiast platform

Drivurs is built to support clearer coordination, calmer communication, and better decisions around events, communities, and performance data. It is not a substitute for judgment, local laws, or emergency services.

  • Events
  • Lawful driving
  • Reporting
  • Controlled environments

Events

Event participation principles

The safest event workflow is the one that removes ambiguity before the day gets chaotic.

Start with clarity

  • Post location, timing, meet rules, and visibility clearly
  • Make host, co-host, and marshal roles obvious when applicable
  • Use the same source of truth for changes instead of scattering updates across channels

Respect venues and local context

  • Use spaces that can handle the event you are organizing
  • Respect venue instructions, neighbors, and local laws
  • If a venue or property owner asks people to leave, leave calmly and regroup elsewhere only if it is lawful and safe to do so

Driving expectations

Lawful driving and phone-use expectations

Drive first

Drivurs should not be used in a way that encourages distracted driving. Drivers should not interact with phones or app workflows while the vehicle is in motion except as allowed by law and handled safely through passengers or lawful hands-free setups.

No reckless or illegal coordination

Do not use Drivurs to organize dangerous driving, street racing, or other unlawful activity. Clear event coordination is not a license to ignore road rules, venue rules, or common sense.

Performance data

Telemetry belongs in controlled environments

Performance and telemetry features should be used for track days, sanctioned events, and other lawful, controlled environments where drivers can focus on setup, consistency, and validation.

Drivurs does not present RaceBox-supported timing or other performance review as a public-road competition tool. The value is in repeatable data and honest context, not reckless behavior.

Reporting

Reporting and moderation pathways

If the issue is on Drivurs

  • Use in-product reporting tools when they are available for the workflow you are in
  • Include screenshots, links, usernames, event names, and context when you email support
  • Use support@drivurs.com for harmful content, organizer abuse, or safety-related platform concerns

What to expect

  • We review reports to understand context and determine whether action is appropriate
  • Possible outcomes can include content removal, restrictions, or account action where warranted
  • Reporting helps, but Drivurs does not monitor or protect users in real time

Urgent situations

Immediate danger requires local emergency services

If someone is in immediate danger, contact local emergency services first. Do not rely on Drivurs messages, support email, or in-product reporting for urgent emergency response.

Drivurs is not emergency response infrastructure. After the situation is safe and the appropriate authorities have been contacted, you can email support@drivurs.com with the relevant platform details.