DESelect stores the following metadata:
- Some details about your Salesforce Marketing Cloud instance and the installed package, necessary
to authenticate users.
- Name, username, and email of every Salesforce Marketing Cloud user that uses DESelect. This
information is updated automatically every time a user opens DESelect.
- Metadata about the selections a user creates in DESelect.
DESelect does not store any of your data on its own databases.
When building a selection, DESelect pulls in the metadata of your data extensions. This means
DESelect only looks at the fields available in the data extensions, not the data. DESelect only needs to
know which fields exist in each data extension, and what the details of those fields are (eg. length of a
The only point in the application where DESelect accesses data in data extensions is when rendering
the preview. Here 20 records are queried from the target data extension after the query has run, so a
preview of the results can be shown to the user. This preview data is presented in the UI and not
stored on the DESelect servers.
The data access level for DESelect is limited to the permissions defined in section 1.2. Concretely, this
means DESelect can only query data extensions, query activities, and automations.
Furthermore, access is limited to the visibility of each user. A user cannot access more data in
DESelect than he has access to in Marketing Cloud directly. Within DESelect all actions are taken as a
user, so DESelect could never access data a user cannot access.
For every Marketing Cloud user that opens DESelect, a user record is created in the DESelect
database to identify the user, so a user can be an owner of a selection. This user record contains the username and name of each user.
Note: this paragraph is about SFMC users, not Subscribers or Contacts. DESelect does not copy any
Please sign in to leave a comment.