Skip to main content

Terms of Service

Version v0.4.1-2026-11-02 · effective November 2, 2026

Doersteps Terms of Service

v0.4.1, effective 2026-11-02

1. Who We Are

Doersteps ("the Platform," "we," "us") is a ministry software platform operated by Doersteps. Doersteps provides tools for discipleship pathways, leadership training, small group management, and ministry communication.

2. Accounts and Eligibility

2.1. During the founding pilot you must be at least 18 years old to create an account. Support for accounts held by people aged 13 to 17, with the safeguards described in 2.2, is built but switched off at every organization; until Doersteps turns it on for an organization, that organization may record a younger participant only as a non-account record under 2.5. Where minor accounts are turned on, organizations may raise (but not lower) the minimum age for their own members.

2.2. Where minor accounts are turned on for an organization, a person aged 13 to 15 waits for a parent or guardian's recorded consent before the account opens, and a person aged 16 or 17 names a parent or guardian, who is confirmed by the organization and told, before the account opens (an organization may require consent for 16 and 17 year olds too). A parent or guardian is confirmed by the organization and accepts the link in their own session; a young person cannot create their own guardian.

2.3. You agree to provide accurate information and to keep your login credentials secure. Two-factor authentication is available for every account. Your organization may require it for accounts at leader level and above; during the founding pilot it is not enforced.

2.4. Each account belongs to one person. Sharing accounts is not permitted.

2.5. Records about people who do not hold accounts. Organizations may keep records about people who have no Doersteps account, including children under 13 tracked on a roster by their ministry and people who have not yet signed up. These people are not users and do not agree to these terms; the organization that records them is responsible for having a lawful basis to do so and for honoring their rights. We provide a route for such a person (or their parent or guardian) to make a data request to us directly.

2.6. Data-access covenants. People whose role lets them see other people's records may be required to sign a versioned data-handling covenant before that access is granted. Your organization, or we, may require re-signature when the covenant is updated. Signatures are recorded with the version signed and the time of signature. Declining, or letting a required signature lapse, removes the elevated access, not the account.

3. Organizations and Roles

3.1. Doersteps accounts exist within organizations (churches, campus ministries, and similar groups). Your organization's administrators control your role, permissions, and what you can see and do within their organization.

3.2. Your organization is responsible for how it configures Doersteps, including its groups and group threads, its safeguarding settings, which details it asks about a person, and the curriculum it offers its members.

3.3. Organization administrators may remove members, change roles, and in serious cases fully remove a person's access and contact surface within their organization. These actions are logged.

4. Transparency About Visibility (Read This Section)

Doersteps is ministry oversight software. It is built so that spiritual care can be supervised. By using Doersteps you acknowledge:

4.1. Group threads are visible to your organization's staff. Where Doersteps has turned group threads on for your organization, a group's thread is read by the group's members and by the organization's staff who read its roster. The thread says so on the screen where you write.

4.2. One-to-one threads are private from ordinary view. The thread between you and your leader is read by the two of you and, where you are recorded as under 18, by a parent or guardian recorded for you. Organization administrators hold an audited emergency access capability ("break-glass"): one administrator asks, a second administrator who is not party to the thread approves, a written reason is required, the access lasts for a set window of no more than 72 hours, every read is written to the organization's audit log, and both people in the thread are told.

4.3. Pathway submissions and related content are visible to your leader, to whoever signs off your steps, and to your organization's staff. Where your course belongs to a group, that group's leaders see them too. Where you are recorded as under 18 at an organization where minor accounts are turned on, a parent or guardian recorded for you sees them as well. The Platform tells you who can see what you write before you write it.

4.4. Leader notes about members flow upward to those responsible for leader development. Members do not see a leader's private notes about them. A note a leader writes on your step when signing it off or sending it back is shown to you, and you can reply to it.

4.5. Platform-level access. Doersteps platform staff can technically access tenant data for support, safety, and legal compliance purposes. Every read of an organization's records made through Doersteps' own console is written to that organization's own audit log, which the people your organization has given the audit log permission can inspect at any time. Two kinds of read are not written there: a help message a person sent to Doersteps and chose not to share with their organization, and a safeguarding referral routed to Doersteps because every safeguarding contact at the organization was conflicted. We operate the database, and a read made with our database credentials rather than through the console is not written to your log.

4.6. Doersteps threads are not end-to-end encrypted, by design, because organizational safeguarding requires readability. Do not use Doersteps for communications you need to keep from your organization's leadership.

4.7. Engagement analytics, including per-person video viewing, are not yet offered. Video engagement analytics are not part of the Platform today. If they are offered, this document will be updated first to say what is recorded, who can see it, and how your organization controls it.

4.8. Practice records. Where your organization uses practice thresholds, the amounts you log are visible to you and to your assigned leader. Staff see only whether a threshold has been met, never the underlying quantities, and these amounts are never ranked or compared between people.

5. Content You Create

5.1. You retain ownership of content you create on Doersteps (curriculum, submissions, messages, files).

