M.I.L.F. Shiksha
All legal pages
Effective October 1, 2026 · 3 min read

Legal

Acceptable Use Policy

What we will not allow — scraping, spam, rate-limit evasion, harassment — and how enforcement works without accounts.

Why this policy exists

The free limits, the anonymous design and the absence of accounts only work if people use the service in good faith. This Acceptable Use Policy ("AUP") defines what we will not allow, so nobody is surprised by an enforcement action. It applies alongside the Terms of Service.

You must not

  • Hammer the service. No scripts, bots or loops that call the API faster than a human would. The rate limits (5 Wingman analyses per day, 10 questions per hour, 60 searches per minute) are part of the terms — evading them (rotating IPs, replaying requests, exploiting the fail-open path) is a violation.
  • Scrape or harvest content. Don't mirror the guides, bulk-download the database, or build a competing dataset by crawling. Reasonable single-page use, linking and search-engine indexing are fine; automated bulk extraction is not.
  • Spam. No unsolicited submissions, repetitive questions, or using the Q&A to advertise anything — services, products, sites or supplements.
  • Send malicious code. No payloads in questions or pasted text: no exploit attempts against the site, its providers or other users, no injection attempts, no attempts to smuggle commands into the AI prompt.
  • Probe or disrupt. No port scanning, vulnerability scanning, load testing, denial-of-service attempts, or accessing endpoints you have not been given permission to test. Found a bug? Report it privately — we welcome that; unannounced stress-testing we do not.
  • Impersonate or deceive. No pretending to be us, our staff, a doctor, or another person. The site's doctors are curated content contributors, not people you can contact through it.
  • Post other people's personal data. Phone numbers, email addresses, full names with cities, addresses, or private conversations you were not party to — our safety screens reject many of these, and deliberately working around the screen is itself a violation.
  • Harass or endanger anyone. No threats, no targeting of individuals, no content that sexualises minors under any circumstances (this is grounds for immediate permanent blocking and, where required, reporting to authorities).
  • Violate the law. No using the service for any unlawful purpose, in violation of any applicable regulation, or to facilitate non-consensual activity.
  • Circumvent protections. No disabling or spoofing the rate limiter, the safety screens, the Content-Security-Policy protections, or any other control meant to keep the service and its users safe.
  • Resell or misrepresent. No selling access to the service, no sublicensing our content, and no presenting AI-generated suggestions from Wingman as professional advice or as statements of ours.

Content rules for what you submit

Questions and pasted text must be yours to share. Strip personal identifiers before submitting — our screens reject obvious ones, but you are the last line of defence for your own privacy and other people's. Do not paste medical records, government identifiers, or third parties' private conversations.

Wingman is a communication-reading tool, not a surveillance tool: use it on conversations you are part of.

Enforcement

We enforce proportionately:

  1. Automatic rejection — content failing the safety screen is refused with an explanation (422) and never stored.
  2. Rate limiting — repeated over-limit requests get 429 responses until the window resets.
  3. Blocking — serious or repeated violations lead to network-level blocking of your salted rate-limit hash for a period or permanently. Because there are no accounts, blocking is necessarily blunt; it targets traffic patterns, not a profile of you as a person.
  4. Removal — violating content is deleted from the database.
  5. Legal referral — where a violation involves unlawful content or activity, we will cooperate with competent authorities as the law requires.

We are not obliged to give advance notice before enforcing, but we will consider good-faith explanations sent to the contact below.

Reporting violations

See someone abusing the service? Email anuragpanda.dev@gmail.com with what you saw (a URL or public question ID helps). Security issues should be reported privately first — see the Privacy Policy for responsible-disclosure expectations.

Changes

We may revise this policy; the date at the top shows the last revision. Continuing to use the service after a revision means you accept the revised policy.

Contact

anuragpanda.dev@gmail.com — or the Contact page for more options.