Docs
relyance.ai ↗
Browse docs

Vendors and Technologies

Updated November 4, 2026View as Markdown ↗

Overview

Not everything Relyance discovers as a "vendor" is a third party. Source code and integration scans also find the frameworks, libraries, and databases your own teams run - LangChain, PostgreSQL, a logging library. These are part of your own stack. They don't receive personal data from you as a separate company, so they shouldn't get processing activity records or be treated as sub-processors.

Mark as Technology lets you reclassify such a vendor as a technology. Relyance then stops creating processing activity records for it, hides the vendor-only sections of its drawer, and keeps your choice through every future scan. You can switch it back to a vendor at any time.

Why

  • Accurate ROPA. Your Records of Processing Activities list only the third parties that actually process personal data on your behalf.
  • Clean sub-processor lists. Your own stack no longer appears as a sub-processor on other records.
  • Less noise in vendor management. Your vendor list and reviews focus on real third parties.
  • Lasting decisions. The classification survives rescans, so you don't have to clean up the same components each time.

How it works

A vendor is either a vendor (the default) or a technology.

Vendor Technology
Processing activity records in Universal ROPA Created and kept up to date by scans Not created; existing records are hidden
Listed as a sub-processor on other records Yes No
Drawer header No tag Technology tag
Drawer Processing Activities and Sub Processors sections Shown Hidden
AI governance sections and the Attestations tab Shown, where licensed Hidden
Can be the subject of an assessment Yes No
Listed on Manage → Vendors Yes Yes

When you mark a vendor as a technology:

  1. Relyance records the classification on the vendor. Scans do not overwrite it.
  2. Processing activity records where the vendor is the processor, or the only sub-processor, are hidden.
  3. On records that have other sub-processors, the vendor is removed as a sub-processor and the rest of the record stays.
  4. An audit log entry is written for the change.

When you mark a technology as a vendor again:

  1. Relyance records the classification.
  2. Its processing activity records return after the next scan.
  3. An audit log entry is written for the change.

Some well-known frameworks and databases may already be marked as technologies by Relyance. Your own choice always takes precedence.

Mark one vendor as a technology

  1. Open the vendor's drawer. In Observe → Inventory, tick Vendors in the Type panel and click the vendor's row. Or click the vendor's name in Manage → Vendors.
  2. Click More actions (⋯) in the drawer header.
  3. Choose Mark as Technology.
  4. Read the confirmation and confirm. It explains that the vendor will be treated as a technology in your own stack, its processing activity records will be hidden, and it will be removed as a sub-processor from other records.

The drawer refreshes and shows a Technology tag next to the name.

To reverse it, open the drawer, click More actions, and choose Mark as Vendor.

Mark many vendors at once

  1. Go to Manage → Vendors.
  2. Select the vendors with the checkboxes in the grid.
  3. Click Bulk Edit in the bar at the bottom of the grid.
  4. In Select field to update, choose Technology.
  5. Choose Technology or Vendor.
  6. Review the preview. It shows each vendor's current and new classification.
  7. Click Apply Changes.

You can reclassify up to 500 vendors in one bulk edit. If some can't be updated, the result says how many and lists the reason for each in the Outcome column.

Note. Bulk Edit is on the Manage → Vendors page. On the Inventory, you reclassify one vendor at a time from its drawer.

Find technologies

On Manage → Vendors, click Add Filter and choose Technology:

  • Technologies only - lists the vendors marked as technologies.
  • Vendors only - lists everything that is not marked as a technology.

Save either as a view to come back to it. See Save views.

Audit trail

Every reclassification writes an audit log entry, whether you change one vendor from its drawer or many with Bulk Edit. The entry's event type is Reclassified as Technology or Vendor, and it is recorded under the Inventory service in the system audit log.

Who can do this

Mark as Technology, Mark as Vendor, and the Technology bulk edit field require permission to edit core inventory data. Without it, the menu items are disabled and Bulk Edit is not shown.

Configuration checklist

  • Vendors list reviewed for frameworks, libraries, and databases in your own stack
  • Each one marked as a technology from its drawer, or in batches with Bulk Edit
  • A Technologies only view saved for periodic review
  • Universal ROPA checked to confirm the expected records are hidden

FAQs and edge cases

Q: What counts as a technology?
A: A framework, library, or database that runs in your own stack - for example, an open-source library your code imports or a database you host. If a company receives or processes personal data on your behalf, it is a vendor, even if you reach it through an SDK.

Q: Will the next scan turn my technology back into a vendor?
A: No. Scans don't change the classification you set.

Q: Are processing activity records deleted when I mark a vendor as a technology?
A: They are hidden, not permanently deleted. If you mark the technology as a vendor again, its records return after the next scan.

Q: Why can't I create an assessment for this vendor?
A: Assessments apply to vendors only. If the vendor is marked as a technology, Relyance tells you so when you try to assess it. Mark it as a vendor from its drawer first.

Q: Can I mark a partner, customer, or service as a technology?
A: No. Mark as Technology is available for vendors only.

Q: I marked a vendor as a technology, but some of its processing activity records are still showing. What should I do?
A: The vendor keeps its new classification even if Relyance could not finish hiding its records, and Relyance shows an error when that happens. Contact Relyance support so the cleanup can be completed.