Log Files and Google Analytics
Like many other web sites, we make use of log files and Google Analytics. The information inside both includes IP addresses, geographic data, types of browsers, Internet Service Providers (ISP), date/time stamps, referring/exit pages, and number of clicks. We use these primarily to debug our codebase, improve our website's speed, and analyse broad trends as to inform management in making decisions about the business's future strategy.
As with most other websites using Paypal, Paypal automatically provides us with your real name and shipping address. We use this information for mandatory taxation and accounting purposes.
We let third party advertising companies track whenever you have visited Oxbridge Notes and its affiliated websites. We also use identifying information (such as your email address) to create custom advertising lists. Both of these sources of information are used to redisplay advertisements to you on other websites, such as Google, Facebook, Twitter, and websites affiliated with the aforementioned.
We use conversion tracking to track whenever you have done certain commercially valuable actions on our website, chiefly when you have made a purchase. This conversion information is later used by us to figure out what advertising campaigns were effective in triggering this sale. Conversion tracking is done in association with a third party advertising provider (e.g. Twitter, Facebook, Google), who also have access to the data.
We allow users to log in to our website with their Facebook account so as to speed up authentication and offer a smoother user experience. Facebook provides a pop-up box detailing exactly what information it will provide to Oxbridge Notes. At time of writing we store only your email address, which we use to send transactional messages and to allow you to log in without Facebook in future. You may opt out of Facebook Connect (and the giving of the above information) by choosing to log in with an email and password combination instead.
We save all enquires made via either via our main contact form or via the queries sent to individual authors. We do this for business analysis, monitoring author responsiveness to consumer requests, and policing transactions that are against our terms of services.
When there is a technical bug with a user account, our staff are empowered to log in with your account and view your account from that perspective. Your password is not leaked to our staff and is stored in a way impossible for them to read.
We use Google Analytics universal User-ID to associate engagement data from different devices and multiple sessions.