OTP Inbox Push

Privacy policy

Private prototype operated by Nishit Bhatt. Updated 6 November 2026.

Data accessed and purpose

With the account owner's consent, OTP Inbox Push uses Gmail read-only access to search recent mail and read candidate messages. This permission technically allows reading Gmail messages and settings; the implementation searches for recent OTP-like mail. It processes the sender, recipient account, subject, message content and timestamps to identify a code, its service and validity. It does not send, edit or delete email.

Google sends mailbox-change notifications through Google Cloud Pub/Sub to our private Railway backend. The backend then fetches matching mail. An independent Google Apps Script collector checks every minute as a fallback. The owner-configured iPhone Shortcut submits SMS text to the same backend. The current broad space trigger can forward ordinary personal and transaction SMS as well as login codes. It does not capture every possible SMS.

Storage and retention

OTP excerpts, codes, sender, account, service and timestamps are held in the private backend's memory for no more than ten minutes, bounded by the detected expiry. Expired entries cannot be retrieved. A service restart clears memory. Claims are also held in memory: after a restart, a still-valid recent email can be loaded again. The original email or SMS stays in its source mailbox; this retention rule applies to inbox copies.

Gmail refresh tokens and agent credentials persist in private configuration until removed or revoked, so background collection can continue. Google watch identifiers, connection state and operational metadata may persist separately. Infrastructure providers may retain their own operational logs; code bodies are not intentionally logged by the application.

Access and sharing

The private dashboard is restricted to the owner. Codes can be retrieved by agent clients explicitly connected by the owner, including Codex, Claude Code and the owner's ChatGPT agent. Retrieval sends the matching code to that chosen client and its provider to finish the authorized task; their own data policies also apply.

Google provides Gmail, Pub/Sub and the fallback collector. Railway hosts the inbox backend. OpenAI hosts the private dashboard and ChatGPT integration. Vercel hosts these public information pages, which contain no inbox data. Data is processed by these services only as needed to provide the tool. We do not sell Google user data, use it for advertising or use it to develop, improve or train generalized AI or machine-learning models. This version does not send mail to an AI model for classification.

OTP Inbox Push's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Chrome helper and optional SMS AI observation

The Chrome helper keeps its reader key, bridge address and saved behavior in extension local storage across restarts. Disconnect removes the saved key and seen-item history. Optional website permission lets it inspect login context and fill a fresh matched code in the selected tab. Site opt-outs are available. Payment fill or fill-and-submit requires a separate saved owner choice; filling alone can authorize a charge on some pages.

SMS AI observation is currently enabled for this personal instance. It sends whole fresh authenticated incoming SMS text to OpenAI, including non-OTP messages reaching the bridge, to compare message categories and extraction with the existing parser. It does not send Gmail messages to this model. AI predictions cannot select a production fill code or trigger a payment or other action.

The bridge keeps aggregate category, comparison, token and timing counts in memory, reset on restart or the next UTC day. It uses private message hashes for ten-minute duplicate suppression. It does not retain per-message AI outputs or codes in observation diagnostics. Responses requests use store:false; this is not zero data retention, and OpenAI provider retention policies still apply. Disable the observation setting and deploy to stop future AI requests; this does not delete data already subject to provider retention.

Control, disconnection and deletion

The owner can revoke OTP Inbox Push from Google Account connections, disable the fallback Apps Script collectors and iPhone automation, and remove agent connections. Revoking the push app alone does not disable the independent fallback collectors. Existing inbox copies expire within ten minutes. Contact Nishit through LinkedIn to request removal of stored connection credentials or report a privacy issue.

Current scope

This service is a personal prototype with no public registration. If it becomes a public service, its access controls, retention and this policy will be reviewed before onboarding other users. This policy describes current behavior and does not claim Google verification or a security certification.