Skip to main content

Privacy Policy

Effective date: 2026-11-16

FreightSIQ Privacy Policy

1. Operator and scope

FreightSIQ is operated by Uzitech LLC, a Georgia limited liability company. This Policy describes information handled for the FreightSIQ application, its business subscription services, account communications and related support. It covers information about users, business contacts and individuals appearing in carrier-source records, as applicable. It does not govern a third party's separate website or independent processing merely because we link to it.

This Policy covers authorized commercial subscriptions and separately maintained noncommercial access. Stripe processes enabled subscription billing; Purelymail processes account and support mail. Scheduled ingestion and monitoring process public carrier records and customer-authorized watches. A feature is offered only when enabled for the account; this Policy does not activate registration, payments or trials.

Human support and privacy requests: support@freightsiq.com, handled through Purelymail. Automated transactional messages are sent through Purelymail from no-reply@freightsiq.com; direct questions and replies requiring human assistance to the support address. Postal contact: Uzitech LLC, 6260 Crested Moss Dr, Alpharetta, GA, 30004, USA. Use the support or postal contact for privacy questions, corrections or rights requests. Updated contacts will be published when the company relocates or changes its notice channel.

2. Information and sources

CategoryExamples and source
Account and organizationEmail, optional display name, password hash, organization details, memberships/roles, verification/reset records; supplied by users, organization operators and account activity.
Authentication and securityHashed token identifiers, session/revocation history, IP address, user agent, request/audit identifiers and relevant security events; generated through service use. Passwords are hashed; ordinary account processing is not designed to store plaintext passwords.
Business activityCarrier searches, saved carriers, watchlists, notes, qualification/onboarding activity, usage counters, notification preferences and delivery records; supplied or generated through authorized use.
Customer contentUploaded COIs, W-9s and related documents, extracted fields and workflow observations; supplied by users/organizations. Documents can contain personal contacts and sensitive tax identifiers.
Public-source carrier informationNames, business/contact addresses, phone/email, authority/insurance filings, inspection/violation information, vehicle/VIN observations, fleet data and historical records obtained from regulatory/public-source deliveries, with provenance. These may identify people or sole proprietors.
Legal and historical commercial recordsPresented document versions, exact content/hash, acceptance and authority acknowledgement, organization/user, server timestamp and release context; customer/subscription/session/payment-method identifiers, invoices, discounts, tax location and identification information, payment/refund/dispute events, state/period and verification metadata where held. Stripe-hosted pages collect payment credentials; FreightSIQ is not designed to store full card numbers or CVC.
CommunicationsSupport correspondence, account messages, recipients, message/delivery metadata and related provider events; supplied by users or generated by sending/support activity.

Sensitive tax fields may be encrypted or masked through applicable functions, but original uploaded documents may still contain them. Masking a display does not erase the underlying record or redact every page. Provide only information needed for the authorized purpose and do not upload unrelated sensitive information or credentials.

3. Purposes and responsibility

We use information to authenticate accounts, enforce organization permissions, deliver requested investigation/qualification/onboarding functions, preserve source history and evidence, maintain saved work, administer subscriptions, authorized access and usage, send necessary account/support communications, protect security, investigate abuse, resolve disputes and meet applicable legal obligations.

Uzitech determines the purposes of account administration, service security and public-source intelligence processing. An organization determines why it uploads its own customer content and instructs its requested service processing. We process that content for the permitted service and security/legal purposes. Where applicable law requires a specific processor/service-provider agreement or transfer arrangement, the required arrangement must be in place; this Policy does not assert that an unverified third-party agreement has been signed.

FreightSIQ Assessment reuses existing public-source facts and derived context. Section coverage is not statistical confidence or a risk prediction; Assessment does not make an automated carrier approval/rejection decision or add private customer COIs to its public-source summary. Customer-specific qualification decisions remain separate. Source matching and observations can be wrong; provenance and alternatives require review.

Historical private documents and tax records whose processing authority has not been established are retained under restricted access pending authorized disposition. They are excluded from ordinary customer access until appropriate processing authority or disposition is established. Restriction is subject to the purpose-based retention and deletion provisions below; it is not permanent authorization to retain information without a lawful basis.

