Last Updated: July 7, 2026
Service: Bridge
Company: Invent Yourself, LLC
1. Introduction
This Privacy Policy describes how Invent Yourself, LLC (“Company,” “we,” “us,” or “our”) collects, uses, discloses, stores, and protects information in connection with Bridge, including our website, application, chatbot features, educational resources, AI-supported tools, account services, subscription features, and related services collectively referred to as the “Service.”
By accessing or using Bridge, you acknowledge that you have read this Privacy Policy. If you do not agree with this Privacy Policy, do not use Bridge.
2. Scope of This Policy
This Privacy Policy applies to information we collect through Bridge, including information collected through our website, application, account system, chatbot features, organization access features, payment-related workflows, support communications, and related services.
This Privacy Policy does not apply to third-party websites, services, or platforms that we do not control, even if they are linked from Bridge. Third-party services may have their own privacy policies and practices.
3. Bridge’s Intended Use and Privacy Posture
Bridge is designed for de-identified, generalized behavioral education, caregiver support, practical reflection, and educational guidance. Bridge is not designed for clinical documentation, diagnosis, treatment planning, emergency support, client-record workflows, healthcare-record workflows, school-record workflows, or the submission of sensitive identifying information.
Bridge is not currently offered as a HIPAA-supported product or service. We do not currently execute Business Associate Agreements (“BAAs”) for Bridge. Users must not submit protected health information (“PHI”), personally identifiable information, student-identifying information, client-identifying information, or other sensitive identifying details into Bridge.
4. Information You Should Not Submit
Bridge is intended to work with general, de-identified descriptions. Users should not submit information that identifies or could reasonably be used to identify a specific child, client, patient, student, family member, provider, teacher, school, clinic, agency, or other individual or organization when tied to a specific person.
Do not enter:
- Names of children, clients, patients, students, family members, providers, teachers, schools, clinics, or agencies;
- Dates of birth;
- Addresses;
- Phone numbers;
- Email addresses;
- Social Security numbers;
- Medical record numbers;
- Insurance numbers;
- Student ID numbers;
- Case numbers;
- Account numbers;
- Full-face images or identifying photos;
- IEPs, evaluations, education records, disciplinary records, medical records, service logs, or clinical records;
- Any other information that could identify a specific person.
Use general, de-identified descriptions instead. For example, use: “A 7-year-old has trouble transitioning away from a preferred activity.” Do not use: “[Child’s name], born [date], at [school name], had an incident with [teacher/provider name] on [specific date].”
5. Information We Collect
We may collect the following categories of information depending on how you use Bridge.
5.1 Account Information
We may collect information used to create, manage, and secure your account, such as your name, email address, authentication identifier, user ID, organization ID, access-code status, role, permissions, account status, and related account settings.
5.2 Authentication and Security Information
We use authentication and security tools to help users sign in, protect accounts, prevent misuse, and operate Bridge safely. This may include information such as login timestamps, authentication events, device or browser information, IP address, user agent, security metadata, and related technical information.
5.3 User-Submitted Content
Bridge may process user-submitted prompts, selected options, optional details, mode selections, conversation context, and other information users provide while using Bridge’s AI-supported features.
Bridge does not currently store full chat conversations or generated responses in our application database. Chat content may be temporarily processed as necessary to generate responses, deliver the Service, maintain security, troubleshoot errors, and comply with legal obligations.
5.4 Generated Responses
Bridge generates AI-supported responses based on user-submitted prompts, selected options, and general context. Generated responses may be temporarily processed as needed to provide the Service. Bridge does not currently store full generated responses in our application database.
5.5 Usage Information
We may collect usage-related information, such as token usage, monthly usage totals, account limits, organization limits, mode usage, timestamps, error events, request metadata, feature usage, and other information needed to operate, secure, monitor, troubleshoot, and improve Bridge.
5.6 Organization Access Information
If you access Bridge through an organization, access code, subscription group, pilot program, school, agency, employer, or similar organization, we may collect and process information related to your organization access, such as your organization ID, access status, role, permissions, usage totals, account status, subscription status, and administrative settings.
5.7 Payment and Subscription Information
If Bridge offers paid subscriptions, we may collect and process subscription-related information, such as Stripe customer identifiers, subscription status, plan type, billing period, cancellation status, payment status, and limited payment metadata.
Payment information may be processed by our payment processor. We do not intend to store full credit card numbers on our own servers.
5.8 Technical, Log, and Device Information
We may collect technical information needed to operate and secure Bridge, such as IP address, browser type, device type, operating system, request metadata, backend logs, error logs, performance data, security events, and similar technical information.
5.9 Support Communications
If you contact us for support, we may collect your name, email address, message content, and any information you choose to provide in your communication.
6. Chat Content, Local Storage, and Exports
Bridge does not currently store full chat conversations or generated responses in our application database. User prompts, selected options, conversation context, and generated responses may be processed temporarily as necessary to provide AI-supported features.
Some information may be stored locally in the user’s browser or device, such as temporary session information, interface preferences, or locally generated export/download content. Local browser storage is controlled by the user’s browser or device settings.
When a user copies or downloads a Bridge response, that export is created locally in the user’s browser. Bridge does not currently create or store a server-side copy of downloaded text exports.
7. How We Use Information
We may use information for the following purposes:
- To provide, operate, and maintain Bridge;
- To authenticate users and manage accounts;
- To provide AI-supported responses and educational guidance;
- To manage subscriptions, billing status, account access, and organization access;
- To enforce usage limits, account limits, and organization limits;
- To provide customer support and respond to user requests;
- To monitor, troubleshoot, and improve Bridge’s functionality;
- To maintain security, prevent misuse, investigate suspicious activity, and protect users;
- To improve Bridge’s educational content library, internal support materials, prompts, workflows, and safety systems;
- To comply with legal obligations, enforce our Terms, and protect our rights.
8. AI Processing and Model Training
Bridge uses artificial intelligence, including large language models and related technologies, to generate educational responses based on user-submitted prompts, selected options, and general context.
Bridge does not use user prompts, chat messages, selected options, uploaded content, or generated responses to train third-party foundation models.
Bridge is supported by an internal educational content library, prompts, workflows, and reference materials designed to provide generalized behavioral education and caregiver support. We may review, update, and improve these internal materials over time to support accuracy, clarity, safety, usefulness, and timeliness.
Licensed or qualified professionals may assist with reviewing Bridge’s educational content, support materials, response patterns, prompts, workflows, and internal knowledge resources to help ensure that the information Bridge draws from remains appropriate, current, and aligned with general professional standards.
Users must not submit PHI, personally identifiable information, student-identifying information, client-identifying information, or other sensitive identifying details into Bridge.
9. De-Identified, Aggregated, and Anonymized Information
We may use aggregated, de-identified, or anonymized information to operate, secure, monitor, troubleshoot, analyze, and improve the Service. This may include usage trends, feature performance, error trends, safety monitoring, product improvement, and educational content improvement.
We do not intend for aggregated, de-identified, or anonymized information to identify a specific user, child, client, patient, student, family member, or other individual.
10. Third-Party Service Providers
We use third-party service providers to operate Bridge. These providers may process information as necessary to provide services to us, including hosting, authentication, database storage, AI response generation, payment processing, security, domain services, and technical operations.
| Provider | Purpose | Examples of Data Processed |
|---|---|---|
| OpenAI | AI response generation | User prompts, selected options, conversation context, generated responses, and technical metadata as needed to provide AI-supported features. |
| Google Firebase Authentication | User login and account authentication | Name, email address, user ID, authentication identifiers, login events, user agents, IP addresses, and security-related login information. |
| Google Firestore / Firebase | Database storage and application functionality | Account records, organization access data, usage records, subscription-related application data, settings, and technical application data. |
| Google Cloud Platform | Backend hosting, infrastructure, and security | Backend request data, service logs, security logs, error logs, technical metadata, IP addresses, and application data needed to operate Bridge. |
| Stripe | Payment processing and subscription management | Billing information, payment status, subscription status, customer identifiers, plan information, and limited payment metadata. |
| Hostinger | Domain registration and DNS services | Domain-related records, DNS records, and related technical information. Hostinger is currently used for domain/DNS services and not as the primary application hosting provider. |
We may add, remove, or replace service providers over time as needed to operate, secure, maintain, or improve Bridge.
11. Organization Accounts and Administrator Access
Some users may access Bridge through an organization, subscription group, pilot program, access code, school, agency, employer, or other organization.
Organization administrators may be able to view limited account and usage information, such as user names, email addresses, account status, organization access status, role or permission level, subscription-related information, token or usage totals, and similar administrative data.
Organization administrators cannot view full user chat conversations through Bridge’s organization dashboard.
Users should not submit PHI, student-identifying information, client-identifying information, or other sensitive identifying details into Bridge, even if they access Bridge through an organization.
12. How We Share Information
We may share information in the following limited circumstances:
- Service providers: We may share information with service providers that help us operate, secure, host, deliver, and improve Bridge.
- Organization administrators: If you access Bridge through an organization, limited account and usage information may be available to organization administrators as described in this Privacy Policy.
- Legal compliance: We may disclose information if we believe disclosure is required by law, court order, subpoena, legal process, government request, or regulatory obligation.
- Security and misuse prevention: We may disclose information when we believe it is necessary to investigate, prevent, or address fraud, security issues, misuse, violations of our Terms, or harm to Bridge, users, or others.
- Business transfers: We may disclose or transfer information in connection with a merger, acquisition, financing, reorganization, sale of assets, bankruptcy, or similar business transaction.
- With your consent: We may share information when you direct us to do so or otherwise give consent.
13. Data Retention
Bridge does not currently store full chat conversations or generated responses in our application database.
We may retain account information, authentication information, organization access information, subscription-related information, usage totals, security information, technical logs, support communications, and similar operational information for as long as needed to provide the Service, maintain security, comply with legal obligations, resolve disputes, enforce agreements, and support legitimate business operations.
We do not intentionally retain chat history for long-term use. However, limited technical logs, backend request records, authentication records, billing records, or service-provider records may be retained for operational, legal, security, troubleshooting, fraud-prevention, subscription-management, or compliance purposes.
If you request account deletion, we will review and process the request consistent with applicable law, our operational needs, security needs, billing obligations, and service-provider limitations.
14. Your Choices and Privacy Requests
Depending on your location and applicable law, you may have certain rights or choices regarding your personal information. These may include the ability to request access to, correction of, or deletion of certain personal information.
You may request account deletion by contacting us at simon [at] 50byfriday [dot] com . We may need to verify your identity before processing certain requests.
If you receive marketing communications from us, you may opt out of those communications by following the instructions in the message or contacting us. Even if you opt out of marketing communications, we may still send administrative, transactional, security, billing, or service-related communications.
15. Children’s Privacy
Bridge is intended for use by adults. Bridge is not intended to be used directly by children, and users must be at least 18 years old, or the age of majority in their jurisdiction, to create an account or use the Service.
Bridge may discuss caregiver, student, child, family, or client-support situations, but adults are responsible for ensuring that their use of Bridge does not include children’s personal information or other identifying details.
We do not knowingly collect personal information directly from children. If you believe a child has provided personal information directly to Bridge, contact us so we can review the issue.
16. HIPAA, PHI, and Health Information
Bridge is not currently offered as a HIPAA-supported product or service. We do not currently execute Business Associate Agreements for Bridge.
Users must not submit PHI, identifiable health information, medical records, insurance information, clinical documentation, diagnosis details tied to an identifiable person, treatment records, provider records, or other regulated health information into Bridge.
If you are a healthcare provider, health plan, clinic, agency, covered entity, business associate, or other regulated organization, you are responsible for determining whether your use of Bridge is permitted under your own legal, privacy, professional, organizational, and contractual obligations.
17. FERPA, Student Records, and School Information
Bridge is not intended to create, receive, maintain, transmit, or process education records, student records, school records, special education records, IEPs, evaluations, disciplinary records, service records, or other records that may be protected by FERPA or similar student-privacy laws.
School personnel, educators, contractors, service providers, and organization users are responsible for determining whether their use of Bridge is permitted under FERPA, state student-privacy laws, school policies, district rules, professional obligations, and any applicable contracts or data-processing agreements.
Users must not submit student-identifying information, school records, education records, IEP content, evaluation reports, disciplinary records, service logs, or other information that could identify a specific student, child, family, school, classroom, provider, or educational record.
18. Mandated Reporting and Safety
Bridge does not monitor situations in real time, does not contact emergency services, and does not make reports to child protective services, adult protective services, schools, law enforcement, or any other authority.
Users remain solely responsible for complying with any mandated-reporting, workplace, school, professional, licensing, ethical, or legal obligations that may apply to them. If you suspect abuse, neglect, exploitation, immediate danger, or another reportable concern, do not rely on Bridge. Contact the appropriate emergency service, protective agency, hotline, supervisor, school official, or legal authority as required by law and your professional or organizational responsibilities.
19. Security
We use reasonable administrative, technical, and organizational safeguards designed to protect information associated with Bridge. These safeguards may include access controls, authentication tools, cloud security practices, database security rules, monitoring, and other measures designed to reduce the risk of unauthorized access, misuse, or disclosure.
However, no system, service, website, database, cloud provider, or internet transmission is completely secure. We cannot guarantee that information will never be accessed, used, disclosed, altered, or destroyed without authorization.
20. Data Breach or Security Incident Notices
If we learn of a security incident affecting personal information, we will evaluate the incident and provide notices as required by applicable law.
Users are responsible for maintaining the security of their own accounts, devices, browsers, and login credentials. Notify us promptly if you believe your Bridge account has been compromised.
21. International Users
Bridge is operated from the United States. If you access Bridge from outside the United States, your information may be processed in the United States or in other locations where our service providers operate.
By using Bridge, you understand that privacy laws in the country where information is processed may differ from the laws in your location.
22. Changes to This Privacy Policy
We may update this Privacy Policy from time to time. If we make material changes, we may provide notice by posting the updated Privacy Policy, sending an email, providing in-app notice, or using another reasonable method.
Your continued use of Bridge after an updated Privacy Policy becomes effective means you acknowledge the updated Privacy Policy.
23. Contact Us
If you have questions about this Privacy Policy or want to submit a privacy request, contact:
Invent Yourself, LLC
47 Rutz Subdivision Rd
Cuba, MO
simon [at] 50byfriday [dot] com