Legal
GSF-E Privacy Notice
Provided by Arjun Sharma, sole proprietor, trading as AI for Products, Gwalior, Madhya Pradesh, India. GSF-E is the product's name. Questions: aiforproducts01@gmail.com. Other policies: Terms · Privacy · Acceptable use · Data processing · Refunds.
Version: 1.0 · Effective: [EFFECTIVE DATE]
This notice explains what personal data the GSF-E service collects, why, and what you can do about it. Section 13 covers this website (aiforproducts.in): its cookie-free analytics, its forms, the community and weekend workshop bookings. It is in English; ask at aiforproducts01@gmail.com if you need it in another language listed in the Eighth Schedule to the Constitution of India.
1. Who we are
The service is run by Arjun Sharma, sole proprietor, trading as AI for Products, of Gwalior, Madhya Pradesh, India ("we", "us"). We decide how your account data is used (we are the "controller" or "Data Fiduciary"). Contact for anything in this notice: aiforproducts01@gmail.com.
- EU and UK: for now, the Service is not offered in the European Union, the European Economic Area or the United Kingdom (Terms 2.3), so no EU or UK representative is appointed. We will appoint them, and add them here, before we accept sign-ups from there.
When you work on an organisation's project, that organisation decides how the project's record is used, and we process it for them while each call runs (see section 9).
2. The short version
- We keep your account (with our sign-in provider, WorkOS), a record of what you accepted, and security logs. We do not keep your projects. 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 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 the repository's history can bring them back; GitHub's checks in the repository report it). Each project's record (its steps, sign-offs and team) lives in your own repository, signed by us. With each call your AI agent sends us the record and an outline of each project document GSF-E checks (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); we use them for that call only and keep no copy. We never receive your code or the text of your documents.
- The record names the team: each person by an account ID that does not reveal who they are and a display name they choose, never an email address, with their role and who signed each gate and when. Those are personal data, and this notice covers them. Anyone who can read the repository can read them: you and your team decide who that is.
- We do not sell personal data, show ads, profile you, make automated decisions about you, or use your data to train AI models.
- Your AI agent (Claude, Codex or another) is run by its own provider under its own privacy policy. What your agent sends to that provider is not covered here.
3. What we collect, why, and on what basis
| Data | Why we need it | Legal basis (GDPR) |
|---|---|---|
| Account: name, email address, sign-in provider (such as Google or GitHub) and its account ID; your GSF-E account ID and display name; whether your account is on the allowed list, or closed | to create your account, sign you in, keep it secure, and send you service messages | performing our contract with you |
| Acceptance record: which version of the Terms and this notice you accepted, when, from which IP address | to prove what you agreed to | our legitimate interest in being able to show the agreement |
| What you state at sign-up: the country you are in, that you are 18 or over, and that sanctions do not bar you (Terms 2) | to check who may use the Service, and that it is not offered where it is closed (the EU, the EEA and the UK, for now) | performing our contract, and legal obligations (sanctions and export-control laws) |
| Team membership: which accounts may act on which project, held with the accounts by WorkOS | to let only a project's team use it | performing our contract |
| Project record, during each call: project and feature names, steps done or skipped, reasons given for skips, gate results (pass or fail) and checkpoint check results, the team's account IDs, display names and roles, who signed each gate and when, the GSF-E release used, and the project's GitHub repository name and folder (a repository name can contain a person's GitHub username) | to run the Service: check the record's signature, give your agent the right next step, and sign the updated record, which goes back to your repository. Used in a temporary folder that is deleted when the call ends | performing our contract |
| Document outlines, during each call: for 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; lines inside code blocks are never sent | to check that a step's document exists and has the sections the step asks for, without reading its text. Deleted when the call ends | performing our contract |
| Your date and time zone, sent with each call | to date sign-offs on your own day. The time zone is remembered in the memory of the server copy that answered, until that copy stops | performing our contract |
| Usage counts: how many requests an account and an IP address made in the last minute or day | to enforce usage limits. Counted in a server copy's memory only, never stored | our legitimate interest in security |
| Security logs: IP address, time, the address requested (which can include a project's ID, made from its name) and the result of each request, and errors (facts only, never a document, a heading or a message's text) | to keep the Service secure, investigate incidents and meet legal duties to keep logs | our legitimate interest in security, and legal obligations |
| Messages: what you send to our contact, grievance or security address (aiforproducts01@gmail.com, a Gmail mailbox), with our replies | to answer you and keep a record of complaints | our legitimate interest, and legal obligations |
You need to give us the account and acceptance data to use the Service; without it we cannot open an account. Everything else is created as you use the Service.
Under Indian law, we process this data for the purposes above, which you agree to when you sign up. You can withdraw that consent at any time, as easily as you gave it, by closing your account in the Service or writing to aiforproducts01@gmail.com. Withdrawing does not affect processing that already took place, and we will then stop the processing, apart from what the law requires us to keep (section 6).
We do not collect your code, the text of your documents, other repository contents, secrets or AI conversations: only the record and the outlines above, during each call. Please do not put them, or sensitive personal data, into names, display names, skip reasons, file names, document labels or headings.
4. Who receives it
- Our service providers, under contract and only to run the Service:
| Provider | What for | Where |
|---|---|---|
| Google Cloud | hosting the Service, acceptance records, logs | India (Mumbai region, asia-south1) |
| WorkOS, Inc. | sign-in and accounts, the allowed list, closed accounts, team membership (who may act on a project) | United States |
| Google (Gmail) | our contact, grievance and security mailbox: the messages you send us and our replies | Google's data centres, which a Gmail mailbox cannot choose; they may be outside India |
| [EMAIL PROVIDER] | service emails | [LOCATION] |
- Anyone who can read a project's repository (your team, anyone you or your organisation let read it, or everyone if it is public) sees its record, including display names, roles and sign-offs. You and your team decide who that is; we do not.
- Authorities, when the law requires it (for example a lawful order from a court, CERT-In or the Data Protection Board of India).
- A successor, if the Service is transferred to a company we form to run it. We will tell you first.
5. Where it is stored
Your account data and team membership are held by WorkOS in the United States. The messages you send us, and our replies, are in our Gmail mailbox, in Google's data centres, which may be outside India. The Service, acceptance records and logs are in India (Google Cloud, Mumbai). Project records stay in your repositories, wherever you keep them. If you live outside India, your data is processed in India and in the United States, and your messages to us wherever Google keeps them. Where the law requires a safeguard for this (for example standard contractual clauses for a provider outside India), we use one. You can ask us for a copy at aiforproducts01@gmail.com.
6. How long we keep it
| Data | Kept for |
|---|---|
| Account data | while your account is open; then kept, locked away, for 1 year after closure, because Indian law requires it, then erased |
| Team membership (which accounts may act on which project) | with WorkOS, while the project is open, so that, once that sign-in is in place, a teammate taken off is cut off at once; an entry goes when that teammate is taken off, and the project's when it is closed |
| Project records, check results and document outlines | not kept: used during each call, then deleted with the call's temporary folder. The record stays in your repository, where you and your team decide how long it is kept |
| Your time zone and usage counts | in a server copy's memory only, lost when that copy stops; usage counts for one day at most |
| Acceptance records | 3 years after your account closes, in case of a dispute |
| Security logs | 1 year |
| What you state at sign-up | with the acceptance record: 3 years after your account closes |
| Complaints and other messages | 3 years, in our Gmail mailbox |
We keep no backups of project data: the Service holds none. There are no organisation workspaces or administrators on the Service. In a project, its owner (the person who set it up, or the teammate they handed it to) adds and removes teammates, can hand the project to a teammate, and can close it; a removed teammate's past sign-offs stay in the record. Closing your account hands each project you own to its tech lead (or, with none, another teammate), so the team carries on; a project is closed only when nobody else is on its team. That happens at the project's next use after your account closed: a project nobody uses in the year your account's closed mark is kept keeps you as its owner after the mark is erased, and nobody can then add or remove its teammates, hand it over or close it (the team can still work in it). An owner who leaves an organisation but keeps their account keeps its projects until they hand them over; in the cloud, an administrator of the organisation in WorkOS will be the way to move them.
7. Your rights
You can ask us to:
- tell you what personal data we hold about you and how we use it, and give you a copy;
- correct, complete or update it;
- erase it, unless the law requires us to keep it;
- give you your account data in a machine-readable format (JSON), or send it to someone else;
- stop or limit some processing, or object to processing based on our legitimate interests;
- withdraw consent (section 3);
- under Indian law, nominate someone to use these rights for you if you die or cannot act yourself.
Write to aiforproducts01@gmail.com. We may need to confirm it is you. We reply within 30 days, or sooner where a law requires it.
Project records are not on the Service, so there is nothing of them for us to hand over or erase: they are in the project's repository. Your AI agent saves a copy of a project's record as a file at any time ("export our GSF-E data"), on your computer, without the Service. To have your display name changed or removed in a project's record, ask the project's owner (the person who set it up, or the teammate it was handed to), or the organisation whose project it is; removing it from the repository's history is for whoever controls the repository. We may pass a request about a project's record to them.
Complaints. Tell our Grievance Officer first (section 11). You can also complain to the Data Protection Board of India, or, in the EU or UK, to your data protection authority.
8. Security
We use encryption in transit and at rest, keep the data in one cloud region, limit access to production systems to the operator of the Service with multi-factor authentication, keep the Service's clocks synchronised, keep logs, sign every project record and every Safety Kit so a change is caught, and keep no project records on the Service (only who may act on each project, with the accounts at WorkOS). If a breach affects your personal data, we will tell you without delay: what happened, the likely consequences, what we have done, what you can do, and whom to contact. We also report breaches to the authorities as the law requires: CERT-In within 6 hours, the Data Protection Board of India, and EU or UK authorities within 72 hours where their rules apply.
9. When we act for your organisation
When an organisation uses the Service for its team, we process its projects' records and document outlines, including its people's display names and sign-offs, on its instructions, during each call only; the one thing kept is who may act on each of its projects (team membership, with WorkOS). Organisations can sign our Data Processing Agreement. Questions about how an organisation uses its project data should go to that organisation.
10. Children
The Service is for people aged 18 or over. We do not knowingly collect data about anyone younger. If you think we have, tell us and we will erase it.
11. Grievance Officer
Arjun Sharma, Gwalior, Madhya Pradesh, India · aiforproducts01@gmail.com
We acknowledge complaints within 24 hours and resolve them within 7 days.
12. Changes
We will tell you before a material change to this notice takes effect, by email and in the Service. Earlier versions are available on request.
13. This website: analytics, forms and the community
This section covers the aiforproducts.in website, its forms and the community. It sets no advertising or tracking cookies.
- Analytics. We use Cloudflare Web Analytics to count visits to this website. It is cookie-free: it sets no cookies, stores nothing on your device and does not follow you across other websites. It records facts about each visit, such as the page, the site that linked to it, the browser, the type of device and the country, and shows us totals only. Cloudflare, Inc. (United States) provides it, and also hosts this website, so it handles the request data (such as your IP address) needed to serve the pages and keep them secure. Our basis is our legitimate interest in knowing which pages are useful and keeping the site secure.
- The community schedule. The Community page reads the session schedule from a Google Sheet we publish. Your browser fetches it from Google, so Google receives the usual request data, such as your IP address, under Google's own privacy policy. Nothing you type is sent.
- Forms. Our consulting, early-access and community forms are Google Forms. What you enter goes to our Google account and is used only to reply to you, prepare a quote, or send you session details. We keep it only as long as we need it for that, and you can ask us to erase it at any time (section 7).
- The WhatsApp group. The community group runs on WhatsApp, under WhatsApp's own terms and privacy policy. Other members of the group can see your name and phone number as WhatsApp shows them. New members are approved by the group admin, and you can leave at any time.
- Email. Messages to aiforproducts01@gmail.com are handled as described in section 3 (Messages).
Weekend workshop bookings
- What we collect. To reserve a seat at a paid weekend workshop, you pay on Razorpay's hosted payment page for that workshop. It asks for your name, email address, phone number and role, and what you want to get out of the workshop. Until online payment is open for a workshop, our Google Form "Weekend workshop: reserve a seat" asks for the same, and which workshop you want.
- Why. To hold your seat (and, while we use the form, to email you a payment link); to send you the workshop's times and joining details; to reach you about a change, by phone if it is close to the start; and to shape the workshop around what the group wants from it. Our basis is taking the steps you ask for before a contract, and then performing it. What you enter on our form goes to our Google account.
- Payment. Payments go through Razorpay's hosted payment page, run by Razorpay (Razorpay Software Private Limited) under its own terms and privacy policy. Razorpay collects your payment details; we do not see or store your card, bank or UPI details. Razorpay sends us your name, email address and phone number, the answers you gave on its page, and the payment's amount, date and reference. Razorpay emails you the receipt.
- How long we keep it. For a booking, we keep your form answers, the payment and any refund as accounting records, for as long as Indian tax and accounting law requires. Answers that do not lead to a booking are kept only as long as we need them to reply to you. You can ask us to erase what the law does not require us to keep (section 7).