BoringKit questions, answered clearly

BoringKit is a utility workspace for practical everyday work: documents, PDFs, images, video/audio basics, data cleanup, text tools, developer utilities, business documents, web checks, privacy/security checks, API jobs, and automation.

The product is built around a simple flow: choose a tool, provide a file/text/URL, review options, run the job, then copy, download, or keep the result in your workspace when retention applies.

No. BoringKit is digital software. We do not sell third-party marketplace goods, ship physical products, charge delivery fees, or accept physical returns.

Paid checkout covers software access, usage credits, account features, queue capacity, file limits, retention, API access, and related digital functionality.

Yes. Public tool pages, pricing, API documentation, support pages, and policies can be browsed without signing in.

Running tools requires login so BoringKit can apply credits, upload limits, workspace ownership, abuse prevention, retained outputs, and support context consistently.

Login keeps the trial fair, prevents automated abuse, and lets BoringKit apply plan limits consistently. In-browser tools use 1 credit per accepted run while keeping input and output in the browser.

When a tool is truly in-browser, the file, text input, and output stay in your browser tab. BoringKit does not create a workspace run row for local tools by default; signed-in users may opt in to metadata-only local activity history when that setting is available.

Free: $0, 100 monthly credits, 25 MB file limit, and 7-day workspace history for trial and one-off usage.

Plus: $1, then $9/month, 5,000 monthly credits, 100 MB file limit, and 30-day history for personal daily tools.

Pro: $19/month, 10,000 monthly credits, 500 MB file limit, 90-day history, batch features, API access, AI tools, and webhooks for power users and freelancers.

Business: $49/month, 35,000 monthly credits, team seats, shared workspace, AI tools, and priority queue for small teams.

Custom: custom pricing for company/API-heavy use, dedicated workers, SSO, procurement, custom retention, and deeper support needs.

Credits are included monthly according to your plan. In-browser tools use 1 credit per accepted run. Worker jobs, server jobs, API jobs, AI-assisted features, and batch processing can consume credits after a run is accepted.

Failed validation should not cost credits. If the system rejects a file because it is too large, unsupported, unsafe, or missing required input, no run should be accepted and no processing credit should be charged.

Cost is based on processing weight, not whether a tool is browser or server only. Small text tools are cheap; file tools can scale by file size and batch count; document/image workers cost more; video/audio jobs usually cost the most because duration, codec, and output type matter.

AI-assisted features are available only on Pro, Business, and Custom. Text enhancement starts at 8 credits plus 1 credit per 1,000 input characters. Document or worker-backed enhancement starts at 12 credits plus 1 credit per 1,000 input characters.

BoringKit should block new paid/credited runs before processing starts and explain that credits are insufficient.

You can wait for the monthly refresh, upgrade, or contact support if you believe credits were charged incorrectly.

Monthly included credits are designed for active use during the billing period and normally do not roll over unless a specific plan or written agreement says otherwise.

Credit corrections for billing or processing errors are handled separately from normal monthly allowance.

In-browser tools should process the file in your tab when practical. Examples can include light text, simple data formatting, checksum, small image operations, or browser-capable PDF actions.

Worker/API tools upload input when server processing is needed, such as office document conversion, heavier PDF work, video/audio processing, batch jobs, retained output, or AI-assisted workflows.

File expiry depends on plan, tool, and output type. Free has short history; paid plans keep workspace records longer according to plan limits.

Server inputs are generally temporary. Outputs, job status, metadata, failure reason, credit entries, and expiry timestamps may remain visible in the signed-in workspace until the displayed retention period expires.

Workspace rows can be closed or hidden where supported so your active workspace stays clean.

Closing a row is not always immediate deletion. Audit metadata, billing ledger records, security events, abuse-prevention signals, and support context may need to remain for a longer period.

Queued and running jobs should have timeouts, cancellation checks, worker sweeps, and safeguards so late worker results cannot overwrite a canceled job.

If a job remains stuck, contact support with the job ID. BoringKit can use the job record to inspect queue state, failure class, credit reservation, and retained output metadata.

Queued jobs should be cancelable before processing starts. Running jobs may be cancelable when the processor supports cancellation-aware execution.

Credits reserved for jobs canceled before processing should normally be returned. Jobs that already consumed compute may follow the documented refund or partial-charge behavior for that tool.

A good tool should do more than run one command. It should validate input, explain options, reject unsafe or unsupported files, produce a useful output, show meaningful diagnostics, and make copy/download/report actions clear.

