In plain language

We cannot see inside your remote sessions. They are encrypted between the two devices, and we hold no key. We know a session happened, between which devices and for how long. We do not know what was on the screen.

The free version needs no account, so we hold no name, no e-mail address and no payment details for free users — only what a device must tell us to be findable.

We never see your card number. Payments go to SafePay directly; we receive a reference and an amount. If you choose to save a card, SafePay keeps it and we keep only its type, last four digits and expiry.

We do not sell your data. Not to advertisers, not to data brokers, not to anyone.

This summary is for convenience only. The numbered clauses below are the agreement.

1. Who we are

Trendifyr Tech (Private) Limited is a private limited company incorporated in the Islamic Republic of Pakistan and registered with the Securities and Exchange Commission of Pakistan (SECP). It develops and operates DeskTunnel (the “Service”), and is the controller of the personal data described in this policy.

You can reach us about anything in this document at [email protected].

Where the Service is operated. We operate the Service from Pakistan. Our coordination servers and database are hosted with infrastructure providers which may be located in Pakistan or elsewhere. Section 9 explains what that means for you.

2. Scope

This policy covers:

this website, https://www.desktunnel.com;
the DeskTunnel application, Windows service and session components;
the coordination (relay-matching) server and the management API;
the DeskTunnel management dashboard available to paid customers.

It does not cover third-party websites we link to, or the internal use a paid customer makes of the Service within their own organisation. Where an organisation uses DeskTunnel to manage its own devices and staff, that organisation is the controller of the data it enters and we act as its processor; see the Data Processing Addendum.

3. The one thing to understand

A remote-desktop product carries everything on a screen and everything typed into it. That is the most sensitive thing we could possibly handle, so we arranged not to handle it.

Each DeskTunnel session is encrypted end to end between the two devices using TLS 1.3 with per-session certificates, and each end pins the other’s certificate. We are not a party to that encryption and hold no key to it.

We therefore do not and cannot collect, read, record or disclose the contents of a session: screen contents, keyboard and mouse input, clipboard data, transferred files, audio, or chat messages. This is a property of the design, not a promise about our conduct, and it holds even where a session is carried by a relay — see the Network Participation Terms.

We do hold metadata about sessions: that one occurred, between which device identifiers, when it started and ended, and which transport was used. Section 4 lists it.

4. What we collect

4.1 Device registration data — every installation, free and paid

A device must be findable to be reachable. When DeskTunnel starts, and again whenever the device moves to a different network, it registers with our coordination server and we record:

a device address — the ten-digit number others use to reach the device — and a machine identifier derived from the hardware;
the device’s public IP address, and the country, city and network operator derived from it;
the device name as reported by Windows, the operating system version and the DeskTunnel version;
connection state and the time it was last seen online;
the device’s local network address and the hardware (MAC) address of its main network card, so that another device of the same organisation on the same network can switch it on remotely (Wake-on-LAN);
network characteristics used to choose a transport: whether UDP and IPv6 work, the type of NAT in front of it, and whether the device is reachable for inbound connections.

A device name may identify a person — Windows machines are frequently named after their user. We treat registration data as personal data for that reason.

4.2 Session metadata

which device connected to which, and at what time;
how long the session lasted and how it ended;
which transport was used (direct QUIC, direct TLS, or relayed) and, if relayed, which relay;
how the two devices reached each other — over the local network, through both routers by hole punching, through a forwarded port, or through a relay — whether hole punching was attempted and succeeded, and the kind of NAT each device’s router showed during the attempt (for example “symmetric”). No address is stored with it beyond what this section already lists;
connection quality measurements reported after the session — round-trip time, jitter, packet loss, throughput and time-to-connect;
for paid customers, an entry in the session history and, where the organisation has enabled it, an audit-log record naming the user who started it.

Not the content. Never the content.

4.3 Account data — paid plans only

your name, username, e-mail address and, if you give it, your telephone number and country;
a hash of your password. We do not store, and cannot recover, the password itself;
your organisation’s name and, if supplied, its domain, address and telephone numbers;
your plan, billing cycle, seat count, subscription status and any coupon applied;
roles and permissions assigned to you within your organisation;
sign-in timestamps, failed sign-in counts and lockout state;
which devices you asked to be notified about (when one goes offline, or somebody connects to it), the notifications sent to you, and the device commands you sent and how they ended.

4.4 Payment data

Payments are processed by SafePay. Card details are entered on SafePay’s own hosted page and are transmitted directly to them. We never receive, see, process or store your card number or security code.

