Privacy Policy

Ce document est publié uniquement en anglais. Le texte anglais est la version qui fait foi et, si tu veux de l'aide pour le comprendre dans ta langue, écris à support@linkraze.com.

1. Introduction

The LinkRaze remote access platform is operated by LinkRaze Technologies Ltd., a private company registered in Israel under company number 517376554 ("LinkRaze", "we", "us", "our", or "Company"). LinkRaze Technologies Ltd. is the data controller responsible for the personal data described in this policy.

This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you use our service, including the web dashboard, the desktop application, and related services (collectively, the "Service"). It also covers people who open a guest link sent by one of our users (see Section 2), who do not need an account.

2. Information We Collect

Account Information: When you register, we collect your email address and a password, which we store only as a hash (see Section 9). If you sign up with Google or another sign-in provider we offer, we receive instead the email address that provider gives us for you and an identifier for your account there; it may also offer us your name and picture, and we do not keep them. You can connect more than one sign-in provider to the same account, and disconnect them, from your account settings. If you use Sign in with Apple, Apple may also tell us when you stop using it with LinkRaze, delete your Apple account, or switch off forwarding to the private address it gave us; we use those notices to disconnect it from your account and to record when mail to that address stopped being delivered. We also keep, encrypted, a token Apple issues each time you sign in with it, and use it for one thing only: to tell Apple to end LinkRaze's access to your Apple sign-in when you delete your LinkRaze account or disconnect Apple from it, so that LinkRaze no longer appears among the apps using your Apple Account. It is deleted with your account, or when Apple is disconnected. We do not ask for your name when you create an account — if you write to us through our contact form, the name you give there is kept with that support request (see Section 4). We also keep any optional profile information you provide.

Device Enrollment Records: Before a computer can be accessed through a LinkRaze account, we may ask the person physically at that computer to confirm it. When we do, we record which version of the confirmation notice was shown, whether it was confirmed or declined, when, and the IP address the answer came from. We keep this because it is the only record of what the person at a computer was actually asked before access to it was granted, and it is what we rely on if that access is later disputed or reported as fraud.

Guest Links: You can give one person at a time temporary access to a computer on your account by sending them a link, which you make at that computer while guest links are turned on there. Before guest links are turned on, we ask the person at the computer to confirm it, and we record which version of that notice was shown, whether it was confirmed or declined, when, the IP address the answer came from, and — where the computer can tell — whether it was typed at that computer's own keyboard or by an accessibility or automation tool. Guest links stay on for up to three hours, and we record when they were turned on, when they were due to turn off, and when and why they did. For each link we record when it was made, when it expires, when and how it was stopped, when it was first and last opened, the IP address it was last opened from, and an identifier of the browser or app that opened it — the link then works there only. We keep only a one-way hash of the link's secret, never the link itself. The person who opens a link also receives a copy of your active touch-control profile: its on-screen controls and touch gestures, but not its name or any of your other settings. A browser keeps it for that tab only and shows it to them read-only: they cannot change it or keep a copy of it. Our Android and iOS apps use only its on-screen controls, for that session only, and keep no copy. While they use the link, they can also see the games installed on that computer, with their pictures but without the games you hid, and start one of them; they cannot hide, add or remove games (see Your Games below).

People Who Open a Guest Link: Someone who opens a guest link does not need a LinkRaze account. While they use it we record the same session information as for any session, including the IP address they connect from. If they open it in a browser, the browser also sends the performance summary described under Diagnostics & Performance below, without the kind of network it is on, that network's speed class or whether the browser kept the screen on; our Android and iOS apps do not send one. Their session is recorded as a session on the account that shared the computer, and the holder of that account is shown when the link was opened and the IP address it was opened from — in our desktop app, in the dashboard's session history and in the account's data export — and, in the data export, what kind of browser or app and device it was opened from (see Session & Activity Data below). If you opened a guest link and want what we recorded about your visit deleted, write to support@linkraze.com.

Device Information: When a computer is added to a LinkRaze account, we record its hostname and a device identifier: on Windows and Linux, the identifier the operating system gives its installation, and on a Mac, the computer's hardware identifier. It stays the same when our software is reinstalled, and on Windows and Linux it changes when the operating system itself is. We use it to recognise a device already on your account, and to stop the same computer being added to a second account without the first one being told.

We also record, as a dated entry on your account, when a computer leaves it: when it is removed from your dashboard, when our software is uninstalled from it, when another account takes it over, when your account is deleted, and when it has not checked in with us for a set number of days — and, if a computer that had stopped checking in starts again, that it came back. Each entry names the computer's record on your account, how it left, when, and which operating system and kind of installation it had. Nothing else is recorded in that entry, and in particular nothing about why; an uninstall our software reports also appears in our audit trail, like other actions on your account (see Session & Activity Data below). When our software is removed from a computer with its uninstaller, with the package manager on Linux or, for the portable version on Windows, with its "Remove LinkRaze data" command, it tells us so itself, once, if it can reach us at that moment. That message names the computer and nothing else. The only other things our software may send on its way out are a renewal of that computer's sign-in, when the sign-in has expired and the message needs it, and a request to sign that computer out of your account — both only when the removal deletes your sign-in from the computer rather than keeping it for a reinstall. If it cannot reach us, nothing is sent, and the computer is recorded as having stopped checking in instead.

We also record what that computer is: the version of its operating system, its processor model and how many logical processors it has, how much memory it has, its graphics adapter and driver, and how many displays are attached to it. Our software reads these once when it starts — and the number of displays again whenever the computer is viewed, because that is the only moment our software can see its screens — and sends them with the routine check-in that tells us the computer is online. The check-in also reports which version of our software the computer runs, whether its automatic updates are on, whether its last update succeeded and, if not, why, which video encoder it uses, and whether someone at the computer has turned remote access off. We keep the most recent answer, and a daily count of how many computers in total are running each operating system version and each graphics vendor. We use them to decide which operating system versions our installers must keep supporting, and which kinds of video encoding our software can offer on a given class of machine — questions we currently answer from guesswork. These details also appear beside the computer on the account pages and lists our staff review (see Section 3). These are the specifications of a computer you added to your own account, recorded against a device record that already identifies it; they tell us nothing about you that the device record did not, and they are never joined to anything anonymous. Whether remote access is off is recorded differently: we keep when it was turned off for as long as it stays off, and use it only to refuse connections to that computer while it is off and to tell you why on your machine list. When it is turned off, the sessions viewing that computer end, and each one's history records that it ended that way.

