iConfirm Pilot Program Participation Agreement — v2

Reviewed — ready for use 2026-08-31
Prepared: August 23, 2026
Pilot: St. Paul confirmation class, beginning September 13, 2026
Version: 2026-08-31

Drafting note — read before editing. This Agreement is a disclosure and expectation-setting instrument, not a liability shield and not a substitute for COPPA compliance. A parent's signature here does not replace the Direct Parental Notice and verifiable parental consent required by 16 C.F.R. § 312.5, and it does not waive the Student's own legal claims — in most states a parent cannot waive a minor's claims, and a clause purporting to do so risks invalidating the surrounding provisions. This Agreement is executed in addition to, never instead of, documents 03 and 04.

Its actual value is threefold: it documents what the Parent was told about the pilot's known limitations; it sets accurate expectations so nobody is surprised; and it creates a clean record that participation was informed and voluntary. Draft it to be true, not to be protective. A pilot agreement that overstates protection is worth less than none.

1. What this is

BIBS Specialty Services, Inc. ("BIBS," "we," "us") is inviting a small number of families at [CHURCH NAME] ("Church") to be the first users of iConfirm, a web application supporting church youth confirmation programs.

This is a pilot. You are being asked to participate with your child before the product is generally available to your congregation, and we want you to make that decision with an accurate picture of what is finished and what is not.

Nothing in this Agreement is a condition of your child's participation in the Church's confirmation program. [CHURCH NAME] will confirm your child whether or not you use iConfirm. If you decline, or withdraw partway through, the Church will provide the confirmation curriculum in another form.

Parties. This Agreement is between BIBS and the parent or legal guardian who signs below ("you" or "Parent"), concerning the student identified below ("Student").

Pilot period. From [START DATE] through [END DATE], unless ended earlier under Section 9.

2. What is finished, and what is not

We would rather tell you this plainly than have you discover it.

Working and tested:

• Lesson delivery, progress tracking, and attendance
• Private reflections and private survey responses, stored under your Student's account
• Separation between what a Church Leader can see and what they cannot — tested and confirmed before the pilot begins
• Parent-controlled PIN reset; Leaders cannot see or reset a Student's PIN
• Your rights to review, export, correct, delete, or stop collection of your Student's information
• In-app sharing revocation — if your Student shares an entry and changes their mind, they can revoke it themselves in the app
• A static "Need help?" page, so a Student is reminded where to turn (a trusted adult, 911, or the 988 Lifeline) — it does not collect information or notify anyone; see Section 5

Not finished during the pilot period:

This table was reconciled against the running code on 2026-08-31 and matched it on every row. It is checked again before signature, and no feature is presented here as working that is not.

3. What we collect, and who can see it

