Paylocity

Structured Summary of Important Changes

1. AI model training and customer-data use

• No express change concerning AI, machine learning, or training models appears in the diff.
• The diff does not add or remove language stating whether customer, employee, or other personal data may be:
• used to train AI or machine-learning models;
• used to improve or develop products;
• combined with other customers’ data;
• anonymized or de-identified for secondary purposes; or
• shared with AI providers or other subprocessors.
• The only potentially relevant privacy language is the unchanged/general statement that, by submitting the form, the user agrees to the “processing of your personal information as described in our Privacy Policy.”
• Risk: Because the Privacy Policy is incorporated by reference but not included in the diff, any AI-training permissions may exist there and cannot be assessed from this comparison. The customer should review the current Privacy Policy and any data-processing agreement for express AI-training and product-improvement provisions.

2. Privacy notice and consent language

• The form content appears to be reorganized rather than substantively amended.
• The language requiring agreement to processing of personal information under the Privacy Policy remains present.
• The form also continues to include an option indicating that the individual would like to receive email updates from Paylocity.
• Potential risk: The diff does not clearly show whether marketing consent is optional, preselected, or properly separated from consent necessary to submit the form. If the checkbox or consent mechanism changed in the underlying webpage, this could affect compliance with marketing and privacy laws.

3. Website navigation and resources

• “Blogs” is added in several navigation areas.
• Various resource labels and navigation categories are reordered or renamed, including references to:
• HR, Payroll, Finance, IT, and labor resources;
• “Access Management” and “Identity”;
• product training, tax and compliance, and other resource pages.
• These changes appear primarily editorial or navigational and do not themselves alter contractual rights or data-use permissions.

4. Contact and form presentation

• The contact telephone number is inconsistently displayed, including both 833.508.0746 and 8335080746.
• Form labels and navigation text appear duplicated, fragmented, or misordered, likely due to a webpage extraction or formatting issue.
• Risk: If this reflects the live customer-facing form, unclear field labels, duplicate content, or malformed consent text could create ambiguity about what information is collected and what the user is agreeing to.

Bottom line

The diff shows no identifiable new authorization to use customer data for AI training. The primary unresolved issue is the referenced Privacy Policy, which must be reviewed separately.

Summary

The diff only states that approximately 160 words were added; it does not include the actual added language or identify where it appears in the document.

Substantive Changes

• Cannot be determined from the information provided.
• The nature, scope, and legal effect of the additions cannot be assessed without the text of the new provisions.

Customer Data and AI Training

• No conclusion can be reached about whether customer data may be used to train, fine-tune, evaluate, or improve AI models.
• The added language could potentially address:
• Use of customer content for model training or service improvement;
• Whether use is limited to aggregated, de-identified, or anonymized data;
• Whether customer consent or an opt-out is required;
• Ownership and licensing rights in customer data and model outputs;
• Retention, deletion, confidentiality, or disclosure of data;
• Use by affiliates, subprocessors, or third-party AI providers; and
• Security, regulatory, or cross-border transfer obligations.

Risk Assessment

The actual additions are necessary to identify any new or increased risks, including:

• Broader rights to use customer data;
• Use of identifiable or confidential information for AI development;
• Ambiguous definitions of “customer data,” “content,” or “service improvement”;
• Lack of customer approval, notice, or opt-out rights;
• Irrevocable, worldwide, royalty-free licenses;
• Reduced confidentiality or data-deletion protections; and
• Conflicts with privacy laws or the customer’s contractual obligations.

Required Information

Please provide the approximately 160 words that were added, together with the surrounding original language if the additions replace or modify existing provisions.

Summary of Important Changes

1. Privacy and data-processing language

• The form now states that, by submitting the form, the user agrees to the processing of their personal information as described in Paylocity’s Privacy Policy.
• This is a potentially important legal change because it may convert submission of a demo/contact form into an affirmative acknowledgement or consent to data processing.
• The wording does not identify:
• The specific categories of data collected;
• The purposes of processing;
• Legal bases for processing;
• Data retention periods;
• Third-party recipients or service providers;
• International transfers; or
• Whether consent can be withdrawn.
• The reference to the Privacy Policy may incorporate terms that can be changed separately, creating uncertainty about what the user is agreeing to at the time of submission.

2. Marketing communications

• The revised form includes language indicating that the user would like to receive email updates from Paylocity.
• The diff does not clearly show whether this is a required field, preselected checkbox, or optional marketing consent. That distinction is legally significant.
• If marketing consent is bundled with a demo request or other necessary form submission, there may be risks under applicable marketing-consent laws, including requirements for freely given, specific, and revocable consent.
• The form should clearly separate:
• Submission of information to respond to the request; and
• Optional consent to receive promotional emails.

3. Information collected

The form continues to request or display fields including:

• Email address and phone number;
• First and last name;
• Company name;
• Business ZIP code;
• Employee-count range;
• Job title; and
• Business or industry-related information.

These fields may constitute personal information, particularly when combined with employment and business affiliation data. The revised privacy language should accurately cover all fields and explain whether information is used for lead qualification, sales activity, analytics, personalization, or marketing.

4. AI-model training

• No express change concerning the use of customer or visitor data to train, fine-tune, evaluate, or improve AI models was identified in this diff.
• The revised reference to processing “personal information” is broad, but it does not expressly authorize AI training or prohibit it.
• If Paylocity intends to use submitted information for AI-related purposes, that use should be addressed expressly in the Privacy Policy or applicable agreement, including applicable opt-out rights, de-identification standards, retention, and disclosure to AI providers.

