Privacy Policy & Ephemeral Telecom Architecture
We engineer virtual telecom interfaces under a simple premise: minimize what we store, keep verification payloads short-lived, and give you clear control over your account footprint.
Privacy-First Architecture & Ephemeral Relay Philosophy
Virtual-sims.com is engineered as an ephemeral routing proxy rather than a long-term telecommunications vault. Conventional telecom models may warehouse call detail records and message content for years. Our product focuses on short-lived verification sessions.
Incoming SMS is treated as a transient transaction: received, shown in your dashboard or API response, and scheduled for deletion according to activation and retention windows.
Ordinary account creation does not require legal name, physical address, or national ID. We ask only for what is needed to operate the account and payment flow.
Data We Minimize (What We Aim Not To Keep)
To reduce unnecessary telemetry, we avoid collecting or retaining categories that are not required to run the service:
We do not run ad pixels or commercial CRM bots for behavioral advertising.
We do not use canvas/WebGL fingerprinting for advertising or resale profiles.
We do not provide phone-book sync or social-graph scraping features.
We do not keep permanent full-text SMS archives beyond short operational windows.
Note: Essential security signals (for example authentication cookies and abuse prevention) may still be processed as described below and in our cookie notice.
Essential Data We Process During Active Sessions
To route OTP codes and operate your wallet, we process a minimal operational footprint:
- Account identifiers: email (or login identifier), session cookies, and API tokens needed to keep you signed in and authorize requests.
- Temporary MSISDN assignment: the rented number for your activation, typically active for about 15–20 minutes.
- Wallet & ledger units: balance, deposits, escrow holds, and transaction history needed for billing integrity.
- Security & abuse signals: limited connection metadata may be used to protect accounts and infrastructure against fraud.
Lifecycle of an Inbound SMS Verification Payload
Typical flow from carrier reception to purge:
Physical SIM banks / carrier interconnects receive inbound SMS for the leased number.
The message (or extracted OTP) is shown in your dashboard and/or returned via API for the active activation.
If a qualifying code arrives, escrow settles. If the window expires with no code, credits restore automatically.
Activation data and message content are removed according to retention rules (short operational windows, typically within 48 hours for transient mail/OTP display needs).
Blockchain & Cryptomus Ledger Privacy
We prefer cryptocurrency top-ups via Cryptomus to reduce reliance on traditional card processors. Payment providers may process blockchain transaction hashes and invoice state. We do not store card CVVs or cardholder billing profiles for crypto deposits.
Deposits may be linked to invoice IDs and transaction hashes required for credit confirmation and dispute handling.
We do not sell personal information to data brokers for advertising.
Data Type Retention & Treatment Matrix
Approximate retention schedule (subject to security, legal, and operational needs):
| Category | Storage | Max retention | Notes |
|---|---|---|---|
| Inbound SMS / OTP display | Activation store | Activation + short purge window | Operational delivery only |
| Rented MSISDN session | Session / activation | ≈ 15–20 minutes active | Then reclaim |
| Crypto Tx / invoice refs | Accounting ledger | Financial record life | Billing integrity |
| Account credentials | Auth store | Until account deletion | Hashed secrets |
| Support tickets | Helpdesk store | While needed to resolve | User-submitted content |
Third-Party Integrations & Sub-Processors
We work with infrastructure and payment partners necessary to deliver the service. Examples include carrier/SIM routing providers and Cryptomus for crypto invoices.
Cookies: essential cookies keep you signed in and secure the session. Optional preference or analytics cookies are used only if you accept them in the cookie dialog.
User Rights & Account Deletion
Depending on your location, you may have rights to access, correct, or delete personal data (for example under GDPR Art. 17 or CCPA-style statutes). You can request deletion via account settings where available, or by contacting support.
When an account is deleted, we remove or anonymize personal identifiers associated with the account, subject to records we must keep for billing, fraud prevention, or legal obligations (for example completed payment ledger entries).
Security Safeguards & Operational Hygiene
Browser and API traffic is protected with modern TLS.
Authenticated sessions and API tokens gate sensitive actions.
Transient OTP/mail data is not kept as a permanent archive.
Privacy Contact
For privacy questions, data requests, or security disclosures related to personal data, contact:
General support: support@virtual-sims.com