SwitchyardPricing

Privacy policy

Last updated 13 October 2026

Switchyard is built to keep as little about you as it can: most of what you do never leaves your browser. This policy says what we do keep, why, for how long, who helps us handle it, and how to use your rights. It is our notice under India's Digital Personal Data Protection Act, 2023.

1. Who is responsible

Robin Maurya, based in India, runs Switchyard and is responsible for your personal data as its “Data Fiduciary”. Questions, requests and complaints go to our grievance officer (section 11) or to robinmaurya619@gmail.com.

When you put other people’s personal data into your modules, you decide what happens to it: for that data you are the Data Fiduciary, and we handle it for you as your Data Processor, under our terms.

2. What stays in your browser

Your modules, files, run results, settings and API keys are kept in your browser, on your device, and we can’t see them. Your keys are sent only with the requests that need them: straight to the model provider you chose, or through our relay, which forwards each request and keeps nothing (not the key, not your text, not the answer). A model running on your own computer, such as Laya, sends nothing anywhere.

When you run a module, your text goes to the model provider you chose, under that provider’s own privacy policy. Read it before you send personal data.

3. What we keep, why, and for how long

If you use Switchyard without an account, we keep only security logs. With an account, we keep:

Your email address, and how you signed in (email link, Google, GitHub or your company)
Why: To make and secure your account, and to write to you about it
Basis: You give it to us to use this feature (section 7(a))
How long: While your account is open; deleted within 30 days of closing it
The publisher name you choose
Why: To show it on modules you publish
Basis: You give it to us to use this feature (section 7(a))
How long: While your account is open
Your plan and subscription status from Paddle (not your card)
Why: To give you what you paid for
Basis: You give it to us to use this feature (section 7(a))
How long: While your account is open, then as long as tax and accounting law requires (up to 8 years)
Modules you save online, their versions and examples (Pro)
Why: To keep them for you and the people you share them with
Basis: You give it to us to use this feature (section 7(a))
How long: Until you delete them or close your account
Share links you make, and how often each was opened
Why: To let others view a module, and to show you its use
Basis: You give it to us to use this feature (section 7(a))
How long: Until you switch the link off or delete it
Teams: members' email addresses, roles, the team library and its activity log
Why: To run the team and let its owner see who changed what
Basis: You give it to us to use this feature (section 7(a))
How long: While the team exists
Modules you publish in the marketplace, with their samples and listing details
Why: To show and distribute them
Basis: You give it to us to use this feature (section 7(a))
How long: While listed; a removed listing's record for 180 days, as the IT Rules require
Your ratings and reviews
Why: To show them on the module
Basis: You give it to us to use this feature (section 7(a))
How long: Until you delete them or close your account
Which marketplace modules you downloaded or looked inside, and when you last passed the human check
Why: To keep downloads fair, stop bulk copying and tell you about updates
Basis: You give it to us to use this feature (section 7(a))
How long: While your account is open
Reports you send about a module or share link
Why: To review and act on them
Basis: The law requires it (section 7)
How long: Until resolved, then 180 days
Access tokens you make (a scrambled copy and their first characters, never the token itself)
Why: To let your own tools reach your account
Basis: You give it to us to use this feature (section 7(a))
How long: Until you revoke them or close your account
Modules your AI tools send as drafts
Why: To open them in the builder
Basis: You give it to us to use this feature (section 7(a))
How long: One week
How many items you ran through the Run API, the API relay or the cloud runner, and how many AI builder requests you made and their cost
Why: To apply your plan's allowances
Basis: You give it to us to use this feature (section 7(a))
How long: While your account is open
For a module you keep running in the cloud (Pro, only if you switch it on): its model keys, secrets and inputs, encrypted; waiting webhooks; its latest 100 results
Why: To run that module while your browser is closed
Basis: Your consent, given when you switch it on (section 6)
How long: Keys, secrets and inputs until you switch it off, then deleted at once; results while it is on
Emails and complaints you send us
Why: To answer them
Basis: You give it to us to use this feature (section 7(a))
How long: Until resolved, then up to one year
Security logs: your IP address, the time, the page or API called and your browser type
Why: To keep the service secure, investigate misuse, and meet Indian log-keeping rules
Basis: The law requires it (section 7)
How long: As long as Indian law requires (currently up to one year), then deleted