Session & Activity Data: We log session metadata including: start time, duration, devices involved, IP addresses, session tokens, and session lifecycle events (when a session starts, ends or reconnects, and why it ended). For each session we also record what kind of client opened it — a web browser, one of our viewer apps, or our desktop app on the computer itself — and, as read from that client's request: which browser it was and the browser's major version (for example, Chrome 141), which family of operating system it ran (for example, Android or Windows, without its version), and whether it was a phone or tablet or a computer. Only these categories are kept, never the full user-agent string the client sent, and they are kept with the session log, for as long as Section 4 says the session log is kept. We use them to tell whether a slow or failed session is particular to one kind of device. IP address logging for account and session actions is enabled by default; administrative and infrastructure actions always record the client IP address for security. This data helps us detect unauthorized access, troubleshoot issues, and enforce security policies. We also record, with the session log and for as long as it is kept, whether the browser or app that opened a session reached us through Apple's iCloud Private Relay. We work that out on our own servers from the address of its request, against the list of addresses Apple publishes for that service, even when your address itself is not logged; we keep only the answer. We record it because a session that goes through iCloud Private Relay takes a longer route to the computer, which can explain why it was slower. Each time, we also tell the viewer the answer for its own request. For someone who opened a guest link we tell their viewer the answer and do not keep it.

Direct Connections: To make a session faster, the viewer and the computer being viewed try to reach each other directly, without one of our relay servers in between. To find a way through, they exchange network addresses: the computer receives the public IP address of the browser or app viewing it, and our software on that computer writes it to its logs there; the viewer receives the computer's public IP address and its addresses on its local network. This happens on most sessions, including those opened from a guest link, so someone you send a guest link to receives your computer's addresses this way. A web browser viewing the computer then compares the two public addresses itself and tells us only whether it and the computer appear to be on the same network, never either address; we keep that answer with the connection diagnostics described in Section 4, except for someone who opened a guest link, whose answer we do not keep.

What We Do Not Collect: We do not record what you do inside a remote session. Keystrokes, mouse input, screen contents, clipboard contents, and transferred files are end-to-end encrypted between your browser and your own device — our servers pass them through without the keys to read them, so we cannot reconstruct, replay or hand over your session activity. We log that a session happened, not what happened in it.

Your Games: When you connect to one of your computers, the viewer can show the games installed on it, so that you can start one. To make that list, our software on that computer reads the records that the game stores installed there keep of their games — Steam, Epic Games, Battle.net and the other stores it supports — the pictures those stores keep on that computer (or, where there is none, the game’s own icon), and which of those games is running. If you choose to add a game yourself, it also lists the programs in that computer’s Start menu or applications folders, by name, for you to choose from. The games you hide or add, and when you last started each one from LinkRaze, are kept in a file on that computer. The list, the pictures and those programs’ names travel to the viewer end-to-end encrypted, like your keyboard and mouse input, and reach our servers only if you choose to send them, as the next two paragraphs describe: otherwise we do not know which games are on your computers or which of them you start, and we count nothing about the list. To mark the games that do not work with LinkRaze, and those best played with a controller, the viewer downloads our own list of such games and compares it with yours on your device; the request names only the session it is for, and which of your games matched is never sent to us. Our software on that computer also downloads our rules for finding and starting games — for example a game a store keeps a record of that would otherwise be left out, the code that starts one of a store’s games, or a game no store keeps a record of, found by the name its own installer registered on that computer and its program in the folder that installer names — and applies them to that computer’s own list. It also downloads the pictures we chose for some games — all of them, whichever games that computer has — keeps them in a folder on that computer, and shows each in place of a store’s own picture for its game, but never in place of a picture you set yourself in Steam. The download is the same for everyone and names neither you nor the computer, and which rules matched is never sent to us, except within a list you choose to share as the next paragraph describes. The viewer keeps the pictures in memory while it is open and writes none of them to your device. Our software’s own logs on that computer note which stores it found and how many games each listed, and when a game was started, hidden or added and from which store, but never a game’s name; those logs reach us only as described under Technical Data below. Someone you let in with a guest link sees the same list, without the games you hid, and can start a game from it, but cannot hide, add or remove games (see Guest Links above).

Game Reports: If you report a game to our support from the viewer — one that does not start, or one missing from the list — we receive what the report shows you before you send it, and nothing is sent until you press Send: the game’s name, its store and its id there, how our software starts it (the program and folder, with your user folder written as %USERPROFILE%, or ~ on a Mac or Linux computer) and whether it saw it start; for a missing game, the name you typed and what our software found in that store, by the store’s own ids and folder names; and the versions of our software, of the store’s app where it records one, and of the computer’s system. What you choose under “What happened?” and the words you add go with it. It is kept with your ticket. Only the account that owns the computer can send one; someone you let in with a guest link cannot.

Game List Sharing: If you switch on “Share this PC’s games with LinkRaze” on a computer, it sends us that computer’s list of games — each game’s name, its store and its id there, whether you hid it, for a game you added yourself, its program’s file name and, when that program sits in the folder of a program installed on that computer, the name that installed program has in the computer’s list of installed programs and where the game’s program sits inside that folder, but never the folder itself, and for a game one of our rules listed or started, which rule — with which version of our rules it applied, each store’s count of the games it listed and left out, and, each time a game is started from our software, when it was started and whether our software saw it start. A computer that was sharing before our software sent the installed program’s name keeps sending the file name alone until you switch sharing off and on again. It also sends which of those games was running during each of your remote sessions, and for how long, so we can measure the stream’s quality for each game. We use it to help you when you contact support, where our support staff see that computer’s list on your tickets, and to decide which games to improve streaming for, and which games our software should find or start better — among them the programs people add themselves most often, by file name or by the installed program they belong to — from totals that each cover at least five accounts. We do not use it for marketing or share it with anyone. It never includes a session or a start made through a link you shared with someone else. It is off unless you switch it on, at that computer; you can switch it off there, or for any computer from the dashboard’s Privacy & Data page, which lists every computer that shares. Switching it off, or removing the computer or your account, deletes it; starts and sessions are deleted after 180 days. We record when you switched it on or off and under which version of this policy.

Payment Information: We do not collect or store your full card number or security code — card entry happens entirely within Paddle's payment form and is never visible to us. Payments are processed by Paddle (paddle.com); we receive the notifications Paddle sends us about your transactions and your subscription, and we keep each one as Paddle sent it. They carry the card brand, expiry date and last four digits, and may also carry other billing details you gave Paddle, such as the name on the card.

Fraud Prevention Records: If we determine that an account has been used for remote-access fraud, we record a block against the identifiers that account cannot cheaply replace: the device identifier of a computer involved, an IP address it was used from, and the customer reference our payment provider holds for its card. Each block records the account it was raised over, the reason, who raised it, and — if it is later lifted — when and why. We separately record which computers that account had added, when we warned the person at each of them, and whether that warning was acknowledged. We keep these records because a block that could be cancelled by deleting an account or removing a device would not be a block at all, and because the record of whom we warned is the only evidence that we acted. If the person at a computer reports the account that can reach it, that report is kept with these records too: what they wrote, the IP address it was sent from, the account's email address, the computer's name, and the times of the session it concerns.

