License Agreement for the PolyApiIDE browser extension
Version 2026-08-21
Website: https://polyapiclient.ru
Privacy Policy: https://polyapiclient.ru/en/privacy
Contact: support@polyapiide.ru
1. General
1.1. This License Agreement (the "Agreement") governs use of the PolyApiIDE browser extension and related services on polyapiclient.ru (the "Product"), provided by the rights holder / service operator (the "Licensor").
1.2. By installing, activating or using the Product, purchasing a plan, or requesting a demo key, you (the "User") confirm that you have read the Agreement and Privacy Policy and accept them.
1.3. If you disagree, you may not use paid or demo features of the Product.
1.4. The sole purpose of the Product is an API client (IDE) for user-initiated API requests, plus collections, environments, QA/load tools, licensing, optional manual cloud backup, and optional AI chat history sync (truncated text after secrets and personal data are stripped; attachment bytes are not stored).
2. Plans and license
2.1. Free — no key, limited features. A site account and IDE sign-up are not required: Free opens immediately and works locally. Free allows up to 2 concurrent active sessions (devices / browser profiles) at a time; on conflict the User may keep the current device or end the session. Fullscreen response, the IDE action log, and all collection import formats (except applying a collection or folder patch) are included in Free. Export and apply of collection, folder (section) and request patches are paid (Month / Year / Lifetime / demo).
2.1a. A technical client_id (API client identifier) and secret are created only when the User opts into a server feature: key activation, demo on the website, cloud backup, AI history sync, a support request via the API, or a counted QA/load run (collection, folder, load). This is not a store account, not a personal cabinet, and not mandatory registration for Free.
2.1b. On Free the QA and Load tabs are visible. QA checks after Send are available, plus limited runs: 3 full collection runs, 3 folder (section) runs and 1 load run per calendar month. The “File a bug” button and advanced QA/Load settings are paid. Counted runs require a technical API client. Demo and paid plans (Month / Year / Lifetime) are not limited by these quotas.
2.2. Month — one-time payment for 30 days of access. Current price is shown at checkout (guide 490 RUB). Month price may change for new purchases; the amount fixed in your payment applies to the paid period. While valid, you get the full paid feature set and IDE updates (typically via Chrome Web Store / normal install). Up to 5 concurrent active IDE sessions (devices / browser profiles) per key are allowed; if exceeded, the User may end other sessions via «Stay here» in the IDE. After payment you receive an activation key and instructions by email. The offline Lifetime archive (zip of the Lifetime build) is not included and is not sent for Month.
2.3. Year — one-time payment for 12 months with 20% off vs 12× Month (guide 4704 RUB). Same features as Month for the key validity period, including up to 5 concurrent active sessions per key. After payment — key and instructions by email; the Lifetime archive (zip) is not included.
2.4. Lifetime — one-time payment (guide 14900 RUB) for ongoing Product access. Fixes (patches and minor bugfixes) of the current line are included at no extra charge. Major-line updates are not included automatically: the User may buy them separately if they want the new major (a separate major SKU is not sold yet; terms will be published on the website before such sales begin). Up to 5 concurrent active IDE sessions per key are allowed (the Free session limit does not apply). After payment you receive a key and archive / download link (Lifetime plan only). The download link is single-use. Re-issue of archive and key is not guaranteed. The archive is a protected build (minify + obfuscate) for offline install; it is a delivery method, not a freeze without fixes. A new build of the current line is available in the archive as soon as you receive it; publication of the same version in the browser store (Chrome Web Store / Firefox Add-ons) may lag while it is reviewed.
2.5. Demo key — once per email, 14 days of the full product. Requested only on the website (the “Activate Demo” form with required license and personal-data consents); the IDE does not issue demo keys. After expiry IDE data may be reset. Demo allows up to 1 concurrent active sessions. While valid, demo includes the full paid feature set.
2.5a. License keys are purchased only on the website (checkout, e.g. https://polyapiclient.ru/en/?plan=year#buy). Email in the IDE is used to activate an already issued key, not to buy.
2.6. The key is personal and bound to email. Sharing with third parties is forbidden and may lead to revocation without compensation.
2.6a. To enforce concurrent session limits and prevent abuse, the server records technical session signals: API client_id, device_id (local extension profile UUID), device label (user-agent), IP hash and country code (when available), and heartbeat timestamps. Data is kept in Redis with a short TTL and is not used for targeted advertising. The Licensor may raise the session limit for a specific key upon support request.
2.7. Payment via a payment provider (YooMoney / YooKassa, etc.).
2.8. Cloud IDE backup runs only manually on explicit User action. No automatic uploads. The User may disable cloud backup in settings. Email backup is on User initiative to the address they provide. The server keeps a history of snapshots: the last 3 on Free and the last 10 on paid plans (Month / Year / Lifetime); older snapshots beyond the limit are deleted when a new one is saved.
2.8a. AI chat history (message text and attachment metadata without file bytes) may be stored on the server for sync across sessions of a registered API client. Before storage, message text and chat titles are scrubbed of typical secrets (logins, passwords, tokens, API keys, Bearer/JWT and similar) and personal data (email, phone numbers, card numbers and similar identifiers). Scrubbing is heuristic and does not guarantee that every secret is found; do not paste live credentials into chat. The server keeps truncated text (up to 255 characters). The User may delete history in IDE settings.
2.9. Feature sets by plan/version are fixed in the licensing system. For Lifetime, fixes of the current line are available; features of a new major line may require a separate purchase when that plan exists. The Licensor may enable/disable features per license.
2.10. If the licensing server is temporarily unreachable, an already activated paid key continues to work locally. The Free plan does not require server-side key checks.
2.11. HTTP client settings are layered IDE → space → request: an enabled request layer overrides space and IDE; a disabled layer is skipped.
2.12. Plan prices, the year discount, demo duration, application versions (including minimum and latest) and other operator parameters are stored in the Service database and may be changed by the Licensor without shipping a new IDE build.
3. Rights and restrictions
3.1. Non-exclusive, non-transferable license for the selected plan.
3.2. Circumventing plan limits, interfering with license checks, or breaking the law is forbidden.
3.3. The Product is provided "as is".
3.4. The User independently creates, stores and sends API requests, imports collections and other data, configures proxies, variables, scripts, integrations (including AI providers, trackers and messengers) and uses responses from third-party servers. The Licensor does not monitor such content in real time and is not the operator of processing for data the User sends to third parties through the Product.
3.5. The Licensor is not liable for losses, third-party claims or other consequences of the User’s acts or omissions in the Product, including requests to arbitrary URLs, processing personal data without a lawful basis, violating third-party terms, using proxies, entering or storing secrets, or relying on AI outputs. Such acts are performed by the User alone; the User’s civil liability is determined by the Civil Code of the Russian Federation and other applicable RF law. This disclaimer does not limit consumer rights that apply mandatorily to a particular transaction.
3.6. The User must use the Product only lawfully and must not infringe third-party rights.
3.7. User-authored pre-request and after-response scripts run locally in a sandbox on the User’s device (including via local new Function / a sandbox iframe). The canonical API object is poly; Postman pm is a compatibility alias wrapping the same object so imported scripts work as-is. The Licensor does not execute user code on its servers and does not pre-review script contents. poly.sendRequest / pm.sendRequest fires HTTP through the same Send stack as the IDE Send button; that request is treated as initiated by the User by running the script. Responsibility for script contents and the requests they trigger follows clauses 3.4 and 3.5. Docs: https://polyapiclient.ru/en/docs/scripts
3.8. “Sync cookies from site” reads the browser cookie jar (chrome.cookies) only after an explicit User click. The optional cookies permission is requested then; the read is scoped to the current request URL hostname. Cookies are not auto-synced. Cookies are not uploaded to the Licensor’s server unless the User later runs a cloud backup that includes request cookies stored in the IDE. Session cookies may leak into IDE storage, subsequent requests, backups, AI prompts and curl preview. Responsibility follows clauses 3.4 and 3.5.
3.9. After the extension is installed, the browser (Google Chrome, Mozilla Firefox, Microsoft Edge or another vendor) may independently collect and process additional data about the User, the device and browser usage under that vendor’s own privacy policy and terms. The Licensor does not control that processing, is not its operator and is not responsible for it. The User’s relationship with the browser vendor is not governed by this Agreement or the Licensor’s Privacy Policy.
4. Personal data and communications
4.1. Policy: https://polyapiclient.ru/en/privacy
4.2. Email and technical data are processed for the contract, support and abuse prevention (including device_id, IP hash, country_code when available). Cloud backup only on manual action if not disabled. AI chat history — truncated message text after secrets and personal data are stripped (no attachment bytes) when sync is used. Details are in the Privacy Policy.
4.3. Marketing emails to the provided address are sent only with separate consent ("I agree to receive emails…"). Consent may be withdrawn via support.
4.4. Extension usage analytics (IDE action events) are sent to web-analytics services (Yandex Metrica; Google Analytics if configured) and are not stored by the Licensor as an event journal in its database. The server may store only the analytics_opt_out flag. The User may disable sending in IDE settings. Site analytics cookies (Metrica with webvisor, GA) load only after consent in the cookie banner.
4.5. The cookie policy is published by the server as its own version alongside the Privacy Policy. Essential site cookies store language and the cookie-choice. Third-party analytics cookies load only after banner consent. The extension does not set site cookies; the IDE analytics_opt_out flag syncs with the technical API client on the server and does not replace site cookie consent.
4.6. The extension may ask the licensing server for current product version information so it can offer an update. That request does not require a license key and does not include collections, environments or request bodies.
5. Changes
5.1. New versions are published on the website (/en/terms, /en/privacy). The current version and the list of versions accepted for demo and checkout are kept on the server: accepting any version from that list counts as accepting the Agreement as of that version. The website is the source of the full text; the extension does not bundle document bodies.
5.2. New purchases and demos may use any version from the accepted list (not only the latest). Paid users (Month / Year / Lifetime) and full-product demo users may accept the Agreement, personal-data processing and email consent in the IDE (Settings → License); document versions come from the server and acceptance is recorded on the server. Free does not show or collect these consents in the IDE. If the User’s accepted version is older than the latest but still on the list, the IDE may show “Service policies have changed” with links to the fresh documents and an option to accept the latest version; acceptance is recorded on the server.
5.3. If the User accepted a version that is still valid, demo and checkout proceed even when a newer edition is already on the website. The IDE may invite the User to review the latest version.
6. Force majeure and network restrictions
6.1. The Licensor is not liable for delays, interruptions or inability to access the Service caused by force majeure, including acts of public authorities (including blocks and other measures by Roskomnadzor and other regulators), provider outages, DDoS attacks and other external restrictions.
6.2. Such restrictions may require time to restore access or provide workarounds. This alone is not grounds for an automatic refund unless required by applicable law.
7. Revocation and support
7.1. A key may be revoked for Agreement violations.
7.2. support@polyapiide.ru
8. Final provisions
8.1. Invalidity of one clause does not affect the rest.
8.2. Current version — at https://polyapiclient.ru/en/terms (source of truth). The IDE shows links and versions from the server.
9. Cessation of operations
9.1. If the Licensor ceases commercial activity for the Product (shutting down the licensing service, liquidation, or otherwise fully discontinuing Product support), every User who paid for a Month, Year or Lifetime plan (per the Licensor’s payment records) will receive a Lifetime archive: a zip of the IDE build current at cessation or the last stable build, so the Product can be used locally without the licensing server.
9.2. Notice is sent to the email used at purchase, with a reasonable period (at least 30 calendar days where technically possible).
9.3. Cloud features (server-side key checks, cloud backup, AI chat history, email notifications) may become unavailable after cessation. The archive does not include an obligation to keep the server running.
9.4. Free-plan and demo-key users do not automatically receive an archive under this clause.