Think2Brief — Marketing
Summary

The Chrome extension uses no developer account or server, analytics, or advertising trackers. It uses Google account authentication and Google Drive save/open features only when you choose them. Project data is never sent to the developer. Website visit analytics and the dedicated Drive file-picker page operate differently — see items 4 and 8.

01

Scope and operator

This privacy policy applies to the Chrome extension Think2Brief — Marketing, provided by Hongseok Ko (talkspinout). Questions about the product website go to think2brief@gmail.com.

02

Information the extension processes

The extension processes the following information, entered or created by you, inside the browser in order to provide its features.

  • Project title and author display name
  • Campaign goal and audience
  • The content of decision, evidence, insight, strategy, activity, and measurement cards
  • Card status, whether a card is included in the brief, logic notes, and drafts in progress
  • Project identifiers, creation and update timestamps, and the data schema version

The author display name and free-text content may include personal or work-related information depending on what you choose to enter. We recommend not entering sensitive or unnecessary personal information.

03

Purpose and storage location

The information above is used only to provide the following features.

  • Autosaving and recovering the project you're working on
  • The work board, strategy review, logic review, and final brief generation
  • JSON, Markdown, or print/PDF export that you request

Autosaved data is stored in localStorage scoped to the Chrome extension. Exported files are saved to a location you choose on your device, and you are responsible for managing them afterward.

04

Collection, transmission, and third parties

Collected on a developer serverNone
Sent to an external serviceGoogle Drive, when you choose
Analytics or ad trackingNone
Developer user accountsNone

This table describes the Chrome extension. When you choose to save to or open from Google Drive, a Google OAuth token and the selected project file are sent to Google. Access is limited to files this app creates or that you explicitly select. No data is sent to Notion, an LLM API, or a developer server, and the developer does not collect, view, or sell your projects. See item 8 for website analytics.

05

Chrome permissions

The extension uses Chrome's identity permission and Google Drive's drive.file scope for Google account authentication. Permission is requested when you use a Drive feature, and does not allow the extension to browse your entire Drive or arbitrarily read files created by other apps. It cannot access your browsing history or the content of other tabs.

Use and transfer of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.

06

Retention and deletion

Autosaved data remains in that browser until you run Clear saved data inside the extension, or clear the extension's data through Chrome.

JSON, Markdown, or PDF files you save separately are not deleted by the extension's Clear saved data feature. Google Drive files are also not deleted when you disconnect Drive. You must delete those files yourself.

07

Security and your choices

Project files are transmitted to Google over encrypted HTTPS only when you choose a Google Drive feature. The OAuth token is never placed in a URL, web storage, or a developer server; it is handled temporarily in browser memory during file selection. You are responsible for securing access to your device account, Chrome profile, Google account, and exported files.

08

Product website

The product introduction and this privacy policy are hosted on GitHub Pages. While you're visiting the website, GitHub may process technical information such as access logs, which is subject to the GitHub Privacy Statement.

This website uses Google Analytics 4 through Google Tag Manager to understand visits and improve the site. This may process pages visited, feature-use events, device and browser information, an approximate region derived from the IP address, and cookies or similar identifiers. Project, card, and brief content entered in the Chrome extension is never included in website analytics. The information is sent to Google and is subject to the Google Privacy Policy. You can limit collection through your browser cookie settings or the Google Analytics opt-out browser add-on. You can decline analytics on the consent screen shown on your first visit and change your choice anytime through “Analytics settings” in the footer. Google Tag Manager and Google Analytics are not loaded before you consent.

The Chrome extension operates separately from this website: it does not include Tag Manager and uses no analytics tools. The dedicated Drive file-picker page at /drive-picker/ also has no Tag Manager or analytics. Its URL never contains an OAuth token, project content, or a unique project identifier. It receives only a one-time handshake value and the extension origin; the token is sent by browser messaging only after the origin, popup window, and handshake value are verified.

09

Future features and policy changes

If our data practices change, we will disclose the changed data types and purposes in advance through this privacy policy and inside the extension. We will not process any newly collected or used data before you explicitly consent. We will also update the Chrome Web Store's privacy disclosures before shipping any such change.

Material changes are shown on this page with an updated effective date and policy version.

10

Contact

For questions about data processing or deletion, contact think2brief@gmail.com.