Diagnostics & Performance: When you view a device, your browser reports a summary of how that viewing session performed, so that we can tell a session that failed from one that merely felt slow — and so that a change to our software can be judged against how sessions actually behaved before it. That summary covers: which video encoder the device used, and if it fell back to a slower one, why, in the words our software on that device gave; which network path the video took — directly between the two ends, or through one of our relay servers — how much of the time each path carried it and which path the session ended on, and which audio codec was used; how your keyboard, mouse and controller input was sent — through our relay, over the direct connection, or both at once — and, when it stayed on our relay, why; how often and for how long changing between them held it back, and which input features our software on the device supports; counts of the input messages the device received on each path, of those it discarded as copies, refused or could not queue, and of the times a direct connection closed and it released held keys, or found it did not need to (counts only, never what was typed); the graphics adapter and driver of the device being viewed; whether your browser was able to decode the video and audio it was sent, and what its decoder did; for video in our own format, how long your browser took to decode a frame, whether it did so in the background or on the page itself, and how far behind the arriving video its decoding fell; how much of that video was sent at half size, how much of it your browser enlarged itself rather than our decoder, and for how long the device being viewed kept sending half size because every screen viewing it showed the picture small; how often the viewer page was held up by a single task running longer than 50 milliseconds, and for how long in total; how many frames arrived and how many bytes they took; round-trip latency over the session, as a typical and a worst-case figure, both overall and for the moments when your browser was not busy showing video, and both with and without the time the device being viewed spent answering; how long that device spent answering each latency check and how long its answer waited to be sent, the round-trip time its own connection to our relay server showed, and how long it took to encode a frame of video; the round-trip time of the direct connection between the two ends, as your browser's own network software timed it; the kind of network your browser says it is using, such as Wi-Fi, mobile data or a wired connection, and how often that changed during the session; the rough speed class your browser gives that network; your browser's own estimate of how long a round trip on it takes; how many times the picture stopped for longer than a fixed threshold and for how long in total; the video resolution delivered and how often it changed as the encoder adapted to your connection, the size the encoder coded the picture at, the frame rate your viewer asked for, and how many monitors the device being viewed offered; how many times the viewer page was hidden, for example because your screen locked or you switched to another app, and whether your browser kept your screen on while you watched; and how much of the session our software was measuring for. So that the device being viewed can send a smaller picture to a small screen, your viewer tells it how large your screen shows the picture; that size goes only to that device and is not stored.

Apart from the round-trip time of the direct connection, which your browser's own network software measures, the three facts about your network and the two facts about your screen described in the next two paragraphs, these are measurements ABOUT the video stream and how your browser and the device being viewed kept up with it, computed inside your browser after the stream has been decrypted there, or timed by our software on that device and passed to your browser beside the stream — never the stream itself, and never anything "What We Do Not Collect" above excludes. They cannot reconstruct what was on the screen: the size of a frame and the gaps between frames say nothing about what the frame showed. The resolution we record is the one the encoder chose for the connection, which moves with available bandwidth and not with anything you did. We also record which build of the viewer produced these measurements, because how they are defined will change over time and readings taken under different definitions must not be silently mixed.

The kind of network, its speed class and your browser's round-trip estimate are what your browser itself reports about the connection it is on, and we record them so that we can tell a slow network from a slow device. They are a category, a class and a coarse figure that your browser already makes available to the websites you visit: the estimate is worked out by your browser from its recent connections in general, which it rounds and adjusts before any website sees it, and it says nothing about which sites those connections were to. None of them is the name of the network, your provider, your location or an address. Browsers that do not report them send nothing: most desktop browsers do not report the kind of network, and some browsers report none of the three.

How many times the viewer page was hidden, and whether your browser kept your screen on, tell us whether a session that kept reconnecting did so because a phone locked its screen or you switched away, rather than because of the network. When this is turned on for your session, the viewer on a phone or tablet asks your browser to keep the screen on while the session is connected and on screen, and lets it lock again when you pause, leave the page or end the session; we record only whether your browser did so, declined, or cannot. Neither says what you switched to or anything you did there.

Alongside each summary, our servers record four facts of their own, which your browser's report cannot set: which of our relay servers the session was assigned to; the country your connection is attributed to; the country the connection of the device you viewed is attributed to; and whether you viewed from a phone or a computer, as read from your browser's request. The two countries are derived on our own servers, as described in Section 3 — yours from the address the summary was sent from, the device's from the address its own connection to our service already records — and only the country is kept with the summary, never either address. We record them so that a slow session can be traced to what made it slow: a relay, a route between two countries, or a kind of device.

Product Usage Events: When you are signed in, we record which steps of the first-machine setup you reached: that the setup screen was shown, that you pressed Download, whether the download succeeded or failed, whether a device appeared while you waited, and — if you left before finishing — which of the three steps you left on. We also record that you started connecting to one of your computers, and that you opened the link in the email we send so that a setup can be finished on the computer it is for: the one sent after a signup on a phone or tablet, or when you ask for it on the setup screen. Each of these is one entry from a fixed list of eight, recorded against your account with the time, and carrying at most one short extra word chosen from a fixed list of its own: which operating system the step concerned, or why a download failed, or which step you stopped at, or whether that connection was to our web viewer or one of our apps, or whether that link was opened on a phone or tablet or on a computer. There is no free text and no attached payload, so nothing else can travel in one of these entries.

We collect these because the stretch between creating an account and adding a first device is otherwise invisible to us: we can see that an account has no device on it, and not why. We use them to find and fix the places where setup goes wrong, and for nothing else — they are first-party, they are never shared with or sold to anyone, they are never used for advertising or to build a profile of you, and no third-party analytics service is involved at any point. They record your progress through our own setup screen, never anything you do inside a remote session (see "What We Do Not Collect" above). Collection can be switched off for the whole Service by an administrator at any time, without a software update.

Help Assistant Conversations: The help on our website can include a chat, "Ask a question", in which an AI assistant answers what you type. The same chat can also be offered in our web dashboard, under "Help", and in our web viewer, in its "Help" tab. It is offered only while we are running the assistant, and using it is up to you. If you use it, we keep what you type and the answers you are given; whether you asked on the website, in the dashboard or in the viewer; the language and address of the page you asked from (in the dashboard, which of its screens you were on), and which topics of the website's button-driven help you had opened before asking; when each message was sent; which AI model wrote each answer, how long it took and how long it was; whether you rated an answer as helpful or not; and a keyed hash of your IP address, never the address itself, so that we can recognise one address behind many conversations and limit abuse. Like every request to our servers, the chat's requests are also recorded in our web server logs with the IP address they came from, but not with the conversation's identifier; those logs are kept for 14 days (see Section 4). None of this is linked to an account: what ties a conversation to you is a random identifier that only your browser holds (see Section 5). The assistant cannot see or change anyone's account, so please do not type passwords, codes or other account details into it.

