Privacy Policy

The short version

BDO Grind Tracker is a hobby site for Black Desert Online players. We keep the account you create, the sessions and builds you log, and not much else. Specifically:

• We use Google Analytics, and only if you say yes. It counts page views so we can see which parts of the site get used. It does not load at all until you accept the notice, and declining keeps it off. There is no advertising and no profile building either way.
• The cookies we set ourselves are first-party and small. Two keep you signed in, two remember how you like the site laid out, and one records your answer about analytics.
• We never sell your data, and we do not share it with advertisers, brokers or anybody else who wants to build a profile of you.
• The site sends no email at all. Your address is used to identify your account and nothing else.
• If you sign in with Discord, we do not keep your Discord token. It is used once to read your profile and then thrown away.

The rest of this page is the detail behind those claims. It is longer than the summary because being specific is the only way any of it is worth reading.

Who we are

This site is operated by Solkarra Group Pty Ltd (ACN 688 412 900), an Australian company. Where this policy says "we" or "us", that is who it means.

BDO Grind Tracker is a fan project. It is not affiliated with, endorsed by or sponsored by Pearl Abyss, and we have no access to your Black Desert Online account. Nothing here is read from the game — everything we hold about your characters is something you typed in yourself.

What we collect

Your account

When you register we store:

• your username, email address and display name;
• a hash of your password — never the password itself. If you signed up with Discord and never set a password, there is no hash at all;
• your region, and the gear figures you choose to record on your profile (AP, combined AP, family fame) so your logged sessions can be valued correctly;
• whether you have a Value Pack or Merchant's Ring, because both change what your loot is worth;
• your display preferences — theme, whether consumable costs are shown, and whether new sessions default to shared or private;
• when your account was created, approved and last signed in.

Discord, only if you link it

Signing in with Discord is optional. The account you already have works fine without it. If you do use it, we ask Discord for two permissions — identify and email — and store what they return: your Discord user ID, username, global (display) name, avatar reference, email address, and whether Discord has verified that address.

We do not store your Discord access or refresh token. The token is used for a single request to read the profile above, and is discarded immediately. We cannot act on your Discord account, read your messages, see your servers, or do anything else with it — and because no token is kept, we could not do so later even if we wanted to.

The stored profile is refreshed each time you sign in through Discord, so it follows your current name and avatar. You can unlink Discord at any time from your profile page, which deletes the link record.

What you log

• Grind sessions — the spot, how long you were there, the loot you recorded, the buffs and costs you applied, whatever you typed in the notes field, and whether the session is shared or private.
• Character profiles — character name, class, specialisation, and the stats you enter (AP, DP, evasion, accuracy, HP).
• Gear builds and crystal presets — their names, notes, contents, visibility setting, and any share link you generate.
• Lifeskill logs — crafting batches and gathering runs, with their inputs and outputs.
• Guild membership — which group you belong to, and the group name and description whoever set it up entered.

Technical records

• Your IP address is recorded against failed and successful sign-in attempts, so the site can rate-limit password guessing. It is also recorded against requests to our machine API, which is only usable with a token an admin issued.
• A hash of your browser's user-agent string is stored with a "remember me" token — the hash, not the string, and it exists so a stolen token is harder to reuse.
• Our web host keeps its own server logs, as every web host does. Those are outside this application.

Cookies

Ours

These five are first-party, none is used to track you across other sites, and none is set by anybody but us:

Cookie	What it does	How long
bdogt_session	Keeps you signed in for the current session.	30 days
bdogt_remember	Signs you back in automatically if you ticked "remember me". It rotates every time it is used, and if we see a token that has already been rotated we treat it as stolen and sign that account out everywhere.	400 days
bdogt_ui	Remembers which panels and menu sections you have folded away, so the layout is where you left it.	1 year
bdogt_seen	Records the last release whose "What's new" note you dismissed, so you are not shown it again.	1 year
bdogt_consent	Records your answer to the analytics question below. It holds one word, granted or denied, and it is what stops you being asked again.	1 year

The two sign-in cookies are marked HttpOnly (so page scripts cannot read them) and SameSite=Lax, and are sent over HTTPS only. The other three are read by the page itself, so they are not HttpOnly, and none of them holds anything about you.

Your browser also stores one small preference locally: how you like large numbers formatted. It never leaves your device.

Google's

