Last updated: January 18, 2025

Privacy Policy

This Privacy Policy explains how Receive-SMSS.live collects, stores, and uses information when you browse public SMS inboxes, create an account, activate premium/private numbers, use our APIs, contact support, or interact with our advertising partners. The service is available in English and Arabic, and the same rules apply to both experiences.

How the platform works

Public numbers are visible to every visitor, while premium and private numbers, dashboards, coupon tools, and payment flows require a verified account.

Security first

Passwords are hashed, Google OAuth tokens are scoped to basic profile data, and reCAPTCHA protects forms against abuse.

Transparent billing

PayPal, NOWPayments, and invoice records are used to provision private numbers and comply with accounting laws.

1. How Receive-SMSS.live operates

The website lists phone numbers sourced through telecom partners so visitors can receive SMS verification codes without exposing personal phones. Public numbers display their message feeds to everyone. Premium numbers limit visibility to logged-in customers, while private numbers are tied to the purchasing account inside the dashboard. Temporary number APIs and “assign/release” endpoints let authenticated users programmatically request a slot for short sprints. Because message content is supplied by the sender, you should never ask third parties to send sensitive data to a public number.

2. Information we collect

Account & authentication data

  • Name, email address, preferred email language, and hashed password when you register manually.
  • Google OAuth ID, avatar URL, and verified email if you sign in with Socialite. No contacts or calendars are requested.
  • Email verification timestamps, login history, coupon redemptions, and dashboard preferences (such as dark mode).

Usage, network, and support data

  • IP address, device/browser type, language, referral URL, and theme cookie so we can localize content and stop abuse.
  • Logs showing which countries, numbers, or temporary assignments you open, plus rate-limit events and error diagnostics.
  • Messages that you send to support (contact form, WhatsApp support page, verification follow-up emails) including attachments and metadata collected by Google reCAPTCHA.

Payments & SMS content

  • We receive transaction IDs, payer references, billing country, and tax details from PayPal and NOWPayments to confirm private-number orders and fight fraud. Card numbers stay with the processor.
  • SMS bodies associated with public numbers remain publicly available while the number is active. Premium/private inboxes are only shown to the purchasing account but still pass through telecom carriers that deliver the messages to us.

3. Cookies, ads, and analytics

Essential cookies keep you signed in, store CSRF tokens, remember the language you selected, and persist dark/light theme choices. Google reCAPTCHA, Google AdSense (disabled on sensitive pages), and Cloudflare-level caching place their own cookies to secure the site and measure impressions. We do not run invasive fingerprinting scripts nor sell standalone cookie data to advertisers.

4. How we use information

Operating the service

  • Provision public and private numbers, display message feeds, and sync dashboard preferences across devices.
  • Authenticate users, enforce rate limits, detect spam, and block abuse of public numbers or contact forms.
  • Send transactional emails (verifications, payment receipts, expiration reminders) in your preferred language.

Improving and protecting the platform

  • Measure number uptime, carrier reliability, and overall SMS throughput to prioritize new countries.
  • Investigate outages, fraud attempts, or policy violations by reviewing relevant logs and support conversations.
  • Generate aggregated, anonymized usage statistics (for example, how many messages were received in the last 24 hours).

5. When we share information

Payment & compliance partners

PayPal, NOWPayments, invoicing services, and tax authorities receive the billing information necessary to process purchases and meet legal obligations.

Google services

We use Google OAuth for login, Google reCAPTCHA on forms, and Google AdSense on non-sensitive pages. These services collect diagnostic and usage data under their own privacy policies.

Infrastructure & support

Hosting providers, SMS carriers, content delivery networks, and email service providers help us deliver messages and support tickets securely.

We may disclose information if required by law, to enforce our Terms of Service, or to protect users and infrastructure from harm.

6. Retention & deletion

  • Account profiles, invoices, and premium/private number assignments are retained while your account is active and for the period required by applicable accounting and anti-fraud laws (typically up to 24 months after the last payment).
  • Public SMS messages remain visible for as long as the number is available on the site. When a number is retired, associated content is either deleted or archived offline for abuse investigations.
  • Support tickets and WhatsApp submissions are stored while the case is open and then archived for audit purposes.

7. Security measures

  • Passwords are hashed with bcrypt, OAuth tokens are stored securely, and all dashboards require HTTPS.
  • Only vetted team members with a support or engineering need can access administrative dashboards or production logs.
  • Rate limiting, firewall rules, and bot protection (including reCAPTCHA) mitigate automated abuse against numbers and forms.

8. Your choices & regional rights

  • You may browse public numbers anonymously. Creating an account is required only for premium/private numbers, dashboards, and API actions.
  • Manage your name, email, password, email language, and dark-mode preference from the dashboard. You can also revoke Google sessions from Google’s security center.
  • To request a copy of your personal data, delete your account, or object to processing (GDPR/UK/EU/other regions), contact us using the channels below. We respond within 7 days whenever possible.

9. Contact us

Email

[email protected]

Mention your account email or transaction ID so we can identify you quickly.

Contact form / dashboard tickets

Use the contact form or the Help & Support widget inside the dashboard for privacy questions, abuse reports, or takedown requests. reCAPTCHA protects the form, so you may be asked to complete a challenge.

If we make material changes to this Privacy Policy, we will announce them in the dashboard and update the “Last updated” date above.