Privacy Policy
Effective date:
Last updated:
HTS Pilot ("we", "us") is a tariff classification tool. This policy explains what personal information the service handles, why, who receives it and what you can ask us to do about it. It covers the website htspilot.com, the application behind the sign-in, the contact form and the support requests.
The service is built for businesses. It needs product descriptions, not information about people, so please leave personal information out of the descriptions and files you submit.
1. Who is responsible
HTS Pilot is the controller of the personal information described here.
Privacy contact: privacy@htspilot.com
2. What we collect
Account. When you sign in with Google we receive and store your email address, your name, the identifier Google assigns to your account and the address of your profile picture. The picture address is updated at each sign-in. We never receive your Google password. Accounts that sign in with a password are created by an administrator; for those we store the email address, the name and the password as an Argon2id hash, never the password itself. For every account we also store its role, its credit balance, whether it is active, when it was created and when it last signed in.
What you submit. The product description and the optional fields that go with it (material, use, composition, origin, notes), the market you chose, and your answers to follow-up questions. For a batch lookup we store the Excel or CSV file you upload and every column of every row in it, including columns you do not map. Entries you add to the SKU catalog are stored and are visible to the members of your workspace, not to other workspaces.
Results and history. For each lookup we store the result: the proposed code and the alternatives, the reasoning written by the language model, the sources and excerpts used as evidence, the name of the model, the number of tokens, the status and the time taken. We store who created the lookup and, if it was reviewed, who decided it, when, and the reviewer's note.
Audit log. Each action on a lookup (created, run again, approved, changed, rejected, reopened, commented) is recorded with the user, the user's display name, the codes before and after, the note, the tariff version and the time.
Credits and usage. A ledger of credit movements: the credits granted when the account was created, credits granted or adjusted by an administrator, and the credits used by each lookup with its token count.
Online purchases. When a plan is bought online, the payment is taken by our payment provider (section 6), not by us. From the provider we receive and store identifiers of the customer, the subscription and each payment, the plan, the status of the subscription and of each payment, the amount, currency and date of each payment, the billing country, and, to show them to you, the card brand, the last four digits and the expiry date of the card. The card number and the security code are entered on the provider's checkout. They never reach us, and we do not store them.
Security records. Session tokens are stored as SHA-256 hashes with their expiry time. When a password sign-in fails we record a hash of the email address that was typed, the IP address the attempt came from, the number of failures and any lock that results. API keys are stored as hashes with a short prefix, a name, the owner and the time they were last used. Administrators can register webhooks; we store their address, their signing secret and a record of each delivery.
Collected automatically. The site is served through Cloudflare, which processes your IP address, your browser's user agent and the address requested in order to deliver and protect the site. The application server logs the method, path, status and duration of each request; the access logs kept by our hosting providers can also contain IP addresses and full request addresses. To choose which price list the landing page shows, the site uses the country that its content delivery network derives from the network address of each request. It uses the country only to prepare that one page and does not store it beyond the request logs described above.
Contact form. Your name, your email address, your phone number and company if you give them, the topic you chose, your message, the language of the page, the country Cloudflare derives from your IP address and the time of the request. Your IP address is used to limit how many messages one address can send and is passed to Cloudflare Turnstile to check that the sender is a person. A message sent through the form is filed as a support request, described next. The number of requests filed from one email address in a day, and the number the form files in all in an hour, are limited; the first is counted from the requests already stored. If the message cannot be filed, because one of these limits is reached, because the service is busy or because filing is not set up, it is delivered to our mailbox instead.
Support requests. A signed-in user can open a support request in the application, and the contact form files one for a visitor. A request from the application holds its subject and category, your messages, the files you attach (images, PDF, spreadsheet, CSV or text; at most 5 files to a message, 10 to a request and 5 MB each) and, taken at the moment you open it, your account, the workspace you were acting in and the plan of that workspace. A request from the contact form holds what the paragraph above lists, and is not linked to any account. The files are stored in our database. The total an account may attach over 30 days, and the total all users may attach in a day, are limited; a file that would pass a limit is refused. Replies are stored in the same thread. Our staff can also add internal notes, which you do not see. Each action on a request (opened, replied, file added, status or assignee changed) is recorded in a trail with the time and the IP address it came from. When our staff reply, or mark a request resolved, we send you an email with the reference of the request; when a request is opened or answered, we send an email with an excerpt of the message to the HTS Pilot staff who handle support.
Search and free classification on the public tariff pages. These need no account. To keep them fair for everyone, we count the searches and the free classifications of each network address: we store a keyed hash of your IP address (the IPv4 address, or the IPv6 /64 network) with a count, for up to 2 days. The address itself is not stored, and we do not store what you search for. The text of a search travels in the body of the request, not in the web address, so the request logs of our application and of our hosting providers, which record the address requested and the time, do not contain it. The free classification also passes your IP address to Cloudflare Turnstile, to check that you are a person.
We do not buy personal information from anyone, and the service has no advertising or analytics trackers.
3. Browser storage and cookies
The site itself sets no cookies. It keeps the entries below in your browser's storage, all of them functional. Session storage belongs to one tab and is emptied when the browser is closed; local storage stays until it is removed:
| Name | Purpose | Kept |
|---|---|---|
| hts_token | Keeps you signed in. It holds the session token. Without "Keep me signed in" it is kept in session storage, and the other open tabs of this site receive it through the browser, so that a link opened in a new tab stays signed in. With "Keep me signed in" it is kept in local storage | Without "Keep me signed in": until you sign out, the browser is closed or the session expires, 12 hours after sign-in. With it: until you sign out or the session expires, up to 30 days after sign-in |
| hts_signed_out | Kept in session storage. Remembers that you signed out in this tab, so that the tab does not take a session over from another tab | Until you sign in again in that tab or close it |
| hts_theme | Remembers the light, dark or system theme | Until you clear site data |
| hts_lang | Remembers the language of these pages and of the application | Until you clear site data |
| hts_tariff_try | Kept in session storage. Holds the token of the free classification you started on the tariff pages, so that its result is still there if you open another tariff page in the same tab | Until the result is shown, or one hour after you started, or until you close the tab |
Third-party components run in your browser on the pages that need them, and are governed by their providers' own terms. Today there are two: the Google sign-in button on the sign-in page, and the Cloudflare Turnstile check on the contact page and in the free classification box of the tariff pages. When you start a purchase online, the checkout of our payment provider loads on the purchase page. Each component is loaded only on the page that needs it. They may store their own cookies or local data to do their job.
4. Why we use it
| Purpose | Lawful basis (GDPR) |
|---|---|
| Providing the service: classifying products, keeping your lookups, batches and history | Performance of a contract |
| Signing you in and keeping accounts secure, including locking after repeated failed sign-ins | Performance of a contract; legitimate interests |
| Review of results and the audit log of decisions | Legitimate interests |
| Improving the ranking of candidate codes and the confidence figure from stored reviewer decisions | Legitimate interests |
| Accounting for credits and usage | Performance of a contract |
| Answering your enquiry | Legitimate interests, or consent where we ask for it |
| Handling support requests: reading them, answering them and keeping the thread and its trail | Performance of a contract for a signed-in user; legitimate interests for a visitor who writes through the contact form |
| Preventing spam and abuse of the contact form | Legitimate interests |
| Meeting accounting and legal obligations | Legal obligation |
We do not sell personal information. We do not use it for advertising. The service proposes tariff codes for products; it does not make decisions about people.
5. How product descriptions are processed by AI
To classify a product, the service sends the product description and the optional fields you filled in to an AI inference gateway, which runs a language model, an embedding model and a reranking model. Your name, your email address, your account identifier and your IP address are not part of what is sent. Because the description is sent as you wrote it, anything personal you type into it is sent too.
The free classification on the public tariff pages, which needs no account, sends the description you type to the same AI inference services in the same way, and keeps nothing of it in a history: the description is deleted from our server when the run ends, and only the short result is kept, for one hour.
When a reviewer decides a lookup, the description, the extracted attributes and the decision are stored as an example. Examples are used inside this service only: as precedents for later lookups of similar products in the same workspace, and for the ranking of candidate codes and the calibration of the confidence figure, as set out below.
Each workspace, personal or team, is separate. Its reviewer decisions are never shown to another workspace and never serve as precedents for its lookups. A lookup made earlier that drew on a decision of another workspace keeps its codes but shows no reference to that decision. The ranking and the calibration are trained on the decisions of the workspace we operate ourselves. An owner of a workspace on a paid plan may opt in, in the workspace settings, to contribute anonymised, aggregated signals from its decisions to improve the ranking for every workspace. No text, code or workspace identifier is contributed, and a figure is used only where at least 5 workspaces contributed to it. The opt-in is off by default and the owner can withdraw it at any time.
We do not use your content to train general-purpose language models.
Product descriptions and the fields you submit with them are sent to third-party AI inference services that we use under contract, only to produce the classification result. A list of the providers in use is available on request at privacy@htspilot.com.
7. Who can see it inside the service
- A user with the User role sees only their own lookups and batches.
- Reviewers and administrators see every member's lookups and batches in their workspace, so that they can review them.
- Administrators see the list of users: email address, name, role, last sign-in, profile picture and credit balance. Reviewers do not see this list. They see a user's name on the lookups they review, and each user's name, role and counts of lookups, decisions and comments in the reports.
- The SKU catalog and its alerts belong to a workspace and are visible to its members only.
- A member of a team who is suspended because the team's plan has fewer seats has no access to the team's data. An owner or administrator of the team may grant temporary read-only access, which never includes export, download or API access.
- Your display name appears next to the decisions you make, in the audit log and in exported batch results.
- A support request is visible to you in your account and to the HTS Pilot staff who handle support, who see every request together with the requester's details, the workspace and its plan. Other members and administrators of your workspace do not see it. Our staff are not named to you in the thread or in the emails.
8. International transfers
We operate from Vietnam and our providers operate in several countries, so your information may be processed outside your own country. Where we transfer personal data out of the EU, the UK, Japan or Korea we rely on the transfer mechanisms available to us, including standard contractual clauses, and we assess whether further safeguards are needed.
9. How long we keep it
The periods below are the ones the service applies today. Where no period has been set yet, this policy says so instead of promising one.
| Information | Kept for |
|---|---|
| Session token | 12 hours after sign-in, or up to 30 days with "Keep me signed in"; earlier if you sign out, your password is changed or your account is locked |
| Record of failed sign-ins, including the IP address | Removed once it is more than one day old; the removal runs at the next failed sign-in |
| Contact-form rate-limit counter, keyed by IP address | About one hour |
| Counter of the free searches and free classifications on the tariff pages, keyed by a hash of the IP address | Up to 2 days |
| Description of a free classification, on our server | Until the run ends, then deleted; the short result is kept for one hour |
| Contact-form messages in our mailbox | 24 months from the last contact, then deleted |
| Counter of contact-form submissions by IP address, in the application | Removed once it is more than one day old; the removal runs at the next contact-form submission or failed sign-in |
| Support requests: subject, messages, files and the requester's details | No period is set. Kept while the account exists. When we erase the account, its requests, and the contact-form requests sent with its email address, lose the requester's details, the subject, the requester's messages and every file, and are closed; our staff's replies and notes stay as written, even where they quote or name the requester. Contact-form requests are found by the email address the account had when it was erased; one sent with an address the account held before is not found. A request from the contact form with no such account is kept until our staff delete it |
| Trail of a support request (action, time and IP address) | No period is set. It stays when a request is anonymised or deleted. When an account is erased, the IP address is removed from every action recorded on each of its requests, and on each contact-form request found as described above, whoever took the action (the requester, a visitor or our staff), and from the actions that account itself took on any request. The rest of the trail stays |
| Account profile | Not yet defined. Kept while the account exists |
| Lookups, results and sources | Not yet defined |
| Uploaded batch files and their rows | Not yet defined |
| SKU catalog entries | Until a reviewer deletes them |
| Audit log and credit ledger | Not yet defined |
| Subscription and payment records received from the payment provider | Not yet defined |
| Stored reviewer decisions used for ranking | Until the decision is reopened; otherwise not yet defined |
| Server and security logs | According to the retention schedule of each hosting provider |
The application has no button to delete an account or to export your data yet. Until it has, write to privacy@htspilot.com and we will do it for you.
10. Your rights
Depending on where you live, you may have the right to:
- access the personal information we hold about you;
- correct information that is inaccurate or incomplete;
- delete information we no longer have a basis to keep;
- restrict or object to how we use it;
- receive a copy in a portable format;
- withdraw consent where consent is the basis we relied on;
- complain to your data protection authority.
To use any of these rights, write to privacy@htspilot.com. We answer within 30 days. We may ask you to confirm your identity first, because handing personal data to the wrong person would be worse than a short delay.
11. Security
Connections to the site are encrypted. Passwords are stored as Argon2id hashes, and session tokens and API keys as SHA-256 hashes. An account is locked for a time after repeated wrong passwords. Access inside the service depends on your role, and actions on lookups are written to the audit log.
No system is perfectly secure. If you believe your account has been used by someone else, tell us at privacy@htspilot.com.
12. Children
The service is a business tool and is not directed at children. We do not knowingly collect personal information from children. If you believe a child has sent us information, contact us and we will delete it.
13. Changes
If we change this policy we will update the date of the last update at the top. Where a change materially affects how we handle information we already hold, we will make a reasonable effort to tell the people affected.
14. Contact
Questions, requests or complaints: HTS Pilot, privacy@htspilot.com.