Ownership follows the batch.
The same checks cover intake, processing, review, sharing, and download.
Intake
01The source batch enters a job with its owner context.
Processing
02Admitted work moves to the queue outside the web request.
Review
03Documents and corrections remain associated with the batch.
Result
04Preview, sharing, and download follow the result boundary.
Two entry paths. One ownership rule.
Signed-in account
Jobs are checked against the account that created them before status, sharing, or result actions.
Anonymous trial session
Trial jobs remain tied to the anonymous session that created them.
A file identifier is not permission to read a result.
File metadata is checked before a download or share path is returned.
Reliability supports the security boundary.
Queue controls and durable records keep long-running work predictable.
- 01
- Job ownership
- Files stay tied to an authenticated user or an anonymous session owner.
- 02
- Durable records
- Database metadata and storage paths remain the source of truth after a reload or worker retry.
- 03
- Queue boundary
- Workers process admitted jobs outside the browser request path.
- 04
- Result checks
- Review, corrected output, sharing, and downloads follow the same ownership model.
AxLiner claims formal certifications only when they are completed and available to customers.
Need to discuss a security or privacy concern?
Contact AxLiner without attaching sensitive source documents.