Política de privacidad

1. Information we collect

We collect only what the product needs in order to work:

1. 1.Account information: your username, display name and account role. Passwords are stored salted and hashed; we cannot recover the plaintext.
2. 2.Device information: the device identifier generated by the client, the device name, device model, system version, the device's IP address on the local network, the group alias you assign, and its online status and last report time.
3. 3.Device status: battery level and charging state, free and total storage, thermal state, whether Low Power Mode is on, the client version, and whether WebDriverAgent on the device is responding. We use it to show device health in the console and, if you turn alerts on, to decide when to notify you.
4. 4.Script and task data: the script code you write or record, parameter settings, task schedules, execution status and execution logs.
5. 5.Synced assets: images, videos or other files you upload for distribution to devices.
6. 6.Alert settings: the addresses and credentials of the notification channels you configure when turning alerts on (such as a WeCom bot address, a Telegram bot token or a webhook address), your alert rules, and the record of alerts and deliveries.
7. 7.Script market details: the description, tags, author name and contact details (WeChat, QQ, Telegram — all optional) you enter when you choose to publish a script.
8. 8.Service logs: sign-in records, account activity records, and operational logs the server produces for security and troubleshooting.

A note on device names: iOS reports the name you gave the device in system settings, and such names sometimes contain a personal name (for example "Alex's iPhone"). If you would rather that not reach our service, rename the device in its system settings.

A note on execution logs: their content is determined by your script. Whatever the script writes through the logging interface is what we store. If your script logs sensitive values such as account names or verification codes, they will be uploaded with the log, so please write scripts with that in mind.

2. Device screen casting

1. 1.When you use casting, the device screen is streamed to the browser you are working in. There are two routes: on the peer-to-peer route the frames travel directly between device and browser without passing through our servers; on the relay route they are forwarded by our servers.
2. 2.The peer-to-peer route is only set up when the device and the browser are on the same local network: the two exchange their local network addresses through our servers and then connect directly, without any third-party relay or address-discovery service.
3. 3.On the relay route, frames are forwarded in real time for the duration of the connection only. We do not write them to disk or to a database, and we keep no recording.
4. 4.Once every viewer has switched to the peer-to-peer route, the server tells the device to stop relaying.
5. 5.A cast shows whatever is on the device screen at that moment. Please make sure it displays nothing you would not want seen before you start.

3. What we do not collect

To avoid any misunderstanding, we expressly do not collect the following:

1. 1.Location coordinates. The iOS client requests location permission for one purpose only: to keep the app running in the background so task heartbeats continue. We do not read, store or upload your coordinates or any location data. You may decline the permission; tasks still run normally in the foreground, and only the app's ability to stay alive in the background is limited by the system.
2. 2.The contents of your photo library. The client requests photo permission so that, as your script instructs, it can save files or downloaded images and videos to the library, count the files there, and delete all photos or videos in it (iOS shows a confirmation prompt first, which the script confirms; deleted items go to Recently Deleted). We do not read the contents of existing files or upload them to our servers.
3. 3.Screenshots and recognition results. Colour matching, image matching and text recognition capture and analyse the screen locally on the device: the screenshots are processed in memory and released immediately, never written to storage or uploaded; text recognition runs on the device with the iOS Vision framework and calls no online recognition service. The results stay inside your script unless the script itself writes them to a log or sends them somewhere.
4. 4.Clipboard contents. Scripts can read and write the device clipboard, and that content stays between the device and the script; it is never uploaded automatically, unless your own script writes it to a log or sends it somewhere.
5. 5.Contacts, messages, call history, microphone and camera. The client requests none of these permissions and has no ability to access them.

4. How we use information

1. 1.Delivering core features: authentication, device onboarding and online status, device health and alert notifications, dispatching and running tasks, returning results and logs, distributing assets, and screen casting.
2. 2.Keeping the service secure: detecting unusual sign-ins and call patterns, enforcing per-account device quotas and expiry, isolating data by tenant, and troubleshooting.
3. 3.Meeting legal obligations: retaining the records the law requires and responding to lawful requests from competent authorities.
4. 4.We do not use your information for automated decision-making, profiling, targeted advertising, or sale to third parties.

5. Sharing and disclosure

