FAQs
Timetable Usability
Is our timetable able to work with screen readers/how accessible is it?
Our timetable is compatible with screen readers such as the Apple iPhone screen reader.
Additional Features
Can you show the locations where sessions are taking place (e.g. main pool & teaching pool)?
Yes we can, but this requires some custom work on our side. Please get in touch with us so we can understand what your requirements and provide you with a quote for the work.
Can we show what exact locations (e.g. pitch 3) are represented in the facilities timetable rows?
We are unable to currently display this in the Facilities Timetable. However, there are workarounds such as including this information in the description, so please share your requirements with us and we will assist you in the best way possible.
Booking & Deep Links
Gladstone: Does member login take the user to the specific session in Gladstone Connect or Gladstone GO?
Yes, the button should function as a deep-link taking the user directly to their chosen session. For Gladstone Connect, if the user isn't logged in, it will take them to the Gladstone log-in page and then, once logged-in, it should take the user automatically to the relevant page within Gladstone. For Gladstone GO, the user will land on the specific page, ready to add to the basket, without needing to log-in first.
When using your Branded Checkout, can we use a different payment gateway other than Stripe?
Currently we are only using Stripe as the payment gateway, however, this may change in the future. Stripe is easy to setup and use, and most finance teams we have spoken to have found Stripe to be user friendly and secure.
Privacy, Data Security & Online Transactions
Your DPO may have questions to do with data privacy and security for the Live Timetables. Below are some helpful answers to common questions from a DPO.
Open Data Feeds
Your open data feed should contain no personal data as it is simply showing activity data such as time, price, location of an activity.
Your open data feed is published using a creative commons CCby4 licence. This means that it can be used by anyone for any purpose so long as they attribute it to your organisation.
There are no restrictions on storage of this data other than respecting your wishes for it to be deleted, which happens automatically. For example, when you cancel a session within your booking system, it will be removed from your open data feed and, therefore, we must remove it from our end, wholesale.
Data Storage Locations (only relevant for customers using our Branded Checkout)
Please refer to our subprocessor's list, privacy policy and security/compliance information.
All of our subprocessors are in the EU, and for those that aren’t, we ensure we have Standard Contractual Clauses signed and documented to ensure data compliance equivalence.
We regularly store data related to payments and transactions in the form of:
The logging procedures of product for reporting, de-bugging; and
Alerting internal team members (e.g. via Slack).
We are required to store this information because:
In the event of an issue or where we are required to manually cancel or issue refunds, we need a history of bookings and transactions;
In the event of a dispute, we need certain information about a booking; and
In accordance with UK laws, financial transaction history must be stored for a certain period of time.
Accessibility
As an organisation, we are required to meet certain standards for accessibility. Does your timetable cater for this?
Yes. The scripts for both the Sessions and Facilities Timetable code includes the information required for the iframes to have title attributes to cater for accessibility requirements. This will allow you to add alt-text to your timetables.
Last updated