Writing watermark-friendly content
Content with lists and parallel phrases produces the strongest signatures.
Good:
Our priorities are revenue growth, market expansion, and operational efficiency.
Weaker:
Revenue growth is our top priority this quarter.
More interchangeable items means more unique permutations and better attribution.
Content patterns that work well
- Comma-separated lists with three or more items
- Parallel phrases joined by "and" or "or"
- Bullet lists of departments, initiatives, or priorities
- Descriptive series of actions or qualities
Before sending to a large list
- Check signature count and permutation totals on the Review page.
- Add or select additional signatures if permutations are less than recipient count.
- For very large lists (50+), contact LeakLocked about capacity planning.
Operational best practices
Send before sharing externally
LeakLocked can only match leaks against versions you sent through the platform. If content was shared outside LeakLocked first, there is nothing to match against.
Use marking policies consistently
Set your footnote and attachment watermark once and align templates across your team so recipients recognize official marked content.
Match recipients to permutations
Each recipient should ideally receive a uniquely watermarked version. Before sending:
- Review the permutation count on the Review page
- Deselect low-value signatures if you need fewer permutations (not recommended for investigations)
- Add more list items or signatures if you need more permutations
Recommended rollout plan
Week 1: Pilot (3–5 users)
| Day | Action |
|---|---|
| 1 | IT verifies DNS domain; pilot users create accounts |
| 2 | Configure marking policies; install Outlook add-in for pilot group |
| 3 | Send a test message to internal addresses; verify each recipient sees slightly different wording |
| 4 | Run a mock investigation — paste one recipient's version as a "leak" and confirm correct attribution |
| 5 | Review results with legal/security; adjust policies |
Week 2–3: Expand
- Roll out to teams handling sensitive communications (legal, HR, finance, exec assistants).
- Document which message types must go through LeakLocked (e.g. "All board materials and M&A comms use LeakLocked").
- Train users on signature selection and the Review step.
Ongoing
- Monitor the Investigations tab for active cases.
- Periodic refresher on writing watermark-friendly content.
- Re-verify DNS if your domain provider changes.
Security & privacy overview
| Topic | How LeakLocked handles it |
|---|---|
| Authentication | JWT sessions; OAuth with PKCE for Google/Microsoft |
| Data storage | Sent messages, versions, and investigations stored securely; tied to your account |
| Recipient visibility | Watermarks are designed to be imperceptible in normal reading |
| Access control | Users only see their own messages and investigations |
| API token | Session token shown for Outlook add-in setup only while logged in |
For full details, see the Terms of Service and Privacy Policy, or contact your account representative for a security questionnaire or DPA.
Internal policy template
Use this as a starting point for your organization's LeakLocked policy:
Scope: All communications classified as Confidential or Restricted that are sent to multiple internal or external recipients must be sent through LeakLocked.
Required steps: Compose in LeakLocked (web or Outlook) → review signatures → confirm unique versions on Review page → send.
Investigations: Any suspected leak of marked content must be reported to [Security/Legal]. Upload the leaked artifact to LeakLocked within [24 hours] and preserve the investigation report.
Exceptions: [Define any exceptions, e.g. single-recipient emails, pre-approved templates]
Getting help
- Product demo: /schedule-a-demo
- Support: /contact
- Outlook add-in deployment: Contact your LeakLocked account team for tenant-wide rollout