Meeting Preparation Workspace Privacy
Meeting titles, schedules, notes, agendas, participants, links, explicitly captured page metadata, templates and imported calendar cache stay in the user's local Chrome extension storage.
Only the extension identifier, license key, locally generated instance name, and server-issued instance ID are sent to CodingFrontend in POST JSON bodies for activation, validation or deactivation.
CodingFrontend owns checkout and payment-provider integration. The extension never handles card data or calls checkout directly.
No analytics, advertising, browsing-history access, content scripts, hosted AI, sale of data or tracking telemetry is included.
Google receives OAuth and Calendar API requests only after the user enables the optional integration; tokens and imported event details remain in local extension storage.
Licensing
For Pro activation, the license key and a user-readable browser instance name are sent over HTTPS to CodingFrontend and Dodo Payments. The CodingFrontend database stores a keyed hash of the license key, the Dodo instance ID, product association, and validation timestamps—not the raw key.
Payments
Checkout is hosted by Dodo Payments. CodingFrontend never embeds payment credentials in the extension and does not treat the checkout return page as proof of purchase.
Contact
Questions can be sent through the CodingFrontend contact page.