Privacy policy

Where your footage goes

The material used for cloud processing, including source footage, masks, reference images and reference videos, together with job parameters such as prompts, is uploaded and submitted by the plugin directly from your computer to your own RunningHub account and does not pass through our servers. How RunningHub handles this material is governed by RunningHub's own terms and is outside the scope of this policy.

When you use Rp Enhance, the material is processed by Topaz Video AI on your computer or on a computer you specify on your local network; it is not uploaded to RunningHub and does not pass through our servers.

How your API Key is stored

Your RunningHub API Key is stored only on your own computer; each plugin account can save several, and you switch between them in “Manage Account…”. The plugin sends it only to RunningHub, to upload material, submit jobs, retrieve results and check queue status and balance. Our licence server does not collect the key, and stores neither the key itself nor a hash of it. The plugin code explicitly keeps it out of logs.

“Manage Account…” shows only the key name you set and the last 4 characters of the key. “Sign out” does not delete the API Keys saved on the computer; to delete one, select it in “Manage Account…” and click “Remove Key”. This does not affect the key on RunningHub.

Files on your computer

The plugin stores the following files in the .nuke directory on your computer:

• pixrepaint_settings.json: your username, the linked RunningHub ID and its platform, the API Keys saved on this computer, the sign-in credential, the machine label, the machine tier, the interface language, and the proxy address and Topaz service address and password entered in “Options…”. This file is stored in plain text, including the API Keys, the sign-in credential and the Topaz service password. The plugin does not store your plugin account password on the computer.
• pixrepaint_licence_v2.json: the licence cache, used to keep working when the licence server cannot be reached for a while.
• pixrepaint_install_id: a random number generated the first time the plugin is used, to tell this computer apart.
• pixrepaint_options.json: the state of the switches in “Options…”.
• pixrepaint_lang: the interface language chosen in the installer.

The plugin also uses these locations:

• The pixRepaint folder in the directory of your project file: generated results, job caches and temporary files.
• %LOCALAPPDATA%\pixrepaint\uploads.json: checksums of uploaded material, their file names on RunningHub and the matching RunningHub ID, to avoid uploading the same material twice.
• If you run the Topaz service on another computer on your local network for Rp Enhance, the %LOCALAPPDATA%\pixrepaint_topaz directory on that computer holds the service password (service.json) and temporary files created during processing.

These files stay on your own computers and we cannot access them. If you send a project or settings to someone else, we recommend not copying your whole .nuke directory.

What the licence server collects

All communication between the plugin and the licence server uses encrypted connections (HTTPS). Each action sends the following:

• “Activate…”: username, password, subscription code, RunningHub ID and its platform, machine label, and a hash of the machine identifier.
• “Sign in…”: username, password, machine label and a hash of the machine identifier; when the machine limit has been reached, also the internal number the server assigned to the machine you choose to sign out.
• “Forgot password…”: username, the last redeemed paid subscription code, the new password, and a hash of the machine identifier.
• Account actions after signing in: the sign-in credential and the information each action needs, such as the subscription code for “Renew / Upgrade”, the current and new passwords for “Change password”, the password and new RunningHub ID for “Change RunningHub ID”, and the server's internal number for the machine selected in “Sign out a machine”.
• When submitting jobs: the sign-in credential, the plugin version and the job's RunningHub task ID, to confirm the job is authorised, count concurrent jobs and keep this machine marked as online while jobs run. If a job does not succeed, the plugin attaches an error code (for example the error code returned by RunningHub, or a failure category such as “out of GPU memory” or “cancelled”), so that we can see why jobs fail and improve the error messages. The code contains no footage, prompts, generated results or file paths.
• “Check for Updates…”: no account information is sent when asking for the latest version; when you confirm the update and download the installer while signed in, the sign-in credential is included so that downloads can be counted per account.

The plugin does not send your API Key, footage, prompts, generated results or Nuke project paths to the licence server, nor your computer's user name or machine name.

Plugin account and subscription codes

The licence server keeps the following for each plugin account:

• The username, and the RunningHub ID linked to the account and its platform.
• An irreversible hash of the password. We do not store and cannot see your password. If you forget it, you can reset it with “Forgot password…” using the last paid subscription code redeemed on the account; accounts that have only used the trial code should contact us by email.
• The plan, length and remaining time of each redeemed subscription code, with the redemption time and the RunningHub ID linked to the account at that time. Subscription codes themselves are stored only as irreversible hashes, never in plain text.
• When the account was created, and when it first ran a job successfully on RunningHub. After the first successful run, the linked RunningHub ID is locked.
• For each signed-in machine: the hash of its machine identifier, the machine label, a hash of the sign-in credential, the plugin version it last reported, and the times of sign-in, last activity and sign-out or being signed out. The plugin version is used to troubleshoot problems and to see which versions are in use.
• When the trial code 8888 is used for activation or redemption, the account's trial entitlement (plan, length, remaining time, redemption time), plus an encrypted, irreversible digest of the RunningHub ID and the time it was recorded. The digest is used only to make sure each RunningHub ID gets one trial; the trial record does not contain the RunningHub ID in plain text.

