A shared understanding for beta testing.

1. Your authority and account

Accounts are for adult representatives authorized to work with their church’s records. Provide accurate account information, use your own password, and protect your recovery code. Do not share an account. Creating a workspace does not grant authority to act for that church; you must already have permission.

The first account has temporary Master Administrator access within its church. Church account managers are responsible for invitations, starting roles, reviewing continued access, and following local approval requirements. App permissions do not authorize conduct prohibited by church policy or applicable law.

2. Beta use and parallel bookkeeping

You may use fictional records or real accounting and giving records your church has authorized you to process. During beta testing, you must maintain your current official books separately, record the same activity there, and reconcile StewardLift against them and original bank statements. Do not use this beta as your only financial record or only backup.

Parallel bookkeeping means maintaining a separate official set of books for comparison. Double-entry accounting is the debit-and-credit method inside the app; it does not replace this beta safeguard. Review totals, imported rows, classifications, reports, and corrections before relying on them.

3. Records you may provide

Only add information you are authorized to use, with any notices, permissions, or legal basis your church requires. Limit donor and household information to what is needed for the available workflows. Protect giving records and exports as private church information.

Do not upload Social Security numbers, full payment-card or bank account numbers, bank login credentials, payroll tax records, medical information, or confidential pastoral-care records. Redact these details from statements, checks, and attachments. Do not use the beta to initiate payments, move actual money, or process payroll.

4. Acceptable use

Do not access another church’s records, bypass permissions, impersonate someone, distribute recovery secrets, upload malicious files, interfere with service, or use the application unlawfully. Report suspected unauthorized access to your church’s account manager and Wisener Ventures LLC. Do not include passwords, recovery codes, or sensitive documents in the initial report.

5. Your records and their processing

Your church retains its rights in the records it provides. You permit Wisener Ventures LLC and hosting providers to store and process those records to operate, secure, maintain, and support the beta as described in the privacy policy. This permission does not transfer ownership of your records.

Invited people access information according to their roles and approved permissions. Authorized service maintainers may need operational access for faults, support, or security investigations. Consider these access paths before adding real records.

6. Verification, recovery, and communications

Automatic email delivery is not connected. The beta supports saved recovery codes and administrator-assisted verification links. Only a Master Administrator can issue a password-recovery link, after checking the recipient’s identity and authority through a separate trusted method. An administrator’s identity check or generating a link alone does not prove email-inbox ownership. Email verification is completed when the recipient confirms the email-bound link delivered to their mailbox. Keep codes and links private.

Do not assume a help request, a new account, or an in-app notice sends an email. Questions can be addressed to the contact above; a response time is not guaranteed.

7. Availability, changes, and exports

This is an evolving beta. Features may change, be interrupted, or be withdrawn. It has no guaranteed uptime, support response, storage duration, or recovery time. Maintain independent official records and export copies you are authorized to hold.

Authorized users can export reports and workspace records with document content. Private operator-managed backups are scheduled; independent off-provider custody and production restoration remain incomplete. Self-service workspace deletion and in-app restoration are not available. Disabling an account does not erase accounting or audit history. Contact Wisener Ventures LLC about workspace closure or deletion; handling depends on identity checks and applicable retention duties.

8. Fees and future releases

The current beta does not request payment details or automatically enroll you in a paid plan. Production pricing has not been set. A paid service would require separate pricing information and affirmative agreement; creating this beta account does not authorize charges.

9. Professional review and beta limitations

To the extent permitted by applicable law, the beta is provided as available, without a promise that it will be uninterrupted, error-free, secure against every threat, or suitable for every church. Independent security validation and production operational readiness are incomplete.

StewardLift provides software, not professional accounting, legal, tax, payroll, investment, or audit advice. Your church remains responsible for its decisions, official filings, donor acknowledgments, records, and controls. Read the specific beta limitations. Nothing in these terms excludes rights, liability, or obligations that applicable law does not allow to be excluded.

10. Ending access

You can stop using the beta and ask your church’s account manager to disable your account. An authorized manager may disable access under church policy. Wisener Ventures LLC may restrict or suspend service to address misuse, security concerns, legal duties, or discontinuation of the beta. Keep separate official books and exports so an interruption does not leave your church without its records.

11. Policy versions

This version is 2026-10-22-beta-5, effective October 22, 2026. Revisions carry an updated effective date and version. Account acceptance history identifies the version presented during signup or invitation acceptance. A later policy does not silently rewrite earlier acceptance records.