Privacy Policy

1. Information we collect

Account information: email, the display name you optionally provide, and a hash of your password. If you sign in with Google, we also store the account identifier and email Google returns, so we can recognize the same account. We do not store your Google password.

Credentials and usage: your API keys, key labels, whether a key is active or revoked, and the time of the last successful call; your credit balance and credit ledger (amount, business type, and the related video or task id).

What you submit: when you call a data endpoint, we use the video or profile link you provide to complete the request. A transcription job also stores the original link, the language you selected, audio duration, and job status. Audio and caption results are stored in object storage.

Orders: the credit pack, currency, amount, order status, and the Stripe Checkout session id. Card numbers are handled by Stripe. We do not store the full card number.

Support: when you use Contact, the chat widget may receive your email, display name, and user id so support can recognize your account.

Logs: for security and troubleshooting, server access logs may include IP address, time, and request path.

2. How we use it

To create and verify accounts, send sign-in codes, keep you signed in, and provide the API, playground, and console.

To deduct credits under the published rules, complete credit-pack purchases and reconciliation, and avoid charging calls that fail.

To run the parse or transcription you request, return the result, and reuse an existing result for the same public content and the same settings.

To detect unusual use, prevent abuse, and answer your support requests.

3. How transcription results are stored and reused

A transcription job keeps the original link you submitted and stores the audio and caption result in object storage, so you can retrieve the result and so a later identical request can reuse it.

A result for the same public post and the same transcription settings may be reused for another user’s identical request. What is reused is the transcript itself. Other users do not receive your email, account, or API key.

4. Who we share it with

We do not sell your personal information. We share it only as needed for each function, with these providers:

Google, when you choose Google sign-in, to verify your identity.

Alibaba Cloud Direct Mail, to send sign-in codes to your email. A code is only for that sign-in, and it expires and is deleted shortly after.

Stripe, to take payment for credit packs, using the email and order details the payment needs.

Alibaba Cloud Object Storage, to store transcription audio and caption results.

Alibaba Cloud Model Studio (speech recognition), which receives the audio to be transcribed and returns the caption text.

Data providers, including TikHub and Supadata, which receive the link or content id needed to fetch the video or captions you asked for.

Chatway, which provides the on-site support chat. When you are signed in, your email, display name, and user id may be synced to it.

Beyond that, we disclose information only when the law requires it, or when it is necessary to protect the service, our users, or the public.

5. Cookies and local storage

The sign-in session uses a cookie named dm_session. It holds only a random token. The user id stays on the server. The cookie lasts 7 days.

Language preference uses a cookie named dataminer_locale, and a matching entry in the browser’s local storage, to remember Chinese or English.

The playground stores the API key you enter in your browser, together with the current account id, so a key from a previous account is not reused after you switch accounts. That copy stays in your browser.

6. How long we keep it

Account details, the credit ledger, and orders are kept while the account is active, so we can provide the service, reconcile payments, and handle disputes.

Original links, audio, and caption results from transcription jobs are kept so results can be returned and reused. Sign-in codes are deleted shortly after they are issued.

You can ask us to delete your account using the contact details below. After deletion, transaction records the law requires us to keep may remain. Other account data is deleted or de-identified.

7. Security

Passwords are stored only as hashes. The sign-in cookie does not contain your password or API key. Card details are handled by Stripe.

You are responsible for keeping API keys safe. Until you disable a leaked key, we cannot tell whether a call was made by you.

8. Your rights

In the console you can view your account, credits, and API keys, and disable a key at any time. You can change your display name on the account page.

You can ask us to correct or delete your account information, or to explain how a specific piece of data is handled. Contact us using the details below. We will act after we verify it is your account.

9. Children

The service is for users who can enter a contract on their own. It is not directed at children under 14. If we learn that we have collected a child’s personal information without a guardian’s consent, we will delete it.

10. Changes to this policy

We may update this policy. Updates are posted on this page with a new “Last updated” date. If a change materially affects your rights, we will also give notice on the site or to your registered email.

11. Contact

To use the rights above, or to ask about this policy, email support@snappdown.com or use Contact on the site.