Transcend

The Transcend Guide to Privacy

Welcome to the Transcend. You'll find comprehensive guides and documentation to help you start working with Transcend as quickly as possible, as well as support if you get stuck. Let's jump right in!

Get Started    

Terminology

Data Subject

This is a person whose data you control or process. In the context of GDPR, it's typically referring to European citizens. They do not include corporations, only natural persons.

One company may collect data on a number of different types of data subjects. Some examples may include:

  • Customers
  • Employees
  • Contractors
  • Job Applicants
  • B2B Contacts

Data Subject Request (DSR)

This is a request by the data subject to perform some action on their data. Some of the actions that Transcend has support for are the following:

Access Request (DSAR)

A request by the data subject to access, download, or export their personal data from your organization. Often called DSARs, or just SARs. We'll call them DSARs.

On consumer-facing interfaces, we'll call them Download Requests.

Erasure Request

A request by the data subject to erase or remove their personal data from your organization.

On consumer-facing interfaces, we'll call this Erase.

Portability Request

A request by the data subject to get a copy of their data and send it somewhere else on their behalf. This is the same as an access request, except another person or organization is the recipient of the response. In the context of GDPR, this must be machine-readable.

On consumer-facing interfaces, we'll call them Transfer Requests.

Rectification Request

A request by the data subject to update inaccurate information that you hold on them. This may be something as simple as change the address you have for me on record.

On consumer-facing interfaces, we'll call this Update Inaccuracies.

Restriction Request

A request by the data subject to restrict the processing of their personal data. An example of this may be due to a court order.

On consumer-facing interfaces, we'll call this Restrict Processing.

Objection Request

A request by the data subject to opt out of particular processings of their personal data. An example of this may be an objection to automated decision making.

On consumer-facing interfaces, we'll call this Object to Processing.

Contact Opt-Out Request

A request by the data subject to opt-out communications with your organization. An example of this is when someone unsubscribes from all marketing emails.

On consumer-facing interfaces, we'll call this Do Not Contact.

Tracking Opt-Out Request

A request by the data subject to opt-out of being tracked by your organization. An example of this is when someone wishes for their page views not to be tracked by your analytics services.

On consumer-facing interfaces, we'll call this Do Not Track.

Sale of Data Opt-Out Request

A request by the data subject to opt-out of the sale of their data to third parties.

On consumer-facing interfaces, we'll call this Do Not Sell My Personal Information.

Custom Opt-Out Request

A request by the data subject to opt-out of something other than contact, tracking, or sale.

On consumer-facing interfaces, we'll call this Custom Objection.

Custom Request

This is out catch all for making a request that is not listed already. Typically this will involve some manual coordination.

On consumer-facing interfaces, we'll call this Custom.

For other GDPR requests read this guide

Data Map

Transcend has the concept of a data map. Your data map represents all the data in your organization (including your DBs, SaaS, offline data). You can set up your data map on the Data Map Page.

Data Silos

A data map has a set of data silos. A silo might be one of your SaaS tools, a database, or even someone's offline filing cabinet.

Datapoints

A data silo contains a set of datapoints. (e.g. Resume, GPA, Education). In the context of a third party SaaS tool, one datapoint is usally one API endpoint.