Prove you wrote
it first.

Terms of Service

1. General Provisions
1.1. These Terms of Service (the “Agreement”) govern the relationship between the Operator (“OneCodeRegister”, “we”, “us”) and the User arising from the use of the code authorship fixation service available at OneCodeRegister.io (the “Service”).
1.2. Use of the Service constitutes the User’s full and unconditional acceptance of this Agreement.

2. Scope of the Service
2.1. The Service allows registration of a digital fingerprint (SHA-256 hash) of code files, followed by triple anchoring: in the Service’s database, with a TSA timestamp (RFC 3161), and on the Polygon blockchain.
2.2. The source code is never transmitted to the Service’s servers and is not stored. It is mathematically impossible to reconstruct the source code from the hash.
2.3. The Service is provided free of charge on a non-commercial basis.

3. User Rights and Obligations
3.1. The User warrants that they own all necessary rights to the code they register.
3.2. The User is solely responsible for keeping the source code safe.
3.3. The User shall not use the Service to register malicious code, materials that violate any applicable law, or third-party works without permission.

4. Operator Rights and Obligations
4.1. The Operator shall maintain the functionality of the Service and preserve registration records.
4.2. The Operator may amend this Agreement by notifying Users via the website.
4.3. The Operator shall not be liable for the User’s loss of source code or the impossibility of reconstructing it from the hash.

5. Disclaimer of Warranties and Limitation of Liability
5.1. The Service is provided “as is”. The Operator does not guarantee that registration with the Service will be recognised as conclusive proof of authorship in any particular court or jurisdiction.
5.2. To the maximum extent permitted by law, the Operator shall not be liable for any direct or indirect damages arising from the use or inability to use the Service.
5.3. In case of abuse, the Operator reserves the right to block access to the Service.

6. Miscellaneous
6.1. This Agreement shall be governed by the laws of the Russian Federation.
6.2. All disputes shall be resolved through a claims procedure; if no agreement is reached, in court at the Operator’s location.
6.3. If any provision of this Agreement is held invalid, the remaining provisions shall remain in full force and effect.

Published: April 2, 2026

Privacy Policy

1. General
1.1. This Privacy Policy describes how the Operator (“OneCodeRegister”) collects, uses, and protects User data when using the Service.
1.2. By using the Service, the User consents to the processing of their data as described in this Policy.

2. What Data We Collect
2.1. When registering a file, the Service receives the SHA-256 hash of the file, metadata (file name, size, date/time of registration), the User’s IP address, and, if provided, the email address (for sending the certificate).
2.2. The source code and file contents are never transmitted or stored.
2.3. Anonymised technical data may be transmitted to TSA and blockchain services as necessary.

3. Purposes of Data Processing
3.1. To provide the Service’s functionality (registration, certificate issuance, verification).
3.2. To improve the quality and security of the Service.
3.3. To comply with legal requirements.

4. Disclosure of Data to Third Parties
4.1. Data is not sold or shared with third parties except as required by law or as necessary for the operation of the Service (e.g., sending requests to TSA services, publishing the hash on the blockchain).
4.2. Only the hash is published on the blockchain, with no link to personal data.

5. Data Storage and Security
5.1. Data is stored on servers located within the Russian Federation. Organisational and technical measures are taken to protect against unauthorised access.
5.2. Retention period: for the duration of the registration plus five years after possible deletion to comply with legal obligations.

6. User Rights
6.1. Users may request information about their data and ask for corrections or deletion by contacting [email protected].
6.2. Deletion may be restricted if it conflicts with legal requirements or undermines the evidentiary value of already issued certificates.

7. Changes to This Policy
7.1. This Policy may be updated. The current version is always available on the website.
7.2. Continued use of the Service after changes constitutes acceptance of the updated Policy.

Published: April 2, 2026

Cookie Policy

1. What are cookies
Cookies are small text files that a website stores on your device to ensure proper functionality, improve user experience, and collect statistics.

2. What cookies we use
2.1. Strictly necessary cookies: ensure basic functionality of the site (e.g., session state). Without them, the Service cannot operate.
2.2. Analytical cookies: used to collect anonymised statistics via services such as Yandex.Metrica. This data helps us improve the site.
2.3. We do not use advertising or third-party targeting cookies.

3. Managing cookies
You can disable cookies in your browser settings. However, this may affect the functionality of the Service (e.g., inability to register code).

4. Retention period
Technical cookies are stored until you close your browser; analytical cookies are retained according to the policies of the respective services (usually up to 2 years).

5. Consent
By using the Service, you consent to the use of cookies in accordance with this Policy. If you do not agree, please disable cookies in your browser or leave the site.

Published: April 2, 2026

Disclaimer

1. Legal nature
The “OneCodeRegister” Service provides a tool to record the existence of code at a specific point in time and does not constitute legal advice. The User is solely responsible for assessing the sufficiency of the evidence obtained to protect their rights in court or before other authorities.

2. Limitation of liability
2.1. The Operator does not guarantee that registration with the Service will be recognised as conclusive or sufficient evidence of authorship in any particular court, arbitration, or before third parties.
2.2. The Operator shall not be liable for any direct or indirect damages, including lost profits, arising from the use or inability to use the Service, even if the Operator has been advised of the possibility of such damages.
2.3. The Operator shall not be liable for actions of government authorities, internet service providers, technical failures of the blockchain or TSA services that may affect the availability or evidentiary value of records.

3. Blockchain‑related risks
Using the public Polygon blockchain means that the record of the hash is irreversible and public. The User assumes all risks associated with decentralised technologies, including but not limited to possible forks, protocol changes, or loss of access to data by the Operator.

4. Information accuracy
We strive to ensure the Service operates correctly but do not guarantee error‑free or uninterrupted operation. If you discover errors, please report them so we can address them promptly.

5. Governing law
This disclaimer is governed by the laws of the Russian Federation and does not limit consumer rights established by law.

Published: April 2, 2026