4. Disclosures and provider processing

We disclose information only as reasonably needed for the following purposes:

  • To an organization and its authorized users for their tenant-scoped records and permitted work; organization administrators may manage access and business records, subject to permissions.
  • To Uzitech's authorized personnel who need it for their duties, including support, billing and account staff and, for the customer organizations assigned to them, account or sales representatives; access is role-limited.
  • To authorized hosting, email and other service providers supporting the enabled service, with access appropriate to their task; to advisers when needed for lawful operations, disputes or obligations.
  • To comply with law, lawful process, protect rights/safety/security, investigate suspected misuse or respond to an authorized request.
  • In a business transfer with appropriate confidentiality and privacy protections, subject to applicable law and the disclosed service purposes.
  • At the relevant person's/customer's direction or with legally sufficient authorization.

Customer documents are stored in persistent local storage on the production application server. Storage is managed by our hosting provider and authorized operators; this statement does not promise a particular cloud certification or an independently verified storage location. Purelymail handles transactional account/security messages from no-reply@freightsiq.com and their recipient/delivery information. Purelymail handles human support mail at support@freightsiq.com, including incoming correspondence, outgoing responses and replies. Providers' own roles and applicable agreements also govern their independent processing. Local document/PDF extraction is not itself a representation that uploads are sent to an external AI service.

Private account information and customer uploads are not sold or rented for unrelated third-party marketing, used for cross-context behavioral advertising, or provided for unrelated third-party model training. These commitments apply to the FreightSIQ service; access to public or derived carrier information is described separately below. Access to public/derived carrier information is part of the freight-intelligence service. Whether a particular disclosure is regulated as a sale, sharing or data-broker activity depends on the actual information, use and law; public availability and business use do not establish a universal exemption. We will address applicable rights and any required additional notice before an activity requiring it.

5. Cookies, local storage and optional verification

First-party refresh/session cookies and organization preferences support authentication, security and the chosen organization. Browser local storage can retain recent search terms and interface preferences; tab-local session storage correlates a pending Checkout return and is not proof of payment. Clear browser storage or use the available history controls to remove browser-held copies; server security/usage records are handled separately. Access tokens are held in browser memory; supported refresh cookies use HttpOnly protections. Security and operational events may include IP/user-agent information. Pseudonymous or hashed identifiers can remain account-linkable.

FreightSIQ does not use behavioral advertising in the service described here. Usage analytics consist of service-use counters, searches and operational/security events needed to operate and protect the service; this is not a claim that a separate advertising analytics platform is installed. Browser controls may limit cookies, but disabling necessary cookies can prevent login or normal use. Browser privacy settings do not replace a request through the contact in Section 1. We will honor opt-out requests and preference signals where applicable law requires; this Policy does not represent that every browser signal is automatically recognized.

The separate commercial trial implementation can use phone verification through Twilio, email/network risk through IPQualityScore, device assessment through Fingerprint and a first-party trial-device cookie. These providers receive the relevant phone, email, network/device or verification-event information only for an enabled verification flow. Provider-backed checks are not initiated by an unavailable flow. A first-party trial-device cookie can persist for up to 730 days; it can be cleared and does not reliably identify every device or person. External checks can affect eligibility but do not establish wrongdoing; contact support to request review of an adverse eligibility decision. Historical trial/security records already stored remain covered by the relevant retention and rights handling.

If paid functionality is separately activated, Stripe-hosted pages collect payment information and the service retains relevant provider/billing identifiers and state. FreightSIQ is not designed to collect/store full card numbers or CVC. Reading or accepting this Policy alone does not authorize charges. A separate disclosed commercial offer and valid payment authorization are required. Stripe Tax, when enabled, processes relevant billing location/tax information to calculate applicable tax; Uzitech remains responsible for its legal tax obligations.

6. Retention

Retention is based on the category, the purpose still needed, account/workflow status, security concerns, applicable law and valid legal holds. It is not determined only by whether an account remains enabled.