If you choose "Talk to a person" in the chat on our website, we copy the conversation, with the page and help topics above, into a support ticket together with the email address you give us and, if you give it, your name, and our support team replies to you by email. From then on it is an ordinary support request (see Section 4). In the dashboard and the viewer, "Talk to a person" only lists the ways to reach us, and nothing is copied or sent.

Staff Notes: Our staff may keep a short note on your account, for example what you told us in an email or a support request, or what we said we would follow up, so that whoever helps you next knows. Notes are seen only by our staff and are never shared or used for advertising.

Controller Profiles and Tutorial Progress: The touch and controller settings you save in our web viewer or in the dashboard’s controls editor — on-screen controls, touch gestures, special-key bindings, controller mapping, and connection settings such as volume, cursor size and pointer lock — are kept with your account as named profiles, up to ten, so that they are the same in any browser you sign in from. If you answer the dashboard’s first-run questions (below) with touch controls, the starter layout you kept, with any controls you moved where you left them, goes into your profiles and becomes the one in use: as your first profile if you have none, into your current profile if it has no controls yet, and otherwise as a new profile named after your game, or under our default name if you typed your game’s name yourself. If you already have ten profiles, it is not added. Our web viewer holds them in the page while it is open and keeps no copy in your browser afterwards. Our Android and iOS apps keep the on-screen controls you arrange in them on that phone or tablet. For each of our web viewer’s tutorials — the getting-started tour on a touch screen and with a mouse, the edit-mode tour, and a one-time hint on the handle at the left edge — we also keep with your account how many times it started, whether it was finished and when that last changed, so that a tutorial you finished in one browser is not shown to you again in another. Whether you have answered or skipped the dashboard’s first-run questions is kept the same way, so that they are asked once per account rather than once per browser. Our support staff can reset either, and each reset is recorded on your account: resetting your profiles deletes them and gives you a fresh default one, and resetting your tutorial progress shows the web viewer’s tutorials again and has the dashboard ask its first-run questions again.

First-Run Questions: When you open the dashboard on a phone or tablet after accepting our Terms, while your account has no computer on it, the dashboard asks a few questions until you answer or skip them: whether you will use LinkRaze to play games or to reach a desktop; for games, which game you play most, whether you will play from a computer or from a phone or tablet, and, on a phone or tablet, with which controls (from a computer, we record a mouse and keyboard without asking); and for a desktop, from which kind of device. If you choose touch controls, it shows you the touch layout you would start with, which you can try and rearrange. We keep your answers with your account: each choice you made, the game you picked from our list or, if your game is not on it, the name you typed, whether you kept the starter touch layout and whether you moved any of its controls, and when you answered. If you skip, we keep the answers you had given and the question you stopped at. If you pick a game whose anti-cheat software stops our software from working, we tell you so and keep which game it was. On a computer, they are asked only where we have switched that on, and an administrator can switch them off for phones and tablets, for computers, or for both.

We use these answers to choose which games we test and add to our list, to word the dashboard’s setup steps for what you said you will do, to set up your first touch layout, and, if you will reach a desktop from a phone or tablet, to start our web viewer there in its productivity mode, made for working on a desktop, rather than its gaming mode, in a browser that has not been set to either. Our staff see the answers added up — how many people gave each answer and picked each game, and the names typed for games not on our list. Our support staff can also see your own answers on your account's page in our internal tools, alongside your controller profiles and tutorial progress, so that they can help you set up and answer your support requests with what you told us in mind; a game name you typed is shown there only until it is deleted, as Section 4 describes. Nothing about your account is decided on the strength of what they see. The answers are first-party, never shared with or sold to anyone, and never used for advertising. They are not one of the Product Usage Events described above, and are not recorded as one.

Community Profiles: Our dashboard has a shared library of on-screen control layouts for games. If you publish one, it is public to other signed-in users: the name and description you give it, the layout itself, and the public name on your account, which you choose. Other people can install it, rate it, comment on it, or report it to us, and you can do the same with theirs; a comment carries the public name of whoever left it, and a rating is shown to others only as part of an average. None of this is needed to use the Service — an account that never opens the library publishes nothing and appears nowhere in it.

Why You Left: When you delete your account yourself, the screen that confirms the deletion asks one optional question — why you left — with a list of reasons and, if you choose "Other", a box to say more. You can also tick a box to let us email you to ask about your answer, which sends us the address you give. Your answer is not linked to your account, which no longer exists; what we keep, and for how long, is in Section 4.

Technical Data: Which kind of browser and device an account was created from (see Section 3), the site you came from on our marketing site (see Section 5), and error logs, to improve service reliability. Our web servers also log each request made to our website, dashboard and API — the IP address it came from, the address it asked for, the page that linked to it and the browser's user-agent — to keep the Service running and investigate abuse; those logs are kept for 14 days (see Section 4). The requests that record our marketing site's analytics, our counted links, and the requests that only report a step of signing up are not logged there at all (see Section 5). If you tick “Attach diagnostic logs” when you contact support from our desktop app, or report a game or open a ticket from the viewer, we also receive the recent logs of our software on that computer — which include the network addresses it used to connect — and, from the viewer, your browser's user-agent, language and screen size and its recent console output, so that we can diagnose the problem you reported.

Cookies: We use session cookies (httpOnly, Secure, SameSite=Strict) to maintain your authenticated state. See our Cookie Policy below.

3. How We Use Your Information

We use collected data to:

• Provide and maintain the Service
• Process transactions and send transaction confirmations
• Send security alerts to the address on the account: a change to your password that you make, a change to your second factor, a new set of recovery codes generated, a recovery code used, a second factor reset or bypassed by our staff, your account signed out of every browser and viewer app by our staff (the LinkRaze app on your computers stays signed in), a sign-in provider such as Google or Apple connected to or disconnected from your account, and — if you sign in with a provider that confirms an address somebody registered here but never confirmed — the password and second factor that had been set on that account removed. Separately, we tell you when a copy of our Viewer app is authorized to sign in to your account, and when a computer already on your account is added to a different one. These are sent even if you have opted out of our other messages — an opt-out is about the mail you want, not about being told somebody took over your account
• Show the holder of an account when a guest link they sent was opened, whether someone is connected through it, and the IP address it was opened from, and let them stop it, or turn guest links off, at any time
• Detect, investigate, and prevent fraud and unauthorized access
• Score accounts against fraud indicators drawn from the records described above — how quickly devices are being added, removed or moved between accounts, how often the person at a device declines or withdraws access or reports the account, and whether one address or one computer appears across several accounts — to produce a queue for a member of staff to review. No account is suspended, restricted, or refused on the strength of that score alone.
• Limit how many devices an account may add, and hold an account's first connection to a newly added device for a short period, where we have those limits switched on. They are aimed at accounts that have not established a payment relationship with us; neither is on by default, and we may turn either on if abuse makes it necessary
• Refuse access to the devices, addresses, and payment instruments recorded under Fraud Prevention Records above
• Refuse connections from countries we have chosen not to serve, or serve only countries we have chosen — the country is derived from your IP address using an IP-to-country database that we download and query on our own servers, so your address is never sent to that database's publisher. It tells us which country an address range is attributed to, which is coarse by design: it is not a precise location, and it does not identify you. For an address that Apple publishes as one of its iCloud Private Relay exits, we use the country Apple publishes for it instead, from Apple's list, which we download and query the same way
• Show which country an IP address is attributed to, on the internal screens our staff use — to investigate a support request, a security alert, or a report of abuse, to review how accounts are getting on (see below), to count how many of our marketing site's visitors came from each country, and to find which countries, and which routes between them, make viewing sessions slow (see Diagnostics & Performance in Section 2). The country is derived the same way as in the bullet above: locally, on our own servers, from an address we have already logged — or, for the visitor counts, from the visitor's address at the moment the page view is recorded, which is discarded in the same step and never stored; and for a viewing session's performance summary, from the address the summary was sent from, which is not stored with it. It is shown only to our staff, and nothing is refused, restricted, or scored on the strength of it
• Warn the person at a computer, in a message shown on that computer, when an account that had access to it has been suspended for fraud — and tell a suspended account that its access has been suspended
• Send you occasional messages about your own account's setup — for example, that your account has no device on it yet, or that a device you added has not connected — each one sent at most once, describing a single next step. These are messages about the Service you signed up for, not advertising: they promote nothing and there is nothing to buy. Every one of them carries a one-click unsubscribe link, and opting out never affects your access to the Service or the mail your account needs, such as sign-in codes, password resets and security alerts
• Tell you, once, when an account has not been used for a long time — that it is still there, that keeping it costs you nothing, and how to delete it if you would rather not. We do not delete an unused account on your behalf, except one that was never set up, as the next point describes. This notice carries the same unsubscribe link and the same promise about your access
• Delete an account that was never set up — one with no computer on it, nothing waiting to be confirmed, nothing ever streamed and no subscription, past or present — once nobody has signed in to it for 90 days. Opening the dashboard while signed in counts as signing in. We email the account's address 14 days before, with the date, and signing in before then keeps the account. That email is about your account, so it is sent even if you have opted out of the messages above. If mail to the address has bounced, or we do not send mail to its domain, the account is deleted on the same schedule without the email. An account whose email address was never confirmed is deleted 30 days after it was created, without an email, because nobody has shown that the address belongs to the person who registered. Such a deletion is the same as one you ask for: what is held against the account is deleted at once, as Section 4 describes, and we keep a record that an account was deleted this way, with its approximate age and how far its setup got, but nothing that identifies it
• Understand why people delete their accounts, from the optional question we ask after a deletion and the other facts described in Section 4. If you let us email you about your answer, a member of our staff may write to you once, personally, to ask about it; the address is never added to a mailing list or used for anything else
• Review how accounts are getting on, so that we can write personally to the people behind accounts whose setup is stuck, whose sessions are failing, or that have stopped using the Service, to ask what went wrong or to offer help. For this our staff see lists of accounts, drawn from the records described in Section 2, that show how far each account has got and when: whether its email address is verified, our Terms accepted and multi-factor authentication set up, whether our software has been downloaded and a computer added, whether the person at that computer confirmed it, declined it, has not answered yet or later withdrew its access, and whether it has been viewed; when the account last signed in and was last used in our dashboard, and whether our apps have been signed in to it; how and when it was created — with a password or through a sign-in provider, from a phone or a computer and in which browser (as read from the request that created it), and, if it was invited, by whom — and the language chosen for it; what the computers on it are called, what platform they run and the hardware and operating system described in Section 2, whether our software is installed on them or run as a portable copy, which version of it they run, whether its last update failed, and whether they are still checking in; how often and for how long its computers were viewed and how those sessions went — whether they produced a picture, whether the picture stopped, how slow they were, whether the video fell back to a slower encoder and why, which network path it took, and how the sessions ended (see Diagnostics & Performance in Section 2); which of our account messages it has already been sent, whether its address has opted out or mail to it has failed, and how many support requests it has made and whether any are still open; whether we have exchanged email with its address, how often and when, read from our own mailboxes and its support requests; any note our staff have written on it; and which country its most recent connections came from, and which country each of its computers connects from, derived the same way as in the country bullets above. The lists also show which channel brought an account, where Section 5 says one is recorded, so that we can see which channels bring the accounts that get stuck; we do not choose whom to write to by it. The messages themselves are written by a member of our staff and sent from one of our linkraze.com addresses: our support address, or the writer's own. They promote nothing and there is nothing to buy, and they are never sent to an address that has asked us to stop our account messages, whose mail has permanently failed, or that has reported one of our messages as unwanted. To stop them, reply and say so: we record that on the same list as the unsubscribe link in our other account messages, so it stops those as well, and it never affects your access to the Service or the mail your account needs. The lists are worked out each time a member of our staff opens one, and are never stored or offered as a download; they are seen only by our staff, they are never shared or used for advertising, and nothing about your account is refused, restricted or scored on the strength of them
• Record whether you asked, when you signed up, to hear from us about new features. We collect that answer so that it exists if we ever have something to offer; nothing in the Service currently sends anything on the strength of it, and the messages described in the three bullets above are not sent on the strength of it either — it does not appear on the lists our staff review for the last of them
• Understand where setting up a first device goes wrong, from the Product Usage Events described above — how many people reached the setup screen, tried the download, were failed by it, and at which step those who did not finish stopped. This is measurement of our own setup screen so that we can repair it; it is never used for advertising, never shared, and nothing about your account is decided on the strength of it
• Answer a game report you send us, and, for a computer whose game list you share, help you when you contact support and choose which games to improve streaming for, from totals that each cover at least five accounts (see Section 2)
• Choose which games we test and add to the list our dashboard offers, from how many people picked each game in the first-run questions and the names typed for games not on it, and learn how many people come for a remote desktop rather than for games, from the answers described in Section 2. The same answers word the dashboard’s setup steps, set up your first touch layout and, for a remote desktop, choose the mode our web viewer starts in on a phone or tablet; our support staff can also see your own answers, to help you set up and to answer your support requests; beyond that, nothing about your account is decided on the strength of them, and they are never used for advertising or shared
• Count how many installations of our software stop being used, and by which route — uninstalled, removed, taken over by another account, lost with a deleted account, or silent — so that we can tell a computer that is switched off from one that has left, and stop describing an account whose computers have all left as merely inactive. An account in that position is not sent the message about unused accounts described above
• Answer the questions you type into the help assistant on our website (see Section 2), and — if you ask for a person — turn that conversation into a support ticket our team answers by email
• Have our staff read stored help assistant conversations, and the ratings given to answers, to find answers that were wrong or unhelpful and correct the help and the assistant's instructions, and to investigate misuse of the assistant. The conversations are never used for advertising or shared with anyone
• Improve service performance and reliability
• Comply with legal obligations (law enforcement requests, court orders)
• Enforce our Terms of Service and other agreements

