Privacy, written for people who commit notebooks to repositories
This page explains what the service needs to run your account and how to avoid leaking more than you intend. It is general by design.
CranSEO research team ·
Your account
Sign-in is by Google account only. We receive the identity details Google shares when you approve the sign-in, and we use them to create and recognise your account.
Beyond that, we keep what the service needs to function: your API keys, your credit balance and the record of calls and top-ups made on your account. We do not run a separate mailing list from it.
Top-ups are made in USDT (TRC-20) from the account page. A blockchain transfer is public by nature, so think about that before you send funds from a wallet you want to keep private.
What a call reveals
| Part of a call | Who can see it |
|---|---|
| The domain in the q parameter | Us, since we answer the question |
| Your key | Us, and anyone who can read your code or logs |
| The URL, if the key is in the query string | Proxies, CI logs and shell history on your side |
| Free actions with no key | Us, without any tie to an account |
Habits that protect you
Keep keys out of notebooks. Put them in .Renviron or your CI secrets store.
If a key leaks into a repository, assume it is public: replace it from the account page and review recent usage there. The Authorization header keeps a key out of URLs, which is tidier for logs.
We may update this page as the service changes, and the date at the top shows when it last changed. For questions about your data, use the account page, which is the way to reach us.
If you share a notebook
Sharing is where leaks happen. A notebook saved with output cells can print a key or a URL that contains one.
Clear outputs before you commit, keep the key in an environment variable, and prefer the Authorization header to the query string so URLs in logs stay clean. Free actions need no key, so a public demo should use only those.
Our own pages are the same: the action glossary and the budget page show example calls with a placeholder key, never a real one, and we ask that you do the same when you write about your setup.
Questions about your account or data go through the account page after you sign in. We do not publish a separate mailbox on this site.