Permissions and privacy
Toado captures page evidence when you use its reporting tools. In-page hooks collect debugging history for those captures. The 0.2.0 extension also supports persistent element pins and narrated walkthroughs, so the data boundary includes more than a screenshot.
Chrome permissions
| Permission | Purpose |
|---|---|
activeTab and tabs | Access the active reporting tab, read its address, capture it, and open related Toado pages. |
scripting and <all_urls> host access | Run page hooks, capture bridges, and the in-page pin controls on supported sites. |
storage and unlimitedStorage | Store connection and preference data and locally retained capture data. |
alarms | Schedule background work such as capture retries. |
identity | Authorize the account connection through Chrome. |
webRequest | Observe network request evidence. |
webNavigation | Track navigation so capture and pin state follow the page. |
Optional desktopCapture | Request a source for extension screen recording. This is requested when needed rather than granted with the base installation. |
Microphone access is requested through the recording setup. Chrome’s source picker and recording permissions control what you share. Narration-only mode does not record the screen but still takes screenshots when you pin elements.
What a report can send
Depending on the workflow and capture policy, the payload can include screenshots, page and element context, the URL, console output, request and response evidence, errors, performance information, and metadata. Walkthroughs add audio and optionally video. Descriptions, mentions, assignments, and comments become ticket data when saved.
Sensitive headers, credential-style URL parameters, and built-in sensitive body keys are redacted by capture rules. This does not guarantee all personal or confidential information is removed from page pixels, arbitrary log text, or narration.
Restrict sensitive pages
Owners can use capture profiles to block matching addresses with Never capture, withhold screenshot assets and request/response bodies with Metadata only, or add redaction names. Metadata only also blocks extension page pins, which require a screenshot. Personal extra header names are configured in extension settings.
Do not capture a page or narrate information that must not be uploaded. There is no pre-upload screenshot review setting in the current Options page.
Screenshot redaction and recording transcription
The annotation editor masks the rendered image. The original screenshot remains stored and can be available to users or agents with access to that ticket. Annotation redaction is presentation rather than deletion of the original.
Audio is not automatically redacted. Where transcription is enabled and requested, audio is sent to OpenAI before transcript text is redacted. Check the workspace’s AI configuration and the content you are recording before starting.
Data sent outside captures
When connected to an account, the extension sends installation/update pings and an authenticated heartbeat about every 15 minutes. It also reports the in-page logging preference. These are separate from a captured report and are associated with the connected account.
Local data and troubleshooting
The extension retains connection information, preferences, and recovery data locally. Uninstalling or clearing extension data can remove local recovery state. Use Diagnostics in Options to copy a troubleshooting report; nothing is sent by that action until you share it.
Browser internal pages, the Chrome Web Store, and other protected surfaces restrict extension access. Incognito access must be explicitly allowed in Chrome’s extension details.
Where to next
- Capture profiles, restrict what is captured by address.
- Walkthrough recording, modes, review, and retention.
- Security, the broader trust model.
- Data retention, ticket and media lifecycles.