Skip to content
Intrelio

Intrelio privacy notice

Last updated: 9 November 2026

This is a translation of the Italian notice, provided for convenience. If the two versions differ, the Italian text prevails.

Intrelio is an application that enables communication and continuity between devices, between Android phones and macOS, Linux and Windows computers.

This notice describes how personal data is processed through the intrelio.com website, the Intrelio applications and the technical services they need to work.

Processing is carried out in compliance with the applicable personal data protection law, including the law of the Republic of Armenia and, where applicable, Regulation (EU) 2016/679 ("GDPR").

1. Data controller

The data controller is:

Nico Weide Zangirolami
Individual Entrepreneur registered in the Republic of Armenia
also operating under the trade name Zangi Cloud
State registration number: 286.1496165
TIN / Taxpayer Identification Number: 20020849
Address: 1 Yekmalyan St, 0002 Yerevan, Armenia

Contacts:

"Intrelio" and "Zangi Cloud" are trade names and are not legal entities separate from the controller named above.

2. In short

Intrelio is designed around the principle of data minimisation.

In particular:

  • you do not need to create an account to use the application on the local network;
  • no name, e-mail address or password is required to use Intrelio; signing in with a Google account is optional and serves only cloud access;
  • clipboard, notification, file and screen content is transmitted with end-to-end encryption;
  • the Intrelio relay does not hold the keys needed to read that content;
  • clipboard, notification, file and screen content is not stored on Intrelio servers;
  • we do not use behavioural analysis or profiling systems;
  • we do not use data for advertising;
  • the website does not use profiling cookies or analytics tools;
  • an e-mail address is processed only if you choose to join the waiting list, to sign in with your Google account or to contact us directly.

3. The intrelio.com website

3.1 Waiting list

If you join the waiting list we collect:

  • your e-mail address;
  • the language used on the website when you signed up;
  • the date and time of sign-up.

This data is used only to manage the waiting list and to tell you when Intrelio is publicly available.

Legal basis: consent of the data subject.

You can withdraw your consent at any time by writing to: privacy@intrelio.com

Withdrawal does not affect the lawfulness of processing carried out before it.

Waiting list data is deleted:

  • after the message about the public release of Intrelio has been sent; or
  • at the latest within 12 months of sign-up;

whichever comes first.

3.2 Website technical logs

The server hosting intrelio.com may automatically record technical information about the requests it receives, including:

  • IP address;
  • date and time of the request;
  • page or resource requested;
  • HTTP method;
  • user agent and browser information;
  • any error codes.

This data is used only for:

  • security of the service;
  • detecting malfunctions;
  • preventing abuse and attacks;
  • technical administration of the infrastructure.

Legal basis: the controller's legitimate interest in the security and proper operation of the service.

Logs are kept for a maximum of 14 days, unless part of them must be kept longer in connection with a specific security incident or a legal obligation.

3.3 Cookies and tracking

The intrelio.com website does not use profiling cookies, advertising systems or analytics tools.

No user profiles are created and no cross-site tracking takes place.

Should this change, this notice will be updated before the relevant tools are activated.

4. Intrelio applications

4.1 Data stored locally

The Intrelio applications may store on the user's devices:

  • cryptographic keys;
  • technical device identifiers;
  • information about paired devices;
  • configuration;
  • user preferences;
  • settings for notifications and authorised applications.

This information normally stays on the user's devices.

It can be deleted by unpairing the devices, clearing the application's data or uninstalling the application.

4.2 Anonymous technical identity

Intrelio does not require a personal account.

To make the remote services work, Firebase may generate a random, anonymous technical identifier for the installation.

This identifier requires no name, e-mail address or password and is used only to identify an Intrelio installation technically.

If you choose to sign in with Google, as described in section 4.7, your Google account is linked to this same identifier.

4.3 Clipboard

When clipboard sync is enabled, copied content may be transmitted between paired devices.

The content is protected by an authenticated connection and end-to-end encryption.

When the devices can communicate directly, for example on the same local network, the transfer takes place directly between them.

When the Intrelio relay is needed, the server forwards encrypted data only.

The relay does not hold the keys needed to decrypt the content.

Clipboard content:

  • is not used for analytics;
  • is not used for profiling;
  • is not written to application logs;
  • is not stored by the relay.

4.4 Android notifications

If you authorise Intrelio to access Android notifications, information such as the following may be transmitted to the paired computers and other phones:

  • application name;
  • notification title;
  • text;
  • any images or other supported content.

