Skip to content
NexaWaste PRO +NexaWorksClean cities. A better tomorrow.

Two products on a common operating engine

NexaWaste PRONexaWaste PRO connects contracts, addresses, waste streams, bins, schedules, vehicles and collections in one workflow.NexaWorksNexaWorks organizes greenery, cleaning, winter maintenance, roads and lighting works.AppsNexaWaste Operator supports drivers and field teams.All functionsThe workspace brings together the operations dashboard, map, dispatch board, calendar, recycling centre records, resident reports, field tasks and billing.Resident PortalSchedule and notifications without installation.How it worksFull service flow step by step.Download appsSigned Android installers.

Modules for operations, finance and security

Fleet and GPSRecords of vehicles, drivers, shifts and equipment show which resources are available each day.Route planningScheduled pickups go to routes, vehicles and drivers.Containers and RFIDThe bin register links capacity, waste stream, ID and location to the collection point.PSZOKThe selective collection point accepts gross, tare and net weights.BDOPrepare draft waste records, weights and validation results.Billing and paymentsApproved work is included in the billing period, and a receivable is created from the closed period.Analytics and AIExplicit analytical rules now work, such as detecting overdue collections based on due date and status.IntegrationsThe platform distinguishes between working integrations, integrations configurable by an administrator and those requiring a provider.SecurityNot yet accepted for production use

Scope tailored to the role of the organization

Waste collection companiesWaste collection companyMunicipalities and citiesThe municipality publishes collection schedules and accepts resident reports and PSZOK bookings.Municipal utilitiesThe municipal company carries out waste collection, PSZOK and field work in one platform.Property managersThe manager maintains a list of addresses and bins, communicates needs to the contractor and checks that the work has been completed.SubcontractorsA subcontractor with the partner role can see assigned orders and related contracts.

Implementation, questions and documents

GuideWe've gathered tips to help you prepare data, plan your work, and evaluate your results.Implementation and migrationImplementation begins with a pilot on the selected scope.Implementation studiesWe do not publish imaginary customers, reviews or savings.FAQWe collected questions about implementation, applications, services for residents, payments and security.Legal documentsRegulations, privacy and cookies.API documentationOpenAPI pilot version.
PricingContactLog in
Log inBook a presentation
TRANSPARENT RULES OF COOPERATION

Privacy Policy

Who is responsible for the data, for what purposes it is used, how long it is stored and how to exercise your rights.

Version 2026-10-28.1Operator details are awaiting publication
Platform regulationsPrivacy PolicyCookies and storageResident Rules
This document contains the full policy text. The operator’s identification details and processes must be completed and confirmed in the administration panel before commercial use.
In this document1. Data controllers and contact details2. Categories of data3. Purposes and legal bases4. Recipients and international data transfers5. Retention6. Your rights7. Security, analytics and AI8. Updates to this notice

1. Data controllers and contact details

The technical operator of the platform is platform operator indicated after completing the company details, PL. Contact: the website contact form. Service hours: Monday–Friday, 08:00–16:00 (Europe/Warsaw).

For information related to contact, account and platform security, please contact us via the website contact form.

The relevant organization is responsible for data related to municipal services and resident affairs: the organisation responsible for the municipality or service — details must be completed in its profile, contact: the contact channel specified by that organisation. The software provider may process this data upon its documented instructions. Individual roles are based on actual goals and agreements, not just the name of the role in the application.

2. Categories of data

Contact form: name, email, optional phone number and organization, selected product/subject, customer type, form language, message, acknowledgement of the privacy information and separate optional marketing consent. Staff notifications, request confirmations and replies may be sent through the configured email channel; their content and sending status are recorded in the queue. Missing email configuration does not remove a saved request and does not mean that an email was delivered. Account: identifiers, role, organization, credentials and access history. Requests and services: address, schedule, description, status, related task and an optional photo or location supplied by the user.

Settlement includes buyer details, amount, title, payment processor status and invoice document. The platform does not require you to enter full card details in its forms. Technical data includes operation ID, time, infrastructure layer IP address, pseudonymous anti-spam hash, and diagnostic information. Do not provide special category data unless it is necessary and permitted by law.

3. Purposes and legal bases

