Our details

1. Purpose and status of this document

1.1. This document sets out the particulars of the person who provides domain name registration and maintenance services through the namespace.com.ua website (the "Provider", "we"), of the registries of the domain zones in which we provide services, and the details and contacts a counterparty needs in order to identify us, pay an invoice and submit a claim.

1.2. Publishing these particulars is an obligation of a seller under article 7 of the Law of Ukraine "On Electronic Commerce" No. 675-VIII. Article 11, part 11 of the same Law additionally requires an order confirmation to contain the name and place of business of the seller and the procedure for the receipt of claims — both of these are set out below in clauses 2.1, 4.1 and 9.

1.3. This document is not a self-standing contract and creates no obligations other than those provided for by the Terms of Service — for retail clients, the Distributor Agreement — for partners, and the Privacy Policy and Payments and Refunds — for both. It is an integral part of them as regards details, addresses and contacts, and the provisions of those documents on details and notices refer to it.

1.4. If this document and a contract diverge as to payment details, addresses or contacts, the particulars in this document apply, as being the more current. In all other respects the contract prevails.

2. Particulars of the Provider

2.1. The services are provided by:

2.2. We are not a legal entity. This does not limit the extent of our obligations under the contracts: an individual entrepreneur is answerable for obligations connected with its entrepreneurial activity with all of its property, save for property that by law cannot be levied against (article 52 of the Civil Code of Ukraine).

2.3. We are not the administrator of any domain zone and are not an operator of a register. Our status and its limits are described in section 6.

2.4. Licensing. The business activity of registering and maintaining domain names is not among the activities subject to licensing: the exhaustive list of such activities is set out in article 7 of the Law of Ukraine "On the Licensing of Types of Business Activity" No. 222-VIII and does not include this activity. We therefore give no licence particulars of the kind required by the sixth paragraph of part one of article 7 of the Law of Ukraine "On Electronic Commerce" No. 675-VIII — the law provides for no licence for this activity. The registrar accreditation described in section 6 is not a licence: it is granted under a contract with the administrator of a domain zone, not by a licensing authority.

3. Taxation system and settlement documents

3.1. We pay the single tax of group three at the rate of 5 per cent of income (clause 293.3 of article 293 of the Tax Code of Ukraine) and the military levy at the rate of 1 per cent of income (clause 16-1 of subsection 10 of section XX "Transitional Provisions" of the Tax Code of Ukraine). Together this is 6 per cent of income; where "6 %" is mentioned in our materials, it means precisely the sum of these two payments and not a third rate.

3.2. We are not registered for value added tax. All prices are stated exclusive of VAT; VAT is not charged on them and is not included in the price. We do not issue VAT invoices — the tax documents that entitle a buyer to a VAT credit in Ukraine, and no VAT credit arises for a counterparty on transactions with us. Counterparties that are themselves VAT payers should take this into account.

3.3. The particulars of whether taxes are included in the price are given in fulfilment of the requirement of the seventh paragraph of part one of article 7 of the Law of Ukraine "On Electronic Commerce" No. 675-VIII. Part one of that article is divided into paragraphs, not into numbered clauses: the first paragraph is the introductory sentence, and the particulars it lists are the second to eighth paragraphs.

3.4. The fact that services have been provided may be evidenced by an invoice signed by the Provider, without drawing up a bilateral act of services rendered (a services-rendered certificate, the primary accounting document customarily signed by both parties in Ukraine) — such a procedure is permitted by article 9 of the Law of Ukraine "On Accounting and Financial Reporting in Ukraine" No. 996-XIV, in the wording of the Law of Ukraine No. 4791-IX in force from 1 April 2026, on condition that it is agreed by contract and that the document contains the date or period of provision of the services. The list of settlement documents, the procedure for generating them and their retention period are set out in the document Payments and Refunds.

