Privacy Policy

Ten dokument jest publikowany wyłącznie w języku angielskim. Wiążąca jest wersja angielska, a jeśli chcesz uzyskać pomoc z tym dokumentem w swoim języku, napisz na adres 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").

2. Information We Collect

Account Information: When you register, we collect your email address, full name, and 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.

Device Information: When a computer is added to a LinkRaze account, we record its hostname and a hardware fingerprint — a value derived from that computer's hardware that identifies it as the same physical machine across reinstalls. 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 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; 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 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.

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). 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.

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.

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 transaction confirmations, subscription status, and the limited card metadata contained in Paddle's transaction records (card brand, expiry date, and the last four digits).

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 hardware fingerprint 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.

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; 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; how many frames arrived and how many bytes they took; round-trip latency over the session, as a typical and a worst-case figure; 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; and how much of the session our software was measuring for.

These are measurements ABOUT the video stream, computed inside your browser after the stream has been decrypted there — 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.

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. Each of these is one entry from a fixed list of six, 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. 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 briefly in our server logs with the IP address they came from, but not with the conversation's identifier. 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.

Technical Data: Browser type, operating system, referring URL, and error logs to improve service reliability.

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 (unauthorized login attempts, password changes, new devices)
• 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, how often the person at a device declines or withdraws access, 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 that has not established a payment relationship with us may add, and hold that account's first connection to a newly added device for a short period
• 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
• 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, and to count how many of our marketing site's visitors came from each country. 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. 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. This notice carries the same unsubscribe link and the same promise about your access
• 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 two bullets above are not sent on the strength of it either
• 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 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. After account deletion or termination, personally identifiable information is permanently deleted within 30 days, except:

• Session logs are retained for 90 days, then summarized into aggregate usage statistics and deleted (security and compliance)
• Audit trail entries (account and security actions) are retained for 180 days (security and compliance)
• 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, both for each country a visit was attributed to and for each channel or campaign that brought it (see Section 5). 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
• 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 which network path the video took 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
• 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. If you ask us to erase your data, the raw entries recorded against your account are deleted along with everything else
• 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
• Fraud prevention records (see Section 2) 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
• Transaction records are retained for 7 years (tax and financial compliance)
• Data required by law is retained for the period legally mandated

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.

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. 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 described in this section — measurement of an anonymous visitor, before there is any account. They do not govern 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. 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.

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: On your first visit, you will see a cookie consent banner explaining our cookie and analytics usage. By accepting it, or by continuing to use the app, you acknowledge the practices described in this section.

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
• 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, 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.

8. Third Parties

Payment Processing: Paddle (paddle.com) handles all payments. Their privacy policy governs payment data.

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 (payment processor, email sender) under data processing agreements
• With Have I Been Pwned, limited to the first five characters of a password hash, as described above
• 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 and file transfers are end-to-end encrypted on their own separate keys
• Our servers, relays and web app require TLS 1.2 or higher in transit; the real-time video and audio path is pinned to DTLS 1.2
• 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 servers currently run in a single hosting region. As we scale, we plan to expand to additional regions (e.g. in Europe and the United States) for redundancy and lower latency; when that happens, your data may be processed and stored 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.