ScrumDo User Agreement
Version: 2.0
Effective Date: January 1, 2019
Last Restated: July 11, 2026
PLEASE READ THIS USER AGREEMENT CAREFULLY. IT CONTAINS IMPORTANT TERMS ABOUT ACCOUNT ACCESS, ROLES, CUSTOMER CONTRIBUTIONS, AND CONNECTED SERVICES.
This ScrumDo User Agreement (“User Agreement” or “Agreement”) is a legally binding agreement between you (“you” or “User”) and ScrumDo, LLC (“ScrumDo,” “we,” “us,” or “our”).
This Agreement forms part of the ScrumDo Terms of Use (“Terms”). Capitalized terms not defined here have the meanings given in the Terms. If there is a conflict, the order of precedence in the Terms governs.
1. Registration and Acceptance
1.1 Account Required. You must register for an Account to use member-only portions of the Services. Some customer-contribution routes may accept a submission without creating a registered Account.
1.2 Acceptance. You accept this Agreement by creating an Account, accessing or using the Services, or clicking “accept,” “agree,” or similar when presented with this Agreement.
1.3 Accurate Information. You must provide accurate registration information, keep it current, and not impersonate another person or misrepresent your authority.
1.4 Age. You must meet the age requirement in the Terms. A contribution route does not waive that requirement.
2. Account Ownership and Roles
2.1 Personal Plan. A Personal Plan is limited to one registered member. Customer Contributors do not become members solely by submitting Content through an authorized contribution route.
2.2 Organization Accounts. Team, Business, and Enterprise Accounts are administered by an Account Owner. The Account Owner is responsible for role assignments, access, billing, connected services, and the organization’s use of the Services.
2.3 Role Boundaries. Depending on the plan and configuration, roles may include:
- Crew: collaborate on work within assigned Rooms and Boards;
- Manager: configure and manage authorized team-level work and planning;
- Business Manager: manage authorized portfolio, economic, reporting, or organization-level surfaces;
- Customer Contributor: submit customer evidence or create and track customer-visible work where that access is enabled; and
- Account Owner or Admin: manage billing, security, roles, and organization-level settings.
No role implies another. A person receives only the permissions expressly assigned through the Account.
2.4 External Advisors and Contractors. An Account Owner may grant scoped access to a coach, consultant, agency, contractor, or other advisor where the plan permits. The Account Owner is responsible for authorization, confidentiality, scope, duration, and removal of that access.
2.5 Access Review. Account Owners must promptly remove or change access when a person no longer needs it. ScrumDo may restrict access that appears unauthorized, unsafe, or inconsistent with the applicable plan or Order Form.
3. Customer Stories and Contribution Routes
3.1 Different Routes Have Different Effects. ScrumDo may support configured routes that:
- collect a story or response without immediately creating a card;
- create a card through an intake flow; or
- allow a registered Customer Contributor to create and track customer-visible work.
The Account Owner is responsible for explaining the route, identity mode, visibility, intended use, and any follow-up that applies before collection.
3.2 Anonymous, Pseudonymous, and Identified Use. A route is anonymous only when the Account Owner and ScrumDo cannot reasonably connect the submission to an individual through the route, Account, link, metadata, or other available information. Pseudonymous and confidential are not the same as anonymous. Account Owners must describe the selected identity mode accurately.
3.3 Customer Access. Customer Contributors may access only the Content and work made available by their assigned role and configuration. A contribution does not grant access to internal Boards, other contributors’ Content, account administration, or unrelated work.
3.4 Account Owner Duties. The Account Owner is responsible for required notices, consent, lawful basis, data minimization, retention, access, response handling, and appropriate use of customer and employee Content. Sensitive or regulated collection may require an Enterprise agreement and security or privacy review.
3.5 No Implied Findings. A story, response, pattern, score, or dashboard does not by itself establish representativeness, causation, employee performance, psychological safety, customer satisfaction, or legal compliance.
3.6 Intake Collectors, CAPTCHA, and Metering. Managers may copy and distribute shareable URLs for intake collectors. Public-facing intake collector endpoints are subject to automated CAPTCHA challenges, bot protection, and daily rate metering (standard limit of up to 50 responses per day per collector). Circumvention of intake safeguards, abusive automated scripting, or use of intake routes for spam or unauthorized harvesting is strictly prohibited and subject to immediate deactivation.
4. Agents, Context, and Connected Services
4.1 Human Accountability. Agents may draft, recommend, inspect, implement, or verify work within configured limits. Authorized Users remain responsible for specifications they accept, approvals they grant, provider access they configure, and outputs they use.
4.2 Context Boundaries. The application may carry approved work context between governed surfaces. Users must not give an agent or connected service access to Content, repositories, credentials, or destinations they are not authorized to use.
4.3 Own Providers and Keys. When you connect your own agent, AI provider, repository, notification destination, or other service, you are responsible for that provider’s terms, availability, security, processing locations, and charges. ScrumDo does not resell your provider’s AI usage unless checkout or an Order Form expressly says otherwise.
4.4 Human Review. Automated and AI-assisted outputs may be inaccurate or incomplete. Required approval, verification, proof, and acceptance steps must not be bypassed.
5. Credential and Account Security
5.1 No Credential Sharing. Each set of member credentials is personal to one individual and may not be shared or used concurrently by multiple people.
5.2 Safeguards. You are responsible for safeguarding passwords, access tokens, API keys, recovery methods, and devices used to access the Services.
5.3 Unauthorized Access. Notify ScrumDo promptly if you suspect unauthorized access or misuse.
6. Single-Entity Use
6.1 Unless an Order Form or the applicable plan expressly permits otherwise, an Organization Account is licensed to the entity that purchased it and does not automatically extend to subsidiaries, affiliates, joint ventures, or external business partners.
6.2 You may not sublicense, transfer, or share licensed member access across entities without ScrumDo’s written authorization.
7. Third-Party Services
You may enable third-party services and integrations. ScrumDo is not responsible for their terms, availability, security, outputs, or performance. Connected providers may receive Content and metadata as described in the Privacy Policy, DPA, Subprocessors List, and applicable feature notice.
8. Data Protection Requests
For Content controlled by an Organization Account, the Account Owner typically determines why and how Personal Information is processed. Contributors and Authorized Users should direct access, correction, deletion, or similar requests to the Account Owner where appropriate. ScrumDo will assist as required by the DPA and applicable law.
9. Paid Services
Paid Services are governed by the checkout disclosure, Subscription Terms, applicable Order Form, and Terms. Downgrades may reduce features, member capacity, customer-account capacity, agent actions, retention, or other allowances. Your AI and connected-service providers may charge you separately.
10. Acceptable Use
You must comply with the Acceptable Use restrictions in the Terms. You may not use customer evidence, employee Content, intake collectors, agents, notifications, connected services, or exports to evade consent, re-identify protected contributors, surveil individuals, host or process sexually explicit or adult entertainment material, engage in unethical or deceptive practices, make prohibited automated decisions, or access systems without authorization. ScrumDo is the sole arbiter of what constitutes abuse or prohibited conduct.
11. Electronic Notices
11.1 You consent to receive contractual and operational communications electronically, including by email and in-product notice.
11.2 Operational notifications may also be delivered through destinations configured by you or the Account Owner. A third-party notification does not replace the governed in-product record or a required acknowledgement.
11.3 You are responsible for keeping your email address and notification destinations current.
12. Suspension and Termination
ScrumDo may immediately suspend or terminate access, throttle usage, or disable intake routes as described in the Terms if abuse, prohibited conduct, or violations occur, as determined in ScrumDo's sole discretion. Upon termination, your right to use the Services ends. Export and retention rights are governed by the Terms, DPA, and any applicable Order Form.
13. Incorporated Protections
The disclaimers, limitation of liability, indemnification, dispute-resolution, export-control, and sanctions provisions in the Terms apply to this Agreement and are incorporated by reference.
14. Contact
Questions: legal@scrumdo.com