GPTrepublicLanguageEnglishDeutschFrançaisItaliano

Beta data and terms

GPTrepublic is an independent experimental project. The beta may experience interruptions, errors and inaccurate answers. The client uses your computer’s resources, electricity and internet traffic.

Check your GPU

A GPU check may be required before registration, depending on the beta settings. It starts on request; continuing after the check sends the model and operating system to the server. The tool will verify the hardware requirements before you contribute computing power.

Registration and diagnostics

Registration uses your email, password and selected country of origin. We do not request your name, address, date of birth or phone number, and participants do not sign in through ChatGPT. We assign an automatic board identifier. Email and country are still personal data: we do not promise anonymity.

The test has 40 participant slots, with admissions managed by the administrator. Registering without a GPU check does not certify computer compatibility. Personal test codes are stored as hashes; the copy needed for delivery is encrypted in the email queue and removed after sending.

Account security

Email is encrypted in the database using AES-256-GCM; keys are stored separately as service secrets. An HMAC index locates the account. Passwords are protected with scrypt and a random salt and cannot be decrypted. Confirmation, recovery and session tokens expire or are single-use; only their hashes are stored. Encryption does not prevent the service from accessing data when it needs to use it.

Email and consent

Registration requires acknowledging the emails needed for testing: welcome, dates, instructions, codes and operational updates. We record the date and version of this acknowledgement separately from optional consent to project news. News preferences do not disable service emails.

Automated emails use the language associated with your selected country when supported; otherwise, including multilingual countries, we use English.

Acknowledging the privacy notice is required. Consent to news and updates is optional, unchecked by default and revocable in email preferences. We store the notice version and acknowledgement date, and the date of your updates choice. Email confirmation, password recovery and test instructions are service communications.

Email is sent through the OVH-hosted admin@gptrepublic.org mailbox. The provider receives the address and message. Unconfirmed self-registrations are removed after 24 hours at the next cleanup; manually added invitations remain until the administrator deletes them. Links and sessions expire. We use technical cookies and temporary HMAC fingerprints to limit abuse.

Contributions and statistics

We associate your account with nodes installed using your personal installer, detected GPU, declared shared memory, observed availability intervals, requests and output-token counts for completed jobs. You and the administrator can view these metadata by period; they can be deleted with the account. They contain no prompts or responses. Statistics start when collection is active; earlier periods are not reconstructed.

Discord

Linking Discord is optional. If you authorize it, the website associates your Discord ID with your account and adds you to the GPTrepublic server to assign the verified member role. We do not collect Discord emails or messages or store Discord access tokens. You can unlink from your personal area. After deletion or unlinking, the ID is kept only until the role is removed; the system retries if errors occur. Messages posted on Discord are managed by Discord and are not deleted when you delete your website account.

Chat history on your device

The portal keeps up to 50 exchanges in your device’s browser, separated by account. This history is not synced to cloud storage. You can delete it using “Clear history” in the chat area. It is tied to the browser and domain: changing device, browser or site address, or clearing browser data, may make it unavailable.

Local history is not encrypted with a dedicated password. Anyone with access to your browser profile can read it. Saving may fail in private browsing or when storage is blocked; the portal will report the issue.

Browser storage does not automatically transfer history to the PC where the tool is installed. If you use the portal on another device, history stays in that device’s browser.

Towards the desktop tool

We want the installed tool’s history to stay on the user’s PC too, without cloud synchronisation. This still needs to be completed and verified in the client; the confirmed feature today is the web portal’s local history.

Network processing

The new protocol separates coordination from content: prompts and responses travel directly between your browser and the GPU node, while the coordinator handles only assignments, status and connections. The portal chat requires this protocol and remains unavailable until the network is updated. Node operators can still inspect or record what they process.

The updated coordinator retains no prompts, responses or history, including in its request queue. It keeps technical metadata needed to operate: nodes, connection addresses, request identifiers and status. The portal separately stores registrations, invitations and discussion posts. This does not mean the service stores no data at all.

Intermediate data does not guarantee anonymity or secrecy: it can reveal information about the original text. Transport encryption alone protects the connection; it does not make data unreadable to the computer that must process it.

This beta does not guarantee end-to-end confidentiality from the coordinator and nodes, and cannot verifiably prevent a participant from recording what they process. We do not promise that no one can read, intercept or collect chats. Clearing browser history does not prove that data has been deleted from other systems.

Registrations and online board

Prompts are processed by participants’ computers. Use only non-sensitive data. Board posts and replies are visible to admitted testers under your automatic identifier. Do not post passwords, keys, private addresses or logs containing personal data.

Control over your data

You can stop contributing by closing the client. Registrations and reports remain available during the test; ask the project owner for deletion through the private board.