Privacy policy

Information we process

We process account and workspace information supplied by customers, including technician names, business contact details, authentication events, tenant roles, and service preferences. Managed endpoint agents report operational data such as device identity, hardware and software inventory, health measurements, network addresses, logged-in username, alerts, and the results of authorized administrative jobs.

How information is used

• Provide monitoring, inventory, alerting, remote administration, automation, reporting, and support.
• Authenticate users and devices, enforce tenant isolation and permissions, and investigate abuse or security events.
• Operate, troubleshoot, measure, and improve the reliability of the service.
• Meet legal obligations and enforce applicable agreements.

Remote administration

Nizlo is designed for authorized IT administration. Sensitive actions are permission checked and auditable. Remote desktop sessions may be handed to an approved remote-access provider. Nizlo does not intentionally collect Windows passwords, browser passwords, Wi-Fi passwords, or stored user credentials from managed devices.

Service providers and disclosure

We use vetted infrastructure, communications, payment, support-chat, and remote-access providers to deliver the service. When someone uses Nizlo support chat, tawk.to may process browser and page-visit information, IP address, conversation content, attachments, any name or email address the visitor supplies in chat, and chat-session cookies so we can respond and preserve the conversation. Nizlo does not automatically pass account profiles or managed-device records to the chat provider. These providers receive only the information needed for their role and are subject to their own contractual and privacy obligations. We may disclose information when legally required, to protect users or the service, or as part of a business transaction with appropriate safeguards.

Security and retention

We use encrypted transport, tenant authorization, device-specific credentials, access controls, logging, and retention controls appropriate to a privileged IT-management service. No system is perfectly secure. Customers are responsible for protecting technician accounts, configuring permissions, and enrolling only systems they are authorized to manage.

Optional Google Ads measurement

If you allow advertising measurement, we use Google Ads across the public Nizlo journey and the authenticated console solely to measure which ads lead to trial creation and which trials connect a first endpoint. Google may receive advertising cookie and click identifiers, a trial-creation or first-endpoint event with a random event identifier, a synthetic non-console measurement path, and browser and network information such as IP address and user agent. We do not include your signup name, email, phone number, company, password, or internal workspace identifier in these events. This setup does not enable enhanced conversions or personalized advertising.

This measurement is optional and starts only after you opt in through Cookie preferences in the footer. We remember that choice in a first-party cookie for up to six months across nizlo.com and app.nizlo.com. After consent, a separate first-party cookie keeps advertising click identifiers and campaign codes for up to 30 days after the latest consented visit so attribution can survive navigation to signup. When that consented visit creates a trial, Nizlo retains those campaign codes and click identifiers with the signup audit record so we can attribute the trial without storing them in the customer profile. Browser storage keeps a duplicate-event marker until you clear it. Google measurement cookies follow Google's settings. You can decline or withdraw consent through Cookie preferences in the footer. Withdrawal stops future Nizlo trial and first-endpoint conversion events and removes our attribution cookie and accessible first-party Google measurement cookies; it does not erase data already received by Google. See Google's privacy policy for information about Google's processing.

Email campaign measurement

On registered email campaign pages, Nizlo automatically counts page visits and trial-button actions using shared batch and creative labels and a random retry identifier held only in page memory. We do not send URLs, referrers, signup form fields, recipient identifiers, or workspace identifiers in these event payloads. This first-party measurement adds no cookies or persistent browser storage and is separate from optional Google advertising measurement. The counts are not sent to Google or another analytics provider. Our servers still receive normal network information needed to handle requests and protect against abuse.

Retry identifiers expire after 24 hours; daily aggregate counters expire 30 days after their last update. We compare batch totals with successful signup and first endpoint enrollment recorded in existing service audit logs, without extending those logs' retention. Only platform owners can access the aggregate report, which does not include account or endpoint identities. Reloads, scanners, blockers, and new tabs can affect visit and action counts; they do not represent unique recipients.

Your choices

Workspace administrators can update customer and endpoint records, archive endpoints, manage technician access, and configure retention. To request access, correction, export, or deletion, use the authenticated Nizlo service desk. Account deletion instructions are available on the account deletion page.

Children

Nizlo is a business IT-management service and is not directed to children under 13. We do not knowingly solicit personal information from children.

Changes and contact

We may update this policy as the product and legal requirements change. Material updates will be posted here. Privacy questions can be submitted through the Nizlo support page or the authenticated service desk.