PRIVACY POLICY
Last updated: June 21, 2026
Short and human: we don't sell your data and we don't collect anything we don't need.
This service makes cards and roasts from public Steam profiles. Below is an honest breakdown
of what's used, why, how long it's kept, and which parts are third-party services.
1. Who we are
This site is an entertainment service that generates cards, receipts, graveyards and
"verdicts" from the public data of a Steam profile. The service is not
affiliated with Valve Corporation and is not an official Steam product. For data-handling
questions you can contact us: contact@steamcard.fun.
2. What data we use
We process exactly as much as the service needs to work and to protect itself:
-
Public Steam profile data that you enter yourself: nickname, avatar,
games list, playtime, level, achievements. Taken through the official Steam Web API and
only if the profile is public. We never ask for your login or password and have no access to them.
-
IP address and technical request data (time of request, page). The IP is
used to protect the service from bots and abuse: rate limiting, detecting automated
scanners, and blocking offenders. An IP can legally qualify as personal data, so we state
this plainly. For load counters the IP is stored as an irreversible hash;
in the security log, when protection triggers, the IP itself may be stored temporarily in
order to block the source of an attack.
-
Cookies and browser local storage: technical ones (language, the fact you
saw this notice, anti-bot service tokens, admin session) and — only after your
consent — analytics (Google Analytics, see section 6).
What we DON'T do: we don't collect or store your logins, passwords or payment
details; we don't sell your data; we don't build ad profiles about you. The only transfer of
data to a third party is anonymized web analytics (Google Analytics), and only if you consented to it.
3. Why it's needed
- Generate a card / roast / receipt from your profile.
- Temporarily cache the result so re-generating is fast and doesn't strain Steam.
- Count overall page traffic.
- Protect the service from spam, bots and abuse (rate limiting, blocking).
4. Cookies and browser storage
We use two categories:
- Necessary (always on): remembering your language, the fact the cookie notice was shown, anti-abuse service tokens, the admin session. The site works incorrectly without them — no consent required.
- Analytics (consent only): Google Analytics. It is not loaded and sets no cookies until you click "Accept" in the banner. If you don't consent, analytics is not connected and the site keeps working.
You can disable or delete cookies at any time in your browser settings.
5. Storage and deletion
- Result cache — on the order of an hour to a day, then expires automatically.
- Counters and rate limits (hashed IP) — short-lived, deleted automatically.
- Security log — IP entries are kept for no more than 4 days since that IP's last recorded activity, then deleted automatically. Blocks: temporary ones lift automatically (usually within an hour), manual ones stay until removed by an administrator.
- Analytics is stored on Google's side per their retention periods.
We don't maintain a long-term user database.
6. Third-party services
- Steam Web API (Valve) — the source of public profile data.
- Google Analytics (Google) — anonymized visit statistics. Loaded only after your consent, with IP anonymization enabled. Transmitted data is processed by Google under the Google Privacy Policy; you can opt out by not clicking "Accept" in the banner, or via the official Google opt-out add-on.
- Pages may contain links to external resources (our channel, partner platforms) — they have their own rules, for which we're not responsible.
7. Your rights
You can withdraw analytics consent (by declining in the banner or clearing cookies and local
storage), and request information about what data is processed about you and its deletion.
Since we keep no user profiles, this usually concerns security-log entries for a specific IP.
To get in touch: contact@steamcard.fun.
8. Changes
We may update this policy. The current version is always on this page, with the update date
shown at the top.
← Back to the site