Legal

GSF-E Terms of Service

---

Version: 1.0 · Effective: [EFFECTIVE DATE]

These Terms are an agreement between you and Arjun Sharma, sole proprietor, trading as AI for Products, of Gwalior, Madhya Pradesh, India ("we", "us"), for the GSF-E service at [SERVICE URL] (the "Service"). You accept them by ticking the box and clicking "Create account" when you sign up. We keep a record of which version you accepted, when, and from which IP address.

If you use the Service for a company or other organisation, you accept these Terms for it and confirm you may do so. "You" then means that organisation.

These Terms are written in English. The GSF-E Acceptable Use Policy and Privacy Notice form part of them.

1. The Service

1.1 GSF-E guides an AI coding agent that you run (for example Claude Code) through a product-development method. You add the GSF-E plugin to your agent; your agent then reaches the Service through the plugin and through a small helper the plugin places in your project. The Service:

• gives your agent the method one step at a time, when your project reaches that step;
• checks, updates and signs your project's record: which steps are done or skipped (with the reason you give), which gates passed, who signed them and when, who is on the team and in which role, and the GSF-E release the project uses. The record lives in your own repository, not on the Service: with each call your agent sends it, and the signed record that comes back is saved in your repository. The Service keeps no copy; the one thing about a project kept outside your repository is who may act on it (which accounts are on its team), held with the accounts by our sign-in provider, WorkOS, so that, once that sign-in is in place, a teammate taken off is cut off at once (before then, as on a pilot copy of the Service, an older signed record put back from your repository's history can bring a removed teammate back; the GitHub checks in your repository report it, they do not block it);
• reads an outline of each project document a step makes (its file path, the label at its top (title, type, status, owner, phase, feature, dates and tags, nothing else), its headings and how many blanks are left), made on your computer and sent with each call, to check the step was done, and does not keep it;
• provides the Safety Kit, a small set of files placed in your project's repository (house rules for your agent, locks that stop risky actions, and GitHub checks), signed by us so the plugin can check it came from us before writing it, and licensed under the GSF-E Safety Kit License.

1.2 We do not want your code or your documents' text. The Service is built so that your agent writes those only in your own repository and accounts; it sees only the record and the outlines above, during each call. Do not send project content to the Service, and keep secrets and personal data out of names, file names, document labels and headings.

1.3 First month free, then paid. Each person's first month is free, counted from their own sign-up. After that, their seat is paid by the team's owner or the company, at the prices on our GSF-E page, under our Refund and Cancellation Policy. We will give at least 30 days' notice before changing a price or these payment terms. If a seat is unpaid, new steps stop; your code, documents and records stay yours, the locks work as before, and disconnecting always works. We may change, suspend or end the Service, or any part of it, and we give no service-level commitment. We will give at least 60 days' notice before ending the Service. Your project's record is always in your repository, and your agent can save a copy of it, with your documents' outlines, as a file at any time, on your own computer, without the Service. If the Service ends, the locks keep working on your computer from your project's last signed record, but nothing new can be recorded or signed (no steps, sign-offs or releases); asking your agent to "disconnect from GSF-E" takes the locks off, and needs no Service.

1.4 The signed record and the locks. The Safety Kit's locks read the signed record in your repository, on your computer: for example, they keep product code locked until the steps before it are signed. A record changed by hand, or merged by git alone, no longer carries a valid signature, and code stays locked until the Service signs the record again. Anyone who can read your repository can read the record, including your team's display names, roles and sign-offs; decide who can read it accordingly. The record names each person by an account ID and a display name they choose, never by an email address.

