Privacy Policy

The controller for this website is the operator listed in the Legal Notice. You can contact the operator about privacy matters at ttrscorecalc@wp.pl.

TTR Calc calculates Ticket to Ride scores in your browser. The score entries you type into the calculator are processed on your device and are not sent to a backend service for solo scoring.

Multiplayer rooms use a backend service to store temporary room state and synchronize players. The site does not currently provide user accounts, login, payment processing, contact forms, advertising scripts, or production analytics scripts.

The current site handles only the information needed to operate a public browser-based calculator and respond to requests.

• Score entries typed into the calculator stay in your browser and are not submitted to the operator in solo mode. In multiplayer rooms, the current player's score snapshot is submitted to the backend so the room can restore the score after refresh and reveal the leaderboard when the room is ready.
• Browser storage stores your consent choices and, if you allow preferences storage, your selected theme mode. Multiplayer also stores a pseudonymous browser-local player ID under localStorage: ttrCalc.playerId. The calculator can remember the last custom player name under localStorage: ttrCalc.playerName.
• Multiplayer rooms store the room code, creation locale, room membership, user-entered player name, selected player color, submitted score snapshot, calculated score totals, reveal confirmation state, and recent room history returned for the same player ID.
• Server access logs may include IP address, date and time, requested URL, user-agent, response status, and referrer when provided by the browser. Multiplayer API URLs may include the player ID because it is used as a technical identifier for room actions.
• If you email the operator, the message, email address, and related correspondence are processed to answer the request.

TTR Calc currently uses localStorage rather than traditional HTTP cookies. Necessary storage remembers your cookie choices. If you consent to preferences storage, localStorage also remembers your selected theme mode. Multiplayer room participation uses localStorage: ttrCalc.playerId to recognize the same browser across room actions and recent room history. The calculator may also store the last custom player name under localStorage: ttrCalc.playerName so new score sheets and join forms can reuse it. Clearing browser storage removes local player recognition for multiplayer rooms and the remembered player name. You can change cookie choices at any time from Cookie settings in the footer.

Multiplayer rooms are temporary shared scoring spaces. Other room participants can see player names, player colors, membership, and reveal readiness. Scores remain hidden from other players before reveal. After reveal, the leaderboard and score totals are visible to room participants and may be visible to anyone who has the room URL.

Public room URLs, shared room links, and QR codes contain only the locale and room code. They do not contain the browser-local player ID. Player IDs may still appear in backend API URLs and access logs as pseudonymous technical identifiers.

Standard web server logs are created by Caddy when the site is requested. These logs are used for security, diagnostics, basic traffic statistics, and analysis of how the site operates. Server logs are retained for 90 days. The production Caddy configuration removes Authorization, Proxy-Authorization, Cookie, and Set-Cookie header values from encoded log output.

The information above is used only for the purposes described in this policy.

• Necessary browser storage is used to remember your consent choices and support core site operation.
• Optional preferences storage is based on your consent and stores the selected theme mode.
• Multiplayer player ID storage is used to provide requested room participation, score saving, room history, and leave/reveal actions for the same browser.
• Server logs are processed for the operator's legitimate interests in security, diagnostics, abuse prevention, and understanding basic traffic levels.
• Email correspondence is processed to answer your request and, where necessary, to handle legal claims or comply with legal obligations.

We do not sell personal information. If analytics, advertising, or other third-party scripts are added later, this policy and the cookie choices will be updated before those scripts are loaded.

Personal information may be processed by infrastructure and email service providers used to operate the website and handle correspondence. It may also be disclosed to public authorities if required by law.

The service is intended to be operated from EU or EEA infrastructure. If a processor or service that transfers personal information outside the EEA is introduced, this policy will be updated before that processing begins.

• Consent choices and theme preferences stay in your browser until you clear browser storage or update your choices.
• The browser-local multiplayer player ID stays in your browser until you clear browser storage.
• Multiplayer room data is temporary and is retained for 7 days from room creation by default.
• Server access logs are retained for 90 days.
• Email correspondence is kept only as long as needed to answer the request, maintain necessary records, or handle legal claims.

Depending on your location and the circumstances, you may have rights to access, correct, delete, restrict, object to processing, or request portability of personal information. Where processing is based on consent, you may withdraw that consent at any time without affecting processing that happened before withdrawal.

If you are in Poland or the European Union, you also have the right to lodge a complaint with a supervisory authority, including the President of the Personal Data Protection Office in Poland (UODO).

To exercise privacy rights or ask questions, contact ttrscorecalc@wp.pl. The operator may ask for information needed to verify and handle the request.

The site is intended to run over HTTPS. Access to deployment systems and logs should be limited to the operator and necessary service providers. No internet service can be guaranteed to be perfectly secure, but the product is intentionally designed to avoid accounts, payments, and permanent multiplayer score storage in the current phase. The player ID is not authentication; anyone with a room link may be able to access the room page according to the room state.

This policy may be updated when the site changes. If production analytics, advertising scripts, accounts, or other data-handling features are added, this policy and the cookie choices will be updated before those features are used in production.