4. Data Retention

Account data is retained for the duration of your account. An account that was never set up is deleted after a period without a sign-in, as Section 3 describes. When an account is deleted — by you, or by us — what is held against it is deleted at once, except the records below, each kept for the period it states. An account we suspend for breaking our Terms is not deleted: it is kept, disabled, so that the suspension holds, until you ask us to delete it or we do.

The exceptions:

• Session logs are retained for 90 days, then deleted (security and compliance). The usage they are counted into is a record of your own account — how much data moved, per computer and per hour — which is kept for 400 days and then collapsed into monthly totals for each account, kept for 7 years so that usage can still be reconciled against a bill. All of it is deleted with your account
• Audit trail entries (account and security actions, including each action our staff take on your account) are retained for 180 days (security and compliance)
• Guest links, and the record of each time guest links were turned on (see Section 2), are deleted 90 days after they were due to end, and with your account or the computer they were made for. The sessions opened through them are session logs, kept as above, and the confirmation that turned guest links on is an audit trail entry
• Our web servers' logs (see Section 2) are kept for 14 days, then deleted
• Marketing site analytics events (see Section 5) are retained in raw form for 180 days, then deleted. The daily counts derived from them are kept indefinitely for trend reporting, and those counts are broken down rather than site-wide: for each day we keep the number of page views, signups, CTA clicks and distinct visitors, and — both for each country a visit was attributed to and for each channel or campaign that brought it (see Section 5) — the number of page views, CTA clicks and distinct visitors. These are counts and nothing else — no identifier, no address, not even a hashed one, and nothing that can be traced back to a visitor or an account — but the breakdown outlives the events it was derived from, so the fact that a visit was attributed to a particular country or channel on a particular day remains in a daily total after the event recording that visit has been deleted
• The daily counts of what the computers on our service are — how many run each operating system version and each graphics vendor, and how many have not reported yet — are kept indefinitely, for the same reason the totals above are: they are what let us see how the machines our software has to run on change over time. They count computers and nothing else — no account, no device identifier, no hostname, no fingerprint — and, like the totals above, a day's count is not revised when a device or an account is later deleted
• A record that a computer was added to an account — which account, and when — is kept indefinitely, and is not deleted with the machine or with the account. So is the record of when each computer left an account, and how (see Section 2): counting how many installations we gain and lose over time depends on neither half disappearing when the thing it describes does. They are what let us count how many computers were added and lost in a month without that month's figures changing afterwards, and they hold nothing else but our own reference for the machine, whether our software was installed on it or run as a portable copy and, for a departure, which operating system it ran: no hostname, no device identifier, no address
• When you delete your account yourself, we keep a record that an account was deleted, with nothing that identifies it: the week it happened, roughly how old the account was, how far it had got in setting up and using the Service (for example, that a computer had been added but never viewed, or that it had not been used for months), whether the deletion began from the email we send about an unused account, and the reason you chose if you answered the optional question we ask afterwards. Anything you typed under "Other" is deleted after 30 days. The rest is kept indefinitely, so that we can see over time why people leave. None of it is linked to your account, your email address or your IP address. If you tick the box that lets us email you about your answer, we keep the address you give with your answer, use it only to ask you about it, and delete it after 30 days
• Session performance diagnostics (see Section 2) are retained in raw, per-session form for 180 days, then deleted. Daily totals derived from them are kept indefinitely for the same reason the marketing totals above are: how many sessions fell into each latency band, how many ran without the picture stopping, how many never produced a picture at all, split by the network path that carried most of the video and whether the device encoded it in hardware. Those totals count sessions and nothing else — no account, no device, no identifier of any kind — and they are what let a change to our software be compared against the months before it once the per-session rows are gone
• Connection diagnostics — for each attempt to connect a session, whether it connected, how long it took, why it failed, which kinds of network path were available, and whether the viewer and the computer appeared to be on the same network (see Direct Connections in Section 2) — are retained in raw, per-session form for 180 days, then deleted. They record no address: the network paths are counted by kind, never by where they led
• Product Usage Events (see Section 2) are retained in raw, per-account form for 180 days, then deleted — the same window as the marketing site events above, so that the two halves of the same question do not expire on different days. Daily counts derived from them are kept indefinitely for the same reason the other daily totals here are: for each day, how many of these entries were recorded of each kind and extra word, and how many distinct accounts each of those came from. Those counts hold no account, no identifier and no address of any kind, and a day's count is not revised when an account is later deleted, except that erasing an account's data within a week of that day can lower it. If you ask us to erase your data, the raw entries recorded against your account are deleted along with everything else
• Controller profiles (see Section 2) are kept until you change or delete them (the last one until your account is deleted), and tutorial progress until it is reset; our support staff can reset either, and both are deleted with your account
• Your answers to the first-run questions (see Section 2) are kept until you answer them again, which replaces them, or until your account is deleted, which deletes them — except that a game name you typed because your game was not on our list is deleted 30 days after you gave it, and the rest of that answer stays
• Community profiles, and the ratings, comments and installs that go with them (see Section 2), are kept until you remove them, and are deleted with your account. A report somebody files about a profile or a comment is kept for 180 days after it has been decided, then deleted; an open report is kept until it is decided, or until the person who filed it deletes their account
• Help assistant conversations (see Section 2) are deleted 30 days after their last message, together with everything recorded about them. A conversation you handed to a person continues as a support ticket, below
• Support tickets — from our contact form, an email to support@linkraze.com, our apps, or a help assistant conversation handed to a person — are kept until they are deleted. A ticket linked to an account — one opened while signed in, or sent from an address that already belonged to an account — is deleted with the account, and you can delete your own tickets from the dashboard's Support page. To have any other ticket deleted, ask us at support@linkraze.com
• Notes our staff keep on an account (see Section 2) are kept until our staff change or remove them, and are deleted with the account
• Diagnostic logs you send us from our desktop app or the viewer (see Section 2) are deleted after 180 days, and with your account
• A game report (see Section 2) is kept with its support ticket and deleted with it
• A computer’s shared game list (see Section 2) is replaced each time the computer sends it, and the starts and sessions it sent are deleted after 180 days; switching sharing off, removing the computer or deleting your account deletes all of it at once. The record that you switched it on or off is kept while the computer is on your account
• A record that the person at a computer declined to add it to an account — which computer, which notice they were shown, and when — is deleted after 180 days. It is kept after the account it concerned is deleted, without the account, for the rest of that time
• Fraud prevention records (see Section 2), including reports made by the person at a computer about the account that could reach it, are retained indefinitely, including after the account they relate to is deleted (fraud prevention, and evidence of the warnings we issued)
• A record that you asked us to stop sending the account messages described in Section 3 — or that a message to your address permanently failed, or was reported as unwanted — is retained indefinitely, including after the account it came from is deleted. It is stored as an irreversible cryptographic hash of the address rather than the address itself, so it can be checked against an address we are about to write to and cannot be read back as a list of people. We keep it because that is what honouring the request requires: an opt-out that expires, or that is erased along with the account, is one we would go on to ignore
• Payments are not switched on in the Service today, so there are no transaction records to keep. When they are: the subscription state on your account is deleted with the account, and the payment notifications our processor sends us are kept for seven years, the period tax and financial law requires, and then deleted
• Data required by law is retained for the period legally mandated

