Bug
What happened
What you tapped, what you expected, and what you saw instead. A screenshot usually says more than a paragraph.
Contact
One inbox, read by a person.
Everything comes to the same address — bug reports, questions, beach requests, billing. There is no ticket system and no bot on the other end. You write, someone who works on WaxUp reads it.
Before you write
A little detail goes a long way.
Three things that turn one email into one answer.
Device
Where it happened
Your iPhone model and iOS version narrow the search from everywhere to somewhere. Both live in Settings, under General, then About.
Anything
No category needed
Feature ideas, a beach you want covered, a forecast that read wrong, a question about Premium. You don't have to sort it first. Just write.
After you send
You'll hear back from a person.
Most emails get a reply within two working days.
WaxUp is built by a small team, so your email lands close to the code. If you found a bug, expect a follow-up question or two and then a fix on the list. If you asked for a beach or a feature, it goes into the same notebook everything else gets built from.
Questions
Support, in plain terms.
Short answers about writing in.
What makes a good bug report?
What you were doing, what you expected, and what happened instead — plus your iPhone model and iOS version. Two sentences and a screenshot beat a page of guesswork.
How fast will I hear back?
Usually within two working days. Replies come from someone who works on the app, so a busy launch week can stretch that a little — but nothing disappears into a queue.
What happens to what I send?
Your address and anything in your email are used to answer you, and nothing else. No marketing list, no sharing. The full detail is in the privacy policy.
Can I suggest a beach or a feature?
Please do. Beach requests and feature ideas shape what gets built next. Name the beach and roughly where it is, and we'll take it from there.