5.2. You grant Doersteps a limited license to host, display, transmit, and back up your content solely to operate the Platform.

5.3. Curriculum sharing. Where Doersteps has turned the library on for your organization, an author at your organization may share a published course with a chosen part of your organization's wider network or with the public catalog. Sharing takes a snapshot of the published student material only; drafts, leader material, people's names and people's records are never included. Other permitted organizations may then view, copy ("fork"), and adapt that snapshot within the Platform, with attribution to the publishing organization preserved, under the license the publisher chose. Withdrawn content stops appearing in catalogs, while existing forks continue to function.

5.4. What survives your departure, and what does not. Section 10.2 describes what happens to an organization's data after it closes. Where another organization has forked your curriculum:

  • The fork's text, structure, and settings are copies held by the forking organization and continue to work.
  • Uploaded files and attachments are not copied into a fork. A fork carries embedded links only. Media your organization uploaded stays in your organization's storage and is subject to Section 10.2.

A forking organization is shown where its copy came from, whether a newer version of the original exists, and whether the original is no longer shared or has been withheld.

5.5. Rights affirmation. By sharing a course beyond your organization you affirm that you own or have rights to all included material, including video, audio, images, and text. Your affirmation, and the version of this wording you affirmed, is recorded with the share. You are solely responsible for rights violations in content you share.

5.6. Doersteps does not endorse user-published content. Attribution of source is displayed so organizations can evaluate content for themselves. Doersteps does not referee theology.

5.7. We may withhold content that violates law, these terms, or platform safety policies. A withheld piece of content is replaced by a placeholder wherever it appeared, and the rest of the course stays open; nothing is deleted. Anyone who can read a piece of content can report it to us and to the organization's administrators.

6. Acceptable Use

You agree not to: - Break the law or help anyone else do so - Harass, abuse, exploit, or endanger any person, especially minors - Upload malicious code or attempt to breach Platform security - Misrepresent your identity or organizational affiliation, including falsely claiming affiliation to obtain discounts - Scrape, resell, or bulk-export data belonging to people who have not authorized you - Circumvent safeguarding features, moderation states, or access controls

6.1. Real human voices only. Audio and video you upload must be recorded by the actual people speaking. Do not upload synthetic, cloned, or AI-generated voices, and do not use a synthetic voice to represent a teacher, leader, or any other person. Formation happens through real people; a ministry teaching through a manufactured voice is not what this Platform is for. This applies to curriculum, submissions, and any other uploaded media.

Accessibility tooling that does not impersonate a person (captions, transcripts, screen readers, and text-to-speech a reader turns on for themselves) is permitted and encouraged.

Violations may result in suspension or termination. Where minors' safety is involved, we may act immediately and report to authorities as required by law.

7. Safeguarding and Mandatory Reporting

7.1. Doersteps provides safeguarding tools (escalation flags, oversight visibility, leader requirement checklists, parent and guardian links). Organizations are responsible for configuring and using them appropriately for their context.

7.2. Doersteps is not a crisis service. The Platform's escalation features route concerns to your organization's designated people, not to Doersteps staff or emergency services.

7.3. Organization leaders may be mandatory reporters under their local law. Nothing in these terms limits any legal reporting obligation.

8. Billing

8.1. Paid plans are not yet offered. During the founding pilot the Platform is provided without charge, and no payment is taken. When paid plans are offered, they will be priced by seats (active accounts), pricing will be published before any organization is charged, and this section will be updated.

8.2. When paid plans are offered, affiliation discounts (including the Chi Alpha discount) will apply only after affiliation is verified through our approval process, and may be revoked if affiliation ends.

8.3. Founding pricing: organizations that take part in the founding pilot will be offered early access pricing when paid plans begin, and will keep that pricing for as long as their subscription remains continuously active.

8.4. Prepaid add-on credits are not yet offered.

8.5. When paid plans are offered, you will be able to upgrade, downgrade, or cancel at any time, effective at the next billing cycle.

9. SMS and Communications

9.1. Text messaging is not yet offered. The Platform does not send text messages today. If it is offered, you will be asked to opt in first, and this section will be updated with how to opt out.

9.2. Transactional email (login links and required notices) is part of operating your account and cannot be fully disabled while your account is active. You can switch other notification email off in your settings.

10. Data Ownership and Export

10.1. Your organization's data belongs to your organization. You can download a copy of your own record at any time, from your account, without asking anyone. Your organization's administrators can download the organization's data; that export requires the administrator's permissions, a written reason, and is logged.

10.2. Upon an organization's closure, its data enters a 90-day frozen recovery period during which you may export or reactivate. After that period the data becomes eligible for deletion. Deletion is a step Doersteps takes by hand after review; it is not automatic, and it is subject to legal retention requirements, the personal-record provision in 10.3, the legal-hold provision in 10.6, and the audit log provisions in 10.5.

