Documentation
Licensing
PixlKey helps you attach clear, repeatable usage terms to a specific work and carry those terms forward in the artefacts you export — so clients, collectors, and collaborators aren’t guessing what they’re allowed to do.
Where licensing lives
Licensing is configured in the PixlKey App and applied during processing. This public site explains the model and what the generated outputs mean.
- App: choose or manage your licence templates (e.g., “My Licences”).
- Processing: the selected licence is tied to the work at export time.
- Outputs: derivatives and documentation artefacts reflect the chosen terms.
What PixlKey produces
PixlKey’s goal is consistency: the same inputs produce the same style of evidence, every time.
- Licence details packaged as human-readable artefacts (certificate-style documentation where applicable).
- Metadata fields embedded into exported derivatives where supported.
- Identifiers/fingerprints that support later verification workflows.
How to think about licence “types”
PixlKey licences are intended to be practical templates you can apply per artwork. Common patterns include:
- Personal / Private use (display, download, no commercial use)
- Educational (training, classrooms, attribution rules)
- Commercial (client usage, term limits, distribution scope)
- Custom (commission-specific terms or special permissions)
Recommended workflow
- Create or select a licence template in the app (your “default” can speed up routine work).
- Process the artwork and generate your derivatives (previews, socials, signed exports).
- Share derivatives publicly, and reserve originals for private storage or trusted delivery.
- Provide documentation (licence/certificate artefacts) when selling or licensing.
Notes and limitations
- Licensing and metadata improve clarity and provenance, but they do not prevent theft or misuse.
- When in doubt, keep the original private and distribute only the derivatives you intend to circulate.
- Some “change after the fact” workflows (transfer/reassignment/revocation) may evolve as PixlKey matures.
If you need formal legal language for high-stakes commercial work, treat PixlKey outputs as your documentation layer and pair them with your contract process.