Privacy Policy

Last updated: April 2026

1Our Philosophy

Privacy is core to Telenumerus. We built the service to require the minimum possible data. No email, no name, no tracking. You get an API key, fund it with crypto, and verify. That's it.

2What We Collect

i Data we store

  • API key (randomly generated, not tied to any personal identifier)
  • Telegram user ID (when using bots, required by the Telegram platform)
  • Order history (platform name, timestamps, prices — needed for billing and support)
  • Crypto deposit transaction hashes (for payment verification)
  • IP addresses in server logs (standard practice, rotated regularly)

3What We Don't Collect

Data we never touch

  • No email address
  • No real name
  • No phone number of the user (we provide numbers to you)
  • No payment card information
  • No cookies (no tracking, no analytics scripts)
  • No third-party trackers or advertising pixels

4Data Storage

Data is stored on encrypted servers. The database uses WAL (Write-Ahead Logging) mode with integrity checks. The audit trail is hash-chained for tamper detection—every record links cryptographically to the previous one.

5Data Retention

Order data is retained for 90 days to support dispute resolution and customer service. Phone numbers are recycled immediately after use. Inactive accounts are pruned after 180 days of inactivity.

6Data Sharing

We do not sell or share your data with third parties. Order data is sent to upstream SMS providers only as needed to fulfill orders. The information shared is limited to platform name and country—no personal identifiers.

7Your Rights

You can request a full export of your account data or request account deletion at any time. Contact support through any of our Telegram bots using the /support command.

8Crypto Payments

Blockchain transactions are public by nature. We store transaction hashes solely for the purpose of verifying deposit confirmations. We do not track or analyze your wallet addresses beyond confirming payment.

9Changes

We will update this page when our data practices change. The revision date at the top of this page reflects the most recent update.