Does Talkala store my card number?
No. Card details go through Stripe. Talkala keeps the billing records it needs (top-ups, invoices, payment-method summaries) but never touches the full card number.
Talkala needs certain data to work. Your account info, billing records, call details, number assignments, and support messages. This page tells you exactly what gets processed, who touches it, and how to ask questions about any of it.
The short version
Your account needs a few things to function: email address, password hash (never the plain-text password), display name, avatar, notification preferences, and security state like whether your email is verified. If you sign in with Google, that identity gets stored too.
Every call creates a record. Every charge creates a record. Talkala keeps all of this so your history works, your billing adds up, and disputes can actually be resolved. That means wallet-ledger entries, call records, rate context, number-subscription links, caller-ID verification state, and support metadata.
If you own a Talkala number, inbound SMS to that number gets stored. The inbox literally cannot work without the messages. If you contact support while signed in, Talkala stores the topic, priority, reply email, and message content needed to handle your request.
Talkala processes some browser and request data to keep sessions alive, prevent abuse, and maintain security. That means essential cookies, local storage, request fingerprinting for rate limits, and coarse country signals for billing and support context.
A small set of providers keeps the lights on. Stripe handles payments and billing. Twilio handles voice calls, SMS, caller-ID verification, and number provisioning. Vercel serves the app, hosts app assets, and provides aggregate web analytics. The backend stack stores product data. That is the full team.
Talkala uses your data to run the service, secure your account, prevent abuse, settle charges, show you your history, and answer your support questions. Data sticks around as long as it is needed for operations, security, financial records, dispute handling, or legal compliance. Some records stay even after you stop using a feature, because billing and audit history needs to remain accurate.
Want to know what data is tied to your account? Start with the contact or support pages. Some records are connected to billing integrity, fraud controls, and telephony reconciliation, so not everything can simply vanish on request. But Talkala will review what can be corrected, explained, or removed for your specific account.
Common questions
No. Card details go through Stripe. Talkala keeps the billing records it needs (top-ups, invoices, payment-method summaries) but never touches the full card number.
No. Call recording is not part of the product. Talkala does keep call metadata (destination, timestamps, duration, status, billing records) so your history and billing reconciliation work correctly.
Yes, for inbound SMS delivered to a number on your account. The inbox literally cannot function without the actual message content and metadata.
Use the contact or support pages with your account details and what you want reviewed. That is the right path for questions about account data, call records, billing, numbers, or privacy.
Next step
Use Security for the safeguards and Help Center for the operational rules that affect calling, billing, numbers, and support.