write to a human.

we do not have a phone number, we do not want one, and we are not going to install a chat widget. email is the way you reach us. the inbox is read by an actual person on the team — usually the founder during european or israeli working hours, sometimes the qa lead at unsociable times when the founder is asleep — and a reply lands within the same working day for almost everything that is not "my refund is overdue," in which case it lands within the hour.

there is no ticket number, no auto-responder explaining that your "request has been received," no follow-up email asking you to rate our service on a one-to-ten scale. you write to the address below; somebody on the team writes back. if the question is technical, the person who wrote the broken code answers; if the question is about money, it is the founder; if the question is about whether a competitor would actually serve you better, we say so out loud.

email — everything

support@voiddo.com

this is the one inbox you actually want. product help, billing and refund questions, bug reports, press requests, partnership intros, "i tried to install your wordpress plugin and the activation step fails," "your refund email said to confirm and i’m confirming," and the polite hello you wrote after reading an essay we published — all of it goes here. the inbox is reviewed by name, not by topic; nobody on our team works for "the support department" because there is no support department.

github — open source

github.com/voidd0

for issue tracking on the open-source tools, npm utilities, and the small command-line packages under the @v0idd0 scope. if you are reporting a bug on a paid product (scrb, rankd, tells), please use the email above instead — the github issue queue is read once a week, the support email is read continuously.

linkedin — the company

linkedin.com/company/vøiddo

for the occasional release post, hiring update when we are hiring (currently not), and the occasional "we just shipped a thing" announcement that is the same announcement we put in the blog. not a great place to ask a support question. the dms are open, but the response time there is days, not hours.

mailing address — estonia

Järveküla tee 64-9, Sviidi 7979
Järve 30322
Kohtla-Järve, Ida-Viru
Eesti

the legal address of the estonian limited company that runs the studio. this is the address to use for paper legal notices, gdpr correspondence, can-spam-style compliance mail, and the formal stuff that has to physically arrive somewhere. product support and refund requests still start by email; a paper letter to the legal address will be read, but it will sit on a desk for two weeks before anybody walks in to collect it.

what to expect when you write in

our standard reply window is the same working day for european and israeli hours; the same evening for american hours; the next morning for everything sent on saturdays and sundays. the founder reads the inbox first thing in the morning, again at lunchtime, and again before the laptop closes. if the servers are on fire, the team prioritises fixing the fire over replying to email, and you may notice a four-to-six-hour gap; once the fire is out, the inbox catches up.

refund requests are processed the same day they arrive. paddle is the merchant of record, the refund is a one-line email plus a one-click action in our paddle dashboard, and the money lands back on the original card within three to five business days depending on which bank you use. there is no "please tell us why you want to cancel" interrogation; the question is rhetorical, the cancel button is the cancel button. if you want to tell us why, the email reply box is right there.

technical bug reports get faster replies the more useful the report. a one-line "it doesn’t work" gets a polite "could you tell me what you tried, what you expected, and what happened instead" within the hour, then a real reply once you write back. a useful report — steps to reproduce, the actual error message, what browser and operating system — usually gets a real reply within the first response. we appreciate the second kind disproportionately; we do not pretend we are unaffected by it.

finally: there is no support sla. there is no enterprise tier with a separate inbox and a higher priority. paying customers and free-tier users wait in the same queue; the founder cannot tell which is which without checking the paddle dashboard, and usually does not bother. fast, honest, same-day replies are how we treat everyone or how we treat no one; we picked the first option in 2024 and have not had a reason to revisit.