10.3. What an individual keeps when an organization closes. A person's own formation history does not disappear because the organization that recorded it shut down. When an organization closes, each person who took part keeps a permanent frozen snapshot of their own record (what they completed, when, and what was attested) which they can continue to view and share.

The snapshot is the person's copy, not the closed organization's records: it does not include leader notes about them, other people's data, or the organization's operational content. Media files are not included in the snapshot; it is a record of formation, not an archive of video.

10.4. Individual users may close their accounts. Closing an account suspends your access at once and ends your pairings. Formation records (such as pathway submissions and attestations) are part of the issuing organization's records; no sooner than 90 days after your request, Doersteps anonymizes your personal identifiers as required by applicable law rather than deleting organizational history. The anonymization is a step Doersteps runs by hand; the Platform tells us when a request is due.

Honest limit on anonymization: removing a name from a database row does not anonymize a voice recording, a video of a person, a photograph, or free-written text in which a person describes their own identifiable circumstances. Where you have submitted such content, we delete it rather than claim to anonymize it, unless a legal-hold obligation under 10.6 requires its retention. If deleting it would destroy an organization's record of a formation event, the record of the event (what was completed and attested) is retained without the media.

10.5. Audit logs. Audit logs are append-only and tamper-evident. The database rejects updates and deletions to audit records, and this restriction applies to our own administrative database credentials, not only to organization users.

We state this precisely rather than promising the impossible: we operate the database, so we could in principle alter its underlying storage. What we commit to is that (a) no ordinary path, including our own support tooling, can modify an audit record, (b) every read of your organization's records made through our console is itself written to the organization's log, with the two exceptions in 4.5, and (c) tampering would be evident rather than silent. Audit logs survive within the retention window even after tenant deletion, for integrity and legal purposes.

10.6. Legal holds. If we receive a legal obligation to preserve specific data (litigation, subpoena, regulatory demand, or a credible safeguarding investigation), we will suspend deletion of the affected data for as long as that obligation lasts. A legal hold overrides the deletion timelines in 10.2, 10.3, and 10.4 for the specific data covered. Where we are legally permitted to tell you, we will.

11. Service Availability, Security, and Incidents

11.1. We aim for high availability but do not guarantee uninterrupted service. Maintenance windows and outages may occur.

11.2. We perform automated daily backups, retained on a rolling seven-day schedule. Point-in-time recovery is not yet enabled and will be enabled before any organization outside the founding pilot is onboarded. You are encouraged to maintain your own exports of critical data.

11.3. Breach notification. If we determine that a security incident has compromised personal data belonging to your organization or its members, we will notify the organization's administrators without undue delay and no later than 72 hours after we determine a breach affecting your data has occurred. Notice will describe what we know, what data was involved, what we are doing, and what you should do. Where the law requires you to notify affected individuals, we will give you the information you need to do so.

12. Termination

12.1. You may stop using Doersteps at any time. Organizations may close their account at any time.

12.2. We may suspend or terminate accounts or organizations for material violation of these terms, non-payment, legal requirement, or serious safety risk. Where practical, we will provide notice and export opportunity consistent with Section 10.

13. Disclaimers and Limitation of Liability

13.1. THE PLATFORM IS PROVIDED "AS IS" WITHOUT WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED.

13.2. Doersteps IS A SOFTWARE TOOL. IT DOES NOT PROVIDE PASTORAL CARE, COUNSELING, OR EMERGENCY SERVICES, AND IS NOT RESPONSIBLE FOR THE CONDUCT OF ORGANIZATIONS OR USERS.

13.3. TO THE MAXIMUM EXTENT PERMITTED BY LAW, OUR TOTAL LIABILITY FOR ANY CLAIM IS LIMITED TO THE GREATER OF (A) THE AMOUNTS YOU PAID US IN THE TWELVE MONTHS BEFORE THE CLAIM AROSE, OR (B) ONE HUNDRED U.S. DOLLARS.

13.4. Some jurisdictions do not allow certain limitations; in those places, these limits apply to the fullest extent permitted.

14. Changes to These Terms

We may update these terms. Material changes will be announced in-app or by email with reasonable notice. When a new version takes effect you will be asked to read it and agree to it before you continue using Doersteps. Where a new version only corrects how this document describes what the Platform already does, we may carry your earlier agreement forward instead of asking again; your agreement record then shows that it was carried, and from which version.

15. Assignment and Change of Control

15.1. You may not transfer your rights under these terms without our written consent.

15.2. We may assign these terms and transfer the data they cover to a successor entity in connection with a reorganization, incorporation, merger, acquisition, or sale of assets. A successor is bound by these terms, including the privacy commitments and the visibility disclosures in Section 4, until they are changed under Section 14.

15.3. We will give organization administrators notice before personal data is transferred to a successor entity.

16. Governing Law

These terms are governed by the laws of the State of Texas, USA, without regard to conflict of law principles. Any dispute will be brought in the state courts located in Caldwell County, Texas, or the federal courts of the Western District of Texas.

17. Contact

Questions about these terms: [email protected]

Terms of Service · Privacy Policy