How this family portal demo uses sample information

This fictional policy supports a SquareKit layout demonstration for Maple Ridge Unified School District. It is not a policy for ParentSquare, a real district, or any production service. All people, schools, records, and support paths in the example are synthetic.

The example shows how legal and plain-language versions can share one responsive page. Any organization using a similar layout would need its own reviewed language, procedures, retention schedules, and contact details.

What information do we collect?

Sample profile details. The interface may display generated names, example.invalid email addresses, school affiliations, preferred languages, and notification choices for fictional family and staff profiles.

Sample school activity. Demonstration posts, messages, attendance reminders, forms, event responses, and payment statuses are generated fixtures. They do not describe real students, families, staff, or transactions.

Typed information. Search, subscription, and settings controls may temporarily hold what a visitor enters so the component can validate and respond. Visitors should not enter real student, family, health, financial, or emergency information.

How do we use your information?

To demonstrate workflows. Synthetic information lets the pages show family communication, translation, attendance follow-up, forms, events, and district help states without connecting to live school systems.

To demonstrate feedback. Buttons may show a toast describing what a real action could do. Search results, subscriptions, support requests, notifications, and data exports are simulated and are not sent anywhere.

To frame a review. The fictional text gives designers and district teams a safe place to discuss content hierarchy. It does not describe advertising, vendor sharing, consent, or legal obligations for a live service.

Do we use cookies and other tracking technologies?

This demonstration does not state what a production site stores. A reviewed district policy could use this section to explain sign-in sessions, language and accessibility preferences, analytics, and third-party school resources.

How long do we keep your information?

No production retention schedule is promised here. Generated fixtures remain part of the local example until the demonstration is reset or changed. Real districts should publish schedules reviewed for their location and record types.

How do we keep your information safe?

This sample makes no security certification, availability guarantee, or incident-notification promise. It demonstrates where a district could place reviewed guidance about account access, family reporting channels, and urgent support.

What are your privacy rights?

Rights and request procedures depend on location and record type. In this fictional scenario, a family member would contact the school office to ask how to review or correct a record. That example is navigation guidance, not legal advice.

How can you contact us about this policy?

The fictional contact is family-help@example.invalid. It cannot receive messages. A production page should replace it with district-approved contact details and a separate urgent-help path. A sample request could:

1. Name the fictional school or program shown on the screen.
2. Describe the sample message, attendance item, form, event, or payment request.
3. Avoid including real student or family information.