Skip to content

📈 Open source, privacy-first web analytics — a cookie-less Google Analytics alternative with built-in error tracking and performance monitoring. Self-host it or use our cloud. Get started for free!

removed obsolete autocaptcha docs (#19)

Andrii Romasiunfa4b30a1c3af
diff --git a/docs/captcha/introduction.md b/docs/captcha/introduction.md
index 4e2261b74..66a2e0cd7 100644
--- a/docs/captcha/introduction.md
+++ b/docs/captcha/introduction.md
@@ -3,11 +3,7 @@ title: Introduction
slug: /captcha/introduction
---
-Swetrix CAPTCHA is a semi-automated, fully open-source and privacy-friendly CAPTCHA service. It is designed to be used on websites and web applications to prevent bots from performing automated actions.
-
-Swetrix CAPTCHA is based on cookies which are used to give users an ability to solve CAPTCHA without an actual challenge. This cookie does not contain any personal information and none of the users identifiable information is stored on our servers.
-
-These cookies are encrypted and only store 2 variables: `automaticallyVerified` and `manuallyVerified` - these are the total number of times the user has automatically or manually solved a CAPTCHA challenge. When user wants to solve a new challenge, this cookie is sent to the server and the server decides whether to show the user a CAPTCHA challenge or not based on the weighted average of these two variables.
+Swetrix CAPTCHA is a fully open source, cookieless and privacy-friendly CAPTCHA service. It is designed to be used on websites and web applications to prevent bots from performing automated actions.
The CAPTCHA challenge is presented to the user in the form of sequence of letters and numbers. The user has to type the letters and numbers in the correct order to solve the challenge.
diff --git a/docs/captcha/server-side-validation.md b/docs/captcha/server-side-validation.md
index 0fe4c4251..2b501a03f 100644
--- a/docs/captcha/server-side-validation.md
+++ b/docs/captcha/server-side-validation.md
@@ -30,14 +30,15 @@ The successful response will have the `success` field set to `true` and the `dat
| --- | --- | --- |
| hash | string | The hash of CAPTCHA user passed. |
| timestamp | number | The timestamp of CAPTCHA user passed. |
-| autoVerified | boolean | Whether the CAPTCHA was auto-verified (i.e. user was NOT presented a CAPTCHA challenge). |
| pid | string | The ID of the CAPTCHA project. |
```json
{
- success: true,
- data: {
- hash, timestamp, autoVerified, pid,
+ "success": true,
+ "data": {
+ "hash": "HASH_12345678",
+ "timestamp": 1111111111,
+ "pid": "PROJECTID123"
}
}
```
diff --git a/docs/captcha/testing.md b/docs/captcha/testing.md
index 426592fc1..e79aaad4a 100644
--- a/docs/captcha/testing.md
+++ b/docs/captcha/testing.md
@@ -8,8 +8,7 @@ You can use the following project IDs for testing.
| Project ID | Description |
|------------|-------------|
-| `AP00000000000` | Always pass captcha without manual verification. |
-| `MP00000000000` | Fail automatic verification, but always pass manual. |
+| `AP00000000000` | Always pass captcha regardless of what was entered in challenge input field. |
| `FAIL000000000` | Always fail captcha. |
## Dummy secret keys