Privacy Policy

Last updated: 5 November 2026 Effective: 5 November 2026 Version: 2026-11-05

This Privacy Policy explains how Hell’s Highway (“we”, “us”, “G-3 Ops”) collects, uses, and protects personal data in connection with the G-3 Operations tour-planning and tour-execution service (the “Service”), available at g3ops.com and as a web/mobile application.

We are established in the Netherlands and process personal data in accordance with the EU General Data Protection Regulation (GDPR) and Dutch data-protection law.

1. Who we are

The data controller for the personal data described in Section 3.1 is:

• Hell’s Highway (eenmanszaak)
• Chamber of Commerce (KvK): 73442372
• VAT (BTW): NL001447641B53
• Registered address: Geerbosch 10a 5461 XJ Veghel The Netherlands
• Contact for privacy matters: info@g3ops.com

We are not required to appoint a Data Protection Officer, but the contact above handles all data-protection requests.

2. Controller and processor — an important distinction

The Service handles two kinds of personal data with two different roles:

• Account and billing data (who you are, how you pay). For this, we are the controller and this Policy applies in full.
• Tour content you enter (tour plans, stops, notes, and any names or details of tour managers, drivers, clients, or third parties you add). For this, you — the account owner — are the controller and we act as your processor, handling that data only on your instructions to provide the Service.

Where we act as your processor, our handling is governed by our Data Processing Agreement (see Section 12), and you are responsible for having a lawful basis to enter that data and for informing the people it concerns.

3. What data we collect and why

3.1 Data we collect as controller

Account data (guides / account owners). When you sign in with Google, we receive your name, email address, and Google account identifier. When you sign in with an emailed link, we receive and store your email address, and the link is delivered through our email delivery provider (Section 6). We use this to create and secure your account and to identify you within the Service.

Tour manager data. A guide adds a tour manager by name. The tour manager signs in with a personal link and a PIN that the guide hands to them; we hold the name, a hash of the PIN (never the PIN itself), and when the link was last used. No email address is needed. Tour managers invited before September 2026 were invited by email address, which we keep for as long as they have access, to authenticate them.

Team member invitations. When an account owner invites a colleague to the team, they enter the colleague’s email address. We email an invitation that shows the inviter’s name and team name, and keep the address, team name and role until the invitation expires, after seven days.

Billing data. Payments are processed by our payment provider. We do not receive or store your full card number. We store the customer identifier our payment provider assigns to you, subscription tier, subscription status, billing interval, and related subscription details (such as subscription and billing-period identifiers) so we can manage your plan and entitlements. Our payment provider also holds your billing email address and emails your invoices to you directly.

Technical and log data. Our infrastructure providers automatically process technical data such as IP address, device and browser information, and access logs, for security, abuse prevention, and reliability.

Driver PIN log. When someone enters a PIN on a driver link, we record the time, the result (PIN accepted, wrong PIN, link locked after too many wrong PINs, link expired, or no PIN set), the name of the link, a shortened IP address (cut to the network it came from: the first three parts of an IPv4 address, the first three groups of an IPv6 address), and the browser and operating system (for example “Safari on iOS”). We never record the PIN, the link itself, or the full IP address. Repeated attempts while a link is temporarily locked, malformed requests, links that do not exist, and requests blocked as abuse are not recorded individually. We keep this record to protect driver links against misuse; the account owner and the account’s administrators can see it for the account’s tours.

3.2 Data we handle as processor

Tour content. Anything you enter into a tour — including any personal data about tour managers, drivers, clients, or others — is stored and processed on your behalf to provide the Service. We do not use it for our own purposes.

3.3 Drivers

Drivers view a tour through a temporary read-only shared link, which is protected by a PIN, and are not required to create an account. We do not collect a driver’s account data. When a driver enters the PIN, the entry is recorded in the driver PIN log described in Section 3.1. Any personal data about a driver that appears in a tour is tour content you control (Section 3.2).

4. Legal bases for processing

We rely on the following GDPR Article 6 legal bases for the data we control:

• Performance of a contract — to create your account, provide the Service, and manage your subscription.
• Legitimate interests — to keep the Service secure, prevent abuse, maintain reliability, and communicate essential service information. We balance these against your rights.
• Legal obligation — to retain billing and administrative records as required by Dutch tax law.
• Consent — only where we specifically ask for it; you may withdraw consent at any time.

5. How we use personal data

We use personal data to provide, secure, and support the Service; to authenticate users; to process subscriptions and send service and billing communications; to comply with legal obligations; and to detect and prevent abuse or misuse. We do not sell personal data and do not use it for advertising.

6. Service providers (subprocessors) and sharing

We share personal data only with the providers we need to run the Service. Each is bound by a data-processing agreement and appropriate safeguards.