The feature is optional and must be explicitly enabled on the Android device.

Sync can also be limited to certain applications, and for each paired device you can choose whether to send notifications to it and whether to receive them from it.

Of the Android system's own notifications, only those that alert with a sound or a banner are forwarded, for example low battery; silent ones stay on the phone.

Notification content is transmitted with end-to-end encryption and is not stored by the Intrelio relay.

4.5 Camera

Intrelio may ask for camera access only to read the QR code used to pair devices.

Images captured while scanning the QR code are not sent to Intrelio servers and are not stored by the controller.

4.6 Shizuku

On Android, some background clipboard features may use Shizuku, if it is installed and authorised by the user.

Shizuku is used locally to grant the application certain operating system permissions or capabilities.

Intrelio does not require Shizuku for features that do not need it.

4.7 Cloud access and Google account

Using the Intrelio relay, that is connecting the devices when they are not on the same network, requires an entitlement. On the local network Intrelio works without one.

Pairing two devices is the exception: if they cannot reach each other directly, the pairing request goes through the relay even without an entitlement. The relay forwards only the few encrypted data of that exchange, for at most two and a half minutes, and cannot read them.

The entitlement is obtained in one of these ways:

  • buying the Intrelio Pro subscription from the Android application through Google Play, as described in section 4.8;
  • signing in from the Android application with a Google account the entitlement is associated with;
  • entering in the application a code received from the controller.

Signing in with Google is optional. If you do, Firebase Authentication receives from Google and keeps the basic account data needed to recognise you:

  • e-mail address;
  • Google account identifier;
  • name and profile picture, if the account has them.

We use the verified e-mail address only to establish whether an entitlement is associated with the account. We do not use it to send you messages.

You can unlink the account at any time from the application, with "Sign out": the installation becomes anonymous again. You can also ask us to delete the account data by writing to privacy@intrelio.com, as described at https://intrelio.com/en/account-deletion/

When you have signed in with the same Google account on several devices, the relay server keeps for the account, in a file named only by an irreversible digest of the account identifier:

  • for each device: its technical identifier, the name you gave it, its kind (phone or computer) and operating system, whether it is active and the day it was last used;
  • the technical invitation with which each active device lets the account's other devices pair with it, and its expiry;
  • the settings you chose to share between the account's devices;
  • for devices removed from the account, the technical identifier and the date of removal, so that they cannot be added again without a new sign-in.

You can remove a device from the account at any time from the application.

To manage entitlements the relay server keeps:

  • for each code: a non-reversible fingerprint of the code, a label chosen by the controller, the dates of creation and of expiry if any, its state and the technical identifier of the installation that redeemed it;
  • a list of e-mail addresses to which the controller granted the entitlement without purchase, with, for each, whether it may mirror the screen through the relay.

This data is kept for as long as the entitlement is valid and deleted when it is revoked.

Legal basis: performance of the service requested by the user.

4.8 Intrelio Pro subscription

The Intrelio Pro subscription is bought from the Android application through Google Play. The payment is handled entirely by Google: we neither receive nor keep your card or payment method data, your name, your address or the order number.

At the time of purchase the application gives Google Play a non-reversible fingerprint of the installation's technical identifier, so that the purchase can be traced back to your installation without revealing the identifier itself to Google.

After the purchase, and every time you restore your purchases, the application sends the Intrelio server the purchase token issued by Google Play. The server asks Google for the state of the purchase and keeps:

  • the purchase token, needed to ask Google again for the state of the subscription;
  • the product and the plan chosen, monthly or yearly, and the offer applied, if any;
  • the state of the subscription, its expiry date and whether automatic renewal is on;
  • the technical identifier of the installation that reported the purchase and the fingerprint given to Google Play.

Google Play also informs us of renewals, cancellations, payment problems and refunds through notifications that contain the purchase token. We use them only to update the state of the subscription.

These data are kept for the duration of the subscription and deleted 12 months after it ends.

You can manage or cancel the subscription at any time on Google Play.

Legal basis: performance of the contract with the user.

4.9 Files and shared folders

You can send files and folders from one device to another paired device. The file travels with end-to-end encryption, directly between the devices when possible and otherwise through the relay, which forwards only encrypted data and does not store it.

You can also choose to share some folders with your paired devices, which can then browse them and copy their files. Sharing is off until you enable it, covers only the folders you choose, and for each device you can decide whether it may browse them and whether it may send you files.

