One person, answering their own email

Support.

There is no ticket system and no support team. There is an address, read by the person who wrote the code.

Before anything else

Jot is available from the Microsoft Store. If something is broken, the fastest route is an issue in the repository with the details below, or an email to the address on this page.

Write to us

hello@wrivio.com - for bugs, questions, deleting your data, or telling us the software is wrong about something.

Expect a reply within about 2 working days. That is a target from one person, not a service level, and it will occasionally be missed.

What to include in a bug report

The difference between a report that gets fixed and one that sits for a month is almost always whether it can be reproduced. Useful:

Never send the contents of a capture unless it is the thing that is broken and you are comfortable doing so. We do not need it, and we would rather not have it.

Where your data is, if you need it

Everything Jot holds is in one folder: com.wrivio.jot in your Windows app-data directory for the direct download, or the app's own storage under %LOCALAPPDATA%\Packages if you installed from the Microsoft Store. Either way it contains:

Moving to a new PC: copy jot.db across, then enter your AI provider key again on the new machine if you use that feature.

If you installed from the Microsoft Store: uninstalling Jot removes that folder with it, which is how Windows treats every Store app. Copy it somewhere first if you want to keep your captures. Installing the Store version on a machine that already has the direct download brings your existing captures across for you, once, and leaves the original folder alone.

Deleting everything: delete the folder. That is the whole of it. There is no server copy to also ask about - though if you are on the launch-notification list, ask us and that address goes too.

Feature requests

Welcome, with one caveat worth reading first: Jot is deliberately a capture tool and not a note app, and a good number of reasonable requests are turned down for that reason rather than for lack of time. The reasoning is written down, so you can tell in advance which kind yours is.

Requests that fit - a token, a keyboard shortcut, a destination, something in the parser - are the best kind of email to get.

Security

Vulnerabilities go to the same address, and there is a separate page about what to expect. Please do not open a public issue for one before it is fixed.