The providers are named in Annex III of our Data Processing Agreement.

The app and this website serve their typefaces from our own hosting, so loading a page sends no request to a third-party font service.

We may also disclose data where legally required, or to protect our rights, safety, or property.

7. International transfers

Tour content and account details are stored in the EU. Sign-in is handled by our hosting provider, which may process sign-in records outside the EEA. Some providers are US-based; where personal data is transferred outside the EEA, we rely on the EU-US Data Privacy Framework and/or the European Commission’s Standard Contractual Clauses.

8. Retention

We keep personal data only as long as we need it for the purposes in this Policy, then delete or anonymise it. Our retention periods are:

• Account and profile data — retained while your account is in use. An account with no active paid subscription and no sign-in by its owner for 24 months is treated as inactive and may be deleted, after a warning sent to its email address at least 30 days beforehand; signing in keeps the account. When you delete your account (Section 9), access is cut off immediately and your data is irreversibly erased after a 30-day recovery window. If you do not restore the account within that window, the erasure is permanent.
• Tour content — retained while your account holds it, and erased with the account if the account is deleted as inactive. You can delete individual tours at any time, and all tour content is erased together with your account (subject to the same 30-day window). Where we act as processor, return and deletion also follow our DPA.
• Billing and administrative records — retained for 7 years as required by Dutch tax law. Your customer record with our payment provider and your invoices are kept even after your account is erased: on deletion your subscription is cancelled, but these billing records are retained to meet this legal obligation.
• Backups — database backups are retained for up to 30 days, so erased data clears from backups within about a month.
• Operational logs — request, error and security logs (which may contain identifiers such as user, tenant or tour IDs) are retained for 30 days. A limited subset of security/audit logs maintained by our cloud infrastructure provider is retained for up to 400 days and cannot be shortened.
• Driver PIN log — each entry is deleted automatically about 90 days after the PIN was entered. Entries stay for that period even if the tour is deleted sooner, and are erased together with your account if you delete it.
• Transactional email data — records held by our email delivery provider, such as recipient address and message subject, are retained for up to 30 days.
• Team invitations (email address, team name, role) — kept until the invitation expires, after seven days.
• Proof-of-erasure record — after your account is erased we keep a minimal record consisting only of an internal account identifier and the date of erasure, to evidence that the deletion took place. It contains no name, email, tour, or billing data.

9. Your rights

Under the GDPR you have the right to access, rectify, erase, or restrict processing of your personal data; to data portability; to object to processing based on legitimate interests; and to withdraw consent. To exercise any of these, contact info@g3ops.com.

If your request concerns tour content where we act as a processor, we will refer you to the relevant account owner (controller) or act on their instructions.

Deleting your account. You can delete your account yourself at any time from your account settings — no request or support ticket needed. Deletion immediately cuts off all access to your tours (including any tour managers’ and drivers’ access to them) and cancels your subscription, then permanently erases your account and Content after a 30-day recovery period. You can cancel the deletion during that period simply by signing back in. An account that owns no tours and exists only through a tour-manager invitation is removed immediately, with no recovery period, because there is nothing of its own to recover. A restored account keeps its tours, but previously issued driver and tour-manager share links are not restored and must be created again. Billing records are retained as described in Section 8.

You also have the right to lodge a complaint with the Dutch supervisory authority, the Autoriteit Persoonsgegevens (autoriteitpersoonsgegevens.nl).

10. Security

We use industry-standard measures including encryption in transit, authenticated and role-based access, tenant isolation, and access controls on our infrastructure. No system is completely secure, but we work to protect your data and to notify you and the authorities of any breach where legally required.

11. Cookies and local storage

The Service uses only strictly necessary cookies and local storage — to keep you signed in, maintain your session, and enable the app to work offline as a progressive web app. We do not use advertising or third-party tracking cookies. If we introduce analytics in future, we will update this Policy and request consent where required.

12. Data Processing Agreement

Where we process tour content on your behalf, we do so under our Data Processing Agreement (DPA), which forms part of our Terms and sets out the Article 28 GDPR terms, our security measures, and our sub-processors. Business and institutional customers may request a countersigned copy at info@g3ops.com.

13. Children

The Service is intended for business use by adults and is not directed at anyone under 18. We do not knowingly collect personal data from children.

14. Changes to this Policy

We may update this Policy from time to time. Material changes will be communicated through the Service or by email. The “Last updated” date and the version above identify the current version.

15. Contact

Questions or requests: info@g3ops.com.

Note: The retention periods in Section 8 and the self-service erasure process in Section 9 reflect the data-deletion and retention controls implemented for the Service. Retention on infrastructure surfaces (backups and logs) is enforced through our cloud provider’s configuration and our documented internal retention policy.