Trust & safety center

Travel with local guides, but keep the experience protected.

Globotrip safety is built around clear guide profiles, on-platform communication, practical meeting rules, and an escalation path when something feels wrong.

Safety promise

Verified guide process

Identity, local expertise, and safety agreement checks.

On-platform communication

Keep itinerary, price, and safety-critical notes reviewable.

Report escalation path

Reports route to review with severity and related request context.

Verified guide steps

5

before approval

Safety report path

Review queue

triaged by severity

!

Emergency profile

Recommended

traveler side

Report review

Structured

with audit trail

Safety rules for the marketplace

These rules guide traveler support, guide approval, and marketplace safety review.

Open report form →
Traveler safetySR-001

Meet in public places first

For first meetings, travelers and guides should start in a visible public location such as a hotel lobby, museum entrance, cafe, or official pickup point.

Recommended action

Share the meeting point inside the request thread before the tour starts.

Platform safetySR-002

Keep plans inside Globotrip

Messages, itinerary notes, special needs, and agreements should stay inside the platform so support can review context later.

Recommended action

Avoid moving price or safety-critical discussions to external apps before confirmation.

Guide verificationSR-003

Confirm guide identity

Travelers should check that the guide name, profile photo, language, and destination match the request before starting the experience.

Recommended action

Use the verified guide badge and profile details as the trust source.

Trip readinessSR-004

Use emergency contact notes

Travelers should add an emergency contact, allergies, mobility notes, and medical restrictions before multi-hour or outdoor tours.

Recommended action

Store this in the travel profile before requesting a proposal.

!
Report flowSR-005

Flag suspicious behavior early

Travelers or guides should report requests for off-platform payment, unsafe itinerary changes, harassment, fake identity, or pressure tactics.

Recommended action

Use the static report form now; later it will create a support case in MySQL.

Policy guideSR-006

Review cancellation expectations

Cancellation rules should be shown clearly before a traveler confirms a guide proposal. Each confirmed proposal can inherit the guide's cancellation terms.

Recommended action

Show policy summaries before proposal acceptance in the backend phase.

Before the tour

Traveler checklist

Confirm guide profile

Name, language, destination, and verified badge match your request.

Confirm pickup point

Use hotel lobby, official site entrance, or public cafe for first contact.

Add trip notes

Emergency contact, allergies, mobility, food restrictions, and children ages.

Keep records

Agree itinerary, price scope, and included items inside Globotrip messages.

Guide quality

Verification checks

RequiredAdmin

Identity check

Confirm legal name, profile photo, primary location, and contact method before guide approval.

legal_nameid_document_typeid_statusverified_at
RequiredAdmin + guide

Local expertise review

Review destination knowledge, languages, sample tour ideas, and local experience evidence.

primary_citylanguagesyears_experienceexpertise_notes
RequiredGuide

Safety agreement

Guide accepts marketplace rules: public meeting points, no unsafe detours, no pressure, no off-platform payment requests.

safety_terms_accepted_atmarketplace_rules_version
RecommendedGuide

Profile quality

Guide profile should include a strong bio, clear languages, tour categories, availability notes, and real traveler-friendly details.

profile_scorebiotour_countprofile_review_status