CategoryRetention criteria
Account and organization recordsWhile needed to administer the account/organization, then only for legitimate support, security, dispute, contractual or legal needs. Inactive-account or valid rights requests trigger operator review.
Sessions, verification/reset and security recordsToken validity is bounded and tokens may be used/revoked; expiry does not itself delete all metadata. Metadata is kept only as reasonably needed for account security, incident investigation and relevant legal/audit purposes.
Customer documents, notes and workflowsWhile the authorized investigation/onboarding or customer record purpose continues, then review retention on closure, termination or a verified request. Sensitive content must not be kept solely because storage is available; lawful business-record needs and valid holds can require continued restricted retention.
Upstream captures, public-source history and derived observationsHistorical provenance is an intentional service function. Records may be retained long term while needed for dated evidence, investigation and lawful source-history purposes. A correction need not erase a prior dated observation; annotation, restriction or appropriate correction may be used. No blanket public-data exemption from law is claimed.
Legal acceptance and historical billing evidenceExact published versions and acceptance evidence are preserved for agreement verification, disputes and legal obligations. They are not automatically deleted with an account. Retention must remain justified; a legally required deletion/restriction requires an appropriate operator/legal process.
Communications, operational copies and recovery archivesKept as needed for delivery/support, security, recovery and legal obligations. Copies can persist separately until their authorized retention/disposal process runs; no immediate all-copy purge or unverified fixed backup-expiration promise is made.

Personal information will be deleted or irreversibly anonymized when it is no longer needed for its documented purpose, subject to applicable legal retention obligations and valid legal holds. If retention is required, we will restrict use to the documented retention purpose and review when that requirement ends. Restriction alone is not a permanent substitute for deletion or anonymization after the need and lawful retention basis end.

Deletion and rights requests are manually reviewed and handled through authorized operator procedures. The current application does not implement automatic whole-account erasure. Removing a document from normal access can leave its metadata, historical submissions or recovery copies; deleting a stored file does not erase every related database record. Those remaining copies require separate retention review and appropriate deletion or anonymization when no longer needed. We will explain an applicable retention exception in response to a verified request where permitted. No one-click export or immediate all-copy purge is promised.

7. Security

Measures include hashed credentials/tokens, bounded token validity, session revocation/replay protections, tenant authorization and controlled document access, and protected handling of configured secrets. Protections apply according to the data/function; we do not represent that every raw document or storage layer has identical encryption. Keep credentials private and report suspected misuse through the contact above.

No system can guarantee perfect security or uninterrupted availability. We will investigate credible incidents and provide notices/cooperation required by applicable law and agreements. We do not claim security certification, government approval or blanket GDPR/CCPA compliance.

8. Privacy choices and requests

Depending on the applicable law and information, you may have rights to access/know, correct, delete, obtain a portable copy, object or opt out, restrict/limit sensitive processing, or appeal a decision. Submit a request to the email or postal contact in Section 1. Requests are handled manually. We will verify identity/authority as appropriate, use verification information only for that purpose and explain the response or an applicable exception. Authorized-agent requests will be handled where required.

We aim to acknowledge requests within ten business days and respond without undue delay within applicable legal deadlines, notifying you of a lawful extension when appropriate. This acknowledgement target does not extend a shorter mandatory deadline. No specific right is promised universally or denied solely because a person acts for a business. We will not unlawfully discriminate for exercising a right.

For content controlled by a customer organization, contacting its administrator may be necessary; we will provide appropriate assistance within our role and authority. We will not disclose another tenant's records to fulfill your request. Corrections to a government source may also require the relevant source authority; we can review the way the source observation is presented without pretending to amend that authority's record.

9. Locations, children and changes

Uzitech is a Georgia, United States company. Information may be accessed or processed in the United States or other locations where authorized personnel/providers operate. Where law requires safeguards for a transfer, we will use the applicable safeguards before that transfer. Nothing here claims enrollment in a transfer/certification program or that US registration removes another jurisdiction's rights.

The service is for adult business users, not a service directed to children. Do not knowingly supply children's information for unrelated purposes. Contact us if you believe such information has been provided so we can investigate and take appropriate action; no automatic age-verification capability is claimed.

We will identify this Policy's published version/effective date and preserve relevant historical notices. Material changes will be disclosed by account communication or a conspicuous service notice and require consent/acceptance where applicable law or the contract requires it. A future use materially inconsistent with these disclosed purposes requires appropriate notice and legal authorization before it begins.