Privacy policy

The Vietnamese version is the reference version.

In force. Reviewer: Lại Minh Thắng (Giám đốc).

1. Who operates this service

Vietnam HS Code & Tariff — by OZ, operated by CÔNG TY CỔ PHẦN DỊCH VỤ VÀ THƯƠNG MẠI QTOZ VIỆT NAM, address Số 57 Ngõ 481, Phố Ngọc Lâm, Phường Bồ Đề, Thành phố Hà Nội, Việt Nam, tax code 0106179886. Contact: ceo@ozfreight.vn. Unofficial; not affiliated with the General Department of Vietnam Customs.

2. When you call tools without an account

• Each call writes one call-log row: call ID, tool name, success or error (and error code), processing time, timestamp, and access type "no account". The row is not linked to any account or key.
• Raw IP addresses are not stored. The IP address is used only while handling the call to compute an ip_bam value: HMAC-SHA256 with a secret key that rotates every day (Vietnam time), truncated to 16 characters. It cannot be reversed without the secret key held by OZ, and the same IP on two different days gives two different values. IPv6 addresses are grouped by /64 before hashing. Traffic from a platform's shared IP range (e.g. claude.ai) shares one value for the whole range. The value is used to count abuse limits.
• Search terms are not stored in clear. The gateway's logs do not record your query text (keywords, product descriptions). For the tool that takes free-text descriptions (ruling search by description), the operational log records only the length and the first 8 characters of a SHA-256 hash. This hash is short and unsalted: for short or common descriptions, someone with access to the log could recover the text by dictionary guessing, so it is not fully anonymous.
• The query is forwarded to OZ's HS lookup system (hs-code-api) to get the result. hs-code-api currently stores: a request URL log (up to 160 characters, which can include the query); a query snippet (first 80 characters) with the returned HS code and processing time; for classification calls when you agreed to share, the first 120 characters of the product description with the top HS code. These records are not directly linked to the end user's identity, because hs-code-api only receives questions through the gateway's service key. When you choose not to share, the gateway sends X-OZ-Chia-Se: 0 and hs-code-api does not store the product description in clear.

3. When you have an account (OZ key or sign-in)

• Account details: for accounts created by OZ: phone number, name, account type (individual or business), tax code if you provide it; for accounts created at sign-in: email (section 4).
• Your OZ key is stored as a SHA-256 hash plus its first 8 characters (the prefix ozk_ + 4 characters) for identification; the full key cannot be read back.
• Call log linked to your account: tool, result, processing time, points, whether it was a trial call, and input source (image, link or text) where given.
• Points ledger: every top-up, hold, charge, refund and bonus is written to an append-only ledger (no edits, no deletions) for reconciliation.
• AI classification: the product description (name, material, use, specifications) is sent to hs-code-api, which uses paid AI services only from third parties (section 9) to classify it — the description is not sent to free tiers. The gateway's log records only the length and an 8-character hash (short and unsalted, as in section 2) of the product name, not the text.
• Order requests through OZ (the yeu_cau_dat_hang table), only when you ask through the yeu_cau_dat_qua_oz tool and agree to be contacted by OZ: the product name, link, quantity and note are stored exactly as you sent them, with the HS code if any, so OZ can contact you with a quote (section 9).
• Feedback (the phan_hoi table) when you rate a result with the gui_phan_hoi tool: the rating, the call ID, the HS code you consider correct (if any); a free-text note is stored only if you agreed to share.
• Consent (the dong_y table, append-only): the terms version you agreed to, your choice about sharing product descriptions and the time, for accounts using an OZ key and accounts created at sign-in.

4. Sign in with email inside your assistant (OAuth)

• Email: the email you enter is stored in your account (the tai_khoan table) once you verify the code and click agree; accounts created by email need no phone number. If you decline, no account is created.
• One-time code (OTP): a 6-digit code sent to your email through an email-sending provider configured by OZ (section 9); valid for 10 minutes; at most 5 wrong attempts per code (and at most 20 wrong attempts per email in 24 hours). The gateway stores only a SHA-256 hash of the code, never the code itself.
• While waiting for verification: the OTP challenge table (otp_thu_thach) does not store your email in clear, only an HMAC-SHA256 of it (secret key) to match it and limit how often codes are sent, plus an ip_bam value of the address (section 2; hashed per IP address (IPv6 grouped by /64), not grouped by platform range) to limit by address. The email travels through the sign-in page in your own browser.
• Email addresses from disposable-mailbox services are refused.
• Tokens: after sign-in your assistant receives an access token (valid 1 hour) and a refresh token (valid 30 days, replaced on every use). The gateway stores only SHA-256 hashes of tokens and of the authorization code (valid 10 minutes).
• Consent: the terms version you agreed to and your choice about sharing product descriptions are written to the dong_y table, append-only.
• Assistant app: the name and redirect addresses that the assistant app (e.g. Claude) declares when connecting. For self-registered apps (DCR), the gateway also stores the ip_bam of the registering address (section 2; hashed per IP address (IPv6 grouped by /64), not grouped by platform range) to limit registrations.
• Sign-in operational logs never record tokens, OTP codes or full email addresses; emails appear only masked, e.g. k***@c***.vn.