5. Website and content changes

• The diff substantially reorganizes navigation and adds or changes links and categories, including “Identity,” “Company,” “About Us,” “Careers,” “Investors,” “Newsroom,” and related resources.
• Repeated or malformed text appears in the diff, suggesting possible template, rendering, or accessibility issues. These should be reviewed to ensure the final form presents legally required notices clearly and accurately.

Summary of Important Changes

1. Marketing communications consent added

The revised text adds an express checkbox/statement:

> “Yes, I’d like to receive email updates from Paylocity.”

This appears in the demo request form and may constitute a marketing opt-in. Key risks:

• The consent language does not clearly describe the types or frequency of communications.
• It does not state whether consent is optional or required to request a demo.
• The mechanism for withdrawing consent is not shown.
• Depending on applicable law, the form may need separate, affirmative consent and appropriate disclosures for email marketing, including CAN-SPAM, GDPR/UK GDPR, and other electronic-marketing laws.
• The text should clarify whether submitting the form automatically enrolls the individual in marketing communications or whether the checkbox is optional and unchecked by default.

2. Expanded personal-information collection and form labeling

The revised form expressly identifies fields including:

• Email address
• Phone number
• First and last name
• Company name
• Business ZIP code
• Employee count
• Job title

The form also appears to add a statement that submission constitutes agreement to:

> “the processing of your personal information as described in our Privacy Policy.”

Risks include:

• The form may be interpreted as requiring consent to data processing, even where processing is based on contract necessity or legitimate interests rather than consent.
• The language does not explain purposes beyond the linked Privacy Policy.
• It is unclear which fields are mandatory and whether all collected information is necessary for a demo request.
• The form should provide a clear, accessible privacy notice at or before collection, rather than relying solely on a linked policy.

3. Privacy Policy reference made more prominent

The revised language adds a direct reference to Paylocity’s Privacy Policy and a “Privacy Center” navigation link. This improves notice visibility, but the legal effect depends on the contents of the linked policy and whether the form accurately summarizes the relevant processing.

4. No identified AI-training change

The diff contains no express language authorizing, restricting, or describing the use of customer or personal data to train AI models. It does not add terms addressing:

• Training or fine-tuning AI or machine-learning models
• Use of customer content or employee data for model development
• De-identification or aggregation for AI training
• Opt-out rights
• Human review of data for AI purposes
• Retention of data used in AI systems
• Sharing data with AI providers

Accordingly, the diff itself does not create a new apparent AI-training right. However, any such rights may exist elsewhere in the Privacy Policy, product terms, data-processing agreement, or applicable service-specific terms and should be reviewed separately.

5. Drafting and implementation concerns

The diff shows duplicated and apparently corrupted navigation/form text, including concatenated field labels and repeated content. The final webpage should be checked carefully to ensure that:

• Consent language is displayed clearly;
• Required and optional fields are accurately marked;
• Privacy links function correctly; and
• No unintended text is submitted or presented to users.

Structured Summary of Important Changes

1. New marketing communications language

The revised text adds:

> “I’d like to receive email updates from Paylocity.”

Legal significance and risks

• This introduces an express marketing opt-in for email updates.
• The wording appears embedded in the demo-request form and may be presented alongside required fields and privacy-policy acceptance. If the checkbox is preselected, unclear, or not separately actionable, consent may not be sufficiently informed or freely given—particularly under GDPR, UK GDPR, and similar laws.
• The language does not specify the types of communications, frequency, use of third-party email providers, or how to unsubscribe.
• Marketing consent should generally be separate from acceptance of data processing necessary to respond to a demo request. Combining these purposes may create consent and electronic-marketing compliance risks under laws such as CAN-SPAM, CASL, GDPR, and state privacy laws.

2. Expanded or reorganized website navigation

The revised content adds or relocates navigation categories, including:

• Partners
• Platform
• Elevate Solutions
• Compliance Resources
• Access Management
• Identity
• Company
• About Us
• Careers
• Investors
• Newsroom
• Culture
• “Serving You” and “Protecting …”

Legal significance and risks

• These changes appear primarily editorial and navigational rather than contractual.
• New product or service labels could create ambiguity if they are interpreted as representations, warranties, or commitments about service scope.
• Any linked privacy, terms, accessibility, or product pages should be reviewed to ensure they are accurate, current, and consistently incorporated into the website and customer agreements.

3. Privacy-policy acknowledgment retained and repositioned

The form continues to state:

> “By submitting this form, you agree to the processing of your personal information as described in our Privacy Policy.”

Legal significance and risks

• The revised version does not materially expand the stated processing purposes, but it continues to use submission of the form as acceptance of privacy-policy processing.
• A privacy policy is generally a notice, not a contract or blanket consent mechanism. The wording may be problematic where consent is legally required or where processing is not necessary to handle the request.
• The policy should clearly identify purposes, legal bases, retention, sharing, international transfers, individual rights, and whether submitted data may be used for analytics, product improvement, or AI training.

4. AI-model training

No express change concerning AI, machine learning, generative AI, model training, model improvement, or use of customer data for training appears in this diff.

Accordingly, the diff does not itself authorize or prohibit using form-submitted personal information or customer data to train AI models. Any such permission would need to be located in the Privacy Policy, terms, data-processing agreement, or product-specific terms.

No

No

No

No

No