Privacy policy
This page describes which information about you or this computer the service handles, and what that information is used for.
This translation is provided for convenience only. The Chinese version of this page prevails.
What we process
- When the service is bound to a computer, we store a hash computed from hardware information. The raw hardware identifiers are not stored. At activation it also sends the client version and whether this computer appears to be a virtual machine. We record the client version last reported, and which version of the user agreement you accepted and when.
- With “Send crash reports and attach logs when I report a problem” on, the client reports a summary of this computer once: system version, manufacturer and model, processor and number of logical processors, number of disks, and whether it appears to be a virtual machine and why. This does not include disk serial numbers or your name. If the same computer hash sends a summary again, we compare the manufacturer, model, processor and number of logical processors with the first report, to notice one hash being used on other hardware (a shared activation code, for example). The later report is used only for that comparison and isn't stored; all we keep is how many times it differed and when it last did. A difference is only a hint, since changing a processor or mainboard looks the same: nothing is disabled, limited or signed out automatically, and a person decides.
- With that setting on, when the program hits an unhandled error, it reports the error message and call stack. The stack may contain paths on this computer. Within one run, the same error is reported only once.
- What you choose to write under Help & feedback in the client or on the site's Messages page, and the email address you may add (used only to tell you there's a reply). The Messages page keeps a message token in your browser so you can see replies; it is not used for tracking. A message or an "I have paid" claim sent from the client also carries this computer's hash (even before activation) and, once activated, the license ID, so that we can match it to this computer.
- Images you upload under Help & feedback in the client or on the site's Messages page (screenshots, for example). Only common image formats are accepted, and files that are not real images or are too large are refused. The server saves each image again, removing metadata such as when and where it was taken. Uploads use a fixed file name, so your file's name does not reach the server. Images are used only to handle that message, and only we and whoever holds that message's token can see them. Screenshots may show personal information such as account numbers or positions, so before uploading, cover what we do not need to see.
- If you turned on “Send crash reports and attach logs when I report a problem” in Settings, “Attach the recent log” is on when you write under Help & feedback in the client (you can turn it off). While it is on, the last part of the run log (up to about 64 KB) is uploaded with your message to help find the problem. The user folder, user name, computer name and email addresses are removed before upload. If you did not turn that setting on, or once you turn it off under Settings → Privacy, no log is attached.
- Emails you send to support@
tickdatadownload.com , including your email address, the message and its attachments, used only to deal with what you raise in them and to reply to you. If you tell us by email that you have paid, we may note your email address on that order when we log the payment, so that we can send you the activation code. - When you send I have paid on the client's License page, we store the plan, amount and payment method you chose, the last digits of the transaction number (or the payer nickname and payment time) you entered, and any payer nickname or payment note you entered, to match the payment and issue your activation code. For a claim sent from client version 1.2.9, we also store the time you ticked the refund confirmation that version showed. A payment screenshot you attach is handled like the images above. We record the same details when we log the payment.
- When the License page offers Pay with crypto and you pay in USDT or USDC, we store the network, coin and amount you chose, and the transaction hash and paying address of the transfer that arrived (both are public on the blockchain anyway), to confirm the payment and issue your activation code; for an order placed from client version 1.2.9, the time you ticked the refund confirmation that version showed is stored here too. When a transfer cannot be matched to an order (for example a wrong amount or coin, a transfer that arrives after the order has lapsed, or an order paid twice), we also store that transfer's network, coin, amount, transaction hash, paying address and time, and our record of how we handled it (an activation code issued afterwards or the money sent back), to check it and then issue the activation code or refund; these are payment records, kept for the period the law requires.
- Activation codes, and the market, symbols, date range and transfer volume of each preparation job, to confirm your plan and troubleshoot.
- IP addresses in the server's access logs, used to limit abnormal traffic. The IP address of a connection is also used to choose a download route and to tell whether it comes from mainland China, which decides whether crypto payment is shown; that result is not stored. To spot an activation code shared between computers, we also count per day how many networks a code connects from, including the network used when the same computer signs in again with its code: only the number can be read back, never a network address. We also keep a per-day count of how many times a code signed in again, with no address. When a code goes over 3 networks in one day, its license number goes on that day's list, with no network or address; monitoring raises an alert without the number and keeps only a running total without the number. These daily records are cleared after two days. They are only a hint: nothing is disabled, limited or signed out automatically, and a person decides.
- When you click Try free for 7 days in the client, the client sends this computer's hash to the server before activation, and we keep it with the trial code issued, so that each computer gets one code. Whichever way a trial code was obtained, once it is activated we record that this computer has had its free trial (the computer's hash, the trial license's ID and the time), so that each computer has one trial.
- When you get a trial code on the site's Messages page, we keep a hash worked out from your network address (not the address itself), so that each network gets one code, and a hash worked out from a random number your browser makes (not the number itself), so that the code is shown again only to the browser that got it. Both are kept for 365 days and then deleted automatically.
- To spot automated fetching and shared activation codes, we record the time, symbols, amount and frequency of each code's download requests, and work out patterns per computer (for example, downloads that start at the same time for many days in a row, or many symbols in a short time). These records are only a hint and a person judges them: no download is refused because of them, and they alone never disable a license or sign it out. When downloads go over the cap (200 GB in any 30 days for a paid code, 30 GB for a trial code), the server refuses the download requests beyond it.
- When you open the website, the page sends the server the address of the current page, the name of the site you came from (the name only) and whether you clicked download, so we can count daily visitors and downloads. This count uses no cookies and keeps nothing on your device. To count people once, it uses the IP address and browser details: only the number can be read back, never an address, and the data is cleared after two days. The number of people is also totalled by region (mainland China or elsewhere) and device type (phone or computer), as totals only. The client checks for a new version each time it starts and every 6 hours while it runs (it also checks before activation and before you accept the user agreement), and each check sends the client version and the update channel in use. The number of clients, their versions and their update channels are counted per day from these checks in the same way.
What stays on your computer
The run log is written on your computer and isn't uploaded with the prepared data; only when you write to us and choose to attach the log is the last part described above uploaded. The download and export folders stay on your computer, in your own keeping.
For a crypto order, the client keeps the order number, the redeem token, the payment page link, the amount and the code it fetched on this computer, and deletes them once the code is activated on this computer (or when the order lapsed long ago and was never paid). The payment page keeps the redeem token in your browser to show the code, until you clear this site's data from your browser.
When you get a trial code on the site's Messages page, the page keeps the random number mentioned above in your browser, and once you have the code, the code as well, to show it again when you open the page; they stay until you clear this site's data from your browser.
If you choose not to see the website's language hint again, a marker is kept in your browser, only so that the hint stays hidden.
What we don't process
We don't collect bank card numbers or contacts, and we don't read files unrelated to the service. We don't sell personal information.
Where it is stored
- Servers: the API, the database and the server logs run on Alibaba Cloud servers in Hong Kong, China; the information listed above is stored and processed there. Database backups are also kept on that server and copied to our private storage on Alibaba Cloud Object Storage (OSS). Images on messages are also stored on that server.
- Data files: the encrypted market data files are stored on Alibaba Cloud OSS and Cloudflare R2, and the client connects to them directly to download (see Transfer below). These files are the same for every user and hold no personal information about you.
- Email reminders: when we send you a reply reminder, the email address you gave is passed to the email delivery service we use, only to send that reminder.
- Email: the emails you send us and our replies are kept in the Alibaba Cloud enterprise email service we use, not on the servers above (except an email address we note on an order when we log a payment).
Hong Kong, China is outside the Chinese mainland. When you use the service from mainland China, your information is transferred to the servers in Hong Kong, China, and stored and processed there, which is a transfer of personal information outside the mainland. With the download route on Automatic, clients from version 1.2.9 on usually connect first to Cloudflare R2, outside the mainland, even when you download from mainland China; Cloudflare sees your IP address and which encrypted files you download, which is also a transfer of personal information outside the mainland. If you choose the Mainland China route under Settings → Advanced options → Download route in the client, downloads use Alibaba Cloud OSS first and move to Cloudflare R2 only when that route keeps failing; if you choose Outside mainland China, downloads use Cloudflare R2 first and use Alibaba Cloud OSS only when that route keeps failing or a day's file is not yet on Cloudflare R2. The storage space on Alibaba Cloud OSS is currently also in Hong Kong, China, so choosing Mainland China does not mean this information stays inside the mainland. By ticking the box in the client that accepts the user agreement, you agree to these transfers; if you do not agree, do not activate or use the service.
Before you send a message from the website's Messages page, you tick a box to agree that the message, the optional email address and any images you upload are transferred to the servers in Hong Kong, China, and stored and processed there; if you do not agree, do not send messages from the website.
How long we keep it
- Error reports are kept for 90 days and the computer summary for 365 days, then deleted automatically. The 365 days run from the first report and do not restart with a later one; the count of differences and its time are deleted with the summary.
- Images on messages are kept for 180 days from the thread's last message, then deleted automatically.
- Download patterns worked out per computer are kept for 90 days after they stop matching, then deleted automatically.
- The record of a trial code requested from the client (this computer's hash and the code issued) and the record that this computer has had its free trial are not deleted automatically. When you ask us to delete, the first is deleted and the second is kept; see Delete below.
- The per-day network counts, sign-in counts and each day's list are cleared after two days.
- Server logs (including the IP addresses in the access logs) rotate by size: each service keeps at most about 30 MB, and once that is full the oldest entries are overwritten by new ones.
- The daily numbers of visitors, page views, downloads and clients are totals with nothing in them that could identify anyone, and are kept indefinitely.
- Messages and replies (including attached logs), the optional email address, payment claims, and license and download records (market, symbols, date range, transfer volume and request time) are not deleted automatically at present: they are kept until you ask us to delete them, and if we stop providing the service, we delete them within 30 days after it stops.
- Emails you send us and our replies are kept, like messages, until you ask us to delete them.
- Payment records are also kept for as long as the law requires; within that period they are kept even if you ask us to delete them.
- After a record is deleted, its copies in the database backups are cleared within about 30 days as the backups rotate.
Your rights
For the information we keep about you or this computer, you can:
- Access and copy: we tell you which records we keep and, if you want, give you a copy in our reply.
- Correct: if a record is wrong, such as the plan or amount in a payment claim, tell us what is right and we will correct it.
- Delete: we delete the messages and replies sent from this computer or about its licenses (including the optional email address, attached logs and images), its download records, download patterns, computer summary and error reports, and the record of a trial code requested from the client (a trial code received but not activated stops working). Every license on this computer is stopped, and its record loses this computer's hash, the client version, the last connection time and the record of accepting the user agreement, keeping only the plan, symbols, start and end times, download count and activation code; after that, this computer can no longer use those codes. Also kept: payment claims we have registered and orders are payment records, kept for the period the law requires, with this computer's hash, the email address and the log removed from the claims, the email address removed from the orders, and the same email address removed from the notes we keep on these activation codes; transfers that matched no order (see above) are payment records too and are kept as well; and if this computer has had its free trial, its hash, the trial license's ID and the time are kept, only so that it cannot get another free trial. Messages from the site's Messages page carry no computer hash: ask in that message, and we delete the whole thread, including replies, the email address and images.
- Withdraw consent: turn off “Send crash reports and attach logs when I report a problem” under Settings → Privacy, and no more errors or computer summary are reported, and no log is attached to your messages. One code per computer needs this computer's hash: withdrawing consent for it means you stop using your license, and once the hash is deleted this computer can no longer use that activation code. Withdrawing does not affect processing that took place before.
Make any of these requests on the site's Messages page or under Help & feedback in the client, and we reply in the thread; or email them to support@
Transfer
The client talks to the server and to the storage services over encrypted connections. Keep your activation code to yourself and don't send it to anyone else.
The client downloads data files directly from a storage service: with the download route on Automatic, it usually connects to Cloudflare R2 first and uses Alibaba Cloud OSS when R2 cannot be reached, is too slow, or would mean a long wait while OSS is clearly faster; it uses OSS for any day whose file is not yet on Cloudflare R2, and it may also connect briefly to the other route to compare speeds. Clients up to version 1.2.8 usually choose by where you connect from: OSS from mainland China, and Cloudflare R2 from elsewhere; when the server's route settings are adjusted, version 1.2.8 may also connect to Cloudflare R2 first. The storage provider sees your IP address and which encrypted files you download, so that the files can be delivered to you, but cannot read them.
When you download the client installer from the website or update inside the client, the file also comes directly from a storage service: Alibaba Cloud Object Storage Service (OSS) when you connect from an address in mainland China, and usually Cloudflare R2 from anywhere else. The storage provider sees your IP address in order to deliver the file to you.