Privacy policy
This page describes the data flows in the BlinkInbox starter website. Review and update this policy to match the final website, hosting configuration, advertising partners, and applicable laws before launch.
Last updated: October 27, 2026
Important: BlinkInbox uses the third-party Neighbours.sh API. Inbox addresses are public: anyone who knows an address can read its messages. Messages are automatically deleted after 48 hours according to the provider's documentation. Never use a temporary inbox for confidential or sensitive information.
1. Information handled by BlinkInbox
The website is designed as a static browser interface and does not include a BlinkInbox application database or server-side email storage in this version. When you generate an address or check its inbox, your browser sends requests directly to the Neighbours.sh API. The provider may process your IP address, request metadata, mailbox address, and incoming email content as needed to operate its service.
The browser keeps the active mailbox address in session storage so the page can continue refreshing that inbox while the browser tab's session remains active. No provider login or bearer token is used by this integration. Because the inbox is public, anyone who knows or guesses the address may be able to read its messages. Avoid using the tool on a shared device.
2. Email and message content
Incoming messages are retrieved from the third-party provider and displayed in your browser. This starter interface displays message bodies as plain text rather than rendering email HTML. Do not use this service for passwords, bank information, healthcare information, private files, or other sensitive content. Mailbox retention and deletion are controlled by the third-party provider and may change.
3. Local browser storage
The site uses session storage to remember the current inbox during a browser-tab session and local storage to remember your light/dark theme preference. Clearing browser data or ending the session may remove this local state. The provider may still retain the mailbox according to its own retention rules; clearing your browser session is not a request to delete that remote mailbox.
4. Hosting logs and security
The static hosting provider may process basic technical information such as IP addresses, request timestamps, and browser details in server logs for delivery, security, and abuse prevention. Review the hosting provider's current privacy documentation for details. No website can guarantee perfect security or uninterrupted service.
5. Advertising and cookies
The site includes the Google AdSense script for publisher ID ca-pub-4853448997318239. Actual ad delivery depends on Google AdSense account and site approval, account settings, and ad availability. If ads are served, Google and its partners may process device identifiers, IP address, cookie data, and ad interaction information to provide, measure, or personalize ads, subject to Google policies and applicable consent requirements. Visitors in regions where consent is required may need a compliant consent-management experience before personalized ads are served. Review and update this section whenever advertising, consent tools, analytics, or other third-party services change.
For information about Google's advertising practices, review Google's advertising and privacy information. If visitors from the EEA, UK, or Switzerland are served personalized ads, applicable consent requirements may apply.
6. Third-party services
The current starter site directly connects to the Neighbours.sh API for disposable inbox functionality. Review the provider's current documentation and privacy information before launch. Links to other websites open under their own terms and privacy policies. BlinkInbox does not control these third parties.
7. Children
This tool is not intended for children under the age required by applicable law to consent to online services. Do not submit children's personal information through a disposable inbox.
8. Changes to this policy
This policy may be updated when the site changes. The site owner should update the date above and describe material changes to data collection, retention, advertising, analytics, or hosting.
9. Contact
The site owner has not yet configured a monitored contact email. Before relying on the service or sending a privacy request, check the Contact page for an updated contact channel. Do not send credentials or sensitive information to temporary inboxes.