Change history

A dated record of every version of the five documents that make up the customer agreement, so that you can tell which text you agreed to and when it changed.

Current version: 13 September 2026. This page is a record about the agreement, not part of it. If this page and a document ever disagree, the document is correct.

The short version. A version is a date. All five documents always carry the same date. Changing any one of them makes a new version of the whole set, listed here with what moved. A superseded version stays published and stays linked from this page. For a material change you get at least 30 days' notice by email before it takes effect, under Terms section 16.

1. What is in the set

1.1 The customer agreement is five documents, and they are versioned together:

1.2 The Terms of Service is the main agreement and it incorporates the other four. Where the Terms and one of the other documents conflict on something the Terms address directly, the Terms win. That is Terms 18.1, and this page does not change it.

1.3 Each of the other four says, in its own Changes section, that it is updated the same way the Terms are, under Terms section 16. So there is one notice promise for the whole set rather than five that could drift apart.

2. How versions work

2.1 A version is a date. There is no separate version number to track. The version is the effective date printed under the heading of each document, written out in full, for example 9 September 2026.

2.2 Every document in the set carries the same version. If you are holding five documents that do not all show the same effective date, one of them is not from the set and you should tell us.

2.3 A change to any one document creates a new version for the whole set. All five get the new effective date, including the ones whose text did not move. This is deliberate. It costs nothing and it means "the 9 September 2026 set" identifies exactly one body of text, with no need to reason about which document changed when.

2.4 A correction that does not change meaning is still a version. A typo, a broken cross-reference or a renumbered section produces a new dated version, marked here as editorial, with what was corrected. We would rather over-record than have you find a difference between your copy and ours that this page does not explain.

2.5 The effective date is the date the version takes effect, not the date it was written. For a material change that date is at least 30 days after the notice described in section 4.

3. Where a superseded version lives

3.1 The previous text stays reachable. When a version is superseded, its full text stays published, unchanged, at a permanent URL, and the entry for that version in section 6 links to it. We do not overwrite a document and leave you with no way to read what you actually agreed to.

3.2 This page itself is only ever added to. An entry that has been published is not edited or removed afterwards, except to add the archive link described in 3.1.

3.3 There are four versions today. The 9, 11 and 12 September 2026 sets are all superseded, and each entry in section 6 links to all five documents as they read on the day that version was replaced.

3.4 If you need a copy of the version in force on a particular date and cannot find it here, ask us at hello@inspekt.gg and we will send it.

4. What we commit to telling you

4.1 The promise is Terms section 16, quoted here in full so that this page cannot be read as adding to it or watering it down:

16.1 We may update this agreement. We will post the new version with a new effective date, and for a material change, including a change to fees, the liability cap or the uptime commitment, we will give you at least 30 days' notice by email or another reasonable method first.

16.2 Using the service after a change takes effect means you accept it. If you do not accept a material change, end the agreement under section 10.2 before the effective date, and the old terms apply until then.

4.2 In practice that means the following, and this is what we will actually do:

Email to the account contact on every account, at least 30 days before the effective date of a material change. Not a banner, not a footnote, not this page on its own.
The email says what changed, in plain language, and links to both the new version and the one it replaces.
A new entry here, published at the same time as the email, listing which documents moved and in what way.
The old version keeps applying until the effective date, and if you end the agreement under Terms 10.2 before that date, it keeps applying to you until the agreement ends.

4.3 For a change that is not material we post the new version and record it here, without the 30-day notice period. Section 2.4 still applies: it is still a new dated version.

4.4 The email address we use is the one on your account. Keeping it current is the one thing this commitment needs from you.

5. What does not create a new version

5.1 Only the five documents in section 1.1 are versioned here. The rest of the site is not part of the agreement, and changing it does not create a version:

The documentation, including parameter tables and error codes.
The Pricing page, the comparison page, and anything else that describes the product rather than governing it.
The product itself. What shipped and when is on the changelog, which is a separate page with a separate purpose.

5.2 The exception worth knowing. Several numbers that also appear on marketing and documentation pages are written into the documents themselves: the plan prices, the monthly quotas, the origin limits and the overage rates are in Terms section 5, the uptime commitment is in SLA section 2, and the 7-day new content commitment is in Terms section 9. Changing any of those is a change to the agreement and gets a version and the notice in section 4, whatever else on the site changes with it.