On Android, Intrelio's file manager may ask for the all files access permission, to show and copy the files in the phone's storage like an ordinary file manager. The permission is optional and is used only on the device, for the operations you request.

File names and content are not sent to the controller, are not written to logs and are not stored by the relay. Temporary copies made to open a received file are deleted from the device.

4.10 Screen mirroring and device control

Intrelio lets you see the screen of one of your paired devices and, if you allow it, use its keyboard, mouse or touch from another of your devices, for example the phone's screen on the computer, or a computer's screen on another computer or on the phone.

A computer can be seen and controlled only if you enable it in its settings. At every request the computer asks for permission, unless you chose to always allow it or never allow it for that device, and while it is controlled it shows by which device, with the command to stop.

Screen images and commands travel with end-to-end encryption between your devices, are not recorded and are not stored by the relay.

On macOS, screen capture requires the screen recording permission granted by the user in the system settings.

5. Communication between devices outside the local network

When devices cannot communicate directly, technical services are used so that they can find each other and establish communication.

5.1 Firebase

Intrelio uses Google's Firebase services, in particular for:

  • anonymous technical authentication;
  • optional linking of a Google account to the installation, as described in section 4.7;
  • temporary association of the endpoints through which devices can be reached.

The information published for rendezvous is encrypted.

Temporary endpoints expire automatically after about 90 seconds.

Google necessarily receives some technical information during the connection, including the IP address.

The database used for rendezvous is configured in a European Union region.

Other technical data needed for Firebase to work may be processed in Google's infrastructure under the terms applicable to Firebase and Google Cloud services.

5.3 Direct connection between devices

When the devices are not on the same network, Intrelio tries to connect them directly over the Internet, without the data passing through the relay. Until the direct connection is ready, and if it fails, data passes through the relay as described in section 5.2.

To find a direct path:

  • each device asks the relay's STUN service (api.intrelio.com) which public IP address and port the Internet sees it with; the service replies and does not store the request;
  • the devices exchange these addresses through the end-to-end encrypted channel, which the relay cannot read;
  • the device may ask the router of its own network, with the UPnP, NAT-PMP or PCP protocols, to open a port temporarily for the connection.

In a direct connection each of your devices learns the other's public IP address. The content stays end-to-end encrypted.

5.2 Intrelio relay

When a direct connection between devices is not possible, Intrelio may use the relay: api.intrelio.com

The relay's only function is to forward encrypted traffic between devices that are paired or being paired.

During a connection the server can technically know:

  • the IP addresses of the connected devices;
  • the time and duration of the connection;
  • the amount of data transferred;
  • the technical identifier of the installation and, if you signed in with Google, the account's verified e-mail address, used when connecting to check the entitlement;
  • technical information needed for the connection to work.

The relay cannot read clipboard, notification, file or screen content because that data is end-to-end encrypted.

The relay application does not persistently store:

  • forwarded content;
  • clipboard content;
  • notifications;
  • the IP addresses used for connections;
  • the e-mail address presented when connecting, unless it is on the list described in section 4.7.

To monitor its operation and load, the relay computes aggregate statistics, such as the number of open connections and channels, the total amount of data forwarded, STUN requests and refused connections. The statistics contain no IP addresses, identifiers, e-mail addresses or content, stay on the controller's server and are kept for 30 days.

Network systems and the infrastructure provider may nevertheless temporarily process technical data strictly necessary to provide, secure and protect the infrastructure.

Legal basis: performance of the service requested by the user and, for infrastructure security, the controller's legitimate interest.

6. Diagnostics and analytics

The Intrelio applications do not send the controller:

  • app usage statistics;
  • activity history;
  • clipboard content;
  • notification content;
  • data used for commercial profiling.

No analytics or advertising systems are active inside the applications.

The applications do not automatically send crash reports to the controller.

7. Support and correspondence

When you contact us at support@intrelio.com or privacy@intrelio.com we may process:

  • your e-mail address;
  • your name, if given;
  • the content of the message;
  • any attachments;
  • technical information you choose to share with us.

We use this data only to answer the request, provide support, handle privacy requests or protect our rights.

Legal basis: steps taken at the data subject's request, performance of the service, legitimate interest and, where applicable, compliance with legal obligations.

Correspondence is kept for as long as needed to handle the request and afterwards only as far as needed for administrative, security or legal protection purposes.

8. Providers and recipients

We do not sell, rent or transfer personal data for advertising purposes.

