Support

Email [email protected]. One person reads it.

Before you write

A file will not import. Send the exact message, the file size, and the first two lines of the file with anything private replaced. Those two lines usually contain the problem, which is normally an unexpected separator or a header that is not on row one.

The columns came out wrong. Reopen the file and look at the import preview before loading. It shows the separator, the encoding and whether row one was treated as a header. Changing one of those there fixes most cases. Tell me which one was wrong and I can make the detection better.

Characters look wrong. Try Latin-1 or Windows-1252 as the encoding in the import preview. Older exports are often one of those rather than UTF-8.

The summary has no written text. The written briefing needs Apple Intelligence, which means macOS 26 on a Mac that supports it. On macOS 12 through 15 the same panel shows the statistics without the prose, and that is working as intended rather than a failure.

It is slow on a large file. Say how large, what you were doing, and which Mac. Import is a single pass over the file, so a multi-gigabyte import takes a while on a slow disk. Scrolling and filtering after that should not.

Asking for a feature

Say what you were trying to do, not which feature you want. The request that gets built is usually the one that describes the task.

Charts, .xlsx files and more than one file open at once are already known gaps, so those are on the list.

Refunds

Refunds go through Apple, not through me. Use Report a Problem with the Apple Account that bought the app.