1. Who is responsible
Data controller: i9x Performance, the business name under which Luis
Adrian Aparicio Saucedo, an individual established in Mexico, provides the i9x Performance
software and services.
Address: Avenida Vasco de Quiroga 1329, C.P. 01220, Mexico City, Mexico.
Privacy contact:
support@i9xperformance.com, with
Privacy request in the subject line. This address is monitored and is the one to
use for any of the rights in section 9.
We have not appointed a Data Protection Officer: our processing does not meet the criteria of Article 37 GDPR. If that changes, this notice will name one. For the purposes of Mexican law, the privacy contact above is the departamento de datos personales.
This notice applies to the portal, the online edition and the desktop application; the same text is shown on the website and inside the dashboard. It forms part of the terms and conditions. Where you use the service on behalf of a company, the company is our customer and this notice describes how we treat the personal data of the individuals who hold the account.
2. Our principles
- We do not use your data for anything other than providing the service you signed up for: running your account, your plan, your credits and your licence, keeping the service secure, and meeting our legal obligations.
- We keep only what is necessary for those purposes, and for no longer than section 8 says.
- The analysis happens where your data already is — on your device — so the content of your tests never reaches us.
- We do not sell personal data, we do not share it for advertising, we do not build profiles and we do not use it to train models.
3. Your email address: identification and communication
Your email address is the only identifier of your account and the only channel we use to contact you. We send to it what the service needs — sign-in and security messages, receipts and renewal notices, notices about these documents and our answers to your messages — and product announcements only if you opt in.
We do not contact you by telephone, post or messaging apps, and we do not ask for a telephone number. We will never ask for your password by email.
The name you give at signup is used only to address you in the application and in our emails; we do not verify it. An account can belong to an individual or to a business: the name is the person who uses the account, and the company name, which is optional, is the registered name of the business. If you give it, it appears on your licence certificate.
4. What we collect, why, and on what legal basis
The table is the complete list. It states the purpose and the legal basis under Article 6 GDPR; under Mexican law the same processing is covered by the contract and by the consent given when you accept this notice.
| Data | What we use it for | Legal basis |
|---|---|---|
| Email address | Identify your account, sign you in and communicate with you (section 3) | Performance of the contract |
| Name; company name if you give it | Address you, and show the company on the licence certificate | Performance of the contract |
| Subscription and payment references, and the billing country reported by Paddle for each payment | Manage the plan, renewals, cancellations and refunds, reconcile payments, and keep the tax records the law requires | Performance of the contract and legal obligation (tax) |
| Approximate country of the connection: the two-letter country code that our hosting provider derives from your IP address when you sign up and each time you sign in. Not the city, the region or the coordinates | Know which countries our accounts come from — including those that have not paid yet and so have no billing country — to plan support, languages and the markets we serve. Never used for tax, prices or the contract: the billing country reported by Paddle always prevails | Our legitimate interest in knowing where our customers are |
| Credit records: credits granted, and for each reading the number of rows and analyses and when it happened | Show your activity and your plan's reference, apply the trial quota and resolve billing questions | Performance of the contract |
| Licence key, device identifier and activation dates | Issue the licence and enforce the rule of one device per seat | Performance of the contract and our legitimate interest in preventing misuse |
| Saved runs, only when you press Save: the run name you choose, the names of the files, the labels of the APIs and their aggregated KPIs | Show your history and let you compare runs | Performance of the contract, at your request |
| History and export audit trail, only on the Business and Enterprise plans: which account saved, renamed or deleted a saved run, or exported results (CSV, PDF or presentation), when, the identifier of the run, and counts such as samples or exported rows. Never the run name, the file names, the labels or what was exported | Let the organisation that holds the plan know who did what with its analyses, and investigate a disputed change or deletion | Performance of the contract with the plan holder and our legitimate interest in an auditable service |
| Two-step verification, only if you turn it on: the secret your authenticator app uses, stored encrypted; a one-way fingerprint (hash) of each recovery code, never the code itself; and, for each device you ask us to remember, a fingerprint of its token, the browser it came from and its 30-day expiry date | Ask for a second code when you sign in on a new device and when you change your security settings or delete the account | Performance of the contract, at your request |
| Acceptance of the terms: date and version accepted | Prove what you agreed to and when | Legal obligation (accountability) and our legitimate interest in evidence |
| Support messages and anything you attach to them | Answer you and keep a record of the case | Performance of the contract |
| Server logs: IP address, timestamp, endpoint, result | Operate the service, diagnose faults, rate-limit abuse and investigate security incidents | Our legitimate interest in a secure, working service |
| Website visit counts: how many pages were viewed and how many visits arrived, per day, page, approximate country and source (a search engine, another website or the campaign name of the link). Only totals: no cookie, no IP address stored and no identifier, so a count cannot be traced back to you | Know how many people visit the website and how many of them sign up and buy | Our legitimate interest in understanding how the website is used |
| Load-test records, in both editions: the target host (never the full URL, headers or bodies), the load (virtual users, duration), start and end time, outcome, the address the test was launched from, and your confirmation that you are authorised to test that host (date and wording). For tests above 200 virtual users, your high-load acceptance (date, host, load and wording). The domains you verify, how, and when each check was made | Enforce the allow-list of targets in the online edition, answer abuse complaints ("who sent load to this host and when"), and disable load testing for an account that misuses it | Our legitimate interest in preventing the service from being used to attack third parties, and legal obligation where misuse is reported |
| Team collaboration, on Business and Enterprise (and snapshot sharing on Pro): the collaboration role of each member of the team, the email address of each guest and the state of the invitation (of its link we keep only a keyed fingerprint), and the name of each team project | Decide who can open a team project and with which role, send and manage invitations, and issue the short-lived signed pass that opens the project in the dashboard | Performance of the contract |
| Your email address for product announcements | Tell you about new versions | Your consent, withdrawable at any time |
Where we rely on legitimate interest we have weighed it against your rights and limited the processing to what is necessary. You may object to it — see section 9.
Providing your email address, your name and a password is necessary to open an account. Everything else is optional or is generated by your own use of the service.
5. What we never receive or collect
This is the part most people want to know, so it is stated plainly:
- Your result files. The JTL/CSV you analyse is parsed on your own device. It is not uploaded to our servers, in either edition. The credit meter receives counts of rows and analyses, never their content. On the Business and Enterprise plans an export is recorded as an event (type, time and number of rows, section 4), never its content. We only see a result file if you choose to attach one to a support request.
- The content of the systems you test. We do not receive response bodies, request bodies, headers, cookies, tokens or credentials from the system under test. When you run a test in the online edition we record metrics — elapsed, latency, connect, response code, bytes — and the scenario parameters, not the traffic itself. In both editions each load test is registered in your account with the target host and the load (section 4), never with the paths, headers or bodies of the requests.
- The address or precise location of your company, or yours. We do not ask for a postal address and we do not use precise geolocation (GPS, city or region). The only location-related values we hold are two two-letter country codes: the billing country that Paddle reports with each payment, kept for the tax records the law requires; and the approximate country of the connection (section 4), used only to know which countries our accounts come from. A VPN changes the second one, which is why it never decides anything about your contract, and you can object to it (section 9). The website's visit counter also adds up visits by country, but only as totals per day that are never linked to you.
- Your card details or billing address. They are collected and held by Paddle, our reseller. We receive a payment reference, the amount, the result and the billing country, never the card number, the bank account or any other detail of your payment method. Nobody at i9x Performance can see them.
- What your team writes when it collaborates. Snapshots, notes, findings, verdicts and the log of the Team panel are written as signed files to a folder that your team chooses and controls (for example in OneDrive, SharePoint or Google Drive). We never receive them; we only hold what section 4 lists to decide who may open each project.
- The content of the desktop edition's analysis. The desktop application signs in with your i9x account and needs an internet connection. Each time you load results it sends the same counts as the online edition — the number of rows and whether it is a new analysis — so that your trial quota or your plan's credits can be applied. The result files and their content stay on your computer.
6. Who else processes it
We share personal data only with the providers needed to run the service, under written data-processing agreements and only for our instructions:
- Paddle — our reseller and Merchant of Record. It processes the payment, collects the billing details it needs for tax (including billing address and, where applicable, tax number) and holds the card data, as an independent controller under its own privacy policy.
- Email provider — delivers transactional and notification email.
- Hosting and infrastructure provider — runs the servers, the database and the encrypted backups of the online edition, and measures anonymous website statistics (pages visited, referrer, approximate country, device type and page-load speed) without cookies and without keeping your IP address (section 12).
- Accountant and tax authority — the records the law requires us to keep.
If you enable an integration with another service — for example an external analysis endpoint you configure in the dashboard — whatever the dashboard sends to it goes directly from your device to that service, under its policy, not this one.
Jira. If you connect the desktop application to Jira, your Atlassian email and API
token are stored on your computer, encrypted with the operating system's data protection, and are
sent only to your own Jira Cloud site (an address ending in .atlassian.net). The defects
you choose to register — their description, the occurrence table, its image and a CSV of the
failed samples — go directly from your computer to that site. We never receive the token or the
defects; Atlassian processes them under its own policy and your organisation's agreement with it.
7. International transfers
We are established in Mexico, and some providers process data in the United States or the European Union. Where personal data of individuals in the European Economic Area or the United Kingdom is transferred outside those areas, we rely on the European Commission's Standard Contractual Clauses (or the UK Addendum/IDTA) together with the technical measures described in section 11. For transfers from Mexico, the recipient assumes the obligations of this notice as required by Article 36 of the Federal Law.
You can ask us for the list of providers and the safeguards in place at support@i9xperformance.com.
8. How long we keep it
- Account data — while the account is open, and 12 months after it is closed, to handle disputes and prevent fraud.
- Approximate country of the connection — replaced by the latest one at each sign-in, and removed when the account is deleted.
- Two-step verification — while it is on. Turning it off, or deleting the account, deletes the secret, the recovery codes and the remembered devices. Each remembered device expires after 30 days, and they are all forgotten when you change or reset your password.
- Saved runs — until you delete them, or until the account is deleted.
- Team collaboration — roles, guests and projects while the account of the plan owner is open; they are deleted with it. What the team writes stays in its own folder, under its control.
- Credit records — while the account is open, and 12 months after it is closed, to resolve billing questions.
- Payment references and tax records — five years, the period required by Mexican law, and longer where another applicable tax law requires it.
- Acceptance of the terms — for as long as the contract may give rise to a claim, as evidence of what was agreed.
- Support correspondence — 24 months, unless a dispute requires longer.
- Result files attached to a support request — until the case is closed, then deleted. The rest of the correspondence follows the line above.
- Server and audit logs — 12 months, then deleted or aggregated. This includes the history and export audit trail of the Business and Enterprise plans, which is also kept for those 12 months after a run is deleted or the account is closed.
- Load-test records and your authorisation confirmations — 12 months from each test or confirmation, then deleted, also after you close your account (they answer abuse complaints). The desktop application keeps its own copy on your computer, capped at 15 MB and also deleted after 12 months. A domain verification code that is never published is deleted after 30 days.
- Website visit counts — kept as totals; they contain nothing that identifies anyone.
9. Your rights
Whatever your country, you can ask us to:
- Access the personal data we hold about you and get a copy.
- Rectify what is wrong or incomplete.
- Erase it, where we are not required to keep it.
- Restrict or object to processing based on legitimate interest, on grounds relating to your situation.
- Port it to another provider in a structured, machine-readable format.
- Withdraw consent at any time — for product announcements, from your profile, with no effect on what was lawful before.
In Mexico these are the ARCO rights (access, rectification, cancellation and opposition) and the right to limit the use or disclosure of your data. In the European Union and the United Kingdom they are the rights in Articles 15 to 22 GDPR.
You can also complain to a supervisory authority: INAI in Mexico, your national data protection authority in the EU, or the ICO in the United Kingdom. We would rather you wrote to us first.
10. How to exercise them
- Email support@i9xperformance.com with the subject "Privacy request", from the address of your account, saying which right you want to exercise. Because your email address is how we identify you, a request from that address is normally all we need.
- If the request comes from another address, we will ask you to confirm it from the address of the account — so that we do not disclose your data to someone else.
- We acknowledge within 5 business days and answer within 20 business days (Mexican law) and in any case within one month (GDPR). If the request is complex we may extend it once, and we will tell you why.
Exercising a right is free. We only charge for manifestly unfounded or repetitive requests.
11. Security
- Encryption in transit with TLS 1.2 or higher.
- Passwords stored only as a derived value using
scrypt; we cannot read them. - Session tokens in HttpOnly, SameSite cookies, with an anti-CSRF header requirement.
- Optional two-step verification with an authenticator app (TOTP), with single-use recovery codes. We never send these codes by email or text message.
- Encrypted backups of the database.
- Role-based access for staff, limited to those who need it.
- Rate limiting and account lockout against brute force, and audit logging of security events.
No system is perfectly secure. If a breach affects your personal data and is likely to result in a risk to you, we will notify you by email and the competent authority within the deadlines the law sets (72 hours under the GDPR).
12. Cookies and local storage
We use only what the service needs to work. There are no advertising cookies, no third-party trackers and no analytics cookies. The website counts its own visits without cookies or any storage on your device (section 4), and our hosting provider measures anonymous visit and page-speed statistics the same way: no cookie, nothing stored on your device, the IP address is not kept, and the query part of web addresses (where reset links carry their token) is removed before anything is sent (section 6). Because everything below is strictly necessary, no consent banner is required.
| Key | Purpose | Type | Retention |
|---|---|---|---|
| dm_at | Keeps your session open | First-party HttpOnly cookie | Short-lived |
| dm_rt | Renews the session without asking for the password again | First-party HttpOnly cookie | Until sign-out, or 30 days without using the service |
| dm_td | Only with two-step verification, and only if you tick "Remember this device": this device does not ask for the code again | First-party HttpOnly cookie | 30 days, or until you change your password or forget your remembered devices |
| iq9.cycle | Remembers whether you were looking at monthly or annual prices | Local storage | Until you clear it |
| performai.* | Interface preferences (language, theme, filters) and the record of the terms you accepted | Local / session storage | Until you clear it |
| i9x.*, i9x-collab | Dashboard preferences (language, theme, collapsed panels) and your saved runner sequences and variables (i9x.*); the reference to the team folder you chose in the Team panel (i9x-collab) | Local / session storage; IndexedDB | Until you clear it |
| dmeter.* | Dashboard preferences: how files are loaded, comparison thresholds and the address of any external analysis endpoint you configure (never its keys) | Local storage | Until you clear it |
You can delete cookies and local storage from your browser at any time; deleting the session ones signs you out. In i9x Web the session also ends after 30 minutes without activity or 8 hours after signing in, and the analysis history it keeps lives only in your browser. Paddle may set its own cookies in its payment window — those are governed by its policy.
Paddle's script (Paddle.js) is loaded only on the pages where you pay or update how you pay:
checkout and the payment update page (/payment-update), which the
links in Paddle's failed-payment emails open so you can change your card without signing in.
If you pay for a plan through Paddle, it is also loaded on your account and profile
pages, where we pass Paddle only your Paddle customer ID so it can show you, right
there, a notice when a payment fails or your card is about to expire. No other page of the
website loads it, and it is not loaded for accounts that do not pay through Paddle. We do not
use it for analytics or advertising; what Paddle stores through it is governed by Paddle's own
privacy policy.
13. Automated decisions and profiling
We do not make decisions producing legal or similarly significant effects about you by automated means, and we do not profile you. Automatic rules exist only to apply the limits and credits of your plan and to stop abuse (rate limiting, lockout after failed sign-ins); you can ask a person to review any of them by writing to us.
14. Children
The service is a professional engineering tool and is not directed at minors. We do not knowingly collect data from anyone under 18. If you believe a minor has created an account, write to us and we will delete it.
15. Changes to this notice
We may update this notice. Material changes are announced by email to account holders and published here with a new version number and date. Earlier versions are kept and can be requested.
Changelog
- 2026-11.24 — Business and Enterprise: we now keep an audit trail of who saved, renamed or deleted a saved run and who exported results, and when, with counts only and never the content, names or labels; it is deleted after 12 months (sections 4, 5 and 8). Other plans do not change. The terms and the plans and credits agreement only take the new version number.
- 2026-11.23 — The plans and credits agreement shows in its plans table and in its short version that paid plans have unlimited rows per analysis at no extra cost; the monthly credit reference of each plan moves to section 6. Nothing changes in this notice.
- 2026-11.22 — Against a public host whose domain you have not verified, load tests are also limited to 15 minutes per host per hour (section 8 of the terms). The plans and credits agreement names the current place of your usage (My profile › My subscription).
- 2026-11.21 — The runner becomes a validation tool: against a public host whose domain you have not verified, tests are limited to 50 virtual users and 50 requests per second in total per account and 5 minutes per test; above that the domain must be verified (DNS TXT record or file), and we record each verification and its checks (sections 4 and 8 of the terms). The plans and credits agreement only takes the new version number.
- 2026-11.20 — Load tests above 200 virtual users against a public host no longer require a verified domain: before each one the application asks you to accept a high-load notice (authorisation and responsibility), and we record that acceptance with its date, host and load (sections 4 and 8 of the terms). The plans and credits agreement only takes the new version number.
- 2026-11.19 — Team collaboration (Business and Enterprise, snapshot sharing on Pro):
what we store to decide who opens each project and what we never receive, because the team's work
stays in its own folder (sections 4, 5 and 8). Jira: where your token is kept and where the defects
go (section 6). Browser storage of the dashboard (
i9x.*) and the length of a session in i9x Web (section 12). The terms now state one session per edition (section 5), forbid reusing the code delivered to the browser (section 6) and name the Jira and k6 trademarks (section 15). The plans and credits agreement only takes the new version number. - 2026-11.17 — Load tests: the desktop application now registers every load test in your account before it starts (target host, load, time and source address, never the requests themselves) and records your confirmation that you are authorised to test each host; large tests against public hosts need a verified domain (sections 4, 5 and 8). The terms (section 8) describe the confirmation, the registration, the domain verification and the suspension of load testing after reported misuse. The plans and credits agreement only takes the new version number.
- 2026-11.14 — Teams: the owner of a Business or Enterprise plan can invite people by email. We store the invited email address and the state of the invitation only to send the invitation, let that person join with their own account and show the team to the owner; an invitation that nobody accepts loses the email address when the owner deletes their account. The terms and the plans agreement are updated to describe users and the Enterprise tiers.
- 2026-11.13 — Credits become an activity indicator that never blocks the application, and consumption alerts by email are withdrawn: the credit records are now used to show your activity, not to send alerts (sections 3 and 4). The plans and credits agreement explains the change and withdraws extra credits; the terms are updated to match.
- 2026-11.12 — Optional two-step verification: what it stores (section 4),
for how long (section 8), the
dm_tdcookie for remembered devices (section 12) and the new security measure (section 11). Section 12 also states that a session lasts until sign-out or 30 days without use. New version number shared with the terms (which now explain how to recover an account that loses its second factor) and the plans and credits agreement (no other change to it). - 2026-11.11 — Section 12: for customers who pay through Paddle, Paddle's script also loads on the account and profile pages, identified only by the Paddle customer ID, to show failed-payment and expiring-card notices there. New version number shared with the terms and the plans and credits agreement (no other change to them).
- 2026-11.10 — Section 12 states that Paddle's script loads only on checkout and on the new payment update page that Paddle's failed-payment emails link to. New version number shared with the terms and the plans and credits agreement, which now state that the statutory 14-day right of withdrawal (European Union, European Economic Area, Switzerland and United Kingdom, including UK annual renewals) and Paddle's refund policy apply in addition to our 30-day refund, that renewals are generally (not always) non-refundable, how failed charges are retried and what happens with a chargeback.
- 2026-11.9 — The desktop application now signs in online and records the same usage counts as the online edition (rows and analyses, never their content) in your account, so the trial quota and the plan's credits apply to it too (section 5). New version number shared with the terms and the plans and credits agreement, which adds the Starter plan, its introductory offer and the new annual prices.
- 2026-11.8 — The website's own visit counter is disclosed: totals of page views and visits per day, page, approximate country and source, without cookies, without storage on your device and without storing IP addresses or any identifier. The hosting provider's anonymous, cookie-free website and page-speed statistics are disclosed in sections 6 and 12. New version number shared with the terms and the plans and credits agreement.
- 2026-11.7 — The business name is written in full as "i9x Performance" in the data controller section and throughout, the same name used in the terms. The controller, the individual behind it and the address do not change. New version number shared with the terms and the plans and credits agreement.
- 2026-11.6 — The approximate country of the connection (a two-letter code derived from the IP address at sign-up and sign-in) is disclosed, with its purpose, legal basis and retention; the billing country reported by Paddle still prevails. It is stated that an account can belong to an individual or a business, and that nobody at i9x sees card or bank details. New version number shared with the terms and the plans and credits agreement.
- 2026-11.5 —Result files attached to a support request are kept only until the case is closed. New version number shared with the terms and the plans and credits agreement (support by email, with a first-response time for each plan in the new support policy, and how a figure that looks wrong is checked).
- 2026-11.4 — No change to this notice; new version number shared with the plans and credits agreement (the saved-scenarios limit, which the application never had, is no longer listed).
- 2026-11.3 — The data controller is identified: i9x, with the name of the individual behind it and the address. The pre-launch notice is removed.
- 2026-11.2 — No change to this notice; new version number shared with the terms and the plans and credits agreement (new prices and credits).
- 2026-11.1 — One text for the website and the dashboard. Principles stated: no use of your data beyond the service, and only what is necessary. Email confirmed as the only identifier and communication channel. Company address and location stated as not collected; tax number removed from what we hold (Paddle collects it). Credit records, saved runs and the billing country reported by Paddle disclosed, with their retention.
- 2026-10.1 — Legal bases stated per purpose; load-test audit records and the record of terms acceptance disclosed; ARCO and GDPR rights set out together with the authorities; international transfers and safeguards described; the cookie table corrected to the cookies actually used — an "analytics" cookie was listed that the service does not set.
- 1.0 — Initial version.
Questions, or to exercise a right: support@i9xperformance.com.