Subprocessor Monitoring: How to Set Up Vendor List Tracking

Subprocessor Monitoring: How to Set Up Vendor List Tracking

A vendor inventory might list sixty SaaS services while the privacy team's monitoring folder contains only twelve subprocessor pages. Some lists are inside trust portals, some are attached to a DPA, and some use different pages for different products. Before the team can review changes consistently, it needs to establish which source covers each service it actually uses.

Subprocessor monitoring starts with that coverage problem. A useful setup connects a vendor, the applicable product and region, the current source, and a responsible reviewer. It also records the gaps: a page that is inaccessible, an incomplete list, or a vendor that only supplies changes by email.

This guide focuses on building and maintaining that monitoring setup. Once an alert arrives, the companion guide explains how to review a subprocessor change against your vendor DPA.

What is a subprocessor, and why does it matter?

A subprocessor is another organization a processor engages to process personal data on a controller's behalf. Its role matters when assessing the processing chain for a service you use. Start by identifying the applicable service and data flows, then connect its published list to your vendor records and signed agreement.

For example, a CRM provider might engage a hosting company or a support service to process customer data. The relevant question is whether a listed entity handles data for the product and configuration you use, rather than whether the vendor's broad corporate list names that entity.

Article 28(2) of the GDPR requires prior specific or general written authorization before a processor engages another processor. Under general authorization, intended additions or replacements must be communicated so the controller can object. The article does not set a universal 30-day objection period. Your privacy or legal owner should identify the notice terms that apply to your agreement.

For the underlying terminology, see what a subprocessor is. This setup guide concentrates on source coverage and alert delivery.

Why monitor pages alongside vendor notifications?

Page monitoring provides an additional source of change information and a comparison against previously captured content. Keep the vendor's required notice channel active too. A page edit, a delivered notice, and your team's detection may have different dates; the monitor does not decide which event starts a contractual response period.

Check the existing notice route

Before adding another alert, verify the route you already have:

  • Does the vendor send notices to a shared address with a current owner?
  • Does that address still reach the privacy team after staffing changes?
  • Does a trust portal require a separate subscription?
  • Does the signed agreement identify a publication page or another notice channel?
  • Who checks notices when the primary reviewer is away?

An email saying "our list has changed" may not include the changed rows. A captured comparison can help the reviewer locate the addition, removal, or edited processing location. Conversely, the email may include an intended effective date that the public list does not show. Keep both records when they are relevant.

Treat gaps as explicit work

A monitor that captures a login screen is not coverage of the list behind it. A privacy-policy page that names broad categories of recipients is not necessarily a substitute for a product-specific subprocessor list. Record these limitations and request the source you need from the vendor.

Which vendor pages should you monitor?

Start with the vendor source referenced by your signed agreement or supplied by its privacy team. That may be a dedicated list, a DPA appendix, or a document inside a trust centre. Confirm its product and regional scope before adding supporting pages, and record any uncertainty about whether the list covers your service.

Vendor Subprocessor Pages

Most SaaS vendors publish their subprocessor list on a dedicated page. The URL typically follows patterns like:

  • /subprocessors
  • /legal/subprocessors
  • /trust/subprocessors
  • /privacy/subprocessors
  • /legal/data-processing

These pages list each subprocessor by name, purpose, and often location. When the vendor adds or removes a subprocessor, this page changes.

Verify the current address directly with each vendor. A familiar URL pattern is a starting point for discovery, not proof that the page is current or complete.

Data Processing Agreement Pages

Some vendors embed subprocessor information within their DPA page or a data processing appendix rather than a standalone subprocessor page. If the vendor does not maintain a separate subprocessor list, monitor the DPA page the same way you would track any other legal and policy page changes.

Trust and Security Pages

Vendors increasingly maintain trust centers or security pages that centralize compliance information. Subprocessor lists may live within these trust centers. Monitor the specific subprocessor section URL if available, or the trust center landing page if subprocessor information is embedded.

Privacy Policy Pages

A small number of vendors include subprocessor-relevant information in their privacy policy rather than a dedicated page. This is less common for enterprise SaaS but occurs with smaller vendors. For these vendors, monitoring privacy policy changes catches subprocessor-related updates alongside other privacy changes.

How do you set up subprocessor list monitoring in PageCrawl?

Build a source inventory, add the applicable list URLs, and inspect each initial capture before enabling routine review. Choose a schedule that leaves time for your internal process, then verify alert delivery to an owner and deputy. Keep unresolved source or capture problems visible instead of counting them as completed coverage.