Sections refer to the Digital Personal Data Protection Act, 2023. We collect no other personal data, and we ask only for what each feature needs.

4. What we never do

  • We never sell your data, or share it for advertising.
  • We never use your modules, your text or your models’ answers to train or tune any model.
  • We use no advertising or tracking cookies, and no analytics that follow you across sites.
  • We never see or keep your card details: Paddle handles payments.

5. Cookies and browser storage

We use your browser’s storage to keep you signed in and to keep your modules, keys and settings on your device. We set one cookie only if you run your own model server, listing its address so the page may reach it. Cloudflare’s human check, shown in the marketplace, may read signals from your browser to tell people from scripts. All of these are needed for the features you use; none track you.

6. Who helps us handle it

These companies process data for us, only to provide Switchyard, under contracts that require them to protect it:

  • Vercel hosts the website, the app, the relay and our server functions, and keeps the security logs.
  • Supabase holds accounts, sign-in, and everything in the table above.
  • Paddle sells Pro as our reseller and Merchant of Record. It handles your payment, invoices, tax and refunds as the seller, under its own privacy policy, and tells us your subscription’s status.
  • Cloudflare runs the human check in the marketplace.
  • Our email provider sends sign-in links and account emails.
  • Anthropic runs the AI builder’s model, when the AI builder is available: what you ask it and the module you’re editing go to Anthropic to propose a change, and are not kept by us.
  • Google, GitHub or your company’s sign-in service, only if you choose to sign in with them.

We may also share data when the law requires it, such as a lawful order from a court or an authorised government agency, or to protect people from harm or fraud. If Switchyard is transferred to a new owner, your data goes with it under this policy, and we’ll tell you first.

7. Where it is kept

Our providers’ servers may be outside India, for example in the United States or the European Union. The Digital Personal Data Protection Act, 2023 allows this, except to countries the Government of India restricts; we don’t send data to them.

8. How we protect it

Data travels encrypted (HTTPS) and is stored encrypted by our providers. Keys you keep in the cloud are sealed again with our own encryption. Only the people who run Switchyard can reach our systems, each with their own account and two-step sign-in, and only when the work needs it. Access tokens and invitation links are kept only as scrambled copies. We keep security logs to detect misuse.

If a breach affects your personal data, we’ll tell you and the Data Protection Board of India as the law requires: what happened, what it means for you, what we’re doing, and what you can do. We report cyber security incidents to CERT-In within the time Indian rules set.

9. Your rights

Under the Digital Personal Data Protection Act, 2023, you can:

  • get a summary of the personal data we keep about you, what we do with it, and who we have shared it with (download it yourself under Your account → Your data);
  • have it corrected, completed or updated;
  • have it erased, unless the law requires us to keep it (close your account yourself under Your account → Your data, which erases it as the table says);
  • withdraw your consent where we rely on it, as easily as you gave it: for the cloud runner, switch the module off;
  • nominate someone to use these rights for you if you die or can’t act;
  • complain to our grievance officer, and then, if you aren’t satisfied, to the Data Protection Board of India.

You can download your data and close your account yourself, in the builder’s account window. To use any other right, or if you’d rather write, email our grievance officer from your account’s email address, saying which right and what it concerns. We may ask you to confirm it’s you. We answer within 30 days, and always within 90 days. You can delete modules, share links, access tokens and ratings yourself at any time, and switch off a cloud module, which deletes its keys at once.

If you’re outside India, you have these rights too, and any others your own country’s law gives you (in the EU and UK, for example, to object and to complain to your data protection authority).

10. Children

Switchyard is only for people aged 18 or over. We don’t knowingly keep data about children; if we learn an account belongs to someone under 18, we close it and delete its data.

11. Grievance officer and contact

For any question, request or complaint about your personal data or about Switchyard, write to our grievance officer. We acknowledge it within 24 hours and resolve it within the times above. You can ask for this policy in English or in any language listed in the Eighth Schedule to the Constitution of India.

  • Grievance officer: (to be added before launch)
  • Email: robinmaurya619@gmail.com
  • Business address: (to be added before launch)
  • Seller: Robin Maurya, based in India

12. Changes to this policy

We’ll update this policy when what we keep or why changes. The date at the top shows the latest version. If a change matters, we’ll tell account holders by email or in the app before it applies, and ask for consent again where the law needs it. Robin Maurya is responsible for this policy.

Terms · Privacy · Refunds · Grievances