Skip to content
wrxstack mark
Back to help

Account and security

Understand data limits and privacy expectations

Know what to paste into generation, what to avoid publishing, and how source-safe support evidence works.

step 1

Keep private data out of source material

The safest public portfolio starts with source text that already excludes confidential or regulated data.

  • Remove home addresses, IDs, payroll, and compensation details.
  • Avoid private customer names unless you have permission.
  • Keep unpublished financials and internal roadmaps out of pasted source text.

step 2

Publish only what can stand in public

A portfolio is discoverable and shareable. Treat every public section as something a recruiter, customer, investor, or colleague may forward.

  • Use broad descriptions when client names are confidential.
  • Avoid claims that cannot be verified or explained.
  • Review media metadata before attaching files.

step 3

Use source-safe support evidence

Good support reports include route, time, browser, and expected behavior, without exposing credentials or customer content.

  • Share timestamps and page names.
  • Redact private data in screenshots.
  • Never paste API keys, database URLs, or provider secrets into support messages.
Understand data limits and privacy expectations | Folio