Privacy Policy
Last updated: September 20, 2026
AnalyticScan (the "Service") collects and uses personal information as described below when you sign up as a beta tester. The Service is currently in beta, and this policy may be updated as the product evolves toward general availability.
1. Information we collect
When you join the beta through our Google Form, we collect your email address, the URL of the site you'd like diagnosed, your role (marketer, analyst, developer, or other), and whether you currently use GA4. Details about your current data challenges are optional. When you submit a consulting inquiry, we collect your name, email address, company (optional), and message. When you run a scan, we collect the hostname of the site you're diagnosing and, if you choose to answer them, closed-option facts about that site (vertical, login/search/ads, where checkout finishes, main market, whether an internal-traffic filter is set up). If you subscribe to the newsletter, we record your email address along with the language of the page you subscribed from, which surface and which post it was (the end of an article, the blog index, or the notice at the bottom of the screen), and two consent timestamps — one for collecting and using the address, one for receiving advertising content — plus the version of the consent wording that was on screen at the time. Those are two separate checkboxes, neither ticked in advance, and both are required.
2. Why we collect it
We use this information solely to run the beta program, send free diagnosis reports, and understand demand so we can prioritize the right features. Waiting-list email addresses for the audits we are still building (Mixpanel, Amplitude) are used for one launch announcement only, and are deleted on request. A newsletter address is used only to send the newsletter — once or twice a month, covering GA4 data quality and news about AnalyticScan; because product news rides along we treat it as advertising and mark the subject line accordingly. We never move an address collected for something else (the waiting list, a diagnosis) onto the newsletter. The consent timestamps and wording version are kept solely as proof that consent was given.
3. Retention
Beta signup information is retained for the duration of the beta program and deleted promptly once it is no longer needed or upon your request. Newsletter subscriptions are kept until you unsubscribe; sending stops immediately at that point, and the record of your consent is kept for six months afterwards in case of a dispute, then deleted — or deleted at once if you ask. Every email carries an unsubscribe link that works without signing in. Retention for data collected by the diagnosis service is covered in section 6 below.
4. Google account and Google Analytics data
Signing in with Google gives us your email address and basic profile information. If you run a diagnosis, you grant read-only access to Google Analytics (analytics.readonly), and for the single GA4 property you choose we read: event names and counts, currency and total revenue for purchase events, daily event counts for the last 28 days, and the property's configuration (data streams, enhanced measurement, key events, custom dimensions and metrics, data retention, linked Google Ads and BigQuery). We do not request user-level records or personally identifying information.
5. How Google data is stored and used
So that you can reopen a diagnosis and download it as a report, we store the aggregated figures and configuration values we read, alongside the result. That includes the number of events recorded on each day of the 28-day window, and the same per-day counts for up to six of the property's busiest event names — this is what the report's volume chart is drawn from. It is whole-number counts and event names only: no individual visitor, session or page, and no revenue figures. These values are deleted with the diagnosis they belong to. Your Google refresh token is stored encrypted and is used only for the reads described above. AnalyticScan never creates, modifies, or deletes anything in Google Analytics, and requests no write scope. Data received from Google is never sold or transferred, never used for advertising, and never used to train AI models, in line with the Limited Use requirements of the Google API Services User Data Policy.
6. Retention and deletion
Diagnoses and the Google data stored with them are retained until you ask us to delete them or delete your account, at which point the associated records and stored tokens are deleted with it. You can revoke access at any time at myaccount.google.com/permissions; revoking prevents new diagnoses and does not affect results you already have. To delete individual diagnoses, write to support@analyticscan.com.
7. Processors and international transfers
We use the following processors to operate the service, each hosting data outside Korea: Supabase (database and authentication, Singapore), Vercel (web hosting, United States), Google LLC (Analytics API and sign-in, United States), Amplitude, Inc. (product usage analytics, United States), Mixpanel, Inc. (product usage analytics, United States), and Resend (Plus Five Five, Inc.) (email delivery, United States). They process only the data described in this policy and are contractually barred from using it for any other purpose. Amplitude and Mixpanel receive how this site is used — pages opened, buttons clicked, which step of the diagnosis or purchase was reached — together with your account identifier; they never receive your email address or name, nor any of your GA4 data.
8. Third parties
We do not share your personal information with third parties, except where required by law.
9. Contact and data protection officer
Questions about this policy, and requests to access, correct, or delete your data, can be sent to support@analyticscan.com. The data protection officer is Taehan Lee.
10. How we protect your data
The following safeguards apply to sensitive data. Encryption in transit: all traffic between your browser and the service, and between the service and Google's APIs, runs over HTTPS (TLS) only. Encryption at rest: your Google refresh token is stored encrypted with AES-256-GCM, and the decryption key is supplied only as a server environment variable held separately from the database. Access tokens are never stored — they exist in memory for the length of a request. Access control: tables holding personal data have row-level security enabled and the public roles (anon, authenticated) revoked, so only the server's trusted role can read or write them. Operator screens sit behind separate authentication, and irreversible actions such as deletion are written to an audit record with who did it and when. Minimal collection, immediate disposal: we request read-only scopes for Google Analytics and Tag Manager, and never request or build the ability to change your configuration. Raw API responses exist only in memory inside the diagnostic function and are discarded once the verdicts are computed; what remains is the verdicts and aggregate figures (sections 4 and 5). Values that could identify a person are counted when detected but never stored. API response bodies are not written to server logs. Revoking access: you can withdraw this service's access at any time from your Google Account settings, after which it can no longer read anything.