Privacy Policy

1. Introduction

RealNonVoIPUSNumber provides SMS verification infrastructure: a public website, authenticated dashboard, wallet deposits, verification orders, developer API, and customer support tools.

This Privacy Policy explains how we handle information when you visit the site, create an account, place orders, fund your wallet, use the API, or contact support. Related policies include our Refund Policy and the Contact page.

2. Information We Collect

Account information

When you register or manage an account we process details such as username, email address, language preference, notification preferences, referral identifiers, account status flags, and credentials. Passwords are stored using Django’s secure password hashing—not in plaintext.

Transaction information

We keep wallet balance records, deposit/top-up status, payment provider references, ledger transactions (including credits, debits, bonuses, and refunds), and related timestamps needed to operate billing and order charging.

Verification and order information

Orders may include service and country selections, provider identifiers used to fulfill the request, public order IDs, phone numbers assigned for a rental, order status, OTP/verification codes when delivered, pricing fields, refund status, and timestamps. Metadata may store operational details required to manage the rental.

Technical information

For security, support, waitlist, contact forms, admin audit events, API requests, and similar flows we may process IP address, browser user agent, and request timestamps. Server and application logs may also record diagnostic events.

3. How We Use Information

We use information to:

• Create and manage accounts and authenticate sessions
• Provide verification services and track order status
• Process deposits, wallet balances, and refunds to account credit
• Operate the developer API and enforce usage limits
• Respond to support tickets and contact messages
• Send service notifications according to your preferences
• Detect abuse, prevent fraud, and protect platform security
• Troubleshoot reliability issues and improve service quality
• Meet legitimate legal or compliance obligations when applicable

We do not operate a third-party advertising pixel or marketing analytics suite on this site based on the current public application configuration.

4. Account Information

Account data authenticates you to the dashboard, stores preferences (language, email/browser notifications, webhook URL), and supports referrals and account status controls. Staff may access account records when needed for support, security review, or administration.

5. Verification and Order Information

Order information is processed to place rentals with integrated SMS providers, show Active Numbers and History, apply wallet charges, handle cancellations and expirations, credit eligible no-OTP refunds, and investigate support issues. OTP values are retained as part of order records so you (and support, when needed) can confirm delivery status.

6. Payment and Transaction Information

Deposits are processed through our integrated crypto payment provider (Cryptomus). The payment provider processes payment-network details according to its own terms. RealNonVoIPUSNumber stores deposit records, provider payment/order references, amounts, bonuses, status, and wallet ledger entries so we can credit balances and show billing history.

We do not store full payment-card numbers. Card payments are not the primary deposit method in the current product; crypto deposit references and wallet credits are what we retain for account funding.

7. API Information

Developer API keys are stored as hashes with a visible prefix. The full secret is shown once when created or rotated and is not stored in recoverable plaintext. Webhook signing secrets are managed for outbound delivery and must be treated as confidential by the account holder.

API request logs may include endpoint path, HTTP method, status code, response time, request ID, IP address, and user agent—without request/response bodies or secrets— for usage visibility, rate limiting, and abuse prevention.

8. Support Communications

Support tickets may include subject, category, message text, status, and timestamps. Staff may add internal notes that are not shown to customers. The public Contact form collects name, email, subject, category, message, and may record IP address and user agent for abuse prevention.

Attachments are not part of the current ticket message model. We use support content to respond to requests, investigate order or billing issues, and maintain a support history.

9. Cookies and Similar Technologies

The platform uses essential cookies and related browser storage needed for operation, including:

• Session cookie — keeps you signed in to the dashboard
• CSRF cookie — helps protect forms and authenticated requests against cross-site request forgery

These are functional/security cookies. The current public site does not implement a separate non-essential cookie-consent banner for advertising trackers because such trackers are not part of the shipped front-end stack.

10. Analytics and Log Data

We do not embed third-party marketing analytics scripts in the public templates reviewed for this policy. We do maintain application and server logs, API request analytics as described above, admin audit logs, and operational monitoring needed for security, debugging, reliability, and abuse prevention.

11. Information Sharing

We may share limited information with:

• Payment processors to complete deposits and reconcile credits
• SMS verification providers to fulfill number rentals and deliver OTPs
• Infrastructure, hosting, and email delivery providers that run the service
• Authorities when legally required
• Successors in a business transfer, if applicable, under appropriate protections

We do not sell personal information. We do not claim that information is never shared with any third party—operating verification and payments requires limited sharing with processors and providers.

12. Service Providers

Third parties process only what is needed for their role—for example payment initiation and webhooks (Cryptomus), transactional email when SMTP is configured, and cloud hosting for the application and database. Provider credentials and private configuration are not published in this policy.

13. Verification Provider Data

To rent a number we send the minimum fulfillment details required by the selected provider integration (such as service and country/server parameters). Providers return phone numbers, status updates, and OTP content which we store on the order for your account. We do not list internal API credentials or private provider endpoints in this public document.

14. Data Security

We use reasonable technical and organizational measures designed to protect information, including HTTPS for site access in production deployments, hashed passwords, hashed API keys, CSRF protection on forms, authenticated dashboard and admin access controls, rate limiting on sensitive flows, and administrative audit logging. No method of transmission or storage is completely secure; we do not claim absolute security.

15. Data Retention

Information is retained for as long as reasonably necessary to operate accounts, preserve order and transaction history, provide support, prevent fraud and abuse, resolve disputes, and satisfy legitimate legal obligations. We do not publish a single fixed deletion calendar for all record types. Soft-deleted accounts may retain historical orders and ledger records for integrity and audit purposes.

16. Your Privacy Choices

Depending on your account access, you may:

• Update profile settings such as language and notification preferences
• Change your password through account security flows
• Manage API keys and webhook settings in the dashboard
• Contact support about account data or privacy questions

A full self-service data-export portal is not part of the current product. Privacy-related requests can be submitted via support for manual review.

17. Account Closure

End users do not currently have a self-service “delete my account” button in the dashboard. Account closure / soft-deletion is handled administratively (for example by staff after confirmation), and related order, transaction, and audit history may be preserved. Contact support if you need help closing an account or have a data-related request, subject to legitimate retention needs.

18. Children's Privacy

The platform is intended for adult users and business customers who can form a valid agreement to use paid verification services. We do not knowingly market the service to children. If you believe a minor has created an account, contact support so we can review appropriate next steps.

19. International Data Processing

Information may be processed where we or our service providers operate, which can include locations outside your home country. By using the service you understand that processing may occur in those locations under this policy and applicable law.

20. Third-Party Links and Services

The website and dashboard may link to external sites (for example documentation, Telegram updates, or payment provider pages). Those services have their own privacy practices. RealNonVoIPUSNumber is not responsible for the privacy practices of unrelated third-party websites.

21. Changes to This Privacy Policy

We may update this Privacy Policy when the product or legal requirements change. Material updates will be reflected by revising the Last Updated date on this page (currently October 01, 2026). We do not promise email notice for every editorial change; continued use of the service after an update means you accept the revised policy.

22. Contact Us

Questions about this Privacy Policy or how information is handled can be sent to our support team via the Contact page or email [email protected] .