Last updated: October 04, 2026
This Privacy Policy explains what information is collected when you use the Personal IT Guy software (the "Software") and its website (the "Site"), where it comes from, why it is collected, to whom it may be disclosed, how long it is kept and what rights you have over it.
It is written in accordance with the Israeli Protection of Privacy Law, 1981, including the Protection of Privacy Law (Amendment No. 13), 2024, and the regulations enacted under it - chiefly the Protection of Privacy (Data Security) Regulations, 2017, and the Protection of Privacy (Transfer of Data to Databases Abroad) Regulations, 2001.
Scope - both systems
- The Software: what is stored on your computer, what it sends to us, and what it sends directly to an outside service.
- The Site: cookies, browser local storage, details submitted through it, and server logs.
This policy covers both. Where the two differ, it says so explicitly.
What is not here, and is better said up front: there is no online sale, no card processing, no marketing mailing list, no paid advertising, no pixels, no analytics tooling and no audience targeting - neither on the Site nor in the Software. The service is not built on collecting information, so the amount of information it collects is deliberately small.
1. Who is responsible for the data
Service operator and owner of the database: Personal IT Guy.
Address: Rishon LeZion, Israel
Email: info@pitguy.com
The contact person for privacy matters is the service operator. Every privacy enquiry is handled by them directly, at the email address above.
1.1 The database's status under Amendment 13
Amendment 13 to the Protection of Privacy Law, which came into force on 14 August 2025, abolished the duty to register most private databases with the Database Registrar and replaced it with internal management and documentation duties. Our database is not one of the kinds that remain registrable: its main purpose is not collecting information in order to pass it to others, it does not belong to a public body, and it does not hold specially sensitive information about a large number of people.
The scale of the activity and of the data also does not require appointing a data protection officer or a data security officer. That said, we keep the internal documentation the law requires, including a database definitions document, and we work to the data security regulations at the security level that applies to us.
2. The guiding principle - your diagnostics stay on your machine
Every check the Software runs - processor, memory, drives, graphics card, battery, network, temperatures, processes, services, installed software, display, audio, camera, microphone, input devices, machine security and the server tools - runs locally on your computer. Its results, the reports, the chat history and the settings are stored on your machine only.
We do not scan your computer remotely, we do not run commands on it remotely, we do not upload files from it, we do not see its contents, and we do not know what you checked, when, or what came out of it. The Software does not transmit results automatically, and it collects no usage data (telemetry) of any kind.
The one exception is remote monitoring (section 4.8) - an option that is off by default, and runs only on a machine where you explicitly switched it on and signed in with a username and password - and only until the monitoring is stopped. On such a machine, and only there, the Software reports the machine's state to our server and carries out a fixed set of actions the administrator asks for. On a machine where remote monitoring was never switched on, everything in the paragraph above holds in full.
3. What is stored on your computer and never reaches us
The Software keeps an encrypted settings file in your user's own data folder. Among other things it holds:
- Your personal API key for the artificial-intelligence service.
- Chat ratings and your conversation history with the assistant.
- The console accounts you saved (SSH, Telnet, ADB), including usernames and passwords.
- The unlock code for the system log - stored as a one-way hash (SHA-256), never as text.
- The registration details you gave in the setup wizard, your preferences, language, text size and window position.
- Reports you produced and stress-test results, as files on your own machine.
Not one item on that list is sent to us or backed up by us. The reports the Software produces never include the settings file - so no API key, no conversation history and no console accounts.
Please note: a report you choose to send to a technician or anyone else does contain your machine's hardware and software details, and who receives it is entirely under your control.
4. What does reach us, and where it comes from
4.1 Registration details
Provided by you in the setup wizard.
A full name and an email address are required to complete the wizard, and the email address serves as your user identifier. Phone number, business name and headcount are optional and may be left blank. The details are stored in our database together with the date you registered.
4.2 Activity marker
Created in the course of use.
If an email address was provided, it is sent to our server each time the Software starts in order to update your last-used date. That is all that is recorded: the email address and the latest timestamp. We do not record what you did in the Software, which screens you visited or which checks you ran.
4.3 Routine requests to our server
Collected automatically.
The Software contacts our server to check whether a new version has been published, to fetch system messages, to read operational settings and to show the legal documents in their current wording. As with any browsing, these requests expose your IP address, the time of the request and its technical details, and they are written to the server log for operations and security.
4.4 The feedback form inside the Software
Provided by you.
If you send feedback from within the Software, what reaches us is the kind of enquiry, the text you wrote, your name and email address if you filled them in, the version number, the operating system, the interface language and the screen the message was sent from - along with a screenshot, if you chose to attach one. The message reaches us as an email and is not stored in the database.
Screenshots: a screenshot may include personal information that happened to be on screen at that moment. Attaching it is your choice, and it is worth checking what is visible in it before sending.
To prevent abuse of the form we keep a send-rate counter identified by a one-way hash of the IP address, which deletes itself after a day.
4.5 Enquiries to us by email
Provided by you.
We keep the enquiry and the contact details in it in order to handle it and to record how it was handled.
4.6 Requests for public information through our server
Created in the course of use.
When the Software checks who owns a domain or an IP address, it asks the authorised registry directly. Only when the network you are connected to blocks that direct request does the query pass through our server, which forwards it to the registry. In that case the query is exposed to our server in passing only and is not stored.
A lookup of your public IP address is answered from tables held on our own server rather than against an outside location service - precisely so that no outside party receives a list of which users were online and when.
4.7 The Site's admin area
For the service operator only.
It holds a username, a password as a one-way hash, the last sign-in time, "remember me" tokens and a failed-login counter keyed by IP address. There are no outside users in this area.
4.8 Remote monitoring (opt-in only)
Sent from the machine, only after it was explicitly switched on.
The Software includes an option, off by default, to report the machine's state to our server so that the administrator can follow it remotely and receive alerts. It is switched on only if you explicitly approved it on the consent screen inside the Software - or, on an agent-only installation, in the window by the clock - and typed a username and password you received from us.
Agent-only installation. The Software can be installed as "agent only". It then runs in the background with no window, for every user who signs in, and shows an icon by the clock. While the computer is connected to monitoring, whoever uses it can hide the icon from the window by the clock, and the window then opens from the Start menu; disconnecting from monitoring brings the icon back. The installation itself does not switch monitoring on: monitoring is switched on only when someone at the computer signs in from the icon with a username and password, after reading in the window what is sent and what the administrator can do - as set out in this section - and confirming that they are authorised to switch monitoring on for the computer and that its users will know it is monitored. From the same window the sync can be paused and resumed at any moment - while it is paused nothing is sent and no actions are carried out, and the monitoring dashboard shows that the user paused it - the computer's name on the dashboard can be changed, sending the location can be switched off (section 4.9), the notices about remote actions can be switched off (see "A notice to whoever sits at the computer" further on in this section), the icon can be hidden, and the computer can be disconnected from monitoring. What is sent and the possible actions are the same as in monitoring switched on from inside the Software, and nothing more is collected. Whoever switches monitoring on for a computer that others use - an employer or an IT service provider, for example - is responsible for being authorised to monitor it, and for its users having been duly informed, including under the law that applies to monitoring in the workplace.
While it is on, the Software checks with the server every few seconds whether the administrator is watching the machine (that check sends no data), and tells the server in a single word when it closes, when the machine goes to sleep or when it shuts down (that word carries no data either).
The routine report is sent every few minutes - and every few seconds while the machine is being watched - and carries: processor load, memory in use, free space on each drive, network rate, time since power-on, the name of the program using the most processor, the processor, graphics card, motherboard and drive temperatures and the graphics card load where they are measured, whether a restart is pending, the notices the Software itself shows in its bell when they change, the Software version, the machine's address on its own network, its time zone and its own time, whether the Software is locked with an entry code, how long it has been since a key or the mouse was last touched at the machine - a length of time and nothing else, which shows whether somebody is sitting at it and never what was typed, in which program, or by whom - and the answers to the actions the administrator asked for, where there are any.
The hardware and software description is sent every 4 hours, and whenever the administrator asks, and carries: the machine's name and the Windows user name, the email address entered in the Software, machine and board model, processor, memory, drives (including serial numbers), graphics card, battery if there is one, the Windows version and which of its features are on, protection state (Defender and the firewall), whether an update is pending, the number of installed programs, the list of installed programs (name, version, publisher, when the program was last opened and how many times, the date on the program's own file, and whether it can be repaired or removed silently from the dashboard) and which of them winget can update, the notices the app itself shows in its bell, the last Computer Doctor score, how the Software is installed on the machine - for every user or for one, and whether the helper service is running, and the hardware (MAC) addresses of the machine's physical network adapters, so that it can be woken remotely (Wake-on-LAN) without a check having been run on it first. When a program was last opened is read from the record Windows itself keeps of programs started from the Start menu, the taskbar or a double click, for the user the Software runs as. What was done inside a program, how long it was open, and which files were opened in it are not collected.
What is never sent: files, browsing history, passwords, document contents or screenshots.
The data is encrypted in transit and stored encrypted on our server, and it is seen by the administrator and, for the machines they connected with them, by whoever received a username and password from us.
AI analysis on the monitoring dashboard. Whoever can see the machine on the monitoring dashboard can press "Explain" or "AI analysis" beside a process, a service, an installed program or an event-log line, or beside the result of a check - the computer doctor, the network check, the heat check, the printers, the system file check, the reliability report or the machine's overall state. Only then, and only the data of that one item or result, is sent from our server to the Google Gemini service to obtain an explanation. Before it is sent, the computer's name, the Windows user name (including inside file paths), the domain name, e-mail addresses, the network's public address, hardware (MAC) addresses, serial numbers, the wireless network's name and location details are removed from it. Nothing is sent to the AI by itself or on a schedule - only on a press. Details in section 6.
A helper service on the machine. When monitoring is switched on with a username and password, or on an agent-only installation, a Windows service named "Personal IT Guy" is installed on the machine as well. It is needed for the things the operating system does not allow without administrator rights - installing updates, reading drive temperatures, updating the Software itself, carrying out the repairs from the Software's fixed list that the administrator asked for (resetting the network settings or restarting a device, for example), and a handful of checks that have no answer without it. Windows asks for administrator approval once, at installation (on an agent-only installation, with the approval already given to the installation itself). The service runs a fixed list of predetermined operations and collects nothing of its own; everything sent from the machine is what this section describes. It is removed when monitoring is stopped or the Software is uninstalled; on an agent-only installation it stays until the Software is uninstalled, so that signing in again does not need another administrator approval.
The actions the administrator can ask for remotely, and these are all of them:
- Ask for a fresh hardware and software inventory, and change the report rate.
- Ask for the installed programs to be updated, all of them or one. The update runs in the background, with no window and at low priority, only when the machine is not busy, touches only programs that install silently, and restarts nothing.
- Read the details of one installed program - what Windows records about it (version, maker, location, size, install date and the uninstall command) and what the winget catalogue knows of it; remove one program silently - only a program whose uninstaller has a silent mode, and never the Software itself - or, for a program installed for the signed-in user that has no silent removal, open its uninstaller on the screen so that whoever sits at the computer confirms the removal themselves; and repair one program - with Windows Installer's own repair, or by installing it again from winget. Removing or repairing a program installed for all users needs administrator rights, which the helper service supplies.
- Install the waiting Windows updates. This needs administrator rights on the machine - the helper service supplies them, and without it the Software has to be running as administrator. The machine is never restarted by itself.
- Update the Software itself to the release on the site. It is installed quietly only while nobody is using the Software, which then opens again by itself.
- Run an internet speed test - the Software moves test data to and from a measurement server for about half a minute, and reports only the speeds, the round-trip time and the kind of link.
- Check the activation state of Windows and its updates - the licence state and kind, the last five characters of the key, the version, the date of the last update and the list of waiting updates are sent.
- Check the machine's network - its internal and public address, the router, the kind of link, the network adapters, and the findings of the network doctor and the slowness check.
- Scan the local network - the address, hardware address, name, maker and kind of every device that answers.
- Send a ping from the machine to an address of their choosing.
- Trace the route (traceroute) from the machine to an address of their choosing, and find the bottleneck along the way.
- Run the computer doctor - the Software's own troubleshooting findings.
- Read a technical sheet of the machine - identity, hardware, drives, and the network adapters with their MAC addresses.
- Check the machine's heat - every temperature the sensors expose (processor, graphics card, drives, board, battery and fans) watched for about twenty seconds. Over those same seconds it also records which programs were loading the processor and how much of it each one took, so the answer can tell heat that comes from heavy work apart from heat that points at a cooling problem.
- Measure the read and write speed of a drive of their choosing - a 256 MB test file is written, read back and deleted.
- Check and repair Windows' system files - Windows' own tool (sfc /scannow) compares every protected system file with the signed copy Windows keeps and replaces a damaged one. The result, the number of components checked, the names of the system files replaced or not repaired, and the tool's output are sent. Your files, programs and settings are not changed.
- Read the last days' failures (a day up to a week, the administrator's pick) from the Windows event log - program crashes, Windows failures, hardware errors, blue screens and unexpected shutdowns, with the explanation the Software gives them.
- Collect the machine's network data - the adapters and their addresses, the router, the wireless network, the DNS servers, the routing table, the proxy, the open connections and their processes, the neighbours on the network and the hosts file.
- Read the machine's network configuration (ipconfig) - the network adapters with their addresses, gateways and DNS servers, and the tool's full output.
- Read the neighbours table of the local network (ARP) - the addresses the machine has talked to and the hardware address each answered with.
- See which programs and services are talking to the network right now - with which addresses, and how much traffic each moves.
- Ask the machine to send a Wake-on-LAN packet to wake another machine of yours on the same network - only the wake packet is sent.
- Restart the machine with a normal restart - half a minute's notice; open programs are asked to close and are never forced - and cancel such a restart before it happens.
- Reset the graphics driver - Windows' own Win+Ctrl+Shift+B combination; the screen flickers for a second and no program closes.
- Read the graphics card's details - the model, its memory, the screen's resolution and colour depth, its load and temperature, and the driver's version and release date.
- See the printers installed on the machine - each one's name, driver, port, state and the jobs waiting in its queue, and the state of the Windows print service; send a test page to a printer; and repair a stuck printer - the print jobs stuck in its queue are cancelled (they will not be printed) and the Windows print service is restarted. How many jobs were cancelled, how many are left and whether the service came back are sent back.
- See the processes running on the machine - name, path, and how much processor and memory each uses - and close a process or restart it, as in Task Manager. System processes themselves are never closed.
- See the Windows services on the machine - name, state, startup type, the account each runs as and its path - and start, stop, restart, pause or resume a service, or change its startup type, as in Windows' own Services window. Services Windows itself needs are never stopped or disabled.
- Set or clear an entry code for the Software on this machine. The code locks the Software and nothing else; the files and the machine itself are not locked.
- Read the Software's own activity log on the machine - what it did, what failed and why - and empty it.
- Empty Windows' Application and System event logs on the machine, once the faults in them have been dealt with. Only the names of the logs, how many records each held and whether it was emptied are sent back. The Security log is not touched.
- Ask the Software for an AI troubleshooting check - of the computer or of the network - from a description the administrator writes, or an investigation of what happened in the last 24 hours. The check runs on the computer itself. If an AI key is set in the Software and you have approved the use of AI in it (section 6), the check uses the Software's own AI and that key, and the administrator's description and the results of the Software's checks are sent from the computer to Google Gemini. Otherwise - as long as you have not switched the AI off in the Software - the check's questions (the administrator's description and the results of the checks) are sent from the computer to our server, and from there to Google Gemini on our key, after the identifying details listed in the paragraph "AI analysis on the monitoring dashboard" above are removed from them. Either way, the explanation that comes back - the problems found, their causes, the steps and the repairs offered - is sent to our server and shown to the administrator. If you have switched the AI off in the Software, the check does not run. The check only reads and changes nothing on the computer.
- Run a repair such a check offered - one at a time, only from a closed list of the Software's own repairs (for example restarting a service or a device, turning back on a device that was switched off in Device Manager, restarting the audio services, unmuting, clearing the name (DNS) cache, returning DNS or proxy settings to their defaults, marking the network private and turning sharing on in it, resetting Windows' network components), and only on the target the Software itself identified in the check. The Software checks after each repair that it worked. The name of the repair, its target and whether it succeeded are sent back.
The administrator cannot run other commands, see the screen or reach files.
A notice to whoever sits at the computer. When the administrator asks for an action from the list above, a notice appears on the computer, by the clock, saying that the technician is working on the computer and which action it is; clicking it opens a window that shows what is running right now, for how long, and what was done before. The notice also has a "Technician's details" button, which shows the administrator's name, company, phone and email as they entered them in their profile on the monitoring dashboard (or Personal IT Guy's contact details, when the computer is monitored by us), as long as the administrator has not switched this off in their monitoring dashboard's settings. The notice is shown as long as the administrator has not switched it off in their monitoring dashboard's settings, and whoever uses the computer can switch it off in the Software's monitoring settings or in the window by the clock. The notice is shown on the computer only and sends no information. Switching the notice off does not release whoever switched monitoring on from their duty to inform the computer's users, as set out in the paragraph "Agent-only installation" above.
Admin log. Every action the administrator asks for from the list above is also recorded in a log kept on the machine itself: what was done, on what, when, how it ended, and the name of the dashboard user who asked for it. The log stays on the machine and is never sent anywhere; it opens from the window by the clock or from the monitoring settings in the Software, only with a code, and holds up to the last 500 actions from the last six months.
You can stop monitoring at any moment from the same screen in the Software; stopping deletes the identification key from the computer and tells the server, and the administrator can also remove the machine from their side. The Software shows exactly what is sent, before consent and after it. On an agent-only installation the computer is disconnected from the window by the clock, where the sync can also be paused for a while; uninstalling the Software from the computer stops the monitoring at once.
4.9 The machine's location (only on machines where remote monitoring was switched on)
Sent from the machine, only while monitoring is on.
So that the administrator can tell where each machine on their list is, the report also carries the place the machine is in: a country, a region and a city, and nothing finer. This clause applies only to machines on which you switched remote monitoring on under section 4.8, and only while it is on; on a machine without remote monitoring no location information is collected or sent at all.
All of it can be switched off. The settings screen inside the Software carries a switch, in the "The machine’s location" row - and on an agent-only installation, the window by the clock - that stops everything in this clause: the position is neither measured nor sent, the Software does not ask Windows for a position at all, and Windows does not contact Microsoft’s location service on this machine’s behalf. The report carries an explicit refusal, so the machine is not given a position by another of your machines on the same network either (see below). The administrator’s screen then shows the internet address alone - the same address every website you visit can see - and nothing else about the report changes. The switch can only be turned back on at the machine itself.
The place is worked out in this order:
- First Windows' location service, if it is switched on and desktop applications are allowed to use it.
- If not, the position another of your machines measured for itself, where that machine is on the same local network and behind the same internet address. In that case the screen names the machine the position came from, and nothing further is collected from any machine.
- If that is not available either, the country set in that machine's own Windows region settings, which is read from the machine itself and needs neither a permission nor an internet connection.
- And if that is unknown too, from the connection's public internet address, as before.
When Windows' location service is the source, the coordinates are sent to our server, matched there to the nearest place name from local tables held on the server, and deleted immediately afterwards - they are not stored, not displayed and not passed to anybody; what is kept is the name of the place only.
A reading whose accuracy is worse than five kilometres is not treated as a position and is not sent at all - a machine with no Wi-Fi and no receiver is given a circle tens of kilometres wide by Windows, which is an answer about a country rather than a location.
Windows' location service is Microsoft's: when it derives a position from the wireless networks around the machine, the operating system itself contacts Microsoft's location service - that is Windows doing its own work, not our Software. You can switch location access off at any moment in the Windows settings, and the place is then worked out by the other means.
The Software's monitoring settings say which of them the current answer came from. That screen also shows the point that was measured and can open it on Google Maps - opening the map is your own request to Google from your own browser, not a request made by the Software.
5. Purposes of use, the basis for processing, and the statutory disclosure
In accordance with the disclosure duty in section 11 of the Protection of Privacy Law we clarify: you are under no legal obligation to give us any information, and providing it is done of your own free will and with your consent. That said, a full name and an email address are needed to complete registration in the Software, and without contact details we cannot identify you, provide personal support or notify you about updates. The information is stored in the service's database, and access to it is limited to the service operator alone.
| Purpose | Basis for processing |
|---|
| Identifying the user and managing the relationship | Your consent at registration, and providing the service you asked for |
| Support, answering enquiries and handling feedback | Providing the service you asked for, at your request |
| Recording a registered user's most recent activity | A legitimate interest in running the service and identifying accounts no longer in use |
| Version updates and operational system messages | Providing the service, and a legitimate interest in keeping it sound and secure |
| Server logs, the failed-login counter and rate limits | A legitimate interest in protecting the system, and a duty under the data security regulations |
| The artificial-intelligence capabilities | Your separate, explicit consent in a dedicated document, using your own personal key |
| Remote monitoring of a machine, alerts, and maintenance actions at the administrator's request | Your separate, explicit consent on the consent screen inside the Software or in the window by the clock on an agent-only installation, and providing the service you asked for |
| Meeting legal duties and legal proceedings | A legal obligation |
We carry out no marketing mailing, no marketing segmentation, no behavioural analysis and no consumer profiling.
6. Artificial intelligence - what is sent, to whom, and when
The AI capabilities work against Google LLC's Google Gemini service, and only after you approve the dedicated "Use of AI" document and enter your own personal API key. Until that document is approved the capabilities stay frozen, and the approval can be withdrawn at any time from the About screen - withdrawal freezes them immediately.
- The key is stored encrypted on your computer and is never sent to us.
- Queries go directly from your computer to Google's servers, not through our servers - except for the case at the end of this list. We do not see, collect or store the content of your conversations.
- Relevant diagnostic data from the machine may be sent alongside your question - the processor model, the amount of memory or a test result, for example - so that the answer is accurate.
- To save repeated queries, the Software produces a numeric representation of your question (an
embedding), also against Google's service, and compares it with earlier questions. This means the text of the question used for that comparison also goes to Google.
- You must use a key with Billing enabled. On the free tier Google may use submitted content to train and improve its models, so a free-tier key must not be used.
- Such use is also subject to Google's terms of service and privacy policy.
- On a computer where remote monitoring is turned on, the administrator can ask the Software for an AI troubleshooting check (section 4.8). If a key is set in the Software and you have approved the use of AI, it is sent the same way - from your computer and on your key. Otherwise - as long as you have not switched the AI off in the Software - it is sent through our server and on our key, as described below under "AI analysis on the remote monitoring dashboard". Either way, the administrator's description and the explanation that came back are sent to our server so they can be shown on the monitoring dashboard, and are kept like the other results of actions.
Warning: do not enter sensitive information into the AI fields - ID numbers, payment-card details, medical information, passwords or trade secrets.
AI analysis on the remote monitoring dashboard. This is a service separate from the Software's own AI, and it works differently:
- It runs from our server and on our key, not from your computer and not on your key. That key has Billing enabled, so Google does not use the content to train its models.
- It is sent only when whoever can see the machine on the dashboard presses "Explain" or "AI analysis", and only the data of the item or result they pressed it for - as described in section 4.8. And also when the administrator asks for an AI troubleshooting check on a computer with no key set (section 4.8): then only the two questions of that one check go through it, and only while the request is open on the dashboard.
- The identifying details listed in section 4.8 are removed before it is sent. The request contains the names of processes, services or programs, lines from the Windows event log and the results of checks, and in a troubleshooting check also the administrator's description - no files, no document contents and no screenshots.
- The answer is kept on our server so that the same question is not asked again. An explanation of a process, a program or an event-log line carries no identifying details, and may therefore also be shown for another machine where the same process, program or line appears. In addition, the last analysis of each kind of check on each machine is kept encrypted, so that the dashboard can show it and it can be printed or exported, until a newer analysis of the same kind replaces it or the machine is removed from monitoring.
- The explanation is written by a model and may be wrong. The dashboard says so beside every answer.
7. Outside services the Software contacts directly from your computer
Some checks cannot be made without reaching outside the machine. In those requests your computer is exposed to the service it contacted, exactly as in ordinary browsing - the request leaves from you and does not pass through us, and we do not see it.
| Service | When, and what for |
|---|
| Google (the Gemini service) | The AI queries, only after your approval and with your own key |
| Cloudflare | The connection speed test and the line-under-load test. Only data packets are sent and received, with no identifying details |
| ipify, ifconfig.me, icanhazip | Public-IP lookup, as a fallback only, if our own server is unreachable at that moment |
| Domain and address registries (RDAP and WHOIS), and IANA's referral table | In ownership checks for a domain or an address |
| DNS servers, routers and devices on your own network | In the network checks, according to what you asked to check |
| GitHub | Only if you explicitly choose to install the optional sensor driver. The file's digital signature is verified before it is run |
| OpenStreetMap | Only if you press the map button. The coordinates are handed to your browser, and no map is embedded in the Software |
| Microsoft (Windows' location service) | Only on a machine where remote monitoring was switched on and Windows' location service is on. That request is made by the operating system itself, not by the Software - see section 4.9 |
| Our own server | Version check, system messages, operational settings, legal documents and downloading the installer |
These requests follow the action you asked for. We receive nothing from them, and we do not know which sites, addresses or devices you contacted.
8. Cookies and local storage on the Site
These are all the cookies the Site sets, and it sets no others:
| Cookie | What for | How long |
|---|
| The session cookie | A secure sign-in to the admin area and the security tokens (CSRF) that protect the forms | Deleted when the browser closes |
PITG_REMEMBER | The admin's "remember me" token. Set only when it was explicitly requested at sign-in | 7 days, renewed on each sign-in |
PITG_MON | The monitoring account's "remember me" token, which keeps you signed in to the monitoring dashboard. Set when you sign in to the account | 30 days, renewed on every visit |
pitg_lang | The interface language you chose. Set only when you actually change the language | A year |
pitg_cookie_ok | A marker that the cookie notice has been shown to you, so it does not reappear on every visit | A year |
The first three are essential to the Site's operation and security and cannot be disabled; the last two hold a preference and nothing more. None of them contains a personal identifier, and none of them follows you across sites.
The devices that remember a sign-in. Beside each monitoring account "remember me" token we keep the time it was issued, the time of the last visit, and two words about the device - the browser's name and the operating system's (for example "Chrome, Windows") - so that your profile can list the devices that remember your sign-in and let you disconnect any one of them. The full string the browser sends about itself is not kept, and no IP address is kept beside it. The token is deleted when you sign out, when the device is disconnected, when the password is changed, and when it expires.
Browser local storage holds the display mode (light/dark) and the accessibility settings you chose. These stay in your browser and are not sent to the server.
The Site has no advertising cookies, no pixels, no traffic analytics, no session recording and no third-party tracking of any kind.
The Site's fonts: the Site loads its Hebrew fonts from Google's font service, so when a page loads, your browser's IP address is exposed to Google's servers. There is no cookie in that, no persistent identifier and no tracking of your browsing - but it is a request to an outside server, and so it is stated here explicitly.
You may block or delete cookies through your browser settings; some Site functionality may be impaired.
9. Disclosure to third parties
We do not sell, rent, trade or transfer your personal information to any third party for any commercial purpose. Information will be disclosed to a third party only where:
- You gave explicit consent.
- A legal duty, a judicial order or a demand from a competent authority applies - and only to the extent required.
- It is needed to defend our legal rights in proceedings.
The hosting and infrastructure provider that hosts our server acts as a data holder on our behalf, is bound to confidentiality and to reasonable security measures under the law, and may not make independent use of the data.
The Google Gemini service receives from us, when AI analysis is asked for on the monitoring dashboard or an AI troubleshooting check is asked for on a computer with no key set, the data described in section 6 - with the identifying details removed - solely to provide the explanation, and subject to Google's terms of service.
10. Transfers outside Israel
Our database, which holds the registration details, is hosted in Israel.
Three transfers outside Israel take place as part of the service. Two leave from your computer or your browser rather than from our database:
- The Software's AI queries, transferred to Google's servers outside Israel, under the separate consent you gave and subject to Google's policies.
- Operational requests to the outside services listed in section 7, including the loading of the Site's fonts.
The third leaves from our server: AI analysis on the remote monitoring dashboard, and an AI troubleshooting check on a computer with no key set, in which the data described in section 6 is sent to Google's servers outside Israel, with the identifying details removed, and only when they are asked for with a press.
These transfers are made in accordance with the Protection of Privacy (Transfer of Data to Databases Abroad) Regulations, 2001, to countries and to bodies subject to a duty of confidentiality and an adequate level of data security.
11. Data security and backups
We apply reasonable and accepted technical and organisational security measures, suited to the security level that applies to the database under the Protection of Privacy (Data Security) Regulations, 2017. Among them:
- An encrypted connection (HTTPS/TLS) for all Site and API traffic.
- Passwords stored only as one-way hashes, which cannot be reversed.
- A strict content security policy in the browser (CSP), CSRF tokens and security headers on every page.
- Protection against SQL injection through prepared statements only.
- Rate limiting and a temporary lock after failed sign-in attempts.
- Direct access to the database file and to the internal folders blocked from the network.
- Permissions kept to the minimum required, on a need-to-know basis.
- The Software's feedback form is cryptographically signed with a timestamp, so a message that did not come from the Software itself is refused.
- The Software's settings file on your computer is stored encrypted.
- Remote monitoring reports are encrypted in transit and stored encrypted on the server, and each machine is identified by a key of its own that is deleted from the machine the moment monitoring is stopped.
- An automatic daily backup of the database, kept in a folder unreachable from the network, and verified.
That said, no online system can be guaranteed absolutely secure. We are not responsible for malicious acts by third parties that could not have been foreseen or prevented by reasonable effort.
12. Retention periods
| Kind of information | Retention period | Reason |
|---|
| Registration details (name, email, phone, business, headcount) | While the account is active, and up to 24 months from the last use | Running the service and providing support |
| The last-used date | Updated on each launch, and deleted together with the registration details | Identifying accounts no longer in use |
| Feedback messages and email enquiries | Up to 24 months after the matter is closed | The record, and repeat handling |
| Screenshots attached to feedback | Deleted together with the message they were attached to | No separate retention needed |
| Server logs | Up to 12 months | Operations and security |
| Remote monitoring reports - full detail | One day | Following the machine's state from moment to moment |
| Remote monitoring reports - hourly summaries | 30 days | Graphs and comparison over time |
| A monitored machine's hardware and software description, including the place it is in (country, region and town) | Replaced by each new report; when monitoring is stopped, all of that machine's data is deleted within 30 days | Identifying the machine and supporting it |
| The feedback send-rate counter | Deleted automatically after 24 hours | Preventing abuse |
| The admin-area failed-login counter | Deleted automatically within 15 minutes | Protection against intrusion attempts |
| The admin's "remember me" tokens | 7 days, and deleted by themselves on expiry | Convenient secure sign-in |
| The monitoring account's "remember me" tokens, and beside them the browser's name, the operating system's name and the time of the last visit | 30 days from that device's last visit, and deleted by themselves on expiry | Convenient sign-in to the dashboard, and telling one device from another in order to disconnect it |
| AI analysis answers on the monitoring dashboard | Up to 30 days, and deleted by themselves | So that the same question is not asked again |
| The last analysis of each kind of check on each machine (the AI report shown on the dashboard) | Until a newer analysis of the same kind replaces it, or until the machine is removed from monitoring | Showing the report on the dashboard, printing it and exporting it |
| Database backups | Up to 30 daily copies; an older one is deleted as a new one takes its place | Recovery after a failure |
| Information subject to a retention duty in law | For as long as the law requires | A legal obligation |
| Information after a deletion request | Deleted within 30 days, except what the law requires us to keep | The data subject's right |
At the end of the period the information is deleted or de-identified.
13. Your rights
Under the Protection of Privacy Law, 1981, and Amendment 13 to it, you have the following rights:
- The right of access (section 13 of the Law) - to review the information held about you in the database.
- The right of correction (section 14 of the Law) - to ask that information which is inaccurate, incomplete, unclear or out of date be corrected.
- The right of deletion - to ask that the information be deleted, subject to retention duties in law.
- The right to know the source of the information - where it was not provided by you directly.
- The right to withdraw consent - including withdrawing approval for the use of artificial intelligence and stopping remote monitoring, at any time and without giving a reason.
- The right to object to direct marketing (section 17f of the Law) - the right is yours at any time, even though we carry out no marketing mailing.
- The right to complain - to the Privacy Protection Authority at the Ministry of Justice.
To exercise any of these rights, email us at info@pitguy.com with "Privacy" in the subject line and details that allow us to identify you. We may ask you to verify your identity before releasing information, so that personal information is never handed to someone it does not belong to.
We will respond within 5 business days, and in any event no later than the period set by law - 30 days.
14. Automated decisions, recommendations and profiling
We carry out no profiling, no user segmentation and no automated decision-making with legal or financial consequences for you.
The Software presents scores, recommendations and explanations - including answers produced by the AI assistant. These are aids only: they rest on measurements from your own machine and on a model that is not always accurate, they do not constitute professional advice, and they change nothing on your computer by themselves. Any action that changes your computer is taken only with your explicit approval, and the decision whether to act on a recommendation is yours.
15. Messages and marketing
System messages are shown inside the Software and concern its operation - a new version, for example, or an operational notice. They are not advertising material.
We will not send you advertising material by email, SMS or any other means without your prior explicit consent. Should we wish to send such mailing in future, we will ask for your consent separately and in advance, every message will carry a simple and immediate way to opt out, and an opt-out will be honoured without your having to give a reason - all in accordance with section 30A of the Communications (Telecommunications and Broadcasting) Law, 1982. Opting out of mailing will not affect essential service messages concerning your use of the Software.
16. Minors
The service is not intended for minors under 18 without the consent of a parent or guardian. We do not knowingly collect information from minors without such consent. If you learn that a minor has given us information, contact us and it will be deleted without delay.
17. Security incidents
In accordance with the Protection of Privacy (Data Security) Regulations, 2017, and Amendment 13 to the Law, in the event of a serious security incident involving personal data:
- We will act immediately to stop the incident, limit the damage and prevent a recurrence.
- We will report to the Privacy Protection Authority with reasonable speed, as the law requires.
- We will inform you of the incident, its extent, the kind of information affected and the steps we recommend you take, where that is required.
- We will document the incident and how it was handled.
18. Changes to this policy
We may update this policy from time to time. The updated wording will be published on this page, with the last-updated date at the top. A material change - broader collection, a new purpose or a new recipient, for example - will be brought to your attention in advance by reasonable means, including a notice inside the Software, and at least 14 days before it takes effect.
The binding wording is the one published on this page at the time of use, and continued use after the effective date constitutes acceptance of it.
19. Contact
For any question, request to exercise a right or privacy complaint, write to us at info@pitguy.com
We would be glad if you came to us first - most requests are settled quickly and with no need for anything further. Alongside that, you are entitled at any time to approach the Privacy Protection Authority at the Ministry of Justice.
