Engrym — Terms of Service

Provider: RTK AI Labs Ltd, a company registered in England and Wales under company number 17179962 ("RTK AI Labs Ltd," "we," "us," "our"), the company behind the Engrym product ("Engrym," the "Service").

Last updated: 11 July 2026

Scope: the Free tier (three Projects), the Solo Builder tier (€29.99 per month, or €287.90 per year), and — during the founding window only — the Founding Supporter price on the Solo Builder tier (Section 5.5). The Team tier is shown in-product as "coming soon" and is not currently purchasable. These terms make no commitments about capabilities that are not yet available.

1. Service description and definitions

1.1 What Engrym is

Engrym is a knowledge layer for software and project teams. It stores a project's documented knowledge — markdown documents and the structured "atoms" (decisions, conventions, constraints, and context entries) extracted from those documents — and serves that knowledge to the AI agents you already use. Where a documented claim can be checked against your code, your own AI agent (running in your editor, where it already holds your repository) reads the code and returns a verdict — upheld, violated, or uncertain — together with an evidence pointer (a path:line locator) and an optional written note. Engrym records the verdict. Engrym does not read, receive, or store your code.

1.2 What Engrym is not

Engrym is not an AI coding assistant, and it is not a replacement for any AI coding tool. It works alongside them. Engrym does not read, index, navigate, or retrieve over your source code (see Section 6, the code-privacy guarantee).

1.3 Definitions

• Project — a bounded scope of work (a codebase, a product, a research initiative) with its own knowledge layer.
• Document — a markdown file with optional frontmatter that you create or import into a Project.
• Atom — a structured knowledge entry (a decision, convention, constraint, or context item) extracted from a Document, with provenance and supersession tracking.
• Brain — the queryable set of a Project's Atoms served to your agents.
• Reconciliation Verdict — the upheld / violated / uncertain result your agent returns when it checks a documented claim against your code at a specific commit.
• Evidence Pointer — a path:line locator string accompanying a Reconciliation Verdict. It never contains code text.
• BYOK Key ("bring your own key") — an AI provider API key (Anthropic, OpenAI, or Google) that you supply so that Engrym can dispatch AI work using your provider account.
• Connected Agent — an MCP-compatible AI tool of your own (for example, Claude Code or Claude Desktop) that you connect to Engrym and that runs on your own AI subscription, in your own environment.
• Extraction Mode — the per-Project setting that controls where extraction runs and who funds it: BYOK mode, agent mode, or mix mode (Section 4.1).
• Platform Key — an AI provider key that RTK AI Labs Ltd supplies and funds, used only for the limited platform-funded operations described in Section 4.3.
• Sync Daemon — the optional local program you install on your own machine to sync a local folder with your Project.
• Git Export — the optional feature that writes your Project's documents, knowledge base, decision log, and activity stream to a Git repository you control.

2. Eligibility and account

2.1 Eligibility

You must be at least 16 years old (or the age of digital consent in your jurisdiction, if higher) and able to form a binding contract to use the Service.

2.2 Your account

You are responsible for the accuracy of the information you register, for keeping your credentials secure, and for all activity under your account.

2.3 Your AI provider accounts

When you use a BYOK Key, you are responsible for maintaining your own account in good standing with that AI provider, for the validity of the key, and for all usage and charges your provider bills to you for that key. When you use a Connected Agent, your agent's usage is governed by your own subscription agreement with your AI provider; Engrym never receives your subscription credentials. See Section 4.

3. Acceptable use

You agree not to:

• upload, store, or process content you do not have the right to upload, store, or process;
• upload unlawful content, or content that infringes a third party's rights;
• use Engrym's AI-dispatch features in a way that violates the terms of the AI provider whose key is used (yours under BYOK, or ours on the Platform Key path), or use a Connected Agent with Engrym in a way that violates your agreement with your AI subscription provider;
• attempt to circumvent the per-account usage limits described in Section 4.4 or the technical rate limits applied to the API;
• reverse-engineer, decompile, or attempt to extract source from the Service, except to the extent that restriction is prohibited by applicable law; or
• use the Service to build a product that is substantially the same as Engrym.

We may suspend or limit access to protect the Service, other users, or our providers from abuse, security risk, or runaway cost.

4. AI work, extraction modes, and our handling commitments

4.1 Extraction runs on your own compute — three modes

