Smart Order Capture
Legal

Acceptable Use Policy

Last updated: 2026-05-16

Pre-launch placeholder. This document has not yet been reviewed by counsel and is published so the user-facing flow exists end-to-end. The final version, signed off before public launch, will replace this text. Do not rely on it as a binding legal document yet.

smartordercapture is built so people can automate their own phone interactions with apps they have the right to use. There are categories of automation we won't enable, regardless of subscription tier, because they violate the host platform's Terms of Service, harm third parties, or both. These restrictions are enforced both server-side (the API and marketplace reject offending workflows) and client-side (the Android app refuses to execute workflows that target denylisted packages, even with no network connectivity).

What you may not automate with smartordercapture

  • Gig delivery driver apps. Including DoorDash, Uber / Uber Eats Driver, Walmart Spark Driver, Amazon Flex, Instacart Shopper, Lyft Driver, and similar platforms. Automating offer acceptance violates these platforms' ToS, exposes drivers to account deactivation, and takes work from other drivers.
  • Ticket purchase platforms. Including Ticketmaster, StubHub, SeatGeek, and comparable services. Automated buying is prohibited by these platforms and, in many U.S. jurisdictions, by the federal BOTS Act of 2016.
  • Ad fraud. Workflows that target ad-network SDKs (Google AdMob, Meta Audience Network, AppLovin, Unity Ads, etc.) to simulate views, clicks, or installs.
  • Account-takeover or credential-stuffing automations.
  • Engagement farming on social platforms. Mass-liking, mass-following, mass- commenting on accounts you don't control. Posting to your own accounts is fine.
  • Anything that requires root, shell, or Xposed. We don't support these and never will.
  • Harassment, doxxing, stalking, or any workflow that targets a specific natural person without their consent.
  • Bypassing CAPTCHAs or anti-bot defenses on platforms where you do not have explicit authorization.

How enforcement works

The Android client ships with a hard-coded list of package names corresponding to the categories above. Workflows that target a denylisted package fail to validate during creation, fail to sync to a device, and fail to execute on-device — three layers of defense. Violations are logged and may result in account suspension. We publish a takedowns log of marketplace templates removed for AUP violations.

Consequences of violation

  • First-time inadvertent violation: warning and education, denylisted workflow refused.
  • Repeated or willful violation: account suspension.
  • Severe violations (fraud, CSAM, threats of violence): immediate termination and report to law enforcement.
  • Marketplace creators: removed templates count against publishing privileges.

Reporting abuse

If you see a workflow, template, or user violating this policy, report it via our abuse form or email abuse@smartordercapture.com. We triage reports within one business day.

Updating the denylist

We update the denylist as we learn about new categories of misuse. Additions are announced in the changelog and reflected in the next Android client release. The current denylist is open- source within the client's build and visible to anyone who inspects the APK.