What Analytics measures
Only events that are useful for improving the game are recorded:
- page entry, discarding reloads detected as F5, pull-to-refresh or automatic refresh, and opening of the game;
- start and completion of a fight, stage and pace of the welcoming difficulty, as well as the explicit request to play the next fight;
- the number and sum of points credited when the fight is lost to one of the two house identities (the Student and Mestre Bibico);
- the chosen style, the style randomly drawn for the opponent and the categorical origin of the rival: position ahead, last in the ranking, the person who invited you, or Bibico. The invitation does not change the pace of the fight;
- the technique attempted, the style and the outcome: success, failure, escape or submission;
- XP awarded to attempts, degree progress and belt promotion; when an achievement is shown after the fight, we record only the family of the milestone: fights, wins, submissions, streak, belts, medals or golds. We do not send the value of the milestone or the counter;
- sharing of the promotion: whether it was a belt or a degree promotion, the path used (image, text, download, copy) and the outcome. The name, the belt and the link with the invitation code carried by the card are not recorded;
- display, tap, sharing and aggregate confirmation of invitations, separated only between the home screen and the ranking;
- deliberate opening of the support explanation, tap on the secure button and redirection to the Stripe payment page, as well as confirmation, failure, expiration or refund reported by Stripe;
- use of the access that takes the account to another device: opening of the panel, revealing or copying the code, QR, signing in with another code, advanced options, change or cancellation of the change, attempt and outcome of the link, separated only between QR and typed. The code itself is never recorded, not in full, not in part, and not in encrypted form;
- categorical result of choosing the ranking name: accepted, already in use or rejected because of its format. The name attempted is not recorded;
- explicit actions on the profile: opening the progression details, opening the name editor and moving on to the next fight. Only three closed categories are included, with no name, XP, belt, milestone, position, address or text. These counters do not allow the actions to be linked to the same person or an individual funnel to be reconstructed;
- use of technique details, replay, opening of the steps and selection of a step number to view its frame, rest, ranking, loading more rows, jumping to your own position and returning to the top. For the ranking, only the action, success or failure and a closed depth band are included; numeric position, name and cursor are not sent. We also measure language changes and changes between the three sound modes: effects only, music with effects and mute. The step text and the frame image are not sent. The device volume, the sounds played and the listening time are not recorded.
- on the Learn screen: the technique that started or completed the 3D demonstration, including each repetition, and the number of a step reviewed after completion. Pausing, resuming and changing the speed are not recorded. The step text, the time watched, the pose and the frame are not sent.
- opening, completion or skipping of the avatar creator, slots changed and final values saved for sex, skin, hair, hair color and kimono. Each choice becomes an independent counter, with no identifier that would allow someone's complete avatar to be reconstructed. The dashboard compares only aggregate distributions by characteristic, separating the first creation, before the first fight, from editing done later through the profile.
- category of a short dojo maxim shown before the first move. We do not record the text, the rival, the seed, the profile or the click on continue.
- historical total of openings of the hidden JDX teaser, which has been removed from the game. The panel still shows this old total, but no new event of this type is sent.
- method of confirming the technique and the style, effective speed chosen and whether the replay was paused or resumed, leaving the fight and confirmation before leaving the game. On leaving, only the categorical screen or the score, which third of the fight the person was in (beginning, middle or end), a broad band of fight duration, the active panel, the method and whether the person stayed or left are included. We do not record the time watched, frame, pose, written reason, idle time or identity.
- safe automatic update of the game on the home screen. Old categories, from when the update was manual, may remain in the historical totals.
- invitation, opening, postponement, failure and submission of feedback, as well as the aggregate ratings for understanding of the techniques, clarity of the steps and willingness to play again.
- aggregate operation of the ranking protection: reservations, adaptive challenges and replays accepted or rejected, separated only by closed categories. Player, IP, token, seed and log are not included.
- transfer of the account from the old address, bjj.patrickcarmo.com, to jitsudex.com: ticket issued, accepted or rejected and the categorical reason for the rejection, arrival with another account already open in the browser and the choice made in that case. Account identifier, ticket, visited address and name never enter these sums.
- origin of the visit when it arrives through one of our promotional links tagged with the channel: Instagram, TikTok, Reddit, itch.io or YouTube. We read only that tag from the address, accepted only when it is on this closed list, keep the channel in the memory of the tab while it is open and remove it from the address right away. We count, per channel, the visit and the first fight started and completed during that same visit. We do not record the address, the page the person came from, the post or the campaign.
- a click on one of the links to our official profiles on Instagram, TikTok and YouTube, found in the footer of the home screen. We count only how many clicks each network received. The icons are drawn by the game itself, so nothing is loaded from those networks while you play. When you open one of those links you leave JITSUDEX and the policy of the chosen network applies.
- in the online ranking: the choice between the overall and online tabs, a tap on the find match button while the online ranking is still empty, the invitation to create a name seen or accepted there, and the end of online match card, whether it appeared and was tapped and whether the match counted, went over the limit of 3 matches per day against the same person or ended before the online ranking started. We do not send position, points, name, opponent or the match identifier.
- on another player's public profile: whether it opened, whether the name had no profile or whether opening failed, separated only by origin (general ranking, online ranking or profile link), and use of the share profile button: tap, share, link copy or cancellation. We do not send the name of the person viewed or of the person viewing.
- in the daily challenge: the card seen on the home screen (once per day), a tap on it, opening the challenge screen, arriving through the challenge link and sharing the result, split between the device share sheet, copying and manual copying. From the server we count accepted attempts, attempts refused because the day was already used and completed fights, by win, draw or loss. We do not send the shared text, the score, the position, the name or the day.
- in missions: when the challenges section on the home screen is opened or closed and, from the server, each completed mission, split only by period (week or month) and by mission type. We do not send the technique, the target, the XP, the name or the account.
The server immediately turns these events into daily counters. There is no table with the individual journey of each visit.
An entry is a technical navigation, not a unique person. The same person may come back at another time and be counted again. Older versions of the game could still count F5; historical data is not rewritten. Known user agents of robots, crawlers, previews and headless browsers are also discarded, without turning the rest into a count of unique humans.
The XP of a fight is divided among the attempts made, without creating a fight identifier. Invitations are counted by stage and result, never by the name or code of whoever sent or received them.
The rival's public name may appear in the game, but it never enters Analytics. The metrics receive only the category that originated that name, and credits are summed without nickname, position, identity or link between players.
Aggregate context
The counters can be separated only by:
- day;
- game language;
- broad device category: mobile or desktop;
- approximate country reported by the Cloudflare infrastructure;
- technical version of the game.
What Analytics does not collect
- name, nickname, email or payment data;
- cookies, cookie content or local storage;
- user ID, session ID or persistent identifier;
- IP address stored by the application;
- browser fingerprint;
- click coordinates or individual browsing history.
Analytics requests are sent with credentials omitted, so not even a possible functional ranking cookie travels with them.
Cloudflare Web Analytics
We also use Cloudflare Web Analytics for pageviews and page performance. This service does not use cookies or browser storage and does not track people across sites.
Technical error diagnostics
When the game fails in the browser, we send a small technical record in order to find and fix the problem. It may contain the error category, sanitized message, relative file path, line, column, game version, language, device category and approximate country. Identical errors are grouped. The panel shows at most the last 30 days, and older records are gradually deleted in batches.
Before sending, and again on the server, we remove email, access code, UUID, local nickname, URL parameters and fragments. We never send identity, name, cookie, IP address or IP hash, full URL, stack, current screen, sequence of actions or individual journey. Errors from external files are included only as a counter, without message, file, line or column.
This operational diagnostic uses omitted credentials and happens even with Global Privacy Control or Do Not Track enabled. Those preferences still disable the product events described on this page; the limited exception exists only to detect broken software, without measuring behavior.
Voluntary support and Stripe
The support option first opens an explanation inside the game. It does not start a payment and can be closed without calling the server. Only the secure support button opens a page hosted by Stripe. Stripe processes the data required for the payment under its own terms and privacy policy; JITSUDEX does not receive or store card numbers or banking credentials.
This Analytics includes only counters by stage, method and currency, as well as the aggregate total in cents after a signed notification from Stripe. We do not copy name, email, payment identifier, charge or checkout session. A minimal technical receipt of the Stripe event is kept only to prevent duplicate counting on resends.
Openings of the explanation, clicks and checkouts delivered can be separated only by the categorical origin of the option. Clicks can also be separated by language, device category and approximate country. Confirmed payments do not carry the origin. This data remains aggregated and does not make it possible to know which person clicked.
Functional game data
Separately from Analytics, the browser may store locally your progress, language, sound preference, optional ranking name and pending submissions while offline. This data enables features requested by the player and can be erased by clearing the site data.
When you join the ranking or use a referral link, a primary technical identity may be created to accumulate score and bonuses. It is neither read nor sent by the Analytics system.
This identity is kept in a functional cookie, jdx_player_v1, signed by the server, inaccessible to the page's scripts and valid for one year. The cookie from the old address, bjj_player_v1, is still accepted and is rewritten under the new name on the first visit.
To take the account to another device without registration, the server stores an access code linked to this identity. It is shown only to someone who is already in the account and can be replaced by a new one.
To limit abuse and excessive requests, the server stores a cryptographic digest (hash) of the IP address, calculated with a secret value, together with the creation of the identity, the invitations, the fight reservations and the counts of recent attempts. The application does not store the IP address itself.
Each ranking fight receives a random configuration from the server, and the result is accepted only if the server can replay the moves. In abnormal functional patterns, the next fight may ask for a Cloudflare Turnstile verification. The verification is performed by Cloudflare, which receives the token and the IP address of the connection. The token is verified and discarded; it does not enter the ranking or Analytics. All valid fights continue to count in full toward the cumulative score.
To set up the next fight, the server may look up the current position and return the public name of the rival immediately ahead or of the last active player. For most rivals, the name serves only to present the opponent, and the result scores only for the person who submitted their own match.
There are two fixed exceptions: the Student and Mestre Bibico, the house identities. When the fight is against one of them, a random identifier, linked to the technical identity and valid for a limited time, makes it possible to credit their win only once if you lose. This use is functional and separate from Analytics.
If you choose to send feedback, we store the message, your ratings, your public ranking name (when there is one) and your email only if you provide it in order to receive a reply. This data is kept in a private inbox of the JITSUDEX administrator, separate from the anonymous Analytics, and is not used for advertising or visitor profiles. You can send new opinions whenever you need to. The form does not trigger automatic email messages: the contact stays available in that private inbox until the administrator reads it.
Anyone who chooses a ranking name has a public profile, opened by tapping the name in the ranking or through the link jitsudex.com/p/ followed by the name. It shows only what the ranking already shows: the name, the avatar, the belt, the number of fights, wins and submissions and the tournament medals. The access code, the invite code and the account identifier never appear in it.
In the daily challenge, the server keeps, per account and per day, the attempt, the result, both sides’ points and the rounds of the fight, to guarantee one attempt per day, build the daily ranking and count the day streak. The daily ranking publicly shows the ranking name and the score of everyone who completed the challenge.
For the weekly and monthly missions, each submitted fight keeps a few of its counters next to the result (successful moves per technique, takedowns, sweeps, guard passes, defenses, points and arrivals at mount and back). The server adds these counters up per week and per month to show your progress and award mission XP; nobody else sees these numbers, and the public profile only shows how many missions and challenges you completed.
Move to jitsudex.com
The game moved from bjj.patrickcarmo.com to jitsudex.com. Anyone who opens the old address with an account is taken to the new one with a ticket signed by the server, which identifies the account, is valid for 60 seconds and can be used only once. Without an account, the old address only redirects.
In the same transfer, the data that the browser kept at the old address (ranking name, progress, avatar, language, sound and speed preferences, championship in progress, pending submissions, state of the feedback invitations and multiplayer style) travels in the URL fragment, the part after the # sign, which the browser does not send to the server. The game stores it locally only where there was no data yet and removes the fragment from the address bar. If the ticket is rejected, this data is discarded.
If the browser already has another account open at jitsudex.com, nothing is switched without your choice: a 15-minute functional cookie, jdx_ponte_escolha, keeps track of which account arrived until you decide.
Anyone who already played at jitsudex.com before the move has the local data of that version (name, profile, language, sound, speed and state of the feedback invitations) copied once to the current version. Nothing is deleted.
The accounts of the old JITSUDEX were brought into this database with their history of fights and points. Two accounts, one from each site, with the same ranking name, regardless of upper or lower case, became a single account, with the points added together. Signing in through either of the two, by the cookie or by the access code, opens the merged account.
Match call notifications
In multiplayer mode you can turn on alerts that call you to a match when someone is looking for an opponent. This is optional, starts turned off and only happens after you tap the control that explains what it is for and the browser grants permission. On iPhone and iPad, alerts work only with the game installed on the home screen.
When you turn them on, we store, per device, the technical address that your browser generates to receive notifications, the two encryption keys it provides with it, the chosen language and the translated text that the device should display. This address is necessary to send the notification and is treated as a secret: it does not appear in any response, not even to you, it is not logged and it does not enter the anonymous Analytics.
You choose between always-on alerts, alerts for two hours, and off. In always-on mode, the server does not send between 11 p.m. and 8 a.m. in the device's local time. For this we store only the current time zone offset in minutes, updated when the game opens. It is functional data, does not enter Analytics and is not used to identify or track anyone. In two-hour mode, availability ends automatically at the end of the period.
When someone looks for a match and finds no one, we call a small group of available people, at most three per search, and the first one to accept takes the spot. We never notify all subscribed people. Each person receives at most six alerts per day, with at least twenty minutes between two alerts. The content sent is only the random identifier of that call plus the text your own device requested, in its language, which may include the public ranking name of the person who is searching and that person's position in the ranking, when they exist. This content travels encrypted: the browser's notification service cannot read it.
If you remain in the queue with the game suspended, we may also notify you that the match was found and must be accepted within thirty seconds. This alert is sent at most once per match and person. It carries the random identifier of your own match, removed from the address bar as soon as the game opens, and never carries data about the opponent.
Apart from that public name and the position, the notification does not carry the identifier or style of the person who is searching. You can turn off alerts in the same place where you turned them on, with one tap, and this deletes both the subscription in the browser and the record on the server. If you clear the site data or revoke the permission, the notification service reports that the subscription no longer exists and we delete it on the first send attempt.
The notification test sends only to the device that requested it. First we record whether the browser received the push and accepted the display request. Then you confirm whether you actually saw it or not. This answer is linked only to the functional batch of the test and is not sent to the anonymous Analytics.
About the anonymous Analytics: we count how many people saw the control, how many requested permission and how many granted, denied, renewed or turned it off, which of the three modes was selected and, by reason from a fixed list, how many times the game needed to reconnect to a multiplayer match in progress. We also count on which screen the entry to the alerts appeared or was tapped, among five from a fixed list (home screen card, waiting in the queue, end of an online match, preferences and multiplayer hub), and how many times an invitation was dismissed with not now. The device stores locally only how many times you dismissed it, to stop inviting after the third time. These are sums by category, with no name, no identifier and without your device's technical address, which stays outside Analytics in any form. Global Privacy Control and Do Not Track also turn off these sums.
Matches against another person
In multiplayer mode we store the match itself: who played, who won, the moves and the reason it ended. This is the game itself, and it is what makes it possible to reconstruct the fight, show the result to both sides and check whether someone was gaming the system. This data is available only to the game administrator.
Separately, the anonymous Analytics counts which controls people tap (create room, find match, confirm readiness, request a rematch), whether the room link was shared at all, how long the queue takes to turn into a match and how rock, paper, scissors decided who starts. These are sums by category. The match identifier, the invitation code, your name and your identifier never enter these sums, and therefore they do not make it possible to reconstruct a person's path.
Since November 14, 2026 these matches also make up the online ranking. It is calculated from them and publicly shows, only for those who chose a name, the position, points, wins and number of matches, next to the avatar and the belt. Those who did not choose a name do not appear. The online ranking does not change the overall ranking, XP or belt.
Privacy preferences
The anonymous Analytics respects Global Privacy Control and Do Not Track: when either of these preferences is enabled, the game does not send the events described on this page.
Responsible party and contact
Patrick Carmo is responsible for the JITSUDEX project. This page will be updated if the metrics or their purposes change.
To talk about the game or privacy, or to request access to, correction or deletion of what you sent through feedback, write to [email protected].
Last updated: November 20, 2026.