Privacy - TELRPC

Who we are

The controller of your personal data is Minutes Network FZ-LLC, Ras Al Khaimah, United Arab Emirates, which operates TELRPC. World Mobile Group Ltd. is our partner in TELRPC; it does not receive the personal data described here.

For any privacy question or request, write to contact@telrpc.com with "Privacy" in the subject line.

The short version

The TELRPC Wallet has no internet permission, so it cannot send us anything about you. We never see your keys or your card number. We process what is needed to answer a call, hold your credit, take a payment and reply to you, and we delete the digits of a call within 24 hours. This website sets no cookies and loads no third-party trackers. It counts visits with its own privacy-first analytics, which never stores your IP address.

What we process

Calls. The number a call comes from (its caller ID), the number it reached, its time and duration, and the digits keyed during it. We use the calling number to route the call, to send the echo back to it, and to apply per-number fair-use limits.

Wallet addresses and credit. The wallet address you top up, any addresses you link to it, your credit balance, each charge to it, and a record of each broadcast (chain, address, transaction ID, status). Each charge also records the calling number, for fair-use limits and support. When you link addresses on this website, we log the request with its IP address.

Payments. Card payments are taken by Stripe on its own hosted page; we receive the amount, time, status and Stripe's reference, never your card number. Crypto payments use our own checkout: we give you a one-time deposit address and read the public blockchain to see your payment arrive. We record the order, the amount and the paying transaction.

Contact form. Your name, email, company or organisation, role and message, and your IP address, which we use briefly to limit abuse.

Document requests under NDA. Your name, email, company, role, the documents you ask for and why, the time you accepted the NDA, your IP address, and how often your personal link is used.

Wallet Kit and waitlist. If you ask to be told when something is ready, your email. When Wallet Kit checkout is open, an order also needs your name, shipping address, email and phone number, taken through Stripe.

TELRPC Console accounts. The name, email and account details a partner gives us.

Server logs. Our web server records the IP address, time, page requested, the page that linked to it and browser type of each visit, to run and protect the site. We also count from it, without keeping the IP address, how many people download the wallet app and our documents, which addresses are not found, and how often search engines and link-preview services visit.

Website analytics. When you view a page, the site's own script tells our server which page it was, the address of the page or site that sent you there, any campaign tags in the link (such as utm_source), your browser's language, and how long the page was on screen. See Cookies and analytics.

Balance and sync pages. These pages run in your browser and ask public blockchain services directly for the address or transaction you enter. Those services see your IP address and the request; we do not receive it.

What we never collect

From the TELRPC Wallet: nothing. It holds no internet permission, so it has no network path to send telemetry, analytics, contacts, location or any key material, even in error.

Phone numbers in our logs are masked.

We never see card numbers, keys or recovery words.

Cookies and analytics

This website sets no cookies and stores nothing on your device: no cookies, no local or session storage, no advertising identifiers, no fingerprinting, and no third-party scripts, fonts or trackers. The only outside requests are the blockchain lookups that the balance and sync pages make from your browser when you ask them to.

Our own analytics. To understand how people find and use the site, we run first-party analytics on our own servers. No one else receives it, and it is never used for advertising or to profile you. For each page view, the site's script sends our server the page, the referring page or site, campaign tags in the link, your browser's language, and how long the page was on screen. From the request our server adds your country, the type of device (phone, tablet or computer), operating system and browser family, worked out from the browser's user agent.

No IP addresses are kept. To count unique visitors, our server combines your IP address and browser details with a random value that changes every day, and keeps only the resulting code. The daily value is deleted shortly after the day ends, so the code cannot be turned back into your IP address, and your visits on different days cannot be linked. Your country is looked up from the IP address in memory, using an offline database, and only the country is kept. A visit (session) is worked out on our server from this daily code; nothing on your device is used for it.

Do Not Track and Global Privacy Control. If your browser sends either signal, the script sends nothing and our server refuses any analytics request that carries one. Download counts come from our server log, which records every request whatever the browser signals, as all web servers do.

Country data. IP Geolocation by DB-IP, licensed under CC BY 4.0.

Why we use it, and on what basis

To provide the service you ask for (performing our contract with you, or taking steps you ask for before one): answering calls, broadcasting transactions, returning the echo, holding and charging credit, taking payments, handling document requests and running Console accounts.

To meet legal duties (legal obligation): payment, tax and accounting records, sanctions and anti-money-laundering duties, and duties that apply to telephone services.

To keep the grid fair and safe and to reply to you (our legitimate interests): fair-use limits, preventing abuse and fraud, securing our systems, answering messages, and understanding how the website is used through the cookieless analytics described above. We do not use your data for advertising or profiling, and we do not sell it.

Who receives it

Stripe, which processes card payments (and Wallet Kit orders when open) as an independent controller under its own privacy policy.

Voice carriers, which connect calls between your phone and our lines and so handle the calling number, the number called and call times, as every phone call does.

Blockchain nodes and RPC providers, which receive the signed transactions and the addresses we broadcast or read.

Hosting providers, which run the servers our systems use, on our instructions.

Public blockchains are public. A transaction you broadcast, with its addresses and amounts, is published to everyone, permanently. Neither we nor anyone else can delete it.

We disclose personal data to authorities only where the law requires it. We resist requests where the law allows, and keep a record of each request where the law does not forbid it.

International transfers

We are based in the United Arab Emirates. Our servers are in the United States and the European Union, and our providers may process data in other countries. Where the law of the country your data comes from requires a safeguard for the transfer, such as standard contractual clauses, we use it.

How long we keep it

Call digits. The digits of a call are held in memory while the call is decoded and broadcast. A processed frame is deleted from the grid within 24 hours of the call. A frame that arrives garbled is kept so the app's automatic redial can be matched to it.

Echoes. The caller-ID digits of an echo are kept for at most 24 hours in route records (1 hour in the echo queue), then reduced to the echo's type.

Call records. Call records (number, time, duration) follow carrier retention rules.

Credit and broadcasts. Transaction ledgers retain public identifiers (chain, address, transaction ID, status), never payload digits. Credit, charge and payment records are kept while the service runs and for as long as tax and accounting law requires.

Messages and requests. Contact messages, document requests and waitlist emails are kept while we are in contact, then deleted, unless the law requires us to keep them. Console account data is kept while the account is open.

Server logs. Web server logs are deleted after 14 days.

Website analytics. Individual page views and visits, which carry the daily visitor code but never an IP address, are deleted after 30 days. Daily totals (counts by page, source, country, device and language) are kept for 13 months, then deleted. The daily value used to make visitor codes is deleted within about two hours after its day ends.

Your rights

Depending on where you live, you may ask us to give you a copy of the personal data we hold about you, to correct it, to delete it, to restrict or object to our use of it, or to send it to you in a portable form. You may also complain to the data protection authority where you live or work.

To make a request, write to contact@telrpc.com with "Privacy" in the subject line. We reply within one month. To protect you, we may ask you to show the request is yours, for example by calling from the phone number concerned or by signing a message with the wallet address concerned.

Some limits apply: we keep records the law requires, deleting the records for an address also removes its credit, and data on a public blockchain cannot be deleted by us or anyone.

Wallet

Partners

Technology

More

Privacy.