To provide Intrelio we use some technical providers that may process data on our behalf or within their own infrastructure.

ZAP-Hosting GmbH

The intrelio.com website, the APIs and the Intrelio relay use infrastructure provided by:

ZAP-Hosting GmbH
Hafenweg 8
48155 Münster
Germany

ZAP-Hosting may process technical data needed to provide, manage and protect the server infrastructure.

Google / Firebase

Intrelio uses Firebase services provided by Google and, if you choose to sign in with your account, Google's sign-in service.

If you buy the Intrelio Pro subscription, the purchase and the payment take place through Google Play, which processes the related data as an independent controller under its own privacy notice. Notifications about the state of the subscription reach us through Google Cloud.

For customers in the EMEA area, Google Cloud services may be provided by the relevant Google contracting entity in the European Union, including Google Cloud EMEA Limited, Ireland, depending on the service and the applicable contract.

Google may also use companies of its group and sub-processors located in other countries.

When personal data is transferred to countries without an applicable adequacy decision, Google uses the transfer mechanisms provided by the applicable law, including, where relevant, standard contractual clauses.

9. International transfers

The controller is established in the Republic of Armenia.

Some providers used by Intrelio are established or have infrastructure in the European Union, while others may use infrastructure or sub-processors in third countries.

When the GDPR applies and an international transfer requires specific safeguards, the mechanisms provided by the applicable law are used.

10. Data retention

The main retention periods are:

  • waiting list: until public release and in any case no longer than 12 months from sign-up;
  • website logs: 14 days at most, except for security incidents;
  • temporary Firebase endpoints: about 90 seconds;
  • content forwarded by the relay: not stored;
  • IP addresses of relay connections: not stored by the relay application;
  • local device data: until unpairing, data clearing or uninstallation;
  • linked Google account: until you unlink it or ask for its deletion;
  • account devices and settings: as long as the device stays in the account, or until you ask for the account data to be deleted;
  • aggregate relay statistics: 30 days;
  • requests to the STUN service: not stored;
  • codes and addresses holding an entitlement: until the entitlement is revoked;
  • Intrelio Pro subscription data: for the duration of the subscription and for 12 months after it ends;
  • support and privacy requests: for as long as needed to handle the request and for any later administrative or legal needs.

11. Security

Intrelio adopts technical measures intended to reduce the amount of personal data accessible to the controller.

These include:

  • end-to-end encryption of transmitted content;
  • authentication of paired devices;
  • keys stored on the devices;
  • minimisation of data stored on the server;
  • automatic expiry of temporary rendezvous data;
  • no server-side storage of synced content;
  • encrypted connections to backend services.

No computer system can, however, guarantee absolute security.

12. Rights of the data subject

In the cases provided by the applicable law you can request:

  • access to your personal data;
  • rectification of inaccurate data;
  • erasure;
  • restriction of processing;
  • objection to processing;
  • data portability;
  • withdrawal of consent previously given.

Requests can be sent to: privacy@intrelio.com

When processing is based on consent, its withdrawal does not affect the lawfulness of processing carried out before the withdrawal.

Because Intrelio does not require personal accounts and many technical identifiers are not directly linked to the user's identity, we may be technically unable to locate certain data without further information from the data subject.

In particular, data stored only on the device can be deleted directly by unpairing the devices, clearing the application's data or uninstalling Intrelio.

Complaints

You can lodge a complaint with the competent personal data protection authority.

For processing subject to Armenian law, the competent authority is the Personal Data Protection Agency of the Ministry of Justice of the Republic of Armenia.

When the GDPR applies, you can also lodge a complaint with a competent supervisory authority in the European Union, in particular in the Member State of your habitual residence, your place of work or the place of the alleged infringement.

13. Automated decisions and profiling

Intrelio makes no automated decisions that produce legal effects on the user and does not profile users for commercial or advertising purposes.

14. Minors

Intrelio is not intended for people under 16.

We do not knowingly collect personal data of minors under 16 through the waiting list.

If we become aware of data collected in breach of this provision, we will delete it where technically possible.

15. Changes to this notice

This notice may be updated as a result of:

  • changes to Intrelio's features;
  • the introduction of new services;
  • infrastructure changes;
  • changes in the law.

The updated version will be published on intrelio.com with the new update date.

In the event of substantial changes, further appropriate means may be used to inform users where necessary.

© 2026 Intrelio · Privacy noticeThis site uses no cookies and no tracking tools.