3.5. A settlement document (fiscal receipt) is issued in the cases where the obligation to issue one is imposed by the Law of Ukraine "On the Use of Cash Registrars in Trade, Public Catering and Services" No. 265/95-VR — in particular on payment using an electronic payment instrument. A transfer of money directly to the Provider's bank account is not a settlement operation within the meaning of that Law, and no fiscal receipt is issued for it. The list of payment methods available on this site is set out in clause 5.4; as at the date of this edition none of them is a payment using an electronic payment instrument, so no obligation to issue a fiscal receipt arises for us.

4. Addresses

4.1. Place of state registration and correspondence addresses:

Both addresses are given because the third paragraph of part one of article 7 of the Law of Ukraine "On Electronic Commerce" No. 675-VIII requires an individual entrepreneur to publish both the place of registration and the place of actual residence, and a postal address for correspondence does not substitute for that requirement.

4.2. Paper correspondence, in particular claims and procedural documents, should be sent to the postal address. Correspondence sent to the address of state registration is deemed delivered, but we do not guarantee the time of its actual receipt.

4.3. We do not have an office open to visitors without prior arrangement. Meetings in person take place only by arrangement through the contacts set out in clause 8.1.

5. Banking details

5.1. Hryvnia account. Details for payment in hryvnia:

The account is identified by the IBAN, and the beneficiary's name is not the identifier. The name above is the English rendering of a name entered in the Ukrainian state register in Ukrainian; a payment reaches the account on the strength of the IBAN, and a bank that asks for the name in the form its own register holds will show that form itself once the IBAN is entered. If a payment is nevertheless returned because of the spelling of the name, write to the financial address in clause 4.2 and we will send the exact string the register holds. | Foreign currency accounts | US dollars (SWIFT route) — IBAN UA543220010000026001380016956; euro (SEPA route) — IBAN GB55CLJU00997190498575; euro (SWIFT route) — IBAN UA093220010000026007380017562. The complete details of each of these three routes are set out in the "Foreign currency accounts" table in this same clause 5.1 |

Foreign currency accounts. We serve counterparties that settle in US dollars and in euro. An invoice issued in a foreign currency carries precisely the block of details that matches its currency; our document generator refuses to issue an invoice in a currency for which no details are configured, so a "neighbouring" account cannot end up on an invoice.

Each row of the table below is a complete set of details for one route: one row is all that is needed to make the payment, and no particular from any other row is required for it.

The beneficiary name must be copied letter for letter. For the SWIFT routes it carries the PE prefix; for the SEPA route it does not. The string must match exactly the one held by the beneficiary bank, otherwise the payment stops for investigation.

Bank charges on a transfer, in particular the fees of correspondent banks, are allocated as set out in the document Payments and Refunds; this clause contains the details themselves and establishes no rule on the allocation of such charges.

5.2. The payment reference should state the account identifier — it begins with the letters NSPC, for example NSPC-EXAMPLE — or the invoice number. Payments in hryvnia that arrive at the account set out in clause 5.1 and carry such a reference are credited to the Ledger Account automatically from the bank statement — within the time stated in clause 3.2 of Payment and Refunds, which is where that time is set. We do not guarantee the crediting time: when a payment reaches our account is decided by the paying bank, not by us. A payment without such particulars is credited by us only once we have established who the payer is; the crediting time in that case is not guaranteed.

5.3. The Ledger Account is maintained in hryvnia. The conditions on which money is credited, the procedure for converting payments made in another currency, and the moment from which a payment is deemed received, are set out in the document Payments and Refunds.

5.4. Payment methods available on this site: bank transfer to the accounts set out in clause 5.1 — in hryvnia, US dollars or euro, according to the currency of the invoice. We accept no other payment method: payment using an electronic payment instrument (a payment card) is not accepted on this site — neither directly, nor through a payment service or aggregator. The obligation to issue a settlement document (fiscal receipt) provided for by clause 3.5 therefore does not arise for us. If card payment is introduced, this page and clause 3.5 will be amended before the day it is introduced, not after.

6. Registrar status, contracts with the registries and domain zones

6.1. We are an accredited domain name registrar and act under contracts with the administrators of the relevant domain zones. We are not a zone administrator, are not an operator of a register and do not maintain a registration database: records in the register are created, changed and deleted solely by the registry.