The Direct Parental Notice and Consent (provided separately, and which you must complete before your Student's account is activated) is the controlling description of what we collect and how we use it. In summary:

We collect your Student's name and nickname, their association with you and the Church, a hashed sign-in PIN, attendance and lesson progress, their reflections and survey responses, their sharing choices, and technical records such as IP address and security logs. We also collect your Student's date of birth when you create the account, and use it only to check eligibility for the optional Discussion Board, which is limited to Students 13 and older — it is never shown to your Church's Leader and never included in a roster or export. We do not sell or rent this information, do not use it for advertising, and do not use your Student's writing to train AI systems.

Who can see private reflections:

Please make sure your Student understands the second and fourth rows. "Private" in iConfirm means private from Church Leaders. It does not mean private from you, and it does not mean nobody at BIBS could ever read it. We have written the Student-facing materials to say this plainly, and we would rather your Student hear it from you as well.

4. Joshua Pittman holds two roles at once during this pilot

This is unusual and you should know about it.

Joshua Pittman is both the sole operator of BIBS Specialty Services, Inc. and [TITLE] at [CHURCH NAME], where he will serve as the Leader for this confirmation class.

These roles are separated in the software. As a Leader, he sees exactly what any other Leader sees: name, attendance, progress, completion, and entries your Student deliberately marks as shared. He cannot reach private reflections or private survey responses through any Leader screen in the application. This has been tested and confirmed before the pilot begins.

As the operator, he has privileged access to the database, where reflections are stored as readable text. They are protected by encryption in transit and by our hosting provider's encryption at rest, but they are not end-to-end encrypted and they are not encrypted in a way that would prevent him from reading them.

He will use that access only when there is a documented reason: fulfilling a verified request from you, keeping the service secure, fixing a technical problem, or complying with the law. Every such access is logged with the date, the reason, and what was accessed. He will not read your Student's reflections out of pastoral interest, curiosity, or concern absent one of those reasons.

We are telling you this because it is true and because you should be able to weigh it. If it is not acceptable to you, that is a legitimate reason to decline, and declining carries no consequence for your Student's confirmation.

5. iConfirm is not a safety monitoring system

We do not read private reflections looking for signs that a young person is in trouble. No person and no software reviews them for mentions of self-harm, abuse, danger, or distress. If your Student writes something concerning in a private reflection, it is very likely that no one will see it.

Please tell your Student, in your own words: iConfirm is not the place to ask for help.

If your Student needs to talk to someone, they should speak to you, to a trusted adult, or to [CHURCH CONTACT]. The app shows a static "Need help?" page saying exactly that — it is informational only, collects nothing, and does not notify anyone. If anyone is in immediate danger, call 911. The 988 Suicide & Crisis Lifeline is available by call or text.

Revised 2026-08-24, on counsel's recommendation. An earlier version of this page was an interactive feature that notified a Leader and Parent when a Student used it. That has been removed from the Student-facing app: an active request-and-notify mechanism creates a mandated-reporter trigger under Missouri law today, and under every other state's law once a Church outside Missouri joins, and the compliance burden of tracking each state's statute for that mechanism is not sustainable at this stage. The underlying code still exists and may be reintroduced later. Your Church is independently responsible for telling your Student how to seek pastoral help outside iConfirm.

A written mandated-reporter escalation protocol for Leaders still exists (LEADER-ESCALATION-PROTOCOL-DRAFT.md, submitted for Missouri counsel review) — it covers a Leader becoming aware of a disclosure "through iConfirm or otherwise," not only through the removed in-app feature.

If we become aware of a disclosure of abuse or neglect. If information indicating that a child has been or may be abused or neglected comes to our attention — however that happens — we may have a legal duty to report it. In Missouri, ministers are mandated reporters under RSMo §§ 210.115 and 352.400 when practicing as a minister with responsibility for or access to a child; many states impose reporting duties on any person who becomes aware of suspected abuse. We will follow the law. We are not able to promise confidentiality in that situation, and we will not pretend otherwise.

iConfirm is not pastoral counseling, mental-health care, emergency services, or a confidential confession. Entries typed into this application are not legally privileged communications and are not protected from valid legal process.

6. Backups, data loss, and things going wrong

This is early software. Assume that anything your Student writes in iConfirm could be lost.

Please encourage your Student to keep anything they truly want to preserve somewhere else as well — a notebook, a document, a note on a phone.

We maintain backups of the production database on a backup-capable hosting plan, with automatic backups active. A restore test using synthetic data has not yet been run and verified, so we do not represent that our restore capability has been tested.

We will tell you promptly if we lose data affecting your Student, if we discover a security problem affecting their information, or if something happens that we think you would want to know about. We would rather over-communicate during a pilot.

7. Fees

Your Student's seat for the pilot is discounted to $0 by [CHURCH NAME] through a coupon applied at checkout. No separate charge occurs. If iConfirm becomes a paid service for your family after the pilot and you wish to continue, we will contact you first, tell you the price, and start no subscription and charge nothing unless you separately and affirmatively agree. You will never be automatically converted from the pilot into a paid subscription.

Because the seat is discounted rather than fee-waived outright, our checkout process previously still asked for a card number even though nothing was charged. That gap is closed: the fix that removed the card prompt was applied to Church-level signups and has since been applied to Student-level signups as well, so a fully discounted seat is not asked for a card. You will not be billed. Cancellation, renewal, and refund terms for any future paid subscription are in the Subscription, Cancellation, and Refund Policy.

How we verify your consent. Because the seat is discounted, we do not rely on the checkout charge itself to verify you as the parent — a $0 charge does not reliably notify a card issuer the way a real charge does. Instead, Joshua will meet with you in person, confirm your consent directly, and issue your Student's enrollment code only after you consent. This is at least as strong a verification method as the video-call method recognized under COPPA, and better suited to a pilot where you already know the person running it.

8. Feedback

We would like to hear what works and what does not. Any feedback you or your Student give us — bug reports, suggestions, criticism — we may use freely to improve iConfirm, without obligation or payment to you. Please do not include your Student's reflection content in feedback. Tell us what broke, not what they wrote.

Feedback is voluntary. Not giving it changes nothing about your participation.

9. You can stop at any time

You may withdraw your Student from the pilot at any moment, for any reason or none, by emailing office@iconfirm.app from the email address associated with your account. No explanation is required and no one will ask for one.

When you withdraw, we will:

1. acknowledge your email within [2] business days;
2. stop collecting new information from your Student immediately;
3. provide a copy of everything your Student wrote, if you want one; and
4. delete their information on the timeline described in the Privacy Policy — or immediately, if you ask us to.

Withdrawing from the iConfirm pilot does not withdraw your Student from confirmation class.

We may also end the pilot — for any family or for everyone — if we find a security or privacy problem, if the software is not working well enough to be worth your Student's time, or if continuing would be irresponsible for any other reason. If we do, we will tell you why, give you your Student's work, and delete their information.

10. Legal terms

No warranty. iConfirm is provided during the pilot "as is" and "as available." We do not promise it will be uninterrupted, error-free, or free of defects. To the maximum extent permitted by law, we disclaim implied warranties including merchantability, fitness for a particular purpose, and non-infringement. Some states do not allow certain disclaimers; those apply only as far as the law permits.

What this Agreement does not do. This Agreement does not waive, limit, or release any claim belonging to your Student, and does not waive any right you have that cannot be waived under applicable law — including your rights under the Children's Online Privacy Protection Act. Nothing here limits liability for gross negligence, willful misconduct, fraud, a privacy or security breach, a child-safety incident, or any liability that cannot lawfully be limited — the same carve-outs used in the Terms of Service, applied here to the pilot specifically because it involves minors' data.

Other documents. The Privacy Policy, Children's Privacy Notice, Direct Parental Notice and Consent, Terms of Service, and Student Privacy and Acceptable Use Notice all apply. Where this Agreement and another document conflict about the pilot period, this Agreement controls — except that the Direct Parental Notice and Consent always controls on the scope of your consent to collect your Student's information.

Governing law. Missouri law governs, without regard to conflict-of-law rules. Disputes not resolved informally will be brought in the state courts located in the City of St. Louis, Missouri, or the applicable federal court — except where consumer protection law requires another forum or where you may bring a claim in small-claims court. No arbitration clause applies to the pilot.

Changes. If we need to change this Agreement during the pilot, we will email you at least [10] days in advance and tell you plainly what changed. If a change materially affects what we collect from your Student or who can see it, we will obtain new consent before it takes effect.

Entire agreement; severability. This Agreement and the documents it references are the complete agreement about the pilot. If any provision is unenforceable, the rest remains in effect.

11. Questions

Ask them. During a pilot, a question is more useful to us than a quiet doubt.

BIBS Specialty Services, Inc.
735 Scanlan Avenue
St. Louis, Missouri 63139
office@iconfirm.app
314-222-2777

Acknowledgment and signature

By signing below, I confirm that:

• I am the parent or legal guardian of the Student named below, or I otherwise have legal authority to enroll them.
• I have read this Agreement, including Section 2 (what is not finished), Section 4 (Joshua Pittman's two roles), Section 5 (iConfirm is not a safety monitoring system), and Section 6 (data loss).
• I understand that "private" means private from Church Leaders, that I can request to see my Student's reflections, and that BIBS's operator can technically access them.
• I understand my Student's participation is voluntary and that declining or withdrawing will not affect their confirmation.
• I have had the opportunity to ask questions, and this consent was given after an in-person conversation with Joshua, not solely through this document.

This signature is not consent to collect my Student's information. I understand I will complete a separate Direct Parental Notice and Consent before my Student's account is activated.

Student name: _______________________________________

Parent/guardian name: _______________________________

Parent/guardian email: ______________________________

Signature: __________________________ Date: ____________

Documents received (versions):
Pilot Agreement [v___] · Privacy Policy [v___] · Children's Privacy Notice [v___] · Direct Parental Notice and Consent [v___] · Terms of Service [v___] · Student Notice [v___]

For BIBS Specialty Services, Inc.

Name: Joshua Pittman Title: _______________

Signature: __________________________ Date: ____________