Scope and our role
This Privacy Policy applies to the CoDesk websites, applications, cloud services, customer console, and support services operated by iHoree Ltd. (collectively, the Services). iHoree Ltd. is the controller of personal data processed for the CoDesk cloud service.
Organizations may deploy CoDesk on their own infrastructure. In a self-hosted deployment, that organization controls its instance and is generally responsible for the personal data it processes. Please contact that organization for requests concerning its instance.
Information we collect
The information collected depends on the features you use and whether you use our cloud service or a self-hosted deployment.
- Account and organization data, such as username, email address, optional phone number, organization, role, authentication method, and password verifier. We do not store your password in readable form.
- Device and connection metadata, such as device identifier and name, platform, app version, IP address, connection route, session timestamps and duration, traffic totals, diagnostics, and security events.
- Content you choose to sync or submit, such as encrypted address-book data and credentials, device groups, preferences, support tickets, and messages to us.
- Subscription and transaction data, such as plan, order, amount, currency, payment status, and transaction reference. Payment providers and app stores process full payment credentials under their own policies.
- Website and console data, such as requested pages, browser and operating-system information, approximate location inferred from IP, language and theme preferences, and server security logs.
Android Local Device Capabilities and Software Information Processing
1. Software installation information
To identify the app installation channel and provide the corresponding subscription method, after the user agrees to the Privacy Policy, CoDesk calls Android PackageManager locally on the device to query only CoDesk's own installation source or app-store identifier.
The scope of processing is limited to CoDesk's own installation source. CoDesk does not enumerate, store, or upload the complete list of installed software on the user's device. This software installation information is used only to distinguish Google Play, other app stores, or sideloading channels and select the corresponding subscription method. It is not used for advertising, user profiling, or cross-app tracking.
2. Network interfaces and MAC addresses
To discover local-area-network addresses, establish peer-to-peer or relay connections, and send Wake-on-LAN packets, after the user agrees to the Privacy Policy, CoDesk uses Qt to enumerate network interfaces, IP addresses, and broadcast addresses locally on the device. Android or Qt may also return the local network interface MAC address while enumerating network interfaces.
The local network interface MAC address is used only to determine local network connectivity. It is not uploaded to CoDesk servers and is not persistently stored.
A target device MAC address entered by the user is used only for the Wake-on-LAN local network wake feature and is stored in the user's local device configuration. It is deleted when the user deletes the corresponding device configuration. A target device MAC address is not processed as a local network interface MAC address; they are separate categories of information.
3. Sensor type and audio device capability lists
To initialize Qt Multimedia components and determine remote-audio compatibility, after the user agrees to the Privacy Policy, CoDesk may call Android system interfaces to read the list of sensor types supported by the device and the list of audio input/output device capabilities.
CoDesk does not read sensor measurements, including acceleration, orientation, location, or motion-state measurements. CoDesk does not upload or store the sensor type list or audio input/output device capabilities, and does not use this information for advertising, user profiling, or cross-app tracking. The scope of reading is limited to device-supported capability types and audio compatibility checks.
4. Processing timing and user choice
The software installation information, network interface/MAC address information, and sensor type list described above may be read by the relevant business modules only after the user explicitly taps “Agree and Continue.” If the user does not agree, CoDesk does not start Qt or its business modules and exits the app.
System permissions for the microphone, notifications, screen recording, and accessibility services are requested only when the user uses the corresponding feature. The user can revoke these permissions in Android system settings.
Remote sessions and sensitive content
CoDesk establishes peer-to-peer remote sessions where possible and may use an encrypted relay when a direct connection cannot be made. Remote screen, input, clipboard, audio, and transferred-file content is transmitted for the session and is not used for advertising or profiling. CoDesk cloud infrastructure is not designed to decrypt end-to-end encrypted session content.
Some optional features store data you intentionally save, such as address books, SSH configuration, snippets, or support attachments. Where the product identifies content as zero-knowledge or client-side encrypted, encryption keys remain under the user's control.
Device permissions
CoDesk requests a device permission only when needed for a feature you initiate. You can revoke permissions in system settings, although the related feature will stop working.
- Android screen capture (MediaProjection) shares the screen only after the system confirmation dialog. A visible foreground-service notification is shown while sharing is active.
- Android Accessibility Service is used solely to translate an authorized remote user's mouse, keyboard, touch, and navigation commands into actions on the controlled device. It is not used to bypass privacy controls, collect data for advertising, or act without an active remote-control purpose.
- Android notification permission displays the persistent screen-sharing service notice and service-related alerts.
- iOS and iPadOS local-network access discovers and connects to devices on the same network. The iOS app does not request camera, photo-library, or microphone access for remote control.
- Desktop screen-recording, accessibility/input-control, and microphone permissions enable screen sharing, remote input, and audio respectively. They are controlled by the operating system and are used only for the selected functionality.
How and why we use information
We process information as needed to perform our contract, operate and secure the Services, comply with law, and, where required, based on consent.
- Create and authenticate accounts, connect authorized devices, route sessions, sync selected settings, and provide support.
- Administer trials, subscriptions, payments, invoices, usage limits, and service communications.
- Detect abuse, investigate incidents, enforce our Terms, prevent fraud, and maintain service reliability.
- Diagnose faults and improve performance and usability using aggregated or appropriately minimized data.
- Meet tax, accounting, legal, sanctions, and regulatory obligations and respond to valid legal requests.
When information is shared
We do not sell personal data or share it for cross-context behavioral advertising.
- Vendors that provide hosting, content delivery, email, customer support, security, analytics if enabled, and other infrastructure, under contractual confidentiality and data-protection duties.
- Payment processors, app stores, identity providers, and enterprise administrators when you choose those services or your organization manages your account.
- Authorities or other parties when reasonably necessary to comply with law, protect users and the Services, investigate abuse, or exercise legal rights.
- A successor in a merger, financing, reorganization, or sale of assets, subject to appropriate safeguards and notice where required.
Retention and deletion
We retain personal data only as long as needed for the purposes described here, including while an account is active and for reasonable periods needed for security, dispute resolution, backups, and legal compliance. Retention varies by data type and applicable law.
After a verified deletion request, we delete or anonymize account data unless retention is required for tax, accounting, fraud prevention, security, transaction records, or legal claims. Residual backup copies are isolated and expire through normal backup rotation. See the Account & Data Deletion page for request instructions.
International data transfers
CoDesk and its service providers may process information in countries other than yours. Where required, we use recognized transfer mechanisms and contractual, technical, and organizational safeguards. Self-hosted customers choose and control the hosting locations for their deployments.
Your privacy choices and rights
Depending on where you live, you may have rights to access, correct, export, delete, or restrict processing of personal data; object to certain processing; withdraw consent; and appeal a decision or complain to a regulator. You may export available account data in the console and submit other requests using the contact details below. We may verify your identity before acting on a request.
- Manage app permissions through your operating-system settings.
- Manage profile, security, and available data-export options in the CoDesk console.
- Use the Account & Data Deletion page to request deletion.
- Opt out of optional marketing using the unsubscribe link in the message or by contacting us.
Security
We use administrative, technical, and physical measures designed to protect data, including transport encryption, access controls, credential hashing, audit logging, rate limits, and encryption features. No system is completely secure, so protect your credentials, enable multi-factor authentication where available, and install updates promptly.
Children
The Services are intended for business and general audiences and are not directed to children under 16. We do not knowingly collect personal data from a child below the applicable age of digital consent without valid authorization. Contact us if you believe a child has provided data improperly.
Changes and contact
We may update this policy as the Services or law changes. We will revise the effective date and provide additional notice when a material change requires it. Privacy questions and rights requests may be sent to the contact address shown on this page.