Privacy, in plain language.
Project notice · October 21, 2026
Replylane is an open-source job application email organizer. This notice describes the software’s behavior. The person operating a live deployment is responsible for identifying themselves, providing a privacy contact, selecting service regions, and supplying the notices appropriate for their users before accepting public registrations.
What you connect
Account sign-in is separate from inbox access. Gmail uses Google’s read-only Gmail scope. Microsoft uses delegated Mail.Read and User.Read with offline access. IMAP connections use TLS on port 993 and open the Inbox read-only. The software does not send email, change read status, delete mail, or move messages.
How messages are organized
When you connect an inbox or start an import, the backend sends our external processing service a shortened message excerpt, subject, sender display name, and received date to decide whether the email is about a job application. Email addresses and links in the submitted text are replaced where recognized. Redaction is limited and does not remove every possible personal detail. Unrelated emails within your selected range may also reach the classifier before being excluded. Attachments are not submitted.
Processing runs on a hosted service with data-retention controls. Deployment owners should enable Zero Data Retention and review their service agreement before activating real mail processing. This app does not use email to train models or enable model tuning.
What is saved
Firebase Authentication stores your sign-in account. Firestore stores connected inbox metadata, encrypted refresh tokens or IMAP passwords, import cursors, usage counts, and processing receipts. Application responses create cards with company, role, sender, date, language, classification, summary, next step, short plain-text excerpt, and any notes or corrections you add. Irrelevant message bodies are discarded; an identifier receipt remains to avoid processing them again.
Credentials are encrypted on the server using AES-256-GCM with a deployment secret. Email excerpts and notes are readable by the app’s backend and stored using Firestore’s managed encryption. This is not end-to-end encryption. The browser cannot access Firestore directly. API access requires a verified, authenticated account and is restricted to that account’s records.
If you connect Telegram, Firestore stores your Telegram chat identifier so the bot can send you private notifications. For newly processed replies, the bot receives the company, role, result category, and a short generated summary. Older imported mail does not trigger notifications. Disconnect Telegram in Settings or send /stop to the bot to remove the link. Telegram processes messages under its own terms and privacy policy.
Your choices
Choose new mail only, the last 30 days, or the last 60 days. Pause a connection to stop scheduled processing. Disconnect to remove its stored credentials. Existing application cards remain available. Export your application data as CSV, or permanently delete your account and workspace in Settings. You can revoke OAuth access or app passwords in your email provider’s security settings too.
Messages already being fetched or classified when you pause or disconnect may complete that external request. The app checks connection and account state again before writing results. Disconnecting does not itself revoke the provider’s authorization. Provider logs, infrastructure backups, and retention schedules are governed by the services and deployment owner.
Browser storage and logs
The theme and board/list preference are stored locally. Firebase manages authentication storage for signed-in users. There are no advertising or analytics trackers in this project. The app’s own error logs omit message content and credentials; hosting services may still retain request metadata.
AI can be wrong
Confidence scores are model estimates. Uncertain results go to review, but a high score does not guarantee correctness. Read the original before responding, attending an interview, or acting on an offer. You can manually correct any card.
Before a public launch
A live operator must supply their identity and contact details here, validate deletion and retention with their hosting setup, complete applicable email provider verification, and ensure that the provider data-processing arrangements fit the intended audience. This project notice does not claim those steps have already been completed.