Three kinds of data are stored separately
The client sign-in session, CSV check results and work progress are three different kinds of data. The session restores your identity; CSV is for reading or organizing results; work progress reloads the task list. Saving one kind does not mean the other two are saved.
On another computer, sign in again. Import, export and the interface follow the client you have.
The platform session and the Windows user
After a successful platform sign-in, the token is stored on the machine with the current Windows user’s encryption; the platform password is not stored. The next launch tries to restore it, then verifies the account and permissions online; a file existing does not mean the authorization is still valid.
This encrypted session is not a sign-in credential you can freely copy to another computer or another Windows user. Sign in again when you change environments. The platform session is independent of the Apple / brand session; you cannot restore a brand check state by copying platform files.
What a CSV export contains
A CSV you export contains the records in that run’s result table, and gift card results may include full card numbers and duplicate marks. The file is saved to the location you chose in the dialog; it is not a sign-in session that continues checks.
- After exporting, check that the file name, row count, currency and amounts match the interface.
- Results without an amount should keep the unknown status and must not be replaced with zero in bulk.
- Make a redacted copy before giving results to anyone, and keep the original file for your own checking.
Work progress and restoring tasks
The work-progress file stores the region, card codes and results, with no account password or sign-in session. Loading the file only restores the list; it does not sign in or send checks automatically, and unfinished tasks are restored as pending.
Loading work progress needs batch import permission, and saving it needs export permission. After restoring the list, confirm the region, brand session and platform authorization before you decide to run it.
Boundaries of signing out and upgrading
Signing out of the platform clears the platform session but does not delete exported files. Deleting the program is also not a way to clean up all exported files; CSV and work progress must be managed separately in the location you chose.
When upgrading, keep the result files you still need and check the source and version on the download page. A portable archive must be fully extracted, keeping the runtime files next to the program. Do not put personal state directories, account configuration or card files into a program package you distribute. The full steps are in the download and update guide.
What data should not be shared publicly
Full card numbers, PINs, platform or brand passwords, verification codes, sign-in tokens and proxy addresses with credentials do not belong in public feedback. Usually the version, the time and time zone, the selected region and a redacted error message are enough to start troubleshooting. A fuller field list and feedback boundaries are in the privacy notes.
For the check steps, see the batch workflow guide; for platform recovery and sign-out, see the platform authorization guide.