About
Why Safar exists
Muslim travelers to Japan, Korea, and Taiwan have inventory access - but not verification quality. Existing platforms tag hotels as "Muslim-friendly" without showing the evidence. We are building the layer that does.
Our mission
Make halal trip planning to Northeast Asia honest by default. Every claim a hotel makes about halal-friendliness - prayer room, halal breakfast, alcohol policy, family rooms - is paired with the underlying evidence and labelled with the tier of verification behind it. No guessing. No surprises at check-in.
What we believe
The Muslim traveler's pain in Japan, Korea, and Taiwan is not finding hotels - it's verifying claims. HalalBooking, HalalTrip, and HHWT label properties as "halal-friendly" but don't show what's behind the label. The result is that families plan trips on incomplete information and either pay for a hotel that turns out to be wrong, or send 30 emails to confirm what should be in the listing. We close that gap.
Who this is for
Muslim travelers from Malaysia, Indonesia, Singapore, Brunei, and the GCC who are planning leisure or family trips to Japan, Korea, or Taiwan. The site is available in English, Bahasa Melayu, and العربية; Bahasa Indonesia readers can use the Malay site comfortably.
What makes us different
We don't compete with major booking platforms on inventory. We link out only to approved booking partners when partner access is active. What we own is the verification layer above the inventory. Three things distinguish us: • Tier-labelled evidence - every claim says how it was verified (owner-claimed, evidence-backed, cert-backed, guest-confirmed, inspected), not just yes/no. • Cross-walk to authoritative cert bodies - CrescentRating, JHA (Japan), KMF (Korea), CMA (Taiwan). We use their data when it exists and cite it. • Guest confirmation loop - past travelers confirm whether claims held. A claim that gets contradicted drops in tier.
Where we are today
v0 covers Tokyo. v0.5 adds Taipei. v1 adds Seoul. Phase B unlocks photo upload automation, distance fetcher, trust score computation, and the guest confirmation loop. The full roadmap lives in our build tracker; the spec lives in AGENTS.md.