Privacy policy

What we collect

• Account details: the email address and organization name given at signup, the IP address the signup came from, and whether the account made the capital-markets attestation, with who made it, when, and a hash of the statement.
• Console sign-in: WorkOS signs console users in. We store each member's WorkOS user ID and role.
• API keys: a key's public prefix and an HMAC of its secret. The secret is shown once, when the key is made, and we cannot read it afterwards.
• Requests and responses: for each API response we keep a log row holding the request, the plan Ask ran, and the response, encrypted, together with the response ID, the key, the capability, the mode and preset, the status, the IDs of the facts returned, and the time. An account chooses how long these rows are kept, or that they are not kept at all.
• Usage records: one row per response with the capability, the units used, whether it was billable, its status, the key, and the time. They hold no request content.
• Billing: the Stripe customer ID and a record of each purchase, refund, and dispute with its amount and Stripe ID. Card details go to Stripe; we never receive them.
• Reports and requests you send: wrong-fact reports and field requests.
• Operational logs, which never contain API keys, other secrets, or the content of requests.

The console uses a sign-in session cookie. The site sets no advertising or analytics cookies.

How we use it

• To run the service: sign you in, check your keys, answer requests, and let you compare a logged response with today.
• To meter usage and bill for it. Abstentions and errors are never billed.
• To prevent abuse: a limit on signups from one IP address in a day.
• To email you: signup verification codes, notices when a source's terms change in a way that affects what you are served, and low-balance alerts you can turn off.
• To answer your reports, field requests, and messages.

Model providers

When Ask cannot read a question with its fixed grammar, it sends the question to Anthropic to plan it. In standard and broad modes, Ask may send the facts it retrieved to Anthropic to write the answer, and every sentence is checked against those facts before it is returned. Content you send goes only to providers on an allow-list, and never to xAI's Grok. Resolve, Fetch, Search, and the other capabilities use no model.

Who else handles it

These companies process data for us, each only for the purpose shown:

• Stripe: payments and refunds.
• Resend: sending email.
• WorkOS: console sign-in.
• Cloudflare: Cloudflare R2 stores copies of the public source files we ingest, never customer data.
• Anthropic: the model calls of Ask described above.
• Vercel: hosting the site and the console.
• Railway: hosting the API service.

The database runs on a server Senal operates. We do not sell personal data.

How long we keep it

• Request and response log rows: 365 days unless the account sets another period, and none at all when it sets 0. A daily job deletes rows past their period.
• You can delete one logged response, or your whole history, from the console or the API. Deleting the whole history also destroys the account's encryption key for those rows.
• Usage and billing records are kept as financial records.
• Account details are kept while the account exists. To close an account, write to [contact email address].

How we protect it

• Logged requests, plans, and responses are encrypted with AES-256-GCM under a key for each account, which is itself encrypted with a key kept in a secret file.
• Row-level security in the database keeps each account's rows invisible to every other account.
• API keys are stored only as HMACs and compared in constant time.
• Each deletion of logged data writes an audit record.

Your choices

You can set how long responses are logged, delete them, revoke keys, and withdraw an attestation in the console. To see, correct, or delete other personal data we hold about you, write to [contact email address].

The service is for businesses and developers. It is not directed at children.

Changes

We will post any change here with a new effective date, and email account owners about a material change before it takes effect.