Privacy Policy

This revision is effective August 27, 2026. Website: neuroslop.net. Service owner: the independent operator of the Neuroslop project; contact: info@neuroslop.net, Telegram **@AITextChecker** (hereinafter "we"). The Neuroslop service checks texts for machine clichés and rewrites them in natural language.

What data we collect

• Email address and password hash: upon registration. The password is stored only as a scrypt hash with a salt and cannot be recovered from the hash.
• Google account data (identifier, email, name): if you sign in via Google.
• Telegram data (identifier, name, username): if you sign in via Telegram.
• Technical device data: browser user-agent, IP address, login time. Needed for the device list in the account and protection against unauthorized access.
• Texts you submit for humanization on the website, through the API, or in the Telegram bot are

transmitted to an AI provider for rewriting. In the Telegram bot, text may also be sent to the provider for optional neural analysis of a checking result. The ordinary deterministic website check runs on our server without sending the text to that provider. We do not use these texts to train our models.

• If you explicitly report a checking result, we retain only an anonymous diagnostic aggregate:

the selected error direction, server score, text-length range, and marker-type identifiers. The checked text, feature vector, matched excerpts, account ID, and Telegram ID are not written to the website feedback log. This signal is ineligible for automatic training or LLM review and is used only for aggregate statistics and manual investigation of systematic drift.

• A website humanization response is kept for up to 24 hours in a separate AES-256-GCM-encrypted

live replay cache. This lets us return a lost HTTP response without charging again. The main billing database keeps only a hashed settlement marker, never the source or rewritten text. The browser keeps a random request identifier and a short text-free fingerprint in `sessionStorage`. The replay database and its separate `0600` key are excluded from deploy/ rollback snapshots and runtime backups; expired rows are removed by a `secure_delete` sweeper.

• In the Telegram bot, the source and generated result may likewise be retained for up to 24 hours

in a separate AES-256-GCM-encrypted outbox solely to resume delivery after a network failure. The outbox and its separate `0600` key are excluded from runtime backups. Its encrypted payload is removed after confirmed delivery, leaving only a short-lived technical tombstone.

• Public API rewrite responses: only when an API client explicitly sends an `Idempotency-Key`, we keep the terminal response encrypted with AES-256-GCM for up to 24 hours so a lost HTTP response can be replayed without another model call or charge. We retain hashes of the API key, request key, and request fingerprint; the raw `Idempotency-Key` is not stored. Without this header no response cache is created.
• Minimal first-party measurement of public pages is collected before an analytics choice and

under “Essential only”: fixed events are immediately summed by UTC day, language, and canonical path. Cookies, IP, user/session/device IDs, fingerprints, user agents, referrers, search queries, and text are not stored, and this table contains no individual visit rows.

• Extended anonymized visit statistics (pages, device, on-site behavior) are processed through

Yandex Metrica and Google Analytics only after consent; see the Cookie Policy.

• First-party content attribution: after a deliberate transition from an article or content

landing page into the editor or toward an API key, we retain only the page path, content type, and locale for 30 days so we can understand which material leads to a check, humanization, or registration. This marker contains no user text, article title, or search query.

Text you submit for an ordinary website check is analyzed on our server in memory and is not stored: only the text length and score remain in the usage log, plus the anonymous diagnostic aggregate described above when you explicitly submit a report. Checked texts are never sent to analytics. Optional neural analysis in the Telegram bot is processed by the AI provider only to answer that request; the text itself is not written to the bot log.

When you move from a content landing page to the editor, the browser temporarily stores the landing-page path, the "check" or "humanize" intent, and the creation time in `sessionStorage`. It is removed when the editor first opens or treated as expired after 30 minutes; it contains no text.

Why we use it

• Account login and its protection (verification codes, device list).
• Accounting for the free daily limit and paid credits.
• Measuring article and landing-page effectiveness without storing checked text.
• Responding to inquiries and account security notifications.

Who we share with

We do not sell to anyone. An AI provider processes text for humanization and optional neural analysis in the Telegram bot under the applicable processing terms. A payment provider processes payment data; we do not store card numbers. Anonymized visit statistics are processed by Yandex Metrica and Google Analytics under their own policies. Upon lawful request by government authorities, data may be disclosed to them.

How long we store

Account and credit balance: as long as the account exists. Usage logs: up to 12 months. Daily identifier-free first-party aggregates: up to 430 days. Encrypted website humanization replay responses: up to 24 hours in the live cache only; that cache is excluded from deploy/rollback snapshots and runtime backups. Opt-in encrypted public API idempotency responses: up to 24 hours in the live cache; that transient table and its separate replay key are excluded from new deploy/rollback snapshots and runtime backups. Deleting the API key removes its live receipts immediately. The encrypted Telegram outbox remains in live storage for no more than 24 hours and is excluded from runtime backups; its payload is removed immediately after confirmed delivery. You can request account deletion by email to the service owner at info@neuroslop.net or via support on Telegram: **@AITextChecker**.

Your rights

You may request a copy of your data, correct it, or delete your account. Write to info@neuroslop.net or Telegram **@AITextChecker**. We respond within 10 business days.

Changes to the policy

The updated version is published on this page. Significant changes will be announced in the service interface.