Film and TV work often runs under NDAs — and we treat that as the default. Our goal is simple: give you practical surface-system support without exposing project information, visuals, or production details.
What “NDA-safe” means with QHL Set
We structure communication so you can get answers fast while keeping information controlled:
- Need-to-know only: we focus on substrates, workflow steps, performance targets, and deadlines — not story, scenes, or sensitive context.
- Minimal identifiers: no project names, no unit names, no call sheets, no talent, no locations.
- Controlled visuals: we only use images/videos when they’re essential for diagnosing a finish — and we keep them strictly technical.
How to share information safely
When you contact us, you can stay NDA-safe by sending only:
- Substrate type (e.g., MDF, wood, primed board, PVC/prop material)
- Current layer stack (primer / base / effect / topcoat)
- The issue or target look (sheen, texture, metallic/pearl intensity, durability needs)
- Timing constraints (dry/recoat windows, approval deadline)
- Close-up technical photos/videos only (no recognisable set context)
If you’re unsure, send less — we’ll tell you exactly what’s needed.
Channels and what we use them for
- Email: best for written instructions, recap, and sharing a clean step-by-step workflow with your team.
- WhatsApp call / video call: best for urgent troubleshooting and fast alignment on application steps (no chat support).
- On-site support: for high-stakes work where rapid decisions and crew alignment matter. (Paid service — travel + time on site agreed in advance.)
What we will not ask for
To stay aligned with production expectations, we don’t require:
- Scripts, scene context, call sheets, schedules, or location details
- Wide shots of sets or recognisable environments
- Talent information or any identifying production material
Handling of samples and test panels
If physical samples are needed, we keep labelling and documentation generic and technical:
- Neutral naming (e.g., “Panel A / B”, “Silver 01”, “Pearl 02”)
- Notes focused on application method and performance — not project references
Your control comes first
If your production has specific rules (approved channels, file handling, naming conventions), we adapt. Tell us the boundaries and we’ll work inside them.
