1. Current preview and future participation
Community is currently a local preview for signed-in adult riders. Sample posts are fictional. Drafts, followed communities, and report/block/mute/review actions remain on the device. Saving a draft or marking an item for review does not publish it or notify a moderator. Live posting and rider messaging remain disabled. These Guidelines describe the standards for any later live launch as well as appropriate use of the preview. They do not announce that live moderation already operates.
2. Respect, age, and truthful identity
Participation is for people 18 or older. Be civil, even when disagreeing. No threats, targeted harassment, hateful attacks, stalking, sexual exploitation, explicit sexual material, encouragement of self-harm, scams, or intimidation. Do not impersonate a person or business, invent credentials, evade a suspension, or use alternate accounts to continue unwanted contact. A public username is allowed; it must not misleadingly claim to be an official, professional, or another rider.
Honest reviews and good-faith criticism are welcome. Describe your own experience accurately, separate opinion from fact, and do not fabricate allegations or organize harassment of someone you dislike.
3. Post in the right community with useful details
Select the community before composing. Complete the fields for the post type and check the information before any live submission. Unfinished drafts can be saved locally.
- Ride: include date, start time, public meeting location/name, city, address, skill level, route/pace expectations, and relevant ride details. State the local time zone when ambiguity is possible.
- Bike Meetup: include date/time, public venue, city/address, skill expectations, venue permission, and what attendees should expect.
- Local Alert: identify the alert category, public road/area, city, when observed, and factual details. Correct or remove outdated information. An alert is not an official emergency or police report.
- Mechanic lead: identify the mechanic/shop, city, service/specialty, publicly available business contact, and the basis of your recommendation. Disclose employment, ownership, payment, or other relevant connections.
- Question: select a topic and ask a clear question with relevant context, excluding private identifiers.
- Shoutout: identify the rider’s username or business and describe the experience honestly; disclose a commercial connection.
4. Ride and meetup responsibilities
Organizers must give accurate information, obtain appropriate venue permission, comply with permit and other legal requirements, and communicate material changes or cancellations. Riders must assess their own ability, motorcycle condition, licensing, protective equipment, weather, and the planned route. Do not pressure anyone to keep up, perform stunts, ignore traffic rules, or ride while impaired. “Beginner,” “Intermediate,” “Advanced,” and “All levels” are self-described expectations, not verified qualifications.
Meet initially in an appropriate public place. Tell a trusted person your plans and leave if you feel unsafe. A post does not mean Motorcycle Bible hosts, supervises, insures, screens, or endorses the event or its participants. Do not rely on the app for rescue, roadside dispatch, live location tracking, or attendance verification.
5. Protect personal information
Do not post private home addresses, full VINs or plates tied to a person, insurance/policy information, identification documents, private phone numbers, account credentials, or private messages without authority. Public event venues and publicly listed business contact information are appropriate when relevant. Obtain permission before identifying another person in content. Do not expose a theft victim’s sensitive records or encourage identifying and confronting a suspected offender.
Anything deliberately published can be copied or redistributed. “Private” profile fields do not protect information you separately type into a public post. Local drafts can be seen by someone with access to the same app/browser storage. Read the Privacy Policy before entering sensitive details.
6. Dangerous conduct, spam, and commercial content
No illegal street racing, road takeovers, reckless challenges, instructions to evade law enforcement, unlawful emissions tampering, stolen-goods trading, malicious links, or dangerous instructions presented as guaranteed safe. Do not coordinate violence, vigilantism, discrimination, or unlawful activity. No unsolicited bulk advertising, deceptive affiliate links, fake reviews, undisclosed paid recommendations, or sales of prohibited goods. Community is not an escrow service or payment guarantee. Verify businesses and use appropriate independent payment protections.
Do not upload copyrighted material you lack permission to share. Summarize advice in your own words and cite legitimate sources where helpful; do not repost service manuals or private communications in full without rights.
7. Reporting, blocking, and emergencies
In an immediate emergency in the United States, call 911. Support and Community reports are not emergency channels and are not continuously monitored. Do not wait for an app response before seeking help. For a nonurgent concern, email support@motorcyclebible.com with the relevant post reference or description, community, approximate date, and reason. Include only necessary information.
Current preview report/block/mute controls save a local demonstration of the action; they do not initiate an investigation or protect you from contact elsewhere. Before live posting launches, usable reporting, blocking, content filtering, and a staffed moderation process must be in place. Future controls will be described in the product when actually available.
8. Moderation and requests for review
For a live service, the operator may review reports, request context, restrict visibility, remove violating content, temporarily restrict functions, or suspend accounts as reasonably needed. Serious safety issues, exploitation, fraud, repeat violations, or legal obligations may require immediate action. Outcomes depend on context; approval or lack of removal is not a certification of accuracy or safety. No guarantee of reviewing every item before anyone sees it is made.
You may ask support to review a decision by describing the action and why you believe it was mistaken. Do not evade restrictions while a request is pending. Records may be retained for the purposes explained in the Privacy Policy. These Guidelines do not prevent lawful complaints, truthful reviews, or cooperation with authorities. Changes require updated notice as appropriate.