Research Studio Privacy Policy
Effective date: October 16, 2026
Liquid Creative Studio LLC (‘Liquid Creative,’ ‘we,’ ‘us,’ or ‘our’) provides Liquid Creative Research Studio (‘Research Studio’), an internal marketing research and planning application intended for authorized Liquid Creative personnel. This policy describes the current local prototype and the planned Google Ads, Google Drive, and AI research integrations. The current prototype does not connect to Google accounts or make live AI provider API calls. Integrations described as planned will be enabled only after their access, data handling, and applicable terms have been reviewed. Research Studio is intended to run locally on authorized agency computers. The public pages on liquidcreativestudio.com describe the app; the website does not host the app or collect its research data. This policy covers the app and its report workflow. Information about cookies on our website is available in our Cookie Statement.
1. Information we handle
Business and project information. Research Studio may store business names, public website addresses, industry and service descriptions, target markets, project objectives, imported keyword data, page-planning information, research notes, and generated recommendations.
Authorized Google account and Google Ads information. When the Google Ads integration is activated and a user grants access, we expect to process the information necessary to authenticate an authorized Google user and access permitted Google Ads accounts, including relevant account identifiers and keyword-planning results such as keyword ideas, historical search demand, competition metrics, and bid estimates. The precise OAuth scopes and fields will be limited to those required for the enabled features and reviewed before launch.
Research reports. Reports may contain project information, research findings, keyword metrics, and recommendations. The planned Google Drive integration will save report files directly from Research Studio to Google Drive. Reports will be shared with the relevant client and retained for ongoing copy development and strategy. The implementation plan uses Google Drive’s per-file permission (drive.file) to create reports and work with files specifically authorized for Research Studio. The permissions actually requested will be checked against this plan before the connection is enabled.
AI visibility testing information. Planned tests may send research prompts, public business names and website addresses, service descriptions, market context, and relevant public website excerpts to supported AI provider APIs. The initial automated visibility tests are planned to use public business information only. Separate copy or strategy work may use client-approved business briefs where permission and provider terms allow. Subject to applicable provider and source-content terms, Research Studio will record the prompt, provider, model, test method, date and time, returned answer and citations, and observations about client and competitor mentions. API results will be distinguished from separately verified observations in consumer AI services.
Technical and operational information. The current prototype suppresses routine HTTP request logging. The implementation plan for connected features is to keep minimal diagnostic metadata, such as timestamps, provider names, status/error codes, and usage counts, for up to 30 days. Diagnostic logs are not intended to include research prompts, report content, passwords, API keys, or Google authorization tokens. Research evidence intentionally saved with a project is part of that project record, rather than a diagnostic log. These planned logging controls will be checked before live integrations are enabled.
2. Why we use the information
We use Research Studio information to organize internal client and prospect research, prepare advertising plans, analyze keyword and geographic opportunities, develop website copy, advertising copy, and marketing strategy, compare and track AI visibility through the planned testing features, prepare client reports, and maintain the service. Data received through the Google Ads API will be used for authorized Google Ads-related research, campaign planning, targeting, budgeting, reporting, or optimization, subject to Google’s applicable policies and the client’s permissions. We do not use authorization to access accounts that Liquid Creative is not permitted to manage or analyze.
3. Google account authorization and access
Research Studio does not have a separate application login or app username and password. Google Ads and Google Drive connections require Google account authorization. When these integrations are enabled, an authorized user will connect through Google’s OAuth authorization process and review requested permissions. The application will use the resulting authorization only for the approved features and permitted Google Ads accounts and Google Drive files. Google authorization uses access tokens and may use refresh tokens to maintain the connection; these are separate from an application login. The approved implementation plan is to keep persistent Google authorization tokens in the operating system’s secure credential store, using macOS Keychain on Macs, and to keep tokens out of report files, Google Drive, source code, and diagnostic logs. Each staff member’s Google authorization is intended to be separate. A planned Disconnect Google control will revoke the app’s grant and remove locally stored tokens without deleting saved reports. These controls describe features still to be built and tested before live Google connections are enabled. Users may revoke permissions through their Google Account. Revoking authorization will stop future access through that grant, although information already lawfully retrieved and reports saved in Google Drive may remain in long-term client records as described below.
4. Storage, security, and access controls
Research Studio is intended to run locally on authorized Liquid Creative personnel’s computers. The current prototype uses a local application database for project information. Research reports will also be stored in Google Drive as part of Liquid Creative’s reporting workflow. Local application storage and Google Drive report storage are separate from the public WordPress website.
The local application has no separate application login, so access depends on the computer’s user account and device controls. The implementation plan requires agency-approved devices, operating-system access controls and disk encryption, API keys and persistent authorization tokens in the operating system’s secure credential store, and report sharing limited to the relevant staff and client. API requests will be made by the local application backend; keys will not be embedded in the browser interface. These controls and the selected Google Drive folders and sharing permissions will be checked before live integrations are enabled. The current prototype does not provide an application-managed backup service. Copies may exist in device backups or Drive version-history and backup systems used by Liquid Creative, with retention governed by those systems’ settings.
5. Sharing and third-party services
Research Studio is intended for Liquid Creative’s authorized personnel. Clients will receive reports and related deliverables rather than access to the internal application. Research reports will be stored in Google Drive and shared with the relevant client. Liquid Creative will use the research and report findings to develop website copy, advertising copy, and marketing strategy for that client. Sharing reports with a client does not grant that client access to other clients’ information.
Google Drive is planned for report storage and sharing. OpenAI, Anthropic (Claude), and Perplexity are planned AI providers. These integrations are not yet active in the prototype. A provider enabled for a test will receive the selected prompt and included research context. Initial automated visibility tests will use public business information. Report storage in Drive does not authorize sending entire Drive files or account contents to AI services. Private Google Ads account data and other nonpublic Google-derived information are excluded from the initial AI testing workflow.
OpenAI. The planned integration uses the Responses API with web search where appropriate. OpenAI states that API data is not used for model training unless the customer opts in. Standard abuse-monitoring logs may retain content for up to 30 days, with legal and safety exceptions. The implementation plan uses store=false to reduce response storage; this does not eliminate all retention, including abuse-monitoring logs and feature-specific caching. See OpenAI’s API data controls.
Anthropic (Claude). The planned integration uses the Claude Messages API with its web search tool where appropriate. Anthropic states that commercial API inputs and outputs are not used for model training by default. Its standard commercial retention policy provides for deletion within 30 days, subject to feature-specific storage, separate agreements, safety enforcement, and legal exceptions. Research Studio will not opt project content into training or submit it as provider feedback. See Anthropic’s training policy and commercial retention policy.
Perplexity. The planned integration uses the Agent API with supported web-search features. Perplexity states that customer API content is not used to train generative AI models by default. Retention depends on the API, underlying model provider, and account configuration. Zero data retention requires an eligible account and a written agreement; it is not the default. The Agent API’s store=false option does not prevent server-side persistence. Results will identify the actual model used, which may be supplied by a third party. The first-release configuration will limit routing to reviewed providers and models and disable unapproved model fallbacks. Only public business information will be used initially; nonpublic inputs remain excluded pending review of the account’s applicable terms and retention. See Perplexity’s API privacy and security guidance and storage behavior.
AI and search providers may process requests through their underlying model providers, search services, and subprocessors under their applicable terms. Research Studio will identify the provider, model, and method in saved test records, retain required source attribution, and distinguish API tests from verified consumer-service observations. We do not promise that all providers apply zero data retention. Liquid Creative will review enabled products and account settings before use and update this policy as needed.
Passwords, authorization tokens, API keys, customer lists, patient information, and unrelated client materials are excluded from AI inputs. Google Ads API data will not be sold or disclosed to unrelated parties for their own advertising or marketing. Any later transfer of nonpublic client information or Google-derived data to an AI provider requires a separate permissions and terms review. Staff will review research findings and generated copy before client use.
6. Retention and deletion
The reporting plan is to retain client and prospect research reports in Google Drive on an ongoing, long-term basis to support future website copy, advertising copy, marketing strategy, and related work. Reports will not have an automatic deletion or expiration schedule. Source material or provider output with incompatible retention or reuse restrictions will be excluded from these long-term reports. Provider-side retention is separate from Liquid Creative’s report retention and is described above.
Questions about retained information, access, correction, or deletion requests can be sent to [email protected]. We will review requests in light of applicable client obligations and contractual, security, or legal requirements. Revoking Google authorization stops future access through that grant but does not automatically delete reports already saved in Google Drive or copies previously shared with a client.
The local prototype retains project records until they are deliberately removed; it has no automatic expiry schedule. The plan for connected features is to retain diagnostic metadata for up to 30 days and persistent authorization credentials only while the connection remains authorized and needed, removing them on disconnection or revocation once detected. Device backups and Drive history may retain copies under their own settings. The planned controls will be tested before live integrations are enabled.
7. Your choices and privacy requests
Authorized users can control Google authorization through their Google Account. For questions about Research Studio information, access, correction, or deletion, email [email protected] and reference ‘Research Studio Privacy.’ You may also use the Liquid Creative contact page.
8. Changes to this policy
We may revise this policy as Research Studio’s capabilities or data practices change. Material changes to Google user data access, use, storage, or sharing will be reflected here and communicated to affected users before we begin using that data in a materially different way when required.
9. Contact
Liquid Creative Studio LLC
Website: Liquid Creative
Contact: Contact Liquid Creative
Email: [email protected]
