Security and Data Use

How we use your data

Your prompts, brand and domain lists, monitor settings and webhook addresses, and the answers, sources and analyses we return, serve your account alone. We use them to deliver your results, bill your usage and help you when you ask.

• Each task, monitor, batch and request log belongs to the account that created it, and the API and dashboard return it only to that account.
• The AI Index and every dataset we publish come from prompts our own team runs.
• We train no models on your data. Model providers that analyze answers for a feature you request process them under API terms that exclude training.
• Automated quality checks that read answer text use only the traffic our own team sends.

Where it is stored

• Google Cloud in Seoul, South Korea (asia-northeast3) holds the database and the archive of answers older than two days.
• The API and dashboard use TLS. Google Cloud encrypts stored data, the database accepts only encrypted connections through Google's connector, and the archive blocks public access.
• API keys are stored as SHA-256 hashes, and service credentials live in Google Secret Manager.

Who can access it

• You, through your API keys and dashboard.
• Named querying.ai operators, to run the service and answer your support requests. An operator's view of a customer dashboard is read-only and logged.
• Production cloud access is limited to company administrators and the service's own accounts.

Who else processes it

• The engine you choose receives your prompt. We send it from our own accounts or anonymous sessions without your identity, and the engine provider's terms apply.
• Commercial network providers carry engine requests over encrypted connections.
• Google Cloud hosts the API, database and archive. Vercel hosts the website and dashboard. Google Analytics and PostHog measure visits to the public website only; they receive no API requests or dashboard data.
• Citation Analysis analyzes answers with cloud AI providers and fetches the public pages an answer cites.
• Answer analysis sends the question, the answer and the brands you list to Microsoft (Azure OpenAI).
• Prompt research sends your topics to OpenAI and keywords to Google Ads and Naver Search Ad. Monitors send their answers to OpenAI and brand names to Parallel to find competitors, and prompt suggestions send your brand details to Google (Vertex AI).
• Clerk handles sign-in, Stripe or Polar handles payments, and Resend sends account email.

Retention and deletion

• Polling returns a result for 24 hours after it completes, and the dashboard shows the last 30 days.
• Tasks, answers and request logs stay stored until you ask us to delete them, so past usage and billing remain auditable.
• To delete your content, email contact@querying.ai from your account email. Within 30 days we erase your prompts, answers, webhook addresses, monitors, batch contents and request IP addresses. Usage and billing records stay for accounting.
• Database backups roll off within 14 days, replaced archive files within 7 days, and operational logs after 30 days.

Agreements and security reviews

Business customers can sign a data processing agreement (DPA), and we answer security questionnaires. Write to contact@querying.ai.