PomoZentraGet in touch.
Product questions, help with your account, bug reports, partnerships, security or press. Everything reaches one inbox, info@pomozentra.com, read by the team that builds PomoZentra. Pick the closest category below so it gets to the right person faster.
What is this about?
Four routes, all to the same address. The category shapes the subject line and who picks it up.
Product questions
Whether PomoZentra fits how you work, what it does not do, how the scoring behaves in your situation. Ask before you spend a week on it. We would rather talk you out of it than have you churn.
Many of these are already answered in the FAQ.
Account and technical help
Sync problems, a block that did not log, missing history, notifications not firing, or anything that looks broken. The fastest route is the feedback button inside the app, because it arrives with context attached.
Include what you expected, what happened, and roughly when.
Partnerships and press
Collaborations, integrations, writing about the product, or a question about the studio. Say what you have in mind in the first message rather than asking for a call to explain it.
Security reports
Suspected vulnerabilities go to the same address with "Security" as the category. Please report privately rather than publicly, and do not include real customer data or credentials in the first message.
We will acknowledge a security report within two business days and tell you what we are doing about it. There is no bug bounty programme.
Send a message
Four fields. Tell us what you need and include the details that would save a round trip.
What this form actually does
It does not send anything by itself. Pressing the button builds a draft and opens it in your own email app, with the category in the subject line, so the message comes from your address and you keep a copy in your sent items.
That means nothing you type here is transmitted to us, stored, or logged by this page. If your device has no mail app configured, just email info@pomozentra.com directly. It is the same inbox.
When you will hear back
We aim to reply within two business days. Security reports are acknowledged in the same window. Partnership and press enquiries sometimes take longer, because they need a considered answer rather than a fast one.
Every message is read and answered by someone who works on the product. There is no ticket queue, no chatbot and no autoresponder, so if you do not hear back, something went wrong and it is worth sending again.
Emailing us means we use your address and message to answer you, and nothing else. You are not added to any mailing list. See the privacy policy for how we handle it.
Already using PomoZentra?
There is no help centre yet, so these are the fastest routes in order.
1. The in-app feedback button
Best for anything broken. It arrives with context about what you were doing, which usually removes an entire round of questions.
2. The FAQ
Forty-nine answers covering setup, the scoring, data, deletion and the product's limits. Most support questions are already there. Open the FAQ.
3. Email
For anything the first two do not cover, or when you would rather explain it in your own words. Same address, same people.
Who you are contacting
Nozentra
PomoZentra is built by Nozentra, an independent product studio that has been building software since 2016. There is no customer-facing office to visit and no phone line, so email is the only route in.
General and only address: info@pomozentra.com. Read the about page for what the company is and how it decides things.
One address, on purpose
There is no separate sales, support, press or security address. A handful of addresses that all forward to the same inbox creates the impression of departments that do not exist, and messages get lost in the pretence.
One inbox, categorised by the subject line, is honest about the size of the operation and is genuinely faster.
You may not need us
These answer most of what arrives in the inbox, and they answer it instantly.
FAQ
Setup, scoring, cost, data, deletion and the product's limits. Forty-nine answers.
Setup guide
Seven steps from naming your work areas to reading the mid-week gap.
The method
How alignment is calculated and why credit is capped per work area.
Changelog
Everything that has shipped, including the fixes that were embarrassing.
Or try it and tell us where it fails.
Two weeks of honest logging and a note about what did not work is the single most useful message we receive.