Privacy Notice
The personal data we handle when you buy, activate and update Kauriq.
| Last updated | November 19, 2026 |
| Controller | Le Van Ninh (trading as “Ninhle”), Ho Chi Minh City, Vietnam |
| Contact | hi@ninhle.com |
This notice is published alongside the Kauriq End-User License Agreement (LICENSE.md).
This notice covers the personal data we handle when you buy Kauriq, activate it and receive updates. It does not cover the Merchant of Record (the platform named on the sales page that sells the licence and processes your payment) or GitHub, which have their own privacy policies.
1. Who we are
Le Van Ninh, an individual seller in Ho Chi Minh City, Vietnam, trading as Ninhle (the Licensor in the End-User License Agreement). Contact: hi@ninhle.com.
2. The software collects nothing
Kauriq runs on your own computer or server. It sends no data to us: there is no telemetry, no usage reporting and no licence server. Your exchange API keys are encrypted on your machine and never leave it. Optional alerts go only to the Telegram bot you set up yourself.
3. Your purchase through the Merchant of Record
The Merchant of Record sells the licence and processes your payment under its own privacy policy. We never receive your card or bank details.
Our administration tool uses only the following from the Merchant of Record, read-only, through its API or the notifications it sends us:
- the order or membership id;
- the edition you bought;
- the order status, start date and expiry date;
- for refunds and chargebacks, the refund and payment status.
The Merchant of Record’s API and notifications also contain other data, for example your email address. Our tool discards it and never writes it to disk.
4. Your activation email
To activate, you email activate@ninhle.com with:
- the license key, or the order or membership number, you received from the Merchant of Record;
- your GitHub username;
- your country of residence;
- the confirmations listed in the activation instructions.
Like any email, it also gives us your email address and the message headers.
An automated tool of ours reads activation emails, makes the checks below and answers you with a fixed message. When it cannot decide (for example a refund for an excluded country), a person handles your email.
We use this to check your licence with the Merchant of Record, check that the edition is offered where you live, give your GitHub account access to your private repository, and keep a record that you made the confirmations.
5. What we keep, where, and for how long
| Data | Where | Why | How long |
|---|---|---|---|
| Your activation and support emails (address, content) | Our activation mailbox (activate@ninhle.com) and support mailbox (hi@ninhle.com), held by our email hosting provider | To answer you, and as evidence of your confirmations if a refund or chargeback is disputed | Until 12 months after your licence period ends, then deleted |
| Buyer record: a random buyer id, the order or membership id at the Merchant of Record, edition, licence period, GitHub username, and, if access ended, the reason (expired, refund, chargeback, other) | The seller’s own computer, with an encrypted backup | To deliver updates, remove access when the licence ends, and trace leaked copies | Until 3 years after your licence period ends |
| Confirmation record: time, buyer id, order or membership id, the country you stated, the licence version you accepted | The same place | To show that you confirmed you may use the edition | The same as the buyer record |
| Activation robot record: a hash of each email’s message id and of the sender’s address, the outcome, and the buyer id | The seller’s own computer | To avoid handling an email twice and to limit automatic replies | 24 months |
| Run logs of the administration tool: order or membership id, edition, status, GitHub username, the country and licence version you stated, the last 4 characters of your license key, and what the tool decided (including a refused activation) | The same place | To check what the tool did and when | 24 months |
We do not store:
- your license key (it is checked once with the Merchant of Record; logs keep only its last 4 characters);
- your name, phone number or postal address;
- your email address anywhere outside the activation and support mailboxes.
6. GitHub and your copy of the software
We give your GitHub account read access to a private repository created for you. To do this we share your GitHub username with GitHub. GitHub then processes it under its own privacy statement. The repository is named after your random buyer id, not after you.
Each copy we deliver carries a watermark derived from your buyer id. The watermark contains no personal data itself. With our buyer record, however, it can link a leaked copy back to your purchase. This is why we keep the buyer record after your licence period ends.
Access is removed when the licence ends (expiry, refund or chargeback). Our tool learns of this from the Merchant of Record’s notifications or its periodic check, which runs at least once a day, so removal can take up to about a day. It is not instant.
7. What we do not do
- We do not sell, rent or share your data, except as described here with the Merchant of Record and GitHub.
- We use your email address only for your activation, your support requests and notices about your licence (for example a security update). We do not send marketing unless you separately agree to it.
- We do not track you or use your data for advertising.
8. Your rights
You can ask us at hi@ninhle.com to:
- see the data we hold about you;
- correct it, for example to move access to a new GitHub username (we verify the request first);
- delete it.
If you ask for deletion while your licence is active, your repository access ends. We may keep the minimum needed to handle a refund or chargeback dispute, or to trace a leaked copy, for the periods in Section 5.
We will answer within 30 days.
9. Changes
If this notice changes, we will publish the new version with its date. If the change affects data we already hold, we will also email you.
Frequently asked questions
Does Kauriq collect data from my computer?
No. Kauriq runs on your own computer or server with no telemetry, no usage reporting and no licence server. Exchange API keys are encrypted and never leave your machine.
What data is kept when I activate Kauriq?
Activation and support emails are kept for up to 12 months after the licence ends. Buyer and confirmation records are kept for up to 3 years; robot records and tool logs for 24 months. Licence keys are not stored, only the last 4 characters in logs.
Why are buyer records kept after the licence ends?
Every copy carries a watermark tied to a buyer ID. Together with the buyer record, the watermark helps trace the source of a leaked copy.
Can I ask for my data to be deleted?
Yes, by emailing hi@ninhle.com. If your licence is still active, repository access will end, and a minimal set of data may be kept to handle refund disputes or trace leaks.
How long does it take to remove GitHub access when a licence ends?
It can take about a day, because the tool checks at least once a day. Removal is not instant.
