Security considerations: how to manage access to your scorecard

Since Rise is used by businesses and enterprises, the data stored is often sensitive. We provide several levels of security.

Level 1 -  Physical and database security

We host all our servers at enterprise class cloud facilities provided by Amazon and SoftLayer.  We expect any third party services we use in providing the service to have a similar level of security.

Level 2 -  Web security

All web connections operate under ‘SSL’ – a cryptology technology much like a ‘phone scrambler’ which avoids intermediaries listening in to your web traffic. Server access is closely controlled to a group of named Rise.global (Leaderboarded Ltd) employees and contractors only.

Level 3 - Rise Scorecards


Each Rise scorecard is uniquely identified and all data associated with it (both unstructured score entries and structured release data) is categorised with that scorecard. When the scorecard is deleted then all data associated with that scorecard is also deleted.

Since Rise is a network model (we operate as a trusted broker between entities - users and administrators) user data (their account details and authorisations) is owned by the user not the administrator.  This means that as well as administrators being able to delete data on a scorecard, users can also delete data that pertains to them (their historic tweets for example) and choose to permanently opt out of any scorecard.

Currently only users and administrators have access to raw data entries - spectators (whether logged in or anonymous) may not browse raw score entries.  Using a specialist "Rise scorecard connector" administrators can give other named Rise scorecard access to use unstructured data entries within their own scorecard scoring algorithms.

Level 4 – Board privacy levels

You can set the privacy level of your Rise board as follows:
  • Public – available for all (including not logged-in  rise.global users) to view and find via the public gallery
  • Unlisted – available for anyone (including not logged-in rise.global users) to view who has the scorecard url and also to users (i.e. someone listed on the scorecard) who would see it when logged into their rise.global account
  • Private – available for users and scorecard administrators only, when logged into rise.global
  • Private: score only – as Private but here only administrators can see the entire scorecard, users just see their own individual scores
  • Stealth unlisted – as unlisted but not available to users
  • Stealth – only authorised administrators of the scorecard have access

Level 5 – Scorecard Administrator roles

There are several access control roles for each scorecard. These allow you to control access for administrators to particular features. Understanding the roles and what they allow helps explain the work required in running a successful leaderboard project.

The scorecard administrator roles are listed in this article: Rise Board Scorecard Administrator Roles

Level 6 - Data Housekeeping

In order to minimise the length of time raw data is kept on the Rise servers Rise operates a 92 day data storage policy (one quarter worth of data). Raw data (API data, social data such as Tweets, Yammer content) that is required to produce scores - is deleted on a rolling 92 day process unless explicitly required to be kept by the scorecard's score algorithm as set by the scorecard administrator.

Additionally a full manual delete of data entries for any metric is possible by the scorecard administrator.

Feedback and Knowledge Base