Privacy Policy
Inspekt is a renderer. It is built so that showing someone a weapon skin does not require knowing who they are, and this policy describes what that means in practice.
This policy covers how Menu Atlas LLC ("we") handles data in running Inspekt: the embed, the Render API and the Inventory API. It covers both our customers and the visitors who meet the service through a customer's site ("end users"). Terms defined in the Terms of Service carry the same meaning here.
This is not a substitute for your own privacy policy. If you put the embed on your site or call our APIs, telling your own users about it is your job, in your own policy.
1. Scope
This covers the service as we run it. It does not cover your site, your app or your data practices, and it does not cover Steam or Valve, whose own policy governs the inventory and inspect-link data we read from their public services on request.
2. What we collect
2.1 Usage records
Every call to the embed, Render API or Inventory API is written as one usage event holding a timestamp, the API key used, the event kind, whether the response came from cache, whether it was over quota, and a reason code if it was refused.
The API key identifies the customer account, not a person. These records carry no end user identity, no IP address, no device information and no cookie or tracking identifier. The origin a request came from is checked when it arrives and is not written into the record. We use this only to enforce quotas, work out bills, and operate and debug the service.
2.2 The embed
The embed sets no cookies and makes no request to any third-party domain from inside the frame. Every asset and API call it makes goes to our own origin. Viewing it collects nothing about the viewer beyond the anonymous usage event above.
2.3 The Render API
A render is produced from the parameters in the request and cached under a hash of those parameters, never under anything identifying the requester. Nothing about who asked is stored with a cached image.
2.4 The Inventory API
This takes a Steam ID, vanity name or profile URL from the caller and looks up that account's public CS2 inventory through Steam. The result is held in server memory for up to 5 minutes, capped at 200 accounts with the oldest evicted first, and is never written to disk. We do not build a database of anyone's inventory.
The caller's IP address is held in memory for a sliding window of roughly 60 seconds, purely to enforce a per-IP rate limit that keeps us from hammering Steam. It is discarded when the window goes idle, is not written to any log, and is not linked to the usage records in 2.1.
2.5 Infrastructure logs
Our hosting and network layer may incidentally record connection metadata such as IP addresses, the way any web server does. The application behaviour described above does not itself keep an end user's IP beyond the transient rate-limiting use in 2.4.
2.6 Customer account data
To run your account we hold your API keys, account or business name, plan, registered origins, quota and overage settings, and account status. This is business data about a customer, not data about end users.
2.7 Dashboard sign-in
There is no password. You enter your email, we send a one-time sign-in link, and following it creates a signed-in browser session. This stores your email address against your account for as long as the account exists; the sign-in link as a hash of its token, never the token itself, with the requesting IP and a timestamp; the session as a hash of its token with a truncated user-agent string; and a CSRF token used only to confirm a dashboard action came from the dashboard.
Sign-in links are delivered by email through our mail provider. A successful send is recorded as the fact that it happened, with the recipient, time and message id, and without the link, so a working sign-in leaves no usable copy of its own token on our servers. If a send fails, the link is written to an operational log so we can pass it on by hand, because at that point it is the only way you can get in. Those entries are purged after 30 days.
2.8 Billing
Payment card and billing details are handled by our payment processor, Stripe, under its own privacy policy. We never store full card numbers. We hold the identifiers Stripe gives us for your customer and subscription, plus your plan and billing status.
3. What we do not do
- No advertising trackers or pixels inside the embed.
- We do not sell personal data.
- No cross-site tracking cookies.
- No device fingerprinting of end users.
- No retained database of Steam inventories beyond the 5-minute cache in 2.4.
- No password for the dashboard, so no password to lose.
4. Why we process it
To enforce quotas and calculate bills; to run, secure and debug the service; to prevent abuse, which is what the per-IP limit in 2.4 is for, and it exists as much to protect Steam from us as us from anyone; to sign you in to your own dashboard; and to meet legal obligations.
5. Who we share with
- Steam and Valve. An inventory lookup or inspect-link request necessarily means we ask Steam's public service on the caller's behalf.
- Our mail provider, which carries dashboard sign-in emails and therefore sees the recipient address.
- Stripe, our payment processor, for billing.
- Hosting and network providers, as far as running the service requires.
- Law enforcement or others, where the law or legal process requires it.
We do not sell customer or end user data to anyone for their own marketing.
6. How long we keep it
| Data | Retention |
|---|---|
| Raw usage logs (2.1) | 13 months, then deleted automatically |
| Monthly usage totals | Life of the account, for billing history and disputes |
| Inventory cache (2.4) | 5 minutes, or sooner if evicted. Memory only |
| Rate-limit IP data (2.4) | About 60 seconds. Memory only |
| Customer account data (2.6) | Life of the account, plus what we need afterward for legal, billing or dispute purposes |
| Unused sign-in link | Expires after 15 minutes |
| Used or superseded sign-in link | 1 hour, so a failed attempt can be investigated |
| Session | Up to 30 days, or 14 days without activity |
| Failed-send mail log (2.7) | 30 days |
The 13-month figure is enforced by a purge that runs in the service itself, not by a note in a calendar. Thirteen months covers a full year of billing plus the month in progress.
7. Security
Access to usage data and customer account data is limited to people who need it to run the service. The public API surface is protected by the origin allowlist and quota checks described in the Terms. Administrative write access to our own systems is separately controlled and is never granted by a customer API key.
Sign-in links and session tokens are stored only as hashes, so a copy of our session store does not let anyone sign in as you. Mail is sent over TLS, and our mail client refuses to authenticate over an unencrypted connection rather than fall back to one.
We claim no security certifications. We are a small operation and would rather say so than imply otherwise.
8. Your rights, and how to reach us
If you are an end user with a question about data collected through a site you visited, ask that site first. We generally cannot identify you from the anonymous usage data in 2.1, which is the point of collecting it that way.
For data we hold ourselves, write to hello@inspekt.gg. You can ask for a copy of the account data we hold about you, ask us to correct it, or ask us to delete your account and the data tied to it, subject to what we must keep for legal and billing reasons. We will respond within 30 days.
Depending on where you live you may have further rights, including under the GDPR or the CCPA. Write to the same address and we will handle the request under the law that applies to you. We do not sell or share personal information as those laws define it.
9. Children
The service is not aimed at children and we do not knowingly collect personal information from them. Customers running a gambling or wagering product have their own age-verification obligations under Acceptable Use section 3.
10. Where data lives
We are based in the United States and process the data described here on infrastructure in the United States. If you use the service from outside the US, you are sending data here.
11. Changes
We update this policy the same way we update the Terms, under Terms section 16.
12. Contact
Menu Atlas LLC
c/o Northwest Registered Agent LLC
7533 S Center View Ct Ste N
West Jordan, UT 84084, USA
By email: hello@inspekt.gg