Skip to content
SCAM?

Legal document

SCAM? Privacy Policy

Last updated: 19 October 2026

Delete your SCAM? account

Sign in to SCAM?, open your data settings and confirm account deletion with your password. The account page will tell you if you need to end an active subscription first.

Go to account deletion

Cannot sign in? Contact SCAM? support.

1. Data controller

  1. The controller of personal data processed within SCAM? (scam.lifenexa.pl) and its companion mobile app is:

The entity running the LifeNexa app ecosystem (lifenexa.pl). The operator's full registration details (name, address, tax ID) will be added before paid plans are launched.

  1. Contact the operator: the chat on lifenexa.pl. When contacting us about data protection, please include the email address of the account concerned.

2. What data we process

  • Account data — email address, hashed password (never plain text), optionally a name, account creation and email-verification dates, chosen plan.
  • Content submitted for analysis — pasted message text, a link or a screenshot that the User submits to be checked. It may contain third parties' data (e.g. phone numbers, names) — please submit only what is needed for the assessment.
  • Check history — the result of each check (risk level, signals, recommendations), your answers to the "was this helpful" prompt, "I already clicked / shared data" reports, and your personal list of reported numbers and links.
  • Billing data — when payments are switched on: subscription and payment information supplied by the payment processor. We do not store card numbers.
  • Technical data — IP address, browser and request time in server logs and in the abuse-prevention mechanism (login/registration attempt limits, held temporarily in server memory), and a session identifier (cookie).

We do not collect more data than the Service needs to work and we do not sell User data.

  • Creating an account and providing the Service (login, running a check, history, plan) — GDPR Art. 6(1)(b) (performance of a contract).
  • Security, abuse prevention, error diagnostics — GDPR Art. 6(1)(f) (legitimate interest of the controller).
  • Billing and tax/accounting obligations (when payments are switched on) — GDPR Art. 6(1)(b) and (c).
  • Defence against and pursuit of claims — GDPR Art. 6(1)(f).
  • System emails (email verification, password reset) are sent as part of the contract. We do not send newsletters or advertising.

4. Recipients and processors

  • Hosting provider (OVH) — servers in the European Union where the Service runs and data is stored.
  • Rule-based scanning — signed-in checks process submitted text and links on the SCAM? server. The separate offline scanner runs only on the phone without saving history. Results indicate whether AI was used.
  • LifeNexa AI assistant — sending a question forwards its text, screen context and a pseudonymous account identifier to the operator’s LifeNexa AI service. That service may retain the conversation for context. Starting a new conversation does not delete service records; contact the controller for data access or deletion. Do not submit passwords, payment codes or banking credentials. Background notification AI requires separate consent and an available analysis service.
  • External AI providers — the assistant defaults to the operator’s local model. If the operator enables cloud routing in Agent IDE, your question and screen context may be sent to OpenAI or Anthropic to generate an answer. Cloud answers are labelled. Documents, analysis history and images are not automatically attached to the conversation. You choose what to include in your question. Image scanning and notification AI have separate configuration and consent; saving a key does not activate them automatically.
  • Assistant feedback — Helpful / Not helpful records aggregate app ratings without conversation text. Reporting a problem requires separate, initially unchecked consent for one answer. Only then does Core share the encrypted question and answer with the administrator, without an account identifier, for up to 90 days. Text may contain information you entered; avoid sensitive data. Without consent, the text is not reported. Reading aloud is optional and off when opening the screen; it does not use the microphone.
  • Stripe — payments and subscriptions, only when payments are switched on.
  • Email provider (SMTP) — sending system emails, only when configured.

Data may be disclosed to public authorities where the law obliges us to.

5. Transfers outside the EEA

Some providers (e.g. OpenAI, Stripe) may process data outside the European Economic Area. This is done under an adequacy decision, standard contractual clauses approved by the European Commission or another mechanism provided for by the GDPR. You can obtain a copy of the safeguards by contacting the controller.

6. How long we keep data

  • Account data and check history — until the account is deleted. You can delete a single check (with its screenshot) at any time; it is then removed immediately.
  • After account deletion, we remove your data from the system without undue delay. Isolated recovery copies are kept until replaced by a verified newer copy or until restoring the service is no longer necessary. They are not used for the ongoing operation of deleted accounts. When restoring data, we take completed deletion requests into account.
  • Billing data — for the period required by tax and accounting law (usually 5 years from the end of the tax year).
  • Server logs — for as long as needed for security and diagnostics, in line with the server configuration.

Preventing repeated free trials

We retain pseudonymous HMAC hashes of the verified email address and a random installation identifier, together with the technical identifier of the trial-claim owner. These are not anonymous data. We do not collect PESEL numbers, identity documents or hardware identifiers. The initial reservation for an unverified account lasts up to 24 hours; after email verification, it lasts up to 24 months. It may remain after account deletion so that deletion does not restart the trial. The legal basis is the legitimate interest in preventing abuse; you may object or submit a request to the Operator. After expiry, the claim no longer prevents registration and is deleted when that identifier is reused.

Offline allocations contain operation identifiers and expiry dates, without message text. Expired allocations are removed when the user requests new ones or deletes the account. Bank orders contain amount, plan, reference, status and the recorded request for early service. On account deletion they lose the active-profile link; billing retention rules remain applicable.

7. Your rights

Under the GDPR you have the right to:

  • access your data and receive a copy (in the app: Settings → Download my data),
  • rectify your data (Settings → Your account),
  • erase your data — the "right to be forgotten" (Settings → Delete account),
  • restrict processing,
  • data portability (the same JSON export),
  • object to processing based on legitimate interest,
  • lodge a complaint with the Polish data protection authority, the President of the Personal Data Protection Office (uodo.gov.pl).

To exercise a right the app does not handle directly, contact the controller.

8. Automated processing

A result is generated automatically (rule engine, optionally an AI model), is purely informational and produces no legal or similarly significant effects for you. You always decide what to do next. You can re-run a check or rate how useful it was.

9. Cookies

The Service uses only strictly necessary cookies:

  • login session (httpOnly, Secure, valid up to 30 days) — keeps you signed in,
  • trial installation (scam_trial_device, httpOnly, Secure, up to 24 months) — limits repeated trials; the app stores a random identifier in protected storage.
  • language preference (lifenexa_locale, Secure, SameSite=Lax, up to 12 months) — remembers the language you explicitly select from 15 available languages. Your selection is shared across ecosystem subdomains of lifenexa.pl. We do not select a language based on your location.

We use no third-party marketing or analytics cookies, so we show no consent banner. You can delete cookies in your browser settings — you will then be signed out.

10. Security

Among other measures we use: encrypted HTTPS connections, passwords stored as hashes (bcrypt), private storage of screenshots (accessible only to the account owner), login attempt limiting, security headers and regular backups.

11. Children

The Service is not aimed at children. Minors may use it only with a legal guardian's consent.

12. Changes to this policy

We will announce material changes to this Policy in the Service or by email (if email sending is configured). The current version is always available at scam.lifenexa.pl/polityka-prywatnosci.