The AI extraction that turns your Documents into Atoms never runs at RTK AI Labs Ltd's expense, is never marked up, and is never billed to you by us. Each Project is set to one of three extraction modes (the default is BYOK; you can change the mode per Project):

• BYOK mode (the default). Our servers dispatch the extraction request to the AI provider you choose (Anthropic, OpenAI, or Google) using your BYOK Key. That inference uses your provider account and is governed by your agreement with that provider.
• Agent mode. No provider key is required. Your Connected Agent pulls the Document text and the extraction instructions from Engrym, runs the extraction model inside your own agent session, on your own AI subscription, and submits the extracted Atoms back to Engrym. Submitted Atoms are recorded as provisional knowledge, subject to your review and ratification. We never receive, store, or use your AI subscription credentials, and we never re-route agent-mode work to any paid key: a Document with no Connected Agent simply waits in an explicit "pending — needs agent" state until an agent picks it up.
• Mix mode. A Connected Agent handles foreground extraction as in agent mode, and a configured BYOK Key handles background extraction as in BYOK mode.

Agent auto-pull is off by default. By default, your Connected Agent pulls extraction work only when you ask it to. You may opt in, per Project, from the dashboard, to allow a Connected Agent to pull waiting work automatically; the same settings let you require an in-session re-confirmation and control how eagerly the agent may pull. Until you opt in, no agent auto-pulls anything.

The contradiction-finding feature's AI judging runs against your BYOK Key.

4.2 How we handle your BYOK key

• Your BYOK key is encrypted at rest using strong, industry-standard encryption. It is never stored in plaintext.
• Your key is decrypted only momentarily, in memory, at the moment an AI request is dispatched, and is then discarded.
• Your key in plaintext is never written to a log, never persisted, and never returned to any caller.

4.3 The Platform Key — the one place we send your text to an AI provider on our account

For two specific operations, where you have not configured your own Google key, Engrym uses a Platform Key that RTK AI Labs Ltd supplies and funds:

1. Semantic-search embeddings — your Atom text is sent to Google's Gemini API to produce search vectors, so your knowledge base can be searched by meaning, not just by keyword.
2. Duplicate detection (claim-merge) — pairs of your Atom texts are sent to Google's Gemini API to decide whether a new Atom duplicates an existing one.

On the Platform Key path we send Atom text only — never your source code, and never your Documents beyond the Atom text already extracted from them. If you configure your own Google key, that key is used instead, and the Platform Key is not used for your Project.

The Platform Key funds embeddings and duplicate detection only. It is never used for chat, extraction, or any other generation. The contradiction-finding feature's AI judging always runs on your key, not ours (Section 4.1).

4.4 Usage limits

To keep platform-funded AI spend bounded, per-account, per-period limits apply:

• Contradiction-finding calls (run on your BYOK key): Free is limited to a set number of invocations per period and is soft-blocked at the ceiling (the feature returns an empty result flagged "limit reached"); Solo is allowed a higher number per period and proceeds with a warning at the ceiling.
• Agent-mode extraction submissions are limited to a set number per account per period. At the ceiling, further Documents remain in the "pending — needs agent" state until the next period — the work is never silently re-routed to a paid key, and you are never billed.
• Platform-funded embedding spend and platform-funded duplicate-detection spend are each capped per account per period. At a ceiling, the affected feature degrades gracefully — semantic search falls back to keyword search, and new Atoms are simply created without duplicate-merging — rather than incurring further spend or charging you.

These are usage controls, not additional charges: reaching a ceiling degrades or pauses a feature; it does not bill you. The current numeric limits are shown on the pricing page and in your billing settings, and may change as described in Section 11.

5. Subscriptions, billing, and refunds

5.1 Tiers and prices

• Free — €0. Three Projects. Projects on the Free tier cannot be linked to one another (connecting Projects is a paid feature). Extraction runs on your own provider key or your own agent subscription (Section 4.1) — no card required, no model-usage markup, no metered trial. History views display the trailing 90 days (Section 7.4); no data expires on any tier (Section 7.4).
• Solo Builder — €29.99 per month, or €287.90 per year (20% off the monthly run-rate). Unlimited Projects.
• Founding Supporter (closed window) — €9 per month, or €90 per year, on the Solo Builder tier: the same tier, the same features, the same limits as Solo Builder, at a locked price. Available only while the founding window is open; see Section 5.5. €29.99 per month (or €287.90 per year) remains the standard Solo Builder price.
• Team — shown in-product as "coming soon"; not currently purchasable. We make no commitment as to its availability, features, or price.

