Privacy Policy

This sample policy belongs to a fictional Maple Ridge Unified School District portal built to demonstrate SquareKit layouts. The people, schools, records, and procedures described here are synthetic. No production service or real district is governed by this page.

In this scenario, families use a demonstration portal to read school announcements, review attendance reminders, complete forms, and find event details. The statements below illustrate the kinds of topics a district policy could cover, but they intentionally make no promises about ParentSquare or any live system.

What information do we collect?

The fictional portal may display synthetic contact details, school affiliations, language preferences, notification choices, and relationships between sample family members and students. Demonstration forms may also contain invented responses, RSVPs, permission choices, or payment-request statuses.

Buttons, searches, subscriptions, and settings on this page are interaction demos. They may temporarily hold text in the browser so the example can respond, but they are not connected to a district directory, student information system, payment processor, or message-delivery service.

Any names, dates, attendance records, balances, and communications shown in the wider example collection are generated fixtures. Visitors should not enter real student, family, staff, financial, health, or emergency information into a demonstration field.

How do we use your information?

Within the fictional story, information helps the sample district route announcements, show translated family updates, demonstrate attendance follow-up, and organize forms or events. These examples describe interface intent only and do not represent live processing.

A demonstration subscription form may confirm the address typed into it and then clear the field. The confirmation is simulated. It does not enroll anyone in district news, emergency alerts, school newsletters, or product marketing.

This example does not define data-sharing, advertising, records-retention, or vendor practices for a real organization. A district adopting a similar layout would need its own reviewed policy, contracts, notices, and family support process.

Do we use cookies and other tracking technologies?

This sample does not state what any production service stores. In a real district notice, this section could explain sign-in sessions, accessibility preferences, analytics choices, and links to third-party school resources.

How long do we keep your information?

No retention schedule is promised here. The demonstration resets with its generated fixtures. A real district would publish schedules based on applicable student-record, public-record, finance, and local policy requirements.

How do we keep your information safe?

This page makes no security certification or incident-response promise. It demonstrates where a reviewed district explanation of account access, staff responsibilities, family reporting channels, and emergency contacts could appear.

What are your privacy rights?

Rights and request procedures vary by location and by the type of school record involved. For this fictional scenario, families are directed to their school office to ask how to review or correct information. This sentence is sample help language, not a legal interpretation.

How can you contact us about this policy?

For the demonstration, write to family-help@example.invalid. This address cannot receive mail. A production district page should replace it with reviewed contact details and tell families how to reach their school when a request is urgent. A useful request could include:

1. The fictional school or program shown in the example.
2. The type of sample record or screen you need help understanding.
3. Whether the question concerns a family message, attendance reminder, form, event, or payment request.