Terms of Service

These terms govern the use of the Anyname Hotel software ("the Service") by the hotel or company that holds the licence ("the Property"), including everyone the Property gives a login to.

The Property's owner account accepts these terms on behalf of the Property and every staff account it creates.

The Service is licensed, not sold, for the licence period agreed with the Property. Access is granted per staff account with a role (owner, manager, accountant, reception, housekeeping) that limits what that person can see and do.

The Property is responsible for keeping logins confidential, for removing accounts when staff leave, and for everything done under its accounts.

There is no public self-signup: accounts exist only where we have created them for a Property.

•Share a login between people, or resell or sublicense the Service.

•Copy, decompile or reverse-engineer the software, or attempt to reach another Property's data.

•Use the Service to store data unrelated to running the property, or to break any law that applies to the Property.

The Property decides what guest data goes into the Service and why; it is the data controller for that information. We process it on the Property's instructions as its processor (see the Privacy Policy).

Turkish law requires accommodation providers to report guest identities to the authorities. Where the Property enables the KBS integration, the Service transmits the identity data the Property entered to the Property's own KBS account. Accuracy, timeliness and the legal duty itself remain with the Property.

The Property must have a lawful basis for the guest data it records, must not enter more than it needs, and must handle guest requests about that data (it can act on them directly inside the Service).

We aim to keep the Service available continuously, but it can be interrupted by maintenance, hosting incidents or events outside our control. Where an interruption is planned, we give notice where we reasonably can.

Support is provided by the contact channel agreed with the Property.

Fees and the length of the licence period are set in the written agreement or offer accepted by the Property; they are not published inside the Service.

The price agreed for a licence period is fixed for the whole of that period. We do not raise it in the middle of a period the Property has already paid for.

We may set a different price for the next period. We tell the owner account in writing at least 30 days before the current period ends. If the Property does not accept the new price it may let the licence lapse at the end of the current period and export its records first; using the Service after a new period has begun means the new price is accepted.

A licence does not renew automatically unless the agreement expressly says so. Where the agreement does provide for automatic renewal, the Property may stop the renewal by telling us before the current period ends.

If a licence expires, or is suspended because an invoice is unpaid, staff logins stop working. The Property's data is then kept for 90 days from the date of expiry so that renewing restores it intact. After those 90 days we may delete it; we write to the owner account before we do.

Rooms, guests, reservations, folios, payments and reports entered by the Property remain the Property's data. We claim no ownership of it and do not use it to build products for anyone else.

The Property can read, search and print its records from inside the Service at any time while its licence is active. That needs no permission from us.

A bulk export — the whole database in one downloadable file — is a reviewed request. The Property asks from Settings → Export data and states what the export is for; we approve or refuse by hand and give the reason. An approval opens the download for a limited period, after which the Property may ask again. We review these because one file containing every guest record, identity number and payment is worth a decision, and because it lets us notice a request that does not come from the people who should be making it.

We will not refuse an export the Property needs to meet a legal duty — answering a data-subject request under KVKK or the GDPR, a court order, or a tax or regulatory audit. Say so in the request and it will be approved. Nor will we refuse one in order to make leaving harder: a Property that has given notice, or whose licence is ending, gets its data.

We may refuse where we cannot establish that the request came from the Property's own owner or manager, where an invoice is unpaid, or where the stated purpose is one we are not willing to assist with. A refusal is always given with its reason in writing.

The Property may stop using the Service at any time. To close the account it sends a deletion request from Settings → Account and property → Delete account.

Deletion is not immediate and is not automatic. We review each request by hand. If we approve it, a waiting period of 30 days begins at the moment of approval — not at the moment the request was sent. Throughout those 30 days the Service keeps working normally and the Property may cancel the request and keep everything. When the 30 days end, the account, its data and its staff logins are erased.

We may refuse a deletion request only where an invoice is unpaid, where the law requires the records to be kept, or where we cannot satisfy ourselves that the request came from the Property's owner account. We give the reason in writing.

Ending early does not refund the rest of the licence period. The licence is granted for a fixed period and the fee is earned for that period. Deleting the account, or simply stopping use, before the period ends does not entitle the Property to a refund, a credit or a transfer of the unused part, unless the written agreement says otherwise or the law requires it. The Property keeps full access, and can export its records, for whatever remains of the period it has paid for.

If we end the agreement for a reason that is not the Property's fault — for example we withdraw the Service — we refund the unused part of the current period, counted in whole months, and give reasonable notice and an opportunity to export data first.

We may suspend access where a licence has expired, where an invoice is unpaid, where use threatens the security of the Service, or where the law requires it. Suspension does not shorten or extend the licence period.

The Service is a record-keeping tool. It does not verify guest identities, calculate taxes, or discharge the Property's legal duties, and the Property is responsible for checking its own figures before relying on them.

To the extent the law allows, we are not liable for indirect or consequential loss, for lost profit, or for data the Property or its staff deleted themselves. Nothing here limits liability that cannot be limited by law.

We may update these terms; the current version always sits at this address with the date it took effect. Where a change materially affects the Property we tell the owner account before it applies.

These terms are governed by Turkish law, and the courts of İstanbul have jurisdiction, unless the agreement with the Property says otherwise.