Data flow
Know where your text goes.
The document tool and Gmail extension use different processing paths. Here is the boundary for each one.
Document workflow
1. In your browser
Files are read, text is extracted, findings are detected, and replacements are produced locally.
2. Account check
Your sign-in and export count are checked by our service. Document content is not included in that request.
3. You choose
Review the result, export it, then decide whether and where to share the new copy.
Optional handoff to the prompt editor places the de-identified text in your browser URL for the next local screen. Using the email generator afterward is a separate AI workflow.
Gmail extension workflow
Gmail context
Subject, draft text, and up to three recent thread messages are read on the Gmail page.
Local first pass
Known patterns are replaced in your browser before the request is sent.
Server and AI
Locally redacted text is sent for a second redaction pass and email generation.
Other data we handle
Account, billing, export-count, invitation, and support information is handled by the services needed to operate SoloScripter. Payment card details are handled by Stripe.
Your review remains essential
Pattern detection can miss unusual or contextual details. Review every finding and the de-identified result before sharing it.