1. Scope and contact
IGAMING TEAM LLC, operating the FreightGuard software product and brand, is the controller of personal information processed through the FreightGuard website, dashboard, API, Carrier Alerts and related support services.
Business mailing address: Tsarav Aghbyur 55 33, Yerevan 0052, Armenia. Privacy inquiries and requests: admin@freightsguard.com.
2. Information we collect
Account and support information
We collect your company name, work email, securely hashed password, account preferences, information you provide in support messages, and outcome or ROI feedback you choose to submit. We store only a one-way hash of an API key after the full key is shown to you.
Service and device information
We process API routes requested, request counts, timestamps, approximate network information such as IP address, browser or client metadata, security events and error logs. Daily API usage records are normally retained for up to 35 days.
Billing information
When you request an invoice, we collect the legal company name, billing contact, address, country, tax identifier if supplied, purchase-order reference, selected plan and preferred payment method. Banks and payment providers may separately process payment instruments, identity checks, fraud screening and transfer records under their own terms and privacy notices. We receive the payment-status and reference information needed to manage FreightGuard access. We do not receive or store full payment-card numbers or online-banking credentials.
Business documents and customer content
If you use document or reconciliation features, we process files and extracted business information you submit to perform the requested workflow. Do not submit information you are not authorized to process.
Freight records
Our product includes carrier, broker, facility, safety, crash, fleet, contact and government-award information obtained primarily from public government records. Some records may identify business officers or contacts acting in a professional capacity.
Carrier Alerts and delivery destinations
When you use Carrier Alerts, we store the USDOT numbers you monitor, baseline snapshots, detected changes, read status and delivery results. If you configure an external channel, we also process the destination email, Slack Incoming Webhook or Telegram chat ID. Slack webhook credentials are encrypted at rest and are never returned through the API after they are saved.
Optional marketing communications
If you separately opt in, we send occasional product updates and freight-risk insights through Resend. We record when and where consent was provided. Marketing messages include an unsubscribe link, and opting out does not affect account notices, billing messages or Carrier Alerts you requested.
3. How we use information
- provide accounts, authentication, API access, searches, exports and support;
- monitor customer-selected carrier records, create change histories and deliver requested alerts;
- measure signup, first-use, checkout and subscription-activation milestones;
- enforce plan limits, secure the service and prevent fraud or abuse;
- process subscriptions and comply with tax, accounting and legal obligations;
- maintain, debug and improve data quality and product performance;
- send transactional or service communications and, where permitted, relevant product updates.
4. Legal bases
Where a legal basis is required, we process information to perform our contract with you, pursue legitimate interests in operating and securing a B2B service, comply with legal obligations, and act on consent where consent is the appropriate basis. You may withdraw consent without affecting earlier lawful processing.
5. Sharing and service providers
We do not sell personal information and do not share it for cross-context behavioral advertising. We may disclose information:
- to infrastructure, security, email, messaging, analytics and support providers, including Resend for email delivery and subscription preferences, acting under our instructions;
- to Slack or Telegram only when you configure and enable the corresponding alert destination;
- to banks and payment providers chosen for invoice delivery, payment collection, fraud screening, refunds and customer payment support;
- when required by law or reasonably necessary to protect users, FreightGuard or the public;
- in connection with a merger, financing, acquisition or sale, subject to appropriate safeguards.
6. Cookies and analytics
FreightGuard uses an HttpOnly, secure, same-site session cookie to keep signed-in users authenticated. We also use limited first-party product telemetry to understand whether core workflow milestones succeed. We do not use third-party advertising cookies. Browser settings can block cookies, but authentication will not work without the session cookie.
7. Retention
We keep account and subscription records while an account is active and afterward as reasonably needed for legal, tax, security and dispute purposes. Service logs and customer content are retained only as long as reasonably necessary for the service or applicable obligations. Backups expire through controlled rotation. We may retain de-identified aggregate statistics that no longer identify an individual or customer.
8. Security
We use transport encryption, access controls, hashed passwords and API keys, private document storage, rate limits, payment verification controls, logging and backups designed to protect information. No system is completely secure, so we cannot guarantee absolute security.
9. International transfers
FreightGuard and its providers may process information in Armenia, the United States and other countries. Where required, we use contractual or other recognized safeguards for international transfers.
10. Your choices and rights
Depending on your location, you may request access, correction, deletion, restriction, objection or portability, or complain to a supervisory authority. We may need to verify your identity and may retain information where law permits or requires. You can stop future subscription billing by contacting us and may opt out of non-essential marketing email using the message instructions.
11. Children
The service is for businesses and is not directed to children under 18. We do not knowingly collect personal information from children.
12. Changes
We may update this policy to reflect changes in law, providers or the service. We will publish the updated date and provide reasonable notice of material changes.