Privacy
What we keep.
Seekyo fetches public web pages on your behalf, so it sees both your requests and other people's content. This page says what happens to each.
What you give us
- An email address, if you ask for a key, so we can send it and reply to you.
- An API key. We store a hash of it and never the key itself, which is why a lost key cannot be recovered, only replaced.
- Your requests: the query text, the starting URL, the limits you set, and the idempotency key if you send one. These are what we bill from.
What we store on your account
- Usage and ledger records: pages fetched and processed, semantic work done, the cost of each request, and every balance change. This is your invoice, and it is kept while your account is open.
- Run records and internal traces, kept on our servers so a crawl can be debugged. Traces hold far more than a response does, including pages that were fetched and then rejected, which is the point of keeping them. They are not returned in API responses.
Who else sees what
- Sites that are fetched see a request from our crawler. They do not see your key, your account, your query, or your end users.
- Our model provider receives the page text and the question. Judging whether a passage answers a question is done by an external model, so page content does leave our servers as part of serving your request. No account identifiers are attached to it.
- Nobody buys it. We do not sell your data or your queries to anyone, and we do not use your queries to build a general index.
Deleting things
Write to us and we will delete your account's records and revoke its keys. Some accounting records may be kept longer where we are required to keep them.
Keys and transport
Everything is served over HTTPS. Keys are compared by hash on every request, and a revoked key stops working immediately. Credit balances are held server-side; the API never trusts a client with a balance.