fuelstops.io
← Back to home

Privacy Policy

Last updated July 10, 2026 (Version 1.0)

This Privacy Policy describes how the fuelstops.io platform (fuelstops.io) operated by Infomax Inc. (“we,” “our,” or “us”) collects, uses, and protects information. fuelstops.io is a business tool sold to freight carriers, and this policy is written for that business audience.

1. Introduction

fuelstops.io helps freight carriers plan cost-efficient fuel stops and deliver those plans to drivers over Telegram. Each carrier that subscribes is a separate, isolated tenant. We act as the business responsible for a carrier's own company and account data, and as a service provider for the fleet and fuel-price data a carrier connects — we process that data on the carrier's instruction and only to provide the service. Each carrier is responsible for its own relationship with, and any notices or consents owed to, its drivers.

2. Information We Collect

  • Company information— carrier company name and identifier, configuration, optimizer settings, driver-group mappings, and plan history.
  • Account information— the email addresses of carrier admins and dispatchers and their roles. Sign-in is passwordless, so we do not collect or store passwords.
  • Telegram identities— the Telegram user IDs on a carrier's dispatcher allow-list and a secure sign-in tied to your carrier through the Telegram Mini App.
  • Fleet and vehicle data— vehicle location and fuel-status data from the telematics provider a carrier connects (such as Samsara), used to build a plan.
  • Fuel-price data— a carrier's negotiated per-gallon contract prices from the fuel-price provider it connects (Pilot Flying J / One9, Axle, and others).
  • Route and plan data— the origin and destination addresses a dispatcher enters and the generated plans. Messages sent to drivers contain stops only — never prices.
  • Consent records— when you create an account we record your acceptance of our Terms and this policy: the document, its version, the date and time, and the IP address used.
  • Credentials— the provider API credentials and Telegram bot token a carrier supplies, stored encrypted and never returned to any client.
  • Billing information— subscription tier, active-truck counts, and billing status. Payments are processed by Infomax Inc. through Stripe; card data is handled entirely by Stripe, and we never receive or store full card numbers.
  • Technical data— IP address and request metadata used to secure the service and prevent abuse.

3. How We Use Information

  • To authenticate users and authorize dispatchers.
  • To read a truck's live status, geocode and route addresses, and generate fuel-stop plans.
  • To deliver plans to the correct driver group through the carrier's own Telegram bot.
  • To operate, secure, monitor, and support the service and prevent abuse.
  • To meter usage, calculate charges, and administer billing.
  • To send transactional email only — passwordless sign-in and account notices such as verification, approval, and suspension. We do not send marketing email through the service.
  • To comply with law and enforce our agreements.

Fuel plans are generated with the help of a third-party AI service (Google Gemini), which we use to help identify suitable fuel stops along a route; no driver personal data is used for this. We do not sell personal information, and we do not use the service for advertising.

4. Information Sharing

We do not sell personal information. We share information only as needed to run the service:

  • With service providers that deliver parts of the service, each receiving only what it needs: Railway (hosting and database), Google Gemini (plan optimization), HERE Maps (geocoding, routing, maps), Telegram (Mini App and plan delivery), Resend (transactional email), Stripe(payment processing), and the telematics and fuel-price providers a carrier connects (e.g. Samsara, Pilot Flying J / One9, Axle), which process data at the carrier's direction.
  • Within a carrier's own tenant, with its authorized admins and dispatchers.
  • When required by law or valid legal process.
  • In connection with a merger, acquisition, or sale of assets, subject to this policy.

5. Data Security

  • Each carrier's data is isolated at the database layer, so one carrier cannot access another's data.
  • Provider credentials and bot tokens are encrypted and access-controlled, and never returned to any client.
  • Traffic to and from the service is protected with TLS.
  • Access is controlled through passwordless authentication, role-based permissions, and time-boxed, audited support access.

No method of transmission or storage is perfectly secure, but we protect information using measures appropriate to its sensitivity.

6. Data Retention

We retain carrier and account information while your account is active and as needed to provide the service. Live vehicle-status snapshots used at plan time are short-lived and expire automatically. We retain billing and consent records as needed for compliance. You may request deletion of your data by contacting us at the email below, subject to legal and accounting obligations.

7. Your Rights

Depending on where you live, you may have the right to:

  • Know and access the personal information we hold about you;
  • Request correction of inaccurate information;
  • Request deletion of your information;
  • Opt out of any sale or sharing of personal information (we do not sell or share personal information for advertising); and
  • Not be treated differently for exercising these rights.

Where we process driver or fleet data on a carrier's behalf, please direct requests to that carrier, which controls the data. To exercise your rights or ask a question, email us at ak@infomaxmgt.com. We will verify your request before responding.

8. Cookies

We use only strictly necessary cookies to run the service — a secure, HttpOnly session cookie and a CSRF-protection token. We do not use analytics, advertising, or tracking cookies.

9. Children's Privacy

fuelstops.io is a business tool for commercial freight operations. It is not directed to children, and we do not knowingly collect information from children. If you believe a child has provided us information, contact us and we will delete it.

10. Changes to This Policy

We may update this policy from time to time. When we make material changes, we will update the version and date at the top of this page. Your continued use of the service after an update takes effect means you accept the revised policy.

11. Contact Us

If you have any questions about this Privacy Policy, please contact us: