Automated File Routing Privacy Policy
Effective October 17, 2026
Published by NM Softworks
1. Files and destinations you choose
The application reads files and metadata from selected local/network folders, compatible remote servers, Outlook mailbox folders and OneDrive folders. Metadata can include filenames, folder paths, file sizes, modification times and service identifiers. Outlook attachment processing also uses message and attachment identifiers and related mailbox metadata to select and track deliveries.
When you run a feed or enable a schedule, file contents and names are sent to its configured destinations. Those destinations may be on your computer, a network share or a remote service. Saved connection settings determine the recipient server or endpoint. Review them before running or scheduling a feed.
2. Microsoft accounts and permissions
Outlook and OneDrive use Microsoft sign-in. The current source features request delegated Mail.Read for Outlook and Files.Read for OneDrive. OneDrive upload destinations use separate connections requesting delegated Files.ReadWrite. That permission covers the signed-in user's files more broadly than the selected folder; the application pins uploads to the account, drive and folder you choose. Company administrator approval may be required. Outgoing email is on hold and Mail.Send is not requested. You can save multiple personal/work accounts; each feed identifies its own account and folder.
Account addresses, account/tenant identifiers and chosen folder/drive identifiers are stored locally. Sign-in tokens are cached separately for Outlook, OneDrive sources and OneDrive upload destinations using Windows protection for the current user. File contents are obtained from Microsoft and its download services as needed for a delivery. Microsoft governs its own authentication, account and service processing.
Disconnecting a saved account removes that connection from the application; it does not delete cloud files, revoke Microsoft consent, erase destination copies or delete saved feeds. Saved folder entries and feed references remain after disconnection; disconnected upload destinations are hidden from Add Saved Location until the account is reconnected. Delete a saved entry through Saved Locations without deleting cloud files. You can manage application consent through your Microsoft account or organization.
3. Local settings, history and delivery records
The application stores settings, saved locations, feeds, schedules, delivery History and Microsoft connection data under %LOCALAPPDATA%\NM Softworks\AutomatedFileRouting. Records can contain account addresses, filenames, source/destination paths, server names, identifiers, timestamps, outcomes and error details.
Outlook attachment records contain delivery identities, allocated filenames, destination identifiers, byte counts and checksums used to prevent duplicate delivery and review interrupted publication. Settings, History and attachment records are local application data and are not all encrypted. Windows account and folder permissions remain important.
Clear History removes selected application History records, not transferred files. Reset Attachment Records clears the application's attachment tracking for all saved mailboxes/destinations for this Windows user and can allow old attachments to be delivered again. It does not delete emails or remote copies. Removing a saved feed or location does not delete already delivered files.
4. Passwords, tokens and keys
Saved remote-service passwords, bearer tokens and key passphrases use Windows Credential Manager. Saved profiles reference those credentials rather than storing the secrets directly in profile JSON. A configured SSH private key remains at the file location you selected. Microsoft token caches use Windows encryption for the current Windows user.
These mechanisms do not protect against every threat, including malicious software running under your Windows account. Protect your account, computer, private keys and destination services. Do not include secrets in support requests.
5. Temporary files, source handling and recovery copies
Remote and Microsoft-source delivery can temporarily store readable file contents on your computer. Transfers may also create staged temporary files at the destination. Normal completion and handled failure/cancellation attempt cleanup, but crashes, power loss or permission errors can leave temporary files.
Some protected replacement operations retain the older destination file under a recovery name until final verification succeeds. Recovery files may remain after interruption or cleanup failure. Details identify retained paths when available. Folder-source archiving, when enabled and supported, stores delivered originals in Used Files. Microsoft-source workflows retain emails and OneDrive originals.
Temporary files, archives, final copies and recovery copies may contain sensitive information. They are not a substitute for a backup strategy. Review retained files before removing them and protect the storage locations involved.
OneDrive uploads use temporary upload sessions and a local temporary verification copy. A completed upload is read back and checked before success is recorded. Incomplete sessions expire automatically; Microsoft may retain an empty placeholder temporarily. A failed or uncertain upload is not automatically retried and its final cloud file is not automatically deleted. Review the cloud item before retrying.
6. Schedules and Background Runs
Enabled schedules can transfer files without a separate confirmation for each run. They use the saved feed and current saved location settings. Background Runs registers a Windows scheduled task to run the application under the signed-in user's normal permissions; it does not require storing the Windows password.
Background Runs is separate from enabling a feed's schedule. You can disable each feed's schedule and disable Background Runs in the application. Existing destination files and records remain after scheduling is disabled. Scheduled Microsoft access requires silent sign-in and does not open an interactive sign-in window.
7. Agreement acceptance
Before using the application, you must affirmatively accept the NM Softworks Software License Agreement and Terms of Use. Acceptance is recorded locally for this Windows user, including the application name, package identifier, version/build, agreement version/identifier/effective date, acceptance time in UTC and a unique acceptance identifier.
The acceptance record is protected using Windows encryption for the current user. It is local evidence, not a permanent server-side acceptance log. A missing, invalid or outdated record requires acceptance again. Background execution requires a valid current record and cannot accept on your behalf. This record is separate from Multi-Pad's acceptance record.
8. Information received by NM Softworks
The current application does not include a feature that sends your routed file contents, mailbox contents, OneDrive contents or local delivery History to NM Softworks for storage or analytics. Its transfer functions communicate with the sources and destinations you select and with Microsoft for sign-in and Microsoft-source access and selected OneDrive destination uploads.
If you contact NM Softworks for support, the information and files you choose to send may be received and used to respond. Send only what is needed, remove secrets, and avoid unrelated personal or confidential material.
9. Third-party services and website visits
Microsoft, your remote storage providers, network administrators and other services you choose may process files, account information, connection metadata and service logs under their own terms and policies. NM Softworks does not control those services. Plain FTP does not encrypt credentials or file contents; choose an appropriate secure protocol for sensitive data.
Opening a website link from the application uses your browser. Website hosting and analytics services may process ordinary web-request and usage information separately from the desktop application's local records. This application policy does not replace third-party privacy policies.
10. Your choices and protecting your information
You choose sources, destinations, saved accounts and enabled schedules. Review file contents and destinations, maintain backups, protect your Windows account and storage, and disable automation before changing delivery settings. Removing local settings or uninstalling the application is not a request to remove files from third-party services; manage those copies with the relevant provider.
11. Changes to this policy
This policy may be updated when application features or data practices change. The effective date above will be updated for material changes.
12. Contact
Questions about this policy or the application may be directed to:
NM Softworks
Email: [email protected]