What is SharkEyes
SharkEyes — lightweight protection service for forms and registrations that helps tell real users from bots. It focuses on privacy-friendly signals and simple integration.
General Questions
What is your service and how does it work?
SharkEyes is a protection system that keeps your website forms safe from bots, scripts, and abuse by real users. It analyzes form interactions, timing, and browser signals to detect suspicious behavior. To activate it, just add one <script> line and the data-sharkeyes attribute to your form — no backend setup required.
What is the purpose of a bot detection service?
The main goal of SharkEyes is to stop both automated bots and malicious users from abusing your website forms. It helps prevent spam, fake submissions, and repeated form misuse while allowing legitimate users to interact freely.
On which platforms can your service be used?
SharkEyes works everywhere — it’s fully client-side and doesn’t depend on your backend. Just include the provided <script> on your site and mark your forms with data-sharkeyes. That’s all you need to instantly add protection.
How does your system distinguish a bot from a real user?
SharkEyes uses browser-level behavior analysis: it checks timing, interaction patterns, and simple environment data like IP address, HTTP headers, and user agent. None of this information is stored or visible to anyone — it’s processed instantly and then discarded.
How accurate is your detection system?
Even in its early development stage, SharkEyes achieves high precision by combining behavioral and environmental checks. It effectively blocks bots and form abuse attempts while keeping legitimate users unaffected and anonymous.
How long does it take to verify one user?
Verification happens instantly in the user’s browser. There’s no delay, no backend communication, and no visible verification steps — everything runs quietly in the background during form interaction.
Are there any limits on the number of verifications?
There are currently no limits. The service is entirely free during the development phase, and anyone who integrates SharkEyes now will keep lifetime free access after the full release.
Do I need to register to use the service?
No account or API key is required. You can start using SharkEyes immediately by adding the script to your site. In the future, registration features may appear, but early users will always keep free access once confirmed.
Functional Questions
What verification methods do you use (CAPTCHA, behavioral analysis, etc.)?
SharkEyes doesn’t rely on CAPTCHAs or user interaction tests. It uses behavioral and technical signal analysis — such as request timing, event consistency, and environment checks — to detect bots and automated form abuse silently in the background.
Can I adjust the verification level?
Not yet. For now, SharkEyes automatically balances sensitivity to block bots and prevent over-triggering for real users. In future updates, site owners will be able to choose between different protection levels depending on their needs.
Does your service support automatic integration with websites or apps?
Yes. Integration is fully automatic and takes less than a minute. You only need to add a single <script> line to your page and the data-sharkeyes attribute to your form — no backend or API setup is required.
Can users be verified in real time?
Yes. All verification happens instantly in the browser, right before form submission. The system detects suspicious activity in real time and can silently block or ignore automated attempts without interrupting the user.
Is there an API available for integration with my website or bot?
Yes. SharkEyes uses an internal API that automatically verifies form submissions through the included <script>. You don’t need to write any backend code or use API keys — the system connects and verifies requests automatically. A public API for developers will be added later for custom integrations and analytics.
Is mobile verification supported?
Yes. SharkEyes works seamlessly on both desktop and mobile devices. It automatically adapts to different browsers and screen sizes without any extra setup.
Can suspicious users be blocked automatically?
Yes. When the system detects a bot or form abuse attempt, the submission is automatically blocked before reaching your server. This prevents spam, fake signups, and repeated submissions by both bots and humans.
How does the service respond to detected bot behavior?
When suspicious activity is detected, SharkEyes prevents the form from being sent. The protection is silent and user-friendly — real users won’t notice it, while bots simply fail to submit.
Technical Questions
What technologies are used to detect bots?
SharkEyes combines multiple lightweight signals: browser headers, user agent, IP pattern checks, and interaction timing. These help detect bots, spam tools, and automation scripts without requiring user actions or CAPTCHAs.
How does the system collect user behavior data?
The script listens for safe, non-personal browser events such as typing activity, focus, and general interaction timing. These indicators help the system distinguish between real users and automated submissions.
Are user data stored?
No. SharkEyes doesn’t store any personal or technical data. IP, user-agent, and event data are processed only during verification and are not visible, logged, or saved anywhere.
Can the service be used without storing personal data?
Yes — that’s one of SharkEyes’ main principles. The system works entirely in the browser, processes temporary signals for analysis, and discards them immediately after verification.
What types of bots can the system detect?
SharkEyes can detect form spammers, automation scripts, and browser emulators. It also blocks human-based abuse such as repeated manual submissions or flooding attempts.
Can the service distinguish real users from scripts or automated clicks?
Yes. SharkEyes analyzes timing, focus, and input behavior to tell apart real interaction from scripted or fake clicks, ensuring that only genuine submissions are accepted.
Does the service work with VPNs and proxies?
Yes. SharkEyes works with users connecting via VPNs or proxies. Detection doesn’t depend on location — it’s based on behavior and signal consistency, not IP origin.
Security and Privacy
Is it safe to use this service on my website?
Yes. SharkEyes is designed with privacy and security in mind. It runs entirely on the client side and performs lightweight verification without affecting your site’s performance or user experience. It cannot access or modify your website’s internal data, forms, or databases.
What user data do you collect?
SharkEyes collects only minimal technical information necessary for verification — such as IP address, user agent, HTTP headers, and basic interaction events (like typing or focus). These signals help identify bots and spam behavior while keeping users completely anonymous.
How do you protect collected data?
Collected signals are processed instantly and are never stored, logged, or visible to anyone — not even during verification. SharkEyes doesn’t build user profiles, track individuals, or keep any data after the security check is completed.
Does your service comply with GDPR and other data protection laws?
Yes. SharkEyes fully complies with GDPR and global privacy standards because it doesn’t store or share personal data. All processing happens in real time, in-memory, and no identifiable information leaves the user’s browser.
Is it possible to disable personal data collection completely?
Yes. Since SharkEyes already avoids storing or viewing any personal data, it’s inherently privacy-safe.
Integration and Setup
Which CMS and platforms are supported?
SharkEyes works on any website or platform — WordPress, Wix, Shopify, custom HTML sites, and web apps. Since it’s purely client-side, there’s no dependency on the backend or server framework.
How do I integrate the service with my website?
Integration is simple: add the provided <script> to your page and mark each form you want to protect with the data-sharkeyes attribute. That’s all — no backend code, API keys, or additional setup required.
HoDo I need to install additional libraries or scripts?
No. SharkEyes comes as a single lightweight script that handles all verification automatically. There’s no need to install or maintain any other libraries or tools.
Can I customize the appearance of the verification widget?
SharkEyes doesn’t display visible CAPTCHAs or widgets by default, so there’s nothing to style. The protection works silently in the background. Any future visual options will be fully customizable.
Are webhooks supported for verification events?
Currently, SharkEyes doesn’t offer webhooks or server-side notifications. Verification happens instantly in the browser. Webhook support may be added in the future for advanced monitoring or analytics.
Billing and Pricing
Is there a free plan available?
Yes. SharkEyes is currently completely free for everyone while in beta. Users who start using it now will keep lifetime free access even after the official launch.
How is the service billed (subscription, per verification, package)?
Currently, there is no billing. SharkEyes is entirely free during development, so there’s no subscription, per-verification fee, or package plan at this stage.
Can I pay based on actual usage?
Not applicable yet. All users have free access for unlimited usage during the beta phase.
Do you offer a trial period?
All features are available for free right now, so a separate trial period is not needed.
Can I cancel my subscription at any time?
Since SharkEyes is free and doesn’t require accounts or subscriptions, there’s nothing to cancel. You can simply stop using the service at any time.
Support and Assistance
Where can I contact support if the service isn’t working?
You can contact support through the dedicated /feedback/ page on the SharkEyes website. Users can submit suggestions, report bugs, or provide any other feedback. The page is protected by SharkEyes, so bots and automated scripts are blocked while legitimate submissions are delivered safely.
Is there developer documentation available?
Yes. SharkEyes has a documentation section covering basic integration, common errors, and troubleshooting. The developers section provides ready-to-use optimized solutions, including sample JS and Python files, and instructions on how to fix common issues during setup.
Can I get personal assistance with integration?
Yes. SharkEyes provides guidance through its documentation and developers section, which includes ready-to-use optimized solutions, example JS and Python files, and instructions for fixing common setup errors. You can also submit questions via the /feedback/ page to receive direct support from the team.
How often are the detection algorithms updated?
SharkEyes is actively developed, and detection algorithms are updated regularly in the background to improve bot detection and form abuse prevention. Updates are automatic and require no action from users.
Do you provide tutorials or video guides for setup?
Yes. The documentation includes step-by-step guides, and the developers section provides ready-to-use examples for common integration scenarios. Video guides and tutorials are planned for future updates to make integration even easier.
Additional Questions
Does the service support multiple languages?
SharkEyes doesn’t display visible content or CAPTCHAs by default, so no language setup is needed. The system works silently on all websites regardless of language.
Can the service work offline or only online?
SharkEyes requires an online connection to the verification API, so it only works while the user is connected to the internet.
How does the service adapt to new types of bots?
Detection algorithms are regularly updated to respond to new automated scripts, spam techniques, and abusive behavior, ensuring the service evolves with emerging threats.
Can it be used for user behavior analytics?
No. SharkEyes is designed solely for bot detection and form abuse prevention. It does not store or analyze user behavior for analytics purposes.
Is it possible to export verification results?
Currently, SharkEyes does not provide export functionality for verification results. Verification happens in real time, and no data is stored. (In the future, logging or export options for analytics may be added.)
Does the service support multi-user accounts?
No accounts are required at this stage. Everyone can integrate the script directly without registration or login.
Can I set different verification levels for different pages or apps?
Not yet. SharkEyes currently uses a single, automatic verification system. Future updates may allow per-page or per-form configuration.