Policy

Talkala Privacy Policy

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

Account and security data
Call, wallet, and number records
Stripe, Twilio, and Vercel processing

Account data Talkala keeps

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.

  • Email and sign-in identity keep your account working.
  • Passwords are stored as hashes. Never plain text. Ever.
  • Google sign-in is optional. It only works when configured for the workspace.
  • Email-password accounts stay in a verification-only state until you confirm your email address.

Records created by calling and billing

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.

  • Wallet balance is ledger-based. Credit entries, holds, captures, releases, and refunds are all separate, immutable entries.
  • Call records can include: destination number, country, line type, timestamps, duration, failure reason, and cost.
  • Number records can include: owned numbers, default voice/SMS assignment, and Stripe subscription links.
  • Caller-ID records can include: Twilio validation-call references and verification outcome.

SMS, support, and message content

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.

  • Launch-scope messaging is inbound SMS only.
  • Outbound SMS is not available in this version.
  • Support requests go to a configured inbox and include your signed-in identity context for follow-up.

Browser, device, and anti-abuse data

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.

  • Essential cookies and browser storage keep sign-in and preferences working.
  • Theme, layout, and presentation preferences can be stored in your browser.
  • Vercel Web Analytics can collect aggregate page-view data without third-party analytics cookies.
  • Rate limiting and fraud controls can use request fingerprinting and security-event records.
  • The product may record coarse country signals from requests or payment context. It does not store raw card numbers.

Who processes data alongside Talkala

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.

  • Stripe: card payments, hosted checkout, receipts, invoices, and billing portal.
  • Twilio: browser voice connectivity, PSTN calling, inbound SMS, caller-ID validation, and number provisioning.
  • Vercel: hosting, app delivery, blob storage, and privacy-focused aggregate web analytics.
  • Email delivery runs through the configured app mail transport.
  • Talkala does not need to store full card numbers to support wallet or number billing.

How Talkala uses and keeps data

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.

Questions, corrections, and privacy requests

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

Related questions

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.

Does Talkala record my calls?

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.

Does Talkala store SMS content?

Yes, for inbound SMS delivered to a number on your account. The inbox literally cannot function without the actual message content and metadata.

How do I ask about my data?

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

Want the security and product-rules picture too?

Use Security for the safeguards and Help Center for the operational rules that affect calling, billing, numbers, and support.