1. Scope and operator
This policy describes information handled by the Lines Tracking website at https://www.linestracking.com and the Lines Tracking browser plugin. It covers public searches, email verification, Google sign-in, private account features, and plugin connections. “Lines Tracking”, “we”, and “our” mean the operator of this service.
It does not cover a carrier’s website or another independent service after you leave Lines Tracking. Read the Terms of service for the conditions of using the Service and the limits of shipping information.
2. Information we handle
- Account and verification information. Your email address, account identifier and status, verification requests, code verification records, and timestamps. We send a verification code by email and store a hash of the code for verification.
- Google account information. If you sign in with Google, the email address on that Google account and Google’s indication that the address is verified. We do not receive your Google password or other Google account content.
- Saved tracking information. Tracking numbers, number types, selected carriers, notes, creation and update times, and the last recorded time you opened official tracking from a saved record.
- Favorites. References to ships, ports, routes, and voyages that you save, together with related account and timing information.
- Session and plugin information. Session identifiers, server-side credential hashes, expiration and revocation records, and the connection between an account, a session, and a plugin token.
- Requests and technical information. Search and identification inputs you submit, plus information exposed by web requests, such as IP address, browser or device details, requested URLs, and request times. Hosting and security providers may process operational logs.
A tracking number can reveal business or shipment information when combined with carrier records. Submit only information you are authorized to use. Notes are optional; avoid including sensitive personal information or unnecessary details about other people.
3. Google user data
If you sign in with Google, Lines Tracking uses Google OAuth and requests only the openid and email scopes. We receive the email address on that Google account and Google’s indication of whether the address is verified. We do not receive your Google password, contacts, calendar, Drive files, Gmail, or any other Google account content. We do not use Google Workspace APIs.
We use that verified email only to sign you in or to create a Lines Tracking account, to show the address on your account, and to send an account-closure code when you close the account. We store it as your Lines Tracking account email. We do not store a Google access token for later use of other Google services.
We do not sell Google user data or transfer it to data brokers, information resellers, or advertising networks. We do not use it for targeted, personalized, retargeted, or interest-based advertising, to determine credit-worthiness, or for lending. We do not use it to develop, improve, or train generalized or non-personalized artificial-intelligence or machine-learning models, and we do not use it to generate imagery. We do not send the Google account email to carrier-identification services.
Google receives the sign-in request so it can authenticate you. After that, the verified email is handled as the account email described in this policy. Hosting, email delivery, and security providers may process it only as needed to run the account, deliver a message you triggered, or protect the service. They are not permitted to use it for their own advertising or to train generalized models for Lines Tracking.
We protect it with access checks, hashed session and plugin credentials, expiration and revocation, and an HTTP-only session cookie that uses the secure flag on HTTPS. The email remains the account email while the account is active. Closing the account in Settings disables sign-in and revokes sessions and plugin tokens. That is how you request deletion of account access. Closed-account records may remain in storage and backups because the service uses logical deletion. They are not used to sign you in again, and they are not used for advertising or model training. Registering again with the same email creates a new account.
4. How and why information is used
We use this information to identify carriers and number types, respond to searches, provide public shipping information, authenticate users, maintain private lists and favorites, connect the plugin, record requested actions, prevent abuse, diagnose problems, and protect the Service.
Account emails are used for verification and account-related functions. An email address received from Google is used only to provide and secure the Lines Tracking account you requested. The account flow does not require a password, payment card, or a name. Do not send those details in a tracking note.
We do not use Google user data for advertising, to sell or license data, or to develop, improve, or train generalized or non-personalized artificial-intelligence or machine-learning models.
Where applicable data-protection law requires a legal basis, processing for requested account and tracking features is based on providing that service; security and reliability processing may rely on legitimate interests where permitted; required records may be processed to comply with legal obligations. Where consent is required for an optional activity, it must be obtained separately. Visiting the website is not blanket consent to unrelated processing.
5. Searches and official tracking
Public searches and carrier identification can be used without signing in. Submitted numbers and search terms are processed by our servers to respond to your request. A search is not added to your private tracking list unless you use a save feature while signed in. This does not mean the request is processed entirely on your device or excluded from operational logs.
If local matching cannot identify a carrier, the number may be sent to external identification services. Opening a carrier’s tracking entry may put the number into its URL, where the carrier receives it. Some entries require you to enter or paste the number on the carrier’s site.
Searches and tracking URLs can also remain in your browser history, clipboard, or the destination website’s records. Your browser controls and the destination’s policy govern those copies. Lines Tracking does not receive a carrier’s private cargo-status page merely because it opens that page.
7. Browser plugin data
When you select text and use the plugin’s right-click action, or submit a number in the plugin, that number is sent to the Lines Tracking identification endpoint. It may then be sent to an external identification service. The plugin then opens the Lines Tracking opening page and the carrier’s official tracking page. When that carrier page has a known form, the plugin writes this number into the form on the tab it opened. It does not copy the number to the clipboard, and it does not upload the carrier page.
On this device only, the plugin stores its connection token and account email when an account is connected, the API endpoint setting, and the most recently opened number and carrier. When you connect an account, the token authenticates supported account requests. The server stores a hash of the token, its associated account and session, and expiration or revocation information.
Plugin credentials are issued with an expiration of up to 90 days, but may stop working earlier if the linked session expires, you sign out of that session, the connection is replaced, or the account is closed. Removing the extension stops it running in that browser but does not itself close the website account or guarantee server-side token revocation.
Disconnecting clears the plugin’s local account email and connection token. The last-opened record and endpoint setting may remain until extension storage is cleared or the extension is removed. The plugin runs when you invoke it. It does not upload your browsing history or carrier cargo-status pages. Cargo status stays on the carrier site.
9. Retention and account closure
Saved numbers, notes, favorites, and account records remain available for account features while the account is active and the records have not been removed. Removing an item hides it from the active list; underlying records may remain because the current service uses logical deletion.
Verification codes expire after 10 minutes, can be used only once, and become invalid after repeated incorrect attempts. Expiration of a code or credential is different from deletion of its server-side record. Operational and security records may remain after access expires.
Closing the account in Settings disables access and revokes its sessions and plugin tokens. Saved tracking numbers and other account records may remain. Registering again with the same email creates a new account and does not restore access to the closed account’s lists. Account closure is not a request that immediately erases every record.
An account email, including an address received from Google, is kept for the account while it remains active. Verification codes stop working after 10 minutes. Sessions last up to 30 days, and plugin credentials last up to 90 days unless revoked sooner. Security and operational logs may be kept after that to prevent abuse and diagnose faults. Retained Google user data is not used for advertising or to train generalized models.
You request deletion of account access with Close account in Settings while signed in. Closing the account disables sign-in and revokes sessions and plugin tokens. Because records are removed from active use by logical deletion, copies may remain in storage and backups. Those copies are not restored when someone registers again with the same email.
You can clear browser history, clipboard contents, site cookies, and extension storage using the relevant device controls. These actions do not by themselves remove server-side account records or copies held by an independent carrier or provider.
10. Security and processing locations
We use measures such as email verification, access checks, credential hashing, expiration and revocation, and HTTPS-protected session cookies when the site is served over HTTPS. No internet transmission, browser, or storage system can be guaranteed completely secure. Protect your email account and devices, and do not share verification codes or connection credentials.
Hosting, email delivery, and security providers may process information in countries other than your own, under their own storage arrangements. Session cookies use the secure flag when the site is served over HTTPS. Google user data is limited to the verified email address described above, and it is protected with the same account controls.
11. Your choices and rights
You can search without an account, choose whether to save a number, edit or remove saved numbers and notes, remove favorites, sign out, clear local storage, remove the extension, or close your account. Removing access and deleting stored data have different effects, as described above.
Depending on the law that applies to you, you may have rights to access or obtain a copy of personal information, correct it, request erasure, restrict or object to processing, request portability, or withdraw consent for processing that relies on consent. These rights can have legal exceptions, and identity verification may be necessary. You may also be entitled to complain to your local data-protection authority.
Signed-in deletion of account access is Close account in Settings. Settings does not offer a self-service email change or a full-data export. The no-reply verification sender is not a privacy request channel. Do not send identity documents to that sender.
12. Children and other people’s information
The Service is designed for people handling container-shipping information and is not directed at children. Do not submit a child’s personal details or use a child’s email address to create an account. Any age or authorization requirements imposed by applicable law still apply.
If you submit information about a colleague, customer, consignee, or another person, you must have a lawful reason to do so and limit it to what is needed. The availability of a tracking number does not by itself give permission to disclose someone else’s information.
13. Updates and privacy contact
Changes to this policy are published on this page with an updated date. If Lines Tracking changes how it uses Google user data, this policy will be updated before that use begins. Material changes receive additional notice or a separate choice where applicable law requires it.
This policy belongs to Lines Tracking, the service at https://www.linestracking.com. A request to delete account access is made with Close account in Settings while you are signed in. The no-reply verification-email sender is not a privacy request channel.