6.2. We are not ICANN-accredited and are not a party to the Registrar Accreditation Agreement: .UA is a country code top-level domain (ccTLD), and the accreditation of registrars in it is carried out by the administrator of the domain, not by ICANN. ICANN's rules on registrars, domain name transfers and data escrow do not apply to our services in the .UA zone.

6.3. Two different kinds of contract. The right to work in a particular domain zone comes from a contract with the administrator of the relevant public domain, while technical access to the registration system comes from a separate contract with the operator of the register. Both kinds are therefore set out below.

Contract with the operator of the register:

A contract with the Operator of the Register opens access to the registration system and opens no zone at all. The list of public domains in which a registrar has the right to perform operations is determined by the administrators of those domains on the basis of contracts in force with the registrar and passed by them to the Operator of the Register; an application is processed only where such a contract exists and the administrator has permitted the operation concerned.

Contracts with the administrators of the public domains:

This table carries one row for every DIRECT contract with an administrator of a public domain. It is not a list of every zone we serve: some of them we serve otherwise than under a direct contract with the administrator. The administrator of each individual zone is given on the zones page (https://namespace.com.ua/zones) — by zone, not by contract, because who sets the rules for a particular domain name is a fact about the zone; that list is complete for every zone we offer. The terms of all such contracts are confidential (clause 6.3.1) and are therefore not set out here; the only confirmation that a zone is served today is the Price List (clause 6.4). A new direct contract with an administrator is added to this table before the corresponding zone appears in the Price List (clause 6.4), not after. The list of persons to whom registrant data is actually passed is wider than this table and is set out in clause 4.3 of the Privacy Policy and in clause 13.4 of the Distributor Agreement.

A contract with an administrator is a necessary but not a sufficient condition: each individual operation in a zone additionally requires the administrator's permission (clause 6.4).

6.3.1. Confidentiality. The contracts listed in clause 6.3 classify as confidential all information relating directly or indirectly to them, and prohibit its disclosure without the written consent of the party concerned. We therefore publish only the fact that a contract exists and the party with whom it was concluded — what makes it possible to check our status — and publish neither the numbers and dates of the contracts nor references to their individual clauses, nor their price annexes, indexation formulas, exchange-rate coefficients, terms, grounds of termination or other conditions. In particular, we do not publish the amount a registry charges us for a specific operation in a specific zone (the cost), and we give no particulars from which it could be calculated. The prices we publish are the final prices of our services; their internal structure is confidential information of the registry, which owns it, not us.

Contract numbers are not published. The registries keep no public index against which a number could be verified, so a published number confirms nothing — our status is checked by the registrar identifier ua.tld in the registries' own lists, in WHOIS and in RDAP (clause 6.8). The number therefore adds no verifiability and discloses precisely what we undertook not to disclose. For the same reason we do not cite the clause numbers of the other party's contracts even when explaining why an obligation of ours arose: the obligation is ours and we state it, but the structure of someone else's document is not ours to publish.

6.4. The list of domain zones in which we actually provide services changes together with the zones in which we are accredited. The current list, with prices (the "Price List"), is published at https://namespace.com.ua/pricing. The current list of zones and of the operations available in each of them, together with the prices, is also shown in the Panel (clause 7.1) and supplied on request through the contacts in clause 8.1, and the rule set out below on the list being the only confirmation applies to that list.

A zone is included in that list solely where there is a contract in force with the administrator of the relevant public domain and that administrator has permitted the operations concerned; a contract with the operator of the register does not by itself confer the right to work in a zone (clause 6.3). A zone whose administrator contract has been terminated or suspended is removed from the list without delay.

The list is given operation by operation. For each zone it states separately whether the registration of a new domain name, the renewal of the registration term, the transfer from another registrar and the restoration after deletion are available. This is not a formality: the rules of some zones have discontinued new registration while leaving renewal, transfer and restoration of already registered domain names available, and in some zones only part of the operations is closed. Our system keeps these flags separately for each operation in each zone, so the Price List reflects the actual state of affairs and not an intention.

The presence of a zone and of a specific operation in that list is the only confirmation that we serve it today; a mention of a zone in any other material — on the home page, in examples in the contracts, in marketing materials — is not such a confirmation and creates no obligation to provide the service.

6.5. The registration of a domain name is subject to the Regulations of the registries, whose titles and addresses of publication are set out in clause 6.9. Those Regulations prevail over our documents in so far as the register itself is concerned, and are changed without our consent. In particular, section 11 of the Public Domain Regulations — the document named in the first row of the table in clause 6.9 — allows the Operator of the Register to amend it 30 days before the amendments take effect and, in a case of urgent necessity, simultaneously with their publication, that is with no notice period whatsoever. We therefore cannot give a counterparty a longer period of notice of changes than the one that applies to the register itself.

6.6. We do not guarantee the registration of any particular domain name. We undertake to transmit a duly completed application to the registry and to communicate its response. A right in a domain name arises only from the moment of confirmation by the registry. Under clause 6.4 of the Public Domain Regulations (clause 6.9), the time taken to process an application may not exceed 120 hours; during that time the outcome of the application is unknown and neither party can guarantee it.

6.7. Disputes over rights in domain names are heard in the manner provided for by the .UA Domain Name Dispute Resolution Policy (.UA-DRP), the Rules for that Policy, and the World Intellectual Property Organization Supplemental Rules for that Policy. All three documents are published by HOSTMASTER LLC at https://www.hostmaster.ua/policy/ua-drp/; the editions in force as at the date of this page are set out in clause 6.9. Disputes under that Policy are heard by the WIPO Arbitration and Mediation Center; a dispute may also be heard in court. We do not decide such disputes on the merits and are not a party to them; our role and the procedure for implementing decisions are described in section 16 of the Terms of Service and, for partners, in section 21 of the Distributor Agreement.

6.8. How to verify our status. Our registrar identifier is ua.tld. It is under that identifier that we appear in the register, in the public WHOIS and RDAP services, and in the lists of registrars published by the operator of the register and by the administrators of the public domains (in particular on the official website of the operator of the register, https://www.hostmaster.ua). Those lists are maintained by them, not by us, and it is against them that you should check whether we are an accredited registrar in a particular zone.

If the particulars in such a list diverge from those set out on this page, the ones published by the registry prevail, and we ask you to report the discrepancy through the contacts in clause 8.1. Bringing them into line is our obligation: we are required to provide full, true and accurate information about ourselves and to give notice of any change of our addresses, banking details and contact particulars without delay.

6.9. Regulations of the registries: full titles and addresses of publication. The documents listed below set the rules that govern the registration and maintenance of domain names. These documents are not adopted by us: each of them is adopted and amended by whoever publishes it. Each row of the table contains the full title of the document, the person who publishes it and the address at which it is published — so that the row can be used on its own, apart from the rest of the table, and in printed form.

The Regulations on the specifics of individual public domains that are not named in this table are listed in section 12 of the Public Domain Regulations themselves — at the address given in the first row of the table.

6.9.1. Which edition applies. The edition of a document that applies to an operation is the edition that was in force at the moment the operation was performed. We cannot guarantee, and do not guarantee, that an edition will remain unchanged: as stated in clause 6.5, in a case of urgent necessity amendments take effect simultaneously with their publication. The column "Edition in force as at the date of this page" is given for orientation and does not freeze the edition.

6.9.2. We keep dated copies. We keep dated copies of the editions of the documents listed in clause 6.9 that were in force at the moment operations on a counterparty's domain names were performed, and supply a copy of the edition concerned on request through the contacts in clause 8.1. Without this, a dispute arising two or three years later could not be resolved: the addresses of publication show only the current edition, and the registries do not keep earlier editions at those addresses. We keep and supply on request the editions of our own documents in the same way (clause 12.1).

6.10. The limits of the registries' liability. We publish these particulars in fulfilment of an obligation placed on us by the contracts with the Operator of the Register and with the administrators of the public domains:

6.10.1. The Operator of the Register cannot be joined as a party to court proceedings over domain names.

6.10.2. The administrator of the public domain and the Operator of the Register bear no liability for the consequences of the use, non-use or unlawful use of a domain name by the registrant, including as toward third parties, or for the registrant's infringement of any rights of third parties.

6.10.3. These two provisions were not laid down by us and not in our favour: they are laid down by the registries and concern the registries, not the Provider. The extent of our own liability is determined by the Terms of Service — for retail clients — and by the Distributor Agreement — for partners; this clause neither changes nor limits it.

7. Technical interfaces and identification of operations

7.1. The services are provided through the following interfaces:

7.2. The test environment (OT&E) is not production: operations in it do not create records in the register, do not give rise to rights in domain names, are not charged for, and the test data may be reset without notice. The test environment's data is stored separately from production data, and no calls to the registries are made from it — their responses are simulated.

7.3. The Operation Identifier. The response to every command carries two transaction identifiers.

7.3.1. The first is the identifier that the counterparty itself assigned to the command (technically, the clTRID element of the EPP protocol). We do not alter it and merely return it unchanged in the response, so its form is determined by the counterparty and not by us.

7.3.2. The second is the Operation Identifier: the identifier that we assign to the operation (technically, the svTRID element of the EPP protocol). It consists of the letters NSPC, the date and time at which the command was accepted in the format "year, month, day, hours, minutes, seconds", and a random number; the date and time in it are Kyiv time, the same time in which we show every date to a counterparty. The Operation Identifier is returned in the response to the command, is shown in the panel, and is repeated in the Message Queue message that delivers the result of an asynchronous operation (clause 7.4).

7.3.2.1. The number in the identifier is random rather than sequential. A sequential number shared by all counterparties would let each of them subtract two of their own identifiers and compute how many operations we had performed for the others in between. Counterparties compete with one another, the identifier is returned in the response to every command, and a counterparty's systems keep it — so such a number would disclose the volume of other parties' operations continuously, without the reader having to do anything. This is not an implementation detail we are free to change: the undertaking to include in this identifier no quantity from which the number or frequency of other counterparties' operations can be computed is given by clause 20.4.2 of the Distributor Agreement — this document is not an agreement and creates no obligations (clause 1.3).

7.3.2.2. The operation's record number. Besides the Operation Identifier we assign every command a record number — before it is performed — and use it to tie together everything that command causes: the requests to the registry operators, the queued job and the movements of funds. It is the number set out beside every debit in the itemisation of operations, so a counterparty holds it even when it did not keep the response to the command.

7.3.3. An enquiry, a claim or a dispute about a debit should quote the Operation Identifier under clause 7.3.2 — the one that arrived in the response to the command — or the operation's record number under clause 7.3.2.2, the one printed beside the debit. Both point to the same operation, either finds it unambiguously, and quoting one is enough. We accept the identifier assigned by the counterparty under clause 7.3.1 in addition, but it may not be sufficient on its own to find an operation: it is not unique in our systems, because the counterparty chooses it.

7.3.4. The command we send to a registry operator in connection with an operation carries an internal reference of our own. We do not describe how it is built: it is our own record-keeping, and only two things about it concern a counterparty. First, it is the reference by which the registry operator finds the operation in its own logs, so we disclose it on request when a matter has to be taken up with that operator. Second, it does not name the counterparty (clause 7.3.4.1).

7.3.4.1. A registry operator cannot tell from our commands who our counterparty is. Registry operators keep the identifiers they receive in their logs permanently and work in the same market as our counterparties, so a counterparty's name or account in that field would disclose to them both who our counterparty is and how many operations it performs. We do not do that: within the internal reference the counterparty is denoted in a way only we can match back to them. This costs the reference nothing — when a registry operator cites one, we do the matching.

7.4. Operations are performed asynchronously. If the registry responds slowly, the command is accepted into a "queued" state and the result arrives as a separate message through the Message Queue — the queue from which a counterparty receives the results of operations; technically it is implemented by the poll command of the EPP protocol — or is shown in the panel. Acceptance of a command is not a confirmation of the registration, renewal or transfer of a domain name. An unread message stays in the queue and remains available to be read for 30 days. The record itself — read or not — is kept for 1,095 days, that is three years, which is the general limitation period under article 257 of the Civil Code of Ukraine, and is evidence of delivery whether or not the message was ever read.

7.5. Every operation is recorded in the tracing logs. We use those records to consider enquiries and claims. The retention period of the tracing logs is 7 days: they are an operational record, not an evidential one. The evidential record is the EPP frame log, from which the content of a command and the registry's response are established; it is retained for 1,095 days — that is three years, which is the general limitation period under article 257 of the Civil Code of Ukraine (clause 7.2 of the Privacy Policy). The manner in which such records are used as evidence in a settlement dispute is established by the relevant contract.

8. Contacts

8.1. Addresses for enquiries:

8.2. The email channel to the support service is available round the clock: enquiries are accepted at any hour of any day and are recorded at the moment they arrive. Round-the-clock acceptance is our obligation under the contract with the Operator of the Register and does not depend on the processing schedule. Enquiries are processed Monday to Friday from 09:00 to 18:00 Kyiv time, excluding days declared non-working in Ukraine. An enquiry received outside that schedule is deemed received at the moment it arrives and is processed from the beginning of the next period stated in the preceding sentence. That schedule does not extend to abuse reports: those are handled in the manner set out in clause 8.3, including round the clock as regards reports of an immediate threat. We undertake no separate obligation as to response time, other than the periods expressly established in our documents (in particular clauses 8.3 and 9.3). We conclude no individual service level agreements with particular retail clients: the Terms of Service are a public contract under Ukrainian law — one the provider undertakes to conclude with anyone who applies whose terms are established identically for everyone (clause 3.13 of those Terms). If a service level undertaking is introduced, it is published together with the tariffs and applies to everyone who meets the published criteria. Separate service level terms are possible only within the Distributor Agreement, which is not a public contract (clause 1.5 of that Agreement), and on terms identical for all Purchasers (clause 1.5.1 of the same Agreement).

8.3. Abuse reports are accepted at the address stated in clause 8.1, from any person, with no requirement to hold an account. We acknowledge receipt of such a report within 1 working day of the moment it is deemed received under clause 8.2, and consider it on the merits within 5 working days. Reports of circumstances that constitute an immediate threat — in particular reports of material depicting the sexual exploitation of children, of phishing, of the distribution of malicious software and of a threat to human life or health — are considered without delay, round the clock, and measures on them are taken no later than 24 hours from receipt. The grounds for and the procedure of suspending services following such a report are set out in the Terms of Service and in the Distributor Agreement.

8.4. We do not change our banking details by an email notice without publishing the change on this page. If you have received a notice in our name about a change of details through any other channel, check this page and verify the notice through the contacts in clause 8.1 before transferring any money.

8.5. Round-the-clock availability of the channels. The website on which this page and the rest of the documents in the Legal section are published is available round the clock. Enquiries are accepted by email at the addresses set out in clause 8.1 round the clock, without days off. The automated application intake and processing interfaces set out in clause 7.1 (EPP and the Panel) are available round the clock, with interruptions only for maintenance, of which we give advance notice. While a particular action is unavailable in the Panel, it is performed by email to the address in clause 8.1, and we do not place the consequences of that unavailability on the counterparty.

8.6. Enquiries from a registrant who ordered the domain name elsewhere. If a domain name is registered in your name but was ordered through one of our partners (a purchaser), you may contact us directly about that domain name — in particular in order to obtain the transfer code (AuthInfo) and move the domain name to another registrar. The address for such an enquiry is in clause 8.1. The state of settlements between you and the partner, or between the partner and us, does not affect that right, and you do not need to hold an account with us for it.

8.6.1. How we confirm that it is the registrant who is asking. One of two ways, whichever you prefer: a message from the e-mail address recorded in the contact particulars of that domain name, or a document signed with a qualified electronic signature. We ask for nothing more: no passport copies, no constitutional documents, and no explanation of why you want the transfer code — we neither request them nor keep them. If the address in the contact is no longer available to you, use the second way. This list is exhaustive and is set by clause 11.1.1.1 of the Distributor Agreement; it is repeated here because the person who will look for it is a registrant, not a party to that Agreement.

8.6.2. In zones where no transfer code exists. The rules of some domain zones do not provide for a transfer code. We then do not issue a code that does not exist; instead we assist with the transfer in the manner established by the registry operator of that zone, and we cannot refuse that assistance on the ground that the zone has no code.

The rules of some domain zones provide for no transfer code at all — in those zones a transfer to another registrar is effected without a code, in the manner established by the registry. We say so on request and do not refuse to assist with a transfer on the ground that no code exists in that zone.

You may prove that you are the person in whose name the domain name is registered by any of the following means: an enquiry from the email address stated in the contact particulars of that domain name; an application signed with your qualified electronic signature (clause 10.3); for a legal entity — a letter signed by an authorised officer with that officer's qualified electronic signature. We do not require proof beyond what is indispensable for performing the action concerned.

9. Procedure for enquiries and claims

9.1. A claim is submitted in written form to the address for legally significant notices (clause 8.1) or to the postal address (clause 4.1). The procedure for the receipt of claims is set out in fulfilment of part eleven of article 11 of the Law of Ukraine "On Electronic Commerce" No. 675-VIII, which requires a confirmation of an electronic transaction to contain the name of the seller (provider), its place of business and the procedure for the receipt of claims. That part consists of an introductory sentence and four unnumbered paragraphs; it contains no numbered clauses.

9.2. A claim must contain: the particulars of the applicant and the means of contacting it; the account identifier or EPP login; the substance of the demand; the date and time of the event; the Operation Identifier (clause 7.3.2), if the claim concerns a specific operation; a calculation of the amount, if the demand is monetary; and copies of supporting documents. A claim from which the operation or the account cannot be established is considered once the applicant has supplied those particulars.

9.3. The period for considering a claim is 30 calendar days from the day it is received. That period is neither extended nor restarted because a response from the registry is needed: clause 24.1 of the Terms of Service and clause 21.2 of the Distributor Agreement provide for no extension, and this page is not an agreement (clause 1.3) and cannot give itself a longer one. If the registry has not answered by the time the period expires, we answer within the period with what we have and say what we are still waiting for.

That period is the maximum across all our documents and matches the period in clause 24.1 of the Terms of Service and in clause 21.2 of the Distributor Agreement. For claims concerning payment and refunds, clause 13.1 of the document Payments and Refunds establishes a shorter initial period — 14 calendar days — which is extended to the same 30 calendar days where a response from the registry is needed. The shorter period operates in the applicant's favour and does not contradict this clause.

9.4. Where the services have been ordered by a natural person for its own needs not connected with entrepreneurial activity, that person is a consumer within the meaning of article 1 of the Law of Ukraine "On Protection of Consumer Rights" No. 1023-XII and additionally has the right to apply to the central executive authority that implements state policy in the field of state control over compliance with consumer protection legislation, or to a court.

The Law of Ukraine "On Protection of Consumer Rights" No. 1023-XII ceases to have effect on the day the Law of Ukraine "On Protection of Consumer Rights" No. 3153-IX enters into force (clause 3 of section IX "Final and Transitional Provisions" of Law No. 3153-IX). Law No. 3153-IX itself enters into force one year after the day of its publication, but not earlier than the day martial law is terminated or lifted (clause 1 of the same section IX). From that day, every reference on this page to Law No. 1023-XII is to be read as a reference to the corresponding provisions of Law No. 3153-IX, and the extent of a consumer's rights is determined by Law No. 3153-IX. We undertake to bring this page and the rest of our documents into conformity with Law No. 3153-IX before the day it enters into force.

9.5. Submitting a pre-action claim is not a mandatory precondition of applying to a court and does not limit the right to judicial protection (article 55 of the Constitution of Ukraine, article 16 of the Civil Code of Ukraine). For counterparties that order services in connection with carrying on entrepreneurial activity, whether a pre-action procedure is mandatory, and its time limits, are determined by the relevant contract.

9.6. Claims concerning the processing of personal data are considered in the manner set out in the Privacy Policy. This does not deprive the data subject of the right to apply to the Ukrainian Parliament Commissioner for Human Rights.

10. Legally significant notices

10.1. The parties send legally significant notices to the addresses set out in clauses 4.1 and 8.1, and we send them to a counterparty at the email address stated in its account and by a notice in the panel. The counterparty is obliged to keep the address in its account up to date; it bears the consequences of not receiving a notice because of an outdated address.

10.2. A notice sent by email is deemed received on the working day following the day it was sent, unless the sender has received a non-delivery report. The same period is established by clause 17.4 of the Distributor Agreement; for retail clients, clause 23.2 of the Terms of Service establishes the next calendar day. This presumption does not deprive the recipient of the right to prove that the notice was in fact not delivered.

10.3. We accept documents signed with a qualified electronic signature, under the Law of Ukraine "On Electronic Identification and Electronic Trust Services" No. 2155-VIII. Such documents have the same legal force as documents signed by hand. Such a document is sent by email to the address in clause 8.1, together with the signature file or in a format that contains the signature inside it. We use no separate electronic document exchange services and require no registration in any of them; a signature received is verified by us on the official qualified electronic signature verification service.

10.4. A one-time identifier as a means of signing an electronic transaction (article 12 of the Law of Ukraine "On Electronic Commerce" No. 675-VIII) is not used: acceptance is effected by the actions set out in clause 3.4 of the Terms of Service, and we neither send nor require a one-time code for that purpose. If you have received a one-time code in our name to confirm an order, it is not a message from us; please report it through the contacts in clause 8.1.

11. Language

11.1. The language of the contract is Ukrainian (part 14 of article 11 of the Law of Ukraine "On Electronic Commerce" No. 675-VIII). The stipulation that the Ukrainian version of this and of the other documents in this section is the only authentic one, and that in the event of a discrepancy it is the version that applies, is our own stipulation and not a requirement of the law: the provision cited requires the state language but does not establish the primacy of one language version over another.

11.2. The language of service is Ukrainian (article 30 of the Law of Ukraine "On Ensuring the Functioning of the Ukrainian Language as the State Language" No. 2704-VIII). At a counterparty's request, service may be provided in English or Russian. The documents in the Legal section are published in the same three languages, the Panel interface works in them, and the system's notifications are sent in them. The language of the EPP session is selected separately and does not affect the language of service (clause 11.3).

11.3. The language of the messages the system sends is configured separately for each account and does not depend on the language of the EPP session.

12. Changes to these particulars

12.1. The edition in force is the one published on this page; its number and date are given in the heading of the document. We keep every previous edition of this page and publish them here: https://namespace.com.ua/legal/archive — at the same address as the editions of the other documents in the Legal section (clause 22.7 of the Terms of Service), stating for each edition its number and the period during which it was in force. We send any edition by email on request to the contacts in clause 8.1. The edition in force at the moment a contract was concluded remains available to the counterparty throughout the term of the contract and for three years after its termination.

12.2. We give notice of a change of banking details by publishing it on this page and by a notice to the email address stated in the account, no later than 10 calendar days before the day from which the new details take effect, except where the change occurs for reasons beyond our control (in particular through the acts of a bank) — in which case the notice is sent without delay after we become aware of it.

12.3. Money transferred to the details in force on the date of payment is deemed to have been paid properly. Money that has in fact arrived at the previous details is credited by us to the counterparty's ledger account.

12.4. Changes brought about by changes to legislation or to the rules of the domain zones take effect at the same time as those changes, even if the period under clause 12.2 has not elapsed. We cannot give a longer period than the one given to us by a registry or by the law.