Overview
What ReplyPort does
ReplyPort works locally with Outlook Classic. It makes approved Outlook information available in a user-selected filesystem location so that a user-chosen AI assistant or other approved tool can help search, analyse and draft a reply. ReplyPort can then create a reply draft in Outlook Classic.
ReplyPort does not operate a remote email server, a hosted AI model or a ReplyPort cloud service.
Information
Personal information accessed and why
ReplyPort accesses the following information only as needed for functions the user authorizes:
- Outlook message content and metadata: message body text, subject, sender and recipient details, date, conversation information, message identifiers, sensitivity/protection state and attachment metadata. This supports approved export, search, analysis, triage, reply drafting, threading and safety checks.
- Outlook account and routing information: the configured account address, Outlook profile/store/folder information, approved signature information and local Outlook item locators. This lets ReplyPort keep work within the correct mailbox, preserve Outlook's recipients and conversation, and place the draft in the correct Drafts folder.
- Approved attachment content: attachment bytes are made available only after local approval and validation when that content is needed for a user-authorized task.
- Operational information: configuration, opaque identifiers, capability material, hashes, indexes, checkpoints, journals, status, error codes and bounded work counts. This supports security, integrity, recovery, deduplication and diagnostics.
ReplyPort refuses protected or incomplete message content for drafting. It does not use personal information for advertising and does not sell personal information.
Storage and protection
Where information is stored
User-selected storage
The user chooses ReplyPort's filesystem storage root. Message snapshots, message metadata, user-authorized AI work records and approved attachment files are stored there. The location may be inside a Dropbox folder.
If the user chooses Dropbox-backed storage, the Dropbox desktop software may sync the ReplyPort storage folder through the user's own Dropbox account. That processing is controlled by the user and is subject to Dropbox's terms and privacy policy. ReplyPort does not use the Dropbox cloud API.
Local operational state
ReplyPort keeps operational state under the current user's local Windows profile. This is limited to configuration, protected Outlook routing state, DPAPI-protected capability keys and journals, hashes, indexes, checkpoints, retry state and content-free logs. Local logs contain operational identifiers, states, durations, error codes and bounded counts—not email subjects, bodies, senders, recipients or attachment filenames.
Safeguards
ReplyPort uses the current Windows user's filesystem permissions, Windows Data Protection API protection for local secrets and sensitive operational state, opaque mailbox identifiers, mailbox-scoped capabilities, immutable records and strict routing and draft verification. A storage root's per-mailbox folders provide logical separation; they are not a substitute for access controls. The user is responsible for securing the Windows account, Outlook profile, selected storage location, Dropbox account and any external AI account they choose.
Services you choose
When third parties may process information
ReplyPort itself does not upload personal information to Sergey Alexeev or a ReplyPort-operated server. The current product contains no ReplyPort analytics or telemetry.
Information may nevertheless be processed by these categories of third party through services the user has selected:
- Microsoft and the user's mailbox provider continue to process Outlook mailbox data under the account and service the user already uses. ReplyPort's local Outlook integration does not replace those arrangements.
- Dropbox or another storage/sync provider may process files if the user puts the ReplyPort storage root in that provider's synced location.
- An external AI service or AI-enabled tool may process the ReplyPort data that the user intentionally makes available to it for analysis or drafting.
Each selected service operates under its own terms and privacy policy. Users should review those terms and only make mailbox information available to a service they are permitted and willing to use.
Generative AI
AI-assisted output requires review
ReplyPort is designed for AI-assisted analysis and drafting. The current product does not itself provide a hosted generative-AI model; the user chooses whether to use an external AI service or AI-enabled tool.
To report inappropriate AI-generated content associated with ReplyPort, email sergei.v.alexeev@gmail.com. Please do not include confidential email content unless it is necessary to investigate the report.
Retention and controls
Your choices
ReplyPort's bounded mirror copies normally expire 90 days after the source message's received or sent date, although records needed for pending work may be retained until that work is resolved. Disposable search requests and results normally expire after seven days. Approved staged attachments normally expire after 24 hours or when the dependent request completes, whichever comes first.
The user controls ReplyPort and can:
- choose the storage location and stop using or remove that location;
- disable ReplyPort to stop its background processing;
- choose whether to use any external AI service or AI-enabled tool;
- delete ReplyPort files from the user's own selected storage; and
- uninstall ReplyPort to remove its local application, configuration and runtime state.
Disabling or uninstalling ReplyPort does not delete, move or otherwise change messages in Outlook. Uninstalling also leaves Dropbox or other user-selected storage content untouched so that it is not silently destroyed. The user may delete ReplyPort's files from that storage separately when appropriate.
Contact
Privacy questions and reports
ReplyPort is published and developed by Sergey Alexeev.
For privacy questions, requests, concerns or reports of inappropriate AI-generated content, contact sergei.v.alexeev@gmail.com.
This policy may be updated if ReplyPort's data practices change. The effective date above identifies the current version.