SLApp Helpdesk
Legal

Privacy Policy

Last updated 1 November 2026

This page explains what personal data SLApp Helpdesk handles — through this website, the application, and the monitoring agent installed on the computers you manage — who is responsible for it, why it is processed, how long it is kept, and how the people it concerns can exercise their rights.

Who's responsible for the data

SLApp Helpdesk is operated by Significado Lógico, Lda., based in Amora, Portugal. Reach us anytime at info@significado-logico.pt.

Data about your clients. Most of the data in the application is about your clients and their staff — their computers, contacts and end users, tickets, Microsoft 365 data, remote sessions, on-site visits. For that data, you (the IT company using SLApp Helpdesk) are the controller: you decide what is collected and why. Significado Lógico is your processor: we store and process it only on your instructions, under our Data Processing Agreement, which forms part of our Terms of Service.

Data we are responsible for. Significado Lógico is the controller only for: your own account and the accounts of your users (technicians and administrators), billing and payment records for your subscription, this website (slapp-helpdesk.com) and its visitors, and the people who contact us for support.

What we collect

Your account. When you or your technicians sign in, we receive your name and email address from your Microsoft account. Sign-in is handled entirely by Microsoft; we never see or store your password. When your clients' contacts sign in to the client portal, the same name and email are data about your clients (see "Who's responsible for the data" above).

The computers you choose to monitor. The agent you install reports: computer name, operating system, local and public IP addresses, CPU/RAM/disk usage, installed software and their versions, Windows Update status, hardware details, the last logged-in user, uptime, and any alert conditions you've configured us to watch for (e.g. the firewall being off, a disk nearly full). We do not collect the contents of files, browsing history, or keystrokes.

Support activity. Tickets, comments, and any attachments you or your technicians add to them.

Billing and commercial details. For the company holding the subscription: name, tax number, address, and billing contacts — used to manage the license and invoicing. Renewals paid online go through Eupago (Multibanco or MB WAY — the payer's mobile number) or Stripe (card, including recurring payments), which receive the payment details.

Technical logs. Server logs kept for a limited time to diagnose problems and keep the service secure.

Emails the application sends. A copy of every email the application sends or tries to send — recipients, subject and the full text of the message (not its attachments) — is kept in a log so you can see what went out and when.

The following only applies if you use the module in question:

  • Microsoft 365 of your clients. An administrator of the client signs in once to connect it. We then read, every 6 hours, the client's organization, domains, licences, admin roles, Secure Score and, for each user: name, sign-in name and email, job title, department, country, account status, creation and last sign-in dates, licences, admin roles, MFA methods and mailbox usage. Technicians can also reset a password (the temporary password is shown once and never stored), block or unblock a user, sign them out, create a user, change licences and set an out-of-office reply. BitLocker recovery keys are imported and stored encrypted; any of your technicians can reveal one, and each reveal is recorded in the audit log. To connect, SLApp Helpdesk creates its own app registration in the client's Microsoft 365; disconnecting deletes the user list we read and our copy of the app's secret, but the app registration stays in the client's Microsoft 365 until the client's administrator deletes it, and the contacts and BitLocker keys already imported stay in SLApp Helpdesk.
  • On-site visits (Agenda). Planned and actual times, address, contact, notes, travel time and kilometres, and — when the client signs — the signer's name and the signature image. We don't record the technician's location. Each technician can create a personal calendar link (iCal) with their visits from the last 90 days and the next two years: client name, ticket number and subject, address, the contact's name and phone, the other technicians and the visit notes. The link has no password — anyone who has it can read the feed — so the technician can replace or revoke it at any time.
  • Staff changes (onboarding and offboarding). Requests made by a client's contact in the portal or by a technician. For a new person: name, job title, department, start date, desired email, licences, equipment, access and manager. For someone leaving: name, email, last day, what to do with their mailbox, the auto-reply text, the equipment to recover (with serial numbers) and the data to keep. A request opens a ticket and sends the usual new-ticket notifications; each Microsoft 365 or contact step (creating or blocking the account, licences, out-of-office, password, the contact) is then carried out by a technician with a click and a confirmation — none of them runs automatically.
  • Remote session recordings. A technician can record a remote session; recording every session automatically is off by default. The recording is a video of the remote screen as the technician sees it (no sound), stored with us; the person at the computer is shown a "being recorded" notice. Any of your technicians can watch a recording, and each viewing is recorded in the audit log.
  • Chat between technician and computer. Messages and the files sent in them. Only a technician can start a conversation.
  • Network device configurations. A Windows agent on the client's network signs in to the equipment over SSH, with the login saved in the client's credentials vault, and reads its configuration. These files can contain passwords or keys; versions that do are visible only to administrators, and each view or download is recorded in the audit log.
  • Active Directory health. Domain facts, account counts (enabled, disabled, locked, inactive and so on) and the members of the Domain, Enterprise and Schema Admins groups (account name, security identifier (SID), display name, whether enabled), read daily by the agent on the client's domain controllers.
  • Hardware warranty, vulnerabilities, domains, third-party backups and printers. Serial numbers, warranty dates, the client's domain names and their registrar (not the registrant's details), backup job names and results, printer supply levels. These hold little or no personal data.
  • Client addresses. Used to show clients and their locations on a map.
  • Credentials vault. Logins your technicians save for a client or a computer: the password is stored encrypted (AES-256-GCM); the title, username and notes are not.
  • AI assistant. Only if you add your own Anthropic (Claude) API key. What a technician types, the list of computers it looks up (name, client, status, last signed-in user), the output of the commands it runs and, for script generation, the script's text are sent to Anthropic. The assistant can run commands, restart or shut down a computer through the agent; those actions are logged like any other. Conversations are kept so each technician can see their own history.
  • Website analytics. If you place our tracking snippet on a website, each visit to it records the page and its title, the referring page and campaign tags, the browser, operating system, device type, language, screen size and time zone, the visit's duration, a truncated IP address, the full browser user-agent string, a random visitor identifier kept in the visitor's browser (local storage) and a session identifier (session storage). The IP address is never stored in full: for IPv4 the last part is removed, for IPv6 only the first 48 bits are kept. Because the snippet stores an identifier in the visitor's browser, the ePrivacy rules require the visitors' consent: the owner of the website is responsible for obtaining it before the snippet stores or sends anything — the snippet has a consent mode that waits for the website's cookie banner. Visits are deleted automatically after 400 days.
  • Payments. Only if you connect your own Stripe or Eupago account to charge your clients: the amount and description of each payment and, for MB WAY, the payer's mobile number, which is sent to Eupago.

