scanuabot
UA RU EN PL DE
← Zurück zur Startseite
Updated October 28, 2026

Datenschutzerklärung (Privacy Policy)

How scanuabot processes data essential for Telegram notifications and how to contact us regarding privacy questions.

Contents 1. Scope and General Provisions 2. What Data We Process 3. Purpose of Processing 4. Data Recipients 5. Payments 6. Data Retention 7. Website & Local Technologies 8. Bot Messages 9. User & Author Rights 10. Security 11. Users Under 16 12. Amendments and Contacts

1. Scope and General Provisions

This Policy describes data processing practices when using the scanuabot Telegram bot and its associated website. By using the service, the user acknowledges and agrees to this Policy.

scanuabot is an independent technical monitoring service for public listings. It is not an official product, partner, or representative of OLX (including OLX.ua and OLX.pl), Vinted (including vinted.pl, vinted.de, vinted.co.uk, vinted.com), AUTO.RIA, DOM.RIA, LUN, or REM.

Legal Qualification: "The service aggregates public information and contact details published by sellers for general public access on public online platforms to sell goods or real estate. The service does not store confidential personal data and operates strictly as a technical monitoring tool."

2. What Data We Process

To provide its functionality, the service may process:

  • Telegram data: numeric user ID, username, interface language, and profile details provided by Telegram to the bot;
  • Search preferences: selected platform, categories, locations, price ranges, keywords, minus-words (negative keywords), and other supported filters;
  • Public listing data and open seller contacts: the service conducts technical monitoring solely of open public information published by sellers on public marketplaces (OLX, Vinted, AUTO.RIA, DOM.RIA, LUN, REM) for the purpose of selling goods, clothing, vehicles, or real estate. Such data includes item title, description, photos, asking price, location, publication date, and public contact information (phone number, author name, direct contact links) that the seller voluntarily made public for communication regarding their offer. The service does not harvest private, confidential personal data and does not engage in covert surveillance;
  • Operational data: status of active queries, identifiers of discovered and dispatched listings, notification queue state, and technical card statuses;
  • Access metadata: timestamps of usage, language selection, subscription statuses, referral and campaign codes;
  • Payment metadata: transaction ID, amount, status, and timestamp when a user purchases paid features;
  • Minimized website analytics: random visit ID, visited language edition, referrer category, device type, browser/OS family, locale, timezone, estimated viewport size, visit duration, and click events on predetermined interface elements;
  • Technical server logs: timestamp, request type, operation IDs, and error diagnostics required for service reliability and cybersecurity.
The service aggregates exclusively public information and contact details published by sellers in the public domain for sales inquiries. The service does not store confidential personal data, does not request, and never receives credit card numbers, banking credentials, or full account details.

3. Purpose of Processing

Data is processed for:

  • identifying users within Telegram and delivering bot features;
  • saving search filters and delivering matching notifications;
  • providing users with the technical ability to promptly review public listing cards and contact sellers regarding advertised offers;
  • preventing duplicate delivery of identical listing alerts;
  • verifying access entitlements and subscription payment statuses;
  • evaluating website usability and technical performance without behavioral advertising profiling;
  • customer support, bug diagnostics, abuse prevention, and infrastructure reliability.

Public seller contact details are never sold, transferred to commercial advertising networks, utilized for behavioral profiling, or used for promotional communications by the service.

4. Data Recipients

To enable service functionality, select data is processed by external service providers:

  • Telegram — message delivery, bot execution, Telegram Stars payments, and a single minimized administrator summary of website visits;
  • Hosting & cloud infrastructure providers — server hosting, database storage, and networking;
  • Listing platforms (OLX, Vinted, AUTO.RIA, DOM.RIA, LUN, REM) — query processing and routing users to original listing pages or checkout endpoints.

Data may also be disclosed if mandated by applicable law or enforceable governmental request.

5. Payments

Payments are handled by Telegram or external payment processors. scanuabot receives only operational metadata required to link the payment to the user account and activate features: transaction ID, selected billing duration, amount, currency, status, and timestamp.

Payment information handling by payment providers is governed by their respective privacy policies.

6. Data Retention

Data is retained only as long as necessary to maintain active searches, deliver alerts, track access status, provide support, ensure security, and fulfill legal requirements. Technical logs and backups are kept until scheduled rotation.

Public listing data and associated seller contact numbers are processed exclusively for the duration necessary to deliver alerts and prevent duplicates, and are routinely purged or overwritten as source platforms update.

Internal website analytics records are automatically purged within 24 hours. Nginx server access logs (recording IP, clean requested path, and User-Agent) rotate approximately every 14 days. Telegram visit summaries in private admin channels are retained until manual cleanup.

Users may request deletion of their personal operational data via customer support. Requests are handled manually; certain records may be retained longer if required for security, dispute resolution, or legal compliance.

7. Website & Local Technologies

The scanuabot website does not use Google Analytics, advertising tracking pixels, third-party cookies, or cross-site tracking technologies. For single-tab session awareness, lightweight internal analytics is used: a signed ephemeral identifier is stored temporarily in sessionStorage and deleted upon sending summary telemetry or closing the tab.

IP addresses are briefly processed on the server to determine country level geolocation and mitigate abuse. The analytics database and Telegram notifications never receive raw IP addresses, full User-Agent strings, complete referrer URLs with query strings, or user search inputs. Telegram summaries contain only country, pseudonymous daily ID, broad device attributes, referrer category, visited locale, duration, and tracked UI interactions.

Website visits are never linked to a user's Telegram profile upon bot redirection. When Global Privacy Control (GPC) or Do Not Track (DNT) signals are detected, client telemetry is completely disabled.

8. Bot Messages

Text messages and attachments voluntarily sent by users to the bot outside standard menu commands may be forwarded to a private administrator Telegram chat along with the user's Telegram ID and profile details for customer support, moderation, and technical diagnostics.

Do not transmit passwords, payment card numbers, confidential documents, or sensitive data not required for service functionality.

9. User & Listing Author Rights

Subject to applicable law, users may request access to their stored data, rectification, deletion, restriction of processing, data portability, or object to specific processing activities.

To submit a request, contact customer support specifying the relevant Telegram account. Identity verification may be required prior to fulfillment.

Listing Author Rights (Notice & Takedown / Contact Exclusion): Sellers and listing authors whose publicly available contact information appears in service alert feeds have the right at any time to request the exclusion of their listings or contact details from our technical feed. To submit an exclusion request, simply contact support at @scanuasupport. Requests are handled with priority and data is added to our technical exclusion list.

10. Security

We implement reasonable technical and organizational safeguards to protect data: encrypted transport connections (HTTPS/TLS), role-based administrative access controls, regular software maintenance, error logging, and routine backups. No method of electronic transmission or storage is entirely invulnerable.

11. Users Under 16

The service is not directed at individuals under 16 years of age and does not perform automated age verification. If a parent or guardian believes a child has submitted data without proper consent, they may contact support for investigation and data deletion.

12. Amendments and Contacts

This Privacy Policy may be updated to reflect changes in service features or regulatory requirements. The latest version is always published on this page.

Data inquiries, access, or erasure requests

@scanuasupport ↗

Nutzungsbedingungen · @scanuabot

© 2026 scanuabot