Name and build the job.
Configure the job name, fixed parent, complete folder tree, and exact camera-media landing path.
Choose a drive or folder. Before we ask for an email, Vaultline reads the naming and folder conventions your team actually uses and shows them back to you.
We inspect names and relative folder paths, not footage, file contents, checksums, media metadata, or other drives.
Your email contains the signed Ingest 0.3.0 DMG, the generated team-profile attachment, checksums, and exact setup steps. If delivery fails, this page does not claim success.
One universal, signed Mac app receives a portable profile generated from the recipe you confirmed.
Configure the job name, fixed parent, complete folder tree, and exact camera-media landing path.
Choose the fields operators complete for each ingest, with automatic dates and sticky values where appropriate.
Use multiple locally authorized destinations, read every copy back, write ASC MHL, and retain a readable ingest record.
The browser scan has one job: recognize visible naming and folder structure. The delivered app has no network client and never moves or deletes source media.
No. The scan reads visible names and relative paths in this browser. File contents, raw examples, exceptions, the folder handle, and absolute paths stay local.
No website can grant macOS folder access on another Mac. The profile configures the destination count and workflow; each operator authorizes the actual mounted locations locally.
It can configure the folder and derived project name. It does not invent an undocumented blank project file. A real team template can be imported separately.
You edit or rescan before requesting delivery. The funnel does not silently hand ambiguous work to a person and call that automation.
No. This page delivers Vaultline Ingest. It does not sell or require Media Nexus, Relay, archive search, or AI tagging.