Privacy Policy

Last updated: 12 October 2026

UIVRA is operated by Ruslan Savchuk, an individual trading as UIVRA. For the purposes of this Privacy Policy, Ruslan Savchuk, trading as UIVRA, is the operator of UIVRA and the controller of the personal information described in this policy.

UIVRA is designed to be local-first. This policy explains what information UIVRA stores, where it is stored, and who else handles it.

1. Summary

• Your analysed pages, selected elements, snapshots and component data stay in your browser unless you choose to save or share them.
• AI Rebuild sends selected component data to our backend when you press Rebuild. Account, credit and checkout features also contact our backend. See sections 3 to 5.
• We do not sell your personal information.
• We do not use advertising or cross-site tracking networks.
• UIVRA never receives or stores your full card number.

2. Data stored in your browser

UIVRA keeps the following on your device:

• session history of elements you have inspected during the current browser session;
• saved snapshots, captured components and your local component library, if you save them;
• interface preferences, including language and development-tool settings;
• an installation identifier, an access key for your account, and a recovery secret, used to connect to your UIVRA account and to restore access if your key is lost.

This data stays on your device. Clearing your browser storage removes it. We can only read the account identifiers above, and only for the account features described in section 4; we cannot read your saved snapshots, history or component library.

3. Information our backend stores

When you use a feature that requires an account, UIVRA sends a limited set of data to our backend. We store only what is needed to provide the account, entitlement and payment features you use:

• your installation identifier, the date it was created, and its current status;
• a hashed access key and a hashed recovery secret, so we can authenticate you. We never store these keys in readable form;
• your entitlement, such as whether your account is on the free plan, Pro annual or Pro Lifetime, and the dates attached to it;
• your AI credit balance, and the ledger of credit purchases and usage;
• AI job records, including operation reference, status, feature, model, credit cost, a request hash and bounded recovery state. These records do not contain the selected component payload or generated code;
• Paddle identifiers associated with your purchases, such as a Paddle customer and subscription reference, and the transaction reference of each purchase;
• the date of the most recent update to any of the above.

We do not store the content of pages you inspect, the elements you select, your snapshots, or your component library on our servers. The single exception is AI Rebuild, described below.

3A. AI Rebuild

AI Rebuild sends selected component data to our backend and AI provider. Inspection, Copy for AI Agent, AI History and successfully delivered generated results remain in your browser. The backend keeps job and recovery metadata, but no generated files. Account, credit and checkout features also contact our backend, as described in sections 3 to 5.

When you press Rebuild, the extension sends us the following, and only then:

• the structure, text and computed visual styles of the single component you selected;
• the output format you chose, for example a component for a JavaScript UI library, or plain HTML and CSS;
• the URLs of any images, icons or fonts that component references — never the files themselves, and never binary or base64 data.

We do not send the rest of the page. The component payload excludes cookies, browser storage, captured form values and your account access key. Text, styles and asset URLs in the selected component can still contain information from that page, so review what you select before pressing Rebuild. Component data is not sent automatically in the background.

We pass that component data to an AI model provider, currently Cloudflare Workers AI, to generate the code, and we return the generated code to your extension. The generated code is shown to you as text for you to review and copy, then saved locally by the extension. We do not execute or store the generated code on our servers. We do not keep a copy of your selected component payload after processing. If a response is lost, the backend can report the job status but cannot replay its files. One bounded recovery attempt may generate the same request again without another UIVRA credit.

Page content is treated as untrusted data only. It is never treated as instructions to the model.

AI Rebuild uses one AI credit per successful rebuild. A failed job has its reserved credit returned. A browser timeout may occur after a successful job, so the extension checks the job and credit state using the same operation reference. See sections 3 and 4 for how credits are recorded.

4. How we use this information

We use the data above only to:

• authenticate your account and keep you signed in;
• determine which features your plan unlocks;
• track and apply your AI credit balance;
• generate code for the component you selected when you press Rebuild, as described in section 3A;
• grant the Pro plan or credits you have purchased, based on confirmed payment events from Paddle;
• prevent misuse of the payment and credit systems.

We do not use your data for advertising. We do not use it to build behavioural profiles. We do not sell it, and we do not share it with data brokers.

5. Payments and card data

Payments are processed by Paddle.com Market Ltd ("Paddle") as merchant of record. Paddle hosts the checkout page and collects payment details directly from you.

UIVRA never receives, processes or stores your full card number or card security code. What reaches us is limited to confirmation of a completed transaction, such as the transaction reference, the product purchased, the amount and your Paddle customer or subscription reference, so that we can grant what you bought.

Paddle's own processing of your payment details is governed by the Paddle privacy policy, which is presented to you at checkout.

6. Third parties

We use the following service providers, each acting on our behalf:

• Cloudflare — hosts our backend and database and processes selected component data through Workers AI and AI Gateway when you use AI Rebuild.
• Paddle — processes payments and acts as merchant of record.

We do not otherwise share personal information with third parties, except where required by law or necessary to protect our rights.

7. Data retention

Account data is retained for as long as your account exists. Credit ledger entries and AI job and recovery metadata are retained with the account. Generated AI code is not stored on our servers. Uninstalling the extension does not delete your account; if you want your account data removed, contact us using the address in section 9 and we will delete it, except where we are required to retain records such as completed transactions for accounting or legal purposes.

8. Your rights

Depending on where you live, you may have the right to access, correct, export or delete your personal information, or to object to or restrict certain processing. To exercise any of these rights, contact us using the address in section 9. We will verify your request and respond within the timeframe required by applicable law.

9. Contact

Questions about this policy, or requests relating to your data, can be sent to ruslikruslan0000@gmail.com. See also our Terms of Service and Refund Policy.