Contact, pre-contractual steps and performance of a contract: Article 6(1)(b) GDPR. Security, business correspondence and legal claims: legitimate interests under Article 6(1)(f), subject to an assessment of individuals’ rights. Accounting and other legal obligations: Article 6(1)(c). Optional marketing: Article 6(1)(a), with separate consent for the communication channel where required. An organisation’s public tasks may rely on Article 6(1)(c) or (e) and the applicable specific legislation.

The required contact information is required to respond and your account information is required to use private features. Marketing consent is optional, does not affect the handling of the inquiry and may be withdrawn in the future. Photos and location are added at the user's request, in accordance with the system permissions and the processing basis adopted by the organization.

4. Recipients and international data transfers

OVHcloud hosts the infrastructure within the EEA. Other providers depend on the integrations actually enabled and the applicable data processing agreements.

Access is granted to authorized persons of the organization and service providers based on appropriate contracts or legal obligations. Stripe, Przelewy24 and Fakturownia receive the data needed to actually enable the service; their own roles and conditions are shared with the process. Private data is not automatically shared with other organizations.

Optional integrations requiring transfers outside the EEA are not enabled. Before enabling one, the operator must establish the transfer basis and update the privacy information.

Map view can get style and tiles from OpenFreeMap; the provider receives the connection data, including IP. An external navigation or site opens when you consciously select a link and is subject to its operator's policies.

5. Retention

Inquiries without a concluded contract: up to 12 months from the last substantive contact; handling of applications: up to 36 months from closing; current application security logs: up to 90 days; rotational backups: up to 30 days. In the event of a claim, the data may be secured until the case is concluded and the applicable statute of limitations expires.

Accounting records and public-task documentation have separate retention periods determined by legislation, records-management rules, contracts and the relevant data controller's obligations. The shorter contact-form retention period does not automatically apply to these records. The authorised organisation reviews retention needs and erases or anonymises data as appropriate. Setting a period in the panel does not confirm deletion from every backup.

Offline device storage contains encrypted data for the user's own account needed for work. Synchronise unsent changes before clearing application data. Sessions have a limited lifetime; ending a session does not replace the organisation's document-retention procedure.

6. Your rights

You may request access to and a copy of your data, rectification, restriction and, where applicable, erasure or portability, and you may object to processing. You may withdraw consent without affecting the lawfulness of earlier processing. Rights depend on the legal basis and statutory exceptions; erasure does not automatically cover accounting records that must be retained.

Select Personal data and privacy or contact the website contact form. The data controller may securely verify your identity; do not send a document scan unless justified. Requests are normally answered within one month. Any extension and its explanation follow GDPR requirements. Complaints may be submitted to the President of Poland's Personal Data Protection Office at uodo.gov.pl.

7. Security, analytics and AI

HTTPS, role and organization control, admin MFA, change logging, and operation restrictions are used. Passwords are not shared with staff; do not send them in your application. The user protects the device and reports loss of access.

In the current configuration, AI is disabled and rule-based analyzes are not automatic legal decisions. No default transfer of resident data to public models. Incorporating a new service requires establishing the purpose, basis, scope, audience and updating information.

8. Updates to this notice

This policy describes the current features and the published organization profile. If the purpose, providers or scope change, an updated version must be published and the required information provided. A copy of the document, its date and version remain available on the website. Do not enter real personal data into training organizations.

Basic legal information

The document describes how the service works. Relevant responsibilities arise from the organization's regulations and actual processes.

GDPR - text in EUR-LexElectronic Communications Law - ELIPersonal Data Protection Act — official text
NexaWaste PRO +NexaWorksClean cities. A better tomorrow.

Waste management, fleet and municipal services in one, controlled workflow. LifeNexa Enterprise product.

Book a presentation
ProductsNexaWaste PRONexaWorksAppsAll functionsResident PortalHow it worksDownload apps
SolutionsFleet and GPSRoute planningContainers and RFIDPSZOKBDOBilling and paymentsAnalytics and AIIntegrationsSecurity
For whomWaste collection companiesMunicipalities and citiesMunicipal utilitiesProperty managersSubcontractors
KnowledgeGuideImplementation and migrationImplementation studiesFAQLegal documentsAPI documentation
Back to LifeNexaQR code for downloading NexaWaste applicationsMobile applications
Scan to check availability
kontakt@lifenexa.plContact and form →Android — signed APKs →iPhone — distribution availability →
© 2026 LifeNexa · NexaWaste PRO + NexaWorks · version 1.0.0
Return to LifeNexa EnterpriseTerms of servicePrivacyCookiesResident RulesSecurityContact