Cool Maze privacy terms

These terms apply since March, 2024.

These terms may evolve. In case this happens, the new terms will apply to data transferred after the new terms have been published. The new terms won't revoke protections granted to previously transferred data.

Cool Maze (the Service) is an online system to transfer data from a source device A to a target device B.

The User must be in control of the source device A, of the browser of the target device B, and of the data D to be transferred from A to B.

The Service is provided free of charge for the User.

The Service is provided without any guarantee, except the best-effort policy to respect the privacy of the personal data of its Users.

The Service doesn't use and doesn't store the identity of its Users.

The Service doesn't correlate its usage with Users' internet browsing data, nor with other apps usage.

The only personal data involved is the payload D that the User explicitly requests to transit by the Service, using a "Share via ... Cool Maze" action.

The data D sent from A to B is routed through intermediary servers: the Brokers and the File server.

All data transfers are protected by the HTTPS protocol:

The transferred data D is kept private and is never made publicly available.

The transferred data D is not disclosed to third parties.

The transferred files are provided to the target B through short-lived URLs to encrypted resources. The User may save the decrypted transferred files to the storage of target device B.

The Service uses cloud computing infrastructure providers. The facilities are Google App Engine, Google Cloud Storage, and Google Cloud Firestore.

Cool Maze for Android uses end-to-end encryption (E2EE) since its version 1.1.1909. This means that the service owner and the cloud infrastructure vendors can't read the data D transiting through the Service.

Cool Maze for iOS uses end-to-end encryption (E2EE) since its version 1.2.1.

Anonymous data may be gathered for statistics purpose. This data includes, and is not limited to:

Data sent from the mobile to the server, necessary for proper message delivery:
actionid
The unique ID of the current "Share" action
qrKey
The unique ID of the ephemeral communication channel of the current "Share" action
crypto
The encryption scheme used by the current "Share" action to achieve E2EE
cryptoiv
The Initialization vector (IV) used by the current encryption scheme of the current "Share" action to achieve E2EE
mobilesecretscrambled
Cryptographic key
multiCount
Number of resources being shared by the current "Share" action
multiIndex
Index (zero-based) of the resource being shared
message
Text message being shared or URL to the resource being shared. This field is end-to-end encrypted (E2EE).
filename
Filename of the resource being shared. This field is end-to-end encrypted (E2EE).
thumb
Thumbnail of the resource being shared. This field is end-to-end encrypted (E2EE).
resized
Whether the shared resource was resized by the Cool Maze mobile app
width
The width of the shared resource (after optional resizing)
height
The height of the shared resource (after optional resizing)
bup
Number of resource bytes already sent, when the QR-code is scanned
gcsObjectName
File server path to the data being shared
user-agent
The Cool-Maze mobile app User Agent contains: App name, App version, App build number, plus 3 fields for service quality monitoring
Data sent from the mobile to the server for service quality monitoring:
connection
Mobile connexion type: wifi, or mobile data
type
MIME type of the resource being shared
ext
File extension of the resource being shared
nth
Number of "Share" actions made by the current mobile app instance (since installation)
dark
Whether Cool Maze is displayed in Dark Mode
ttrz
Time to resize the resource on the mobile to reduce it, in milliseconds
ttmultrz
Time to resize all the resources of a multiple share action on the mobile, in milliseconds
origsize
Size of the original resource in bytes, before resizing
tte
Time to encrypt the resource on the mobile before uploading, in milliseconds
ttup
Time to upload the single resource from the mobile to the cloud File server, in milliseconds
ttmultup
Time to upload all the resources of a multiple share action from the mobile to the cloud File server, in milliseconds
ttscan
Time between the start of the "Share" action and the QR-code scan, in milliseconds
malg
Mobile display language
muloc
Mobile user locale
sample
When the sample picture is being shared
filenameUnknown
When the mobile app could not determine the original filename of the resource being shared
user-agent
The Cool-Maze mobile app User Agent contains: App installation ID, mobile OS, mobile model, plus 3 necessary App fields
sharer
The app that iniatiated the share intent
ttrtcx
Duration of WebRTC SDP exchange on the Mobile side, in milliseconds
Data sent from the target web browser to the server for service quality monitoring:
ttf
Time to fetch (download) the resource from the cloud File server, in milliseconds
ttpf
Time to prefetch (download before scan) the encrypted resource from the cloud File server, in milliseconds
ttd
Time to decrypt the resource on the target web browser, in milliseconds
qrttnotif
Time between the generation of the QR-code and a scan notification for a single resource received by the web browser, in milliseconds
qrttcast
Time between the generation of the QR-code and a notification of (single or multiple) resource ready received by the web browser, in milliseconds
ctn
Short-lived cookie (36h) used for prefetch performance optimization
ttrtcx
Duration of WebRTC SDP exchange on the browser side, in milliseconds

Acknowlegements

We thank

Copyright

©2017-2024 Bartalog Software

Contact

bartalogsoftware@gmail.com