ACIS RESEARCH · ACIS ANALYTICS
Privacy Policy
Effective and last updated: 2 November 2026
How we handle enquiries, subscriptions, website analytics and authorized Google Search Console data.
1. Optional voice input
If you choose voice input and grant microphone permission, browser or operating-system speech services may process audio to produce text. Our site code does not store raw recordings. Transcripts enter the form and, if submitted, are handled as enquiry content. Keyboard input remains available.
2. Who operates this website
This policy covers acisresearch.com, operated as ACIS Research, and its operator-facing ACIS Analytics / ACIS Analytics GSC search-performance features. The privacy contact is Yolanda Tang: yolandatgy2018@gmail.com.
3. Enquiries, subscriptions and research feedback
For enquiries, we store the name, region, contact details, consultation type, preferred time, message, language and source you submit to respond and follow up. A diagnosis summary is submitted only when you choose to include it; it contains bands and a brief summary, rather than automatically submitting full asset inputs. Subscription records include email, language, topics, status, source page and timestamps. Research feedback may be linked to a subscription. We use these records for requested communications, research emails and preference management; subscription emails are not linked to anonymous browsing analytics. Do not submit identity documents, passwords, full account numbers or complete financial records.
4. Analytics and browser storage
Our first-party analytics records page views, source categories or domains, landing pages, country or region, device class, language and reading or subscription-entry events. localStorage holds language preferences, a random visitor identifier and a returning marker; sessionStorage holds session and source information and optional diagnosis handoff summaries. Persistent storage may remain until you clear site data; session storage normally ends with the tab session. Server analytics stores hashed identifiers and aggregates. Request analytics temporarily uses IP address and User-Agent to derive time-bucketed hashes; business analytics tables do not store full IP addresses. These are pseudonymous estimates, not a guarantee of anonymity. We currently use neither advertising tracking cookies nor Google Analytics. Do Not Track disables the relevant browser event tracking, but not network processing needed to deliver pages or platform security logs.
5. Google Search Console data
ACIS Analytics GSC requests only https://www.googleapis.com/auth/webmasters.readonly from an authorized website operator. It verifies accessible Search Console properties and permissions and reads impressions, clicks, CTR, average position and query, page, country, device and date breakdowns for internal reporting and website improvement. Ordinary visitors do not need to authorize a Google account. This policy does not imply that GSC is connected: data is shown only after successful queries; failures or empty results are not represented as real zeroes. Google data is not used for advertising, sale, credit assessment or training general-purpose AI models, nor matched to subscriber emails. Raw search reports are for authorized operators, not public publication.
6. Google data storage, revocation and deletion
OAuth client secrets and refresh tokens are stored as server-side secrets, not in frontend code or public source; access tokens are used for server requests. GSC supports on-demand reports and operator-enabled daily collection. Daily collection stores Google aggregates, dimensional reports, date windows and success or failure status in the server database for internal historical comparison and diagnostics. Successful records are not duplicated for the same Shanghai day. Records remain for these purposes until removal is requested; there is currently no uniform automatic-expiry deletion job. Credentials remain while needed for the connection until removed. Operators can revoke ACIS Analytics in their Google Account third-party connections and request removal of server credentials and any retained Google data under our control through the privacy email. Revocation stops new authorized reads and does not delete data held by Google Search Console itself. Our use and transfer of Google API data adheres to the Google API Services User Data Policy, including its Limited Use requirements.
7. Service providers and international processing
The site uses Sites hosting and Cloudflare infrastructure for requests and business databases, Resend for email delivery (recipient address, message content and delivery status as needed), and Google for OAuth and Search Console queries. Infrastructure providers may process network identifiers and logs for delivery, security and diagnostics under their applicable policies. External WeChat, WhatsApp and email communications are also governed by those providers' policies. Processing may occur outside your country. We do not sell personal information or Google data; necessary disclosures are limited to requested functionality, security, applicable legal requirements or your authorization.
8. Retention and security
Enquiry, subscription, feedback and analytics records are retained for the relevant service, historical analysis, security and necessary record keeping. The current business system has no uniform automatic-expiry deletion job. Unsubscribing changes subscription status rather than automatically erasing historical records. You may request deletion; we assess identity and any necessary retention and explain applicable limits. Provider logs and backups may remain through their retention cycles. HTTPS, server-side authorization and secret configuration help limit access; no system can be guaranteed absolutely secure.
9. Your choices and contact
Use management or unsubscribe links in emails to change subscriptions, clear browser site data to reset local identifiers, or omit optional information. Contact yolandatgy2018@gmail.com to request access, correction, deletion or withdrawal of authorization; do not send passwords, tokens or full identity documents. Pseudonymous analytics may not be reliably attributable to an individual. Clearing browser storage does not automatically erase server records. Requests are handled under applicable rules. Policy changes update this page's date; new Google-data purposes or permissions require updated disclosures and the necessary authorization first.