EtchDeck Collector

EtchDeck Collector has one purpose: let an EtchDeck user collect text or an image they deliberately choose on a webpage and save it as a private EtchDeck memory card. DATA USE BEFORE INSTALLATION EtchDeck Collector handles only the data needed for that purpose: - Authentication information: an EtchDeck API Key that the user creates in the EtchDeck web app and pastes into the extension. It is encrypted and stored privately in the extension's own browser storage, then sent only to EtchDeck over HTTPS for authentication. - Website content and browsing context: only text or images the user deliberately chooses, the edited card content, a cleaned source URL, and the user's private card-group IDs/names needed to choose a destination. Selected text is sent to EtchDeck when the user clicks the text capture button so the extension can find an exact private match and load card groups. A chosen public image is fetched without website cookies and sent to EtchDeck only when the user presses Save; if that fetch fails, a visible-tab crop is uploaded only after the user explicitly chooses the screenshot fallback and presses Save again. - Local interaction data: the current selection, hover/click trigger, and target geometry are processed temporarily to display the capture control and crop the chosen visible image area. They are not retained or sent as an activity log. EtchDeck uses this data only to authenticate the user, show and save the private card the user requested, prevent duplicate private cards, provide security, and operate the service. Private image objects are stored by Cloudflare R2 on EtchDeck's behalf. EtchDeck does not sell extension data or use it for advertising, data brokerage, credit decisions, or lending. Install EtchDeck Collector only if you consent to the data handling and necessary transfers above. See https://etchdeck.com/privacy for retention, service providers, deletion, security, and Chrome Web Store Limited Use details. SECOND IN-PRODUCT GATE After installation, the extension still remains inactive on webpages until it shows the same data categories and the user clicks the single explicit “Agree & Enable EtchDeck” button. A changed data practice requires a new affirmative action before collection resumes. How it works: - Select webpage text and click the EtchDeck button. The selected text is sent over HTTPS to the user’s EtchDeck account to check for an exact private card match and load card groups. The user reviews and edits the card before saving. - Hover a chosen webpage image using the configured trigger and click the EtchDeck button. A visible-tab screenshot is processed locally only to prepare a cropped fallback. On Save, the extension first fetches the public original image without website cookies. The background rejects local/private addresses and unverified redirects, streams no more than the configured 4 MiB default hard limit, then uploads the accepted/compressed image and edited card to EtchDeck. A cropped screenshot is uploaded only if the original cannot be read and the user explicitly chooses the screenshot fallback and saves again. - Configure independent text and image triggers, button offsets, and ignored domains. The extension uses an API Key generated in the EtchDeck web app; it does not collect a username or password. Whenever the user saves or replaces an API Key, Chrome generates a new non-exportable AES-256-GCM CryptoKey and random IV, then stores the encrypted API Key and CryptoKey persistently in IndexedDB under the extension's own origin. The accepted disclosure version, capture settings, and ignored domains persist separately in Chrome's local extension storage, which is restricted to trusted extension contexts. Webpage content scripts cannot read the encrypted credential store or obtain the plaintext API Key through messages. The key remains available after Chrome restarts or the extension reloads or updates, and its local copy is removed when the user explicitly clears it or uninstalls the extension. Revoking the key in the EtchDeck web app immediately makes the stored copy unusable. Card-group IDs and names are fetched for each editor and are not stored or cached by the extension. Earlier plaintext keys, tokens, and group-cache data are removed during migration. All executable code is packaged with the extension. The extension does not execute remotely hosted code.