5. Declaration data (declaration review and HS-code disputes)

• What is sent: when you use soat_to_khai, kiem_ma_to_khai or soan_ho_so_giai_trinh, the gateway forwards to hs-code-api exactly the fields you enter: declared HS code, goods description, origin, value, declared duty rate, declaration type, licences, specifications (for a dispute draft: the declared code, the code customs applied, the reason customs gave, the goods description, the documents you have, the reply deadline). These tools have no field for company name, tax code, declaration number, seller or invoice number; unknown fields are rejected. Do not type such details into the description.
• AI: kiem_ma_to_khai and soan_ho_so_giai_trinh use paid AI services from third parties through hs-code-api (section 9), not the free tier; the content is sent to the providers' servers abroad. soat_to_khai does not use AI. OZ does not promise on behalf of the AI providers whether they use the content sent to them for model training; that follows each provider's own terms.
• Storage: what you send to kiem_ma_to_khai and soan_ho_so_giai_trinh is kept in the dau_vao column of the background-job table so it can be processed and you can fetch the result. For a background code-check job, the input and result are cleared after 7 days from when the job finishes, and the job row is deleted entirely after 14 days (section 8). The gateway's call log records only the number of lines, the length and an 8-character hash of the description, not the text.
• OZ specialist: an OZ specialist can open the content of a run only if you agree, through the choPhepXemNoiDung field of that very yeu_cau_chuyen_gia_oz call; you choose each time you send a request, with no default. If you do not agree, the specialist only calls you back and does not open the run.
• Telegram: the message about a specialist request, sent to OZ staff's Telegram group, contains only the request code, urgency, callback phone number, run ID and whether you agreed to let them view it; messages do not copy product names, goods descriptions or declaration lines.

6. Using it through claude.ai, ChatGPT or another assistant

Your conversation is processed by that platform under its own terms. The gateway only receives the arguments the assistant sends when calling a tool.

7. Purposes

Returning lookup results; counting abuse limits; verifying sign-in; charging and reconciling points; contacting you with an import quote when you ask; improving quality (when you agree); operational statistics (call counts, error rate, latency).

8. Retention

• Call log: rows older than 12 months are deleted automatically; cleanup runs daily.
• What you send to kiem_ma_to_khai and soan_ho_so_giai_trinh (the dau_vao column of the background-job table): for a background code-check job, the input and result are cleared after 7 days from when the job finishes, and the job row is deleted entirely after 14 days; cleanup runs daily.
• ip_bam values: values older than 30 days are blanked automatically; cleanup runs daily.
• Expired OTP challenges, authorization codes and tokens: they stop working once expired (OTP 10 minutes, authorization code 10 minutes, refresh token 30 days) and are deleted from the database 7 days after expiry; a token chain's root row is deleted only when the whole chain has expired and no call log row references it. Cleanup runs daily.
• Server operational logs (access, errors): kept as needed for operations, maintenance and incident response, and cleaned up periodically according to the system's configuration.
• Account details and points ledger: kept while the account is active and for up to 10 years after the last transaction, to meet accounting and tax obligations under Vietnamese law; after that they are deleted or anonymised at your request or under OZ's policy.

9. Sharing

• hs-code-api (OZ's own system): receives queries and product descriptions (sections 2, 3).
• AI providers behind hs-code-api during classification: MiniMax (outside Vietnam) and Google (Gemini, paid tier; United States). Product descriptions are sent to these providers' servers abroad, which is a cross-border transfer of data.
• Telegram (Telegram FZ-LLC, outside Vietnam): when you use the yeu_cau_dat_qua_oz tool, your phone number, name, product name, HS code, link, quantity and note are sent to OZ staff's Telegram group so they can contact you with a quote. Operational cost alerts are also sent through Telegram (they contain none of your data).
• When you use the DSH package: the DSH assistant's requests go through a LiteLLM server operated by OZ to OpenAI or Anthropic (United States).
• Infrastructure: servers operated by OZ itself in Vietnam; the CDN and edge network of Cloudflare, Inc.
• Sending sign-in codes (OTP): Google (Gmail, outside Vietnam) — the email-sending provider configured by OZ.
• Google (Google LLC, outside Vietnam): when you choose "Sign in with Google", Google verifies that you own the account and sends the gateway your email address. The gateway receives only the email; it does not receive your name, picture or any other data, and does not store the Google sign-in code after verification.

10. Your rights

Under Decree 13/2023/ND-CP on personal data protection, you have the right to: be informed about and consent to the processing of your data; access, view and request correction of your personal data; withdraw consent; request deletion, restriction of or object to processing; request that your data be provided or transferred; and complain, denounce or sue as provided by law. These requests are handled manually via the support email (ceo@ozfreight.vn); the transaction ledger cannot be deleted under accounting rules; only the account details are anonymised. OZ replies within the time limits set by law. Calls without an account are not linked to an identity and raw IPs are not stored, so OZ cannot find one person's calls.

11. Cookies

These pages set no cookies and run no tracking code.

12. Contact

ceo@ozfreight.vn