Where possible, tools should show output metadata such as file type, size, page count, dimensions, duration, codec, line count, detected fields, warnings, and before/after differences.

Office and PDF conversion depends on fonts, layout engines, embedded objects, page setup, images, language scripts, and document complexity. BoringKit should validate output quality where possible, but exact visual parity is not always guaranteed.

For important documents, review the output before sending it to customers, regulators, clients, or accounting systems.

BoringKit focuses on practical utility workflows. General tools such as convert, compress, mute, extract, resize, metadata, and generate should stay quick and direct.

When a workflow needs visual timing, crop handles, trim ranges, preview, or multi-step media adjustments, it should live in an editor-style surface rather than as a vague one-button tool.

Keep the job ID, input type, output type, and a short description of what is wrong. For documents, mention whether the issue is text, font, spacing, images, page count, or conversion failure.

Send that to support. If the issue is a processing bug, BoringKit can inspect worker metadata, fixture coverage, failure class, and retained output details where available.

No. BoringKit is utility-first. AI is not shown as a generic badge. It should appear only when a tool has a concrete action, useful output, privacy copy, plan gate, and live proof.

AI assistance is reserved for Pro, Business, and Custom. Plus remains a strong daily-tools plan, but tools that require AI should ask the user to upgrade to Pro or higher before processing starts.

BoringKit is provider-agnostic. AI routing can change based on runtime configuration, plan, availability, privacy controls, cost, and reliability.

User-facing behavior should describe the actual AI-assisted action without locking the product to one model provider.

No. AI output can be incomplete, inaccurate, or inappropriate for your context. Review AI-assisted results before using them in legal, financial, medical, safety, employment, regulated, or customer-facing decisions.

For sensitive workflows, compare the output with the original source and keep a human review step.

Yes. Paid plans may include API keys for server-to-server utility jobs, tool metadata, queued processing, polling, downloads, webhooks, and automation.

API keys are managed from the signed-in account area and should be treated like passwords.

Free users can view API documentation and upgrade prompts, but API key creation is for paid plans unless a specific agreement says otherwise.

Keys should support scopes or permissions so a key can be limited to the work it needs, such as reading metadata, creating jobs, reading job status, downloading outputs, using webhooks, or accessing specific tool groups.

Revoke keys you no longer use, rotate keys that may have leaked, and never expose API keys in browser-side code.

Checkout starts from BoringKit pricing and opens a BoringKit payment page tied to your signed-in account.

The page shows the selected plan, amount, supported currency, payment status, and security notes before opening the secure payment modal.

Public pricing may use USD for easy comparison. The payment flow may use a supported local or provider-specific currency and must show the final payable amount before payment.

International payment support is still in progress. Contact support for cards, invoices, procurement, or unsupported payment methods.

Yes, where subscription management is available. Cancellation stops future renewals but does not automatically refund previous charges outside the refund rules.

You should keep access for the paid period unless the plan, provider, or support decision says otherwise.

Most first-time paid subscriptions may be reviewed within the refund window if usage is consistent with evaluation and the account has not violated the Terms.

Duplicate charges, wrong-plan activation, failed activation after verified payment, and billing errors are investigated separately and corrected where verified.

Refunds may be denied for substantial usage beyond evaluation, consumed API usage, processed credits, abuse, fraud signals, chargeback abuse, custom procurement work, enterprise commitments, or accounts that violate the Terms.

No. BoringKit does not sell personal data. Data is used to provide the service, secure accounts, run tools, maintain workspace history, support billing, prevent abuse, debug failures, and improve reliability.

Only if you have authorization and your plan, organization policy, and applicable law allow it.

For sensitive or regulated data, review the tool path, file expiry window, API behavior, output sharing, and any enterprise agreement before uploading.

BoringKit uses account-scoped access, session checks, upload limits, accepted-type validation, API key revocation, retention controls, runtime secret management, monitoring, rate limits, and queue safeguards.

No online system is risk-free, so users should avoid uploading data they are not authorized to process.

Email support@boringkit.com. Include your account email, plan, relevant job ID, tool name, file type, expected output, actual output, and screenshots when useful.

Do not send full card numbers, passwords, API keys, or sensitive payment credentials by email.

BoringKit is digital software for utility processing, not a marketplace and not a physical-goods business.

Reviewers can contact support@boringkit.com for product clarification, checkout evidence, test access, billing-flow questions, or policy documentation.