6. Version history

13 September 2026, not material

Three changes, in three different documents, none of which moves a fee, a quota, a liability cap or an uptime commitment.

How we write about regulated customers. Terms 4.2 and Acceptable Use 3 used to single out one trade by name and say we serve it. That sentence did no work: what protects both sides is the set of warranties underneath it, and those are unchanged. Both sections now read on any customer whose business needs a licence, permit or registration, or is subject to age-verification, anti-money-laundering or consumer-protection rules. Nobody is newly excluded and nothing is newly required. Terms 14.2 follows the same move: the limb that named one sector's law now names the obligation, which reaches strictly more than it did. No section number moved; Acceptable Use 3 is still 3, which is what Terms 4.2 and Privacy 9 cite. The link fragment did change, to #regulated, so an old deep link into that section lands at the top of the page rather than at the section itself.
Terms 17.5 is new. 17.2 sends disputes to the courts in Salt Lake County, and 17.2 to 17.4 are written on the assumption that both sides are businesses — which this agreement had never actually said. If the law where you live treats you as a consumer and gives you a right you cannot waive, 17.5 says this agreement does not take it away. It gives something up and takes nothing.
Terms 5.5 says how tax is worked out. Fees have always excluded sales tax and that has not changed. What 5.5 now adds is the mechanics: where we are registered to collect a tax it is calculated at checkout from your billing address, shown before you confirm, and itemised on the invoice; where we are not registered, the fee is the whole of what we charge. If you are tax-exempt, send us the certificate before you subscribe — tax already collected has already been remitted and we cannot refund it.

Why this is not material. Nothing here changes what a plan costs, what it includes, what either of us owes, or what we promise about availability. Section 4.3 therefore applies and there is no 30-day notice period. One thing is worth saying plainly even so, because it can change the number on a card: when sales tax collection begins, an invoice in a state where we are registered will be the fee plus that state's tax. The fee is unchanged; the total is not the same number.

Supersedes 12 September 2026, which is kept in full below. Current version.

12 September 2026, not material

One addition to Terms 5.6, and one description of it in Privacy 2.2. Every plan is sold by the month in embed loads, renders and inventory lookups, and the agreement never said what one of those is. It does now, and for the embed the answer is more generous than the one our documentation had been giving:

Terms 5.6 is new. An embed load is counted once per viewer, per item, per 24 hours. A page showing twelve different items is twelve loads; the same viewer reloading, scrolling back to something they have already seen, or returning to it later the same day is served and not counted again. Renders and inventory lookups are counted per request, which is what they always were. No existing clause number moved. The new text reads better as 5.2, but 5.2 through 5.5 are published numbers that other documents and other people's notes cite — Refunds 4.3 names Terms 5.4 — so it takes the next free number at the end of the section and 5.1 points at it.
Privacy 2.2 says how a returning viewer is recognised, because counting one requires it. There is no cookie and nothing identifying is stored: the address and user-agent are hashed together with the customer's key and the item, under a secret held only in memory, and the result is kept for 24 hours and never written to disk. The customer's key inside the hash is what makes the same person on two different sites two unrelated values, so this cannot become a record of where anyone has been. The retention table in Privacy 6 carries it.

Why this is not material, and why it is dated tomorrow. It can only raise what a plan allows and lower what a bill says: no fee, quota, liability cap or uptime commitment moves, and nobody can be worse off under it than under the rule it replaces. Section 4.3 therefore applies and there is no 30-day notice period. The date is 12 September because a version is a date (section 2.1), 11 September already names the version published that morning, and rewriting the text behind a date somebody may already have accepted is the exact thing section 3 exists to prevent.

Supersedes 11 September 2026, which is kept in full below. Superseded on 13 September 2026. The text as it stood that day is kept, unchanged, at Terms of Service, Privacy Policy, Acceptable Use, SLA and Refunds and Cancellation.

11 September 2026, editorial

A correction pass across all five documents, checking every figure and cross-reference in them against the code that has to honour it. Nothing here changes what anyone owes, is charged, or is promised, so it is not a material change and carries no notice period under section 4.3. Section 2.4 makes it a version regardless, and this is what it corrected:

