ShieldPUBLIC INFORMATION / TRANSPARENT METHODS
Privacy policy
This policy describes the current Shield website operated by 蓝星工作室 (Lanxing Studio). Questions and requests can be sent through our private contact form. No email address is required to use that form.
Data we use and why
| Category | Purpose and handling | Retention |
|---|---|---|
| Account and saved watchlist | If you register, we store your email address, a salted password hash and saved watchlist. Plaintext passwords are not stored. Sign-in and saved-rule actions are recorded in a private audit history. | Account and watchlist records have no automatic age-based expiry. Contact us to request access, correction or deletion. Some append-only security and rule-history records may remain; we will explain applicable limitations. |
| Session cookie | A first-party HttpOnly session cookie supports signed-in features; the server stores a hash of its token. | Issued for up to 30 days. Signing out expires the browser cookie and ends the session. |
| Local preferences | Guest watchlists, alert review state, saved companies, company-update reading history, language and statistics preferences use browser storage. These are not advertising identifiers. | Until changed or cleared in this browser. Guest data is not automatically copied to another device. Company-update reading history stores source-item IDs and review times locally; clearing it starts a new baseline. |
| Optional statistics | After opt-in: a random browser identifier, public page path, referring domain, broad device category and timestamps. The server hashes the identifier. A signed-in visit can be associated with the Shield account. Search queries, ticket secrets and full referring URLs are not included. | Visits older than 90 days and presence records older than one day are removed during subsequent collection. Withdrawal stops future collection and clears the local statistics identifier; it does not itself erase earlier server records. |
| Contact tickets | Topic, subject, message, optional page URL, timestamps and operator reply. Only the operator and a holder of the private lookup link can read a ticket. The lookup secret is stored as a hash. | 180 days from creation, with removal on subsequent inbox operations. Private links then stop working. Contact us to request earlier removal. |
| Delivery and security | Hosting and web servers process request addresses and browser information to deliver the site and control abuse. Rate-limit identifiers are hashed and held in memory. Raw IP addresses are not stored in the analytics database; server access logs are separate. | Operational logs and backups follow the hosting configuration. Ask through the contact form about a specific request. Removal from live data does not instantly remove every backup. |
Your statistics choice
Statistics are disabled until you allow them. Rejecting them does not prevent market searches, research access or contact messages. We respect Global Privacy Control and Do Not Track signals for this optional collection.
Optional statistics are off unless you have allowed them.
Requests and private replies
Use the privacy topic in the contact form. State what you would like accessed, corrected or removed. Do not send passwords, card details or full identity documents. For an account request we may need to verify control of the account before changing data. Keep the private ticket link to read a reply. A browser-storage reset is not a server-account deletion request.
Who can receive information
Authorized operators can access account, message and statistics records to run the service. Hosting uses Alibaba Cloud infrastructure in the United States region used by this website. Opening an external source takes you to a third party with its own privacy practices. We do not sell personal data or publish contact tickets in a public feed.
Advertising and Google services
No Google advertising tags are installed in this version. The statistics choice controls Shield's measurement; it is not a Google-certified advertising consent platform. Before enabling Google advertising, the operator must add the applicable third-party disclosures and configure consent for the relevant regions and ad types. See How Google uses information from partner sites.
Updates
The date above records this policy version. Changes to optional collection must be reflected in both the implementation and visitor controls.