If, and only if, you accept the analytics notice, Google Analytics sets its own cookies on this domain. They carry a random identifier that lets Google tell a returning browser from a new one. They are not set before you accept, and if you decline they are never set at all.

Cookie	What it does	How long
_ga	Tells one browser from another, so a person who visits three pages is counted as one visit rather than three.	2 years
_ga_ followed by our property id	Holds the state of the current visit for the same purpose.	2 years

There are no advertising cookies on this site, and no other third party sets a cookie here.

Analytics

We use Google Analytics 4 to count page views. The reason is narrow and worth stating: we want to know which parts of the site people actually open, so the menus and the features can be built around that instead of around a guess.

It is off until you turn it on

Nothing is requested from Google until you accept the notice. This is not a script that loads and then promises not to report: the tag is not in the page at all, so your browser makes no request to Google and Google is not told your IP address. If you decline, that stays true permanently.

What it is told

• the page you opened, its title, and the page you came from;
• rough technical details of your browser: type, version, screen size, language;
• an approximate location, worked out from your IP address and no finer than a city;
• a random identifier held in the cookies above, which lets Google tell a returning browser from a new one.

Your IP address is anonymised. Google Analytics 4 truncates it before the event is stored, so the full address is never written to a report, and there is no setting we could change to make it keep one.

We do not send Google your username, your email address, or anything you have logged. It is not told who you are, and the figures we look at are counts of pages rather than lists of people.

What we have switched off

Two Google Analytics features are on by default and are turned off here, in the code that loads the tag:

• Google signals, which would tie your visit to a signed-in Google account and follow it across devices;
• Advertising personalisation, which would let the data feed ad targeting.

With both off, the data is used to count visits to this site and nothing else. Google processes it as our processor, and holds it under its own privacy policy.

Where it does not run

Even after you accept, the tag is not loaded on share links, on the sign-in and registration pages, or on the admin screens. A share link is a private URL somebody sent you, and measuring it would hand a third party a page that is meant to be seen by whoever holds the link and nobody else.

Changing your mind

Whatever you chose, you can change it here, at any time, without asking us:

Turning it off stops the tag loading from the next page you open. You can also block it in your browser, or turn on Do Not Track or a content blocker, and nothing here will work around that.

Who else sees it

We are not in the business of passing your data around. These are the only third parties involved, and what each one gets:

• Cloudflare (Turnstile) — the anti-bot check on the sign-in, registration, guild-invite and Discord-completion forms. Completing that check sends your IP address to Cloudflare along with the challenge response. The Turnstile script is loaded only on those pages, not site-wide, so Cloudflare does not see you browsing the rest of the site.
• Google (Analytics), only if you accept the analytics notice. Accepting sends your IP address to Google along with the page you are on, and Google truncates that address before storing it. Decline and Google is never contacted about you at all. The full detail is in Analytics above.
• Discord — only if you choose to sign in or link your account. You are sent to Discord to approve it, and Discord tells us the profile fields listed above.
• Discord's image CDN — if your account is linked, your avatar is loaded directly from cdn.discordapp.com, which means your browser makes a request to Discord to fetch it.
• Stripe — only if you pay for something. Payment pages are Stripe's own, hosted on their domain, so your card details go to Stripe and never touch this site — we cannot see them, and there is nowhere here for them to be stored. We send Stripe your email address and a display name (your guild's name for a guild payment, yours for a personal one) so it can issue a receipt, plus a reference identifying what is being bought. Stripe sends us back the fact that a payment succeeded, the amount, and the last state of the subscription. Stripe is an independent controller of the payment data it holds and keeps it under its own privacy policy.
• Our web host — a shared hosting provider, which necessarily stores the site's files, database and server logs.

If you never pay for anything, Stripe is never contacted about you at all — no script, no request, nothing. It is reached only when you start a checkout.

Market prices come from a third-party Black Desert market API. That is an outbound request made by our server on a schedule — no information about you is sent to it, and it does not know you exist.

We may also disclose information if we are legally required to, or where it is genuinely necessary to investigate abuse of the site.

What other players see

This is the part worth reading properly, because some of it is not obvious.

Shared and private sessions

Every session you log is either shared or private, and you choose the default. It is important that you understand what "private" actually means here:

Private means not attributed to you. It does not mean not counted.

A private session never appears on a leaderboard, in a head-to-head comparison, or on any list that names you — including to admins. But it does still contribute to the anonymous community averages and the crowdsourced baselines that make the site useful, in a form that cannot be traced back to you. If you do not want a run counted at all, delete it.