Terms 5.1 now says what Enterprise is. The table is a list of self-serve prices and deliberately does not carry a plan that has none, but an Enterprise customer was reading a heading that said "current plans" and finding nothing about theirs. A sentence under the table says the fees, quotas and origin limit come from a written agreement, and that everything else in the terms — the SLA included — applies to that account like any other.
Terms 10.4 listed what survives termination as "sections 1 (as to definitions), 3.2, 3.4, 11, 12, 13, 14 and 17". The definitions are not in section 1 — they are in "The agreement", above it and unnumbered — and the list left out section 15, although 15.5 says in its own words that confidentiality survives three years and 13.3 carves it out of the liability cap. It now names the definitions where they actually are, and adds 15 and 18.
Terms 18.1 said the whole agreement was these terms plus the Acceptable Use Policy, Privacy Policy and SLA. It is five documents: the preamble and 6.6 both incorporate the Refunds and Cancellation Policy, and section 1.2 of this page cites 18.1 as the authority for the set being five. The clause now lists it.
Privacy 8 told you that deleting your account leaves the usage counts of Privacy 2.3 for thirteen months. Privacy 2.3 is the Render API. What outlives a deleted account is the usage records in Privacy 2.1, which is what the retention table cites.
SLA 1.1 applied the uptime commitment to "a paid plan (Starter or Pro)", which read Enterprise out of it. It now covers every paid plan.
SLA 2.1 said 99.5% allows "about 3 hours 39 minutes" in a 30-day month. Half a percent of 43,200 minutes is 216, which is 3 hours 36. The old figure was half a percent of an average month, and no month is an average one. It now gives the rule — 0.5% of the month — and the figure for a 30-day and a 31-day month.
Refunds 7 promised a reply to billing email "within one business day", to everyone, where Terms 8.2 commits to one business day on Pro, two on Starter and best effort on Free. Terms 8.2 governed either way under 18.1; the Refunds page now quotes it instead of contradicting it.
The closing "see also" on each document listed three of the other four. Five hand-written lists that each dropped something different is how the Refunds policy came to be unreachable from the foot of four documents that incorporate it. All five now list the other four and this page.

Supersedes 9 September 2026, which is kept in full below. Superseded on 12 September 2026. The text as it stood that day is kept, unchanged, at Terms of Service, Privacy Policy, Acceptable Use, SLA and Refunds and Cancellation.

9 September 2026, initial publication

The first published version of the customer agreement. Nothing is superseded, because there is no earlier version. Five documents:

Document	What it covers
Terms of Service	The agreement between you and Menu Atlas LLC, a Utah limited liability company: what the service does, accounts, keys and registered origins, the licence and its limits, plans, fees, quotas and overage, payment, the uptime commitment, support response targets, the 7-day commitment on newly released CS2 content, suspension and termination, our position on Valve and game content, warranties, the liability cap, indemnities, confidentiality, how the agreement changes, and Utah governing law.
Privacy Policy	Everything we collect, per surface, and what we deliberately do not: usage records that identify an account rather than a person, an embed that sets no cookies and calls no third party, inventory results held in memory and never written to disk, the retention table, who we share with, your rights, and where the data lives.
Acceptable Use	What you may build on the service and what you may not, including the limits on extracting or re-serving assets, our position on skin gambling and the conditions attached to it, how to report a vulnerability, and how the policy is enforced.
Service Level Agreement	The 99.5% monthly uptime commitment, a full description of the single self-hosted origin behind it, how downtime is measured, what does not count as downtime, the service credit schedule, how to claim, and that credits are the sole remedy for missed uptime.
Refunds and Cancellation	What a payment buys, when we refund and when we do not, how to cancel and when it takes effect, what happens to your keys and embeds afterwards, how upgrades and downgrades are timed, failed payments, and how to raise a billing problem.

Superseded on 11 September 2026. The text as it stood that day is kept, unchanged, at Terms of Service, Privacy Policy, Acceptable Use, SLA and Refunds and Cancellation.

7. Contact

Questions about any version, or a request for the text in force on a particular date: hello@inspekt.gg.

Menu Atlas LLC
c/o Northwest Registered Agent LLC
7533 S Center View Ct Ste N
West Jordan, UT 84084, USA

The documents themselves: Terms of Service, Privacy Policy, Acceptable Use Policy, Service Level Agreement and Refunds and Cancellation Policy.