Settings

Your library

Your saved games, ratings, private notes, play history, weights, completed and unfinished Showdowns, Daily attempts, portable preferences and watched-game choices are stored in this browser. Connecting optional Google Drive sync uploads these records to your own Drive. Library records are not included in site analytics. Downloaded backups contain private notes; keep them somewhere safe.

Google Drive (optional)

These disclosures apply wherever optional sync is available. If you connect Google Drive, Pixelog synchronizes your journal, including private notes and play history, in a hidden Pixelog folder in your own Drive, using your storage. Its permission is limited to application-specific data in that folder, not your other Drive files. Google stores and processes that copy; it is not end-to-end encrypted.

Journal files travel directly between this browser and Google. Pixelog has no server-side journal database. Its servers process Google authorization tokens during requests. A refresh token is kept in an encrypted, HttpOnly cookie on this device that page scripts cannot read. Its 180-day cookie lifetime renews when used. Short-lived access tokens are held in browser memory to communicate with Drive; they are not saved in browser storage.

Drive stores historical changes and complete journal checkpoints. Editing a note or deleting a game does not erase its earlier content from that history. Historical files remain until the corresponding Drive library is explicitly removed. Expiry of an item in the recovery list does not erase its cloud history.

Disconnecting in Settings → Google Drive stops this device from syncing and leaves the local journal and Drive files in place. Use Settings → Delete data to request removal of the current Drive library. Removal does not erase other Drive libraries, local copies on other devices, or downloaded backups. Delete those copies separately. Keep the app open until removal finishes; if it fails, follow the displayed recovery instructions before disconnecting.

Umami counts Drive connection and completed restoration actions without journal data. Background sync cycles send no analytics. Copied sync diagnostics contain codes and counts only, never titles, notes or tokens. A change saved only on this device is lost if this browser's storage is cleared before the change reaches Drive or you export a backup.

Pixelog's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements. This commitment does not represent Google certification or endorsement.

Steam import (optional)

After you verify with Steam, your owned games load for review. Steam hours come with the games you choose to import. Ratings and notes stay in your journal and are not sent to Steam. Pixelog processes your Steam ID to verify ownership and fetch your library. An encrypted, HttpOnly proof cookie containing that ID expires after 15 minutes. Fetch protection stores pseudonymous hashed Steam account counters and request times in Redis. These are used to enforce request budgets, not to identify visitors for analytics. Entries age out of the rolling budget within 24 hours; inactive budget keys expire within 24 hours and one second. Redis receives no raw Steam IDs, IP addresses, game lists or journal content from this protection. The games and hours you import remain in your journal until you delete them.

Pixelog's Vercel server processing and Upstash Redis counters are configured in the United States (Washington, D.C. region). Hosting providers may route traffic through other countries. The Steam games and hours you select are stored in your browser, in the country where you use your device, and in your own Google Drive if you enable sync. Google controls the location of that Drive storage under its terms; Pixelog does not select or guarantee its country. Downloaded backups are stored wherever you save them.

Pixelhub game lookups (optional)

Personal game lookups are off until you turn them on in Pixelhub. Then Pixelog sends the public IGDB IDs of up to 12 games you play or rated recently and up to 40 Want to play games to its server, which asks IGDB for release dates and Steam app mappings, then sends the mapped public app IDs to Steam for official announcements. No titles, ratings, notes, playtime or Google Drive data are sent.

The server caches the public answers by game, not by visitor, and keeps no record of who asked; the hosting provider's ordinary request logs may include the requested IDs and ordinary request metadata. The selected IDs can reveal game interests; they are not anonymous just because the IDs are public. Pixelhub never changes your journal. With lookups on, this device remembers when Pixelhub last showed you news, so newer posts can say New. Turning lookups off stops them and removes that time and the copy Pixelhub keeps on this device for offline visits.

Opening Pixelhub also requests shared public lists of upcoming and recently released games from IGDB through Pixelog, even when personal lookups are off. This request includes no journal game IDs, and the platform you pick for those lists stays in this browser. Steam sale dates come with the page and need no request. Calendar files Pixelhub offers are made in this browser and hold only game titles, release dates and platforms, or Steam sale dates. Saved answers remain in this browser until cleared. Server cache freshness windows range from 30 minutes to 24 hours; they do not define hosting-log retention.

Patch alerts (optional)

You can search for any game in Patch alerts without adding it to your journal. Pressing Search sends the game name you entered to Pixelog and IGDB, using the same game-info search as Add game. Typing alone sends nothing. Choosing a result saves only its public IGDB ID and title to this device's alert list.

