Site and first-season licence terms

Scope and agreement

These Terms apply to relay-project.com and access to the first season through a one-time code. Viewing the site alone does not create a licence. An agreement arises when the user separately accepts these Terms, the Privacy Policy, and the 18+ notice on the access page.

The edition shown at the time of access may be stored with a version identifier, language, acceptance time, and a technical fingerprint of the published document or an immutable snapshot link. The stored edition applies after the site changes.

The Organiser

The site and project are administered by an individual operating from Georgia (the “Organiser”). The Organiser's identification number is 300448870.

The Organiser's name is not published on the site. Confirmation of identity and authority is provided on request sent to relayproject.ai@gmail.com. The address is also used for support, recovery, and licence enquiries.

First-season licence

One licence

One licence creates one first-season team. A team may have no more than five participants.

Key term

An activation key may be used for 12 months after issue. An unused key does not extend that period automatically.

Licence term

The licence to the first-season content is perpetual, subject to these Terms and mandatory applicable law.

Online access

After activation, the first-season online service is guaranteed for at least 24 months. If the service closes, the team receives an export or offline completion kit in advance.

Content version

A compatible delivery version is fixed when the licence is created. A later site or service change does not move the licence to an incompatible version automatically.

Codes and access

An activation code, invitation code, and protected link have different purposes. A one-time code is used for one licence and does not become a key for unlimited teams.

• an activation key creates or claims one team once
• an invitation code adds a participant to an existing team
• a protected link confirms an address and helps restore access
• the starter archive alone does not transfer a licence

Do not forward an activation key, invitation code, recovery code, or protected link. The project does not ask for them in a support email and does not put open secrets into mail analytics.

Access and service messages

To request access, the user provides an email, accepts the documents through separate checkboxes, and enters a one-time code. The service checks the code, creates a technical record, and starts issue of the licence described by the terms. A repeated request should not create a second licence or team.

Confirmation, protected links, recovery, security messages, and mandatory notices are service communications. Email is not added to news automatically. The link leads to a protected page and does not put the full secret in the subject line or message body.

18+ rule

A user requesting access must be an adult and separately confirm that they are at least 18. Every invited participant must also be at least 18. One person's confirmation is not consent for another person.

The invitation repeats the 18+ restriction before the participant joins and requires a separate confirmation. A date of birth and document copy are not requested.

If the age requirement is breached, the Organiser may refuse access or revoke the licence subject to applicable law.

Delivery and first launch

The protected page shows the fixed delivery version, activation key, starter archive, instructions, and diagnostics. The archive matches the fixed version and does not contain the activation key.

The user follows the published launch instructions. Before access is requested, the project describes technical requirements, including a compatible application, third-party programs, or APIs where required.

Recovery and revocation

Before activation

A lost key may be invalidated and reissued for the same licence through a protected request. No new team is created.

After activation

Restoring access does not reset saved results or create a second licence.

Licence revocation

After confirmed revocation, the key and licence no longer provide access. The project does not delete local files on the user's computer.

A recovery or revocation request may be sent through the protected page or to relayproject.ai@gmail.com. The project may request minimal proof of control of the access record.

Intellectual property

Exclusive rights in original RELAY materials — text, story, characters, tasks, names, illustrations, presentation, and original code — belong to their author or are used lawfully by the project. Third-party materials retain their own licences and rightsholders.

Work a user creates during the course belongs to that user to the extent exclusive rights arise. This is subject to rights in third-party materials and the terms of services used to create the work. Rights in RELAY materials and the teaching structure remain with the project.

Without written permission, you may not copy or republish materials in full or substantial parts, use them in another product, create derivative works from the story or course structure, or present the RELAY name and presentation as your own project.

Without separate permission, you may mention the project, quote a short excerpt with a link to relay-project.com, and share a link to the site.

Third-party services and programs

The course may require third-party programs, APIs, and other services. Each service has its own terms and privacy policy; the user accepts them directly and is responsible for following them.

RELAY is not affiliated with third-party rightsholders and does not promise the availability, pricing, or compatibility of external services beyond the description expressly provided.

Acceptable use

When using the site and the provided service, you must not:

• bypass protection, scan services, or interfere with their operation
• attempt to reuse one one-time code or send automated requests
• publish keys, recovery codes, or private links
• impersonate the project, the Organiser, or another user
• use RELAY for unlawful, harmful, or rights-infringing activity

Security exercises concern the user's own local learning environment, not attempts to attack the site or the provided service.

Availability and liability boundaries

The site and service are provided in working form but may be temporarily unavailable for updates, protection, diagnosis, or supplier failures. The project does not guarantee uninterrupted operation of third-party programs, APIs, email, or networks.

To the extent permitted by law, the project is not liable for indirect loss, lost profit, or data loss caused by a third-party service or use of the site outside these Terms. This does not limit liability for intent, gross negligence, or consumer rights that cannot be limited by agreement.

Changes and versions

The project may update the site and these Terms for future access requests. The accepted edition is not silently replaced: a version identifier, language, acceptance time, and a hash of the published document or immutable snapshot link may be retained.

If a change affects an issued licence or a material access method, the Organiser publishes a clear notice and applies mandatory law. The edition in force is dated 24 August 2026.

Governing law and contact

These Terms are governed by the law of Georgia. Disputes are heard by a competent court under applicable jurisdiction rules; this wording does not limit mandatory user rights or a right to choose a court where the law provides one.

Before going to court, the parties may try to resolve the matter at relayproject.ai@gmail.com. Identify the access address and the operation you want.