Acceptable Use Policy

Sprigged exists to help small groups run their thing — rosters, snack rotations, gear lists, carpools. This policy describes what you agree to do (and not do) when you use Sprigged. It complements our Privacy Policy, which covers what we collect and how we use it.

Sprigged is operated by Brefi LLC in the United States. Questions about this policy go to [email protected].

Who this applies to

This policy applies to anyone who creates, joins, or contributes content to a Sprigged patch — whether you're a maintainer running an app you built, a member sharing records, or someone authoring an app with Sprigged's "Build with AI" assistance. By using Sprigged you agree to follow this policy.

Prohibited content

You may not create, store, share, or distribute any of the following through Sprigged:

• CSAM and child-safety violations. Any content that sexualizes, exploits, or endangers minors. We report confirmed CSAM to the National Center for Missing & Exploited Children (NCMEC) as required by law.
• Harassment or hate speech. Targeting individuals or groups with abuse, slurs, or threats based on race, ethnicity, religion, gender identity, sexual orientation, disability, or other protected characteristics.
• Spam. Bulk unsolicited content; using Sprigged as a distribution channel for unrelated promotional material; auto-generated noise designed to drown out real activity.
• Impersonation. Pretending to be a person or organization you are not, in a way intended to deceive others.
• Intellectual property infringement. Content that infringes copyright, trademark, or other intellectual property rights. Submit DMCA takedown notices via [email protected]; include the patch name, the infringed work, and a good-faith statement of authority.
• Illegal content. Content that violates applicable law in the United States or Canada (the jurisdictions Sprigged currently serves — see the Privacy Policy for the full jurisdictional scope).

Prohibited use

Beyond content, you may not use Sprigged to:

• Coordinate real-world targeting, harassment, or harm of any individual or group.
• Bypass technical or access controls on Sprigged itself (the per-patch isolation, the identity model, the rate-limits, the maintainer permissions) or on third-party systems you reach via a Sprigged-hosted app.
• Build systems that automate access to other users' patches without their permission, or that scrape Sprigged's services beyond what your own membership grants you.
• Use Sprigged to send marketing or recruiting messages to patch members who joined for an unrelated reason — patches are for the thing the patch is about.

LLM-authored content

Sprigged includes an LLM-assisted authoring loop ("Build with AI"). When you use it to draft a spec, the resulting patch is yours — and so is the responsibility for what's inside it.

You are responsible for what you author and share, even if Claude drafted it. The same prohibitions in this policy apply to LLM-assisted output. If you ship a patch that contains something Claude generated and that something violates this policy, the violation is on you, not the model.

Takedown rights

We may archive or permanently delete patches that violate this policy. Decisions are made case-by-case using the criteria in our internal takedown-response runbook. Most violations result in a soft takedown (the patch is archived and members can no longer access it but the data is preserved); egregious or illegal violations — CSAM, repeat egregious abuse, clear illegal content — may be hard-deleted with no recovery path.

To appeal an action against a patch you maintain, write to [email protected] with the patch name and a description of why you believe the action was incorrect. We aim to respond within 7 days.

How to report a patch

For urgent reports, use the Report this patch link inside any patch you're a member of (Patch settings → Help → Report this patch). Reports are reviewed within 7 days. Reporters are anonymous to the patch's maintainer — we do not share your identity with the people you report.

Changes to this policy

When we make material changes to this policy, we'll bump the version date at the top and surface the change inside the app before it takes effect. Cosmetic edits and clarifications won't trigger an in-app notice.

Contact

Questions or appeals about this policy go to [email protected]. We read every message.