The record
The Only Honest Account of What Was Spent
Held inside the product, for an unstated period, in a form nobody has described.
No retention period, level of detail or export route is published. A record you cannot keep is a record that can disappear.
What a history normally holds
Two separate things that get conflated. A transaction history, listing deposits, withdrawals and bonuses with dates and amounts, and a game history listing rounds played, stakes and results. The first answers what an account cost; the second answers what happened inside it.
Only the first can be checked against anything external, because deposits and withdrawals also appear on a bank statement. That external cross-check is the most useful property the record has — and it is what the four-step sequence rests on.
Why it matters more than it sounds
Because memory of spending across a fast-cycling product is unreliable in a specific direction: people underestimate totals. A fifty-rupee stake repeated over an evening is not remembered as its sum, and a list that shows the sum is the only thing that corrects it.
That is also why the record is worth consulting deliberately rather than incidentally. It is the single input for what an account here actually costs, and the only one the product itself supplies.
What is published about it
Nothing. No retention period, no level of detail, no statement of whether history survives a reinstall, and no export route. Whether a record exists at all beyond a short recent window cannot be established without installing, which this site does not do.
In-app histories in this category are frequently short, which matters because the evidence you would need in a dispute is the evidence most likely to have been trimmed — and the complaints route that would use it is missing too.
Keeping your own
The bank statement is the durable half and it belongs to you. Deposits and withdrawals appear there with dates and amounts regardless of what any application retains, and no operator can trim it.
For the rest, a screenshot taken at the time is worth more than a search for one later. Where the point of the exercise is control rather than evidence, the tools that work from outside the product are more effective than any record. The overview explains the sourcing rule.
Frequently asked
Does the app keep a history of my spending?
Not stated. No retention period, level of detail, export route or statement about surviving a reinstall appears anywhere.
Why does the history matter?
It is the only record of what an account cost, and memory of spending across a fast-cycling product reliably underestimates the total.
What record can I rely on?
Your bank statement. Deposits and withdrawals appear there with dates and amounts regardless of what the application retains, and no operator can trim it.