Privacy Policy
This Privacy Policy explains how LibOTP (“we”, “us”) collects, uses, and shares information when you use our website and services. By using LibOTP you agree to this Policy together with our Terms of Service.
1. Who we are
LibOTP is a virtual SMS / OTP number platform with wallet billing and optional USDT recharge. Contact us via the in-app support tools on the Recharge page or through channels published by the site administrator.
2. Information we collect
- Account data: name, email, password hash (if you register), wallet ID, display name, ban status.
- Wallet & billing: balance, deposits, transaction hashes (TxIDs), network (e.g. TRC20 / BSC), package selections, approval notes.
- Activations: country, service, operator, phone number assigned, status, SMS code/text when received, timestamps, expiry.
- Support messages: message text, optional contact handle, wallet ID, admin replies.
- Technical data: basic server logs such as IP address, user agent, request paths, and error logs needed to operate and secure the Service.
- Preferences: settings stored in your browser (for example wallet ID in local storage, OTP sound preference).
We do not intentionally collect government ID or full payment-card data through the standard LibOTP wallet recharge flow (crypto deposits are verified on-chain).
3. How we use information
- Provide numbers, show SMS/OTP, and manage your wallet balance.
- Verify USDT deposits and prevent duplicate or fraudulent TxID submissions.
- Price services, prevent abuse, enforce bans, and improve reliability.
- Respond to support requests and operate the admin panel.
- Comply with law and protect LibOTP, users, and third parties.
4. Legal bases (where applicable)
Where privacy laws require a legal basis, we rely on: performance of a contract (providing the Service you request), legitimate interests (security, fraud prevention, product improvement), and consent where you voluntarily provide optional data (for example a contact handle in support).
5. Sharing
We may share data with:
- SMS / number providers necessary to obtain numbers and retrieve SMS status (API calls from our servers).
- Blockchain networks / explorers / APIs used to verify USDT transfers (transaction data is public on-chain).
- Infrastructure providers that host the site, database, or related systems under appropriate confidentiality.
- Authorities when required by law or to respond to lawful requests related to fraud or abuse.
We do not sell your personal information.
6. Cookies and local storage
LibOTP uses browser storage (such as localStorage / sessionStorage) to keep your wallet session, admin session (for operators), and UI preferences. These are required for the app to function. You can clear them in your browser; doing so may log you out or create a new guest wallet.
7. Retention
We keep account, activation, deposit, and support records for as long as needed to operate the Service, resolve disputes, prevent fraud, and meet legal obligations. You may request account deletion through Settings (where available); some records may be retained in anonymized or limited form for security and accounting.
8. Security
We use measures such as server-side API keys, hashed passwords, and access controls for the admin panel. No method of transmission or storage is 100% secure. Protect your wallet ID and password. Prefer HTTPS when accessing LibOTP in production.
9. International transfers
Your data may be processed in countries where our servers or providers operate. By using LibOTP you understand that data may leave your country of residence.
10. Your choices
- Update or delete account data where the app provides those controls.
- Stop using the Service and clear browser storage.
- Contact support to ask about access, correction, or deletion subject to law and fraud-prevention needs.
11. Children
LibOTP is not directed to children under 18. We do not knowingly collect personal data from children. If you believe a child has used the Service, contact us to remove the account.
12. Changes
We may update this Privacy Policy. The “Last updated” date will change when we do. Continued use after an update means you accept the revised Policy.
13. Contact
Privacy questions: use in-app support on the Recharge page or contact the LibOTP administrator through published channels.