Terms of Service
The service limits below are read from the running code and are accurate. Everything else — the agreement itself, liability, termination, governing law — has not been written. Those are decisions for the operator and, where it matters, a lawyer. Do not treat this page as terms in force.
Service limits as implemented
Rate limits
- Screenshot requests are limited to five per fifteen seconds per
IP address; exceeding it returns
429. Saving a capture as a shared link draws on the same allowance. - Administrator login is limited to five attempts per minute per IP address.
Capture allowances
One capture means one submission — a single URL at a single viewport — however many regions it is sent to. A result served from cache is not counted, and a capture that fails to render is refunded.
- Not signed in: 3 captures per day, and 1 of those may be a forced fresh render that bypasses the cache.
- Free account: 10 captures per day and 50 per month — whichever is reached first applies — with up to 10 fresh renders per day.
- Paid account: 2,000 captures per month with no daily ceiling, and up to 200 fresh renders per day.
- An account whose email address has not yet been confirmed is held at the not-signed-in allowance until it is.
Days and months are counted in Western Indonesian Time (UTC+7), so a daily allowance resets at midnight Jakarta time and a monthly one on the first of the month there. These figures are the defaults the service ships with and are set by configuration, not fixed in the software.
Shared links
Pressing Share stores the capture that has just run and returns a link to it, which stays available for seven days and is then deleted. Saving a link does not consume a capture allowance, because no new render is performed — neither when it is saved nor when it is opened.
A shared link is unlisted rather than private: the identifier in it cannot be guessed and the page is not offered to search engines, but anyone who has the link can open it without signing in. Share accordingly.
Request bounds
- Viewport width must be between 320 and 2560 pixels.
- Viewport height must be between 240 and 1600 pixels.
- A worker that does not respond within 35 seconds is treated as
timed out and returns
504.
Blocked targets
Requests that resolve to local or private network addresses are refused before any render is attempted. This is an SSRF guard, not a policy choice, and it cannot be waived per request. The guard is re-applied to redirects and to sub-resources the page loads, so a target cannot reach a private address by bouncing through one.
What is not checked
Stated plainly because an acceptable-use policy has to be written against it: beyond the network guard above, the service performs no assessment of the sites it is asked to capture. There is no reputation, malware or content check, no blocklist of targets, and no review of what a user chooses to save as a shared link. A capture is whatever the target site returned to a browser at that moment.
There is also no self-service way to withdraw a shared link once it is created. It becomes unavailable when its seven days elapse; removing one sooner requires the operator to do it by hand.
API access
Programmatic access requires an API key issued from the administrator portal, sent as a bearer token. Usage is counted per key.
Acceptance of terms
Content required How a user accepts these terms and what happens if they do not.Acceptable use
Content required This one matters more than usual here: the service fetches third-party websites on a user's behalf. State what users may and may not capture, and where responsibility sits for the content they request. Shared links raise the stakes — a capture stops being something one person looked at and becomes content this service hosts on its own domain, reachable by anyone holding the link, for seven days. Cover at least: whether capturing a site behind a login or paywall is permitted, whether capturing a site the user has no relationship with is, who is responsible when a saved capture reproduces someone else's copyrighted or unlawful material, and what a rightsholder or subject should do to have one removed — noting that removal is manual today, so any promised response time has to be one a person can meet.Availability and support
For support, questions about these terms, or to report abuse, contact us at hi@pagefleets.com.
Content required Any uptime commitment, planned maintenance, and what happens when a region is unavailable.