Correspondence.
One address, read by the people who wrote the software. We use it for support, for bug reports, for feature proposals, and for letters that do not quite fit any category. We read every letter ourselves, and we answer — as a rule — within one working day.
A.1Address
Electronic. [email protected]
Postal. Kunaeva 43–303, Almaty, Kazakhstan
Electronic correspondence is preferred and faster. There is no queue, no ticket number, no intermediate form to fill. The address goes to a human. The human reads it. The human answers.
A.2When to write
- When one of our applications does something you did not expect.
- When one of our applications fails to do something you did expect.
- When something is wrong that is not strictly a defect, but offends anyway.
- When you have an idea for a thing we have not thought of.
- When you have a question about billing, a subscription, or an account.
- When you have a question that fits nowhere above.
A.3Anatomy of a useful letter
The shortest useful letter identifies the application, the device, and the thing that happened. In practice, a letter of the following form is always easy to act on:
- Application and version. Available in the app's settings, typically at the bottom.
- Device and operating system. For example: iPhone 15 on iOS 18.3, or Pixel 8a on Android 15.
- What you were doing at the moment the problem occurred.
- What happened, and what you expected to happen instead.
- A screenshot, if a screenshot would clarify the situation.
None of this is required. We can usually make sense of almost any letter. But the more you tell us, the less we need to ask, and the sooner the thing gets fixed.
A.4What not to expect
We do not reply to unsolicited sales outreach, link-building proposals, SEO services, "partnership opportunities" that mean advertising, or offers to rewrite our software for us. We do read these letters, briefly, to make sure we are not missing something. We rarely are.