Privacy Policy
Last updated 30 July 2026.
This notice describes what querying.ai, operated by Opactor Inc., collects, why, who else sees it, and how long we keep it.
What we collect
- Account — email address and sign-in identity, handled by our authentication provider (Clerk). We never see or store your password.
- API keys — stored only as a hash plus a short display prefix. A key’s full value is shown once, at creation, and cannot be recovered afterwards.
- Task content — the prompt or query you submit, and the answer and sources returned.
- Request metadata — timestamp, path, HTTP status, duration, which key was used, IP address and user agent.
- Billing — plan, subscription status and credit ledger. Card details are handled entirely by Stripe; they never reach our servers.
Who else sees it
- The target engine. Running your task means sending your prompt to the engine you selected (for example OpenAI, Google, Perplexity or Naver), where that provider’s own terms and privacy notice apply. Do not submit personal or confidential information in a prompt.
- Network providers. Requests leave through commercial proxy networks, and Google AI Overview and AI Mode are collected through a scraping vendor. Those providers carry the request in transit.
- Infrastructure. Google Cloud (Seoul region) hosts the service, database and archive. Clerk handles authentication; Stripe handles payments.
We do not sell your data, and we do not use your prompts or results to train models.
How long we keep it
- Tasks stay queryable through the API for about 24 hours after completion.
- Request logs are kept in the live database for about 2 days.
- Both are then moved to an archive (Cloud Storage and BigQuery) which we retain for billing, security and abuse investigation.
- Billing records are kept as long as accounting and tax rules require.
Cookies
The site sets only the cookies needed to keep you signed in, via Clerk. There is no advertising or third-party analytics tracking on this site.
Your choices
Email us to access, correct or delete your account data, or to have archived task content erased. Deleting an account cancels the subscription and removes its keys; some records are retained where law requires it.
Security
Secrets are held in a managed secret store, keys are hashed, database access is private, and every task is scoped to the account that submitted it. If you believe you have found a vulnerability, report it to the address below before disclosing it.