Who to contact
This policy covers the ELEV8 MTB journal and editorial workspace. Questions and requests can be sent to the ELEV8 editorial team at elev8mtb@gmail.com.
Readership information
Our own analytics count page loads on the homepage and published article pages. We store aggregate counts by date, page path, broad device group (mobile, tablet or desktop), and referring website domain. We do not store full referring URLs, IP addresses or persistent visitor identifiers in this analytics database. This counter does not set cookies.
We use these counts to understand readership and improve the journal. They count visits, including repeat loads, rather than identified individual readers.
Email you send us
If you email us, we receive your email address, message and any information or attachments you include. We use them to answer enquiries, investigate corrections, handle rights requests or discuss proposals. Our inbox is provided by Google’s Gmail service. Do not send passwords, payment details or unnecessary sensitive information.
Hosting and external services
The site uses AWS Lightsail hosting managed through RunCloud. Hosting and security providers may process technical request information, such as IP addresses and browser details, to deliver and protect the service. The private editorial workspace uses an essential, HttpOnly sign-in cookie. Session tokens are stored as hashes and expire after 24 hours. Login attempts are limited using hashed network addresses; these security records are separate from readership analytics.
Fonts are requested from Google Fonts. Some article images or other resources may load from third-party hosts, which receive technical information needed to serve them. Links and share buttons take you to external services with their own privacy policies.
Authorized editors use OpenAI-powered tools to prepare content. Editor prompts and selected article material are sent to OpenAI when an editor starts an agent task. Reading an article does not itself start an agent chat.
Optional Facebook panel
The homepage links to our Facebook community and offers an optional embedded page panel. It connects to Meta only after you choose to load it. Meta may receive your IP address, browser details and the page you are visiting, and may use cookies or associate the visit with your Facebook account. The embed is governed by Meta’s Privacy Policy. You can hide the panel to stop further requests from that embed; hiding it does not erase data or cookies already handled by Meta.
Challenge entries
When you submit a challenge entry, we store your Facebook name and profile link, selected answer, Facebook comment and share links, optional Instagram username, avatar choice, submission date, evidence notes and review status in our editorial database. We use them to verify eligibility, prevent duplicate entries, award approved tickets and reconcile the ongoing giveaway. Authorized reviewers can access these details. Only approved first names with last initials, avatars and weekly tickets are included in the public board; answers, profile links, comment/share evidence and review notes are not public.
When an authorized reviewer starts the Challenge Verifier, the selected participant’s name, social profile and evidence links, optional Instagram username, computed answer results, prior review checks and evidence notes are sent to OpenAI. The agent may search publicly accessible evidence. Its dated advisory report is stored privately for eligibility review. It does not access private accounts or make final ticket decisions.
Entry details are retained while needed to administer and reconcile the giveaway and resolve related disputes. You may request a correction or deletion at elev8mtb@gmail.com; deletion may prevent participation. Imported Week 1 records also retain their original social-verification flags and ticket history for reconciliation. Old administrator credentials and IP hashes are excluded from the migration.
Advertising: current status and future use
Google AdSense ads and Google Analytics are not currently enabled on this journal. The following describes advertising processing that may apply if Google ads are enabled; it does not mean advertising cookies are active today.
Third-party vendors, including Google, use cookies to serve ads based on users’ previous visits to this or other websites. Google’s advertising cookies allow it and its partners to serve ads based on visits across sites. Manage personalized advertising through Google My Ad Center and participating vendors through industry opt-out choices.
Before enabling advertising, we will update active vendor information and implement applicable consent controls. Read how Google uses advertising information and our Cookie policy.
Access, retention and your choices
Editorial records and aggregate analytics are available to authorized workspace users. Service providers process information needed to operate their services. We may also disclose information when legally required.
We retain aggregate statistics for readership reporting and correspondence while needed to handle enquiries and related records. There is currently no automatic deletion schedule for aggregate counts. Provider logs and account data follow the respective provider’s retention practices.
You can ask about information you provided, request correction or deletion, or raise an objection where applicable. Email us with enough context to locate the relevant correspondence. Aggregate counts without a visitor identifier generally cannot be traced to a specific reader.
Changes
We update this page when data practices change. The date above identifies the latest revision.