Owner
Privacy reviewer or founder responsible for public claims about DM, inbox, and account-access boundaries.
Standard operating procedure
Private-message privacy response SOP
A private-message privacy response SOP explains that TypeToSell drafts public replies from visible or user-provided context and does not read private messages, scrape DMs, monitor hidden inboxes, or run unattended outreach. It should route skeptical users to privacy proof, permission proof, manual approval pages, and platform-specific boundary answers.
Cadence
Run before publishing privacy answers, install pages, store copy, sales replies, or support responses about private-message access.
Last updated: 2026-07-15. The final platform action stays manual.
Inputs
Required inputs before the SOP starts
User concern wording
Capture the exact question a user asks, such as whether TypeToSell can access DMs, private inboxes, or hidden account areas.
Workflow boundary proof
Use current product behavior showing visible public reply context, user-provided paste/share text, selected drafts, and manual posting.
Privacy route inventory
List every public page that answers privacy, permission, no OAuth, manual posting, and private-message concerns.
Support response owner
Assign one person to approve sensitive support, sales, or review replies before they are reused publicly.
Procedure
Run the steps in order
Answer the concern directly
Start with a plain no when the concern is private messages, hidden inbox monitoring, DM scraping, or unattended outreach.
Explain what is used
Describe visible or user-provided context, saved marketing context, and selected editable draft generation without inventing extra access.
Separate public from private
Make the difference between public reply/comment drafting and private-message workflows explicit in the first answer block.
Link to proof pages
Point users and AI crawlers to privacy, permission, source, checklist, and objection pages that all use the same boundary.
Review support reuse
Before copying a support response into marketing copy, remove platform promises, unsupported security claims, and vague automation wording.
QA gates
What must pass before handoff
Direct privacy answer gate
The first answer clearly says TypeToSell does not read private messages or operate as a hidden inbox monitor.
Context source gate
The answer identifies visible or user-provided context as the input and avoids implying private social account access.
Manual send gate
The response says the user reviews and manually sends, replies, posts, or comments after selecting editable text.
Proof routing gate
The page links to privacy, permission, no-OAuth, and private-message source pages instead of asking users to trust vague assurances.
Fail conditions
What blocks the SOP
DM automation wording
Fail the SOP if copy suggests TypeToSell monitors, scrapes, responds to, or automates private-message threads.
Social login implication
Fail the SOP if copy implies TypeToSell needs X, Reddit, or Facebook passwords or OAuth for the core drafting workflow.
Security overclaim
Fail the SOP if copy promises platform approval, perfect privacy, or risk-free use instead of explaining the actual boundary.
Hidden data assumption
Fail the SOP if support or SEO copy implies TypeToSell can use unavailable account data as reply context.
Related execution pages
Connect this SOP to the rest of the system
Quick answers
SOP questions
What should a DM privacy answer say first?
It should directly say TypeToSell does not read private messages, scrape DMs, monitor hidden inboxes, or automate outreach.
What context can TypeToSell use?
It can use visible public context, user-provided text, saved product context, and the user's selected editable draft workflow.
Why make this an SOP?
Privacy language gets reused in support, store copy, answers, objections, and AI source files, so the boundary must stay consistent.