The same RunningHub ID can be linked to several plugin accounts. In that case the plugin only says so and shows nothing about the other accounts. To prevent password guessing, the server counts daily failed sign-ins and password resets, keeping only irreversible digests for the count.

Machine identifier

The hash of the machine identifier is computed by the plugin on your computer. It distinguishes the different computers of an account and counts how many are online. We collect only the hash, not the information used to compute it, and we do not collect your computer's user name, machine name or project paths.

Job authorisation records

To check that each job was started by an authorised plugin account and does not exceed the plan's concurrent job limit, the licence server keeps these records: when the job authorisation was issued, the account and signed-in machine it belongs to, the linked RunningHub ID, the matching RunningHub task ID, the result of the check and the reason, when the job started and ended, and the error code the plugin attached if the job did not succeed.

While the job runs, the server also receives the RunningHub ID that started the run, which is used only for comparison with the ID linked to the account: if they match, the server records that the account has run successfully on RunningHub; if they do not match, only its last 4 digits are kept, to remind you in “Manage Account…” to switch to an API Key under the linked ID. The reminder and the stored last 4 digits are cleared once a job runs successfully with an API Key under the linked ID or after you change the link with “Change RunningHub ID”. These records contain no footage, prompts or generated results.

Machine list and RunningHub ID

The machine list under “Machines” in “Manage Account…”, and the machines listed for “Sign out a machine” and when the machine limit is reached at sign-in, show only each machine's number within your account (#1, #2, … in the order the machines signed in), the machine label you set and whether it is online or idle; they show neither machine names nor machine identifiers. “Manage Account…” shows only the first and last few digits of your RunningHub ID, never the full ID.

IP addresses

The licence server uses the source IP address to limit the rate of requests such as activation, sign-in, password reset and installer downloads; these counts are not written to the database. When a password entered again after signing in (“Change password”, “Change RunningHub ID”) is wrong, the server stores an irreversible digest that includes IP information, to pause attempts after repeated errors. In addition, the server access logs record the full IP address; see Access logs.

Access logs

To keep the service secure (identifying scans, attacks and other malicious traffic) and to count visits, the server keeps access logs. Visiting this website, downloading installers, and communication between the plugin and the licence server all produce access log entries.

• What is recorded: the visitor's full IP address, the time, the domain and page visited, the request method and result, and the browser or client identifier.
• What is not recorded: the body of forms and plugin requests (including usernames, passwords and subscription codes), cookies and credentials.
• Retention: at least 6 months. Log files are rotated by size and archives are deleted automatically after 6 months. Under the Cybersecurity Law of the People's Republic of China, network logs must be kept for no less than six months.
• Use: only for security and visit statistics; not provided to third parties, except where laws and regulations require otherwise.

We do not accept trial applications through web forms; trials are activated in the plugin with the trial code, and the information sent and kept is described in What the licence server collects and Plugin account and subscription codes.

Retention and deletion

Server access logs are kept for at least 6 months; rotated log archives are deleted automatically after 6 months.

These licence server records are deleted automatically when they expire: records related to job authorisations are deleted 14 days after the job ends or the authorisation expires; finished machine sign-ins (signed out, signed out by another machine and so on) are deleted 30 days after they end, and sign-ins that go unused for a long time are deleted 60 days after their last activity; records of “Sign out a machine” actions are deleted after 7 days; failed sign-in and password check counts are deleted after two days.

Plugin account and subscription data (the username, the irreversible password hash, the linked RunningHub ID and subscription entitlements) are kept for as long as the plugin account exists, to provide the subscription, sign-in and password reset. You can ask us to close your plugin account using the contact details below; we will close it within 15 working days after verifying your identity. After closure the account can no longer sign in, the username is marked as closed and can be registered again, the linked RunningHub ID is released, and the subscription entitlements, machine sign-in records and job authorisation records are deleted at once.

Subscription code redemption records (the irreversible hash of the code, the plan, length, redemption time and the RunningHub ID linked to the account at redemption) are used to reconcile orders and prevent a code from being redeemed twice; they are kept for at least three years from redemption, including after the account is closed. Digests of RunningHub IDs that have used the trial are encrypted and cannot be turned back into the RunningHub ID; they are used only to make sure each RunningHub ID gets one trial, and are kept long term.

Contact us

If you have any questions about this policy, please email us at pixRepaint@163.com.