Church Abandoned Parent Notice and Consent Version CA-PARENT-CONSENT-2026-10-17-v4 Church Abandoned operates this app for church participation. We need your permission and verification that you are the parent or legal guardian before creating an account for a child under 13. You may decline; we will not activate the child account without verified consent. You reached this notice by signing into your own account and linking the child's pairing request. Before linking, that request uses an opaque installation identifier, request and recovery information, status and timestamps. It does not retain the child's name, birthday or email. Your account identifies you as the parent requesting verification. Signing or scanning the QR code alone does not activate an account. Read our full privacy notice: https://solideosoftware.com/church-abandoned/privacy/ Referenced privacy version: CA-PRIVACY-2026-10-17-v3 Operator and parent-rights contact: Church Abandoned, Mountain View Elementary School, 145 Co Rd 627, Etowah, TN 37331; telephone (423) 404-1772; email ChurchAbandoned@ChurchAbdanoned.org. Church Administration handles authenticated requests concerning the child's records. Soli Deo Software handles ordinary support and privacy inquiries at support@solideosoftware.com. Do not email passwords, verification codes or consent records to SDS. Information and use After verification, you enter the child's first name, last name, birthday and a separate username and password. We use those details, an account identifier, parent/family links, account status and security/session information to provide sign-in, family management, age-based access and recovery. The child's account initially has no email address and is not recorded as email-verified. The password is protected through a private salted verifier, not stored as readable password text. Church participation and family links may reveal religious affiliation. Available church features can process group-membership requests, event registrations, profile changes and family relationships. Chat participation can involve message text, sender identity, room membership, timestamps, read status and attachments received in permitted rooms. Messages and files can be seen by the applicable participants and authorized church dashboard users; recipients can save their own copies. Sending attachments requires additional permissions and is not granted merely by this consent. Permissions and room membership determine access; this is not a promise of a child-only or no-chat account. Device notification tokens and preferences support notifications. A manually submitted problem report includes the user's description and limited app/device/permission/error information for troubleshooting. In the upcoming mobile update, failed chat requests also automatically generate sanitized technical reports for troubleshooting, at most once per user per hour. These automatic reports exclude message and file contents and raw exception text, use the same problem-report service and its existing limits, and are separate from moderation decision metadata. Developer users can review manual and automatic reports. Automatic reporting requires the new mobile build and is not yet released. Do not put passwords, consent records or other people's private information in reports. Providers and disclosure choices Google Firebase services handle authentication, database and backend processing; private Google Cloud Storage holds files. Apple APNs and Google FCM deliver device notifications. Resend handles recipient addresses and delivery metadata for generic administrative alerts; those alerts do not contain consent forms or report/chat bodies. Authorized church reviewers and technical administrators can access the information needed for their roles. Consent forms stay in the restricted church system and are not emailed to SDS. The app also contains YouTube media and external giving, map and social links. Opening an external service may send device/network information and anything entered there to that service. Scripture passage requests go through the backend to Crossway ESV without the child's identity in the passage query. The church uses automated chat safety screening hosted privately on Google Cloud Run. It checks submitted or edited text and captions, together with up to six recent messages from the same room that the sender can access. It does not inspect binary attachments, and chat moderation does not send this content to OpenAI or a hosted Qwen or Hugging Face inference service. Your consent to this notice includes this safety-processing purpose; it does not authorize undisclosed new uses or replace separate choices for optional external services. Screening can make mistakes. Blocked messages are not delivered and create restricted incident records for authorized church administrators to review. Five distinct blocked messages within 30 minutes restrict chat until an authorized administrator lifts the restriction. You can request review through the app. Model decisions are automated judgments, not findings that a person has confirmed abuse. Checking failures preserve the draft and do not count as violations. The model uses in-memory prefix caching; saved whole-prompt and response caches are disabled. Requests are not written to the model service’s disk or application logs, but request-derived memory is not promised to be erased immediately. Restricted moderation incidents can retain blocked text and decision information under the separate 90-day incident schedule. After incident text and details expire, minimal room/restriction associations can remain so an authorized administrator can review and lift an existing restriction; this does not extend retention of the expired text. Debugging metadata has a 30-day availability period and does not contain copied message or conversation bodies. Authorized viewing of original text/context follows the source records’ access, retention and edit checks. Google infrastructure metadata follows separate provider retention rules. You may consent to collection and use without consenting to non-integral third-party disclosures. A disclosure that is not integral to the requested service requires separate parental consent before it occurs. Merely opening a feature, or signing this general form, is not that separate consent. We must provide the applicable choice or keep that disclosure unavailable to the child. Changes requiring new consent cannot be authorized by silently changing this signed notice. Optional reuse of reviewed messages to improve chat safety rules is limited to adults who separately opt in. Your child's messages and identifiable information about children are excluded from that optional process; ordinary safety screening and authorized incident review continue as described in this notice. This notice does not offer or grant a parent choice for improvement use. Verifying your permission Enter your required phone number in the separate contact field. A permission-authorized church leader will speak with you in person or through independently established contact to confirm your identity, parental authority and agreement to this notice. Your entered phone number by itself is not proof. The church records the reviewer, date, method, decision and confirmations; it does not require a recording or identity-document copy under this process. If authority cannot be established, the request is not approved. The phone is separate from the signed notice and is removed from the verification contact record at the decision. It is not a marketing subscription or ongoing recovery credential. The exact signed notice, signature and version remain unchanged. Your controls and requests After account creation, use Settings/account → Child accounts to reset the child's password, suspend or resume access, withdraw consent and remove the account, or delete the child account. These actions require you to sign in again. For an unfinished request, use Withdraw request. Suspension stops access but is not withdrawal. Withdrawal or deletion stops access and starts deletion of the child's account, profile, messages and uploaded files; it cannot be undone by simply resuming access. You may ask Church Administration to review the child's information, obtain a copy of the signed notice, stop further collection/use or delete the child's information. Use the church telephone, email or mailing contact above; the church must verify your authority before securely providing records. Do not send those records to SDS. To view or save your retained signed consent record, sign in to the account that originally signed it, then open Settings → Your account → My signed consent forms → choose a record → Save a copy of my signed record. The list includes only your own retained, unexpired forms. Your account must remain active and email-verified. A copy you save or share outside the app is not removed by the app’s later cleanup. Retention An unlinked request expires 24 hours after its creation. A parent-linked unfinished request, including approval not used to create an account, expires 30 days after its first linking. QR replacement, recovery and activity do not extend those deadlines. Expired requests lose access and enter cleanup. While the under-13 account relies on consent, the church keeps the exact notice/signature and necessary verification evidence. Withdrawal, account deletion or the actual 13th birthday closes that consent purpose. Only minimal consent/verification evidence is then kept, for up to 90 days from the original closure, to reconcile verification and closure requests; valid deletion or loss of necessity can remove it earlier. This does not permit retaining the child's profile, messages or files for those 90 days. Account/family/security records remain only for their ongoing account purpose and applicable deletion process. The separate minimal parent-management link does not extend signed-consent retention. Active chat content/files have a 90-day-from-creation rule; still-unexpired content in an archived room can instead remain for 90 days from archival. Abuse-report evidence has its separate 90-day-from-report schedule. Manual and automatic problem reports have a 30-day availability cutoff and scheduled cleanup. Manually saved pending report attempts expire on access after seven days. In the upcoming mobile update, automatic chat-error reports use a separate secure on-device retry queue with a 24-hour delivery window. Delivery is attempted immediately and retried after a later successful chat request; expired queued reports are discarded when the queue is next checked, rather than guaranteed to be physically erased at exactly 24 hours. The full privacy notice describes shared-record and provider metadata limits. Access ends at the applicable cutoff; physical cleanup runs in batches and can lag during outages or backlogs. Database prior versions have a one-hour window. Inventoried cloud-log buckets use 30-day and 400-day schedules; these are separate provider/administrative records, not an extension of consent-evidence retention. We cannot erase copies already saved by recipients. No universal immediate-erasure guarantee is made. At age 13 The actual 13th birthday ends reliance on this under-13 consent. Parent password-reset, suspension and deletion controls continue until the account holder is also verified by the authentication service as owning their recovery email. Once both conditions hold, parent controls end even if password setup is unfinished. If needed, the account holder must use password recovery through that verified email before username/email-and-password sign-in. The old private sign-in method is retired. Removing the email later does not restore parent controls. These transitions do not reactivate suspended, withdrawn or deleted accounts. Parent declaration I am the child's parent or legal guardian and have authority to consent. I have read this notice and authorize the described collection and use and disclosures integral to the requested church services. I understand that non-integral third-party disclosure requires a separate choice and is not authorized merely by this signature. I provide the required phone for verification contact and intend my entered full name to be my electronic signature. I understand that verification and current approval are required before account creation, and that I may refuse or withdraw permission.