PageCrawl change diff for GitHub Subprocessors, highlighting the added and removed text

Step 1: Inventory Your Vendors

Start with a list of every SaaS vendor that processes personal data on your behalf. Your vendor management system, DPA register, or procurement records should have this list. If no central register exists, this exercise is valuable in itself.

For each vendor, find its subprocessor page URL. Check the legal, trust, or privacy sections and the references in the signed DPA. Add these fields to your existing register:

Field Why it belongs in the setup record
Vendor and service Distinguishes the product you use from the vendor's wider catalogue
Applicable region or tenant Prevents relying on a list for another service configuration
List URL and access requirements Identifies the source and any login dependency
Signed DPA reference Gives reviewers the applicable agreement, not only current website terms
Notice channel Preserves the vendor's agreed notification route
Owner and deputy Identifies who handles changes and coverage failures
Capture status Separates verified coverage from incomplete or inaccessible sources

Step 2: Add Monitors

Add each vendor's subprocessor page URL to PageCrawl and choose a text capture that includes the complete relevant list.

  • Selected content: A list or table region can exclude unrelated navigation while retaining entity names, processing purposes, countries, and any effective dates.
  • Reader or Content only: These can reduce surrounding page content, but inspect the extracted result. A cleaner-looking capture is not useful if it omits table columns or notes.
  • Fullpage text: Use this when the relevant material spans several regions or the list is the main page content. Text comparison does not by itself establish that every visual or structural detail is unchanged.

Check rows near the top and bottom, column headings, footnotes, pagination, and any product filters. For a gated source, configure the authorized login and confirm the saved capture shows the list rather than a sign-in prompt.

Choose cadence from the response process and check allowance. Five monitors checked daily use about 150 scheduled checks in a 30-day month. A daily schedule is not a guarantee of detection within 24 hours: failed checks, unavailable pages, and notification delivery can add time. Use the check-frequency planning guidance when planning a larger portfolio.

Step 3: Organize Monitors

Create a folder structure that supports your review workflow:

Subprocessor Monitoring/
  Critical Vendors/
    CRM (Salesforce)
    Cloud Infrastructure (AWS)
    Email Platform (SendGrid)
    Analytics (Mixpanel)
  Standard Vendors/
    Project Management (Asana)
    Documentation (Notion)
    Support (Zendesk)
    HR Platform (BambooHR)
  Low-Risk Vendors/
    Design Tools (Figma)
    Scheduling (Calendly)

Categorize vendors by the sensitivity of data they process and the volume of personal data involved. Critical vendors process large volumes of sensitive personal data. Standard vendors process personal data in normal business operations. Low-risk vendors process minimal personal data. If several teams own different slices of the portfolio, labels, nested folders, and workspaces keep each group's alerts separate.

Use these categories as a starting point for routing. Confirm urgency against the actual service risk and applicable agreement rather than assuming every vendor in a folder has the same response window.

Step 4: Configure Notifications

Route each monitor to a channel the responsible team actively reviews. Record a backup route for absence or delivery problems. A critical vendor may need a direct notification; lower-priority changes may fit a scheduled review only if that schedule leaves enough time for the applicable response process.

Scheduled reports can group changes for periodic review. They should complement any time-sensitive alert route. A weekly digest is a poor fit when a notice must be assessed sooner.

For organizations using webhook automation, a receiving workflow can create an assessment ticket from a change notification. Configure and test that receiving workflow separately; selecting a webhook destination does not by itself define owners, deadlines, or ticket fields.

How do you expand coverage across more vendors?

Expand from verified sources and repeatable setup records. Prioritize vendors using documented service risk and contractual requirements, then calculate the checks required by the proposed schedule. Bulk creation can reduce setup effort, but each new monitor still needs a capture review, an owner, and a tested notification route.

Prioritization

You do not need to monitor every vendor with the same intensity. Prioritize based on:

Data sensitivity: Vendors processing financial data, health data, or other sensitive categories deserve more attention than vendors processing only business contact information.

Data volume: A CRM holding millions of customer records matters more than a scheduling tool with a few hundred user accounts.

Contractual requirements: Some customer contracts specifically require you to monitor certain vendor categories. These are non-negotiable priorities.

Regulatory context: Vendors in regulated industries (healthcare, life sciences, financial services) or processing data subject to specific regulations (GDPR, CCPA) require closer monitoring.

