rugbyAPI

Privacy notice

Last updated 23 September 2026 · DeveloperData.net, Bangkok
In shortWe keep your name, email, plan and how you use the API; nothing more.
 We never sell your data or use advertising or tracking cookies.
 Google, Stripe and Cloudflare process data for us to run the service.
 Ask us any time to see or delete what we hold.

01Who is responsible

DeveloperData.net, Empire Tower, 41st Floor, Unit 4106-7, South Sathorn Road, Yannawa, Sathorn, Bangkok 10120, Thailand, is responsible for the personal data described here. Contact: [email protected].

02What we collect

Your account: the name, email address and profile picture Google shares when you sign in (we do not keep the picture), your plan and when you joined. Your key: a fingerprint of it and its first characters, never the key itself. Your use of the API: the time, endpoint, response status and speed of each call, and a daily count. Payments: Stripe handles your card; we receive only the plan, the amount and whether it was paid. Visits to the website: the page, the referring site, the browser type, the IP address and the country Cloudflare reports, to count visitors and to spot and block abusive or automated traffic.

03Why we use it

To run your account and key, enforce plan allowances, show you your own usage, answer support requests, take payments, keep the service secure and understand which parts of the site are used. We rely on our contract with you and on our legitimate interest in running and protecting the service.

04Who else processes it

Google (sign-in, including its sign-in script, which pages load while you are signed out), Stripe (payments), Cloudflare (network and security) and our email provider (account and billing emails). Each handles data only to provide its service to us. We never sell personal data and do not use it for advertising.

05Cookies and storage

One cookie keeps you signed in. While you are signed out, pages load Google's sign-in script, so Google receives your IP address and may use its own cookies. Signing in through Google's pop-up or button sets a security cookie that lasts ten minutes, and signing out sets a marker that lasts one minute so the pop-up does not open again straight away. If you arrive through a partner's link, a cookie named ap_click remembers which partner sent you, for 60 days (a newer partner link replaces it), so the partner can be credited if you buy a plan; it is our own cookie and holds no personal details. The documentation keeps your API key and your sidebar choice in your browser's own storage, so its examples run with your key; they stay in your browser and you can forget the key from any endpoint page. There are no advertising or cross-site tracking cookies.

06How long we keep it

Account details for as long as your account is open. API call logs and website visit records for up to 12 months, then they are deleted. Payment records for as long as tax law requires. When you close your account we delete your personal data within 30 days, except what the law requires us to keep.

07Your rights

You can ask to see, correct, export or delete your personal data, or object to how we use it, by writing to [email protected]. We answer within 30 days. You may also complain to your local data protection authority.

08Changes

If we change how we use personal data we will update this notice and, for changes that matter, email you first.