Privacy Policy

VoxaRTC is operated by Md. Shamsuzzaman, a sole proprietor in Bangladesh, who is the data controller for the information described here. Contact: support@voxartc.com.

Where you use VoxaRTC to serve your own users, you are the controller of their data and we act as your processor.

Worth saying first, because it is the question people actually have: we do not record, store or listen to the contents of your calls. Audio and video are relayed between participants and then gone. There is no recording feature that we operate on your behalf, and no archive to subpoena, leak or hand over.

We also never see payment card details. Those go directly to Paddle.

• Account data — the email address you sign up with, a scrypt hash of your password (never the password), and the company name you supply.
• Call metadata — for each session: which App ID and channel name it belonged to, the participant identifier your application supplied, when it started and ended, how many seconds it lasted, and whether video was on. This is what your invoice and your usage dashboard are computed from.
• Project data — App IDs, App Certificates and project names you create.
• Technical logs — IP address and request metadata, kept briefly to debug faults and to rate-limit abuse.
• Billing records — the subscription status, plan and customer identifier that Paddle sends us. Not card numbers.

The participant identifier is chosen by your application. If you pass us a real name or an email address as the identifier, we will store that; if you pass an opaque id, we will store that instead. We recommend the latter.

• To provide the service you asked for — performance of our contract with you.
• To bill accurately, and to prove what we billed for.
• To keep the service up and to stop abuse — our legitimate interest in a working, un-abused platform.
• To meet legal and tax obligations.

We do not sell personal data, we do not share it for advertising, and we do not profile you.

• Paddle.com Market Ltd — our merchant of record, which processes payments and holds the billing relationship. Paddle receives your email and billing details directly from you at checkout.
• Infrastructure providers — the hosting on which the service runs.
• Authorities, where we are legally required to — noting again that call content does not exist to be handed over.

• Account data: while the account exists, then deleted on request.
• Call metadata: retained as billing history, because it is the record of what you were charged for.
• Technical logs: days, not months.
• Billing records: as long as tax law requires.

Only essential ones. Signing in sets a single httpOnly session cookie that holds an opaque random identifier and nothing else — the account it stands for is looked up server-side. It expires after 12 hours or when you sign out.

There is no analytics, no advertising pixel and no third-party tracking script on this site. Paddle sets its own cookies inside the checkout window when you buy; those are described in Paddle's privacy policy.

You may ask for a copy of your data, ask us to correct it, ask us to delete it, or object to processing. Email support@voxartc.com and we will respond within 30 days. If you are in the UK or EU you may also complain to your local supervisory authority.

Deleting an account removes account and project data. Billing records are kept where tax law requires it.

Our infrastructure and our providers may process data outside your country. Where that happens we rely on appropriate safeguards, such as the European Commission's standard contractual clauses.

We will update this page when our practices change, and change the date at the top. For material changes we will email the address on your account.