File expiry
Know what stays local, what expires, and what you must store yourself.
BoringKit is designed for short-lived utility processing. Browser tools avoid upload; worker jobs use temporary input and output objects; account history depends on plan limits.
File handling by processing type
Browser tools
Input and output stay in the browser tab. BoringKit does not receive or store the submitted file or text for these tools.
URL checks
URL metadata requests fetch public pages through a protected URL fetch and return a JSON result. Store anything you need in your own system.
Worker input
File inputs are uploaded to temporary private storage only after a job is accepted. Upload intents expire quickly.
Worker output
Completed output is downloadable until the output expiry shown on the job. After expiry, download requests return download_expired.
Job metadata
Job status, timestamps, error reason, and output metadata remain visible according to account history and plan limits.
Plan history
Free
Short account history for basic usage. Move completed outputs to your own storage immediately.
Plus
Longer account history for regular individual usage. AI actions require Pro or higher.
Pro
Higher-volume account history and usage limits for heavier automation. Concrete AI actions may appear when supported and enabled.
Business
Shared workspace history, priority queueing, and team usage limits for small teams. AI is exposed only for supported actions.
Custom
File-expiry, support, compliance, and optional AI routing needs can be agreed in the custom plan.
Operational checklist
- Read
expiresAtand output metadata from the job response. - Download successful output before expiry and store long-lived files in your own system.
- Do not treat download URLs as permanent links; request a fresh intent while the output still exists.
- For sensitive workflows, prefer tools that run in the browser when the catalog supports them.