Privacy policy

Public Steam data, including people who have never used this site

The main purpose of Database.TF is to record the history of TF2 items. To do that we collect information that is already public, mainly from Steam, about players whether or not they have an account here:

• Steam IDs, display names, avatars and custom profile URLs
• The contents of public TF2 inventories
• Item details, including the Steam IDs of an item's crafter and gifter
• Which account held an item, and when we saw it there

Approved users can see this on item and profile pages. We keep it with no fixed end date, because the history is what the database is for. If an inventory is private we cannot update it, but records we already made remain. We don't remove these records on request; see your choices.

Your account

You don't need to give us your name, email address or payment details to use Database.TF. You sign in on Steam's own page, so we never see your Steam password. Steam tells us your Steam ID, and we store it with your first and last sign-in times, your access level, and a hashed session token. Sessions last seven days.

We use two cookies, both needed for signing in: one keeps you signed in, and one protects the sign-in itself and is removed when it finishes. We don't use analytics, adverts or tracking cookies.

Using the site

We record which account requests inventory refreshes, item inspections and profile lookups, so we can apply usage limits and deliver the results. These records are removed after a limited time; daily lookup counts are kept for about two days.

Your IP address is used in memory to limit request rates. We don't store it in our database or keep web access logs. Error logs are kept for running the service and are filtered to exclude credentials and request contents.

The browser extension

The optional Database.TF Companion extension keeps its settings and your extension token in your browser. On the sites it supports (Steam, backpack.tf, marketplace.tf and mannco.store), it sends us the item IDs and inspect links on the pages you view, and the Steam IDs of inventories you open, along with your token so that requests count against your account.

It doesn't have access to your cookies or Steam sign-in, and it doesn't report your activity on other sites. Tokens expire after 90 days and are deleted 30 days later. Records of what the extension submitted are kept for 30 days.

Game servers

If you use Inspect in Server, we store your Steam ID with the request and the server that handled it until the request is cleaned up. Connected game servers report the Steam IDs of players on them, which we keep only while those players are connected.

Where data is stored and who else handles it

Our data is stored in the United States, on Amazon Web Services, in an encrypted database with daily backups kept for seven days. Requests we make to Steam pass through a proxy provider, which handles the public Steam IDs in those requests. When you browse the site, your browser loads images directly from Steam, so Valve can see your IP address as it does on Steam's own sites.

We don't sell personal data or show adverts. We only disclose data if the law requires it.

Your choices

If you have a Database.TF account, email privacy@database.tf to ask for a copy of your account data, to correct it, or to delete your account. We'll check that the request comes from the account's owner, normally by asking you to make a temporary change to your Steam profile.

We don't remove public Steam data on request. It comes from information Steam already makes public, and it forms part of the historical record of items that other people rely on. To stop us collecting new inventory data, set your Steam inventory to private; records we already made stay in the database.

Depending on where you live, data protection law may give you further rights, including the right to complain to your local data protection authority. Database.TF is not intended for children under 13, the minimum age for a Steam account.

Changes

If this policy changes, we'll update it here and change the date at the top. If a change is significant, we'll tell signed-in users on the site.