LogLyn · Security & Data Handling
Security & Data Handling
This page explains what belongs in the website form, what may be requested after scope is agreed, how engagement files are handled, and which actions remain yours.
Last updated: 2026-08-19
Before you send anything
Five things to know before sharing any data.
What may be requested
Only files needed for the written scope. Depending on the work, these may include invoices, purchase orders, delivery or acceptance records, remittances, deduction notices, counterparty requirements, and related correspondence.
How files are transferred
The website form is not an engagement-file intake channel. LogLyn confirms the transfer method after scope is agreed. Do not send operational files until you receive those instructions.
Who may handle them
Access is limited to the people and service providers needed to receive, perform, support, and deliver the agreed work.
How long they are kept
Retention and deletion terms are confirmed in the written agreement or intake instructions. You may ask for the current terms before files move and request deletion subject to applicable recordkeeping or legal obligations.
Your NDA option
If you require an NDA, request it before files move. Work begins only after the scope and applicable data-handling terms are agreed.
Scope
File-based work, scoped before transfer.
You choose the records for the agreed scope. LogLyn prepares, repairs, reconciles, and organizes payment-related documents, registers, and exception or decision items for your review. The requested inputs and deliverables are confirmed before files move.
LogLyn does not request buyer- or customer-portal credentials and does not submit or send materials externally. You keep control of source systems, approvals, submissions, communications, and every other external action.
Handling Rules
Every rule stated plainly.
These boundaries apply to the files used for agreed work. Any engagement-specific terms belong in the written agreement or intake instructions.
Purpose
Engagement files are used to perform and administer the agreed work. LogLyn does not sell them or use them for advertising. Any materially different use requires disclosure and written agreement.
Access
Access is limited to the people and service providers needed for receipt, performance, support, and delivery of the agreed work.
Transfer boundary
The website form is for contact and scoping information only. Operational files move through the transfer method confirmed for the engagement, not through the public form.
Input minimization
Send only the records requested for the written scope. Do not include passwords, API keys, browser or session tokens, bank credentials, portal credentials, or unrelated sensitive data, and do not grant broad access to source systems.
Customer-shared third-party data
Files may contain information about customers, counterparties, or other third parties. You are responsible for authority to share it. LogLyn uses it only for the agreed work and does not contact those parties.
Scope Limits
What we do not do.
- We do not claim a security certification or control framework that is not expressly listed on this page or in the written agreement.
- We do not request buyer- or customer-portal credentials.
- We do not sign, certify, submit, send, or contact counterparties on your behalf.
- We do not process payments, hold funds, purchase receivables, or act as a payment intermediary.
- We do not make legal, contractual, accounting, tax, or payment decisions for you.
Ready to start
Contact LogLyn.
Contact us to confirm the scope, requested files, transfer method, retention terms, and any NDA requirement before operational records move.