You email support and I answer.
I am Alfonso, and I build DeftNib. There is no first line support team and no form that opens a ticket: you write to support@deftnib.com and I answer, and I am the person who wrote the code you are writing about.
That has a consequence worth saying out loud: this is a one person app. Which is exactly why it is built not to depend on me. There is no server transcribing anything and no account to administer, and once a Mac is activated it checks the license on its own, with cryptography that runs right there. If I disappear tomorrow, the Macs you already activated keep working exactly the same.
What to include in an email
The answer is faster when the first message has what I need to reproduce the problem:
- The app version. It is in the About window and at the bottom of Settings.
- Your macOS version (About This Mac). DeftNib needs macOS 26 or later on Apple Silicon.
- The app you were dictating into (Slack, Cursor, Mail, a browser and which one) and what you expected to happen.
- What you said and what was written, if the problem is in the text. The history section of the app has both, if you turned history on.
You never need to send audio: the app does not keep any, and I would not want it. If a dictation contained something private, describe the shape of the problem instead of pasting the text.
How long it takes
Usually within a day on working days, sometimes the same hour, sometimes two days when a release is in progress. I read everything. A bug with a clear reproduction goes to the top of the list; a feature request gets an honest answer, including "no" when it is no.
Things you can do without writing
- See or free up your Macs: paste your key on the license page. It is the way out when a Mac no longer exists.
- Get a refund: 30 days, no questions. How a refund works.
- Check what the app sends: the four kinds of calls to our servers, each with what it carries, on the private dictation page.
- Read how a feature works: the guides in Learn, and the complete tour in Features.