# Contact Luuphub One mailbox, read by the person who builds the product: . ## Email support Write to for anything: a bug in the widget or dashboard, a question about what a plan includes, billing and invoices, account or data deletion, privacy and GDPR requests, security reports, or a feature you want Luuphub to have. Luuphub is run by a small independent team, so there is no ticket maze and no tier-one script — but also no published response-time guarantee. Replies are sent as soon as the message is read. What helps most in a first email: your account or site name, the URL where the problem happened, what you expected versus what occurred, and a screenshot or the exact error text. For an API or MCP problem, include the request path and the JSON error body — every API error carries a machine-readable `code` that points straight at the cause. ## Before you write Some answers are faster to look up than to ask for. The [developer docs](https://luuphub.com/developers) cover widget installation and theming, user identification, webhooks, the REST API, and the MCP server, and every page has a plain-markdown mirror for agents. [Pricing](https://luuphub.com/pricing) lists what each plan includes, and [data processing](https://luuphub.com/data-processing) answers most GDPR and hosting questions. If something looks broken across the whole product rather than just your account, check the [status page](https://luuphub.com/status) first — it reports live service health. ## Legal and privacy Privacy requests, data-export requests, and erasure requests go to the same address and are handled under the [privacy policy](https://luuphub.com/privacy). The [terms of service](https://luuphub.com/terms) state the governing law: the Republic of Latvia. Luuphub publishes no telephone number or postal address; email is the contact channel of record.