Terms of service

This is a beta working draft, not a final agreement reviewed for legal compliance. nData's legal operator, jurisdiction, and governing terms have not been confirmed. These pages do not claim that any particular country's law applies.

The service is a developing beta for extraction and transcription of individual public posts. Features, provider availability, limits and workflows may change or be withdrawn. nData does not promise continuous availability, a response time, an uptime level, or a particular completion time.

Use accurate account information, keep your login and API keys private, and use only the access granted to your account and workspace role. Workspace owners control membership and billing settings; API keys carry workspace scopes and can be revoked. You are responsible for activity performed with credentials you control and should revoke a key you no longer need or suspect has been exposed.

Access may be limited where needed to protect the service, users, sources or providers, respond to abuse, or maintain the beta. Workspace closure and confirmed account deletion revoke access and preserve job and accounting history as described in the privacy policy.

Submit only an individual public post URL from a platform supported by the service configuration. nData does not accept private or authenticated feeds, profiles, feeds, search pages, or content that requires nData to use your social account. A syntactically valid URL does not guarantee that its platform, post, media or transcript can be retrieved.

Do not use nData to bypass authentication, access controls, rate limits or platform restrictions; to submit content you are not entitled to use; to violate another person's privacy or intellectual-property rights; to send unlawful or harmful material; to interfere with the service; or to probe, overload or evade its technical limits. Do not submit secrets, credentials or confidential material in prompts, schemas, templates, URLs or support messages.

Report suspected misuse or security issues through support. The operator still needs to confirm an abuse-handling and escalation process.

You remain responsible for the URLs, prompts, schemas, templates and webhook details you submit. You confirm that you have the rights and permissions needed to ask nData to process them for your use. Source-platform terms and third-party rights may also apply.

To provide the requested service, nData must store and process submitted material and may pass the necessary content to the configured processor and external source, speech-recognition or model services. Public-source media may be retained in a cache shared across workspaces, while prompts, prompt-derived evidence and results are kept within the submitting workspace or execution. See the privacy and data-handling policies for current details.

nData does not claim ownership of your submitted prompts or output. This draft does not grant you rights to source material that belongs to someone else or override platform terms.

Extraction and transcription use automated systems and external providers. Results can omit information, contain errors, reflect a stale retained source copy, or misinterpret speech or visual content. Schema validation checks output structure, not whether the result is true. Do not rely on a result as legal, medical, financial, safety, identity-verification, or other expert advice. Review important results against the source and use human judgment.

nData does not promise that a particular URL will succeed, that captions exist, that generated timestamps are exact, or that outputs meet your purpose. New API jobs are processed live when the required services are configured; the public anonymous playground displays static samples and does not create a processing job.

The free beta starts new personal workspaces with 100 one-time credits, with no automatic refill. Current default charges are 5 credits for a successful extraction and 2 for a successful transcription. A job reserves credits when accepted, then charges on success or releases its reservation on terminal failure. These credits are product accounting units, not a dollar amount or a final tariff. Existing granted credits are preserved.

Paid checkout, subscriptions, and the customer portal are disabled in beta billing mode. You can request more beta credits; a request does not guarantee a grant. The operator must confirm commercial pricing and payment terms before enabling paid access. No service level or credit-refund promise beyond the current job accounting behavior is made by this draft.

The beta may have bugs, limited capacity, provider interruptions, changing limits, or incomplete operational setup. nData may modify the product, supported sources, policies and features. A successful request acceptance means a job was queued, not that it has completed. Processing allowances and request quotas can limit submissions.

No uptime target, service credit, support response time, or guaranteed retention period has been established. The service may not be suitable for production-critical workloads.

Send questions, privacy requests, abuse reports, bug reports or feedback through the support form. It displays whether nData saved a ticket locally or queued it for email. Ticket content is retained indefinitely until the operator sets a retention policy, so avoid including information that is not needed to explain the request.

The legal operator, jurisdiction, final pricing and exact retention periods remain pending confirmation. These terms should be updated after the operator and applicable legal requirements are established.

Read the privacy policy or read the data-handling policy.