5.2 Billing mechanics

Paid subscriptions are billed through our payment processor. RTK AI Labs Ltd does not receive or store your full card number; card data is held by the payment processor, which is the PCI boundary. We store customer and subscription identifiers and subscription status only. Subscriptions renew automatically each period until cancelled. Prices are stated in euros (EUR). RTK AI Labs Ltd is not registered for VAT, so no VAT is added; the EUR prices stated are the total amount payable.

A paid subscription is attached to your user account, not to a single Project: a Solo Builder subscription entitles your account on every Project you use, and one account holds at most one active paid subscription at a time.

5.3 Checkout terms

The following applies to every paid purchase, and is presented at checkout:

• Prices are in euros (EUR): €29.99 per month, or €287.90 per year, for Solo Builder.
• You choose the billing interval — monthly or yearly — at checkout. Billing is in advance, at the start of each period.
• There is no free trial: the paid period starts when the purchase completes, and the Free tier remains available without payment.
• Subscriptions renew automatically at the end of each period until cancelled.
• You can cancel at any time through the billing portal linked from your billing settings; cancellation takes effect at the end of the current paid period, and you retain paid features until then.
• If you are a consumer in the UK or the EU, you may have a statutory 14-day right of withdrawal for purchases made online. Where you request that the service start immediately, the checkout will ask for your express acknowledgement, and the statutory rules on early supply of digital services then apply. Nothing in these terms limits rights you have under mandatory consumer-protection law.
• During the founding window only, checkout also offers the Founding Supporter price on the Solo Builder tier; Section 5.5 governs that price, its lock, and the supporters-wall opt-in presented at founding checkout.

5.4 Effect of downgrade or cancellation on your data

Your right to export your Project (Section 7) survives cancellation. Export, deletion, and retention windows are set out in our Privacy Policy and govern this Section and Section 9. After cancellation, export remains available for a limited period, as described in our Privacy Policy.

5.5 The Founding Supporter price (closed window)

5.5.1 What it is — a price, not a tier

During the founding window (Section 5.5.2), you can subscribe to the Solo Builder tier at the Founding Supporter price: €9 per month, or €90 per year, instead of the standard €29.99 per month or €287.90 per year. The Founding Supporter price is a price, not a separate plan: a Founding Supporter subscription is a Solo Builder subscription in every respect — the same features, the same Project limits, the same usage limits (Section 4.4), and the same checkout terms (Section 5.3). There are no features available to Founding Supporters that are not available to standard Solo Builder subscribers, and no features withheld. The standard prices stated in Section 5.1 remain the Service's live prices throughout.

5.5.2 The founding window — when the price is available

The Founding Supporter price is available only during a single, closed founding window. The window opens on a date we announce and closes at the earlier of:

• a stated close date, 30 days after the window opens; or
• the moment 400 Founding Supporter subscriptions exist.

Once the window has closed — by date or by count — no new Founding Supporter purchase is possible, and the checkout will refuse founding purchases from that moment. Checkouts already in progress when the cap is reached may still complete, so the founding cohort can marginally exceed 400. The close of the window has no effect on existing Founding Supporter subscriptions (Section 5.5.3): it ends availability to new supporters, not existing price locks. We publish a live counter of founding subscriptions during the window; the authoritative control is the checkout's own refusal, not the displayed counter.

5.5.3 The price lock — what "locked" means, exactly

If you subscribe at the Founding Supporter price during the window, that price is locked for the life of your continuous Founding Supporter subscription: for as long as the subscription remains in effect, each renewal bills at €9 per month or €90 per year (whichever interval you chose), regardless of the Service's standard prices at the time. Nothing in the Service re-prices a Founding Supporter subscription, and Section 11 (changes to the Service and these terms) does not permit us to raise the price of an existing, continuing Founding Supporter subscription.

The lock ends when the subscription ends. Specifically:

• Cancellation ends the lock. If you cancel (Section 5.3), your Founding Supporter subscription — and with it the founding price — ends at the end of the current paid period.
• The subscription otherwise ending ends the lock — including where the subscription is cancelled after repeated payment failure. A temporary payment failure that is resolved within the payment processor's retry process does not by itself end the subscription or the lock.
• Moving to a different plan ends the lock. The Founding Supporter price attaches to the Solo Builder tier only; it does not carry to any other tier or plan (including any future Team plan).
• There is no re-entry. Once your Founding Supporter subscription has ended — for any of the reasons above — the founding price is not available to you again, because the window is closed to all new founding purchases (Section 5.5.2). A new subscription is at the then-standard prices.

5.5.4 The public supporters wall — opt-in, display name only, revocable

During and after the window, we publish a supporters wall: a public page listing Founding Supporters who chose to be listed. The wall works like this:

• Opt-in only, and off by default. You are listed only if you explicitly opt in — via the checkbox at checkout (unchecked by default) or later from your account settings. If you do not opt in, you are never listed; you are counted only in the aggregate supporter count, which contains no names.
• Display name only. The wall shows a display name and nothing else. When you opt in — at checkout or from your account settings — the name shown is the display name already on your account, resolved on our side at that moment; where your account has no display name set, the wall shows "Anonymous" instead, and your account settings tell you so. You can change the name shown on the wall at any time from your account settings, including to a pseudonym. We never display — and the wall's data source does not even contain — your email address, your payment details, any payment or subscription identifier, or the price you pay.
• Listed only while you are a supporter and opted in. Your name appears only while you both remain opted in and hold a live Founding Supporter subscription. The close of the founding window does not remove any name: opted-in supporters remain listed after the window closes. If your Founding Supporter subscription ends, your name leaves the wall.
• Revocable at any time. You can withdraw from the wall at any time from your account settings. Withdrawal deletes the opt-in record outright — your name is removed from the wall promptly, and re-opting in later starts a fresh opt-in. Deleting your account removes the opt-in record automatically.

5.5.5 Founding extras — courtesies, not purchased features

Alongside the price lock — which is the contractual substance of the Founding Supporter purchase — we currently extend Founding Supporters some courtesies:

• Weighted feedback votes. On the public feedback board, a Founding Supporter's upvote currently carries five times the ranking weight of a standard vote. The board discloses this, and the displayed supporter counts always reflect real numbers of people.
• Team-beta priority. The Team tier is a private beta and is not purchasable (Section 5.1). While that remains true, Founding Supporters who ask to join the Team beta are admitted ahead of the queue. This does not change Section 5.1's position: we make no commitment as to the Team tier's availability, features, or price.
• The supporters wall (Section 5.5.4).

These extras are provided as courtesies to the founding cohort. They are not part of the paid subscription — what you purchase is the Solo Builder tier at the locked founding price (Sections 5.5.1 and 5.5.3) — and we may adjust how the courtesies work as the product develops. We will not remove the price lock itself, which Section 5.5.3 governs.

6. The code-privacy guarantee (the transient-sensor boundary)

This is a core commitment of the Service:

Engrym does not read, store, embed, index, cache, or persist any representation of your source code. This means no file contents, no abstract syntax tree, no call graph, no import graph, no file tree, no snippet — and no code text inside a Reconciliation Verdict beyond the path:line Evidence Pointer.

Reconciliation is performed by your AI agent, in your own environment, which already holds your repository. Your agent reads the code transiently within its own session and returns only the verdict, the evidence pointer, and an optional note. Engrym serves the documented claim and records the verdict.

7. Your data: ownership, portability, and export

7.1 You own your content

As between you and RTK AI Labs Ltd, you own the Documents, Atoms, verdicts, and other content you create or import. You grant RTK AI Labs Ltd the limited licence necessary to operate the Service for you — to store, sync, extract Atoms from, index, and serve your content to your own AI agents, and to provide the features described in these terms. We claim no broader rights.

7.2 Portability and export

Engrym is built so you can leave with your data. Every Project can be exported, and you may configure an optional Git export that writes a standard, human-readable copy of your Project, in open formats, to a Git repository you control — containing your documents, your knowledge base, and your decision and activity history, and no source code.

7.3 We do not train on your content

RTK AI Labs Ltd does not use your content to train any model. We run no first-party model training. Platform-funded inference is dispatched to Google's Gemini API solely to provide the features described in Section 4.3.

7.4 Free-tier history views: a 90-day display window (not deletion)