If you ask us to erase your data, we do not wait for the periods above to run out: the records that outlive a deleted account — the audit entries, the marketing site events, the Product Usage Events, the session performance and connection diagnostics, and the records that a computer was added and that it left — are deleted when we act on your request. The exceptions are the fraud prevention records, the record of an opt-out, the record of a declined computer, transaction records, and anything the law requires us to keep, each described above. One kind of audit entry is not deleted but changed: the record of an action our staff took on your account is our record of what our staff did, so it stays for the rest of its 180 days with your account removed from it. Deleting your account from the dashboard is such a request: confirming it removes everything held against the account directly, and clears those records in the same step. What it leaves are the fraud prevention records, which is what the exception above means, and the anonymous record of the deletion described above, which holds nothing that identifies the account.

5. Cookies & Tracking

Session Cookies: We use httpOnly session cookies to maintain your login state in the web dashboard. These cookies are essential for the Service to function and are automatically set when you access the app. The dashboard shows a notice about them the first time you open it, and remembers in your browser's local storage that you have dismissed it.

Marketing Site Analytics: Our public marketing site uses first-party, consent-gated analytics to measure page views and signup attribution. This does not use cookies — it stores a random identifier in your browser's local storage, and a separate per-visit identifier in session storage — and only activates if you accept the cookie banner. We store a hashed IP address and coarse (country-level) location, never a raw IP address or precise location, and this data is never shared with or sold to third parties. The request that records a page view is not written to our web server logs either. We do not use any third-party analytics services (Google Analytics, Mixpanel, etc.) anywhere in the Service.

What This Choice Does And Does Not Cover: The banner, and the choice you make on it, govern the marketing site analytics described in this section — measurement of an anonymous visitor, before there is any account. They do not govern the Counted Links and Signup Steps described below, which keep only running totals that hold nothing about the visitor, nor the records we keep about the Service itself once you are signed in, such as your sessions, your downloads, the security actions on your account, or the Product Usage Events described in Section 2. Those are records of the Service you signed up for rather than measurement of a visitor, so they are not gated on a cookie choice, they set no cookie of their own and store nothing in your browser, and they are never used for advertising or shared with anyone. Section 6 (GDPR) and Section 7 (CCPA) describe the rights you have over them, including having them erased.

How We Recognise Where You Came From: If you accept the banner, we also record which channel brought you to the site — for example a link we published in a social media profile. This is worked out from information your browser already sends us: any tracking parameters on the address you arrived at (including click identifiers such as fbclid, igshid or ttclid, which the platform adds to the link, not us), the site you came from, and whether the page was opened inside a social app's built-in browser. That result — the channel, and nothing else about the link — is stored in your browser's local storage alongside the identifier above, is attached to the page views we record, and is passed to your account if you sign up. It is deleted from your browser together with the identifier if you withdraw consent.

Counted Links: Some links we publish (for example linkraze.com/go/ig) pass through our own server so that we can count how many people followed them, before sending you to the page. This runs before and regardless of the cookie banner, because it records nothing about you: no cookie is set, nothing is written to your browser, and no IP address — not even a hashed one — is stored, including in our web server logs. All that is kept is a running total per link, per hour, split only by whether the request looked like a phone, a computer or an automated crawler.

Signup Steps: We count how many requests reach each step of signing up: a click on a link to sign up on our site, the app opening on its signup form, that form (which carries the terms summary) being shown, the form's Google, Apple and other sign-in buttons being pressed, the form being sent, an account being created or the form being turned down, and Sign in being pressed when the form answers that the address already has an account. Like counted links, this runs before and regardless of the cookie banner, because the totals record nothing about you: no cookie is set or sent for them, nothing is written to your browser, and no IP address — not even a hashed one — is kept with them. The requests your browser sends only to report a step are not written to our web server logs, and the address they come from is used only in our server's memory, never stored, to limit how many of them one address can send in an hour. An account being created or turned down is counted from the signup itself, whose request is logged like any other (see Section 2). All that is kept is a running total per step, per hour, split only by where a step happened — for a click, which page of our site and which part of it; for the app opening, which of the two signup addresses it opened on; for a sign-in button or an account it created, which provider; for a form turned down, the reason our server gave — and by whether the request looked like a phone, a computer or an automated crawler. These totals cannot tell one visitor from another or follow anyone from one step to the next, and are kept indefinitely.

If you go on to create an account, the marketing-site events recorded under that identifier before you signed up are linked to your account, so that we can attribute the signup. If you withdraw consent, the identifier is deleted from your browser and is not carried into signup.

Help Assistant: If you use the chat described in Section 2, your browser keeps a copy of that conversation — its random identifier, the messages, and a support reference if you asked for a person — in session storage, so that the conversation carries on when you move to another page of our website or another screen of the dashboard. The dashboard and the viewer each keep their own conversation this way, separate from the website's and from each other. It is written only once you have sent a first message. It is not a cookie and is not used to measure or recognise you, it does not depend on the cookie banner because it exists only to carry on a conversation you started, and your browser deletes it when you close the tab.

Cookie Consent: The first time you open our home page or one of our product pages, you will see a banner describing the measurement above and asking you to accept or decline. None of the Marketing Site Analytics described above happens until you accept: declining leaves it off, and so does ignoring the banner. Counted Links and Signup Steps are counted either way, because they keep nothing about you. Continuing to browse is not how we take that answer. You can change it at any time with the "Cookie Preferences" link in the site footer.

Viewer Settings: Our web viewer keeps a few settings in your browser’s local storage, because they are about that browser and its screen — such as your stream quality, the monitor you last chose on each computer, whether the list of your games opens by itself when you connect to each computer, whether haptic feedback and clipboard sync are on, and where you moved the handle at the left edge. For the tab you have open, it also keeps in session storage which session it last showed that list for, so that reconnecting does not show it again; your browser deletes that when you close the tab. If the viewer shows you its note about iCloud Private Relay, it keeps the same kind of mark in session storage so that the note is not shown twice in one session, and, if you choose not to see it again, a mark in local storage that says so. Your controller profiles and, once you are signed in, your tutorial progress are kept with your account instead (see Section 2); someone using a guest link has no account, so for them the viewer remembers in that browser which tutorials they have seen.

