Privacy

Where BluffLog stores your hands, what anonymous telemetry sends, and the two data channels that only work with your explicit consent.

BluffLog analyses your game after the session, on your machine. The database with your hands is a file on your disk, and every stat, graph and replay is computed from it locally. Nothing about your poker travels anywhere on its own.

Exactly two channels can carry hand data off your computer — the import error report and the anonymous hand corpus. Both are off until you switch them on, and both are described below in full. Everything else the app sends is anonymous usage telemetry with no game content in it.

Everything lives in one folder

Hero.db is ordinary SQLite. Don’t take this page’s word for anything — open the file with any SQLite browser and look at what’s inside. Settings hold your filters, paths and preferences; logs are plain text files that never leave the disk.

Backing up means copying the folder. That’s the whole procedure. Deleting works the same way: remove the folder and BluffLog forgets everything. We can’t restore it — we never had it.

What the app sends automatically

Anonymous usage statistics, so we know which features get used and what breaks:

• which screens are opened — ids only, no content;
• errors and crashes;
• app version and OS version;
• coarse performance numbers.

No cards, no boards, no table names, no nicknames, no results. One narrow exception: when hands fail to import, the completion event carries the failure counts and one short error message per failure class, with the id of a failing hand attached — enough for us to see a parser break, while the hand itself stays on your disk. The rule we build by: if a field would let anyone reconstruct a hand, a table or a person, it doesn’t belong in this channel — it goes into a consented one or nowhere.

Telemetry has a switch in the settings. Off means off, and the app works exactly the same.

Exception one: the import error report

Some hands fail to parse. GG changes formats, and our parser has bugs like any other. When that happens, the app shows what failed and asks whether to send us those specific hands so we can fix it. Every report is its own question with Send and Don’t send — nothing goes on its own, and hands that imported fine are never included.

You can add a comment, and an email if you want a reply. The email travels only when you tick that box.

Exception two: the anonymous hand corpus

You can donate the structure of your hands to a shared corpus, so the trainer’s norms rest on how the field actually plays rather than on our idea of it. Off by default. The app asks once, lists what travels, and shows the actual data of one of your hands exactly as it would leave — there’s a button for that in the dialog. Two separate checkboxes: future imports, and hands already in your database.

What travels:

• stake, format and table type;
• positions relative to the button, stacks, every action;
• the board and any known cards;
• pot, rake and jackpot;
• the date to the day, and the app version.

What never travels:

• the hand id and the table name;
• the exact time the hand was played;
• the tournament number, your finish and your prize;
• player identifiers;
• any marker of whose hand it was.

The install id never enters the corpus. It exists only to count your contribution and is stored separately from the hands — the hands themselves contain nothing that points at you. That cuts both ways: you can switch sending off at any time, but what has already been sent cannot be recalled, because nothing remains in the corpus by which your hands could be found.

One honest limit. Inside a single hand your hole cards are present even when you folded without showing — a fold with a known holding is exactly what range analysis is made of. So the claim we can actually stand behind is this: we do not know whose hand it is, which account it came from, at which table, or at what moment it was played.

Sending runs in the background with visible progress in the settings (“sent 12,400 of 203,000”) and a pause button, and it stands down while an import is running.

The full policy

The short legal version lives at Privacy Policy. Questions — support@blufflog.app.

BluffLog is free and offline. Download it and check this page against the folder on your own disk.