Privacy Policy

Effective: April 22, 2026

Slowthought STL Inc. ("the Company") establishes and publishes this Privacy Policy to protect the personal information of users in accordance with the Personal Information Protection Act of Korea and to handle related grievances promptly and smoothly.

No Visitor Data Retention Principle

The Company does not store on its servers the individual visitor data (raw events, user_pseudo_id, client_id, individual session records, etc.) from the GA4 properties and GTM containers connected by users. Such data is retrieved in real time via Google APIs only at the moment a user issues a query, used for analysis, and discarded from memory immediately after the response. What the Company stores is limited to the user's chat history and the aggregated analytical results contained therein.

Article 1 (Categories of Personal Information Collected and Methods of Collection)

The Company collects the following personal information for the provision of the Service.

CategoryItems CollectedCollection Method
Account (Required)Email address, name (Google profile), Google profile image URLAutomatically collected on Google OAuth sign-in
Service ConnectionGoogle OAuth access/refresh tokens (encrypted at rest), connected GA4 property IDs/names, connected GTM container IDs/namesAt the time the user authorizes the GA4/GTM connection
Shopify Connection & Storefront BehaviorShopify app access token (stored encrypted), connected store domain/name/plan. When you connect a store, Maron installs a web pixel on it and collects visitor behavior events (page views, product views, add to cart, checkout steps, purchase): event type, time, page path, referrer host, product name and amount, and an anonymous per-browser visitor identifier. Names, email addresses, postal addresses, phone numbers, payment details and search terms are not collected. Store data such as orders and sales is fetched from the Shopify API only at query time and not storedFrom the moment you approve the Maron app in your Shopify admin; collected automatically on storefront visits
TikTok ConnectionTikTok for Business access token (stored encrypted), authorized ad account IDs/names/currency, TikTok user ID/email. Ad performance data is fetched from the TikTok Marketing API only at query time and not storedWhen you approve the ad account connection on the TikTok for Business authorization page
Pinterest ConnectionPinterest access and refresh tokens (stored encrypted), accessible ad account IDs/names/currency, Pinterest user ID/username. Ad performance data is fetched from the Pinterest API only at query time and not storedWhen you approve Maron access on the Pinterest consent screen
X (Twitter) ConnectionX OAuth 1.0a access token and token secret (stored encrypted), accessible ad account IDs/names/currency, X user ID/handle. Campaign and ad performance data is fetched from the X Ads API only at query time and not stored; campaign status and budget changes are made only on your instructionWhen you approve Maron access on the X app authorization screen
Klaviyo ConnectionKlaviyo OAuth access and refresh tokens (stored encrypted), Klaviyo account ID, organization name, website, timezone, currency and granted scopes. Names and settings of campaigns, flows, lists, segments and templates and aggregate performance statistics (recipients, opens, clicks, conversions, revenue) are fetched from the Klaviyo API only at query time and passed to your AI client; they are not stored. Profile (per-person email, phone) and event scopes are not requested.When you approve Maron access on the Klaviyo app authorization screen
Microsoft Advertising ConnectionMicrosoft account OAuth access/refresh tokens (stored encrypted), Microsoft Advertising user ID/email, accessible ad account IDs/names/numbers/currency. Campaign and performance data is fetched from the Microsoft Advertising API only at query time and not storedWhen you sign in with your Microsoft account and grant Maron access to Microsoft Advertising (msads.manage)
Amazon Ads ConnectionLogin with Amazon OAuth access/refresh tokens (stored encrypted), Amazon user ID/email, accessible advertising profile IDs/names/countries/currencies/account types. Campaign and performance data is fetched from the Amazon Ads API only at query time and not storedWhen you sign in with your Amazon account and grant Maron access to Amazon Ads (advertising::campaign_management)
Adobe Analytics ConnectionThe Adobe Developer Console OAuth credential you enter (Client ID and Client Secret — the secret is stored encrypted), Adobe IMS access/refresh tokens (stored encrypted), Adobe user ID/email, accessible companies (login companies) and report suite IDs/names. Report and metric data is fetched from the Adobe Analytics API only at query time and not storedWhen you enter the credential in the dashboard, sign in with your Adobe account and grant Maron access to Adobe Analytics
YouTube Data (Google Connection)YouTube channel IDs/titles/handles accessible through the Google connection you authorize. Channel analytics (views, watch time, subscribers, traffic sources, devices, demographics; revenue metrics only for YouTube Partner Program channels) and video details/public statistics are fetched from the YouTube APIs only at query time and not storedWhen you connect a Google account and grant YouTube read access (youtube.readonly, yt-analytics.readonly, yt-analytics-monetary.readonly)
Search Console Data (Google Connection)Search Console property URLs and permission levels accessible through the Google connection you authorize. Search performance (clicks, impressions, CTR, average position by query, page, country, device), sitemap status and URL index status are fetched from the Search Console API only at query time and not stored. The only write is submitting a sitemap when you ask for it (Maron never deletes sites or sitemaps)When you connect a Google account and grant Search Console access (webmasters)
Merchant Center Data (Google Connection)Merchant Center account IDs/names accessible through the Google connection you authorize. Product information, product status and issues, and shopping performance reports are fetched from the Merchant API only at query time and not stored (Maron tools only read; they never change products or accounts)When you connect a Google account and grant Merchant Center access (content)
ChatGPT Ads (OpenAI) ConnectionThe ChatGPT Ads Manager API key you enter (stored encrypted), ad account ID/name/brand/currency/status. Campaign and performance data is fetched from the OpenAI Advertiser API only at query time and not storedWhen you paste an API key in the dashboard (Connections)
Service UsageChat session and message history, conversation summary/preference memory, prompt logs, feedback, token usageAutomatically generated during Service use
BillingSubscription plan, status and period, transaction IDs, payment amounts, payment method type, recurring-billing keys (encrypted at rest)Received from the payment processor on paid checkout
AutomaticIP address, browser type, access time, request pathAutomatically collected during Service use

