RELAY
Back to site

ENG/РУ

PRIVACY POLICYLast updated 24 August 2026

Privacy Policy

This Policy describes processing when you use relay-project.com, contact the project, or request access to RELAY materials. Visit analytics is enabled only after a separate user choice.

CONTENTS
  1. 01Person responsible for processing
  2. 02Data we process
  3. 03Requesting access
  4. 04Website data and enquiries
  5. 05Cookies and browser storage
  6. 06Analytics and consent
  7. 07Purposes and legal bases
  8. 08Recipients
  9. 09International processing
  10. 10Retention periods
  11. 1118+ rule
  12. 12Your rights
  13. 13Processing restrictions
  14. 14Policy changes and versions
01

Person responsible for processing

The site and the personal-data processing function 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 public site. Confirmation of identity and authority is provided on request sent to relayproject.ai@gmail.com. Data-subject requests and service enquiries use the same address.

Georgian personal-data law applies to the processing. GDPR applies to the extent that the relevant processing falls within its territorial scope.

02

Data we process

The data we process depends on what you do on the site. We aim to collect only what is needed to operate the service, provide support, maintain security, and perform the function you choose.

Contact data
An email address and any name in a signature, if you provide them when contacting the project or requesting access.
Access data
A record identifier, access state, content version, licence details, and a protected link. Secret values are stored securely and do not enter ordinary logs.
Accepted documents
Versions of the terms and policy, language, acceptance time, and a technical fingerprint of the published edition.
Technical data
Request time, page, response, error indicators, minimal browser information, and network signals needed to operate, diagnose, and protect the service.
Messages and materials
The contents of a message or materials you voluntarily send to the project, used only to reply, provide support, or perform the relevant service function.
03

Requesting access

When access is requested, the service may ask for an email, a one-time code, and separate confirmations of the documents. It checks the code, records the accepted editions, and provides the result described by the terms. Repeating a request should not create duplicate access.

A protected link is used for address confirmation, recovery, and mandatory service messages. We do not add an address to news or use it for advertising without a separate request.

04

Website data and enquiries

When you contact the project by email, the Organiser receives the sender's address, any name in the signature, and the message only after you send it yourself. They are used for replies, support, recovery, and mandatory notices.

Site responses do not reveal to an unrelated person whether a particular address exists in the system. We may request minimal proof of control of an address to locate a record.

05

Cookies and browser storage

The site uses strictly necessary technologies and, when allowed, analytics technologies. Necessary technologies display pages, protect them from automated traffic, and remember selected settings. They are not used for advertising.

Security cookie
A short-lived cookie that helps distinguish a normal request from an automated one and protects the site from abuse. It is independent of the analytics choice.
Analytics cookies
Cookies with a pseudonymous browser identifier. They are set only after analytics is allowed and may last up to two years unless consent is withdrawn or browser data is cleared sooner.
Choice storage
A localStorage record keeps the analytics choice in the browser and is not automatically sent to the server.
06

Analytics and consent

On the first visit a panel offers “Allow” or “Not now”. Before analytics storage is allowed, only limited technical signals needed for the panel and its choice may be sent.

After “Allow”, an analytics service receives the consent status and visit information. Possible data includes pages opened, session duration, device type, browser, language, screen resolution, and an approximate region.

Advertising identifiers, advertising personalisation, message contents, and access secrets are not sent to analytics. Consent can be withdrawn through the “Analytics settings” link in the footer; the site deletes accessible analytics cookies and reloads the page.

07

Purposes and legal bases

Site operation and access
Contact data, access records, and accepted documents are needed to perform the selected function and the agreement.
Support and service messages
Email is used for replies, confirmation, recovery, security messages, and mandatory notices.
Security and audit
Technical records help prevent abuse, repeated code use, errors, and loss of the accepted document edition.
Analytics
Visit data is processed only after a separate user choice.
08

Recipients

Hosting and security provider
Delivers pages, technical protection, security logs, and infrastructure services.
Transactional email
Sends confirmations, protected links, and mandatory service messages.
Analytics service
Receives limited visit data only after user consent.
Backup storage
May retain encrypted copies for a limited recovery period.

We do not disclose data to third parties for their own purposes or marketing. Disclosure outside these categories occurs only when required by law or supported by a separate legal basis.

09

International processing

The Organiser is in Georgia. Hosting, email, analytics, and backup suppliers may process data in Georgia, the European Economic Area, the United States, and other jurisdictions named in their current documents and settings.

For external suppliers, contractual safeguards, processing locations, subprocessors, and deletion duties are recorded. You may request the relevant supplier and transfer basis at relayproject.ai@gmail.com.

10

Retention periods

Access records and accepted documents
Kept for the period needed to provide access, support users, resolve disputes, and meet mandatory requirements.
Protected links
Stored securely until used or until their short validity period expires, then deleted or reduced to a minimal audit record.
Email and enquiries
Kept for the minimum period needed to reply, deliver service messages, and provide support.
Technical logs
Kept only for the scope and period needed for security, diagnosis, and audit.
Backups
Deletion from the working system does not mean immediate deletion from an encrypted copy. Backups are cleared under a limited recovery schedule.
11

18+ rule

A user requesting access confirms that they are at least 18. A confirmation by one person does not replace a separate confirmation by another person.

The 18+ confirmation is a separate unchecked box. The wording version, language, and time are stored; the service does not collect a date of birth, document photo, or identity-document copy.

If a minor nevertheless sends data, a parent or legal representative may write to relayproject.ai@gmail.com to request deletion.

12

Your rights

Within the limits provided by Georgian law and, where applicable, GDPR, you may ask for:

  • access to your data and a copy of the accepted document versions
  • correction of inaccurate data
  • erasure of data
  • restriction of processing
  • objection to processing based on legitimate interests
  • your data in a portable format where the law provides for it
  • withdrawal of analytics consent without consequences for access

A request may be sent in free form to relayproject.ai@gmail.com. Identify the address concerned and the operation you want. If more information is needed to locate a record, we will request only what is necessary.

You may complain about processing in Georgia to the competent supervisory authority or a court. Where GDPR applies, you also retain the right to contact a competent European Union supervisory authority.

13

Processing restrictions

  • we do not disclose data for advertising or build marketing profiles
  • we do not add an email to news without a separate request
  • we do not send access secrets or message contents to analytics
  • we do not make automated access decisions about you
  • we do not use emails or access data to train models
14

Policy changes and versions

Before new forms, accounts, or collection methods go live, this Policy is updated. An operation may retain an edition identifier, language, acceptance time, and a hash of the published document or an immutable snapshot link.

The service preserves the edition shown to a person even after the website changes. The edition in force is dated 24 August 2026.

Last updated 24 August 2026

RELAY

Contact the projectrelayproject.ai@gmail.com

Top
ТелеграмИнстаграмТредс

© 2026 RELAY Project

Project organiser · Georgia · ID 300448870

Privacy PolicySite and licence terms