Privacy Policy

This Website (mp-opt-info)

This documentation and information site does not collect personal data or use tracking cookies or analytics.

• Theme preference - your choice of light, dark, or system theme is saved in your browser's local storage so it persists between visits. No data is sent to any server.

The Application (mp-opt.net)

The Masterplan Optimiser web application stores the minimum data necessary to provide its scheduling functionality:

• Names and email addresses - to identify participants and assign them to tasks.
• Locations and times - to build and optimise event schedules.
• Authentication credentials - passkey public keys for secure sign-in. No passwords are stored.

Cookies & Local Storage

The application does not use tracking cookies or analytics. The following items are stored locally or on the server:

• Session cookie - used solely for authentication. Expires when you sign out or after a period of inactivity.
• Theme preference - your light or dark mode choice is saved in local storage.
• Push notification subscription - if you enable notifications, your browser generates a push subscription (endpoint URL and encryption keys) which is stored on the server so schedule updates and announcements can be delivered. You can unsubscribe at any time via the notification bell icon.
• Offline calendar cache - your schedule data is cached locally by the service worker so you can view it without an internet connection. This cache is automatically refreshed whenever you load the calendar online.

How We Use Your Data

Data is used solely to provide the scheduling and calendar features of Masterplan Optimiser. We do not sell, share, or transfer personal data to third parties for marketing or advertising purposes.

Data Retention

Published schedule data is retained for the duration of the event. Administrators may delete events and all associated data at any time through the admin interface.

Third-Party Services

If Google Calendar integration is configured by the organiser, limited data (task titles, times, locations, and attendee names) is sent to Google's API to create calendar entries. This is governed by Google's Privacy Policy.

Push notifications are delivered via the Web Push protocol through your browser vendor's push service (e.g. Firebase Cloud Messaging for Chrome, Mozilla Push Service for Firefox). Message payloads are end-to-end encrypted and cannot be read by the push service.

Contact

For questions about your data, contact the event administrator who provided you access, or reach out via the contact page.