1. What this covers
This policy describes which personal data we process when you visit this website (www.deskranger.app) and when you use DeskRanger: the apps, the web console and the services behind them – account, coordination, relays and support. DeskRanger is in development; where something is only planned, we say so. It describes principles, not individual features:
- Content stays with you. The screen, sound, input, clipboard, files and terminal of a session never reach our servers in cleartext (section 6).
- What a feature reads on your device stays on your device – for example the location, the Wi-Fi name or device information – unless this text expressly says otherwise. Whoever sees your screen in a session also sees what is shown there.
- We store only what the service needs: account, devices and connection metadata (sections 4 and 5), never session content. What you send us yourself, such as a chat message, an email or a diagnostic package, is covered in sections 7 and 10.
- No advertising, no tracking, no sale of data. The apps send error reports only with your consent.
2. Controller
The controller within the meaning of the General Data Protection Regulation (GDPR) is:
exenso GmbH
Gutenbergstraße 9
77955 Ettenheim
Germany
Represented by the managing directors Thomas Schwarz, Michael Unmüßig. For any data protection question you can reach us at support@exenso.ai. Further details are in the Legal notice.
3. Visiting this website
No cookies, no third-party trackers
The website sets no cookies of its own (it only reads the account service’s signed-in hint, see the account section; for the help chat see below), includes no advertising or tracking services and loads nothing from foreign servers. Your choice of “Light”, “Dark” or “System” and the platform you pick in the help are stored locally by your browser (localStorage, deskranger-theme, deskranger-help-platform); they never leave your browser and are strictly necessary for the function you asked for (§ 25(2) no. 2 TDDDG). Links to other providers open their pages only when you click them.
If you start the help chat without signing in, our support service sets the cookie __Host-dr-chat with your conversation’s identifier. It is valid for 30 days, is deleted when you sign in from the chat and is strictly necessary for the chat you asked for (§ 25(2) no. 2 TDDDG).
Audience measurement with Plausible
To understand which pages are of interest, we count page views and a few clicks (for example on “Download free”, in the help the answers to “Was this helpful?” and searches without a hit, without the search term) with Plausible Community Edition. We run it ourselves, in the EU at our cloud hosting provider (section 11); the data goes to no other provider.
Recorded are the page viewed and the referring page, campaign details in the address, browser, operating system, device type and the country derived from the IP address at the time of the request. Plausible sets no cookies. The IP address is not stored; a daily changing random value, deleted after 24 hours, groups views of the same day. Recognising you across days or building a profile is not possible.
The legal basis is our legitimate interest in data-sparing audience measurement (Art. 6(1)(f) GDPR). You can object at any time: with “Stop counting this device” on this page your browser stores plausible_ignore, after which the script sends nothing. Retention: once the random value is deleted, views can no longer be attributed to anyone; we keep the statistics as long as we need them to improve the website.
Hosting, forwarding and status page
The website runs as a static site at our cloud hosting provider (section 11). Our web server writes no access logs. At its network edge the hosting provider records technical data for every request: IP address, time, method, address requested, status code, browser identifier, data volume, response time and region. It is needed to deliver the website securely and to find faults (Art. 6(1)(f) GDPR); the provider deletes it after 30 days.
If someone opens deskranger.app without “www”, a service of our domain registrar forwards the request and technically processes the IP address and the request. The status page (status.deskranger.app) deliberately sits with a different provider of code hosting and static websites so that it stays reachable during an outage; it too technically processes the IP address on each visit. The status page sets no cookies and counts no visits. Both: Art. 6(1)(f) GDPR; for transfers to the USA see section 13.
4. DeskRanger account
You need an account for DeskRanger. Our account service stores:
- Account data: name, email address (confirmed or not), time of registration and, for an account with a password, the password only as a cryptographic hash.
- Sign-in sessions: session key, expiry, and the IP address and browser or app identifier at sign-in. A session ends on sign-out or after seven days without use.
- Sign-in activity: for every sign-in and every failed attempt the time, result, method, app or browser and system, and the approximate place (city and country, section 5) – not the IP address. You see it under Security to spot foreign sign-ins. We delete it after 90 days.
- Sign in with Apple or Google: the provider’s identifier, the email address (with Apple, on request a relay address), your name if you release it, possibly the address of your profile picture, and the sign-in tokens. We link an existing account only if the provider reports the email address as confirmed. The provider’s own privacy terms apply as well (Google Ireland Limited).
- Codes for email links (section 8): a single-use code for resetting the password (valid one hour); the confirmation link (24 hours) is not stored.
To prevent abuse the service limits sign-in attempts per IP address, in memory only. For the coordination service it issues short-lived proofs (15 minutes) that contain only the account identifier and display name, never your email address.
In the web console (app.deskranger.app, in preparation) a cookie of the account service keeps you signed in (__Secure-better-auth.session_token, up to seven days or until the browser closes), and with Apple/Google a second one for five minutes for the sign-in. While you are signed in, the account service also sets the hint dr_signed_in for deskranger.app: it holds only the value “1”, no session and nothing about you, lives as long as the sign-in and is deleted when you sign out; the website uses it to show that you are signed in. All three are strictly necessary cookies for the sign-in you asked for (§ 25(2) no. 2 TDDDG). The apps keep the sign-in in the device’s keychain or secure storage.
Legal basis: Art. 6(1)(b) GDPR; for abuse protection and sign-in activity (protecting your account) Art. 6(1)(f) GDPR. Deletion: you can delete your account at any time in the app or the web console. We then delete account data, sessions, sign-in activity and linked sign-ins; beforehand the coordination service deletes everything it stores about your account (section 5). We keep the invoices, credit notes and refunds of your purchases after your account is deleted, for ten years from the end of the calendar year they were issued in, because the law requires it (§ 147 AO, § 257 HGB; Art. 6(1)(c) GDPR); then we delete them.
5. Devices and connections
Our coordination service manages your devices and brokers connections. It knows your account only by an identifier; it never sees your email address or password. It stores:
- Devices: name, platform, type, app version, supported features, the result of its self-check (whether the device can show a screen right now: yes, no or not testable, with a fixed cause such as “permission missing” when no; never names, paths, window contents or pictures), public key and certificate lifetime, whether unattended access is on, a salted hash that merges entries of the same computer, and when the device was added and last online.
- What you create: groups, favourites, connection targets (name, protocol, address, port, brokering device, possibly a user name – never a password, which stays in your device’s keychain), and your account’s plan and limits.
- Connection metadata: for each connection, which device of which account connected to which device, the permissions, whether it was attended (accepted by someone at the device) or via a support code, times, duration, data volume and whether it ran directly or via a relay. We also count, per account and day, how many bytes of your connections went directly and how many through our relay, without content or addresses; we delete these totals after 13 months or with your account. Rough set-up times we count only as totals across all connections, with no link to a person or device. At the end of a screen session two marks are added: “picture” (whether the viewing side saw a picture, yes or no) and, when the device could not show one, “host_cause” (the fixed cause, such as “permission missing”, with the device’s build number); both are closed codes with no names, paths or pictures, belong to the session’s log entry and are deleted with it. Never session content (for support messages and diagnostic packages see sections 7 and 10).
- Support codes only as a keyed hash, deleted 24 hours after expiry.
While a device is online the service keeps its network addresses and a summary of its reachability in memory and passes them only to devices allowed to connect (your own, or the person you help with a support code or who helps you). From the IP address it forms a per-account hashed network marker to recognise devices on the same network; the IP address itself is not stored in the database. It limits redeeming support codes per IP address in memory.
We derive the approximate place (city and country) for approval requests and sign-in activity, to protect your account (Art. 6(1)(f) GDPR), from the IP address on our own server with the “IP to City Lite” database by DB-IP (licence CC BY 4.0), with no request to third parties. Only the result is stored, in the sign-in activity; for approval requests only while the request is open. Directly distributed versions ask the coordination service for updates (platform, channel and version are sent) and download them from storage at our cloud hosting provider in the EU.
Legal basis: Art. 6(1)(b) GDPR; for connection metadata also (f) (security, traceability, plan limits).
Retention: device data, groups, favourites and connection targets until you remove them or delete your account; network addresses while the device is online. We delete connection grants after 30 days and session logs (start, end, direct or relay, duration, data volume) after 12 months; if you delete your account, immediately. If you had a session with another person’s device via a support code, their log entry stays with them until its period ends, with no link to your account.
6. Session content, relays and device information
What happens in a session – screen, sound, input, clipboard, files, terminal – is end-to-end encrypted and runs directly between the devices where possible. If there is no direct path, our relays forward the data; they see only encrypted data, the devices’ IP addresses and their public keys, hold no keys and store no content. A relay admits only devices signed in at the coordination service.
Device information such as load or operating system version is exchanged directly and encrypted between your devices; it is not stored on our servers. The apps contain no analytics or tracking services.
Our services’ operating logs are kept at the cloud hosting provider. They contain no passwords, session keys, email addresses, IP addresses or content, only technical identifiers; relays log only a shortened device identifier and a connection number. At its network edge, however, the hosting provider records for every request, including setting up a relay connection, the data named in section 3 including the IP address, and deletes it after 30 days.
7. Error reports, help chat and requests
Faults and questions reach us as an error report after a crash, in the help chat and as a request. The apps use no libraries that record screens or the operation.
Error reports after a crash
Only with your consent. After a crash the app asks at the next start whether it may send a report (“Send”, “Always send”, “Don’t send” – which deletes it). Under Settings › Privacy you switch “Send error reports” on or off at any time; for a device’s service that runs for all users an administrator decides, and only that administrator’s app sends. The web console asks in the same way and stores nothing in the browser before you answer; only “Always send” or the switch stores the choice, installation identifier and report identifiers (localStorage), and switching off deletes them. Development builds (DEV) for us and invited testers always send; testers are told beforehand.
Content: where in the program the fault occurred, its kind and cleaned message, app version, operating system, architecture, device class, language, whether the device was in a session (direct or relay), the last error codes, time and run time, a random installation identifier (created with consent, deleted on withdrawal; neither account nor device identifier, not linked to your account) and the number of app starts and crashes per version. Never included: screen contents, sound, clipboard, files and file names, terminal, input, passwords, keys, tokens, support codes, memory dumps, recordings of operation. The app replaces device names, user names in paths, host names, IP and email addresses with placeholders before sending.
Route and recipients: encrypted to our own intake service (diag.deskranger.app, cloud hosting provider in the EU, section 11). It checks and cleans the report again and passes it without your IP address to an error analysis provider, which stores it as our processor in the EU (Frankfurt am Main); it is based in the USA (section 13). IP storage and AI features are switched off there. To limit abuse the intake service uses your IP address only in memory as a daily changing check value.
Legal basis: your consent (Art. 6(1)(a) GDPR, § 25(1) TDDDG); you can withdraw it at any time, and the app then deletes unsent reports and the installation identifier. Retention: on the device at most 20 reports for up to 30 days; at the provider at most 90 days. For earlier deletion give us the report identifier (shown in the settings).
Help chat and requests
In the help chat an AI answers your questions. For this, your messages go through an intermediary service to AI models (section 12). The chat accesses data of your account (plan, devices, versions, recent sign-ins) only with your consent for that conversation, never IP addresses, session content or files.
A request arises from the chat, by email to support@deskranger.app or with “Report a problem”. For it we process your messages, attached files, email address, language and plan; an AI helps classify, summarise, translate and draft answers, which a person sends. With “Report a problem” you can attach a diagnostic package: versions, system, network type and connection path, the reachability check result, the last error codes, connection values and the logs of the last 24 hours (in the web console: browser, system, error codes, report identifiers, page log), never session content, files, clipboard, input, passwords, keys or peer addresses. You can look at it first or leave it out; it is encrypted on your device so that only our support can open it.
Legal basis: Art. 6(1)(b) GDPR for questions about an account or contract, otherwise (f) (answering your question, preventing abuse); for access to account data in the chat your consent ((a)), which you can withdraw at any time. You send the diagnostic package yourself for help you request (§ 25(2) no. 2 TDDDG). Retention: chats without sign-in 30 days after they start, chats with sign-in without a request 90 days after the last message, requests 24 months after they are closed (Free: 12 months), diagnostic packages 30 days. When you delete your account we also delete your chats and requests, unless statutory retention applies. Unanswered questions help us improve the help. They stay internal and are deleted with the chat. We note them without a person, addresses, numbers or names; for up to 180 days only a count with keywords remains, without the wording of the question.
8. Emails
For “Reset password”, confirming your email address, acknowledgements of and answers to requests and later team invitations we send emails (noreply@deskranger.app, for requests support@deskranger.app) through an email delivery provider, which receives your email address and the message content and stores delivery and log data in the USA (section 13). Content from sessions or devices does not go to it. Legal basis: Art. 6(1)(b) GDPR; for the acknowledgement without an account (f). The provider is our processor.
9. Purchases, App Store and TestFlight
DeskRanger cannot be bought at present; before purchases become possible we will add here who handles them and which data arises. You get the iPhone and iPad apps through Apple’s App Store (in the EU: Apple Distribution International Ltd., Ireland), pre-release versions through TestFlight. Apple processes data on your Apple ID, downloads and purchases as an independent controller. If you take part in TestFlight, Apple gives us your name and the email address you were invited with, installation and usage details, crash reports and feedback if you send them; we use them to distribute test versions and fix faults (Art. 6(1)(b) and (f) GDPR). Purchases in app stores are handled by the store; we receive only your subscription status.
11. Where the services run
Website, audience measurement, account service, coordination service, relays, database, update storage, the intake service for error reports and the support service run at a cloud hosting provider as our processor, in data centres in the EU (Netherlands). The provider is based in the USA; access from there, for example for support and operations, cannot be ruled out (section 13).
12. Recipients at a glance
- Cloud hosting provider (based in the USA, data centres in the EU) – running the website and all services; processor.
- Email delivery provider (based in the USA) – sending emails; processor.
- Error analysis provider (based in the USA, data kept in the EU) – error reports, without IP addresses; processor.
- Intermediary service and providers of AI models (in the EU or in third countries with appropriate safeguards, section 13) – help chat and handling of requests, without storage and without training on our data; processor.
- Object storage provider (data kept in the EU) – files for chats and requests, encrypted; processor.
- Email forwarding provider (based in the USA) – receiving emails to support; processor.
- Provider of office and email services – our mailbox; processor.
- Domain registrar (based in the USA) – forwarding to www.deskranger.app.
- Provider of code hosting and static websites (based in the USA) – our status page.
- Provider of a video decoder (based in the US) – only in the Linux app and only if the computer cannot decode the picture on its graphics card: your device downloads the decoder once, directly from there; the provider sees your IP address, we learn nothing of it; an independent controller. You can switch this off in the app.
- App stores and sign-in providers (Sign in with Apple/Google, once offered) – each an independent controller.
We do not sell personal data. Authorities receive data only if we are legally obliged to provide it.
13. Transfers to third countries
Some of our providers are based in the USA or can access data from there (section 12). Where they are certified under the EU-US Data Privacy Framework, we base transfers to the USA on the European Commission’s adequacy decision for it (Art. 45 GDPR); otherwise, for other third countries and where necessary additionally, on the EU standard contractual clauses (Art. 46(2)(c) GDPR). You can get a copy of the safeguards on request at support@exenso.ai (section 2).
14. Your rights
You have the right of access (Art. 15 GDPR), rectification (Art. 16), erasure (Art. 17), restriction of processing (Art. 18) and data portability (Art. 20). You can withdraw consent at any time with effect for the future (Art. 7(3)). Write to us at support@exenso.ai.
Right to object: where we process data on the basis of Art. 6(1)(f) GDPR, you can object at any time on grounds relating to your particular situation (Art. 21 GDPR).
Complaint: you can complain to a data protection supervisory authority (Art. 77 GDPR). Responsible for us is the Landesbeauftragte für den Datenschutz und die Informationsfreiheit Baden-Württemberg, Lautenschlagerstraße 20, 70173 Stuttgart, Germany, www.baden-wuerttemberg.datenschutz.de.
15. Required data and automated decisions
Without an email address (or sign-in with Apple or Google) and a name we cannot set up an account; without the device data in section 5 we cannot broker connections. You can use the website without giving any data. We make no automated decisions within the meaning of Art. 22 GDPR and create no profiles.
16. Security
All connections to our services are encrypted with TLS, sessions between devices additionally end-to-end. Each device has its own key that never leaves the device; a session needs a short-lived authorisation that the target device itself checks. Every running session is visible on the device.
17. Changes
We adapt this policy when DeskRanger or the law changes, in particular before email sending or purchases start. The version published here applies.