Terms of Use
Effective date: 2026-05-06
Version: 1.1
These Terms govern the use of:
detector404.in;downdetect.in.Operator: OOO “DETEKTIKUM”
Country of registration: Russian Federation
Address: 127045, Moscow, Municipal District Krasnoselsky, Daev Lane, 2, apt. 11, Russian Federation
Email: admin@detector404.com
By using the Site, users agree to these Terms.
1. Description of the Service
Detector404 is an informational service that allows users to report possible outages of online services and view aggregated statistics.
The Site may display:
2. Not an official source
Detector404 is not an official representative of any company, bank, telecom operator, app, government authority or service mentioned on the Site.
Information is based on user reports, statistical processing and algorithms.
Information may be incomplete, inaccurate or outdated.
For official information, users should contact the relevant service or organisation directly.
3. No warranties
The Site is provided “as is” and “as available”.
We do not guarantee:
4. User comments
Comments are public after pre-moderation.
By submitting a comment, the user confirms that:
5. Prohibited content
Users must not publish:
6. Moderation
Comments are subject to pre-moderation.
We may:
We may use automated filters, regular expressions, text analysis, anti-fraud mechanisms and manual moderation.
We are not obliged to publish any comment.
7. Complaints and removal requests
Complaints regarding comments may be sent to: admin@detector404.com
Please include, where possible:
We will review the complaint and take appropriate action if the issue is confirmed.
For detector404.com, this contact also functions as a notice-and-action contact for unlawful content and personal data in user comments.
8. Licence to user content
By submitting a comment or report, the user grants OOO “DETEKTIKUM” a non-exclusive, royalty-free, worldwide licence to use the content for the operation of the Site, including to:
9. Anti-fraud and security
We may use technical measures to prevent:
This may involve:
10. Authentication sessions
If authentication functionality is available, the Site may use a session cookie to maintain authenticated sessions and protect access-controlled areas.
The session cookie is not used for advertising.
11. Geolocation
The Site may use geolocation to determine the region of a possible outage.
This may include:
Users may disable location access in browser or device settings.
12. Analytics
The Site uses analytics tools to understand traffic and improve the interface:
The Site does not use:
Analytics are used in accordance with the Privacy Policy and Cookie Policy.
13. Prohibited use
Users must not:
14. Intellectual property
The Site, software, design, interface, text, graphics, database and brand are owned by OOO “DETEKTIKUM” or used lawfully.
Third-party names and trademarks belong to their respective owners.
Mention of a third-party service does not imply partnership, endorsement or official representation.
15. Third-party links
The Site may contain links to third-party websites.
We do not control third-party websites and are not responsible for their content, availability, security or privacy practices.
16. Limitation of liability
To the maximum extent permitted by applicable law, we are not liable for:
Nothing in these Terms limits rights that cannot be limited under applicable law.
17. Privacy and cookies
Data processing is governed by:
18. Governing law
Unless mandatory laws of the user’s country provide otherwise, these Terms are governed by the laws of the Russian Federation.
For users in South Africa, India, the EEA, UK or other jurisdictions, mandatory consumer protection, data protection, online content and electronic services laws may apply regardless of this clause.
19. Contact
admin@detector404.com
Privacy Policy
Effective date: 2026-05-06
Version: 1.1
This Privacy Policy explains how OOO “DETEKTIKUM” processes data in connection with the use of the following websites:
detector404.in;downdetect.in.Together, these websites are referred to as the “Site”, “Service” or Detector404.
Detector404 is an informational service that allows users to report possible outages, failures or disruptions of online services, analyses such reports, and displays aggregated outage statistics.
This Policy takes into account, where applicable:
DPDP Act;1. Data controller / responsible party
The operator of the Site is:
OOO “DETEKTIKUM” Country of registration: Russian Federation Address: 127045, Moscow, Municipal District Krasnoselsky, Daev Lane, 2, apt. 11, Russian Federation Email: admin@detector404.com
This email may be used for:
For South African users, the operator acts as the responsible party where POPIA applies.
For Indian users, the operator acts as the data fiduciary where the DPDP Act applies.
For EEA/UK users, the operator acts as the controller where GDPR or UK GDPR applies.
2. We do not ask users to provide personal data in comments
The Site does not ask users to provide personal data in comments or outage reports.
We do not ask users to submit:
Such information is not required for the purpose of the Service, which is to detect possible outages and display aggregated statistics.
3. Data we may process
Although we do not ask users to submit personal data directly, we may process technical data, cookies and user comments when the Site is used.
Depending on the jurisdiction and context, some of this data may be considered personal data or personal information.
3.1. Technical data
We may process:
3.2. Anti-fraud tag
The Site uses a cookie named tag.
The tag cookie is used for anti-fraud and abuse prevention purposes. It creates a unique technical tag based on the user’s IP address and helps us:
The tag cookie is not used for advertising or marketing profiling.
Because the tag may be derived from the IP address, it may be treated as personal data or pseudonymous personal data in some jurisdictions.
3.3. Session identifier
The Site may use a cookie named jwt.
The jwt cookie is used as a session identifier for authenticated users if authentication functionality is available.
It may be used to:
The jwt cookie is not used for advertising.
3.4. Geolocation
The Site may use a cookie named geoPos.
The geoPos cookie may store or help process geographic position information based on browser settings or browser permission.
To determine the region of a possible outage, we may use:
Approximate location based on IP address
For example, country, region or city.
Browser-based location
Only if the user grants permission through the browser or operating system, or where the browser/device settings provide location information.
Users may revoke browser geolocation permission at any time in their browser or device settings.
3.5. Comments and outage reports
If a user submits a comment or outage report, we may process:
Comments are subject to pre-moderation and may be published on the Site.
4. Prohibited information in comments
Users must not publish in comments:
If such information is voluntarily provided by a user, we may remove, hide or mask it.
5. Pre-moderation and automatic removal of personal data
Comments are subject to pre-moderation.
To identify and remove information that should not be published, we may use:
We may remove or mask:
If you find a comment containing personal data or unlawful content, please contact: admin@detector404.com
6. Analytics
The Site may use the following analytics tools:
The Site does not use:
Analytics tools are used only to understand traffic, improve the Site, detect technical issues and analyse general usage.
Where required by applicable law, analytics tools are activated only after the user gives consent.
7. Purposes of processing
We process data for the following purposes:
| Purpose | Examples of data |
|---|---|
| Detecting possible outages | comments, selected service, region, time |
| Displaying aggregated statistics | number of reports, trends, aggregated indicators |
| Publishing moderated comments | comment text after pre-moderation |
| Moderating comments | text, technical signals, anti-fraud tag |
| Preventing spam and manipulation | tag, IP, device, browser, frequency of actions |
| Maintaining sessions, if authentication is used | jwt |
| Operating the Site | technical cookies, logs, settings |
| Determining outage region | IP-based location or geoPos |
| Analytics | Google Analytics, Yandex Metrica, Bing/Microsoft analytics |
| Legal compliance | handling requests, complaints and regulatory inquiries |
8. Legal bases for processing
Depending on the applicable law, we may process data on the following legal bases:
Where applicable law requires consent for a specific processing activity, that activity will be performed only after consent is obtained.
For EEA/UK users, non-essential cookies and analytics tools are used only with prior consent.
9. Cookies
The Site uses cookies and similar technologies.
We may use:
tag — anti-fraud cookie;jwt — session identifier for authenticated users, if used;geoPos — geographic position based on browser settings or browser permission;More information is available in the Cookie Policy.
10. Sharing data with third parties
We may share data with the following categories of recipients:
| Recipient | Purpose |
|---|---|
| Hosting providers | technical infrastructure |
| CDN and security providers | protection against attacks and performance |
| Google Analytics | traffic analytics |
| Yandex Metrica | traffic analytics |
| Microsoft/Bing analytics | traffic analytics |
| Technical contractors | support, development and maintenance |
| Public authorities | where required by law |
We do not sell personal data.
We do not use user data for advertising, retargeting or direct marketing.
11. International data transfers
Because the Site uses international technical and analytics services, data may be processed outside the user’s country.
This may involve:
Where international transfers are subject to applicable data protection requirements, we take appropriate contractual, technical and organisational measures.
For EEA/UK users, where required, transfers may rely on adequacy decisions, standard contractual clauses, data processing terms, supplementary measures or other mechanisms permitted by applicable law.
For South African users, transfers are made in accordance with POPIA requirements where applicable.
For Indian users, transfers are made in accordance with applicable Indian law.
12. Retention
We retain data only for as long as necessary for the purposes described in this Policy and as permitted or required by applicable law.
| Category | Retention period |
|---|---|
tag anti-fraud cookie |
1 year |
jwt session cookie |
for the duration of the session or until logout/expiration |
geoPos cookie |
until location settings are changed, the cookie is deleted, or the configured storage period expires |
| Comments | for the period permitted by applicable law or until removed |
| IP and technical logs | for the period permitted by applicable law or as necessary for security |
| Analytics data | according to analytics tool settings and applicable law |
| Aggregated outage statistics | may be retained longer if users cannot be identified |
| Requests and complaints | as long as necessary to process and evidence handling |
Anonymised or aggregated data may be retained longer if it cannot identify a user.
13. User rights
Depending on applicable law, users may have the right to:
Requests should be sent to: admin@detector404.com
We may request additional information to verify the request and prevent unauthorised deletion or modification.
14. India-specific provisions — detector404.in, downdetect.in
For users in India, the processing of digital personal data is subject to applicable Indian data protection laws, including the DPDP Act where applicable.
Users may have rights to:
Grievance and privacy contact: admin@detector404.com
We do not use the Site for advertising or direct marketing.
Cookies and analytics tools are used for site operation, anti-fraud, security and analytics.
15. Security
We implement reasonable technical and organisational measures, including:
16. Children
The Site is not directed to children.
We do not request age and do not knowingly collect children’s data.
If we become aware that a comment contains children’s data, we may remove or mask it.
17. Changes to this Policy
We may update this Policy from time to time.
The current version will be available on the Site with the effective date.
Cookie Policy
Effective date: 2026-05-06
Version: 1.1
This Cookie Policy explains how Detector404 uses cookies and similar technologies on:
detector404.in;downdetect.in.1. What cookies are
Cookies are small files or identifiers stored in a user’s browser or device.
They help us:
2. Categories of cookies
| Category | Description | Status |
|---|---|---|
| Strictly necessary | Site operation and essential technical functions | Always active |
| Anti-fraud | Prevention of spam, bots and statistical manipulation | Always active |
| Session/authentication | Maintaining authenticated sessions, if used | Active when authentication is used |
| Geolocation | Browser-based location or saved location preference | Based on browser permission/settings |
| Analytics | Google Analytics, Yandex Metrica, Bing/Microsoft | Consent-based where required |
| Advertising | Advertising, retargeting and marketing | Not used |
| Session recording / Webvisor | Session replay or screen recording | Not used |
3. First-party cookies
| Cookie | Purpose | Duration |
|---|---|---|
tag |
Anti-fraud technical tag generated based on IP address; used to prevent spam, bots and manipulation | 1 year |
jwt |
Session identifier for authenticated users, if authentication functionality is used | session / until logout or expiration |
geoPos |
Geographic position based on browser settings or browser permission | until changed, deleted or expired according to browser/site settings |
accepted |
Stores the user's cookie preferences and the version of the Cookie Policy accepted or saved by the user | until changed, withdrawn, deleted or expired according to browser/site settings |
4. tag anti-fraud cookie
The tag cookie helps us:
The tag cookie is not used for advertising or marketing profiling.
Because it may be generated based on an IP address, it may be treated as personal data or pseudonymous personal data in some jurisdictions.
5. jwt session cookie
The jwt cookie is used as a session identifier for authenticated users, if authentication functionality is available.
It may be used to:
The jwt cookie is not used for advertising or analytics.
6. geoPos location cookie
The geoPos cookie may store geographic position information based on browser settings or browser permission.
It helps us:
Precise browser geolocation is used only if the user grants permission through the browser or operating system.
Users may revoke location permission in their browser or device settings.
7. accepted cookie preferences cookie
We use the accepted cookie to store information about your cookie choices and the version of the current Cookie Policy.
The accepted cookie may contain information about whether non-essential cookies were accepted or rejected, as well as the version number of the Cookie Policy that was in effect when you gave your consent or saved your preferences.
This cookie is necessary because it allows the Site to remember your choice and avoid showing the cookie banner on every visit. The accepted cookie is not used for advertising, retargeting, marketing profiling or tracking you across third-party websites.
You can change or withdraw your choice in the cookie settings or delete the accepted cookie in your browser settings. In that case, the Site may ask you to make your cookie choice again.
8. Google Analytics
We use Google Analytics only for analytics.
We do not use Google Signals or Google advertising features.
| Cookie | Purpose | Approximate duration |
|---|---|---|
_ga |
distinguishes users | up to 2 years |
_ga_* |
stores session state | up to 2 years |
_gid |
distinguishes users | up to 24 hours |
_gat |
throttles request rate | up to 1 minute |
Google Privacy Policy: https://policies.google.com/privacy
9. Yandex Metrica
We may use Yandex Metrica for traffic analytics and technical performance analysis.
We do not use Yandex Metrica for advertising.
Yandex Webvisor is disabled and is not used on the Site.
| Cookie | Purpose | Approximate duration |
|---|---|---|
_ym_uid |
user identifier | up to 1 year |
_ym_d |
first visit date | up to 1 year |
_ym_isad |
technical analytics parameter | up to 2 days |
Yandex Privacy Policy: https://yandex.com/legal/confidential/
10. Bing / Microsoft analytics
We use Bing/Microsoft analytics only for analytics.
We do not use Microsoft/Bing for advertising or retargeting.
| Cookie | Purpose | Approximate duration |
|---|---|---|
_uetsid |
session identifier | up to 1 day |
_uetvid |
user identifier | up to 13 months |
MUID |
Microsoft identifier | up to 13 months |
Microsoft Privacy Statement: https://privacy.microsoft.com/
11. Cookie banner
The Site may display the following notice:
We use necessary cookies to operate the Site and protect it from spam. With your consent, we also use analytics cookies from Google Analytics, Yandex Metrica and Bing/Microsoft analytics to analyse traffic and improve the Site. We do not use advertising cookies or session recording tools.
Buttons:
For EEA/UK users, non-essential cookies are disabled by default until consent is given.
12. Changing cookie preferences
Users can:
Links:
https://tools.google.com/dlpage/gaoptouthttps://yandex.com/support/metrica/general/opt-out.htmlhttps://account.microsoft.com/privacy/ad-settings13. International processing
Google Analytics, Yandex Metrica and Microsoft/Bing analytics may process data outside the user’s country.
More information is available in the Privacy Policy.
14. Changes
We may update this Cookie Policy.
The current version will be available on the Site.