Privacy Notice

1. Who this notice covers

This Privacy Notice describes PrincipalGO™, operated by Strategically Engaged, a business of Nielsen Family Holdings LLC. It applies to individual beta users and visitors to PrincipalGO’s beta service. A school or district agreement may add or replace certain data-handling terms for organizational use.

2. Information we collect

Depending on how you use PrincipalGO, we may collect:

Account information: name, email address, authentication status, account timestamps, and profile preferences.

Workflow information: task titles and instructions, reminders, deadlines, status, activity history, and settings.

Delegation information: trusted-contact names, roles, email addresses, recipient details, and task-related message records.

Attachments: photos or files you intentionally attach to a PrincipalGO task or workflow.

Connected-service information: information needed to perform the Google Gmail, Calendar, or Drive actions you authorize.

Usage and security information: product activity timestamps, integration status, diagnostic events, and security-related logs.

Consent records: the versions and timestamps associated with Terms, Privacy, and safe-use acknowledgments.

3. How we use information

We use information to provide and secure PrincipalGO, save and synchronize your workspace, perform the actions you request, route delegated work, support connected integrations, troubleshoot problems, prevent abuse, improve beta functionality, communicate about the service, and document required user consent.

4. Google user data

PrincipalGO requests Google access only for features you choose to use. Current beta features may use Gmail to identify or act on messages you authorize, Calendar to check availability or create events, and Drive to work with Approved Folders and Approved Files.

Approved Folders: when you approve a Drive folder, PrincipalGO may list and work with files in that folder and its subfolders so GO can find the content you ask it to use or edit and can create new files there. Files inside an Approved Folder do not require separate one-by-one approval.

Approved Files: when you approve one file, PrincipalGO may work with that specific file without treating the folder it lives in or neighboring files as approved.

Google’s authorization required to support folder-level behavior can technically permit broader Drive access. PrincipalGO is designed to enforce a narrower product boundary by limiting Drive discovery and actions to your Approved Folders, their subfolders, and your explicitly Approved Files. PrincipalGO does not intentionally scan or copy the rest of your Drive into the PrincipalGO workspace.

We use Google user data only to provide or improve the user-facing features you request and in accordance with applicable Google API Services policies and Limited Use requirements.

5. Student and sensitive information

PrincipalGO Beta is designed for adult school-leadership workflow, not student accounts. Unless your school or district has specifically authorized the use and an appropriate agreement is in place, do not submit student education records, health information, discipline or special-education records, passwords, credentials, financial information, or other restricted information.

6. How information is shared

We may share information only as needed to operate the service, including with service providers that host, authenticate, secure, transmit, or support PrincipalGO; with connected providers such as Google when you authorize an integration; with recipients you direct PrincipalGO to contact; when required by law; or as part of a business transaction subject to appropriate safeguards.

We do not sell PrincipalGO user data to advertisers. We do not use Google Workspace data for targeted advertising.

7. Data storage and retention

PrincipalGO stores account and workflow data needed to provide the service and maintain task history. Retention may vary by data type, beta testing needs, security requirements, or a separate school/district agreement. When a beta account is closed or a pilot ends, data may be deleted, de-identified, or retained for a limited period where necessary for security, legal obligations, dispute resolution, or documented customer requirements.

8. Security

We use reasonable technical and administrative safeguards designed to protect PrincipalGO data, including authenticated access and user-level data controls. No internet service can guarantee absolute security. If you believe your account or data has been compromised, contact support@principal-go.com.

9. Your choices and controls

You can choose whether to connect supported integrations, manage Approved Folders and Approved Files, manage trusted contacts, sign out, and stop using the beta. You may contact us to ask about access, correction, deletion, or other privacy rights that apply to you under applicable law. Some requests may be subject to identity verification, organizational requirements, or legal retention obligations.

10. Individual accounts and organizational use

PrincipalGO may be used through individual accounts, subject to any applicable employer policies and required approvals.

If a district or other authorized educational organization chooses to deploy PrincipalGO across multiple users or campuses, centrally manage accounts, or require institutional privacy and security terms, a separate written agreement may apply.

Users should not enter restricted student or organizational information unless that use has been appropriately authorized.

11. Changes to this Notice

We may update this Privacy Notice as the beta evolves. If a material change affects the version you previously acknowledged, PrincipalGO may require a new acknowledgment before continued use.

12. Contact

Questions or privacy requests may be sent to support@principal-go.com.