1. Information we process
Depending on how you use ScriptureGuard, we may process account and authentication information such as email address and login credentials; organization and membership information; submitted ministry content; doctrine-profile settings; verification findings; review decisions; approval and release records; technical and security information; and messages you send to support.
ScriptureGuard is designed so church workspaces are organization-scoped. Content, doctrine snapshots, findings, reviews, and release records are associated with the applicable workspace and access controls.
2. Why we process information
We use information to provide and secure the service, authenticate users, maintain organization boundaries, preserve exact verification and release records, support users, troubleshoot problems, improve reliability, and comply with applicable legal obligations.
3. AI-assisted features
Some signed-in features can use an external AI provider when configured. The ScriptureGuard Guide is limited to product-use questions. Review Assist may send a bounded subset of an existing finding record to generate reviewer-support material. These features are designed to assist workflow and do not replace human theological judgment or final approval.
Do not place confidential pastoral counseling information, highly sensitive personal information, or material unrelated to the verification workflow into tutorial or support prompts.
4. Service providers
ScriptureGuard currently relies on service providers for hosting and network delivery, authentication and database services, and optional AI-assisted features. These providers process information only as needed to provide their respective services and are subject to their own contractual and privacy obligations.
5. Cookies and local storage
ScriptureGuard uses essential authentication and security technologies required to keep users signed in, protect sessions, and operate the service. We do not describe an essential session cookie as optional because the authenticated workspace cannot function without it.
6. Data retention
Verification, review, approval, and release records may be retained as part of the product's audit and evidence model. Other information is retained for as long as reasonably necessary for service operation, security, support, contractual obligations, and applicable law. Deletion requests may be limited where retention is required to preserve security, legal, contractual, or immutable audit records.
7. Security
We use technical and organizational controls intended to protect account and workspace information, including authenticated access, organization-scoped data access, role-based authority, and protected server-side command paths. No internet service can guarantee absolute security.
8. Your choices and requests
For privacy questions, access or correction requests, account questions, or other data-related requests, contact support@scriptureguard.com. We may need to verify your identity and authority before acting on a request involving a church workspace.
9. Children
ScriptureGuard is a professional ministry workflow product and is not directed to children for independent account use. Organizations using ScriptureGuard remain responsible for their own policies and legal obligations regarding children's information and ministry content.
10. Changes
We may update this policy as ScriptureGuard, its providers, or legal requirements change. The effective date shown on this page identifies the current version.