Four things to keep out of an AI reply prompt

A reply tool that drafts comments for you is reading something to do it. With ReplyPilot that means the post context you're looking at, the platform, your reply settings, and whatever you type into the instructions. It goes to a service that prepares the draft. It isn't an offline writing tool, and the service can record requests and responses.

So before you hit Generate, it helps to know what doesn't belong in there. We keep a short list:

Passwords, sign-in links, tokens and cookies. Never in instructions, never in a support email.

Confidential work. Customer records, internal documents and unreleased company plans stay out unless your organization has approved that kind of processing.

Personal details the draft doesn't need. A one-line description of your role does more than a pasted document full of names.

Screenshots you haven't redacted. If you send one to support, blur private conversations and account details first.

One thing people mix up: removing the extension from Chrome changes what's installed in that browser. It doesn't delete anything held on the service side. That's a separate request.

The full version, including what a workplace should ask before adopting it, is our privacy checklist before you generate.

ReplyPilot · m@replypilot.app