Some parts of the Service present a chronological history of Project activity — timeline and history views. On the Free tier, these history views display the most recent 90 days of events, on a per-account rolling basis. This is a display rule applied when history is read. It is not a data-retention rule, and nothing about it deletes anything. Specifically:

• No customer data expires on any tier — Free included. Your Atoms, your Documents, your decisions, search, and the current Brain never expire and are never subject to this window. The complete underlying event stream remains stored in full and remains the Service's system of record; the window changes only what a Free-tier history view displays.
• Reconciliation Verdict history is exempt on every tier. Verdict history (Section 1.3) always displays in full, on Free and on every paid tier.
• Nothing disappears silently. Where a Free account has history older than the window, the history view says so — it indicates that older events exist beyond the 90 days shown.
• Per-account rolling window. The 90 days are measured per account, rolling with time — the trailing 90 days as of the moment you read. There is no fixed cut-off date and no cohort freeze.
• Upgrading restores full history reads immediately. Because the data was never removed, upgrading to a paid tier makes your full history readable at once, with no restoration step, no waiting period, and no data operation of any kind. If a paid subscription later ends and the account returns to the Free tier, the display window applies to reads again — the underlying data remains untouched throughout.
• The window applies to history views however they are accessed — in the dashboard, through the API, or through a Connected Agent — and applies identically in each.
• This window limits nothing else in these terms. It does not limit your ownership of your content (Section 7.1), your export and portability rights (Section 7.2) — export always covers your full data, not a 90-day slice — or anything in our Privacy Policy, whose retention and deletion commitments are unchanged by this section.

Effective date of enforcement. We state this display rule here, in advance, so that it is transparent from the start and is never applied retroactively: the window will not begin to be enforced in the product until at least 90 days after this section first appears in these terms. Until it is enforced, Free-tier history views display full history.

8. Warranties, disclaimers, limitation of liability, and indemnity

8.1 Service provided "as is"

The Service is provided "as is" and "as available." To the maximum extent permitted by law, RTK AI Labs Ltd disclaims all implied warranties, including merchantability, fitness for a particular purpose, and non-infringement. Nothing in these terms excludes or limits any rights you have under mandatory consumer-protection law that cannot be excluded or limited.

8.2 Reconciliation verdicts and extracted Atoms are your agent's, not ours

A Reconciliation Verdict is produced by your AI agent. In agent mode, extracted Atoms are likewise produced by your agent and recorded as provisional pending your review. RTK AI Labs Ltd records these outputs; it does not generate them and does not warrant that they are correct. You are responsible for any decision you make based on a verdict, an Atom, or any content the Service serves to your agents.

8.3 Third-party AI providers

RTK AI Labs Ltd is not responsible for the availability, performance, output, or data-handling of the AI providers you choose under BYOK or through a Connected Agent, or for outages or changes at any AI provider. The relationship between you and your provider is governed by your agreement with that provider.

8.4 Limitation of liability

To the maximum extent permitted by law, RTK AI Labs Ltd will not be liable for indirect, incidental, special, consequential, or punitive damages, and its total liability arising out of or relating to the Service is limited as set out in these terms. Nothing in these terms limits liability that cannot be limited under applicable law, including liability for death or personal injury caused by negligence, for fraud, or under non-excludable consumer rights.

8.5 Indemnity

You are responsible for the content you upload and for your use of the Service, and you will be responsible for claims arising from your breach of these terms or your misuse of the Service, to the extent permitted by applicable law.

9. Suspension, termination, and deleting your data

Archiving a Project (self-serve). You can archive any Project you own from the product at any time. Archiving removes the Project from your working set. Archived-Project data is retained rather than purged — archiving never leads to deletion by itself — and there is currently no self-serve restore for an archived Project: contact us at the address in Section 12 to restore one. (Restoring a Project during the deletion grace window is different, and is self-serve — see the next paragraph.) If you want an archived Project's data gone rather than retained, you no longer need to contact us: you can permanently delete it yourself — the deletion flow below accepts archived Projects.

Deleting a Project (self-serve, permanent). A Project's owner — and only the owner — can permanently delete the Project, active or archived, from the Project's settings. Deletion requires typing the Project's name to confirm, and the confirmation shows real counts of what will be destroyed. Deletion then runs in two stages: first a grace window — currently seven days; the product shows the exact window and purge date — during which the Project disappears from every part of the Service and the owner, and only the owner, can restore it intact (restoring counts against your plan's Project limit: at the limit, you need a free slot or an upgrade first); then an automatic, irreversible purge of the Project's data. There is no restore after the purge. Deletion is refused while the Project is linked to another Project — remove the link first; the product tells you which linked Projects block and how many cross-references are involved — and, in the rare case that a subscription is anchored directly to the Project, until the billing situation is resolved: contact us at the address in Section 12.

