1. Scope
This policy covers pay2clone.com — this website, the public demo hosted on it, and purchases made through it.
It does not cover deployments of pay2clone run by other people. When you buy software from a seller who runs their own pay2clone deployment, that seller is the controller of your data and their policy applies, not this one. We have no access to their deployment, their database, or their buyers.
2. What this website collects
The marketing pages are static files. They set no cookies, embed no third-party scripts, and load no fonts, images, or analytics from other domains.
Our host, Cloudflare, processes ordinary request metadata — IP address, user agent, requested path, timestamp — to serve and protect the site. We do not build profiles from it and we do not use it for advertising.
3. The public demo
The demo is a real, working deployment. Using it means real data is written:
- the GitHub account you sign in with, and the invitation it receives;
- a test-mode payment record, made with a published test card;
- the events, orders and entitlements those actions produce.
All demo data is erased every hour, on the hour. The database is wiped whole; nothing is archived and nothing is carried across a reset. Repository access granted during a demo session is withdrawn by the same reset, so an invitation lasts at most one hour.
Do not put anything into the demo that you would not want erased, and do not use it with an account you cannot afford to have publicly visible as a collaborator on a throwaway repository for up to an hour.
Payments in the demo are test mode only. No real card is charged and no real card number reaches us.
4. Buying a license
When you buy a license, the payment provider processes your payment and sends us a webhook describing it. From that we store your order, your email address, and the GitHub account you connect in order to receive repository access.
We never receive your card details. They are handled by the payment provider under its own policy and never touch our systems.
We keep order records for as long as the law requires us to keep accounting records, and for as long as we need them to prove what you are entitled to.
5. GitHub
To grant repository access we ask GitHub for your account identity and act on your behalf to add or remove you as a collaborator. We request the narrowest permissions that allow this, and we do not read the contents of your repositories.
6. Cookies
This website sets no cookies of its own.
The demo and the seller dashboard set a session cookie when you sign in. It is strictly necessary for keeping you signed in, is not shared, and is not used for tracking.
7. Sharing
We do not sell personal data and we do not share it for advertising.
We share it only with the processors needed to run the service: our hosting provider, the payment provider you chose, GitHub for access management, and our email provider for transactional messages.
8. Your rights
You can ask us for a copy of the personal data we hold about you, ask us to correct it, or ask us to delete it. Write to the address under Who we are and we will answer.
Deleting your data may end repository access that depends on it.
9. Changes
If we change this policy we will change the page. Material changes will be announced to license holders by email.
10. Who we are, and how to reach us
The controller is:
- Guangzhou Agile Byte Information Technology Co., Ltd. (广州敏捷字节信息科技有限公司)
- Unified Social Credit Code: 91440101MA5CQKFRXF
- Room 1445-M81, No. 167 Linhe West Road, Tianhe District, Guangzhou, China
- hello@agilebyte.cc
The English text of this policy is the binding version.