We record what we need for accounting and support: the amount, the currency, the date, a payment reference, the status, and whether a coupon was applied, and we keep every invoice we issue.

If you save a card for future payments, SafePay stores it against a customer record it keeps for your organisation. We keep SafePay’s reference to that customer and card, and the card’s type, last four digits and expiry month and year, so that you can recognise it in the billing portal and so that we can ask SafePay to charge it for a renewal you have agreed to. We also record when, and by whom, consent to save it was given. Remove the card in the billing portal and we ask SafePay to delete it.

4.5 Support and contact data

When you use the contact form or write to us we keep your name, e-mail address, any company details and telephone number you supply, your message, the page you submitted it from, your IP address and browser user-agent, and our correspondence with you.

4.6 Website data

See the Cookie Policy. In short, this website sets no advertising or cross-site tracking cookies, and the only thing it stores in your browser by default is your choice of light or dark theme and, while you are signing up, the state of that sign-up.

4.7 What we do not collect

session content, in any form;
your card number or its security code;
your DeskTunnel password, or the password that protects unattended access to a device;
the files on your computer, except a file you choose to transfer, which we do not see;
advertising identifiers, or data for sale to third parties;
special-category data, which we neither ask for nor want.

5. Why, and on what legal basis

Where the General Data Protection Regulation (EU) 2016/679 or the UK GDPR applies to our processing of your data, the following table sets out our purposes and the lawful bases we rely on. Where Pakistani law applies, we process on the basis of your consent and of our legitimate interest in operating the Service, and we apply the same standards.

Purpose	Data	Lawful basis
Make a device reachable and connect two devices	Registration data, network characteristics	Performance of a contract — it is the Service
Choose the best transport and relay for a session	Network characteristics, quality measurements, geo data	Legitimate interests — a usable connection
Provide the management dashboard	Account data, session metadata	Performance of a contract
Take payment and keep accounts	Billing data, payment references	Performance of a contract; legal obligation (tax)
Answer your enquiry	Contact data	Legitimate interests; steps prior to a contract
Prevent abuse, fraud and unauthorised access	IP addresses, sign-in and lockout records, audit logs	Legitimate interests — security of the Service
Diagnose faults and improve the product	Error logs, aggregate quality measurements	Legitimate interests
Send product and offer e-mails	Name, e-mail address	Consent — given by ticking the box, withdrawable at any time
Comply with law and defend claims	Whatever is relevant	Legal obligation; legitimate interests

Where we rely on legitimate interests we have considered whether those interests are overridden by your rights and freedoms, and we have concluded they are not. You may object to that processing: see section 11.

6. Children

The Service is not directed at children and is not intended for use by anyone under 16. We do not knowingly collect personal data from a child under 16. If you believe a child has provided us with personal data, write to [email protected] and we will delete it promptly.

7. How long we keep it

What	How long
Device registration records	While the device registers, then 12 months after it is last seen
Session metadata, free plan	Up to 7 days
Session metadata, paid plans	The retention period of the plan: 90 days (Pro), 365 days (Business), 1,095 days (Enterprise)
Account data	While the account exists, then 90 days, unless we must keep it longer
Billing and accounting records	As required by Pakistani tax and company law — generally 6 years
Audit logs	The retention period of the plan
Contact form submissions	24 months from the last correspondence
Error logs and diagnostics	90 days
Relay quality measurements	Aggregated continuously; raw per-session reports for 90 days

Where a record is subject to a legal hold, an unresolved dispute or an ongoing investigation, we keep it until that concludes.

We do not sell personal data, and we do not share it for advertising. We share it only in these circumstances:

Service providers (processors) who act on our instructions and are bound by contract: our hosting and database providers, SafePay for payments, and our e-mail delivery provider. They are listed in the sub-processor list.
Within your own organisation. If you use DeskTunnel under an organisational account, your administrators can see the devices you connect to, when and for how long, and the audit entries your actions generate. That is the point of a management dashboard, and you should assume it.
Professional advisers — lawyers, auditors and accountants — under a duty of confidence.
A buyer or successor, if the business or the relevant part of it is sold, merged or reorganised. We would tell you, and this policy would continue to apply until replaced by one no less protective.
Authorities, where we are lawfully required to disclose. See section 14.

9. International transfers

The Service is operated from Pakistan, and your personal data will be processed there. Depending on where our infrastructure and relay servers are located at any time, it may also be processed in other countries.

