
Service Annexes
Version: 1.0 · Effective: 16 Nov 2026
This English version is provided for convenience; in case of conflict the Turkish version prevails. These Annexes form an integral part of the Terms of Service ("ToS"). The general rules in the ToS are not repeated here; if an Annex conflicts with the ToS, the Annex applies with respect to the relevant Service (ToS s.2.2). Numerical limits (quota, speed, duration, fees) are shown on the product page and in the order summary unless otherwise stated.
| Annex | Scope |
|---|---|
| Annex 1 | Shared and reseller web hosting |
| Annex 2 | Türkiye virtual server (VDS), Managed Server, physical server |
| Annex 3 | Gyro Cloud servers, hourly prepayment and one-click applications |
| Annex 4 | Gyro Containers, Serverless, Pipeline and log retention |
| Annex 5 | Object Storage (S3) and Protected Storage |
| Annex 6 | Network services: private network (VPC), load balancer, Gyro DNS, network firewall |
| Annex 7 | Business Email |
| Annex 8 | Uptime Monitoring and status page |
| Annex 9 | Domain names |
| Annex 10 | Software licences |
| Annex 11 | API, command-line tool, Terraform provider and MCP server |
Annex 1 · Shared and reseller web hosting
1.1 Scope. Hosting of a website, database and e-mail accounts linked to that site on a shared server. Resource limits (disk, number of files, CPU, memory, concurrent processes, databases, scheduled tasks) are stated on the product page.
1.2 Fair use. When usage that blocks or noticeably slows the service of other customers on the shared server is detected, Gyro warns the Customer and, if necessary, limits the relevant process. If it continues, a move to a suitable plan is recommended.
1.3 Off-purpose use. Shared hosting is for hosting websites. Large file archives unrelated to the website, backup storage, file/media sharing services, bulk e-mail sending, cryptocurrency mining, proxy and background services cannot be hosted. Object Storage (Annex 5) is recommended for large files and backups.
1.4 E-mail. E-mail on shared hosting is a basic e-mail service linked to the site; because a shared sending infrastructure is used, inbox delivery at recipient servers is not guaranteed. For business-grade e-mail, Annex 7 applies. Hourly sending limits are stated on the product page.
1.5 Access. Shell (SSH) access is not offered on shared hosting.
1.6 Backup. For plans on whose product page backup is stated as included, the backup frequency and retention period are stated on the product page; restoration is done through the Customer Panel or by support request. In other cases ToS s.7 applies.
1.7 Reseller hosting. The reseller is the party to the agreement towards its own customers; it provides them with support and is responsible to Gyro for their content and for their use in compliance with these Terms. With respect to the reseller's customers, the reseller is the data controller and Gyro is the data processor (ToS s.13). Gyro forwards abuse complaints concerning the reseller's end users to the reseller; if the reseller does not take the necessary action within 48 hours, Gyro may suspend the relevant account.
1.8 Migration. The free migration assistance offered by Gyro is on a best-efforts basis; the backup of data on the source system remains with the Customer.
Annex 2 · Türkiye virtual server (VDS), Managed Server, physical server
2.1 Management responsibility. For VDS and physical servers, management, updating, security and backup of the operating system and the software on it belong to the Customer. Gyro is responsible for the hardware, the virtualisation layer and the network connection on which the server runs.
2.2 Managed Server. The tasks undertaken by Gyro in a managed plan (e.g. installation, operating system updates, control panel maintenance, monitoring) are listed on the product page. Tasks not on the list (application development, third-party software faults, etc.) are out of scope. For the managed Service, the Customer consents to Gyro staff accessing the server with administrator privileges.
2.3 Backup. Gyro has no backup commitment for VDS, Managed Server and physical servers; if a separate backup add-on has been purchased, the terms of that Service apply.
2.4 Traffic and port. On Türkiye VDS and Managed Server, traffic is subject to fair use; port speed is stated on the product page. An additional fee may be applied for prolonged continuous use close to line capacity (e.g. continuous streaming, large file distribution); before the fee is applied, the Customer is notified in writing and, if the Customer does not accept, the Customer reduces its usage or terminates without penalty.
2.5 Prohibited use. Providing proxy or VPN services to third parties on servers located in Türkiye is prohibited (Acceptable Use Policy §2).
2.6 IPv6. IPv6 addresses are not offered on Türkiye VDS unless stated on the product page.
2.7 Access credentials. In the event of a security incident or at the Customer's request, Gyro may reset the server administrator password; in that case it notifies the Customer.
2.8 Physical server. A physical server is allocated exclusively to the Customer. In case of hardware failure, Gyro replaces the faulty part within a reasonable time; target times are stated on the product page. When a disk is replaced, data is restored from the Customer's backup. At the end of the rental term, disks are securely erased in accordance with ToS s.9.
2.9 Kirala Senin Olsun (rent-to-own) (KSO). The rental model involving transfer of ownership is subject to the separate Dedicated Server Rental (KSO) Agreement; if this Annex conflicts with that agreement, the KSO agreement applies.
2.10 Add-on services. Add-ons such as additional IPs, network firewall, licences and backups are subject to their own Annexes.
Annex 3 · Gyro Cloud servers, hourly prepayment and one-click applications
A. Gyro Cloud servers
3.1 Region selection. The Customer selects a region during ordering (e.g. Istanbul, Germany, Finland, USA, Singapore). Customer Content is kept and processed in the selected region; servers in the Istanbul region are hosted in data centres in Türkiye. A server is not moved to another region without the Customer's consent (ToS s.13.7 for personal data; Section 3 of the Privacy Notice for data relating to the Customer's account).
3.2 Shared resources. In standard cloud plans, CPU resources are shared among servers using the same physical infrastructure; dedicated CPU is provided only in plans sold as "dedicated" on the product page. Gyro may apply CPU usage limits for fair distribution of shared resources.
3.3 Backup and snapshot. Cloud servers are not backed up by Gyro. Snapshot and backup features are offered as stated on the product page; a snapshot is not a substitute for a backup.
3.4 Reinstallation and deletion. Reinstalling the operating system or deleting the server permanently erases disk contents. These actions are carried out in the Customer Panel with an explicit warning and confirmation step; actions made through the API are also deemed Customer actions.
3.5 Additional IPs and disks. Additional IPv4 addresses and additional disks are charged separately; limits are stated on the product page and in the account limits. An IP address removed from a server does not remain with the Customer and may be allocated to another customer after a period.
3.6 Resizing. When upgrading a plan, the disk cannot be reduced; an upgrade may require the server to be restarted. This information is shown on screen before the operation.
B. Hourly prepayment
3.7 Nature. The fee for Hourly Prepaid Services is deducted from the Customer's Balance according to duration of use. Every hour started counts as a full hour. For Services so indicated on the product page, the billed time in a calendar month does not exceed 672 hours (monthly cap); Services to which the cap does not apply are indicated on the product page.
3.8 Continued billing. Servers that are shut down (powered off) but not deleted continue to reserve resources and are therefore charged. Billing stops only when the Service is deleted.
3.9 When Balance runs out. The Customer is warned when the Balance falls below projected usage. When the Balance runs out, the Service is suspended; if Balance is not loaded within 72 hours, the Service is cancelled and its data is deleted immediately (ToS s.9.3).
3.10 Account limits. For security and capacity planning, limits on servers, CPU, memory, IPs and the like apply per account; new accounts may have lower limits in the first days. Current limits are shown in the Customer Panel and the API; increases are considered by support request.
3.11 Price changes. Hourly prices may change with the advance notice in ToS s.15.2; the change applies to hours after the effective date. There is no commitment to preserve the old price for hourly Services.
3.12 Refunds. The fee for used time is not refunded. For Balance, ToS s.5.6 applies.
C. One-click applications and AI applications
3.13 Installation service. The "one-click application" feature installs the selected open-source or third-party software on the Customer's server. After installation, management, updating, security and data of the software are the Customer's responsibility. Gyro's support is limited to completion of the installation.
3.14 Third-party licences. Each application is subject to its own licence; the Customer agrees to use it in accordance with that licence.
3.15 AI applications. In AI applications installed by the Customer, access to the model provider is through the Customer's own account and key; that provider's terms of use and fees are between the Customer and the provider. The commands these applications run on the server, the data they access, the content they send to third parties and their consequences are the Customer's responsibility. The Customer limits the authority it gives these applications under the principle of least privilege. Automated scanning, attacks or spam with these applications are prohibited.
3.16 Personal data. With respect to personal data the Customer processes with these applications, the Customer is the data controller; if it sends data to a model provider abroad, it provides the necessary legal basis itself.
Annex 4 · Gyro Containers, Serverless, Pipeline and log retention
4.1 Service model. In the container Service, the Customer's container images run on a cluster managed by Gyro. In dedicated plans, nodes belonging to the Customer are used; in the Serverless plan, a shared resource pool is used. The Customer is responsible for the content of its images, software licences and information it keeps in environment variables and secrets.
4.2 Billing. Environments and nodes are measured hourly; Serverless usage is measured by running time and the amount of CPU and memory allocated, and is deducted from the Balance (Annex 3 section B applies). No monthly hour cap applies to Serverless; the estimated monthly amount is calculated on the product page.
4.3 Egress IP addresses. Outbound connections of containers originate from IP addresses determined by Gyro; these addresses may change on infrastructure changes, node renewal or plan changes. Current addresses are shown in the Customer Panel and the API and changes are notified. A fixed egress IP is committed only with the add-on sold for that purpose.
4.4 Automatic repair. Gyro may automatically renew failed nodes; a brief interruption may occur in the meantime. For stateful applications, persistent storage and backup are the Customer's responsibility.
4.5 Pipeline (build and deploy). The service of building images from the Customer's source code repository is offered with the monthly free-minutes limit on the product page. The Customer defines repository access tokens with least privilege. Attacks on third-party systems, mining and similar use in the build environment are prohibited.
4.6 Container application logs.
(1) In the Container and Serverless Services, logs produced by the Customer's applications are retained for the duration of the plan selected by the Customer: the default plan is 7 days (free); paid plans are 30, 90 or 365 days. Expired logs are deleted automatically. If the plan is reduced, logs exceeding the new period are deleted.
(2) Logs are Customer Content. With respect to personal data in logs, the Customer is the data controller and Gyro is the data processor; Gyro processes logs only for retention, display to the Customer and operation of the Service (ToS s.13).
(3) The Customer is responsible for ensuring that its applications do not write personal data, special categories of personal data, passwords, access keys or payment card information to logs, and for the legal basis for retaining the logs. The Customer determines whether the selected retention period complies with the legislation to which it is subject.
(4) Log retention is offered on a best-efforts basis. Logs are not backed up and may not be recoverable in case of failure. This Service is not an archive, audit trail or legal retention solution; for legal retention needs, immutable storage such as Protected Storage should be used. For damage arising from log loss, and without prejudice to cases of intent and gross negligence, Gyro's liability is limited to the fee of the log retention plan for the relevant month.
(5) When an environment or Service is cancelled, logs are permanently deleted immediately in accordance with ToS s.9.1. The Customer exports its logs itself before cancellation.
(6) Infrastructure and traffic records kept by Gyro for Service security and under Law No. 5651 are outside this section.
4.7 Preview features. Features marked "preview" or "beta" may change or be removed and are not covered by the Service Level Agreement.
Annex 5 · Object Storage (S3) and Protected Storage
A. Object Storage
5.1 Scope. Hosting of objects (files) via an S3-compatible interface, static website publishing and the feature of mounting on the Customer's servers. The off-purpose use limit on shared hosting (Annex 1 s.1.3) does not apply to this Service; this Service is for file hosting.
5.2 Storage and traffic allowance. Plan storage and the monthly traffic allowance are stated on the product page. When the traffic allowance is exhausted, no overage invoice is issued; the speed of the relevant buckets is reduced to the level stated on the product page. The Customer may purchase an additional traffic package for that month; an additional traffic package expires at the end of the calendar month in which it is purchased, does not carry over and is not refundable. The Customer is warned by e-mail before the allowance runs out (e.g. at 80% and 100%).
5.3 No backup. Objects in Object Storage are not backed up by Gyro. A deleted or overwritten object cannot be recovered. Protected Storage should be used for the need for an immutable copy.
5.4 Bucket names. If the Customer changes a bucket name, the old name is kept reserved within this Service for 40 days and redirection from the old web address to the new one is provided; after this period the old name becomes available. A limit on the frequency of name changes may be applied.
5.5 Static site and sharing. The Customer is responsible for the content of the website published from a bucket and of sharing links, for access permissions (including public buckets) and for cross-origin resource sharing (CORS) settings. Content involving phishing, malware distribution and copyright infringement is immediately made inaccessible under the Acceptable Use Policy.
5.6 Capacity. Gyro may temporarily withdraw certain plan sizes from sale depending on capacity; existing Services are not affected.
B. Protected Storage
5.7 In the Protected Storage Service, versioning is enabled on buckets. Old versions and delete markers of overwritten or deleted objects count against the plan storage. By default, old versions are automatically deleted after 30 days; the Customer may change this period or disable automatic deletion. Versions deleted by the automatic deletion rule or permanently by the Customer cannot be recovered.
5.8 The Object Lock add-on is selected when the bucket is created; it cannot be enabled or disabled after the bucket is created. The Customer determines the lock mode (Governance, Compliance), retention periods and the application of legal hold (Legal Hold); only the Customer is responsible for the consequences of these choices and for determining the legal obligations on which data is to be retained and for how long.
5.9 Data locked in Compliance mode cannot be deleted, modified or overwritten by anyone, including Gyro, before the retention period expires, and data under Legal Hold cannot be so treated before the Legal Hold is removed. In Compliance mode the retention period cannot be shortened, only extended. Gyro does not delete such data before its term for any reason, including at the Customer's request; therefore requests for deletion, refund or shortening of the term cannot be met.
5.10 A lock in Governance mode cannot be bypassed with the Customer's access keys and the Customer Panel. This lock can be bypassed only by authorised Gyro staff, on the Customer's request and on the record; if the Service ends, data in Governance mode is deleted together with the other data of the Service.
5.11 The Customer cannot request cancellation of a Service that has data locked in Compliance mode or under Legal Hold. Even if the Service expires, is suspended or terminated for non-payment or any other reason, this data is retained until the end of the retention period (for data under Legal Hold, until the Legal Hold is removed). During this period, the space occupied by locked data and the Object Lock add-on are invoiced periodically until the end of the term; unpaid amounts are pursued under the general provisions. Buckets and Services with locked data are deleted at the end of the term in accordance with ToS s.9.1.
5.12 Versioning and Object Lock are technical measures that help create an immutable copy against accidental deletion and unauthorised changes such as ransomware. These features do not constitute a compliance document or certificate under any legislation.
5.13 Mounting of Protected Storage buckets on a server is read-only by default; when mounting with write permission, the Customer acknowledges that every write operation will create a new version and consume space.
Annex 6 · Network services
A. Private network (VPC) and gateway
6.1 The Customer creates its own private networks and subnets in supported regions; addressing, routing, port forwarding and access configuration are the Customer's responsibility.
6.2 When a server's public IP address is turned off, access to the server from the internet is possible only through the gateway and port forwardings defined by the Customer; loss of access due to misconfiguration is the Customer's responsibility. Console access in the Customer Panel remains open.
6.3 The gateway (NAT) fee is stated on the product page and is charged hourly (Annex 3 B).
6.4 For traffic going out to the internet through the gateway, mapping records of which internal address used which external address and port at what time are kept under Law No. 5651 (Acceptable Use Policy §7).
B. Load balancer
6.5 The load balancer distributes traffic to targets defined by the Customer. Health check and target configuration are the Customer's responsibility.
6.6 When the Customer uses the automatic certificate option, Gyro obtains and renews a domain-validated certificate from a free certificate authority on the Customer's behalf. The Customer is deemed to have accepted that certificate authority's subscriber terms and declares that it has authority over the domain name.
C. Gyro DNS
6.7 Gyro DNS is offered in free and paid plans; limits are stated on the product page. The content and accuracy of DNS records are the Customer's responsibility.
6.8 For domain names registered or transferred through Gyro and using Gyro name servers, a free plan and an empty zone may be created automatically; the Customer is informed of this.
6.9 When DNSSEC is enabled, key management is carried out by Gyro; when moving the domain name to another provider, disabling DNSSEC in the correct order is the Customer's responsibility.
6.10 DNS service for domain names used for phishing, malware distribution or network attacks may be suspended.
D. Network firewall
6.11 Customer-defined firewall rules and security groups are the Customer's responsibility; loss of access caused by incorrect rules, or ports left open, are at the Customer's risk.
6.12 Changes that narrow management access (e.g. remote desktop, SSH) are first applied with a temporary trial period; if the Customer does not confirm, the previous state is restored. The "emergency open" feature in the Customer Panel is intended for self-lockout situations.
6.13 Gyro may put in place infrastructure rules applied before the Customer's rules to combat attacks and abuse; these rules cannot be removed by the Customer.
6.14 Limits on the number of rules are stated on the product page.
Annex 7 · Business Email
7.1 Scope. Mailbox, webmail, IMAP/SMTP, calendar and contact synchronisation for the Customer's domain name, and the add-ons on the product page (e.g. mobile synchronisation, archive, additional storage). This Service is an e-mail hosting service offered by Gyro.
7.2 Quotas and sending limits. Mailbox storage, number of mailboxes and hourly sending limits (per domain name and per mailbox) are stated on the product page. Sending that exceeds the limits is deferred or rejected. Sending bulk marketing e-mail is outside the purpose of this Service.
7.3 Delivery and reputation. Gyro takes reasonable measures to protect the reputation of the sending infrastructure; acceptance decisions of recipient servers are not under Gyro's control. Mailboxes whose accounts have been compromised or that send spam may be stopped immediately.
7.4 DNS records. If the Customer's domain name is on Gyro DNS, the records required for e-mail (MX, SPF, DKIM, autodiscovery records) may be created with the Customer's consent or automatically at Service setup; the Customer's existing conflicting records are not changed.
7.5 Migration. When using the migration tool from another provider, the Customer declares that it is authorised to enter the access credentials of the source account; these credentials are used only for the duration of the migration.
7.6 Backup. Unless the archive add-on is purchased, no backup commitment is given for mailboxes on the Customer's behalf; ToS s.7 applies.
7.7 End of Service. Cancelled mailboxes and their contents are deleted immediately in accordance with ToS s.9.1; the Customer exports before cancellation.
7.8 Personal data. With respect to the contents of mailboxes, the Customer is the data controller and Gyro is the data processor (ToS s.13). The Customer is responsible for its employment-law and personal data obligations (including notification) regarding its employees' mailboxes.
Annex 8 · Uptime Monitoring and status page
8.1 The monitoring Service checks addresses and services defined by the Customer from outside at certain intervals and sends notifications. Monitoring is for information purposes; for damage arising from a delay or failure of a notification, Gyro's liability is limited to the Service fee for the relevant month (ToS s.11.4 reserved).
8.2 With respect to the personal data of notification recipients (e-mail, telephone number, messaging account), the Customer is the data controller; the Customer is responsible for informing recipients and, where necessary, for their permissions.
8.3 SMS credits are one-off, carry over at the end of the period, are not convertible to cash and are not refundable.
8.4 Free plan limits are stated on the product page; the free plan is not covered by the Service Level Agreement.
8.5 The Customer is responsible for the content of a status page published on its own domain name. When the status page is published on its own domain name, the certificate is obtained by Gyro (Annex 6 s.6.6 applies by analogy).
8.6 Monitoring is carried out at a frequency that does not place load on the monitored system; the Customer monitors only addresses that belong to it or that it is authorised to monitor.
Annex 9 · Domain names
9.1 Intermediation. Gyro offers domain name registration, renewal and transfer services through an authorised registrar partner. The holder of the domain name (registrant) is the person named in the registration details; Gyro is not the registrant. Registration terms are also set out in the Domain Name Registration Agreement.
9.2 ICANN extensions. Registration is subject to ICANN rules and the policies of the relevant extension operator (registry). The Customer accepts the registrants' benefits and responsibilities document, the transfer policy (60-day transfer lock after new registration and change of registrant), the expiration renewal reminder policy and the Uniform Domain Name Dispute Resolution Policy (UDRP/URS). Summary and links: ICANN Domain Procedures.
9.3 .tr extensions. .tr domain names are subject to the Internet Domain Names Regulation, the .tr domain name rules and the .tr dispute resolution procedure. For .tr extensions that require documents, the document obligation rests with the Customer.
9.4 Accurate information. Keeping registration details accurate and up to date is mandatory; incorrect information is grounds for suspension or deletion by the registrar or operator.
9.5 Personal data privacy. For supported extensions, registration details are hidden in public lookups; access by the operator or competent authorities is reserved.
9.6 Expiry. Renewal reminders are sent to the Registered E-mail before expiry. An expired domain name is subject to the grace and redemption periods in the extension's rules; during these periods the redemption fee varies by extension and is shown before payment. At the end of the term the domain name may be released.
9.7 Name servers. Unless otherwise selected, Gyro DNS name servers are used for new registrations and Annex 6 s.6.8 applies.
9.8 Refunds. Domain name registration, renewal and transfer are services performed instantly and are not refundable (Distance Sales Agreement s.6); if the operation fails, the fee is refunded.
9.9 Disputes. Gyro is not a party to domain name disputes; it implements the decision of the competent dispute resolution body or court.
Annex 10 · Software licences
10.1 Licences for control panels, web servers, operating system security software and the like are obtained through third-party licence providers. Licence activation and continuity depend on these providers' systems; Gyro makes reasonable efforts to remedy disruptions.
10.2 Licences are bound to the server (IP address or server ID) on which the licence is registered; changing the IP is subject to the provider's rules.
10.3 The Customer agrees to use the software in accordance with the end-user licence agreement (EULA) published on the relevant software manufacturer's website.
10.4 Licence fees are for services performed instantly and are not refundable (Distance Sales Agreement s.6); if the licence cannot be activated at all, the fee is refunded.
Annex 11 · API, command-line tool, Terraform provider and MCP server
11.1 Binding effect. All actions and orders made through an API key, a command-line tool session, the Terraform provider or AI clients authorised by the Customer (including the MCP server) are deemed to have been made by the Customer, and their fee is collected from the Balance or the registered payment method.
11.2 Key security. The confidentiality, scope of authority, IP restriction and validity period of keys are the Customer's responsibility. The Customer immediately revokes a key it suspects has been compromised.
11.3 AI clients. Actions taken with the key and authority the Customer gives to an AI tool (including deleting servers and placing orders) are the Customer's responsibility. Gyro may require additional verification for actions requiring confirmation (e.g. a confirmation field, a repeat-protection key); passing these verifications by automation is the Customer's responsibility.
11.4 Limits. For the continuity of the Service, Gyro may apply request rate limits and daily limits on spending made through automation. Limits are published in the documentation.
11.5 Abuse. In case of breach of the Acceptable Use Policy or use that endangers the Service, Gyro may suspend the key and informs the Customer.
11.6 Versioning. API endpoints are versioned. Backwards-incompatible changes and endpoint removals are announced at least 90 days in advance; this period may be shortened in case of security necessity.
11.7 Open-source tools. The command-line tool, Terraform provider and MCP server published by Gyro are subject to their own open-source licences and are provided "as is". The API service itself is subject to the ToS.
11.8 Documentation. Sample code in the API documentation is for information only.
Ready to Get Started?
Join thousands of businesses that build, host and grow with us every day.