Security

AI prompt security. Three scopes to understand.

AI prompt security covers three distinct scopes: the information stored in Do Prompt, access permissions to that information, and the content you deliberately copy into an external AI tool. Each has its own controls and responsibilities.

In brief

  • Prompts and context are organized by workspace, with assigned access.
  • You review the copied prompt and choose which AI tool receives it.
  • Simple practices reduce the risk of unintended sharing.

Information stored in Do Prompt

Do Prompt stores your prompts, their versions and each workspace’s reusable content: an offer description, a brand voice, information about a client. Kept in one place, this information is no longer copied into every prompt or scattered across documents.

  • Prompts and context organized by workspace.
  • Reusable content instead of scattered copies.
  • Only the information the team needs to prepare its requests.

Access permissions

A workspace brings together the prompts and context of a team, a client or an activity. Context stays within each workspace: its prompts and content are available to the people who have access to it, according to their permissions. Choosing those people remains your organization’s decision.

  • One workspace per client or team to keep contexts apart.
  • Permissions assigned to each workspace member.
  • An access review when someone changes role or leaves a project.

Content copied to an external AI tool

Do Prompt prepares the request; you review it, then copy it into the AI tool of your choice. Once copied, the text is subject to that tool and its terms of use: Do Prompt can neither change it nor withdraw it.

  • A full preview before every copy.
  • Only the information the task needs in the prompt.
  • Your organization’s rules on permitted AI tools still apply.

Available controls and responsibilities

Security must remain workable: guiding usage is better than banning all experimentation. Do Prompt provides workspace separation, access permissions, version history and a preview before copying. Your organization decides who accesses what, which information goes into the context and which AI tools are allowed.

  • Do Prompt: workspaces, permissions, versions and preview.
  • Your organization: choice of people, information and AI tools.
  • Each user: reviewing the request before copying it.

What the browser extension can do

To work, the Do Prompt extension asks your browser for a few permissions, which the store shows before installation. Here is, in plain words, what each one is for. None of them lets it read your conversations, your history or the content of the pages you visit.

  • Keep your session, your preferences and the list of your prompts (titles and descriptions, 24 hours at most) on your computer. Everything related to your account is erased when you sign out.
  • Copy the prompt when you click “Copy”. It never reads what you copied elsewhere.
  • Recognize the AI tool open in the tab where you click its icon, from the page address, without keeping or sending it. Can be turned off in the settings.
  • Open at the side of the window, next to your AI tool, in Chrome and Edge.
  • Talk only to the Do Prompt servers, to load your workspaces and prompts.

Where the extension acts on websites

The extension only acts on a page in three places, and only when you use it.

  • In your AI tool (ChatGPT, Claude, Gemini, Le Chat, Perplexity, Copilot): it places the copied prompt in the input box, after your text. It never sends it for you and erases nothing. Can be turned off in the settings.
  • On the Do Prompt website: it shares your sign-in and your workspace with the site, so you only sign in once.
  • On other websites, only if your organization has set a list of allowed tools: when you paste a prompt copied from the extension, it checks that the site is on that list. If your organization asks for it, it also erases that copy when you close the browser, and tells you so. This check reduces accidental sharing; it does not replace reviewing what you paste.

In practice

  • Illustrative example

    Client context

    A client’s information stays in that client’s workspace instead of being copied into every shared prompt.

  • Illustrative example

    Sensitive prompt

    A sales reply prompt serves as the reference version for the sales team; changes go through the people responsible for it.

Frequently asked questions

Who can access the context?

The people who have access to the workspace where it is stored, according to the permissions assigned to them. To keep two clients or two teams apart, create a workspace for each.

What does the copied prompt contain?

The prompt’s instructions, the information you filled in and, if the prompt references it, the workspace context. You can review the full preview before copying.

How do we choose who gets access?

Start from real needs: give workspace access to the people who prepare or use its prompts, then review that access when roles change.

Try it with your own reference prompts.

Try Do Prompt for free during the beta, starting from a task your team already does.

Try for free

Free during beta