Verification
Verification and trust signals
How Limowo should explain email, Swiss phone, account, seller, and agent-related trust signals without pretending that verification replaces user judgment.
Last updated: 1 July 2026
Contact support
Signals
Email, phone, account, seller
Boundary
Verification is not a guarantee
Launch gate
Review rules and evidence quality
Current verification model
Limowo uses account status, email verification, Swiss phone verification, profile review, verified contact signals, and moderation history to give buyers and sellers better context before they interact.
Swiss phone verification
Publishing and trust flows may require a verified Swiss phone number. This helps keep marketplace activity grounded in Switzerland, but it does not prove item ownership, identity documents, account authority, product quality, or payment safety.
Profile review
Profile and listing signals should be based on reviewed account information, verified contact methods, listing history, and moderation checks. Final criteria, evidence retention, rejection reasons, and appeal paths remain launch gates.
What verification does not mean
A verified badge must not be treated as a Limowo guarantee, insurance, escrow, product certification, background check, legal approval, or promise that a transaction is risk-free. Users should still check item condition, counterparties, pickup details, payment requests, and delivery expectations.
Trust signals on listings and profiles
Listing and profile trust signals should be clear, current, and explainable. Limowo should avoid vague badges and should show only signals supported by account state, verified contact methods, reviewed account information, moderation state, or other auditable evidence.
Privacy and data minimization
Verification should collect only the information needed for the specific check, protect private phone, identity, account, and seller data, and expose only public signals that users need to evaluate marketplace interactions.
Agent and API use
Agent/API surfaces may read public verification signals when documented, but they must not create, modify, bypass, or infer private verification state without explicit authorization, audit records, and human review where required.
Launch-gate verification work
Before Limowo claims mature verification operations, it should finalize verification criteria, evidence quality rules, manual review ownership, data retention, appeal handling, badge wording, fraud escalation, audit logging, and production acceptance evidence.
