Privacy Policy
Effective Date: 12.08.2025 • Last Updated: March 2, 2026
1. Who We Are
EquiOps is operated by VenturePath Enterprises LLC, registered in Missouri. This Privacy Policy explains how EquiOps collects, uses, discloses, stores, and protects information through our website, pilot intake workflows, and district analytics platform.
2. Scope and Applicability
This policy applies to website visitors, district personnel, pilot applicants, demo users, and authorized users of EquiOps services. It does not replace district-level policies, contracts, or applicable law that govern district-owned records.
3. Information We Collect
- Contact and account information such as name, work email, role, district, and related organization details.
- District operational inputs such as enrollment, attendance, FRL aggregates, meal counts, labor allocation metrics, and program performance indicators.
- Platform usage and technical information such as device/browser metadata, session diagnostics, feature usage events, and security logs.
- Communications and support information submitted by district users and website visitors.
4. Sources of Information
Information is collected from:
- District users and administrators directly.
- District-provided datasets and authorized data transfers under district agreement.
- Website interactions and technical instrumentation necessary for security and product operations.
- Service providers acting on our instructions for hosting, monitoring, and operational support.
5. How We Use Information
- Provide and maintain EquiOps services.
- Generate analytics outputs, forecasting, benchmark reporting, and workflow recommendations requested by districts.
- Authenticate users, enforce access controls, and secure service integrity.
- Respond to support, onboarding, contracting, and operational inquiries.
- Improve usability, reliability, and performance in line with legitimate business and contractual obligations.
6. Disclosures and Service Providers
We may share information with vetted service providers that support hosting, monitoring, security operations, communications, and related platform services. These providers are contractually required to use data only for authorized purposes and to maintain appropriate privacy and security safeguards.
7. District Role and Data Ownership
Districts retain ownership of district data. In most district service contexts, the district is the controller and EquiOps acts as a processor under district instructions and agreement terms, including any Data Processing Addendum.
8. FERPA Context
EquiOps is designed for FERPA-aligned district operations and focuses on operational analytics. Where student-related data is processed, processing occurs under district authorization, role-based access controls, and applicable contractual and legal obligations.
9. Data Minimization and Use Limitation
We seek to limit collection and retention to data reasonably necessary for defined operational purposes. Data is not sold and is not used for unrelated third-party marketing.
10. Security Safeguards
EquiOps uses administrative, technical, and organizational safeguards, including least-privilege access, encrypted transport, protected storage controls, monitoring, and incident response procedures appropriate to risk and service context.
11. Retention and Deletion
Information is retained according to contract requirements, legitimate business needs, and legal obligations. Upon termination or request, district data handling follows contractual return/deletion provisions, subject to lawful retention requirements.
12. U.S. Privacy Rights and Requests
Depending on applicable U.S. law and context, individuals may request access, correction, deletion, or restriction of personal information. District users may need to route certain requests through district administrators where district policy or law requires.
13. Children and School Context
EquiOps services are intended for district-authorized adult users and are not consumer-directed services for children. District-authorized student-related processing is governed by district agreements and education privacy requirements.
14. Data Location
EquiOps generally operates using U.S.-based service infrastructure, except where a written agreement specifies otherwise.
15. Changes to This Policy
We may update this Privacy Policy periodically. Material updates are posted on this page with an updated revision date. Continued use after updates is subject to applicable law and contract terms.
16. Contact
For privacy inquiries, contact privacy@equiops.org.
17. Informational Notice
This policy is provided for general informational purposes and does not constitute legal advice.