N-Otp Mail · nezam
Privacy policy
Last updated: November 8, 2026
Operator and contact
nezam operates N-Otp at n-otp.com. Contact nezam.vip.official@gmail.com for privacy questions or data deletion requests. Do not include passwords, codes or secret keys in support messages.
Google data and its purpose
With the mailbox owner's consent, openid and the email scope identify the authorizing account, and gmail.readonly reads recent messages for a private inbox and operator-directed sharing of extracted sign-in codes. Data includes the mailbox address and provider identity, message sender, subject, content, extracted codes, safe action links, synchronization metadata and authorization tokens. We do not request permission to send, modify or delete mail, or ask for the Google account password.
Sharing and recipients
Authorized operators see their private inbox. A holder of an operator-created link receives codes and expressly shared subscription credentials within that link's policy, but not message bodies, email actions or OAuth tokens. Data is processed on our Hostinger-hosted server and necessary requests go to the selected mail provider. We do not sell Google data, use it for advertising or train general-purpose AI models with it, or transfer it for unrelated purposes. Human support access to content requires specific user consent unless necessary for permitted security or legal reasons.
Storage and protection
Only messages received after connection and within the recent five-minute window are imported. Copies stop being displayed five minutes after receipt at the provider and scheduled cleanup deletes them. Stored message content, codes, authorization grants and subscription passwords use AES-256-GCM encryption, with HTTPS in transit. Account, link and necessary connection metadata remain until deletion or disconnection; non-code quota and security records may be retained as usage evidence.
Backups and deletion limits
Temporary messages, codes, sessions and pending OAuth state are excluded from durable backups. Encrypted account recovery backups contain account and connection data and may include encrypted authorization grants. Deleting live data does not immediately erase older recovery archives; request their removal through the operator's deletion process. Restored mailbox grants must be invalidated before synchronization and fresh consent requested. We do not delete your original messages at the mail provider.
Control and disconnection
Disconnect a mailbox in N-Otp to remove its live grant, stop synchronization and block its links from accessing codes. Local disconnection is not Google-wide consent revocation; you can also remove N-Otp Mail in your Google Account connections settings. Delete the mailbox and its links from the dashboard, or use the data deletion page to request removal.
Limited Use
N-Otp'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. This policy is not a Google approval certificate; feature eligibility and restricted-scope access require Google's review.