1.5 GSF-E releases (the support window). Each project uses one GSF-E release, named in its record. We serve the newest release and the one before it: when a new release comes, the one before it is served for 12 more months, and any older one until its end date or for 60 more days, whichever is sooner. We tell you at least 60 days before a release your project uses stops being served, in your agent's session and in the project's status. Fix releases of the same release line reach your project on their own, and so, while GSF-E is in release candidates, does the next release candidate of the candidates your project uses (every release is a candidate until the first final release); a new project starts on the newest final release (on the newest candidate while there is none), and a project on a final release is offered only a newer final unless your team asks for a candidate by name. Moving to a newer release needs your team's yes, and can be undone while the release before it is served. When a release stops being served, the Service refuses its calls, except the upgrade, closing, handing a project over, the project's owner re-signing the record after a key leak, and the tech lead moving it to a renamed repository; the locks keep working.

2. Who may use the Service

2.1 You must be at least 18 years old and able to make a binding contract. 2.2 You may not use the Service if you are in, or ordinarily resident in, a country or region under comprehensive sanctions by India, the United Nations, the United States or the European Union, or if you are a person on a sanctions list of any of them. You must not use or let anyone use the Service in breach of export-control or sanctions laws. 2.3 Not yet in the EU, the EEA or the UK. For now, the Service is not offered to people in the European Union, the European Economic Area or the United Kingdom, or to organisations established there. Do not sign up from there; we may close an account that was. We will update these Terms before we open to those places. 2.4 One account is for one person. Keep your sign-in and access tokens secret; you are responsible for what happens under your account. Tell us at once at aiforproducts01@gmail.com if you think someone else is using it. 2.5 Give accurate account details, including the country you are in, and keep them up to date.

3. What is yours

3.1 You own what you build. Your code, documents, products and anything else you or your AI agent create while using the Service belong to you, or to whoever you agreed they belong to. We claim no rights in them. 3.2 That includes documents your agent writes by following a step, even when they follow the structure the step suggests. 3.3 You are responsible for your project and your product, and for having the rights to everything you put into them.

4. What is ours

4.1 The method (its steps, gates, checklists, templates, rules and their wording), the engine, the server, the GSF-E plugin and the rest of the Service, except the Safety Kit, belong to us and are protected by copyright and other laws. These Terms give you no ownership of any of it. The GSF-E plugin comes with its own licence (the LICENSE file inside it), and the Safety Kit with the GSF-E Safety Kit License.

4.2 Your licence. While your account is open, we give you a personal, non-exclusive, non-transferable, revocable licence to use the Service to build your own products and your organisation's products.

4.3 You may not, and may not help anyone to:

• copy, collect, store, compile or publish the method's steps or a substantial part of them, beyond what your agent needs while working on a real project;
• scrape, crawl or bulk-download the Service, or request steps your projects have not reached;
• reverse engineer, decompile or try to extract the Service's code or content, except where the law allows it despite this clause;
• use the Service, or anything from it, to build or offer a competing method, framework, product or service;
• resell, sublicense, rent or share access to the Service, or let anyone else use your account;
• remove or change ownership notices.

4.4 Section 4.3 does not cover text the Owner has published under an open licence, such as the Agentic SDLC method up to v5.11.1 under the Apache License 2.0: that text stays available under that licence.

5. Your AI tools

5.1 You choose and pay for your own AI agent and model provider. Their terms and privacy policies cover what your agent sends them, including the steps it receives from us. We are not responsible for them. 5.2 Do not publish the steps your agent receives or use them outside the Service. Text the Owner has published under an open licence, such as the Agentic SDLC method up to v5.11.1 under the Apache License 2.0, stays available under that licence; this does not cover it.

6. Acceptable use

You must follow the GSF-E Acceptable Use Policy. It also lists the kinds of information you must never put into the Service.

7. Not professional advice

The Service helps you follow a development method. It is not legal, regulatory, compliance, security or other professional advice. Using it does not make your product, organisation or practices compliant with any law or standard. You decide what to build and how, and you review and approve the work.

8. Privacy

The GSF-E Privacy Notice explains how we handle personal data. Organisations can ask for the GSF-E Data Processing Agreement at aiforproducts01@gmail.com.

9. Feedback

If you send us ideas or suggestions, we may use them freely and owe you nothing for them.

10. Disclaimers

