Trust center
Trust center for Limowo
A single public overview of Limowo's marketplace workflow, trust, moderation, privacy, safety, security, status, support, and agent/API readiness surfaces for an early marketplace project.
Last updated: 1 July 2026
Contact LimowoScope
Marketplace project
Public policies
Privacy, safety, fees, status
Boundary
Early project status
What this center covers
This Trust Center connects the public pages that explain Limowo's marketplace workflow, platform role, account signals, moderation and appeals, privacy and data processing, cookie controls, safety rules, fee transparency, security reporting, availability communication, support paths, accessibility intent, and agent/API boundaries.
Identity and legal notice boundary
Limowo is currently a marketplace project name. Public copy should use the current project contact and should not imply formal operator details that do not exist yet.
Privacy and data protection
The Privacy, Privacy Rights, Cookies, and Data Processing pages explain controller readiness, data categories, purposes, legal bases, access/export, retention and deletion expectations, consent controls, processors, international transfer notes, and privacy rights. A final provider register and legal review remain required before broad production promotion.
Marketplace safety
The Verification, Safety, Safe Trading, Terms, Fees, and Support pages explain trust signals, prohibited listings, safe trading expectations, moderation, dispute boundaries, appeal readiness, CHF/payment clarity, and user support. Final verification criteria, prohibited-items wording, escalation paths, appeal windows, and commercial terms remain subject to operations and legal review.
Security, availability, and support
The Security and Status pages explain responsible vulnerability reporting, responsible testing limits, machine-readable security contact discovery, service status communication, planned maintenance, and incident reporting. Monitoring, alerting, severity levels, on-call ownership, response targets, and uptime/SLA wording remain launch gates.
Agent and API boundaries
The Agent Policy and public agent contracts describe discovery surfaces, human approval for writes, excluded capabilities, data minimization, MCP release gates, and production readiness boundaries. Delegated authorization, durable command state, approval records, revocation, rate limits, and MCP conformance must pass before broad rollout.
What remains before launch
Before claiming full professional launch readiness, Limowo should close verified operator/legal details, legal review, privacy/provider register, cookie governance, accessibility audit evidence, support escalation, moderation operations, monitoring and incident evidence, agent/API release gates, and Hetzner acceptance-test records.

