Quick Email : Temp Email and quick Email Finder

Create temporary inboxes, send and receive quick emails, and find public email addresses on authorized websites.

Quick Email brings temporary mailbox workflows and local email-address organization into one browser side panel. Quick Email module - Create or import a temporary mailbox. - Send email with an explicit recipient, subject, body, and optional attachments. - View and search inbound and outbound messages. - Keep mailbox configuration and access credentials in Chrome extension storage. Email Collect module - Find email addresses visible in page text and mailto links. - Request access one website at a time only after a user action. - Scan an authorized page once after it finishes loading; page changes are not continuously monitored. - Store email addresses, source URL/title, and discovery times locally in the browser. - Search, copy, inspect sources, delete records, and export a user-initiated JSON file. - Skip sensitive login, account, payment, financial, medical, and webmail pages by default. Privacy and control Collector data is not uploaded to CCTor, the mail API, analytics services, or third parties. Users receive a prominent disclosure before enabling collection and can revoke each website permission in Settings. Mail content is transferred separately to the configured mail API only when the user requests mailbox, inbox, or sending functionality. Privacy Policy: https://cctor.com/quick-email-privacy ## Privacy practices Select the applicable dashboard data categories and use the explanations below. Match the labels shown by the current Dashboard if wording differs. ### Personally identifiable information / email addresses Yes. The Email Collect module locally stores email addresses visible on user-authorized pages. Quick Email also processes the user's mailbox address and message recipients. Collector records remain local; mailbox and recipient data are sent to the production mail API only for user-requested mail operations. ### Authentication information Yes. Mailbox access tokens and imported mailbox keys are stored in Chrome extension storage and sent only to the configured mail API for authentication. They are not included in collector exports. ### Personal communications Yes. Recipients, subjects, message bodies, attachments, and received messages are processed only to provide user-requested send and inbox functionality through the configured mail API. ### Website content Yes. On websites the user explicitly authorizes, the extension scans visible text and mailto links to identify email addresses. It does not retain the page body, form fields, cookies, or passwords. ### Web history / browsing activity Yes, to the limited extent needed for the user-facing collector. The extension stores the source URL and page title for a collected address and listens for completed navigation on already-authorized sites to trigger one scan. This information is not used for advertising, analytics, or unrelated profiling. ### Data usage certifications - Data is used only to provide the disclosed browser email workflow. - Collector data is not sold or transferred to third parties. - Data is not used for personalized advertising, credit decisions, or unrelated profiling. - Humans do not read collector data unless the user explicitly provides specific data for support, or access is required for security or legal compliance. - The use of information received from Google APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements.