Trust & privacy

Built for communities where trust already matters.

RideSmart gives coordinators useful tools without taking control away from the people responsible for their members, volunteers, and transportation plan.

Our approach

Clear boundaries around people and information.

Trust is a product requirement, not a badge added after the workflow is built.
1

Purpose-limited information

Member details are used to coordinate rides and support the product, not for advertising or data resale.

2

Organization-controlled drivers

Each organization decides which members are approved to volunteer as drivers.

3

Coordinator review

Suggested assignments remain drafts until a coordinator reviews and finalizes the plan.

4

Role-based access

Coordinators, drivers, and riders receive different access based on what they need to do.

Permissions

Access follows responsibility.

Coordinators need the full event picture. Drivers need the riders and route assigned to them. Riders need their own invitation and pickup details.

RideSmart separates those responsibilities so the product can remain useful without treating every member like an administrator.

Volunteer drivers

Your organization decides who can drive.

RideSmart does not source drivers from outside your community. Driver approval stays with the organization and its coordinators.

Organizations remain responsible for their own policies, screening, insurance expectations, and suitability decisions. RideSmart provides coordination tools; it does not replace those responsibilities.

Important boundary

RideSmart is coordination software, not a transportation provider.

RideSmart is not a taxi service or commercial rideshare platform. It does not employ or pay drivers, provide vehicles, or replace an organization's own volunteer, safety, and insurance policies.

Have a trust or privacy question?

Bring it to the conversation. Early church partners should know exactly where the product's boundaries are.