Last updated: 12/9/2025
1. Introduction
School Conference Go respects your privacy and is committed to protecting your personal data. This privacy policy will inform you as to how we look after your personal data when you visit our website and tell you about your privacy rights and how the law protects you.
2. Data We Collect
We collect data necessary to schedule parent-teacher conferences. This includes:
- Identity Data: First name, last name.
- Contact Data: Email address, telephone number.
- Technical Data: Internet protocol (IP) address, browser type and version, time zone setting and location.
- Usage Data: Information about how you use our website and services.
3. How We Use Your Data
We will only use your personal data when the law allows us to. Most commonly, we will use your personal data in the following circumstances:
- To facilitate the booking of appointments between parents and teachers.
- To send you confirmation emails and reminders about your appointments.
- To manage our relationship with you (e.g., notifying you about changes to our terms or privacy policy).
4. Data Security
We have put in place appropriate security measures to prevent your personal data from being accidentally lost, used, or accessed in an unauthorized way, altered, or disclosed.
5. Your Legal Rights
Under certain circumstances, you have rights under data protection laws in relation to your personal data, including the right to request access, correction, erasure, restriction, transfer, or to object to processing.
Student Privacy Quick Guide
FERPA + COPPA Compliance for School and District Customers
What This Product Does
School Conference Go helps schools run parent-teacher conference scheduling and reminders, making it easy for families to book appointments and for administrators to manage the entire process.
Data We May Process
- Account Data: Name, email address, role (staff, parent/guardian, admin).
- Optional Contact Data: Phone number if SMS reminders are enabled.
- Scheduling Data: Time-slot selections, availability, and attendance status.
- Conference Context: Teacher names and meeting slot info; student name may be entered only when a school chooses to use it.
- Operational Logs: Audit and security logs to prevent abuse and support troubleshooting.
FERPA: How We Support School Compliance
When a school or district uses our products, we act as a service provider performing an institutional function for the school. Our goal is to help schools meet the requirements commonly used for outsourcing under FERPA.
- We use student data only to provide the service requested by the school or district.
- We do not sell student data and we do not use it for targeted advertising.
- We contractually limit access to authorized personnel and approved subprocessors that help deliver the service (for example, hosting, email, and SMS vendors).
- We support school control: data access is role-based and administrators can export or delete data subject to applicable retention needs.
COPPA: Children Under 13
Our products are intended for school-administered use and are not designed as child-directed services. If a school enables use involving children under 13, we follow COPPA expectations for education technology use in schools.
- We provide schools notice about what data is collected and how it is used.
- Where a school acts as the parent's agent for consent in an educational context, we rely on the school's authorization and limit use to the school purpose.
- As a best practice, we make privacy information available to parents and provide a path to review or request deletion of a child's information.
Security, Retention, and Deletion
- Security: Encryption in transit; least-privilege access; monitoring and logging; secure vendor management.
- Retention: Customer data is retained only as needed to provide the service and meet contractual or legal requirements.
- Deletion: Upon request and subject to school approval, we support deletion of records; after contract end, we delete or de-identify data per the agreement and operational backup cycles.
What Schools and Districts Should Do
- Configure roles and permissions so staff and parents see only what they need.
- Share appropriate notices with families and follow district policy for vendor use.
- Request a Data Privacy Agreement (DPA) or addendum if required by your district.