// legal

Terms of Service

Last updated: 16 May 2026

In one paragraph

Pickle is a hosted MCP server you can plug into Claude / Cursor / Codex / Cline to audit your ClickUp / Slack / Microsoft Teams workspace. It's currently free during Beta. By using it, you accept these terms. They cap my liability, govern what you can and can't do with the service, and explain what happens when Pro launches.

1. Who runs this

The "Service" is Pickle (pickle.adityaarsharma.com), operated by Aditya Sharma (sole founder, based in Kolkata, India). "I", "me", "we" all refer to Aditya. "You" / "your" means the person using the Service.

2. What you get during Beta

While Pickle is in Beta (first 200 sign-ups), you get:

A free Pickle key delivered to your email
Access to the hosted MCP server at https://pickle.adityaarsharma.com/mcp
All 13 audit patterns across ClickUp, Slack, and Microsoft Teams
Unlimited team members audited, unlimited scans
Founder email support at [email protected]

When the Beta closes (200 seats claimed), Pro launches with team tiers. Beta users grandfather into the lowest price I'll ever charge.

Beta = no warranty

Pickle is provided "as is" during Beta. I make no promise of uptime, accuracy, or fitness for any particular purpose. The patterns can be wrong. The server can be down. The brief can miss things. Treat it like a tool to assist your judgment, not replace it.

3. Your responsibilities

Tokens are yours. Your ClickUp / Slack / Microsoft Teams API tokens travel through Pickle to call those platforms on your behalf. You're responsible for keeping them secret and revoking them if compromised. Pickle never stores them; you store them in your local MCP config.
Workspace permissions are yours. Anything Pickle reads or does in your workspace is what your token allowed. If you give Pickle a write-capable token, it can write. Generate read-only tokens if that's what you want.
Don't abuse the service. No automated scraping that exceeds reasonable per-user load, no attempts to read other users' keys, no probing for vulnerabilities without contacting me first.
One key per person/team. Don't share your Pickle key publicly or with strangers. If you do, I may rotate it.
You're using your own workspace's data. If you're not allowed by your employer to connect a third-party MCP server, that's on you, not me.

4. Acceptable use

Don't use Pickle to:

Audit a workspace you don't have authorization to audit
Surveil employees in ways that violate local labor laws (jurisdictions like the EU have strict rules)
Build a competing service by scraping the patterns
Run automated load against the server outside normal MCP usage
Anything illegal under the laws of India, the EU, your country, or any country where you operate

I reserve the right to revoke your Pickle key at any time if I believe you're violating these terms. I'll email you first if it's not an emergency.

5. Intellectual property

The code running Pickle's server is open source under the MIT license. You can read it, fork it, run your own copy.
The "Pickle" name, logo, and landing-page design are mine. Don't use them to brand a competing product or imply endorsement.
The 13 audit patterns + their specific rule definitions are mine. The general idea of "audit a workspace" is fair game.
Your workspace data, your tokens, your team's content — all yours. Pickle never claims any rights over it.

6. Service availability

I'll try hard to keep Pickle up. I run it on my own infrastructure (Hetzner + Cloudflare). I do not commit to any specific uptime SLA during Beta. When Pro launches, paid tiers may include uptime commitments.

If the service goes down and you're stuck, email me. The hosted Cloud is a convenience — the code is open source, you can self-host if availability is critical for you.

7. Pro tier (future)

Pro is not live yet. When it launches, you'll have the option to:

Stay on Free if your usage fits (some limits may apply)
Upgrade to Pro at the early-bird price you've been grandfathered into (Beta cohort only)
Stop using Pickle

When you pay for Pro, additional terms will apply (billing, refunds, plan changes). I'll publish those separately and link them here before charging anyone.

8. Limitation of liability

To the maximum extent permitted by law, my total liability to you for any claim related to the Service is capped at the amount you've paid for Pickle in the 12 months before the claim arose. While Pickle is free, that cap is zero. I am not liable for indirect, incidental, consequential, or special damages.

This doesn't limit liability for things the law says can't be limited (gross negligence, willful misconduct, etc.).

9. Indemnity

If your use of Pickle gets me sued by a third party (e.g. you audited a workspace you weren't allowed to), you agree to indemnify me for reasonable legal costs.

10. Termination

By you: stop using Pickle anytime. Remove the MCP config block from your assistant. Optionally email me to delete your data (see Privacy Policy).
By me: I can suspend or terminate any Pickle key for violation of these terms, with notice unless it's an emergency.

11. Changes to these terms

If I change anything material, I'll update the "Last updated" date and email everyone on the signup list at least 14 days before the new terms take effect. Continued use after that means you accept the new terms.

12. Governing law & disputes

These terms are governed by the laws of India. Any dispute will be resolved in the courts of Kolkata, India. If you're in the EU, you keep any consumer protection rights that local law grants.

13. Contact

Questions about these terms? Email [email protected]. I'm the only person who reads it.