Report the evidence, not just the symptom.
Good beta reports include the device, browser, build, page, expected result and the exact steps that produced the problem.
Security reports
security@cryptotracka.comReport suspected vulnerabilities privately. Do not publish exploitable details.
Include these details
- CryptoTracka build or deployment date, when known.
- Phone, tablet or computer model.
- Browser name and whether CryptoTracka is installed.
- Page and portfolio source involved.
- Steps taken immediately before the issue.
- Expected result and actual result.
- Screenshot or short video, after hiding personal information where practical.
[Build] [Device] [Page] Short problem
Example: 2.6.21 · Infinix · Portfolio · language returns to English
A specific subject line makes regression tracking and duplicate reports much easier.
Common first checks.
These steps resolve many browser-state problems without changing account data.
Language changes unexpectedly
Disable Chrome's automatic translation for CryptoTracka, then use the app's own EN/TL control.
The app shows an old page after deployment
Fully close the installed app, reopen it and refresh. Avoid clearing stored data unless support specifically asks.
A CSV is rejected
Confirm the selected importer matches the export source and compare its headings with the current sample file.
Portfolio totals look wrong
Check for duplicate imports, missing sells, unsupported assets, transfer warnings and incorrect transaction dates before editing any history.