Privacy Policy

Effective date: October 24, 2026.

Airbnb Local Mail Listener is a private desktop application operated by its account owner for managing their own rental-property notifications.

Access and purpose

The application requests Gmail read-only permission. This permission allows reading mailbox content, even though routine local filtering is designed to process relevant Airbnb notifications. It reads relevant message metadata and, when needed, notification excerpts to detect updates and prompt verification in Airbnb. It does not use Gmail permission to send email, delete messages, or modify mailbox settings.

Storage and processing

OAuth credentials are stored in macOS Keychain. Local databases retain operational metadata, checkpoints, identifiers, deduplication records, and processing status. Relevant notification excerpts and Airbnb website context may be processed by the operator’s configured OpenAI Work/Codex service to interpret events and assist with property management. Local records and service conversation history may have different retention periods; this policy does not promise automatic deletion or zero retention.

The public information website does not receive mailbox content or OAuth credentials. Hosting providers may maintain ordinary access logs under their own policies.

Use and disclosure

Google user data is used only for the operator’s requested monitoring and property-management functions. It is not sold, used for advertising, or intentionally made public. Necessary processing by configured service providers is limited to these functions. No claim is made here about service-provider training or retention terms without checking the operator’s actual account settings and agreement.

The application's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements.

Control and deletion

The operator can stop the local listener and revoke its Google Account connection. Revocation prevents future authorized access but does not automatically erase existing local records or service conversation history. To delete those records, the operator must remove applicable local application data and manage service history through the relevant service controls. Credentials should be removed from Keychain when the integration is retired.

Contact

chaiyiding@gmail.com