Web
StoriBot can read the public web from its own cloud environment: fetch a page you link, or search when you ask. It never signs in anywhere.
What it does
Section titled “What it does”- Reads a page you give it. Paste a link and StoriBot fetches it: a web page, a PDF, a CSV, a company’s stylesheet. It reads what a plain client sees, with no browser session and no cookies, and pulls out what the work needs.
- Searches when you ask. “Find the latest quarterly on the ASX for this company.” It searches, reads the results it chooses, and tells you where each fact came from.
- Checks with you first. Before reaching anything external for the first time in a piece of work, StoriBot says what it is about to read and why.
Everything it reads this way is treated as reference material, like a file you uploaded. Numbers you want traced to source belong in a connected system, not on a web page.
What it does not do
Section titled “What it does not do”- It never signs in as you. StoriBot holds none of your passwords, cookies or sessions. It cannot read anything behind a login, a paywall or a consent wall, and it does not ask you for credentials to get past one.
- It does not act on a site. No forms, no purchases, no posting. Writing into a system only happens through an integration you granted.
- It respects a refusal. Some sites block automated access. StoriBot does not work around that; it tells you the page could not be read.
- It does not crawl. It reads the pages the work calls for, not a site top to bottom.
Where the request comes from
Section titled “Where the request comes from”The fetch is made from StoriBot’s own cloud environment in AWS Sydney. A site sees a request from there, never from your machine, your network or your accounts.