Privacy And Data Practices

Connect360 helps trained staff find and coordinate community resources without building another identity database. Connect360 does not ask for or store names, dates of birth, street addresses, phone numbers, email addresses, student IDs, identity documents, diagnoses, treatment records, or medical documents.

A claim code and PIN connect a person to their service-navigation record. The organization helping the person may keep the code-to-person link in its own system; Connect360 does not receive that link.

In school deployments, students do not complete the Connect360 eligibility assessment themselves. Only district-approved staff conduct intake. Student identity remains in district systems, while Connect360 receives only the minimum service-navigation information needed for matching, referral tracking, barriers, and outcomes.

Final privacy, consent, retention, and data-handling terms are established with district counsel and technology leadership.

Your Connect360 claim code and PIN open your service-navigation record. Keep them private and store the printout in a safe place. Connect360 does not know your name or contact information. The school, church, or organization helping you may keep the connection between your name and code in its own records. If your code is lost, contact the organization that issued it.

Connect360 is not an electronic health record, clinical exchange, or repository for protected health information. Healthcare organizations may maintain resource listings and participate in non-PHI referral workflows, but they must not send diagnoses, treatment information, medical documents, or other PHI through Connect360. Any workflow that requires PHI remains in the provider's own system.

Your organization may continue using its own member or client records to know who you are serving. Connect360 does not need that identity. If you need to connect a person to a Connect360 claim code, keep that code-to-person reference in your own approved system.

Your Connect360 staff account uses multi-factor authentication for security, while the claim code and PIN control access to the service-navigation record.

This is a demonstration environment. All organizations, campuses, families, and records shown are fictional.

We record which invitation link was used, which role you selected, and which screens you reached, so we can understand how the demo is being used. We do not use advertising trackers, cross-site cookies, or third-party analytics services, and we do not record your screen or store full IP addresses.

If you ask us to contact you, we store the name, organization, email, and phone number you provide, and we use it only to follow up with you. To have that information removed, email privacy@talentyieldcoalition.org.

Connect360 itself stores no family names, dates of birth, addresses, or contact information. The contact form on this demonstration site is how you reach us — it is not how the platform works.

Connect360 keeps resource information current through human-validated updates. Trusted contributors can submit official policy, resource, meeting, or training sources. AI may extract proposed changes, but it never publishes them automatically. Community Workers and Administrators may validate and publish directly; other approved contributors submit their validated changes for Community Worker or Administrator review. Each published change keeps its source and version history.

Upload only official resource, policy, meeting, or training material that is appropriate for the resource knowledge base. Do not upload client or student case notes, names, contact information, student IDs, medical records, diagnoses, treatment details, or other person-specific information. Uploaded source material is temporarily quarantined for sanitization and extraction before any structured change can be published.

Connect360 separates identity from navigation. Your organization keeps the person's identity in the system you already use. Connect360 receives only the minimum information needed to find resources and track the service pathway. Staff use secure accounts with multi-factor authentication, while families use a claim code and PIN. Resource rules can improve over time through AI-assisted extraction, but a trained human validates every published change.