What customer data do you hold?
In order to be able to provide our software and service, we need to maintain customer records.As part of our transparent approach to data privacy and security, this article outlines the limits to the data we record, specifically in relation to past and present customers.
We strive to ensure that we only collect and store the minimum amount of customer information necessary in order for us to effectively provide our services.
The data we hold
The following table provides a breakdown of exactly what customer information we hold, along with why, and how it's used:| Data | Example | Purpose | |
| The name of the customer's organization | My Company | This aids us in providing support to customers and their end users | |
| The industry sector of the customer's organization | Education (University) | This allows us to identify the industries in which our software is being used | |
| The country and region of the customer's base of operation | US, New York | This aids us in providing support to customers and their end users | |
| The name and email address of the current primary administrative contact for MIDAS-related correspondence at the customer's organization | Joe Bloggs ([email protected]) | Usually the person who originally purchased/subscribed to MIDAS, the Primary Contact is the person that we send important correspondence to relating to their MIDAS system. This typically includes subscription renewal reminders. | |
| The name and email address of the current primary billing contact for MIDAS-related correspondence at the customer's organization | Joe Bloggs ([email protected]) | In most cases, this is the same as the primary administrative contact. However, some customers specifically request that subscription renewal reminders are sent to a different person/department within their organization. | |
| The name and email address of any previous primary administrative contacts at the customer's organization | Jane Doe ([email protected]) | From time to time, responsibility from MIDAS can change within an organization (i.e. if a member of staff leave). In such instances, we update our records with a new primary administrative contact accordingly. We retain the name and email of the previous primary contact, as often these individuals move on to other organizations who in turn purchase/subscribe to MIDAS. | |
| The date the customer originally purchased or subscribed to MIDAS, and the initial value of that purchase | 23 May 2025 / $31 | If we receive a support request from an individual but are unable to ascertain their association with a customer's organization, we may use this information to assess the validate of the request. | |
| The number of users/venues/databases on your customer's current MIDAS license | 10 users / 20 venues / 1 database | We require this information in order to calculate subscription renewal costs, and to aids us in providing customer support. | |
| Any upgrades/addons purchased for the customer's MIDAS system, and the date they were purchased | Digital Signage / 23 May 2025 | We require this information in order to calculate subscription renewal costs, and to aids us in providing customer support. | |
| When the customer's subscription expired or is next due for renewal | 14 April 2026 | This allows us to send subscription renewal reminder, and assess whether a support request is considered a 'Priority Support' request. | |
| The customer's unique MIDAS ID (Product Key) | XXXX-XXXX-XXXX-XXXX | If we receive a support request from an individual but are unable to ascertain their association with a customer's organization, we may use this information to assess the validate of the request. | |
| The number of times a MIDAS system has been installed using the customer's unique MIDAS ID | 2 | This is used to prevent unauthorized use and abuse of product keys. | |
| The data center in which the customer's live MIDAS system resides | EU | This only applies to cloud-hosted customers. This aids us in providing customer support. | |
| The URL(s) at which MIDAS systems associated with the customer's Product Key are currently running | example.com/midas | This is used to prevent unauthorized use and abuse of product keys, and to aid us in providing customer support. | |
| The date of the most recent install of MIDAS using the customer's Product Key | 23 May 2025 | This aids us in providing customer support. | |
| The date of the last update check from the customer's MIDAS system | 23 May 2025 | This aids us in providing customer support. | |
| The most recent version of MIDAS available at time of initial purchase/subscription | 4.12 | This aids us in providing customer support. | |
| The current version of MIDAS the customer is running | 4.37 | This aids us in providing customer support. | |
| The latest version of MIDAS the customer is eligible to update to | 4.39 | This aids us in providing customer support. | |
| The currency the customer's purchase/renewals are in | USD | This is used to ensure correct billing. | |
| The postal address of the customer's business | PO Box 224 Cheadle SK8 4WB UNITED KIMGDOM | This is generally not collected/stored and is only done so in instances where the customer specifically requests a formal quotation or invoice. | |
| Miscellaneous notes | Migrated to a cloud-hosted 23/05/25 | We may retain generic additional information relating to a customer's particular MIDAS system, license status, payment status. | |
| The initial and most recently used payment processor for the customer's payments | PayPal / Stripe | We record the name only of the method through which the customer first/last made a payment. Possible values we store are limted to 'Stripe', 'PayPal', 'EFT' (Bank/Wire Transfer), 'Cheque', 'SO' (Standing Order). |
The data we don't hold
The above table outlines all the data we retain on our customers.We do not hold any other personally identifiable information.
Payments made through our website are handled by 3rd party payment processors (namely, Stripe and PayPal). We do not store - nor have access to - full transaction details (i.e. card numbers) of payments made via these payment processors.
How we store the data we hold
The customer data we do hold is stored in two separate databases, one on-server, and one off-server. Data is encrypted at rest in both these databases. Access is restricted to only those staff who require access in order to perform their duties. Access to the on-server database is IP limited to allow access from two IP addresses only. Access to both databases is password protected, with a different password for each. The off-server database is not stored on laptops, tablets, or other mobile devices, nor is it stored on any removable media (such as USB drives).Finally, we are registered with the UK Information Commissioner's Office (ICO), registration number ZA131245.
← Return to the Knowledge Base