TaskHound Acceptable Use Policy

Effective Date: July 2, 2026  |  Last updated: July 2, 2026

This Acceptable Use Policy ("AUP") governs use of TaskHound, provided by Snaju LLC ("Snaju," "we," "us"), including TaskHound Containers, agent sessions, TH Git, the TaskHound Pipeline, deployments on th.works, and all related services (the "Service"). It is incorporated by reference into the TaskHound Terms of Service and applies to all users of the Service, including every member of a Team and any third party accessing a Customer's deployments. Capitalized terms not defined here have the meanings given in the Terms of Service.

BY USING TASKHOUND, YOU AGREE TO COMPLY WITH THIS AUP. MATERIAL VIOLATIONS MAY RESULT IN SUSPENSION OR TERMINATION UNDER THE TERMS OF SERVICE.

Article I - General Principles

Section 1.1 - Lawful Use. The Service is provided exclusively for lawful purposes. You must comply with all applicable local, state, national, and international laws when using the Service.

Section 1.2 - Agent Conduct Is Your Conduct. AI agent sessions run at your direction, in your Container, with your provider credentials. Anything an agent executes, hosts, transmits, or deploys through the Service is attributed to you under this AUP, exactly as if you had done it yourself. Configure, steer, and supervise your agents accordingly.

Section 1.3 - Responsibility for Your Team and Visitors. The Team owner and admins are responsible for the conduct of invited users, and for the content their deployments serve to third parties.

Section 1.4 - Platform Flow-Down. TaskHound Containers run on the DartNode Platform (AS399646). The DartNode Acceptable Use Policy published at dartnode.com/legal/aup applies to all workloads on that platform and flows down to you as a TaskHound customer, in addition to this AUP. Where the two policies differ, the stricter rule applies to conduct on the platform.

Article II - Prohibited Content

Section 2.1 - Illegal Activity. The following are prohibited anywhere in the Service: activity violating any applicable law; fraud, identity theft, or financial crimes; money laundering or terrorist financing; unlicensed sale of controlled substances; trafficking in stolen or counterfeit goods; unlicensed gambling operations; violations of export control or sanctions law; and any activity that would subject Snaju to criminal or civil liability.

Section 2.2 - Prohibited Content. The following content may not be stored in a Container, committed to TH Git, or served from a deployment:

1. CSAM: any content depicting the sexual exploitation or abuse of minors. Confirmed CSAM is reported to NCMEC as required by 18 U.S.C. § 2258A, evidence is preserved as required by law, and the account is terminated immediately without notice;
2. Non-consensual intimate imagery;
3. Copyright-infringing material distributed without authorization, including pirated software, media, and games;
4. Defamatory content that is knowingly false and injurious;
5. Content inciting or glorifying violence or terrorism;
6. Doxing - publishing private information to harass, intimidate, or endanger; and
7. Counterfeit goods or trademark-infringing storefronts.

Article III - th.works Deployments

Section 3.1 - Purpose. Deployments on *.th.works exist so teams can review, demonstrate, and share running builds of their own work. They are development and review environments, not general-purpose anonymous hosting.

Section 3.2 - Prohibited Demo Content. In addition to Article II, deployed demos must not host or serve:

1. Illegal or abusive content of any kind;
2. Phishing pages, credential-harvesting forms, or lookalike login portals for third-party brands;
3. Malware, exploit kits, or drive-by download payloads;
4. Spam landing pages, link farms, or deceptive redirect chains;
5. Pirated media distribution or warez indexes;
6. Content that impersonates another organization in a misleading manner; or
7. Services designed to conceal the origin of third-party traffic (open proxies, relays, or anonymization endpoints).

Section 3.3 - Enforcement on Deployments. Snaju may stop a deployment, unroute its th.works subdomain, or disable public access to it at any time when it reasonably believes this Article is being violated, independent of other enforcement under Article VII.

Section 3.4 - Responsibility to Audiences. If you make a demo public or share it with clients, you are the publisher of what it serves. Use access controls (basic-auth, team-only) for anything not intended for the public.

Article IV - Prohibited Technical Activity

