← Back to TP1

DocsIndicator Lab

Own code and protected builds

Why some builds are marked Protected, and what you can and can't do with them.

Every saved build is one of two kinds. Your indicators shows it in the Access column as Own code or Protected; the Saved panel labels them Private or Protected.

Own code

Most builds. The code is yours: read it, copy or download it, take it to TradingView, publish it to the community, and use the “Marked because” popup on the chart.

Protected

Taking Prophets keeps a catalog of protected indicators: its own published indicators and the ones it builds for partners. When a build comes out very close to one of them, the Lab still saves it, but as Protected. The reply says: “Your private indicator is ready to use. Its source remains protected and cannot be viewed, exported, or published.”

The check compares your code with those specific indicators, not with ideas. You're free to build your own FVG, sweep, session or order-block indicator from scratch. The Lab never says which indicator a build matched.

With a protected build you can:

  • Use it on the Lab's chart and change its inputs.
  • Revise it in the Assistant. Every new version is checked again.
  • Backtest it in the Backtester, where it runs privately. See Testing in the Backtester.
  • Use Replay in the Lab with the history jumps. Continuous play is in the Backtester.

You can't:

  • View, copy or download its code.
  • Publish it. You'll see “Saved privately — protected indicators can be used in both Labs, but cannot be published.”
  • Use the “Marked because” popup, because its code never runs in your browser.

“Make it yours first”

The same check runs whenever you open or download code. If the code on screen is very close to a protected indicator, the code panel shows Make it yours first with this message:

“This build is very close to a protected indicator in our catalog. Change the logic to make it your own — different signals, levels, or drawing — and it'll export.”

Describe a real change in the Assistant. A new version that's different enough comes back as Own code. An imported script that matches a protected indicator is saved as Protected too.