CanMailCleaner Privacy Policy
Last updated: October 26, 2026
Scope and operator
This policy describes CanMailCleaner, an independent desktop email application developed by Can Ürek.
The application is currently a private development project for personal use. It is not publicly distributed or offered as a hosted mailbox service.
This policy distinguishes the current development build and limited pilot from features that have not yet been implemented.
Contact: lmcgs@yahoo.com
Information processed during the initial pilot
The initial Yahoo pilot is limited to the developer's own account and manually initiated, read-only access.
Within that scope, the application may process:
- The account email address entered by the user.
- Credentials entered for the experimental password-based connection.
- The From, Subject and Date headers of up to five INBOX messages per read.
- Operational status information needed to display the result of a read.
Message headers may contain personal information about the account owner and other correspondents.
The initial pilot does not retrieve message bodies or attachments, access contacts or calendars, send email or modify the mailbox.
Purpose of processing
Account information and credentials are used to establish the requested connection.
Retrieved headers are used to display messages and provide local search, date filtering and sender grouping.
Yahoo mailbox data is not used for advertising, audience targeting, sale of data or monetization in this personal development project.
Local processing and retention
In the current development build, entered account information, credentials and retrieved headers are held in application memory for the session. The application does not intentionally persist these values to disk.
Closing the application ends that in-memory session. Clearing the current read removes the stored password and retrieved header snapshot from the application's active state; the account address can remain visible until the application is closed.
There is no developer-operated server that receives or stores mailbox data as part of the initial pilot.
OAuth token storage has not yet been designed or implemented. This policy does not claim that persistent OAuth token storage is already available.
Authentication and provider connections
The current development build includes an experimental password-based IMAP reader. Credentials entered into that flow are used for authentication with the email provider and are held in application memory for the session.
The intended account connection uses Yahoo's own sign-in and consent page with Authorization Code and PKCE. This OAuth flow is not yet implemented.
Once implemented and appropriately authorized, Yahoo would handle sign-in, while CanMailCleaner would receive the authorization response needed to request permitted access. The intended OAuth flow would not require the application to collect the user's normal Yahoo account password.
Connecting an account does not itself authorize mailbox modifications.
Third-party sharing and AI
The initial pilot does not upload Yahoo mailbox data to a developer-operated backend or send it to AI providers, advertising services or analytics services.
Communicating with Yahoo to authenticate and retrieve the requested headers is necessary for the provider connection.
Optional AI assistance is a future product goal. It is not enabled for Yahoo mailbox data in the current pilot. Any future transfer to an AI provider or other third party will require a review of applicable provider policies, updated disclosures and appropriate authorization before it is enabled.
User control
Reads are manually initiated and require a preview and explicit confirmation. The pilot does not perform unattended background synchronization.
The user can cancel an active read and close the application to end the local session.
Ending a local session does not revoke credentials or permissions at Yahoo. Any application password or provider authorization must be managed separately through the user's Yahoo account settings. OAuth permission management is relevant when that integration becomes available.
Contact correspondence
If you email the developer, your email address and the information you include will be processed to respond to your request. That correspondence is handled through the developer's email provider.
Do not include passwords, access tokens or private message contents in support correspondence.
Website hosting
These information pages are hosted using Hashnode. Website hosting is separate from CanMailCleaner's processing of mailbox data.
Hashnode's handling of website visitor information is described in its Privacy Policy.
Changes to this policy
This policy will be updated as the application's data handling changes. Material changes, including persistent storage, broader mailbox access, public distribution or third-party processing, will be described before those features are enabled.
Contact
For questions about this policy or requests concerning information provided directly to the developer:
Can Ürek
lmcgs@yahoo.com