Section 4.1 - Network Abuse. The following are prohibited, whether initiated manually or by an agent: launching or facilitating DoS/DDoS attacks; unauthorized access attempts against any system; port scanning or vulnerability probing without the target owner's authorization; brute forcing or credential stuffing; operating botnet command-and-control; hosting or distributing malware; hosting phishing infrastructure; intercepting traffic not intended for your systems; IP spoofing; and any manipulation of Internet routing.

Section 4.2 - Email and Messaging Abuse. The Service may not be used to send unsolicited bulk email or SMS, harvest addresses, operate open relays, forge message headers, or evade sender-reputation systems. Outbound port 25 is restricted by default; legitimate transactional-mail development should use an authenticated third-party mail API.

Section 4.3 - Proxies and Anonymization. Operating open proxies, open recursive DNS resolvers, open mail relays, commercial VPN/proxy services, or Tor exit nodes from a Container is prohibited without prior written authorization from Snaju.

Section 4.4 - Cryptocurrency Mining. Cryptocurrency mining and similar resource-intensive validation activities are prohibited in TaskHound Containers. Containers are sized and priced for development workloads.

Section 4.5 - Security Violations. You may not attempt to bypass or disable the Service's security or isolation controls, access another Team's Container or data, share account credentials, tamper with slot or resource enforcement, or use the Service to develop or stage offensive tooling for unauthorized deployment against third parties.

Article V - Resource Use and Fair Use

Section 5.1 - Documented Limits. Containers are subject to the resources, concurrent agent sessions, deployment counts, and snapshot retention of the subscribed Container tier. You may not circumvent these controls, including concurrency enforcement, or use the Service in a way that materially degrades the platform for others.

Section 5.2 - Persistent Load. Deployments and background processes designed to consume maximum resources continuously, or to repurpose a Container as generic production hosting inconsistent with its tier, are prohibited. Idle demos may be auto-slept per your tier.

Article VI - Fraud and Account Integrity

Section 6.1 - Prohibited Fraud. Payment fraud (including use of payment instruments without the accountholder's authorization), identity fraud, synthetic identities, automated account creation, and multi-account abuse to evade enforcement or promotional limits are prohibited.

Article VII - Abuse Reporting and Enforcement

Section 7.1 - Reporting. Report abuse to abuse@taskhound.com, including where possible: the th.works URL, hostname, or IP involved; a description of the violation; supporting evidence (logs, headers, screenshots); and timestamps with time zone.

Section 7.2 - Our Commitments. Snaju will acknowledge abuse reports within twenty-four (24) hours, provide an initial substantive response within seventy-two (72) hours, and pursue good-faith remediation of confirmed abuse.

Section 7.3 - Your Obligations. Customers must respond to abuse notifications within twenty-four (24) hours, take corrective action for confirmed issues, provide remediation updates, and prevent recurrence - including by constraining the agent, prompt, or workflow that produced the violation.

Section 7.4 - Range of Responses. Upon a confirmed violation, Snaju may - proportionate to severity and pattern - issue a warning, throttle resources, remove content, stop deployments or unroute th.works subdomains, suspend sessions or the Container, terminate the Service or the account, preserve data for lawful investigation, or refer the matter to law enforcement. First-time, isolated, or inadvertent violations are generally addressed through warning and cooperative remediation.

Section 7.5 - Immediate Action. Snaju may act without advance notice for illegal content (in particular CSAM), active attacks sourced from a Container, severe resource abuse affecting the platform, court orders, or imminent harm to Snaju, the DartNode Platform, or third parties.

Section 7.6 - No Refunds on AUP Termination. Services terminated for confirmed AUP violations are not eligible for refunds, except as required by applicable law.

Article VIII - Modifications

Section 8.1 - Changes. Snaju may modify this AUP from time to time. Updates are posted with a revised "Last updated" date; material changes are notified by email or dashboard notice. Continued use after the effective date constitutes acceptance.

Article IX - Contact

Snaju LLC - TaskHound
League City, Texas, United States
Abuse: abuse@taskhound.com
Legal: legal@taskhound.com
Support: support@taskhound.com

BY USING TASKHOUND, YOU ACKNOWLEDGE THAT YOU HAVE READ, UNDERSTOOD, AND AGREE TO COMPLY WITH THIS ACCEPTABLE USE POLICY.