Pakistan has not been the subject of an adequacy decision by the European Commission or the UK government. If you are in the European Economic Area or the United Kingdom, this means your personal data will be transferred to a country which is not recognised as providing an equivalent level of protection to that of EU or UK law, and you may have fewer or less practically enforceable rights there.

Where we make such a transfer we rely on one or more of the following:

Standard Contractual Clauses adopted by the European Commission (and the UK International Data Transfer Addendum where the UK GDPR applies), which we will provide a copy of on request;
your explicit consent to the transfer, having been informed of the risks by this section;
necessity for the performance of the contract between you and us, since the Service cannot be delivered without it.

Regardless of location we apply the safeguards in section 10 and require the same of our processors.

10. How we protect it

End-to-end encryption of session content, with per-session certificates pinned at both ends and TLS session resumption disabled so that pinning cannot be bypassed.
Encryption in transit for every connection to our servers, and encryption of the local settings file on your device.
Passwords hashed with bcrypt. Unattended-access passwords are derived with PBKDF2-SHA256 using a per-device salt and are proven by HMAC — the password itself never leaves the device.
Strict tenant isolation. Every query in the management API is scoped to one organisation. A query that could cross that boundary is treated as a security defect.
Least privilege within our team, with access to production data limited to those who need it and logged.
Lockouts and rate limits on sign-in, on unattended-access attempts and on the contact form.

No system is perfectly secure, and we do not claim otherwise. The Security Statement goes into more detail.

11. Your rights

Subject to the law that applies to you, you may ask us to:

tell you what we hold about you, and give you a copy;
correct anything inaccurate or incomplete;
delete it, where we have no overriding reason or obligation to keep it;
restrict what we do with it while a dispute about it is resolved;
port it — receive it in a structured, machine-readable format, or have it sent to another controller where technically feasible;
object to processing we base on legitimate interests, and to direct marketing at any time and absolutely;
withdraw consent you have given, without affecting processing already carried out on it.

Write to [email protected]. We answer within 30 days, and will tell you if we need longer and why. We may ask you to verify your identity first — not to obstruct you, but because handing your data to somebody pretending to be you would be the worse failure. We do not charge for this unless a request is manifestly unfounded or excessive.

If you use DeskTunnel through your employer or another organisation, that organisation controls your data. Send your request to them; we will assist them in answering it and will refer you to them if you come to us first.

12. Regional rights

12.1 European Economic Area and United Kingdom

You have the rights in section 11 under the GDPR or UK GDPR and the right to lodge a complaint with your national supervisory authority — in the UK, the Information Commissioner’s Office. We would ask you to raise it with us first, but you are not obliged to.

12.2 Pakistan

We process personal data in accordance with applicable Pakistani law, including the Prevention of Electronic Crimes Act 2016 and data-protection legislation as and when it is brought into force. Where new obligations commence, we will meet them and update this policy.

12.3 California

If you are a California resident, you may request disclosure of the categories and specific pieces of personal information we have collected, request deletion, and request correction. We do not and have not sold or shared personal information as those terms are defined by the CCPA/CPRA, and we do not process it for cross-context behavioural advertising. We will not discriminate against you for exercising these rights.

12.4 Elsewhere

If the law where you live gives you rights beyond those described here, tell us and we will honour them.

13. Cookies

This website does not use advertising or cross-site tracking cookies. Full detail is in the Cookie Policy.

14. Lawful disclosure

We may disclose personal data where we are required to by law, by a court of competent jurisdiction, or by a lawful request from a competent authority; or where it is necessary to establish, exercise or defend a legal claim, or to protect the rights, property or safety of any person.

Our practice is:

to satisfy ourselves that a request is lawful and properly issued, and to narrow it where it is broader than the law requires;
to notify the affected user where we are permitted to do so;
to be unable to produce session content, because we do not hold it and are not technically able to obtain it.

15. If something goes wrong

If a personal data breach occurs that is likely to result in a risk to your rights and freedoms, we will notify the competent supervisory authority without undue delay and, where required, within 72 hours of becoming aware of it. Where the risk is high, we will tell you directly and without undue delay, describing what happened, what it means for you and what we are doing about it.

16. Changes

We update this policy as the Service changes. For a material change we will give at least thirty (30) days’ notice by e-mail to account holders and by a prominent notice on this website. The date at the top is the date of the current version, and previous versions are available on request.

17. Contact and complaints

Trendifyr Tech (Private) Limited
Pakistan
Privacy: [email protected]
Security: [email protected]

If you are unhappy with how we have handled your data or your request, tell us and we will look at it again. You may also complain to the supervisory authority in your country.

Privacy Policy