Digit Cookie Notice

  1. INTRODUCTION
    1. Privacy is important to DGIT Technologies CC with registration number: 2005/126861/23 (“Digit”). This cookie notice applies to all websites that belong to Digit which are applicable to South Africa (websites).
    2. Please refer to Digit merchant privacy notice for details on the way Digit uses personal information. Digit merchant privacy notice is available www.digit.co.za.
  2. WHAT IS A COOKIE?
    1. A cookie is a small piece of data that is sent (usually in the form of a text file) from a website to the user’s device, such as a computer, smartphone or tablet. The purpose of a cookie is to provide a reliable mechanism to “remember” user behaviour (keeping track of previous actions), e.g. remembering the contents of an online shopping cart and actions the user performed whilst browsing, when not signed up or logged into their online account.
    2. Digit does not necessarily know the identity of the user of the device but does see the behaviour recorded on the device. Multiple users of the same device would not necessarily be distinguishable from one another. Cookies could however be used to identify the device and if the device is linked to a specific user, the user would also be identifiable.
  3. WHICH COOKIES CAN BE FOUND ON DIGIT WEBSITES?
    1. First- and third-party cookies refer to the website or domain using the cookie. Cookies are set by the website that the user is visiting.
    2. First-party cookies are directly stored by the website (or domain) visited by a user. These cookies allow website owners to collect analytics, data, remember language settings or perform other useful functions that provide a good user experience.
    3. Third-party cookies are created by domains separate/different from the website (or domain) that the user is visiting. These cookies are usually used for online advertising, cross-site tracking and are accessible on any website that loads the third party’s server code, e.g. when a user visits a site and clicks a “like” button, this could be stored in a cookie and, upon visiting the third-party site, the cookie will be used to action the request.
    4. For example, a user browses online for a specific product, finds an advert of interest, clicks the advert and thereafter closes their browser. Several hours later, the user notices advertising of the same product that they were browsing for earlier.
    5. When a user visits Digit’s website, Digit may include any of the cookies listed in the table below. The table explains what the cookies are used for and the time period for which the cookie could remain valid. Where cookies are only valid for a single session, the cookie will be erased when the user closes their browser. Where cookies persist, the cookie will be stored by the user’s browser until deleted by the user.
  4. WHEN WILL THE GROUP USE COOKIES?
    1. Digit will only process cookies which identify users for lawful purposes:
      1. if a user has consented thereto;
      2. if a person legally authorised by the user, the law or a court, has consented thereto on the user’s behalf;
      3. if it is necessary to conclude or perform under a contract that Digit has with the user;
      4. if the law requires or permits it;
      5. if it is required to protect or pursue the user’s, Digit’s or a third party’s legitimate interest (e.g. for fraud prevention);
      6. if the user is a child and a competent person (like a parent) has consented thereto on the child’s behalf.
    2. Digit may use cookies for reasons including but not limited to:
      1. fraud, financial crime and other crime prevention, detection or reporting;
      2. managing and improving security for Digit and users (for example to prevent fraudulent use of login details);
      3. various analytical reasons, e.g. how Digit websites are used so that improvements can be made;
      4. marketing and advertising, for example to decide which solutions users may be interested in and to customise marketing on various applications and websites;
      5. recognition of users of Digit websites, or devices which return to Digit websites.
  5. WHAT HAPPENS IS A USER DOES NOT WANT COOKIES?
    1. All browsers allow users to refuse to accept cookies and to remove current cookies. The methods for doing so vary between different browsers and versions. Users can block cookies on Digit websites, if desired.
    2. Blocking certain cookies may have a negative impact upon the usability of Digit websites. For example, Digit requires cookies to allow users to log in. By removing first-party cookies, a user’s solution experience may be affected.
  6. FURTHER INFORMATION ABOUT COOKIES
    1. Users’ browsers store cookies and Digit websites cannot access any data on a user’s device.
    2. As cookies are stored in text files, they cannot be used to distribute viruses to a device.
    3. On a single device with multiple users, the experience of Digit websites would be customised based on the behaviour of all users using the device and not just an individual user.
    4. If users disable cookies, previous cookies collected will not be deleted however, this will prevent the creation of new cookies. Expired cookies will be removed automatically
Origin UseServiceDuration 
First-party cookiesBrowser/device identificationEnable Digit to identify the device/browser.Persist beyond a single session. 
First-party cookiesAuthenticationUpon logging into a web server, a cookie will be returned that identifies that the user has been successfully logged in.Only valid for the single session.
First- and third-party cookiesAnalyticsTo collect information about how visitors use Digit websites. This can provide Digit with insight on website performance and metrics.Persist beyond a single session.
Third-party cookiesMarketing and otherUsed for tracking and online advertising purposes.Persist beyond a single session.
OptionDescription
HTTPSMakes a cookie secure by ensuring it is only sent over HTTPS protocol. This prevents attackers from secretly extracting it.
Same-site cookie Makes the cookie secure by limiting the sites to which the cookie is allowed to be sent.
ExpirySets the duration a cookie will last for before it expires.
SecureMakes a cookie secure by ensuring it is only sent over a securely encrypted channel.
PathHelps to protect a cookie by restricting the location where it is allowed to be sent.