* The Company does not collect or store website-visitor personal data such as raw GA4 events, user_pseudo_id, client_id, or individual visit records from the GA4 properties connected by users.

* GA4P uses YouTube API Services. By using the YouTube features you agree to the YouTube Terms of Service, and YouTube data is subject to the Google Privacy Policy.

Article 2 (Purposes of Use)

The Company uses the collected personal information for the following purposes.

  • Service provision and operation: member identification, GA4 data analysis, GTM configuration automation, AI-based insight delivery
  • Payment processing: subscription billing, recurring billing, refunds
  • Service improvement: usage analytics, AI response quality enhancement
  • Customer support: responding to inquiries, delivering notices
  • Legal compliance: meeting obligations under applicable law

Article 3 (Retention and Use Periods)

After the purpose of collection and use has been achieved, the Company destroys the relevant information without delay.

  • Member information: until withdrawal (destroyed immediately upon withdrawal)
  • Google OAuth tokens: stored AES-encrypted; destroyed immediately upon user disconnection or withdrawal
  • Connected GA4 property / GTM container metadata: until the user disconnects or withdraws
  • Shopify access token and store metadata: stored AES-encrypted; destroyed immediately when the user disconnects the store in the dashboard (Connections), uninstalls the app in Shopify, or withdraws
  • TikTok access token and ad account metadata: stored AES-encrypted; destroyed immediately (and revoked at TikTok) when the user disconnects TikTok in the dashboard (Connections) or withdraws
  • Pinterest tokens and ad account metadata: stored AES-encrypted; destroyed immediately when the user disconnects Pinterest in the dashboard (Connections) or withdraws. Pinterest does not offer a token-revocation API for apps, so the user can also remove Maron under Pinterest Settings → Security → Connected apps
  • X tokens and ad account metadata: stored AES-encrypted; destroyed immediately when the user disconnects X in the dashboard (Connections) or withdraws. X does not offer a token-revocation API for OAuth 1.0a apps, so the user can also remove Maron under x.com Settings → Security and account access → Apps and sessions
  • Klaviyo tokens and account metadata: stored AES-encrypted; destroyed immediately when the user disconnects Klaviyo in the dashboard (Connections) or withdraws, and the refresh token is revoked at Klaviyo.
  • Microsoft tokens and ad account metadata: stored AES-encrypted; destroyed immediately when the user disconnects Microsoft in the dashboard (Connections) or withdraws. App permission can also be revoked at https://account.live.com/consent/Manage
  • Amazon tokens and advertising profile metadata: stored AES-encrypted; destroyed immediately when the user disconnects Amazon in the dashboard (Connections) or withdraws. App permission can also be revoked at amazon.com → Your Account → Login with Amazon
  • Adobe credential, tokens and report suite metadata: stored AES-encrypted; tokens are destroyed immediately when the user disconnects Adobe in the dashboard (Connections), and the credential as well when the user withdraws. Approval can also be revoked under Connected applications at account.adobe.com
  • YouTube channel metadata (ID, title, handle): kept only in the connection snapshot that is refreshed daily (never kept for more than 30 days without refresh); destroyed immediately when the user disconnects the Google account or withdraws. Access can be revoked at any time in Google security settings (https://security.google.com/settings/security/permissions)
  • ChatGPT Ads API key and ad account metadata: stored AES-encrypted; destroyed immediately when the user disconnects in the dashboard (Connections) or withdraws. The key can also be revoked by the user in OpenAI Ads Manager
  • Shopify storefront behavior events (web pixel): kept for 90 days from occurrence, then deleted automatically; deleted immediately in full when the store is disconnected. Used only to provide funnel analysis to the user's AI client
  • Raw GA4 event data: not stored — fetched in real time from Google APIs only at query time and discarded from memory immediately after the response
  • Chat history and memory: destroyed upon withdrawal or user request
  • Payment records: retained for 5 years under applicable laws (e.g., the Act on the Consumer Protection in Electronic Commerce), then destroyed
  • Recurring-billing keys: stored encrypted; destroyed immediately upon subscription cancellation or withdrawal
  • Access logs: retained for 3 months, then destroyed (per the Protection of Communications Secrets Act)

Article 4 (Provision of Personal Information to Third Parties)

In principle, the Company does not provide users' personal information to third parties. The following are exceptions.

  • Where the user has given prior consent
  • Where required by law

Article 5 (Outsourcing of Personal Information Processing)

For smooth Service delivery, the Company outsources personal information processing as follows.

Sub-processorEntrusted WorkRetention
Vercel Inc.Frontend web hosting (static asset delivery)For the duration of Service use
Fly.io (Fly Services Inc.)Backend application hostingFor the duration of Service use
Supabase Inc.Database storage and management, authentication, embedding processing (Edge Functions)For the duration of Service use
Google LLCOAuth authentication, GA4 Data/Admin API, GTM API integrationFor the duration of Service use
Anthropic PBCAI processing (Claude API)Only at the moment of query processing (results not retained)
KG Mobilians Co., Ltd.Credit card / simple payment / mobile payment processing and recurring billingRetention as required by applicable law

If sub-processors change, the Company will provide advance notice through this Privacy Policy.

Article 6 (Data Processing Agreement (DPA))

  1. When a user connects a GA4 property or GTM container for which they hold rights to the Service, the user is the Controller of the website-visitor information collected through that property/container, and the Company acts as the user's Processor, handling such information solely for the analytical purposes entrusted by the user.
  2. By agreeing to the Terms of Service and this Privacy Policy, the user is deemed to have entered into a Data Processing Agreement (DPA) with the Company as required by Article 26 of the Personal Information Protection Act of Korea and Article 28 of the GDPR.
  3. As a Processor, the Company observes the following:
    • Processing only within the scope of purposes specified by the user (GA4 analysis / GTM configuration)
    • Not permanently storing individual visitor raw data in any separate datastore (see Article 3)
    • Sub-processing only with the sub-processors listed in Article 5 and only to the minimum extent necessary
    • TLS encryption in transit and encryption at rest for sensitive information
    • Notifying the user without undue delay in the event of a personal-data breach
    • Upon termination of the entrustment relationship, destroying or returning user-related data
  4. Where website visitors (data subjects) managed by the user wish to exercise rights to access, deletion, or restriction of processing of their personal data, the primary obligation to respond rests with the user; the Company will cooperate with the user's request when made.
  5. Enterprise customers requiring a separate signed DPA may, in lieu of paragraph 2 of this Article, execute the Company's separate DPA form, which will prevail in such case. Please direct requests to help@stlabs.co.kr.

Article 7 (Destruction of Personal Information)

  1. When personal information becomes unnecessary — due to expiry of the retention period, achievement of the processing purpose, etc. — the Company destroys it without delay.
  2. Information held in electronic files is permanently erased in a manner that prevents recovery; printed personal information is shredded or incinerated.

Article 8 (User Rights and How to Exercise Them)

  1. Users may at any time request access to, correction of, deletion of, or restriction of processing of their personal information.
  2. Rights may be exercised through the in-app settings page or by email at help@stlabs.co.kr; the Company will act without delay.
  3. Where a user requests deletion of personal information, the Company will destroy such information without delay.

Article 9 (Measures to Ensure the Security of Personal Information)

The Company implements the following measures to ensure the security of personal information.

  • Data encryption: SSL/TLS encryption in transit; sensitive information such as OAuth tokens and billing keys are stored AES-encrypted
  • Access controls: access to systems that handle personal information is restricted to the minimum necessary personnel
  • Access-log retention: access records to personal-information processing systems are retained for at least one year
  • Data minimization: collecting only the minimum information necessary to provide the Service; visitor raw data is not stored

Article 10 (Privacy Officer)

The Company designates the following Privacy Officer to oversee personal-information processing.

Name: Chansung Park

Title: CEO

Email: help@stlabs.co.kr

Article 11 (Changes to this Privacy Policy)

This Privacy Policy takes effect on the date stated above. Any changes will be announced through in-Service notices.

Article 12 (Remedies for Infringement of Rights)

Users in Korea may contact the following authorities for relief from personal-data infringements:

  • KISA Privacy Infringement Reporting Center: 118 (within Korea)
  • Personal Information Dispute Mediation Committee: 1833-6972
  • Supreme Prosecutors' Office Cybercrime Investigation: 1301 (within Korea)
  • Korean National Police Cyber Bureau: 182 (within Korea)

Supplementary Provisions

This Privacy Policy is effective as of April 22, 2026.

For the legally binding Korean original, see /ko/privacy. In the event of any discrepancy, the Korean original prevails.