VOIDEK

Legal

Terms of Service

The operating rules for accounts, APIs, protected sites, quotas, beta use, and crawler defense decisions.

Last updated
June 22, 2026
Operator
Teero Inc.
Contact
voidek.dev@gmail.com
Launch note

These policies are production-oriented templates for the Voidek beta. Before paid checkout opens, add the final registered business name, representative, business registration number, mailing address, phone number, payment provider, and any required telecom sales registration details.

1. Agreement

These Terms govern access to Voidek, the website at https://voidek.dev, the dashboard, snippets, middleware, APIs, documentation, and related support services operated by Teero Inc..

By creating an account, installing Voidek on a site, calling the API, or using the dashboard, you agree to these Terms and any policy linked from them, including the Privacy Policy, Privacy Choices, Cookie Policy, and Data Processing Addendum. Refund, cancellation, acceptable use, and security rules are included in these Terms.

2. Accounts and authority

You must provide accurate account information and keep your login credentials, API keys, and environment variables confidential. You are responsible for all activity under your account and workspace.

If you use Voidek for a company, customer, or client, you represent that you have authority to bind that organization and to install bot-defense code on the protected properties.

  • Do not share API keys in public repositories, browser JavaScript, client logs, or screenshots.
  • Notify us promptly if credentials are exposed or a workspace is compromised.
  • Workspace owners are responsible for member access, protected sites, and configuration changes.

3. Service scope

Voidek provides crawler and automation defense tools, including request scoring, browser signal collection, challenge/block decisions, site registration, logging, quota reporting, and installation snippets.

Voidek reduces automated abuse risk but does not guarantee that every bot, proxy, scraper, headless browser, or malicious actor will be detected or blocked. You remain responsible for your own origin security, authentication, rate limits, backups, and incident response.

4. Beta and availability

During beta, features may change, break, or be withdrawn. We may add, remove, rename, or limit features to improve security, performance, reliability, or compliance.

You should configure protected production routes with a reasonable timeout and fail-open or fail-closed behavior appropriate for your risk. We recommend fail-open for critical public pages until your rules are tuned.

5. Plans, quotas, and billing

Free plans are limited by site count, monthly request quota, log retention, and beta availability. Paid plans, overage rules, refunds, taxes, invoices, and cancellation terms will become binding only after a payment provider and checkout terms are enabled.

When billing launches, the order page or checkout screen will control plan price, billing interval, taxes, quota, renewal, cancellation, and payment method terms. If there is a conflict between the checkout screen and marketing copy, the checkout screen controls for that purchase.

  • We may throttle, sample, or stop logging requests after quota limits to protect service stability.
  • Security-critical decision calls may be prioritized over dashboard analytics during high load.
  • Pro or custom plans may require written commercial terms.

6. Refunds, cancellations, and plan changes

Billing is not enabled during the current beta, and no paid subscription starts until a customer completes an explicit checkout or written order form. Once billing launches, the checkout screen or order form will control plan price, billing interval, renewal date, taxes, cancellation, downgrade, overage, and refund terms.

Unless the checkout or order form says otherwise, subscriptions renew automatically for the selected billing interval until cancelled. Cancellation normally stops renewal at the end of the current billing period.

Self-serve SaaS fees are generally non-refundable after the paid service period begins except where required by law, payment provider rules, checkout terms, or a written agreement. Downgrades normally take effect at the next billing period, and overage billing will not be introduced without clear pricing and controls.

7. Customer data and protected sites

You retain ownership of your sites, traffic data, configurations, and customer content. You grant Voidek a limited right to process request metadata, browser signals, logs, account details, and configuration data as needed to provide, secure, troubleshoot, and improve the service.

You must ensure that your own privacy notices and contracts allow you to send request metadata and security telemetry to Voidek. If you protect a third-party property, you are responsible for obtaining the required permission.

8. Acceptable use

You may not use Voidek to attack, scan, overload, scrape, or evade protection on systems you do not own or control. You may not reverse engineer the service to bypass detections, resell access without permission, or use Voidek for unlawful surveillance or discrimination.

We may suspend accounts, block API keys, or remove protected sites when activity threatens the service, our infrastructure, other users, or third parties.

  • Allowed testing must be limited to systems you own, control, or have written permission to assess.
  • Do not use Voidek to improve bot evasion, credential stuffing, spam, phishing, scraping, malware, or fraud.
  • Stop live testing if you see sustained 5xx responses, visible user-facing breakage, data loss, or infrastructure instability.

9. Third-party services

Voidek relies on hosting, DNS, deployment, database, email, analytics, payment, and monitoring providers. Third-party terms may apply to your use of integrations, payment checkout, or hosted infrastructure.

We are not responsible for third-party service outages, policy changes, fees, or data processing except to the extent required by applicable law or a separate written agreement.

10. Security and responsible disclosure

Report suspected vulnerabilities to voidek.dev@gmail.com. Do not access, alter, exfiltrate, destroy, or disclose data that is not yours. Give us a reasonable time to investigate and remediate before public disclosure.

We may collect logs, IP addresses, user agents, headers, and browser signals to detect abuse, debug incidents, verify account activity, and protect the platform.

  • Voidek is not a substitute for origin authentication, authorization, secure coding, backups, WAF rules, DDoS protection, or incident response.
  • Do not perform destructive testing, persistence, data exfiltration, social engineering, spam, or denial-of-service against Voidek.
  • Customers are responsible for API key storage, protected route configuration, timeout and fail mode, and their own user-facing privacy notices.

11. Disclaimers and liability

To the maximum extent permitted by law, Voidek is provided as-is and as-available. We disclaim implied warranties of merchantability, fitness for a particular purpose, non-infringement, and uninterrupted or error-free operation.

To the maximum extent permitted by law, we will not be liable for lost profits, lost revenue, lost data, security incidents caused by your configuration, business interruption, or indirect, special, incidental, consequential, exemplary, or punitive damages.

12. Termination

You may stop using Voidek and request account deletion at any time. We may suspend or terminate access for Terms violations, security risk, non-payment after billing launches, unlawful use, or prolonged inactivity.

Sections about confidentiality, data rights, payment obligations, disclaimers, liability limits, dispute handling, and records needed for compliance survive termination.

13. Changes

We may update these Terms as the product, law, or risk profile changes. Material changes will be posted on the site or sent to the account email when practical. Continued use after the effective date means you accept the updated Terms.