Consumption shows a dash
The figure needs two full fill-ups of the same fuel, each with an odometer reading, and it stays a dash until they exist. Partial fill-ups are left out of the calculation unless you turn on Fuel consumption in Settings.
Support
One developer reads both mailboxes. A report gets fixed sooner when it arrives with the version number, the phone, and a screenshot.
Bugs and questions go to support@mve.suxlv2.space. Anything about your own data — a copy, a correction, deletion — goes to contacts@mve.suxlv2.space, the address the privacy policy names. The same person reads both, so a letter to the wrong one is not lost. MiExpenses is built and supported by one person, so the honest answer about reply time is days rather than hours. Write in English or Russian; both are read.
The app also has a Feedback item in the side menu, which sends a rating and a comment. It is useful for a short remark, but it has no reply channel, so use e-mail when you expect an answer.
Four lines. With them a problem can usually be reproduced without another round of questions.
Open Settings and scroll to the User preference section. The last row there reads Version followed by the number, with the build date underneath. Copy both as they stand.
Model and Android version, from the phone's own settings under About phone. Behaviour that depends on the manufacturer, late notifications above all, cannot be guessed without it.
The screen you were on, the steps in order, and what the app actually showed. "Consumption is wrong" cannot be reproduced; "the fill-up on 25 August shows a dash instead of a figure" can.
One frame of the screen where it goes wrong saves a paragraph of description. If an error message appeared, catch it in the shot.
The figure needs two full fill-ups of the same fuel, each with an odometer reading, and it stays a dash until they exist. Partial fill-ups are left out of the calculation unless you turn on Fuel consumption in Settings.
That line means the action needs the server: signing in, reloading everything, and any change to a record that has already been uploaded. Creating is the other way round — a new vehicle, category, reminder or expense all save with no network and go out the next time the home screen opens online.
Monthly limits and expense templates are saved to the server, and that is part of MiExpenses Premium. Without it they stay on the phone alone: a reinstall removes them, a second phone with the same account does not show them, and signing in again does not bring them back. They are written into the CSV export either way, which is the copy you can keep.
The check runs in the background roughly every six hours, and Android battery optimisation can push it later. Reminder notifications are also held to 09:00-22:00 local time, at most one every eight hours, and none are shown while the app is open on screen.
The export needs no request and no waiting: it comes straight out of the app, one vehicle at a time. It is not an automatic backup — nothing is written anywhere on a schedule — but the file is not a dead end either: Data → Import in the side menu reads it back in, and running an import twice is safe.
Deletion is different. The app has no delete-account screen and the API has no endpoint for one, so it is a request handled by hand, and no same-day promise is made here. What is held on the server, and who else can see it, is set out in the privacy policy.