The SLApp Vault browser extension

SLApp Vault is a separate, optional personal password manager — for your own accounts, not anything your organization manages. It's end-to-end encrypted: the encryption key is derived on your own device from a master password you choose, which never reaches our servers and which we never see, store, or could reset for you.

What we do store: an encryption salt, a "verifier" value that lets us confirm your master password is correct without ever learning it, your saved entries in encrypted form (we cannot read their contents — not the passwords, not the usernames, not even the website names or titles), and basic device metadata (a label like "Chrome extension" and when it was last used) so you can see and revoke devices linked to your vault.

You can organize entries into folders and choose to share a folder — with specific colleagues, or with everyone at your company automatically. A shared folder stays encrypted so that we can never read it, but it becomes readable by whoever you (or another member) choose to add; removing someone from a shared folder revokes their access for good, not just from future updates.

If you forget your master password, your vault cannot be recovered — by you, by us, or by anyone. There is no "reset password" option for this vault, by design.

Why we process it

Data we are responsible for (your account, billing, this website, support contacts): to deliver the service you or your organization signed up for (performance of a contract), to keep it secure and working reliably (our legitimate interest), to keep payment records as tax law requires (legal obligation), and — only where you've agreed to it, such as optional notification emails — with your consent, which you can withdraw at any time.

Data about your clients and their staff (the modules listed above): the legal basis is determined by you, as controller. We process this data only on your documented instructions — given through your use and configuration of the application — and only to provide the service, as set out in the Data Processing Agreement.

Sub-processors and other recipients

We don't sell data, and we don't use advertising networks or analytics trackers on the service or on this website.

Hosting. The application runs on our own servers, located in Portugal. Accounts that chose to use their own database keep their data on the database server they designate.

Sub-processors. We have terms in place with each of these providers, which process personal data for us:

  • Microsoft (Microsoft 365, Graph and Entra ID): sign-in, sending the application's emails (through our Microsoft 365 or, if you choose, your own) and — when you connect a client's Microsoft 365 — reading and managing that client's users as described above.
  • Anthropic: the AI assistant, only if you add your own API key; it receives what is described under "AI assistant" above.
  • Stripe and Eupago: payment of your SLApp Helpdesk subscription and, when you connect your own account to charge your clients, those payments; they receive the payment details described above.
  • TeamViewer: the remote access integration, only if you add your own TeamViewer token; we read your TeamViewer devices, groups and policies, and can rename a device, create a group or move a device to a group (computer and group names).

