Privacy notice

Last updated: 2026-09-14

Who is responsible for your information

Simon Kirby operates TrigPoint and is the controller of personal information described in this notice.

Simon Kirby

admin@trigpoint.uk

Information we collect

Account details, including your email address, login provider, public username and profile image.
Optional rider setup information you choose to save, such as mass, dimensions and suspension preferences.
Bikes, geometry, images, collections, ratings, comments and other material you create or upload.
Support messages, content reports and correspondence you send us.
Security and technical information such as session identifiers, IP address, browser details and request logs.

How and why we use it

To create and operate your account and provide the features you request (performance of our contract).
To authenticate users, prevent abuse, secure the service, diagnose faults and improve reliability (our legitimate interests and legal obligations).
To publish material you deliberately make public and enable community ratings and discussion (performance of our contract).
To answer enquiries, investigate reports and enforce our Terms (our legitimate interests and legal obligations).
To send account verification, password reset, security and service messages (performance of our contract and our legitimate interests).

We do not sell personal information or use it for behavioural advertising. TrigPoint's engineering outputs are not used to make automated decisions about people.

Who receives information

We use service providers for cloud hosting, database hosting, media storage and email delivery. Google receives information when you choose Google sign-in. Providers may process information outside the UK under the safeguards required by data-protection law. We may also disclose information when required by law or to protect users and the service.

Public content

Public bikes, profile information, ratings and comments can be seen and copied by other people. Do not publish personal information you do not want made public, or information about another person without permission.

How long we keep it

We generally keep account information and user content while your account is active. Security logs, support correspondence and records needed to establish or defend legal claims are kept only for as long as reasonably necessary for those purposes. Backup copies may remain for a limited period until overwritten.

Requesting account deletion disables the account and revokes its sessions immediately. In production, it remains recoverable for 30 days; registering and verifying the same email during that period restores it. After the deadline, TrigPoint permanently deletes the account and its associated private data. Material already promoted into the shared bike library may be retained as library content without continuing to identify you as its account holder.

Your rights

Depending on the circumstances, you may ask for access, correction, deletion, restriction or a portable copy of your information, or object to its use. Where processing relies on consent, you may withdraw it. Contact us to exercise a right. You may also complain to the UK Information Commissioner's Office at ico.org.uk.

Cookies and browser storage

TrigPoint uses the tp_session cookie to keep signed-in users authenticated for up to 30 days. During Google sign-in it uses short-lived tp_oauth_state, tp_oauth_pkce and tp_oauth_next cookies for security and to complete the sign-in flow. These are necessary to provide the requested account service.

The app also uses local or session browser storage to remember your theme, panel layout, viewer height and recent in-tab navigation state. These settings support features you choose and are not used for advertising or cross-site tracking. You can remove them using your browser controls, although doing so signs you out or resets preferences.

Contact and changes

Questions about privacy can be sent to admin@trigpoint.uk. We may update this notice as TrigPoint changes and will show the revision date here.