Patch alerts are off until you press a game's bell or turn them on in Settings. While on, Pixelog sends the public IGDB IDs of the games you chose (up to 12) to its server, the same request Pixelhub makes, at most every 30 minutes while Pixelog is open. If you allow notifications and have Pixelog installed in a browser that offers background sync, the browser may also run that check about twice a day while Pixelog is closed. No titles, ratings, notes, playtime or Google Drive data are sent, and the chosen IDs can reveal game interests in the same way as Pixelhub's. While alerts are on for some games, Pixelhub's updates show only those games and ask for their news when you open Pixelhub, even with game lookups off.

Your chosen games and their titles are included in full private backups and Google Drive sync. Found patch notes, delivery state and the switch that activates checks stay on this device. Receiving a watched-game list never enables checks or asks for notification permission. Turning alerts off keeps your chosen games. Deleting journal games keeps the separate watchlist; remove watched games in Patch alerts. Notifications appear only if you allow them in this browser.

Pixelog Daily

Your Daily guesses, results and streak are saved in this browser. Full private backups include all retained days, including unfinished attempts. When Google Drive is connected, these attempts and results synchronize so you can resume on another device. Pixelog retains the newest 800 days. To show the day's cover, Pixelog asks its server for that one game, the same game for everyone. Game facts come from Wikidata.

Taste Battle

A battle lives in its link, after the # sign, which browsers never send to a server. It holds only the game titles, optional IGDB game and cover IDs, optional Verdicts, an optional display name you choose and, for a themed battle, the theme. It never holds notes, play history, hours, category scores, rating dates or library IDs. A theme such as “rated in 2026” shows that your picks were rated that year, but not when. A reply link you send back holds your own Top 10 the same way, plus the battle you answered: its titles, IGDB game and cover IDs and its sender's display name, never its Verdicts. To give the link a short address such as pixelog.my/b/Ab3dEf9h, Pixelog's server keeps those same fields for as long as the link might be shared, without expiry, and nothing else about you. Anyone you send a link to, and anyone they pass it to, can read those fields. Ask through Contact to have a short link removed.

Opening a battle loads covers by their image IDs only. Adding battle games to your library is optional and fetches each game's details by its IGDB ID, one at a time. Analytics and page views never include the link.

Indie game submissions

Developers submit games through a form hosted by Tally. It asks for the game's details, a name or studio, an email address and permission to feature the game. Pixelog uses the email only to reply about that submission, never for marketing, and deletes a submission on request. A game appears in Indie picks or Pixelog Daily only with that permission.

Fresh Top 10s on Pixelhub

When you create a Top 10 card with “Show this Top 10 on Pixelhub” ticked, Pixelog's server stores that list for everyone to see on Pixelhub: the game titles in order, their IGDB game and cover IDs, the time, and your card username or a number such as PixelogUser#12. It never includes Verdicts, notes, play history or anything else from your journal. Untick the box before creating the card to keep the list to yourself.

A list stays for 90 days. Each browser has one list on Pixelhub: a new card replaces it, and Remove from Pixelhub deletes it, from the browser that published it. To keep your number, this browser holds a random token that the server stores only as a hash; the server keeps no account, email or address. Publishing is rate limited by a keyed hash of your network address, as searches are. Ask through Contact to remove a list you can no longer reach.

Analytics

Pixelog uses Umami Cloud and Vercel Web Analytics to compare page counts. No Pixelog account or analytics cookie is used. Umami also receives the listed product events without library data. Umami respects Do Not Track. Both services receive page addresses without their query string or fragment, so a game title or Taste Battle in an address never reaches analytics. Vercel receives page and route data, referrer, coarse location, browser, operating system, device type, and event time, with no Pixelog custom events.

Search counts

Successful game-discovery search terms are filtered by Pixelog's server and sent to Umami as individual search-count events. The event includes the filtered term, not only an aggregate total. Pixelog adds no visitor identifier to these events, but filtering cannot guarantee that a term contains no personal information. Avoid entering private information into game search.

Search counting is skipped when Umami is unavailable, opted out, offline, or Do Not Track is enabled. It never delays or breaks search.

IGDB

Searching sends the query through Pixelog to IGDB. Refreshing game info sends IGDB identifiers. Finding missing covers searches imported game titles. Your personal ratings and notes are not sent to IGDB.

Covers

IGDB covers load through Pixelog's server and may be cached by the hosting provider.

Files you share

Sharing or exporting creates files from the fields shown in that flow. Public shares exclude private notes. Downloaded backups include them. Pixelog cannot erase files you download, send to someone else, or save to another service.

Feedback

Send feedback opens Tally in a new tab. Pixelog adds no library data to the link and does not read your response. Don't paste private notes or backup contents.

Browser storage

Browser storage protection can reduce automatic clearing. Keep a backup too.

Contact and privacy requests

Pixelog is operated by Pixelog Team. For privacy questions or to request access, correction or deletion of personal information handled by Pixelog, email hello@pixelog.my. Applicable privacy rights depend on your location and the processing involved. Do not email private notes, backup files, passwords or authorization tokens. Pixelog cannot remotely access or erase a journal stored only in your browser; use the deletion controls on each device.