Check an edited privacy policy against a supplier contract

A supplier has edited its privacy policy, and you need to know whether the new wording still fits the contract. A small change to a deadline, permission, or responsibility can matter even when the document looks mostly the same.

First compare the old and edited policy to find the changes. Then check those changes against the supplier contract and any data processing or security addendum. Text Compare can help identify changed wording, but it cannot decide whether a change meets your legal or business requirements.

Compare the policy and contract

1. Open Text Compare and compare the previous privacy policy with the edited version. Use the complete text where possible, so a changed sentence is not read without the paragraph around it. If you need a refresher on comparing drafts, see how to compare policy texts without tracked changes.
2. Review the differences one section at a time. Note the heading, the old wording, the new wording, and any date or version label. Pay close attention to small changes in terms such as “may,” “will,” “only,” and “including.”
3. Find the matching obligations in the supplier contract, data processing agreement, security schedule, or order form. Compare topics such as data use, breach notification, subcontractors, retention, deletion, and international transfers.
4. Record each potential conflict with references to both documents. Mark it for the contract owner, privacy contact, or legal reviewer instead of resolving an unclear conflict by assumption.

Do not compare the full policy directly against the full contract and treat every difference as a conflict. The documents have different purposes and may use different wording. The useful comparison is between the policy's statements and the specific contract duties that cover the same subject.

What the differences mean

A sentence was added or removed

An addition may introduce a new purpose for using data, a new category of recipient, or a new exception. A deletion may remove a commitment that appeared in the earlier version. Check whether the contract already permits the new activity or still requires the removed promise. A policy change does not automatically amend a signed contract, but the contract may refer to the policy or set rules for updates, so check its wording.

A deadline or frequency changed

Compare time periods carefully. For example, a policy saying the supplier will notify you “without undue delay” may not match a contract requiring notice within 24 hours. A new retention period may also conflict with a contract that requires deletion within a stated number of days after the service ends. Record the exact language and ask the contract owner to assess the difference.

A permission or responsibility became broader

Words like “may,” “as needed,” and “for service improvement” can allow more discretion than a narrower contract clause. Check whether the policy now permits analytics, advertising, product development, or sharing with additional providers. Confirm that any permission is consistent with the contract's stated purpose and limits.

The documents appear to say different things

Check which document controls if terms conflict. The agreement may include an order of precedence, a section incorporating the policy by reference, or a rule for future policy updates. Do not assume that the newer document overrides the signed agreement, or that the contract always takes priority. The exact contract language and applicable law matter.

The comparison shows no text changes

That only means the versions you compared appear identical as text. It does not confirm that you selected the correct versions, checked every attachment, or reviewed whether the policy meets the contract. Verify the dates, document names, and supplier entity before treating the comparison as complete.

How to resolve a possible conflict

1. Confirm the documents are the right versions. Check the supplier name, effective date, policy version, contract date, and any referenced schedules. A clean comparison between the wrong versions can lead to a false result.
2. Read the full clause in context. Include its definitions, exceptions, and linked sections. A sentence may look broad on its own but be limited elsewhere in the document.
3. Check the contract's update and precedence language. Look for terms explaining how policies are incorporated, whether changes require notice or approval, and which document controls if they conflict.
4. Ask the supplier for a specific clarification. Quote the policy section and contract clause, then ask how the supplier will meet the contract requirement. Avoid asking only whether the documents are “consistent,” since that may not produce a clear commitment.
5. Request a written amendment if needed. If the supplier's explanation does not resolve the issue, have the authorized contract owner review an amendment or other formal change before approval or renewal.
6. Keep a dated review record. Save the compared versions, the clauses checked, the question raised, and the final decision in the approved contract record. Follow your organization's process for handling confidential supplier documents.

When to involve a specialist

Escalate the review when the change affects sensitive personal data, security incident reporting, data location, use of subcontractors, deletion after termination, or a regulatory obligation. Also seek legal or privacy review if the agreement incorporates the policy, allows unilateral updates, or does not clearly say which terms take priority. A text comparison can point to the wording that changed, but it cannot interpret enforceability or replace advice from a qualified reviewer.

Use the comparison as a way to prepare precise questions, not as approval by itself. For a detailed review, include the full relevant clauses and document dates, not just a screenshot of highlighted changes.