Privacy Policy
Last updated September 6, 2026
HALZAT is freight software for carriers and brokers. This policy explains what we collect, what we do with it, and what we will never do with it. The section on Google account data is the one most people are looking for, so it comes first.
1. Google account data
HALZAT can connect to a Gmail or Google Workspace mailbox that you choose to link. Connecting is optional. The product works without it, and you can disconnect at any time.
What we request, and why
| Google permission | What it lets us do | Why HALZAT needs it |
|---|---|---|
gmail.readonly | Read messages and attachments in the connected mailbox | To find freight quote requests, rate sheets and booking emails, and turn them into quotes and shipments automatically instead of you retyping them |
gmail.send | Send a message from the connected mailbox | So quotes, replies and bills of lading arrive from your own address. Your carriers and customers already know that address; a message from ours would be treated as a stranger, or as fraud |
userinfo.email | See the email address of the account you connected | To label the connection in your settings, and to make sure a message is sent from the mailbox you actually linked |
We do not request permission to delete mail, change your Google account, or read any other Google service. We do not read mailboxes that have not been explicitly connected by the account holder.
Limited Use
HALZAT’s use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
In plain terms, and specifically for data we obtain from your Google account:
- We do not sell it. Not to data brokers, not to advertisers, not to anyone.
- We do not use it for advertising. No ad targeting, no ad measurement, no audience building.
- We do not use it to train generalized AI or machine learning models. Your mail is passed to a language model to read one message and return structured freight details back to you, and for nothing else. Our model providers are contractually bound not to train on it.
- Humans do not read it except in the narrow cases Google permits: with your explicit prior consent for a specific support request, where required by law, or where strictly necessary for a security investigation. Any such access is logged.
Who else touches it
Reading a freight email requires sending its contents to a language model, so Google account data does leave our servers. These are all of the sub-processors that can see it:
| Sub-processor | Role | What it can see |
|---|---|---|
| OpenAI | Language model that extracts freight details from a message | The text and attachments of messages our scan identifies as freight-related. Sent through the API, which is not used for model training. |
| Supabase | Database hosting | Extracted freight records, and your encrypted Google refresh token. Isolated per tenant. |
| Vercel | Application hosting | Data in transit while a request is being served. |
We do not transfer Google account data to any other third party, and we do not use it for any purpose outside the features described above.
What we store, and for how long
- Your Google refresh token, encrypted at rest, so the connection keeps working without asking you to sign in every day. Deleted immediately when you disconnect.
- Extracted freight records — the quote, shipment or booking we built from a message. This is your operating record and we keep it while your account is open.
- Message identifiers of mail we have already processed, so the same email is not turned into a duplicate shipment.
- Message bodies and attachments are not retained as a mail archive. We read a message, extract what the product needs, and keep the extraction — not a copy of your mailbox.
How to revoke access
Two ways, either is enough. Inside HALZAT, open the email integration settings and disconnect the mailbox — this deletes our stored token. Or from Google directly, at myaccount.google.com/permissions, remove HALZAT’s access. Revoking stops all future reading and sending immediately.
2. Other data we handle
- Account data — your name, work email, company, and role, so we know who is signing in and what they are allowed to see.
- Freight and operating data — shipments, quotes, rates, documents, proofs of delivery, invoices and the addresses and contacts attached to them. This is the substance of the product.
- Site analytics — page views and referral source, on our marketing pages, so we know which ads bring real carriers. This is separate from any connected mailbox and never mixes with it.
- Support messages you send us.
We do not sell any of it. We share it only with the sub-processors listed above, with the carriers and partners a shipment is actually being tendered to, and where the law requires.
3. Security
Data is encrypted in transit and at rest. Access is scoped per tenant at the database layer, so one company’s records are not reachable from another’s session. OAuth tokens are encrypted with a key held outside the database. Access to production is restricted to staff who need it and is logged.
No system is perfect. If we discover a breach affecting your data we will tell you promptly and tell you what we know, including what we do not yet know.
4. Your choices
- Connect a mailbox, or do not. The product works either way.
- Disconnect at any time, from HALZAT or from your Google account settings.
- Ask us for a copy of your data, or ask us to delete it, by writing to the address below. We will respond within 30 days.
- Closing your account deletes your operating data on request; some records are retained where we are legally required to keep them, such as invoices.
5. Children
HALZAT is business software sold to companies. It is not directed at anyone under 18 and we do not knowingly collect their data.
6. Changes
If we change this policy in a way that affects what we do with your data, we will update the date at the top and tell account holders before the change takes effect.
7. Contact
Privacy questions, data requests and deletion requests: privacy@halzat.com.
Halzat Logistic Technology Inc, a Delaware corporation, Los Angeles, California, USA.
Halzat Logistic Technology Inc, Los Angeles, California, USA.