Document why each vendor receives its chosen schedule and review route. Do not label an unmonitored vendor covered merely because it has a lower risk rating. If manual review is the chosen control, record its owner, cadence, and limitations separately.

Bulk Setup

For organizations monitoring many vendors, PageCrawl's API allows bulk creation of monitors. Prepare a list of vendor subprocessor URLs in a spreadsheet, then use the API to create monitors programmatically. This avoids the tedium of adding 50+ monitors individually through the web interface.

See the API dashboard guide for details on programmatic monitor management.

Handling Vendors Without Subprocessor Pages

Some vendors, particularly smaller SaaS companies, do not maintain a public subprocessor page. For these vendors:

  • Request a subprocessor list directly and ask for their update notification process
  • Monitor their DPA page, privacy policy, or trust page as a proxy
  • Include subprocessor review as a standing item in vendor review meetings
  • Consider whether the vendor's lack of subprocessor transparency is itself a compliance concern

What should the setup hand over when a change arrives?

Hand the reviewer the changed source, captured comparison, detection time, applicable service, and a link to the signed agreement. That gives them enough context to begin assessment without searching the vendor inventory again. Keep the monitor's detection timestamp distinct from the notice or effective date the vendor has provided.

Handover item Example content
Source and scope Vendor list for the product and region in use
Captured change Added entity, removed entity, or edited purpose/location
Timing Previous capture time, detection time, and any separate notice date
Review context Agreement reference, owner, deputy, and ticket or review record

The next step is a contract-aware assessment, not an automatic objection or approval. The subprocessor change review workflow covers applicability, deadline verification, evidence, and recorded decisions.

For team visibility, use folders and labels to organize monitored vendors and the review board to track detected changes awaiting review. Maintain contractual deadlines and individual assignments in the team's agreed review register or ticketing system. Do not assume a monitoring folder is a complete vendor-risk register.

If you connect a GRC platform, test the mapping from the incoming alert to the destination record. Verify the URL, captured change, event time, and source identifiers survive the handoff, and that a failed integration leaves a visible follow-up task.

How do you maintain verified coverage over time?

Review coverage when vendors, services, contracts, or team ownership change, and set a recurring check of the inventory and monitor health. Inspect failures and unexpectedly empty captures promptly. The useful measure is how many applicable sources are successfully captured and reviewed, rather than how many URLs appear in a folder.

Quarterly Vendor Inventory Review

Review your vendor list quarterly:

  • Have new vendors been onboarded? Add their subprocessor pages to monitoring.
  • Have vendors been offboarded? Remove or deactivate their monitors.
  • Have vendors changed their subprocessor page URLs? Update monitors accordingly.
  • Are there vendors without subprocessor monitoring that should be covered?

Annual DPA Review

Review DPAs annually alongside monitoring. Confirm that:

  • Notification clauses are current and address your monitoring approach
  • Objection periods and processes are understood
  • Contact information for privacy and legal teams is current
  • The DPA reflects the current data processing scope

Monitoring System Health

Periodically verify that monitoring is functioning correctly:

  • Are alerts being received by the right people?
  • Have any monitors failed (page errors, URL changes)?
  • Is the notification routing still correct after team changes?
  • Are assessments being completed in response to alerts?

How do you start subprocessor monitoring this week?

Choose a small set of vendors whose sources and owners you can verify, configure their monitors, and inspect the captured lists before expanding. Confirm the notice route, test alert delivery, and record any gaps. A complete setup includes a review handoff; adding URLs alone does not establish a working monitoring process.

Five daily monitors require about 150 scheduled checks over a 30-day month, before initial, manual, or other checks. Compare that total with your available allowance on the current pricing page. For business portfolios that need managed connection options, assess Enterprise or Ultimate against the actual sources and access requirements.

Finish the first batch with a short coverage review:

  1. Each source covers the intended service and region.
  2. Captures include the relevant list, columns, and notes.
  3. The monitor has a practical schedule and enough check budget.
  4. The owner and deputy can receive and open a notification.
  5. The signed agreement and vendor notice channel are recorded.
  6. Inaccessible or incomplete sources have an explicit follow-up.

Once those checks pass, expand using the same record and verification process. For evidence beyond the saved comparison, the website archiving guide explains capture options; for the response itself, use the subprocessor change review workflow.

Originally published: 24 February, 2026 | Last updated: 10 November, 2026

Get Started with PageCrawl.io

Start monitoring website changes in under 60 seconds. Join thousands of users who never miss important updates. No credit card required.

Go to dashboard