Legal

Terms And Conditions

This page explains how SocialQuery handles public-data API accounts, service usage, operational records, cookies, privacy rights, and customer responsibilities.

Effective date: July 3, 2026 · Last updated: July 3, 2026

1. Agreement

These terms govern use of SocialQuery, including the public site, docs, dashboard, API, credits, generated files, and support surfaces.

2. Accounts and API keys

Customers are responsible for securing accounts and API keys, keeping keys server-side, and promptly reporting suspected unauthorized use.

3. Credits, billing, and refunds

SocialQuery uses credit-based pricing. Endpoint costs are shown before use, and customers are responsible for monitoring balances, usage, and billing records.

4. Acceptable use

Customers must use SocialQuery for lawful, approved public-data workflows and may not use it for harassment, credential harvesting, spam, unlawful profiling, or attempts to bypass security.

  • Comply with applicable laws and platform obligations.
  • Respect privacy, retention, and downstream processing requirements.
  • Do not resell, abuse, overload, or reverse engineer the service.

5. Service changes and availability

Endpoints, providers, cache behavior, pricing, and docs may change as platforms and upstream sources change. We aim to provide stable contracts and clear metadata.

6. Limitation and contact

The service is provided subject to the limits in these terms. Questions should be sent through the contact page or support dashboard.

FAQ

Terms And Conditions questions

Short implementation notes for coverage, costs, compliance, production behavior, and agent workflows.

Does this page cover public-data workflows?

+

Yes. The page is structured around SocialQuery's public data API, account, credit, cache, and provider-routing model.

Should this be reviewed before launch?

+

Yes. The structure is implementation-ready, but final legal wording should be reviewed for the business and jurisdictions involved.

Where can customers ask follow-up questions?

+

Use the contact page or dashboard support route so the request is tied to the right account context.