1. 1.The client integrates no third-party analytics, advertising or crash-reporting SDK, so no information flows to services of that kind.
2. 2.If your script calls network interfaces (such as httpGet or httpPost) to reach third-party services, your script sends that data to the address it names; we neither take part in it nor control it. Those third parties handle the data under their own privacy policies.
3. 3.If you turn on alerts and configure notification channels, alert messages (the device name or alias, device identifier, alert type, time and a short note such as how long it has been offline, the battery level or the failing script's name) are sent to the WeCom, Telegram or webhook addresses you specify. Those channels are run by their providers or by you, and the data is handled there under their own privacy policies.
4. 4.If you publish a script in the script market, the description, tags, author name and contact details you enter become visible to other users of the platform; the script's source code is not published. Leave out any contact details you do not want to make public.
5. 5.If you share a script with another account, the shared script's content becomes visible to the recipient. Do not keep credentials in a script you intend to share.
6. 6.We do not provide your personal information to third parties except where required by law, where you have given separate consent, or where it is necessary to protect someone's vital lawful interests. If information must transfer because of a merger, division or dissolution, we will tell you the recipient's name and contact details and require it to remain bound by this policy.

6. Self-hosted deployments

1. 1.CloudClick iOS can be deployed on servers you control. In that arrangement, all data — accounts, devices, scripts, tasks and logs — resides on your servers and we cannot access it.
2. 2.In a self-hosted deployment you, not we, are the personal information handler with respect to your end users. The corresponding duties of notice and consent, security, responding to rights requests and compliance rest with you.
3. 3.Whether traffic is encrypted depends on how you configure the deployment. We recommend enabling HTTPS and WSS and restricting network access to the service ports.

7. Storage location and retention

1. 1.With the hosted service, your information is stored on servers we operate inside the People's Republic of China. We do not transfer your personal information abroad; should that become necessary, we will obtain your separate consent and complete the required legal procedures first.
2. 2.Sign-in session tokens carry an expiry and are removed automatically once they lapse.
3. 3.Accounts, devices, scripts, tasks and execution logs are retained until you delete them or close your account, so that you can review past runs at any time. You can delete an individual script, task or device record whenever you wish.
4. 4.Beyond those periods we delete or anonymize your personal information, unless the law prescribes a different retention period.

8. Security

1. 1.We protect your information by storing passwords salted and hashed, limiting the lifetime of sign-in session tokens, issuing separate tokens for device onboarding, isolating data by tenant, and enforcing per-account device quotas and expiry.
2. 2.Despite the reasonable measures we take, no system on the internet is absolutely secure. Please safeguard your password and access keys and do not share them.
3. 3.If a breach, alteration or loss of personal information occurs, we will take remedial action promptly as the law requires and notify affected users and the competent authorities by appropriate means.

9. Your rights

Within the limits set by law, you may exercise the following rights:

• ·Access and copy: view your account details, device list, scripts, tasks and execution logs in the console; contact us if you need a copy.
• ·Correct and supplement: change your display name, device aliases, script content and parameter settings in the console.
• ·Delete: remove an individual script, task, device record or uploaded asset.
• ·Close your account: afterwards we delete or anonymize your information, except where the law requires it to be retained.
• ·Withdraw consent: turn off location, photo library and other permissions in the device's system settings at any time. Withdrawal does not affect processing already carried out on the basis of your earlier consent.
• ·Complain: if you disagree with how we handle information, contact us through section 12. You also have the right to complain to the cyberspace, market regulation or other competent authorities, or to bring proceedings.

1. 1.We will respond within fifteen working days of receiving your request. To verify your identity we may ask you for the information necessary to do so.

10. Minors

1. 1.CloudClick iOS is aimed at business and professional development use and is not offered to minors.
2. 2.If you are the guardian of a child under fourteen and find they have used our services without your consent, please contact us through section 12 and we will delete the information promptly.

11. Cookies and local storage

1. 1.The console uses browser local storage to keep your sign-in state, interface language and display preferences, so that you stay signed in and your settings persist.
2. 2.This marketing website is a static site and uses no third-party analytics or advertising cookies.
3. 3.You can clear local storage through your browser settings; you will need to sign in again afterwards.

12. Updates and contact

1. 1.We may update this policy as the law or our features change. For significant changes to the purpose, manner or scope of processing, we will give prominent notice and, where the law requires, obtain your consent again.
2. 2.An updated policy is published on this page and takes effect on publication.

If you have questions, comments or complaints about this policy or about how we handle personal information, contact us as below and we will respond within fifteen working days:

• ·Website: https://www.wtscript.com
• ·Email: support@wtscript.com