LV · LocalVeil Studio

Agency evaluation · version 1.0.0

Evaluate before you deploy.

A short synthetic-data workflow for teams considering a local, inspectable privacy pass before screenshots and text excerpts leave the organization.

Use synthetic data only. Do not test with client, employee, customer, production, regulated, or confidential material.
No uploadProduct features run in the active browser tab.
No accountNo login, API key, or cloud workspace.
Fresh exportsSource files are not edited or overwritten.
Manual reviewEvery output must be checked before sharing.

Ten-minute synthetic evaluation

A short test with a clear stopping point.

1. Open locally

Open the demo in a current desktop browser. No installer, account, subscription, or API key is required.

2. Create fresh outputs

Use solid masks on synthetic content, export PNG and JPG copies, and confirm the original remains unchanged.

3. Explain the limits

Confirm the evaluator can describe the manual-review requirement and when solid masking should be preferred.

Evidence boundary

Pass only what you observe.

This evaluation can establish

  • The observed synthetic workflow on the evaluator's browser and device
  • Whether image, text, and metadata-clean features work for that test
  • Whether the team understands the package's local operating model

This evaluation cannot establish

  • Complete removal of privacy risk or legal suitability
  • Central administration, audit logs, or policy enforcement
  • Support for PDFs, video, office documents, or direct cloud-file editing
  • Compliance certification or a guarantee against disclosure

Procurement questions

Clear scope, without sales theater.

Is the Agency license a subscription?

No. It is a one-time version 1.0.0 license.

Does Agency unlock additional product features?

No. Every tier contains the same application and guides. Agency changes the permitted internal user count and deployment scope.

Can the application package be sent to clients?

No. Exported files may be used without restriction, but the application package must remain within the licensed organization and named-user scope.

Does support require private source files?

No. Use synthetic reproduction material and non-sensitive error text. Do not send confidential source files.