What "permanent" means. The full deletion mechanics — what the purge destroys, what it does not touch, and what happens to your external Git repository (nothing: it is yours, and everything already exported to it stays where it is) — are set out in our Privacy Policy (Section 5), which governs this Section. Consistent with that policy: the purge removes the Project's data from our live systems, and nothing in the Service can bring it back; copies may persist for a limited period in our hosting providers' routine backups, which expire on those providers' backup-retention cycles, and we do not restore purged Project data from backups; and the Project's encryption keys are destroyed in the purge, which makes its stored provider keys and Git-export credential permanently unreadable everywhere, including in any backup copy. We do not claim deletion is instantaneous everywhere at once.

Deleting your account (via support). Account deletion is not yet self-serve. To delete your account, email us at the address in Section 12 from the email address on the account; we will verify the request and carry out the deletion, and your data is then handled as set out in our Privacy Policy (retention, deletion, and the export window). You may stop using the Service at any time without contacting us.

Suspension and termination by us. We may suspend or terminate your access for material breach of these terms, non-payment, or abuse (including conduct that threatens the security or stability of the Service or our providers). On termination, your data is handled as set out in our Privacy Policy, and the same windows govern this Section and Section 5.4.

10. Telemetry and the local Sync Daemon

The optional Sync Daemon runs on your own machine and ships without third-party error-telemetry, specifically to avoid sending telemetry from your environment. It transmits only your own Project sync data between your machine and your Project.

11. Changes to the Service and these terms

We may change features, tiers, and limits (including moving the Team tier from "coming soon" to available, or adjusting the usage limits in Section 4.4) as the product develops. For material changes to these terms, we will give notice through the Service or by email before the change takes effect.

12. Governing law, venue, and contact

RTK AI Labs Ltd is incorporated in England and Wales (company number 17179962). Registered office: 66 Paul Street, London EC2A 4NA, England. These terms are governed by the laws of England and Wales, and the courts of England and Wales have jurisdiction, except that, where you are a consumer, you retain the protection of mandatory provisions of the law of your country of residence and any right to bring proceedings there.

Contact: notices and legal correspondence can be sent to us by email at oussama.berrahal@engrym.com.

13. Document history

• 11 July 2026 — Section 9 updated for self-serve Project deletion, published together with the matching Privacy Policy Section 5 rewrite: a Project's owner can now permanently delete any Project — including an archived one — from the product, with a grace window (currently seven days; restorable by the owner during the window, and only then) followed by an automatic, irreversible purge. The archive paragraph is conformed: archived-Project data remains retained and restoring an archived Project still requires contacting us, but permanently deleting one no longer does. Added "What 'permanent' means" (the Privacy Policy governs; backup copies expire on our hosting providers' retention cycles; the Project's encryption keys are destroyed at purge; no claim that deletion is instantaneous everywhere). Account deletion remains via support, unchanged.
• 10 July 2026 — Added Section 5.5 (the Founding Supporter price: closed window, price lock, supporters-wall consent) and Section 7.4 (the Free-tier 90-day history display window — a display rule, not deletion; stated here before it is enforced so it is never retroactive). Free tier raised from one Project to three (unlinked). Scope line and Section 5.1 updated to match.
• 3 July 2026 — Updated to match the live product: Section 4.1 now describes the three extraction modes (BYOK, agent, mix) and the per-Project agent auto-pull consent switch; the earlier description of extraction as always running on a BYOK key predated agent mode. Removed the "first extraction free" wording from the scope line and Section 5.1 — no platform-funded extraction path exists; extraction runs on your own key or your own agent subscription in every mode. Section 4.4 adds the agent-mode submission ceiling. Section 5 sets out the checkout terms (EUR pricing, monthly or yearly interval, no trial, portal cancellation, user-level subscription) and the exact yearly price. Section 9 now describes what exists today: self-serve Project archive (retained data, no self-serve restore) and account deletion via support rather than self-serve. Company-detail fields added for completion.
• 19 June 2026 — First published version.