Your Rights: You can disable cookies in your browser settings, but this will prevent the Service from functioning properly (you will not be able to maintain a session). You may accept, decline, or change your choice on the marketing site analytics at any time using the "Cookie Preferences" link in the site footer, without affecting your ability to use the Service.

6. Your GDPR Rights (EU/EEA Users)

If you are in the EU/EEA, you have:

• Right of Access: Request a copy of your personal data
• Right to Rectification: Correct inaccurate data
• Right to Erasure ("Right to be Forgotten"): Request deletion of your data
• Right to Restrict Processing: Limit how we use your data
• Right to Data Portability: Export your data in a portable format. The export includes your controller profiles with what is in them, your tutorial progress, your answers to the first-run questions, the game lists your computers share with us (see Section 2), and each action our staff took on your account — a change to its settings, its sign-in or second factor, its computers or sessions, its controller profiles or tutorial progress, or a ban raised over it — and when; it does not say which member of staff took it, or include the details they recorded with it. It also leaves out the staff note on the account (see Section 2) and any change to it: ask us at support@linkraze.com for a copy of that note
• Right to Object: Opt out of specific processing

The right to erasure does not extend to the fraud prevention records described in Section 2. We retain those to prevent fraud and to keep a record of the warnings we issued; everything else is deleted as described in Section 4.

To exercise these rights, visit your account settings → Privacy & Data, or contact support@linkraze.com.

7. Your CCPA Rights (California Users)

If you are a California resident, you have:

• Right to Know: Request what personal information we collect
• Right to Delete: Request deletion of your personal information, except the fraud prevention records described in Section 2
• Right to Opt-Out: Opt out of "sales" of personal information (we do not sell data, but you can opt out of any data sharing)
• Right to Non-Discrimination: We will not discriminate against you for exercising these rights

To submit a request, email support@linkraze.com or visit account settings → Privacy & Data.

8. Third Parties

Payment Processing: Paddle (paddle.com) handles all payments. Their privacy policy governs payment data. Our dashboard loads Paddle's checkout only where payments are switched on.

Hosting: Our servers, our database and its encrypted backups, and the service that sends our email run on Amazon Web Services (AWS). Cloudflare carries the traffic to our marketing site (linkraze.com), so it sees the IP address of everyone who visits it.

Sign-in Providers: If you sign in with Google, Apple, Microsoft or Facebook, that provider tells us who you are when you sign in (see Section 2), and learns that you used it to sign in to LinkRaze. Their own privacy policies govern what they keep.

Videos: The videos on our website and in our dashboard are hosted on YouTube. Their poster images are served from our own servers, so YouTube receives nothing when a page opens; when you press play, the video loads from YouTube (youtube-nocookie.com), which then receives your IP address and applies its own privacy policy.

Password Breach Checking: When you set a password, we check whether it appears in the Have I Been Pwned database of passwords exposed in public data breaches. Your password is never sent to them, and neither is your email address or your IP address. The password is hashed, and only the first five characters of that hash are used to fetch a set of several hundred candidate hashes; the comparison is then made against that set. Five characters identify a bucket of candidates, not your password. Your browser performs this check as you type, and our server repeats it when the password is saved. The request to Have I Been Pwned is made by our server, so they see our server, not you. If the check cannot be completed, your password is accepted anyway.

Help Assistant: The answers in our help assistant are written by an AI model that runs on a computer LinkRaze operates in Israel, not by a third-party AI service, so no AI provider receives your conversation. That computer receives the text of the conversation; whether it was asked on the website, in the dashboard or in the viewer; the language and address of the page (in the dashboard, the screen) and the help topics you had opened — never your IP address or its hash, an email address, anything about your account, or the conversation's identifier — and it does not store or log what it receives.

No Third-Party Sharing: We do not share, sell, or rent your personal information to third parties for marketing. We share data only:

• With service providers (hosting, email sending, delivery of our marketing site, and the payment processor) under data processing agreements
• With Have I Been Pwned, limited to the first five characters of a password hash, as described above
• With the sign-in provider you choose, when you sign in with it
• When legally required (subpoena, court order, law enforcement)
• To protect the safety and integrity of the Service

9. Security

We implement industry-standard security measures:

• Video and audio streams are always end-to-end encrypted (AES-256-GCM); the encryption key is derived directly between your browser and your own device, our relay servers cannot decrypt your stream, and a session cannot be established without end-to-end encryption
• Keyboard, mouse, clipboard, file transfers and the list of games on your computer are end-to-end encrypted on their own separate keys on their way to the viewer
• Our servers, relays and web app require TLS 1.2 or higher in transit; the real-time video and audio path, and input sent over a direct connection, use DTLS 1.2 or higher
• Password hashing (bcrypt, 12 rounds minimum)
• Multi-factor authentication, required by default on all accounts (authenticator app; email codes may also be enabled)
• Desktop installers are code-signed so your operating system can verify their origin and integrity before they run: Authenticode with a trusted timestamp on Windows, and an Apple Developer ID signature with a stapled Apple notarization ticket on macOS
• Audit logging of account and session activity
• Regular security assessments

However, no system is completely secure. We are not liable for unauthorized access resulting from user negligence or compromised credentials.

10. International Transfers

LinkRaze Technologies Ltd. is based in Israel, and our main servers and database run in Israel. The relay servers that carry remote sessions run in Israel, in Ireland (in the EU), in the United States and in Australia, and a session may be carried by any of them: a relay sees the IP addresses of both ends and the session's encrypted stream, which it cannot decrypt. As we scale, we may add servers in other regions; when that happens, your data may be processed in whichever region serves your account. Regardless of where you access the Service from, your data may be transferred to and processed in Israel, where LinkRaze is operated. The AI model that answers our website's help assistant (see Section 8) runs in Israel too.

If you are in the EU/EEA: the European Commission has recognised Israel as providing an adequate level of protection for personal data, so transfers of your data to Israel do not require any additional safeguard or your separate consent. If we later process your data in a region that is not covered by an adequacy decision, we will put an appropriate transfer mechanism in place before doing so.

11. Children & Minimum Age

LinkRaze is for adults only. You must be at least 18 years old to create an account or use the Service — this is a condition of use, set out in section 1.5 of our Terms of Service, not only a statement of who we design for.

The Service is not directed to children, and we do not knowingly collect personal information from anyone under 18. We do not ask for a date of birth: we rely on the confirmation you give when you create an account, and we act on what we learn afterwards.

If we learn that we hold personal information about someone under 18, we will delete that information and close the account without undue delay.

If you are a parent or guardian and believe your child has given us personal information, or you believe an account belongs to someone under 18, email support@linkraze.com. Tell us the email address on the account and we will act on it.

12. Contact Us

For privacy-related questions, requests, or complaints, contact the data controller:

LinkRaze Technologies Ltd. (company number 517376554)
Shoval 40, Alfe Menashe, Israel
Email: support@linkraze.com

You also have the right to lodge a complaint with your local data protection authority (DPA) in your country.