What SafeShare processes
Only content the user explicitly selects: captured tab pixels, imported images, rendered PDF pages and pasted text. Processing occurs locally in extension memory.
SafeShare is built around a simple boundary: protected source content stays on the device where you opened it.
Only content the user explicitly selects: captured tab pixels, imported images, rendered PDF pages and pasted text. Processing occurs locally in extension memory.
Chrome storage contains preferences, rectangle-only layouts, custom detector definitions and a signed XPayr entitlement. It does not contain protected source content.
SafeShare contacts xpayr.com only for public product information and signed license issue, restore or refresh requests. Protected content and detection results are excluded.
activeTab and scripting are used only after an explicit capture command. storage keeps non-content settings and entitlement state. alarms performs bounded license refresh. No host permissions are requested.
Working content is held in memory and disappears when the editor is cleared, reloaded or closed. Settings and layouts can be removed by clearing extension storage or uninstalling SafeShare.
Local OCR and pattern detection can miss or over-identify data. Users must review the flattened output. Solid masks are recommended for authentication and financial secrets.
Privacy questions can be sent through the XPayr contact page. Material policy changes will be dated on this page and reflected in the extension listing.