Is my card number stored on Talkala?
No. Card numbers, CVCs, and expiry dates are processed entirely by Stripe. Talkala receives only the last four digits, card type, and expiry date for display in your billing settings.
Some things in Talkala deserve a direct answer: what the app can access, what it stores, and what it cannot touch. This page covers each one specifically.
The short version
Before any call, your browser asks whether Talkala can access your microphone. That permission request is issued by the browser itself and shows the browser's native dialog, not a custom one from Talkala. If you deny permission, calls cannot start.
You can revoke microphone access at any time in your browser or device settings. Talkala has no path to the microphone that bypasses the browser permission system.
Talkala does not record call audio and does not instruct Twilio, the underlying call carrier, to record calls. The spoken content of a call never touches Talkala's servers.
Talkala stores only call details needed for your history and billing: the number called, when the call started, how long it lasted, what it cost, and whether it connected. Those details are not playback or transcripts.
Top-ups go through a Stripe-hosted payment flow. Your card number, CVC, and expiry date are entered directly into Stripe and processed there. Talkala never sees the full card details.
After a successful payment, Stripe returns only a summary: the card's last four digits, card type, and expiry month and year. That summary is what appears in your billing settings.
Every completed call creates a record in your account with the destination number, call duration, outcome, and the amount charged. That record drives your call history and billing receipts. It does not include audio.
Internal audit logs that reference your number use a masked or hashed version, not the full digits. Contacts you save are stored under your account only and can be deleted individually at any time.
To place a call, your email address must be verified first. Talkala also enforces daily call and minute limits per account, blocks calls to premium-rate and shared-cost number ranges, and can flag or block accounts that show signs of abuse.
These controls apply to everyone on the platform. New accounts face the same limits as established ones because the rules exist to protect the service as a whole, not to single out individual users.
There is no self-service account closure button. To close your account, contact the support team through the in-app support form or the contact page.
When an account is closed, payment methods are detached from Stripe, any phone numbers you purchased are released from Twilio, and active subscriptions are canceled. For data deletion requests beyond that, the privacy policy covers the process.
Common questions
No. Card numbers, CVCs, and expiry dates are processed entirely by Stripe. Talkala receives only the last four digits, card type, and expiry date for display in your billing settings.
No. Microphone access requires explicit browser permission, and that permission is controlled by your browser, not by Talkala. You can revoke it at any time in your browser or device settings. Without permission, no call can start.
No. Talkala does not record call audio and does not enable call recording through Twilio. Call records contain the destination number, duration, cost, and outcome only.
Email verification is a basic fraud-prevention check. International calling services are a common target for abusive traffic. Verification, combined with daily call limits and blocked number ranges, keeps Talkala usable and trustworthy for everyone.
Contact the support team through the in-app support form or the contact page. Account closure is handled by the support team. When closed, your payment methods are detached from Stripe, any phone numbers you hold are released, and active subscriptions are canceled.
Next step
This page gives you the practical picture. The privacy policy and terms of service have the formal details.