A glossary of terminology used throughout the Transcend platform. These terms are typically highlighted in the documentation, where you can view the definition by hovering over it like so: (data subject).

A connection between Transcend and another system, like Salesforce, Slack, or your database. These are also data silos, but they are connected to Transcend and have purpose-built functionality.
A functionality available in an integration, such as Silo Discovery, Structured Discovery, Unstructured Discovery, or DSR Automation.
A notification from our system to yours, such as a notification for a new erasure request that triggers an account deletion job in your application.
Any individual person whose data is being processed. Typically these are your users.
A preference is a choice made by a user, which specifies how a business can use that user's data or how they can communicate with them. Preferences dictate how the business can use your data in the future. In Transcend, this can refer to any privacy setting, communication preference, or consent preference.
A record of all the actions performed in Transcend. Actions can be performed by people (such as admin users and data subjects) or systems (such as Transcend, your SaaS tools, or your own systems).
Transcend's security gateway which, if self-hosted, keeps your corporate data and API keys end-to-end encrypted, and not seen by Transcend.
Used to add custom metadata to any object in Transcend. For example, you may have a custom field named "Product Line" to track which of your products a processing activity relates to in your data inventory.
A method of encrypting data from the moment it's created to the moment it's consumed. When you self-host Sombra, your corporate data and API keys are end-to-end encrypted, preventing Transcend's cloud from having access to your corporate data.
Why you are using this data. The purpose for collecting, storing, or analyzing a type of data.
A store of data within your organization. This is any location where data is logically stored, like a database, a SaaS tool, an S3 bucket... or even a filing cabinet with paper documents!
A data object inside a data silo. For example, the Lead object in Salesforce.
When Transcend automatically finds information about the data in your organization—such as a data silo, datapoints, data flows, or cookies.
When Transcend automatically labels information in your organization, such as labeling a discovered data silo as being a Snowflake data warehouse, labeling a datapoint as being a Biometric Identifier, or labeling a data flow as being sent to Facebook Ads for the purpose of Advertising.
A legal business entity in your organization, such as a subsidiary or brand.
If you have multiple Transcend organizations, one is the "parent" organization, and the others are "child" organizations. A parent organization has special permissions to manage child organizations and report on data from them.
When Transcend automatically labels a datapoint, it will also provide a confidence score. This is a measure of how certain Transcend is that the label is correct.
Also known as "DSR". Individual rights request, such as a request to access, delete, or correct personal data.
A request from an individual to obtain a copy of their personal data.
A type of data subject request, like "Download my data" or "Delete my data".
A unique identifier for a user, like an email address, phone number, or user ID. Transcend uses identifiers to precisely find a user's personal data across your data systems.
The process of adding more identifiers to a data subject request, based on a trusted mapping of identifiers in your data systems.
A phase in a DSR workflow performed before the request is fulfilled, to confirm that the request can be processed, and to add additional identifiers to a request.
A scheduled task that runs at a specific time or interval. In Transcend, your systems can run cron jobs that batch process pending data subject requests.
A JavaScript library that runs on your website to regulate data collection in accordance with a user's consent preferences.
Anonymous data collected from real web sessions, used to discover your data flows and cookies.
A user’s choice to allow or deny data collection for a particular purpose.
A URL that you are sending user data to, such as This is network traffic that is automatically discovered by Transcend.
The vendor or system behind the data flow. For example, a data flow to would have the service LinkedIn Ads. The URLs can be very obscure, so data flows are automatically classified by Transcend and labeled with their associated service.
A small piece of data stored on a user’s browser and attached to data flows, often used to track user behavior.
The pages on your website where a particular data flow or cookie was observed.
The number of users who encountered a particular data flow or cookie.
A geographic location, which can be used to set regionalized consent experiences and airgap.js configurations. A user's region is automatically detected by Transcend through a variety of privacy-preserving methods.
A legal regime, such as GDPR or CCPA, which can be used to set consent experiences and airgap.js configurations.
Your instance of Transcend's consent manager, which is configured to run on your website or mobile app. There are two separate bundles: Test and Production.
Software Development Kit. This is third-party code installed in your mobile app, which often is used to track user behavior and send data to third-party services.
Transparency and Consent Framework. A standard made by the International Advertising Bureau (IAB) for signaling a user's consent preferences to your advertising vendors.
A preference dataset stored in the Preference Database. These are often used to separate staging and production environments, or for multi-national organizations, to give users the ability make different choices across different brands.
Privacy policies, consent notices, or any other policies you wish to publish for your users.
Potential compliance issues found on your website.
A customizable questionnaire for assessing your data processing activities.
Large Language Model. A type of AI model that can understand and generate human language.
A set of rules that determine how data can flow into (or out of) a large language model (LLM).
An AI agent specialized in a particular task, like extracting vendor information from a contract.
The software tools that an AI assistant can use to complete a task.
A question asked of an AI chat bot.