Acceptable Use Policy

This Acceptable Use Policy governs everything you do with SmartOrderCapture: workflows you build, templates you publish or install, API calls you make, and anything the Android application does at your instruction. It forms part of the Terms of Service, and breaching it is a breach of that contract.

It applies to you, to anyone using your account, and to every member of an organisation workspace you administer.

The list below is illustrative, not exhaustive. If something is obviously abusive but not named here, it is still prohibited.

Almost everything below follows from that. SmartOrderCapture exists so that a person can stop repeating themselves — not so that a person can out-click everyone else, defraud an advertiser, or wear down a service that never agreed to be automated.

You must not use the Service to:

• interact with any application, website or service in a way its terms of service, acceptable use policy, robots directives or automation policy prohibit;
• access an account you are not authorised to access, or use automation on an employer’s or client’s device or account without their documented permission;
• defeat a rate limit, a CAPTCHA, an anti-bot control, a device-attestation check, a paywall or any other access control;
• create, verify or operate accounts in bulk, or make automation appear to be organic human activity in order to evade a provider’s enforcement; or
• scrape or harvest personal information about other people, whether from an application screen or from any other source.

Whether a given application permits automation is your responsibility to determine, before you run the workflow. We give no assurance either way.

Some categories are prohibited outright and enforced technically. Workflows may not target the following applications, and the restriction is compiled into the Android application so it holds even with no network connection, and mirrored server-side so an offending workflow is rejected before it syncs or publishes.

Gig-economy and delivery dispatch

Automatically accepting, declining or filtering offers distorts a marketplace other people depend on for income, and every major platform prohibits it. Do not automate driver, courier or shopper applications.

Ticketing

Automated purchasing of tickets is prohibited. In the United States it may also violate the Better Online Ticket Sales (BOTS) Act.

Advertising SDKs

Generating impressions, clicks or installs by automation is advertising fraud. Do not target ad SDKs or any surface whose purpose is to count human attention.

The denylist currently covers 17 package names. The live list, with each entry and its category, is in the denylist reference. We add to it as new abuse patterns appear; additions take effect on your next sync or application update.

Illegal and harmful activity

• Anything unlawful, or that facilitates unlawful activity, including fraud, money laundering, sanctions evasion, or the sale of controlled or counterfeit goods.
• Harassment, stalking, threats, doxxing, or automating contact with a person who has asked you to stop. Do not use the Service to monitor another person’s device or communications without their knowing consent.
• Child sexual abuse material, or content that sexualises minors, in any form. We report this to the National Center for Missing & Exploited Children and to law enforcement.
• Content or automation that promotes violence, terrorism, or targets people on the basis of a protected characteristic.

Messaging and telephony

• Bulk, unsolicited or automated commercial text messages. If you use an SMS action, you are the sender: you are responsible for consent, for opt-out handling, for identifying yourself, and for compliance with the Telephone Consumer Protection Act, the CAN-SPAM Act, carrier rules and any equivalent law where your recipients are.
• Spam, phishing, spoofing, or any message designed to deceive a recipient about who sent it.

Security and integrity

• Distributing malware, or building workflows that install, hide or persist software without the device owner’s knowledge.
• Probing, scanning or testing the vulnerability of our systems or anyone else’s without authorisation. Good-faith research on our own systems is welcome under the security policy.
• Denial-of-service traffic, whether by volume from many devices or by a workflow looping requests against an endpoint.
• Interfering with the Service — circumventing rate limits, kill switches, the denylist, plan limits or licensing checks, or overloading shared infrastructure.

Financial and safety-critical

• Automating banking, brokerage, payment or cryptocurrency applications to move funds, place trades or approve transactions.
• Gambling and betting applications, wherever automated wagering is restricted.
• Any use where a failure, delay or mis-tap could cause death, injury, or serious environmental or financial harm — including medical treatment, emergency alerting, vehicle or machinery control, aviation, navigation and critical infrastructure.

Marketplace

• Publishing a template that violates this policy, misrepresents what it does, hides an action from its description, or targets a denylisted application.
• Manipulating ratings, install counts or search placement, including with duplicate accounts.
• Publishing anyone else’s content without the right to do so. Copyright complaints are handled under the DMCA Policy.

To be clear about the large space this policy leaves open — all of the following are exactly what the Service is for:

• Accessibility. Flattening a multi-tap interface into one trigger, replacing gestures you cannot perform reliably, and automating anything on your own device that your own hands would otherwise do.
• Personal productivity. Morning and end-of-day routines, focus modes, device settings, launching and arranging your own applications.
• Your own work. Capturing data in the field, logging to your own spreadsheet, calling your own APIs, cross-posting your own content to your own accounts, where the platforms involved permit it.
• Automating your own systems at any scale you like.

We enforce in proportion to what happened. Depending on severity, intent and history, we may:

• contact you and ask you to fix the problem;
• kill-switch a specific workflow so it stops executing on every device it is synced to;
• unpublish or remove a template, and reverse related payouts;
• restrict marketplace access, or apply a stricter rate limit;
• suspend the account pending investigation; or
• terminate the account, and where warranted report it to law enforcement or to the affected platform.

Where the violation is curable and the risk allows, we will give notice and a reasonable chance to fix it first. For severe violations — child safety, malware, fraud, or an active threat to another person or system — we act immediately and without notice.

If you think we got it wrong, reply to the enforcement notice or write to abuse@smartordercapture.com. A person will review it, and we will restore access if we made a mistake.

No refund is due for a period during which an account is suspended or terminated for violating this policy.

If you see a template, workflow or account that violates this policy — or a workflow automating your platform in a way you prohibit — tell us. Use the abuse report form or write to abuse@smartordercapture.com.

Include what you saw, where (a template link, an account, a package name), and why it breaks the rules. If you are reporting on behalf of a platform whose terms are being violated, say so and identify yourself — we prioritise those and will act on a credible report from a platform operator quickly.

We acknowledge reports within two business days and tell you the outcome where we lawfully can. Copyright complaints go through the DMCA process instead, which has its own required form.

Abuse patterns change, so this policy will too. We will update the “Last updated” date, and for material changes we will give at least 30 days’ notice as the Terms of Service require — except where a change is needed immediately to stop active harm, in which case it takes effect at once and we will explain why.