SendAware is optimized for speed and a light system footprint. It currently supports:
| Problem | Likely cause | Fix | |--------|--------------|-----| | No open detected even though recipient replied | Recipient uses Outlook + POP3 without syncing read status | Send a test to a Gmail account first | | Location shows only country | Recipient’s IP is masked (VPN, corporate proxy) | Accept as limitation | | Tracking stops working after 2 weeks | Gmail API token expired | Re-authenticate in extension | | Double opens within 1 second | Email client pre-fetching (e.g., Outlook on Windows) | Ignore; it’s a false duplicate | | Extension not showing in compose window | Gmail interface update | Disable/re-enable extension; clear Chrome cache |
SendAware: Preventing Costly Accidental Data Disclosures in Outlook sendaware
The primary purpose of SendAware is to train users to be more mindful of potential security issues before they hit "Send". Unlike passive security measures, it proactively prompts users to confirm their actions if certain configurable criteria are met.
SendAware leverages the and Google’s internal read-receipt mechanism . SendAware is optimized for speed and a light
: SendAware can be configured to prompt for confirmation or block specific attachment types and check if attachments are encrypted.
Clicking "Send" before attaching the correct document or realizing a sensitive file is attached. SendAware does not automate this natively, but its
SendAware does not automate this natively, but its labels update in real-time.