← Back to the overview

Privacy policy

Last updated:

This policy covers the Do I Own These Games? extension, its public recognition catalogue, this website and the reports and feedback form.

Data stored on your device

When you connect Steam or request a library sync, the extension reads game names and owned Steam app and package IDs. It stores the library, ownership snapshot, sync time, display preferences, custom mappings and cached public recognition data in local extension storage.

On supported store pages, it reads product titles, Steam IDs and relevant game-card content to compare them with your synced library. Matching happens in your browser. Your library and browsing history are not uploaded to the public catalogue service.

Ownership badges and styling are added to the page. The storefront can observe these page changes, including which products are marked as owned.

The extension does not sell your data, use it for personalised advertising or include analytics or advertising SDKs.

Steam sign-in and library syncing

Library syncing starts when you connect Steam or click Sync; it does not run on a schedule. Connecting opens Steam’s own page and completes the requested sync after sign-in. The extension never receives or stores your Steam password. Permitted ownership requests to Steam use your browser’s existing Steam session; the extension does not read, save or export authentication cookie values.

Opening or focusing the popup or settings may check whether you are signed in. This checks a sign-in flag; it does not save your Steam account identity or the page content.

With Steam Store access and a saved ownership snapshot, the extension listens for Steam’s ownership-change signal on supported product, checkout and key-activation pages. It saves a local change counter and detection time. Detecting a change does not start a sync. Click Sync Steam library to refresh ownership. The extension does not read purchase details, payment information, product keys or sign-in fields, or send this signal to the catalogue service.

During a requested sync, the extension may obtain a temporary token from Steam to check additional owned apps through Steam’s library service. Account identifiers, family-sharing information and playtime in the response are processed in memory; only personally owned app IDs and game names are saved. The token is sent only to Steam and is not saved, logged or sent to the catalogue service.

With the relevant Steam permissions and a saved library, unresolved products may be checked against Steam’s public search, product and edition data. These requests send product titles or Steam IDs directly to Steam, without your library, ownership status, storefront URL, sign-in cookies, account token or API key. Steam receives normal connection information, including your IP address. Lookup results are cached locally for 24 hours; temporary failures can retain earlier verified results.

A temporary sign-in progress banner receives status updates, not your library or account details. Session storage holds the tab ID, start time, progress, sync time, any error and dismissal state. Closing the tab removes this temporary state; a pending sign-in expires after 15 minutes and is not resumed after a browser restart. The banner does not read sign-in form fields. Steam can observe the banner added to its page.

If you use the alternative public-profile or Web API sync, the profile URL or Steam ID and any API key you enter are sent directly to Steam. The API key is cleared from the input after use and is not saved by the extension or sent to the catalogue service.

Steam handles its own account and connection data under the Steam privacy agreement.

Public recognition updates

The extension downloads public title corrections and edition definitions from a service hosted on Cloudflare. Checks begin after a Steam connection or alternative import saves a library or ownership snapshot, then run every 24 hours while the extension is enabled in Chrome. Startup checks run only when due. A closed browser or sleeping device can delay a check. The downloaded data is cached locally for use offline. Logging out stops these checks until a library is saved again.

These requests do not include your library, ownership snapshot, Steam profile ID, API key, Steam cookies or the storefront page you are viewing. The catalogue contains public matching metadata, not executable code.

Cloudflare receives normal connection information, such as your IP address, request time, service URL and network headers, to operate and secure the service. The catalogue application does not keep user libraries or a user browsing log. See Cloudflare’s privacy policy.

Catalogue administration is separate from ordinary extension use. Authorised maintainers sign in through Cloudflare Access and its identity provider. Protected revision history records the verified administrator email, time, note, summary and catalogue snapshot for accountability and recovery. That history has no automatic expiry and is not included in public catalogue downloads.

Storage, controls and deletion

Your library and preferences remain in local extension storage until you replace or clear them, or remove the extension. The project does not provide cloud library syncing or keep a remote copy of your library.

  • Under Your data in settings, Log out and delete data asks for confirmation, cancels pending work and deletes all extension storage: your library, ownership snapshot, settings, mappings, caches, request times, change markers and temporary connection progress. It also revokes optional Steam access and stops catalogue checks until you connect or import a library again.
  • Logging out disconnects the extension. It does not remove Steam cookies, sign you out of Steam’s website or delete data held by Steam or a storefront.
  • Removing the extension removes its local data. Exported library files remain wherever you saved them; you control and delete those separately.
  • Turning off ownership marks or a supported store changes the display. It does not sign you out of Steam or delete your Steam data.
  • You can also revoke optional Steam access, disable the extension or remove it in Chrome.

The developer cannot retrieve or delete library data that exists only in your browser.

This website

This is a static site with no account system, analytics scripts, advertising trackers or cookies added by the site itself. Fonts and images are served with the site. The ownership example uses fixed sample data and runs in your browser; it does not read your Steam library.

When the site is hosted, the hosting provider receives normal connection information to serve it, including your IP address and requested page. Any hosting logs are subject to that provider’s practices.

The reports page embeds the form hosted by Tally. Opening that page loads Tally’s form and embed script; neither loads on the overview or privacy pages. Tally receives normal connection information to serve the form. Its embed script forwards the reports page path and any URL query parameters to the form. Submissions and uploaded files go directly to Tally.

Reports and feedback

The report form asks for a category, summary and details. Depending on the category, it also asks for the affected game or edition, store, page link or steps to reproduce. A Steam page, ownership description, country or store region, extension and browser versions, media uploads or links, and reply email are optional.

You can upload up to five images, videos or audio files, up to 10 MB each. For larger files or a collection, use the media-link field. Files you link to remain with the service where you uploaded them, under that service’s privacy practices.

Submitted reports and uploaded files are stored in Tally and reviewed by the project’s developer to investigate matches and bugs, consider suggestions, address website issues or respond to privacy requests. If you provide an email address, it is used only to follow up on your report, not for marketing.

Tally also processes technical information needed to provide and protect its forms. No unfinished responses are collected through Tally’s partial-submission feature, and save-for-later is disabled for this form.

Reports and uploaded files remain in Tally until the developer deletes them; automatic deletion is not configured. You can request access, correction or deletion through the form by choosing Privacy request. Include enough context to identify your earlier report. Provide contact details if you want a reply.

Include only information needed to explain the issue. Remove account details and other personal information from screenshots and media, and do not send passwords, authentication cookies, API keys or payment details.

Contact and policy changes

Use the reports and feedback form for questions about this policy or privacy requests.

Data is used for the ownership and matching features described here, report handling, and service operation and security. It is not sold or used for advertising, credit decisions or lending.

This policy will be updated when data handling changes. The date at the top identifies the latest revision.