The Service and the Safety Kit are provided "as is" and "as available". To the extent the law allows, we give no warranties, express or implied, including of fitness for a particular purpose, merchantability, accuracy or non-infringement. We do not promise that the Service will be uninterrupted, secure or error-free, or that following the method will produce any particular result.

11. Limits on our liability

11.1 To the extent the law allows, we are not liable for indirect, incidental, special, consequential or punitive loss, or for loss of profit, revenue, data, goodwill or opportunity. 11.2 To the extent the law allows, our total liability for all claims about the Service is limited to the greater of (a) what you paid us for the Service in the 12 months before the claim, and (b) ₹5,000. 11.3 Nothing in these Terms limits liability for death or personal injury caused by negligence, for fraud, or any other liability the law does not allow to be limited, and nothing takes away rights you have as a consumer under the law of the country where you live.

12. Indemnity

To the extent the law allows, you will compensate us for losses and reasonable costs caused by your breach of these Terms or your misuse of the Service. This clause does not apply to you if you use the Service as a consumer.

13. Suspension and termination

13.1 You may stop using the Service and close your account at any time, by asking your agent ("close my GSF-E account") or by writing to aiforproducts01@gmail.com. 13.2 If you do not comply with these Terms, the Acceptable Use Policy or the Privacy Notice, we may end your access at once, refuse to process information that breaks them, or both. We may also suspend or close an account when the law requires it or to protect the Service or other users. Where it is reasonable, we will tell you first and give you a chance to fix the problem. 13.3 When your account ends, your licence under section 4.2 ends and your agent can no longer receive steps. Each project your account owns goes to its tech lead (or, with none, another teammate), who owns it from then on, so the team carries on; the record keeps the change. A project with nobody else on its team is closed instead: nobody can work on it in GSF-E any more, and GSF-E's locks in it come off once the closing record is saved in git. In projects others own, you leave the team. While your account is open, you can also hand a project you own to a teammate yourself (one confirmation). Your code, documents and project records stay in your repositories, and you can save a copy of a project's record at any time (section 1.3). You may keep using the Safety Kit in your repositories, under its own licence. 13.4 Sections 3, 4.1, 4.3, 7 and 9 to 17 continue after your account ends.

14. Changes to these Terms

We may update these Terms. We will tell you about material changes at least 30 days before they take effect, by email and in the Service, and ask you to accept them. If you do not accept, you can close your account; your project records stay in your repositories.

15. Law and courts

These Terms are governed by the laws of India. Disputes go to the courts with jurisdiction over Gwalior, Madhya Pradesh, India. If you are a consumer living outside India, you keep the protection of the mandatory laws of your country and may also bring proceedings in its courts.

16. General

16.1 These Terms, the Acceptable Use Policy, the Privacy Notice and, where signed, the Data Processing Agreement are the whole agreement about the Service. 16.2 If a provision is unenforceable, the rest stays in force. Not enforcing a provision is not a waiver. 16.3 You may not transfer these Terms without our written consent. We may transfer them to a successor, including a company we form to run the Service, and will tell you if we do.

17. Contact and grievances

Grievance Officer: Arjun Sharma, Gwalior, Madhya Pradesh, India · aiforproducts01@gmail.com

Send complaints about the Service, about content, or about your personal data to the Grievance Officer. We acknowledge every complaint within 24 hours and resolve it within 7 days. Security problems: aiforproducts01@gmail.com. Reports of unlawful content: aiforproducts01@gmail.com.

18. Weekend workshops

These Terms are for the GSF-E service. Our paid weekend workshops are separate. Each workshop's page and our emails set out its topic, dates, times, format and fee. You reserve a seat by paying on Razorpay's hosted payment page for that workshop, or by a payment link we email you while online payment is not yet open. Your own work, and what you make at a workshop, stays yours. Cancelling, moving a seat and refunds follow section 8 of our Refund and Cancellation Policy. Sections 7, 11, 15 and 17 of these Terms apply to workshops too, with "the Service" read as "the workshop".