Privacy Policy and Terms & Conditions

Here's the Privacy Policy and Terms & Conditions for TheGpsBlog.com.

Data and TheGpsBlog.com

TheGpsBlog.com maintains and uses the following data

• GPS track data (including latitude, longitude, time and sometimes elevation) for activities undertaken by the application developer, the application developer's wife and the application developer's dog (hereinafter known as Tye Hound). Occasionally, other people accompany us on those activities.

  Data item	Processing	Processing purpose
  Latitude / longitude	Stored	To be able to display a track (polyline) of latitude / longitude points on maps and charts
  Time	Stored	To be able to display where an activity tool place and how fast tje user was travelling
  Elevation	Stored	To be able to show elevation gain during cycling and dog walking activities

  Requesting data deletion The application developer is (in GDPR terms) both the "data controller" and "data processor". If the application developer's wife wants any GPS track removed she should talk to her husband. If Tye Hound wants any GPS track removed, he should provide proof to the application developer's wife (with references) that he can be considered a "data subject" (in GDPR terms). On provision of such proof, the application developer's wife will contact the "data controller" to ensure the offending track(s) are removed.

  Slightly more seriously, if any other person accompanying the application developer, the applications developer's wife or application developer's dog on an activity logged as a GPS track in TheGpsBlog.com has any privacy concerns, please contact the data controller and we'll agree whether the activity needs to be made private (there are several levels of privacy within TheGpsBlog.com) or deleted entirely.

• Photos taken during activities logged as GPS tracks on TheGpsBlog.com

  Data item	Processing	Processing purpose
  Photos	Generation and storage of multiple image sizes	To be able to display photos taken during and activity

  Requesting data deletion Photos that clearly show someone's face and/or identity tend to be marked as "private" on TheGpsBlog.com. However, this is not a hard and fast rule.

  Therefore, if anyone has a concern about the privacy of anyone shown in any photo on TheGpsBlog.com, please contact the data controller and we'll agree whether the photo needs to be made private (there are several levels of privacy within TheGpsBlog.com) or deleted entirely.

• Logon details when logging on to TheGpsBlog.com via Google or Facebook.

  Friends of the application developer, the application developer's wife or the application developer's dog are invited to log on to TheGpsBlog.com - after which the "data processor" may add permissions to their account such that activities and photos marked with privacy levels might be viewed. There is nothing to stop anyone else logging on to the application but unless and until the "data processor" adds permissions to that logon's account, then logging on gets a user no additional access.

  When you log on to TheGpsBlog.com, the application stores the following information (mostly provided by the Authorisation Server i.e. Google or Facebook):

  Data item	Processing	Processing purpose
  First name	Stored	To be able to display a friendly greeting when logging on (and to confirm your identity)
  Last name	Stored	To be able to display a friendly greeting when logging on (and to confirm your identity)
  Email address	Stored	To support communication to users if any change to TheGPsBlog.com will affect their usage of it
  The "provider key" on the authorisation server	Stored	To enable successful completion of logon processing
  Authorisation server used	Stored	To show the user whether they have logged on via Google or Facebook
  URL to user's avatar (if any)	Stored	This is no longer used in the application and will be removed in the future
  Previous and last logon dates	Stored	To help debug any problems when logging on
  User's access level	Set by the administrator and stored	So that a user who has been given elevated access rights can do more on TheGpsBlog.com
  Logon count	Calculated and stored	So that an adminstrator can see how many active users there are

  Requesting data deletion If you no longer want TheGpsBlog.com to store the above data for you, please contact the data controller and we'll delete your data.

  If you want a copy of the above data that TheGpsBlog.com holds for you, please send a subject access request to the data controller.

Cookies and TheGpsBlog.com

TheGpsBlog.com makes minimal use of cookies (and no use of local or session storage).

• A cookie named "JSESSIONID" maintains a logon token for the user during their current logon session. This is a "strictly necessary" functional cookie - logged in access to the application won't work without it
• The Cloudflare Content Delivery Network (CDN) sits in front of The GPS Blog and may set a "cf_clearance" cookie as a security token to prove that a visitor has successfully passed a bot mitigation challenge. Again, this is a "strictly necessary" cookie to allow the site to function properly
• TheGpsBlog.com makes no use of any tracking cookies.

Website analytics

TheGpsBlog.com uses a self-hosted instance of Umami to count page views and a small number of anonymous interactions (for example, opening a photo, downloading a GPX file or using a search form). Umami is a privacy-focused analytics tool:

• it sets no cookies and stores nothing in your browser;
• it collects no personal data - no names, email addresses, search text or locations are sent;
• the data collected (such as the page visited, referring site, browser type, screen size, language and country) is aggregated and is not used to identify or follow individual visitors, and is not shared with any third party.
• it is configured to respect Do Not Track settings in users' browsers (i.e. if set, we do not collect any data)

APIs and TheGpsBlog.com

TheGpsBlog.com makes use of several publicly available APIs. These include:

• The Google Maps API - please see the Google Privacy Policy
• The Google GeoCoding API - please see the Google Privacy Policy
• The Google Elevation API - please see the Google Privacy Policy

Terms and conditions

These terms and conditions (“Agreement”) set forth the general terms and conditions of your use of the thegpsblog.com website (“Website” or “Service”) and any of its related products and services (collectively, “Services”). This Agreement is legally binding between you (“User”, “you” or “your”) and this Website operator (“Operator”, “we”, “us” or “our”). If you are entering into this agreement on behalf of a business or other legal entity, you represent that you have the authority to bind such entity to this agreement, in which case the terms “User”, “you” or “your” shall refer to such entity. If you do not have such authority, or if you do not agree with the terms of this agreement, you must not accept this agreement and may not access and use the Website and Services. By accessing and using the Website and Services, you acknowledge that you have read, understood, and agree to be bound by the terms of this Agreement. You acknowledge that this Agreement is a contract between you and the Operator, even though it is electronic and is not physically signed by you, and it governs your use of the Website and Services.

Accounts and membership

If you create an account on the Website, you are responsible for maintaining the security of your account and you are fully responsible for all activities that occur under the account and any other actions taken in connection with it. We may, but have no obligation to, monitor and review new accounts before you may sign in and start using the Services. Providing false contact information of any kind may result in the termination of your account. You must immediately notify us of any unauthorized uses of your account or any other breaches of security. We will not be liable for any acts or omissions by you, including any damages of any kind incurred as a result of such acts or omissions. We may suspend, disable, or delete your account (or any part thereof) if we determine that you have violated any provision of this Agreement or that your conduct or content would tend to damage our reputation and goodwill. If we delete your account for the foregoing reasons, you may not re-register for our Services. We may block your email address and Internet protocol address to prevent further registration.

Links to other resources

Although the Website and Services may link to other resources (such as websites, mobile applications, etc.), we are not, directly or indirectly, implying any approval, association, sponsorship, endorsement, or affiliation with any linked resource, unless specifically stated herein. We are not responsible for examining or evaluating, and we do not warrant the offerings of, any businesses or individuals or the content of their resources. We do not assume any responsibility or liability for the actions, products, services, and content of any other third parties. You should carefully review the legal statements and other conditions of use of any resource which you access through a link on the Website. Your linking to any other off-site resources is at your own risk.

Limitation of liability

To the fullest extent permitted by applicable law, in no event will the Operator, its affiliates, directors, officers, employees, agents, suppliers or licensors be liable to any person for any indirect, incidental, special, punitive, cover or consequential damages (including, without limitation, damages for lost profits, revenue, sales, goodwill, use of content, impact on business, business interruption, loss of anticipated savings, loss of business opportunity) however caused, under any theory of liability, including, without limitation, contract, tort, warranty, breach of statutory duty, negligence or otherwise, even if the liable party has been advised as to the possibility of such damages or could have foreseen such damages. To the maximum extent permitted by applicable law, the aggregate liability of the Operator and its affiliates, officers, employees, agents, suppliers and licensors relating to the services will be limited to an amount greater of one pound or any amounts actually paid in cash by you to the Operator for the prior one month period prior to the first event or occurrence giving rise to such liability. The limitations and exclusions also apply if this remedy does not fully compensate you for any losses or fails of its essential purpose.

Changes and amendments

We reserve the right to modify this Agreement or its terms related to the Website and Services at any time at our discretion. When we do, we will revise the updated date at the bottom of this page. We may also provide notice to you in other ways at our discretion, such as through the contact information you have provided.

An updated version of this Agreement will be effective immediately upon the posting of the revised Agreement unless otherwise specified. Your continued use of the Website and Services after the effective date of the revised Agreement (or such other act specified at that time) will constitute your consent to those changes.

Acceptance of these terms

You acknowledge that you have read this Agreement and agree to all its terms and conditions. By accessing and using the Website and Services you agree to be bound by this Agreement. If you do not agree to abide by the terms of this Agreement, you are not authorized to access or use the Website and Services. This terms and conditions policy was created with the terms and conditions generator.

Contacting us

If you have any questions, concerns, or complaints regarding this Agreement, we encourage you to contact us using the contact page.

This document was last updated on September 17th, 2026