Other recipients. These are not sub-processors; apart from the map tile servers below, they only receive lookups that don't identify anyone:

  • Cloudflare (1.1.1.1) and Google (8.8.8.8) public DNS, and the RDAP/WHOIS services of IANA and the domain registries (such as DNS.PT for .pt): your clients' domain names, for the daily domain and email checks.
  • OpenStreetMap Foundation (Nominatim): client and location addresses, to turn them into map coordinates; and the OpenStreetMap tile servers, which receive the viewer's IP address and browser details when the clients map is shown.
  • Dell, Lenovo and HP, only if you add your own API keys for warranty lookups: the computer's serial number, nothing else.
  • CISA (the US cybersecurity agency): we download its public list of known exploited vulnerabilities every day. Nothing is sent.
  • Your own email server, if you choose to send the application's emails through SMTP: it receives every email we send for you.

Transfers outside the EEA

Some of the providers above handle data outside the European Economic Area. Each transfer is covered as follows:

  • Microsoft, Stripe, Cloudflare and Google: the EU-US Data Privacy Framework, under which they are certified.
  • Anthropic, Dell, Lenovo and HP: the European Commission's standard contractual clauses.
  • OpenStreetMap Foundation is in the United Kingdom, covered by the European Commission's adequacy decision for the UK.
  • TeamViewer (Germany) and Eupago (Portugal) are in the EEA.

If the Data Privacy Framework stops applying, the standard contractual clauses included in those providers' terms apply instead. RDAP/WHOIS lookups send only a domain name and can reach a registry in any country, depending on the domain's ending.

How long we keep it

While your subscription lasts. Some data is deleted automatically after a fixed time:

  • Computer events: 7 days. Performance metrics and agent errors: 30 days.
  • Network log entries: 14 days. Website checks: 90 days. Backup run history: 180 days. Website visits: 400 days.
  • Remote session recordings: 30 days by default (you can choose anything from 1 day to 10 years).
  • Network device configurations: per device, the newest 50 versions plus every version from the last 30 days; the record of each backup run, 90 days.
  • Active Directory checks: a summary of the last 30 per server. Third-party backups: the last 20 runs per job.
  • Microsoft 365 users: replaced on every sync, and deleted when you disconnect the client (the contacts and BitLocker keys imported from it are not).

Everything else — including tickets, on-site visits and signatures, staff change requests, chat messages and files, AI assistant conversations, the credentials vault, the email log, the audit log and BitLocker recovery keys — is kept while your subscription lasts. You can delete it earlier in the application, where the application allows it.

When your subscription ends. When a subscription ends — because it expires, is cancelled, or a one-month trial expires — the account is suspended. 90 days later the account and all its data are deleted automatically. The account's administrators receive email warnings 60 and 83 days after the suspension; renewing before the deletion keeps everything. After the account is deleted, the agents on its computers uninstall themselves.

Exceptions. Payment records are kept for 10 years, as Portuguese tax law requires. Accounts that use their own database: the data on that database server is under the account's own control. Backups of our servers are rotated, and deleted data disappears from them as they are overwritten.

Your rights

Under the GDPR, you can ask for access to, correction, deletion or export of your personal data, and you can object to how it is processed.

For data we are responsible for (your account, billing, this website, support contacts), write to info@significado-logico.pt and we'll respond within the legal timeframe.

If you are a client or end user of an IT company that uses SLApp Helpdesk, that company is responsible for your data: send your request to it. If you write to us, we'll pass your request to that company and help it answer.

If you're not satisfied with the answer, you can lodge a complaint with the Portuguese data protection authority, the CNPD.

Cookies and local storage

This website doesn't use tracking cookies or analytics. The one third-party request it makes is to Google Fonts, to load the typefaces you're reading right now — Google may log that request, but no cookie is set by it. The application itself uses your browser's local storage (not cookies) to keep you signed in and remember preferences like language and light/dark theme — this is required for the service to work and is never shared with anyone.

Changes to this policy

We'll update the date at the top of this page whenever we make a meaningful change, and — for significant changes — let active customers know directly.

Contact

Significado Lógico, Lda. — Amora, Portugal
info@significado-logico.pt

This page is written in plain language to be genuinely useful, not just to cover us legally — but it's a general description of our practices, not a substitute for legal advice about your own specific situation.