Cookie Policy for the Researcher Access Service
This policy outlines the cookies used in the Researcher Access Service.
About this policy
This Cookie Policy applies to:
- The Research Data Scotland enquiry form (rds-ras.researchdata.scot/enquiry-form)
- The Researcher Access Service where researchers manage their applications for data access (rds-my.researchdata.scot)
This service is built on Appian technology and operated by Research Data Scotland (RDS).
Like most organisations, Research Data Scotland (“RDS”) uses Cookies to capture information about our digital service users (referred to as "you").
Where cookies are not strictly necessary for the provision of our website and services, we will ask you to consent to our use of cookies when you first visit our service.
What are cookies?
A Cookie is a small file containing an identifier (a string of letters and numbers) that is sent by a web server to a web browser and is stored by the browser. The identifier is then sent back to the server each time the browser requests a page from the server.
Cookies may be either "persistent" cookies or "session" cookies: a persistent cookie will be stored by a web browser and will remain valid until its set expiry date, unless deleted by the user before the expiry date; a session cookie, on the other hand, will expire at the end of the user session, when the web browser is closed.
Cookies do not typically contain any information that personally identifies a user, but personal data that we store about you may be linked to the information stored in and obtained from cookies.
For more information on Cookies, see https://www.aboutcookies.org/ and https://www.allaboutcookies.org/.
Cookies that we use
The Researcher Access Service is built using the Appian technology platform. As such, only cookies categorised as 'Essential' are used in the service, outlined below:
- Appian uses browser cookies to maintain user sessions, to enable protections against threats such as cross-site request forgeries (CSRF), and, if configured, remember certain user choices between sessions.
- The cookies contain anonymized tokens and unique identifiers. No personally identifiable information (PII) is ever stored by Appian in a browser cookie.
- More information can be found in Appian's System Requirements documentation.
Essential Cookies
COOKIE | PURPOSE | EXPIRY |
---|---|---|
JSESSIONID | JSESSIONID is a cookie generated by Servlet containers and used for session management in J2EE web applications for HTTP protocol | Session |
_appianCsrfToken | This is an Anti-forgery token Cookie used to prevent cross-origin request forgery | Session |
Depending on Appian Version: _appianMultipartCsr _appianMultipartCsrfToken |
This is an Anti-forgery token Cookie used to prevent cross-origin request forgery for multi-part requests | Session |
Cookie consent
We will ask for your consent to place Cookies on your computer or device, except in certain circumstances where Cookies are essential for us to provide you with a service that you have requested (see the section on essential Cookies above for more information about how we use these types of Cookies).
Contact us
If you want to talk to us in relation to this Cookie Policy, please contact our Data Protection Officer:
Data Protection Officer
Research Data Scotland
Edinburgh Futures Institute
1 Lauriston Place
Edinburgh EH3 9EF
Last Updated 14 Nov 2024