Leaderboards and comparisons

Leaderboards and head-to-head comparisons name players, and are visible only to people signed in to the site. They are built from shared sessions only.

Share links

You can generate a link to a session, your stats, a build or a crystal preset. These links contain a long random slug, and the slug is the only thing protecting them — anyone who has the link can open the page without an account. They are marked so search engines do not index them, but treat them as public. Revoking a share link stops the old URL working immediately.

Guilds and the build library

If you join a guild group, its members can see what you have chosen to share with the guild. If you publish a build or preset to the public library, other users can view it, copy it and edit their copy — that is what the library is for. Your original stays yours; their copy is theirs.

What admins can do

Accounts are approved by hand, so there are administrators, and you should know what they are able to do. An admin can approve, suspend or delete accounts, issue a password-reset link, view the list of sessions on an account, unlink a Discord account, moderate published builds — and sign in as another user to diagnose a problem.

We mention that last one explicitly because a policy that quietly omits it would be misleading. It is a support tool, it is recorded in the admin log, and it does not bypass the rule above: a session you marked private is not attributed to you for an admin either.

How long we keep it

What	Kept for
Your account and everything you logged	Until the account is deleted
Sign-in attempt records (including IP)	24 hours
Machine API request records (including IP)	72 hours
Anonymous session files on the server	48 hours
Machine API audit records and admin action logs	Retained
Web host server logs	Per the host's own policy
Google Analytics events, if you accepted	At most 14 months, then deleted by Google

Your choices

Without asking anyone, you can:

• edit or clear anything on your profile;
• set whether new sessions default to shared or private, and change any individual session at any time;
• delete a session, build, preset or log entry;
• revoke a share link;
• unlink your Discord account;
• turn analytics on or off, as often as you like.

Ask us and we will give you a copy of what we hold about you, correct anything that is wrong, or delete your account.

Getting your data deleted

Message us on Discord or send an email — both are below — from the account you want deleted, or from a Discord account linked to it, so we know it is you. There is no self-service delete button yet; an admin does it by hand.

When we delete an account:

• your username, email, display name, password hash, character names, any linked Discord identity and everything else that identifies you is removed;
• your share links stop working;
• the sessions you logged are detached from you and kept as anonymous data, continuing to feed the community averages and baselines exactly as a private session already did.

We do it that way because those aggregates are the point of the site, and pulling historical runs out of them would quietly degrade the numbers everyone else relies on. Once detached, the data no longer identifies you and cannot be linked back. If that is not acceptable to you, tell us when you write and we will talk it through rather than assume.

Some records survive deletion because they have to: entries in the admin action log, and anything we are required to keep.

Children

This site is not intended for anyone under 13, and you may not create an account if you are younger than that. If we find out an account belongs to a child under 13, we will delete it. If you believe a child has given us their information, contact us and we will remove it.

Where your data goes

We are an Australian company, but the internet is not. Our web host, Cloudflare, Discord, Stripe and Google all operate infrastructure outside Australia, so your information may be stored or processed overseas. By using the site you accept that this happens. Google is the one you can opt out of entirely, by declining the analytics notice.

Security

Passwords are stored only as hashes. Session and sign-in cookies are HttpOnly and HTTPS-only. "Remember me" tokens rotate on every use and are revoked across the whole account if we detect one being reused. Sign-in attempts are rate-limited by both username and IP, and the sign-in and registration forms are behind an anti-bot check.

None of that adds up to a guarantee. No website is perfectly secure, and we are not going to pretend otherwise. Use a password you do not use anywhere else, and do not put anything in a notes field you would mind being seen.

Changes to this policy

If we change this policy in a way that matters, we will update the version at the top of the page and ask you to agree again the next time you sign in. Small corrections — a fixed typo, a clearer sentence — just change the date.

This is version 2026-08-19, published 19 August 2026.

Contact

For anything on this page — a question, a correction, a copy of your data, a deletion request or a complaint — reach us at:

• Email — [email protected]
• Discord — our Discord server

Solkarra Group Pty Ltd (ACN 688 412 900), Western Australia.

If you are not happy with how we have handled a privacy matter, tell us first — we would rather fix it. If that goes nowhere, you can complain to the Office of the Australian Information Commissioner.

---

See also the Terms of Service.