Skip to main content

Terms, Privacy & Service Policies

Clear terms for your account, payments, domains, hosting and optional paid SSL. Fasting Host operates under the registered business name METI HOSTING LLC. Effective 31 October 2026 · Updated 10 November 2026 · Version 2026-11-10.1.

Browse All Policies Contact Fasting Host
Legal & Service Information

Company & policy centre

METI HOSTING LLC · Fasting Host

447 Mount Pleasant Rd, Bedford, KY 40006, United States

support@fasting.host

For support, billing, legal, privacy, copyright or abuse matters, email us with the relevant subject. This is a business mailing address; it is not a statement of server location.

Terms of Service

1. Your agreement with Fasting Host

Fasting Host is operated under METI HOSTING LLC, the registered assumed name of FiveM Store L.L.C. (Kentucky organization number 1174776; assumed-name filing) ("we", "us", "our"). Our business mailing address is 447 Mount Pleasant Rd, Bedford, KY 40006, United States. Contact us at support@fasting.host for account, legal, privacy or abuse matters. You are the account holder purchasing the service. A person ordering for an organisation must have authority to bind it. Account holders must be at least 18 and legally able to contract.

The accepted order, its service description and price, these terms and the relevant policies form the service agreement. Mandatory law prevails. A negotiated written agreement prevails over a conflicting standard term; a service-specific condition prevails for that service. Our privacy notice explains processing and does not turn all processing into consent.

2. Orders and activation

An order acknowledgement, invoice or payment receipt does not by itself confirm that a VPS, hosting account or domain has been activated. An order is accepted when we confirm acceptance or activate the requested service. Availability, eligibility and proportionate fraud checks may affect acceptance. We will refund payments for services we decline and do not supply, subject to any separately disclosed, lawfully incurred charge.

Published specifications describe the selected service. A page labelled coming soon is not an offer of immediate provisioning. We do not guarantee an activation date unless we expressly agree one. Material pre-activation changes require your agreement or the option to cancel for a refund of the unprovided service.

3. Account and security

Fasting Host does not perform KYC or request government-issued ID, identity-verification selfies or biometric checks. An account and accurate contact and billing details are still required. This is not a guarantee of anonymous service or of payment without verification: independent payment providers may apply their own checks, domain eligibility and registrant verification follow the Domain Policy, and optional paid SSL requires the issuer’s domain and, for OV/EV, organization checks under the SSL Certificate Policy. See payment verification details.

Provide accurate contact and billing details and keep them current. Protect passwords, API keys, recovery methods and authorised-user access. Enable available multifactor authentication. Notify us promptly of suspected compromise. You are responsible for activity you authorise and for taking reasonable steps to protect your account; this does not excuse our own failures or override mandatory protections for unauthorised transactions.

We may use existing account, contact and transaction information to confirm account control or investigate suspected fraud, explaining what is needed and why. We do not request government-issued identity documents for this process. Email verification, sign-in authentication and account-control checks protect access to your services; they are separate from KYC identity checks. Never send passwords, full payment-card details, identity documents, verification selfies or biometric data in a Fasting Host ticket. Complete a genuine independent-provider verification request through that provider’s approved secure channel.

4. Service scope

VPS services provide the resources in the accepted plan on a VMware-based platform. Root or Administrator access normally makes you responsible for your guest operating system, updates, applications, firewall and data. Management, migrations, application repair and third-party software support are included only when expressly listed.

cPanel hosting supports compatible websites and applications within the published plan limits. Compatibility with WordPress or WooCommerce does not guarantee every plugin, extension or workload. Email, certificates, backups, extra IP addresses and licences are included only when specified.

Paid SSL certificates are optional and governed by the SSL Certificate Policy; eligible cPanel hosting already includes free AutoSSL. Domain names are separate from web hosting and mailboxes. Domain processing, eligibility, renewals and disputes are governed by our Domain Policy and the applicable registrar and registry agreements.

5. Your content and responsibilities

You retain ownership of your content. You grant us only the rights reasonably needed to host, transmit, back up where agreed, secure and support the service. We do not acquire ownership of your software, business or domain rights merely by providing a service.

You must have the necessary rights and permissions, obey applicable law and the Acceptable Use Policy, maintain independent backups, and ensure your application is appropriate for the selected plan. Reselling an eligible service does not remove your responsibility for your customers' activity. Resale rights are not implied for third-party licences.

6. Fees and renewals

The Billing, Cancellation and Refund Policy applies. The order must show the billing period, currency, recurring price and applicable taxes or additional charges before payment. Payment-provider authorisation must be separate from any optional marketing consent. A recurring invoice is not proof of a completed payment or renewal.

We may change prices for future billing periods on at least 30 days' notice, or a longer period required by law. An already paid fixed term is not repriced. You can cancel before a changed renewal takes effect. Registry, tax or legally required changes may need a different notice period; we will explain the change and any cancellation rights.

7. Availability and maintenance

We use reasonable care to operate the service. Maintenance, failures, security events, upstream networks and events outside reasonable control may affect availability. We will communicate significant planned maintenance where practicable and act reasonably to restore affected services.

No numerical uptime guarantee, fixed response time, managed-service commitment or service-credit scheme applies unless expressly included in the accepted order. This does not remove mandatory rights where a service is defective or not supplied with reasonable care.

8. Suspension and enforcement

We may restrict the affected service for overdue payment after notice and an opportunity to pay, material policy breaches, legal requirements or a credible security threat. For urgent harm we may act immediately and explain afterwards where lawful. We will aim to use proportionate measures, identify the reason and explain what is needed to restore access.

An allegation is not automatically proof. You may challenge a decision through the complaints process. We will not demand an undisclosed arbitrary fee to restore access. Domain locks, registry actions and lawful disclosure requests may follow separate mandatory procedures.

9. Ending a service

You may cancel using the client area or support@fasting.host. We may end a service for a material breach that is not remedied after reasonable notice, serious repeated abuse or a legal requirement. We may discontinue a service for business reasons on at least 30 days' notice and refund prepaid charges for the unused, unprovided period, unless a lawful agreed alternative applies.

Export your data before termination. The Backup and Data Lifecycle Policy explains deletion and recovery limitations. Cancellation of hosting does not cancel a domain, and disabling a recurring payment does not by itself transfer a domain or resolve an outstanding invoice.

10. Responsibility and liability

We remain responsible for duties that cannot lawfully be excluded, including applicable consumer remedies and liability for fraud or other matters the law does not permit us to limit. Nothing requires you to waive mandatory privacy, payment, consumer or domain rights.

For business customers only, and only to the extent lawful, neither party is liable for indirect or consequential losses that were not reasonably foreseeable. Our total contractual liability for an affected service is limited to the charges paid or payable for that service during the 12 months before the event. This limit does not apply where prohibited by law or to our fraud, wilful misconduct or liabilities that cannot be limited. Consumer liability is governed by applicable mandatory law rather than this business cap.

You are responsible for third-party claims caused by your unlawful content or deliberate misuse to the extent attributable to you. We will notify you and cooperate reasonably; you do not assume responsibility for our own fault. We will take reasonable steps to reduce losses.

11. Disputes, law and policy changes

Start with the complaints process. These terms select no arbitration requirement, class-action waiver or foreign exclusive forum. Applicable law and court jurisdiction will be determined by the relevant legal rules, preserving mandatory consumer protections and access to competent courts. Our business mailing address does not make a choice of exclusive governing law or forum.

We will give reasonable advance notice of material contractual changes, normally at least 30 days, and explain options where a change materially disadvantages an existing customer. Urgent legal or security changes may take effect sooner. Updated terms will not retrospectively rewrite a completed purchase. An unenforceable provision will be limited or severed without removing the rest of the agreement. Changes and notices will be communicated through the account email or client area as appropriate.

Back to policy index

Billing, Cancellation and Refund Policy

1. Prices, billing periods and authorisation

Annual Cloud VPS and cPanel hosting prices equal ten monthly payments for twelve months of service: two months free, a saving of 16.67% compared with twelve monthly payments. This discount applies only to the annual billing cycle. Monthly prices are not discounted. The annual recurring total is shown before purchase; any later price change follows the notice and cancellation terms.

Prices are in USD unless checkout states otherwise. Your order must show the initial payment, recurring amount, billing period and applicable taxes or other unavoidable charges. Discounts apply only for the stated term; a discounted registration price does not make the renewal price the same. Optional extras require a positive choice.

Services are generally paid in advance. Invoices show their due date. We will not add a late fee, collection fee, processor surcharge or restoration charge unless it was disclosed, agreed and lawful. Recurring Amazon Pay charges require the appropriate payment authorisation; we do not treat acceptance of our privacy notice as that authorisation.

2. Renewals and payment failure

Hosting and VPS renew for the billing period shown when recurring renewal is enabled. Domain renewal depends on the extension, a completed payment and successful registrar processing. Review your account regularly; an enabled auto-renew switch, saved payment method or issued invoice is not a guarantee of renewal.

We will show and provide notice of the recurring amount and renewal/cancellation conditions as required. If payment fails, we may send reminders and retry only within the payment authorisation and applicable law. Update or cancel recurring authorisation through the account/payment provider. Tell us if you see an unexpected or duplicate charge.

3. How to cancel

Use the service's cancellation option in the client area or send a clear request through support@fasting.host. If account access fails, the public contact channel remains available. State the service and whether you request cancellation at the end of the paid term or earlier. We may verify account control before destructive changes.

For end-of-term cancellation, submit the request before the next renewal is processed; we recommend at least 48 hours in advance to allow time for assistance, but this recommendation does not remove statutory cancellation rights or make a timely request invalid. We will confirm the cancellation date and any remaining payment obligation. Removing a payment authorisation and cancelling a service are related but distinct actions.

Do not use an immediate-cancellation request as a way to disable only auto-renew if you still need your server or data. Immediate termination can end access and start deletion. Domain auto-renew must be disabled separately; a completed registration or renewal normally remains until its paid expiry date.

4. Seven-day refund guarantee for all services

Every newly purchased Fasting Host service is covered by our seven-day refund guarantee. You may cancel within seven calendar days of initial activation and request a refund of the service payment, whether the billing term is monthly or annual. This applies across our services, not only to your first service. Request a refund through your client area or support@fasting.host and identify the service and payment.

The guarantee applies to all newly purchased services, including a completed domain purchase where offered. There is no first-service-only or once-per-customer restriction. After the seven-day guarantee window, cancellation does not automatically create a refund for an already supplied service or unused term. This does not limit mandatory rights, duplicate-charge corrections or refunds for services we decline and do not provide.

5. Failed orders, errors and domain refunds

We refund duplicate charges and payments for an order that we decline and do not fulfil. If only part of a bundle was supplied, we will explain the allocation and refund the unprovided part. We will not insist on account credit where a money refund is legally due.

Our seven-day guarantee also covers newly purchased domain services where offered. After that guarantee window, a completed domain registration, renewal, paid restoration or transfer is normally not refundable merely because it is no longer wanted. A refund does not itself transfer ownership or reverse a registry transaction; we will explain the service status when processing it. Failed or unprovided orders, duplicate charges and mandatory remedies remain covered.

6. Statutory consumer rights

Mandatory consumer law overrides narrower commercial refund exclusions. Where a consumer has a 14-day service withdrawal right, it runs from the date the contract is concluded, subject to the applicable rules. You can exercise it by sending a clear statement identifying the contract; use of a particular form is not compulsory.

Starting service during a withdrawal period requires the consent/request required by law. A loss of the withdrawal right on full performance is not assumed merely because you accepted these terms, paid or bought a domain. Any required express request and acknowledgement must be collected separately and confirmed on a durable medium. Where lawful, a proportionate amount for requested performance may be due. We will provide legally required refunds within the applicable deadline, including 14 days where that rule applies.

7. Refund processing and disputes

Approved refunds are sent to the original payment method where possible. Our processing target is five business days after approval; your bank or payment provider may take longer. Currency conversion differences are determined by the payment provider and do not reduce a statutory refund obligation. We will explain any lawful deduction in advance.

Contact us to resolve a billing issue, but you do not have to surrender your right to dispute a payment. A dispute is not automatically fraud. We may suspend the affected unpaid service where justified, with notice where appropriate, while investigating. We will not hold an unrelated paid service or domain hostage solely because you raised a good-faith complaint.

8. Cryptocurrency and card payments

Cards, digital wallets, PayPal, bank payments and regional payment options are offered through Tebex, alongside eligible card payments through Amazon Pay. Cryptocurrency payments are available through NOWPayments. Tebex is the seller and merchant of record for transactions made through its checkout and handles payment processing, applicable sales tax and payment refunds under its checkout terms. Fasting Host provides the hosting service and technical support. Browse our payment guide for cryptocurrency instructions and the full 75-method Tebex catalogue. Choose a method shown in checkout or on your unpaid invoice; the relevant provider presents the final options, total, currency and any applicable tax. NOWPayments presents its enabled coins and networks. Our planned Bitcart option is not currently enabled.

For cryptocurrency, use the exact coin, network, address, amount and any memo/tag shown for that invoice, within its payment instructions and quote validity. Allow for wallet or network fees so the requested amount reaches the payment destination. A broadcast transaction or wallet receipt alone does not mark an invoice paid: the processor must confirm the payment. If a payment is short, late, duplicated or sent incorrectly, contact support with the invoice reference and transaction identifier before sending again. Recovery of an incorrect-network or incorrect-address transfer may be impossible.

NOWPayments may place a flagged cryptocurrency payment on hold and request identity or source-of-funds verification under its KYC/AML procedure. Fasting Host does not conduct those checks or request government-issued ID. Tebex, Amazon Pay, your bank, card issuer or a wallet/exchange service you choose may also apply authentication or verification requirements. Fasting Host cannot override independent provider checks. Review the payment verification details before choosing.

A processor hold does not remove our seven-day refund guarantee or mandatory refund obligations. We will explain the payment status and available next steps and work with the relevant provider; checks and provider processing may affect when funds can be returned. No processor surcharge is added unless disclosed before you authorise payment and permitted by law. Keep passwords, full card details, wallet seed phrases and identity documents out of Fasting Host support messages. Read the Privacy Notice and payment guide for more information.

Back to policy index

Acceptable Use Policy

1. Responsible use

Use our services only for lawful activity and in a way that respects other people, networks and intellectual property. You are responsible for the activity of users, applications and customers operating through your service. Reasonable security research is permitted only with the relevant system owner's authorisation and without affecting other tenants or networks.

2. Prohibited activity

You must not use the service to distribute malware, run botnets, conduct phishing or credential theft, deploy ransomware, exploit unauthorised systems, perform denial-of-service attacks or facilitate other unlawful access. Unauthorised scanning, spoofing, open relays, amplification services and deliberate evasion of network protection are prohibited.

Child sexual abuse or exploitation material, unlawful sexual content, trafficking, credible threats, unlawful harassment, doxxing and content that unlawfully infringes another person's rights are prohibited. We do not offer a service that disregards valid abuse reports, court orders or applicable law.

Do not send unsolicited bulk messages or use harvested lists. Bulk email requires lawful recipient permission, accurate sender identification, a working unsubscribe process and compliance with applicable law and the plan's published mail limits. Buying a VPS is not permission to send spam.

Do not use unauthorised payment methods, impersonate others, falsify registration data, misuse third-party licences or redistribute content without the necessary rights. Customer encryption does not make unlawful use permissible.

3. Resource and network protection

Stay within the selected plan's CPU, memory, storage, I/O, network and account limits. Do not attempt to escape the virtual environment or access another tenant's data. Keep software patched and investigate compromise promptly. High-load lawful workloads are subject to the Fair Use Policy and the resources purchased.

Cryptocurrency mining, continuous benchmark/stress workloads and public traffic relays require prior written approval on infrastructure used by multiple customers. Private VPN use and legitimate development are subject to the same security, legal and resource rules; this policy does not grant permission to attack third parties or operate an unauthorised public proxy.

4. Reports and evidence

Report suspected misuse to support@fasting.host (subject: Abuse report) with the domain or IP, exact URLs where relevant, timestamps with timezone, a description and supporting logs. Do not send malware attachments, stolen credentials or illegal images. For immediate danger, contact the relevant emergency authority as well as reporting the service.

We review credible reports in context, may seek clarification and may preserve necessary evidence. We may share a proportionate report with the account holder, relevant supplier or lawful authority where appropriate, while considering the reporter's safety and privacy. Anonymous or unsupported allegations may be difficult to investigate.

5. Enforcement and appeal

We may require remediation, restrict a process, rate-limit traffic or suspend an affected service. Urgent risks may require immediate isolation or network null-routing. We will use proportionate action and provide a reason and restoration steps where lawful and practicable. Serious or repeated breaches may lead to termination.

You may request review through support@fasting.host (subject: Complaint). We consider corrections, mistaken identity and evidence of compromise. Refunds and retention are handled under the applicable policies and mandatory law. We do not impose an undisclosed penalty merely because an abuse report was received.

Back to policy index

Bandwidth and Fair Use Policy

1. Meaning of the network description

Our published Cloud VPS range uses a host with a 10 Gbps uplink. Gbps means gigabits per second, not gigabytes per second. The host connection serves multiple VPS workloads; it provides no dedicated 10 Gbps port or minimum throughput promise for each VPS. Actual speeds depend on host utilisation, routing, protocol overhead, destination networks and your application.

Unmetered bandwidth means the stated plan has no fixed monthly traffic allowance or per-GB charge under normal compliant use. It does not mean unlimited simultaneous throughput, unlimited hardware capacity or permission to disrupt other customers. We will not silently convert unmetered traffic into undisclosed per-GB billing.

2. Fair and predictable operation

You can use your allocated resources for legitimate websites, applications and other compatible workloads. CPU scheduling, I/O and network capacity must remain usable for other tenants. We assess congestion, sustained resource saturation, packet rates, abuse patterns and actual service impact rather than imposing a hidden universal transfer quota.

Any fixed monthly traffic allowance, advertised bandwidth rate limit or per-GB overage price is shown with the affected offer before purchase. Our Unlimited* plans do not have a fixed monthly transfer quota or per-GB traffic charge. The resource and network-protection measures described in this policy still apply. A high transfer volume alone is not proof of abuse.

3. When intervention is necessary

Where a workload materially affects infrastructure used by multiple customers, we will normally contact you with the observed issue and reasonable steps to reduce it. Options may include tuning the workload, scheduling jobs, a proportionate temporary limit or a mutually agreed move to a suitable plan. We will explain a proposed paid change before charging for it.

An attack, compromised service or immediate threat may require urgent filtering, rate-limiting or temporary isolation. We will explain the action when safe and lawful. If we cannot supply the purchased service on reasonable terms, cancellation and refund rights for the unprovided service apply. You may ask for review of a restriction.

4. DDoS protection and IP resources

All VPS and hosting services include DDoS protection. Performance Cloud VPS uses PLETX protection. Additional IPv4 addresses remain subject to availability and the selected configuration. Mitigation does not guarantee immunity from every attack or uninterrupted operation. IP assignments may change where operationally necessary with reasonable notice where possible; IP ownership and portability are not implied. Misuse or blacklisting may require remediation under the Acceptable Use Policy.

Back to policy index

Domain Registration, Renewal and Transfer Policy

1. Your domain and the registration chain

Fasting Host provides domain services as a reseller. We are not claiming ICANN accreditation. Registration takes place through an accredited sponsoring registrar and the relevant registry. You can identify a registered name's sponsoring registrar using ICANN's registration data lookup tool, and we will identify it on request. The applicable sponsoring registrar agreement and extension conditions are supplied with the relevant order and available from support@fasting.host before you order.

You hold the registrant's rights for the paid registration term, subject to the relevant agreements and eligibility rules. Payment for a search result does not reserve a name or establish trademark rights. Availability is confirmed only when registration succeeds. We cannot promise priority access over another registrar or applicant.

2. Accurate information and eligibility

Supply accurate registrant, administrative and contact information, and keep it current. We transmit required information to the sponsoring registrar, registry and related domain systems. Some extensions require residency, citizenship, organisational status or supporting information. Additional .fi information must match the registrant's legal type. Do not provide false details to obtain an ineligible name.

Respond promptly to data-validation and verification messages. Failure to complete a required check or correct inaccurate information can lead to suspension or cancellation under the applicable registration terms. WHOIS/RDAP redaction is not a promise of anonymity, and privacy protection does not remove the obligation to provide accurate data.

3. Prices and premium names

The order must show the extension, registration period, registration price and renewal price before payment. Transfer, restoration, premium-name and optional privacy charges must also be clearly identified where relevant. We will not treat a standard price as authorisation for an undisclosed premium purchase.

Current standard registration, transfer, renewal and configured recovery fees are published in the live domain price list, together with the available registration terms and expiry-period information. A recovery surcharge is additional to the normal renewal charge when the registrar requires renewal as part of restoration. A zero recovery surcharge does not waive renewal fees. Recovery is handled through support and remains subject to the extension, registrar and current domain status; a displayed billing window does not guarantee registry eligibility. For an extension without a quoted recovery fee, contact support for its availability, conditions and charge before ordering or authorising recovery. We do not perform or charge for a recovery without the required authorisation.

4. Renewal and expiry

Keep your account email reachable and monitor the expiry date. Auto-renew and recurring-payment settings are not guarantees: payment and registrar processing must succeed before the relevant deadline. Renew well before expiry and confirm the new registry expiry date after processing.

For gTLDs covered by the applicable ICANN recovery policy, expiry reminders are sent to the registrant's contact email approximately one month and one week before expiry, and a further notice is sent within five days after expiry where required. Additional notices may be sent. Keep a reachable contact email that does not depend solely on the expiring domain and check spam filtering.

After expiry, DNS and associated websites or email may stop working. Renewal, deletion, auction and recovery windows depend on the extension and sponsoring registrar; a universal grace period is not promised. Where a registry redemption period applies, recovery may involve a separate disclosed fee. Once final deletion has occurred, recovery may be impossible and another person may register the name. Applicable recovery rights are preserved.

5. Transfers and contact changes

Confirm eligibility and obtain the required transfer authorisation from your current provider. Many transfers need an unlocked domain and an authorisation code; some extensions use other procedures. Registration-age or registrant-change locks and pending disputes can prevent a transfer. Keep access to the contact email and respond to legitimate verification requests.

An incoming transfer does not always add a year or preserve the same expiry calculation. Extension rules and recent renewals can change the outcome. Confirm the expected term and price before authorising the transfer. Transferring hosting, mail or DNS is a separate task. Changing nameservers without copying needed records can interrupt services.

We will assist with a legitimate transfer out and provide available authorisation information subject to confirmation of account and domain control, applicable registrar or registry requirements, and lawful transfer restrictions. We do not invent a transfer-out penalty or refuse solely because you raised a good-faith complaint. Expiring a hosting service does not transfer or renew its domain.

6. DNS, privacy and related services

Nameserver management and supported DNSSEC options depend on the extension and configuration. You are responsible for correct records and for removing or updating DS records when changing DNS providers. DNS propagation and third-party cache expiry are outside an instant-change guarantee.

The current catalog does not include a paid WHOIS privacy, DNS-management or email-forwarding addon unless specifically offered in the order. A domain alone does not include a website, mailbox or hosting account. If a future privacy service is offered, its price, provider terms and eligibility must be disclosed before selection.

7. Disputes, legal orders and cancellation

Applicable ICANN dispute rules, including UDRP or URS where relevant, and registry-specific procedures may apply. Registration does not establish a right to infringe a trademark or another person's rights. We and the sponsoring registrar may comply with a binding dispute outcome, court order, registry instruction or lawful abuse mitigation requirement.

Newly purchased domain services are included in our seven-day refund guarantee under the Billing, Cancellation and Refund Policy. Refunds do not by themselves reverse a completed registry transaction. Disabling renewal leaves a paid registration in place until its applicable expiry. Failed or unprovided orders and mandatory remedies are also addressed in the Refund Policy.

8. Registrant information and assistance

Review ICANN's Registrants' Benefits and Responsibilities and registrant educational material using the links below. Applicable sponsoring-registrar and extension conditions remain part of the relevant domain agreement. Contact support@fasting.host for assistance, registrar identification, expiry information, abuse reports or transfer questions.

Use the live domain price list for current registration, transfer and renewal prices and available terms in USD. The same WHMCS pricing system supplies checkout; this policy does not keep a separate, potentially outdated copy. Review the final order amount before purchase. Premium, post-expiry and restoration terms require the disclosures described above.

View current domain prices

Back to policy index

SSL Certificate Policy

1. Included free SSL and optional paid certificates

Eligible cPanel-hosted websites include free automatic domain-validated SSL through AutoSSL, subject to working DNS and successful certificate-authority validation. Paid SSL is an optional, separately priced service. It is not required for ordinary HTTPS on eligible cPanel hosting. Unmanaged VPS customers configure their own certificate, web server and renewal process unless separate assistance is agreed.

2. Coverage and validation

The selected certificate product and issued subject alternative names (SANs) define coverage. A wildcard normally covers one level of subdomains; apex, www, additional domains and nested names must not be assumed. All public certificates require domain-control validation. OV and EV also require organization and authorization checks, and the issuer may request business records or other supporting information. Provide accurate, authorized information and complete checks through the stated secure process. Our approach to ordinary hosting/VPS signup does not waive issuer or payment-provider checks.

3. Paid service terms and certificate validity

The purchased one-, two- or three-year service term is not a promise that one issued certificate remains valid for that entire period. Current issuer and browser rules may require shorter certificate lifetimes, revalidation, reissuance and installation during the term. Follow client-area instructions and notices before expiry. Issuance depends on successful checks and provider processing; a stated estimate is not a guaranteed delivery time.

4. Installation, keys and renewals

Eligible connected cPanel hosting can use supported WHMCS certificate automation. Other environments may require you to generate a CSR and install each issued certificate and its chain. Keep private keys secure on the server; do not send them in ordinary tickets. You are responsible for correctly configuring applications and responding to validation or renewal requests within the accepted service scope. An invoice, payment or enabled renewal setting alone does not establish successful issuance or installation. Contact support promptly if validation, reissue or installation fails.

5. Public certificate records and issuer terms

Public TLS certificates are recorded in permanent Certificate Transparency logs. Domain names and, for OV/EV, validated organization details can be publicly searchable. Necessary order, domain, contact, CSR and validation information is processed through WHMCS Marketplace/MarketConnect and the issuing certificate authority, including DigiCert, GeoTrust or RapidSSL as applicable. Their independent processing and subscriber requirements apply to issuance. Review the DigiCert legal repository and the terms presented for the selected product. The Privacy Notice explains our processing.

6. Cancellation, refunds and limits of a certificate

The Billing, Cancellation and Refund Policy, including our seven-day guarantee for newly purchased services, applies. Hosting's annual two-free-month offer does not apply to certificate terms. Cancellation or a refund does not by itself erase Certificate Transparency records or reverse completed issuer actions. A compromised or no-longer-authorized certificate may require revocation; tell support promptly. A certificate supports encrypted transport and the stated identity validation; it is not a guarantee of trustworthy content, a green address bar, legal compliance, protection from every attack or improved rankings. Any issuer warranty is subject to that product's conditions and is not general breach insurance. Mandatory rights remain unaffected.

Back to policy index

Privacy Notice

1. Who is responsible

METI HOSTING LLC, the registered assumed name of FiveM Store L.L.C., operates Fasting Host and is responsible for personal information used to operate our own website, accounts, billing and support. Our business mailing address is 447 Mount Pleasant Rd, Bedford, KY 40006, United States. Our privacy contact is support@fasting.host; use the subject "Privacy request". Where a customer places personal data on a hosted service, the customer normally determines that processing and we may act as its processor under a separately applicable processing agreement.

This notice concerns Fasting Host's processing. A customer's website, an independent payment provider, registrar or registry may have its own notice and responsibilities. We do not claim that every supplier is our processor or that all data remains in one country.

2. Information we process and its sources

Account and order information includes names, organisation, contact details, billing address, tax details where needed, orders, invoices and service settings provided by you or an authorised representative. Domain applications may include registrant contacts and extension-specific eligibility information. Support communications and attachments come from you and people reporting issues.

Fasting Host does not request government-issued identity documents, identity-verification selfies or biometric scans for KYC. Please do not send these to our support channels. A payment provider, domain registrar or SSL certificate issuer may have separate requirements and its own secure verification process, as explained below.

Technical information can include IP address, access times, browser and request details, authentication and security events, service identifiers, usage measurements and diagnostic logs. Payment providers can return transaction identifiers, status, amounts and limited payment metadata. We do not need your Amazon password or complete card security credentials in support correspondence. Service content and backups, where applicable, are processed to provide the service, rather than to acquire ownership of the content.

3. Purposes and legal grounds

We use necessary account, order and service data to enter into and perform the service contract. We use billing records and required registration information to meet applicable legal duties. We use proportionate security logs, fraud investigation, service diagnostics and complaint records for legitimate interests in operating a secure business and protecting people, after considering their rights.

Where consent is required for marketing or optional tracking, it is requested separately and can be withdrawn. We will not bundle optional consent into a necessary service condition. If legally required information is not provided, an order or registration may not be possible. We will explain any necessary account-control or service-information request and minimise what we collect. Fasting Host does not request identity documents for KYC.

4. Recipients and international processing

Necessary data is provided to infrastructure, billing/support, communications and security providers, and to payment providers, sponsoring registrars and registries for the operation requested. Relevant advisers or authorities may receive information where necessary and lawful. We may share limited evidence when investigating an abuse report or defending a claim.

Payment processing: Tebex handles its checkout as seller and merchant of record, Amazon Pay handles eligible card payments, and NOWPayments handles cryptocurrency checkout. To create a NOWPayments invoice, WHMCS sends the invoice reference, amount, billing currency, payment description and return/callback URLs. This module does not send the customer email or billing address in that request. NOWPayments may collect checkout, device, payment and verification information directly. We receive payment status, amounts, currencies and transaction references, and keep records needed to reconcile invoices and handle support or refunds. For Tebex checkout, WHMCS provides the invoice reference, item descriptions, amount and customer contact details needed to create the basket. Providers and their payment partners process information under their own notices. Do not send wallet seeds, private keys or identity documents in an ordinary Fasting Host support ticket.

Tebex, Amazon Pay and NOWPayments describe their processing in Tebex’s Privacy Policy, the Amazon Payments Privacy Notice, and NOWPayments’ Privacy Policy. Fasting Host does not receive your Amazon password, full card credentials, wallet seed phrase or private key through these payment flows. Cryptocurrency records and public blockchains can reveal transaction details; crypto is not a promise of anonymity. Providers may process data internationally.

Our business contact address is in the United States. NOWPayments, Tebex and their payment partners may process payment information internationally. Amazon Pay is configured for the US region, and domain operations involve a sponsoring registrar and the relevant registry, which may process data in other countries. A service location does not mean all billing, support, payment or registration data stays there. Ask support@fasting.host for the recipients and countries relevant to your order before supplying data with location restrictions.

Where GDPR/UK GDPR transfer rules apply, restricted transfers require an applicable lawful mechanism and any necessary supplementary measures. A statement in this notice is not itself an executed set of Standard Contractual Clauses. You may request information about safeguards. Hosting that requires a specific processor/subprocessor or location agreement must not be activated for that processing until the relevant schedule and transfer arrangements are agreed.

Optional paid SSL: necessary certificate order, domain, contact, CSR and validation information is processed through WHMCS Marketplace/MarketConnect and the issuing CA (DigiCert, GeoTrust or RapidSSL as applicable). OV/EV may require company and authorization records. The issuer acts under its own subscriber terms and privacy notice; see the DigiCert Privacy Policy. Public TLS certificate domain names and, for OV/EV, validated organization details can appear in permanent, publicly searchable Certificate Transparency logs. Cancelling a service or requesting account deletion does not erase those independent public records. Do not include private keys in support messages.

5. Retention and deletion

We retain account administration information while the account is active and afterwards only to resolve remaining obligations, complaints or legal claims. Billing and transaction records are kept for the period applicable tax/accounting law and enforceable claims require. Domain records may be subject to independent registrar, registry and escrow duties. These criteria, rather than a universal period for every record, determine retention.

Support records are retained while the case or related service needs them and for a proportionate period to resolve repeat issues or establish a claim. Technical/security logs are kept for troubleshooting, prevention and investigation and restricted where preservation is justified. We assess deletion or anonymisation when information is no longer necessary, including on a valid account-closure or privacy request.

Customer-hosted content follows the service term, export arrangements and applicable processing agreement. An immediate cancellation or reinstall can remove the active environment. Do not rely on a post-termination retrieval period unless it is expressly agreed. Backup copies, if any, follow their stated rotation and legal preservation rules; deletion of an account does not imply every invoice, independent registry record or restricted recovery copy is erased immediately. Request the retention and deletion arrangements for your intended processing before purchasing a service with specific requirements.

6. Security and incident handling

We use measures proportionate to the service and risk, including access restrictions, confidentiality duties, transport security, credential protection and operational monitoring. We cannot guarantee that every attack will be prevented. A customer's software, passwords and independent backups remain its responsibility within the agreed service scope.

We investigate suspected incidents and give notifications required by law or a processing agreement. We will not describe an unverified certification, backup arrangement or security feature as implemented. Security reports should use support@fasting.host (subject: Security report); do not exploit another customer's data to prove a report.

7. Your choices and rights

Depending on applicable law, you may request access, correction, deletion, restriction, portability or object to particular processing. You may withdraw consent without affecting earlier lawful processing and complain to the competent privacy regulator. Some requests have lawful exceptions. We confirm that a request comes from the account holder or an authorised representative using proportionate account-control checks, without requesting government-issued identity documents. We respond within the deadline that applies, generally one month for applicable GDPR requests, explaining any permitted extension.

You can manage marketing preferences and unsubscribe using the available mechanism. Necessary service, payment, security and domain-expiry notices are separate from optional marketing. We will not require consent to optional marketing as a condition of handling a privacy request. Contact us if you act for someone else or need an accessible response format.

8. Automated decisions and children

We may use automated security or fraud signals to flag unusual activity. Contact support@fasting.host to ask for a human review of a disputed order or restriction, to understand the reason where it can lawfully be provided, or to correct inaccurate information. This notice does not authorise undisclosed decisions made solely by automated means with legal or similarly significant effects; any such process requires its own applicable disclosures and safeguards.

Our purchasing services are intended for adults and are not directed at children. Do not open an account if you are under 18. Report a concern that information about a child has been collected to the privacy contact so it can be assessed under applicable law. Customer-hosted services remain subject to the customer's own responsibilities.

9. Cookies, changes and contact

The Cookie Notice explains device storage and related choices. Material changes to this notice will be identified with a new version and communicated as appropriate; where a new purpose needs consent, it will be requested before that processing. A notice update does not legalise an incompatible use of existing data. Use support@fasting.host (subject: Privacy request) for questions or requests.

Back to policy index

Cookie and Device Storage Notice

1. How device storage is used

Cookies and similar technologies can support login sessions, shopping baskets, security, language/display choices and payment functionality. A cookie stores or accesses information on a device; the privacy implications depend on what it does and the information involved. Browser settings can manage cookies, but blocking essential storage can prevent requested features from working.

2. Necessary and optional technologies

Authentication, account-security and basket/session storage may be necessary to provide a feature you request. Optional analytics, advertising, cross-site profiling and nonessential embedded services require the choice or consent required by applicable law before activation. Continuing to browse is not treated as consent to optional tracking.

Where a consent control is needed, rejecting optional storage must be as accessible as accepting it. You can change a prior optional choice without losing access to basic services. Withdrawing consent stops future optional use; browser/provider tools may also be needed to remove previously stored information.

3. The published inventory

The marketing site uses a fixed visual configuration. It does not need to store the default theme layout, colour, font, header, background, radius or text-direction choices in cookies. The language code may read an existing locally stored "lng" preference; a default English visit does not create a new language preference. Local storage remains until cleared by the browser or site unless an expiry is implemented.

The WHMCS client area uses an installation-specific session cookie to maintain login, basket and session state; session cookies normally expire when the browser closes. If you choose a remember-me option, WHMCS can use a persistent user cookie (documented as WHMCSUser, up to 365 days or logout). Names may include an installation identifier. Authentication cookies are not disclosed by this notice or disclosed to unrelated sites.

WHMCS features can also use WHMCSAffiliateID (90 days) for referral attribution or WHMCSLinkID for link tracking when those features are used. They are not necessary simply to read our policy page; optional tracking requires the choice or consent applicable to its purpose. A policy link is not a substitute for a required consent control.

Returning visitors may still have cookies written by an older theme version: layout, color, background, font, header, textDirection or radius (previously up to 365 days), or cookieControlPrefs from the older notice (previously one day). You can remove them in browser settings. The updated fixed marketing theme no longer creates those default preference cookies or treats continued browsing as optional consent.

The AutoVM client-area integration can set the functional language cookie temlangcookie for up to 360 days. It stores the interface language, may be read by the client interface and can be cleared through browser settings; clearing it resets that preference. It is sent over HTTPS with a SameSite=Lax restriction.

4. Payments and third-party choices

When you use NOWPayments, Tebex or Amazon Pay, or follow another third-party service link, the provider may process device, cookie and transaction information under its own notice. The payment guide identifies our current payment options. Necessary checkout storage and connection data support the payment flow. We identify necessary third-party use and request consent where required. We will not load an unrelated tracking service because you accepted service terms.

The homepage includes a SourceForge review badge image loaded from sourceforge.net. Loading that image sends a request to SourceForge, including your IP address and ordinary browser/request information. The image is a link to our independent directory profile, not a representation that customers have supplied a particular rating. The image request uses a no-referrer setting; following the link opens SourceForge under its own privacy notice. The badge does not require a SourceForge widget script on the marketing site.

5. Updates and help

We review this notice when technologies or their purposes change. Material changes to optional processing may need a fresh choice. Contact support@fasting.host with cookie questions. Browser settings can clear cookies and local storage, but clearing authentication/session data can sign you out or empty a basket. This notice does not claim that accepting a generic banner enables or disables every third-party technology.

Back to policy index

Backup, Security and Data Lifecycle Policy

1. Backup scope

Unless an accepted plan expressly includes a backup service with a stated scope, schedule and retention, no managed backup or restoration commitment is included. A control-panel feature, provider snapshot or occasional maintenance copy is not proof of a complete, tested recovery service.

Keep independent off-service copies of files, databases, configurations, encryption keys and other important data, and test restoring them. A backup stored only inside the same VPS can be lost with that VPS. Never assume a backup includes an external database, email service or customer-controlled encryption key.

2. When a backup service is included

The service description must specify what is copied, how often, how long copies are kept, relevant location and access protections, exclusions, and any restoration charge. We will describe known limits such as crash-consistent snapshots, databases requiring application-aware export, or customer encryption that prevents recovery without a key.

Restore points and retention are not guarantees of recovery to every second. We will use reasonable care for a purchased backup service and explain a known failed backup or restore. Unspecified recovery time and recovery point objectives are not promised. Mandatory remedies for a defective purchased service remain available.

3. Security responsibilities

We operate the infrastructure within the purchased scope. On unmanaged VPS services you maintain guest software, access permissions, application security and configuration. Do not expose unnecessary services or reuse compromised credentials. Tell us promptly about a suspected compromise so we can coordinate proportionate containment.

Maintenance, suspension and incident investigation may affect access. We will restrict access only as justified by the contract, a security need or law. Support access to customer content should be limited to what is necessary for the authorised task or a lawful security purpose.

4. Cancellation, deletion and recovery

Export your data before the service ends. An immediate cancellation or an agreed reprovisioning/reinstallation can destroy the active environment. An end-of-term cancellation normally leaves the paid service accessible until that term ends unless a separate justified suspension applies. Do not request deletion or reinstall if you only intend to stop renewal.

After termination, deletion follows the retention criteria in our Privacy Notice and any agreed service schedule, legal preservation duties and any agreed processing addendum. Recovery copies may be unavailable; do not rely on a grace period for retrieving content. Copies kept solely for lawful retention or recovery must be access-restricted and not reused for an unrelated purpose. At the end of their permitted retention they are deleted or overwritten through the applicable lifecycle.

5. Incident and recovery assistance

Report the affected service, event times and symptoms through the support/security contact. Do not send live passwords in a public report. We will explain available recovery options, known limitations and any quoted work before charging. A restoration or migration does not remove the need for a fresh customer backup and verification of the application.

Back to policy index

Service Availability and Support Policy

1. Getting assistance

Use support@fasting.host or a client-area ticket. State the service identifier, symptoms, timestamps, recent changes and steps already tried. If you cannot sign in, email support@fasting.host. Never include full card credentials or unnecessary personal information.

Support covers account, billing and the service scope purchased. Guest operating-system administration, custom software debugging, migrations and third-party application work are included only when expressly stated. We will identify chargeable work and obtain agreement before starting it.

2. Response and resolution

We prioritise issues according to impact, security and the agreed service. Acknowledgement is not a guarantee of resolution at that time. Support is available 24/7 through online tickets and email. Response and resolution times depend on the issue, its impact and the service scope. No fixed response target, numerical uptime SLA or automatic service credit is promised unless a written service description expressly includes it.

For an outage we will investigate the infrastructure within our control, coordinate with relevant suppliers and provide reasonable updates as information becomes available. Planned maintenance will be communicated where practicable. Urgent protective maintenance may need to proceed before advance notice is possible.

3. Fair treatment and remedies

We will consider evidence and explain significant decisions. Escalate an unresolved issue using the complaints process. A missing service-credit scheme does not remove statutory rights to an appropriate remedy for a service we fail to provide. We do not advertise an unconfigured SLA as a guarantee.

The accepted order determines the resources, location and operating-system availability. Descriptions of host uplink capacity, DDoS mitigation and unmetered traffic have the qualifications in the Fair Use Policy. Customers needing a specific availability commitment should obtain a written agreement before ordering.

Back to policy index

Abuse, Copyright and Security Reporting Policy

Offshore and DMCA-ignored service positioning

Fasting Host handles DMCA and copyright reports directly across all our services. We review reports individually and do not automatically suspend a service solely because a copyright allegation is received. Our offshore, DMCA-ignored and privacy-focused positioning does not remove applicable legal requirements, binding court orders or our responsibility to address prohibited abuse. We protect customer privacy and disclose information only as described in our privacy notice and applicable obligations.

1. Where to send a report

Use support@fasting.host; use the subject Abuse report, Security report or Copyright report. You do not need a customer login to email a report. Provide the exact domain or IP, URLs where applicable, relevant times with timezone, the type of issue, supporting evidence and a way to contact you. For an immediate threat to life or safety, contact the appropriate emergency authority too.

Do not include illegal images, executable malware attachments, passwords, stolen datasets or identity documents. Use a concise description or a safe reference. If evidence is particularly sensitive, ask for a suitable secure submission method first.

2. Assessment and response

We assess actionable evidence, check which service is involved and may request missing information. Our response may include notifying the account holder, requiring remediation, limiting traffic, disabling particular content, suspending the affected service or referring a matter to the responsible registrar, registry or authority.

We consider urgency, legal obligations, the reliability of the evidence and collateral impact. Not every disagreement or unsupported complaint justifies taking a site offline. Where lawful and appropriate, we explain the decision and how the customer can seek review. We preserve necessary evidence only for a justified period.

3. Copyright complaints

A copyright report should identify the protected work, the specific allegedly infringing location, the reporter's contact details and authority to act, and explain the good-faith basis for the claim. A formal notice under applicable law may require a signature and additional statements about accuracy and authorisation. Email support@fasting.host with the subject "Copyright report".

We may forward sufficient information to the affected customer so it can respond, while considering legal requirements and safety. Repeated substantiated infringement may lead to account termination in appropriate circumstances. We consider legitimate objections, mistaken identity and lawful uses.

The contact above is our general copyright-reporting channel. We do not represent it as a registered US DMCA designated agent or claim statutory safe-harbour status through this policy. Any legally required designated-agent notice and counter-notice procedure will identify the verified designation and applicable process; general correspondence does not waive either party's legal rights.

4. Vulnerability reports

Report a suspected vulnerability privately with a minimal reproducible explanation, affected endpoint, impact and your contact details. Stop when you have demonstrated the issue safely. Do not access unrelated customer records, modify data, persist access, extort payment or conduct disruptive testing. This reporting process does not authorise access to systems or promise a bounty or blanket legal immunity.

We will review good-faith reports and coordinate remediation and proportionate disclosure. Ask before sending exploit attachments or sensitive data. We do not make an unverified response-time guarantee.

5. Legal requests and appeals

Legal or law-enforcement requests should identify the requesting authority, legal basis, affected identifiers, scope and relevant deadline. We verify authority and assess applicable requirements before disclosure; informal demands are not treated as unlimited access. We may notify the affected person where lawful and appropriate.

Reporters and customers can ask for a decision to be reviewed through support@fasting.host (subject: Complaint). A complaint should include the original reference, the disputed action and the correction sought. We will consider new evidence and explain the outcome where we can lawfully do so.

Back to policy index

Complaints and Dispute Resolution Policy

1. How to raise a complaint

Contact support@fasting.host (subject: Complaint) with the account or service identifier, relevant dates, the issue, evidence and the resolution you seek. Use the public route if you cannot sign in. We will verify account control proportionately where access or a refund is requested. Do not send unnecessary confidential information.

2. Our process

Our handling targets are acknowledgement within two business days and a substantive response within ten business days. A complex investigation may take longer; we will explain why and provide an update date. These are handling targets, not a shorter limit on legal rights or a guarantee that every technical issue is resolved in ten days.

If you disagree, request escalation for a fresh review by a responsible person who was not the original decision-maker where practicable. We will consider the contract, evidence, applicable law and a fair remedy. We will not penalise a customer merely for making a good-faith complaint or exercising a payment-dispute right.

3. External rights

You may use a competent court, privacy regulator, payment-provider dispute process, registry/registrar procedure or applicable consumer dispute scheme. We do not claim membership of an ombudsman, arbitration or certification scheme that has not been verified. Your mandatory local rights and access to competent courts remain available.

Domain ownership disputes may follow ICANN or registry rules rather than this ordinary support process. Copyright notices and urgent security matters should use their dedicated reporting process. Contacting us does not suspend a legal filing deadline or remove a right to seek urgent relief.

Back to policy index

Data Processing Addendum

1. Scope and roles

These processing terms describe the framework for a customer's use of purchased hosting/VPS services to process personal data where Fasting Host acts as its processor/subprocessor. Contact support@fasting.host before placing regulated, sensitive or location-restricted personal data on a service. Fasting Host remains an independent controller for its own billing, account administration and legal duties described in the Privacy Notice. Registrars and payment providers are not automatically subprocessors of customer-hosted content.

A service-specific processing agreement must identify the actual processing particulars, authorised subprocessors, locations, security measures, return/deletion arrangements and any required transfer mechanism before the relevant processing begins. The framework below does not itself execute transfer clauses, approve an unspecified subprocessor, or certify compliance with every privacy law. It applies with the parties' completed agreement and schedules.

2. Processing particulars

Subject matter: supplying the purchased hosting/VPS environment and agreed support or backup services. Duration: the service term plus the limited return/deletion period set out in the agreed service schedule. Nature: storage, retrieval, transmission, protection, support access and deletion, with backup only where purchased. Purpose: operating the customer's instructed online service.

Data subjects may include the customer's users, staff, contacts, suppliers and visitors. Categories may include contact, account, communications and application data selected by the customer. Special-category, criminal-offence or highly regulated data is not included in a default approval; discuss the requirements and suitability before placing it on the service. The customer controls what it uploads and the lawful instructions it issues.

3. Instructions, confidentiality and security

We process customer personal data only on documented lawful instructions, including the service configuration and agreed support requests, unless law requires otherwise. Where legally permitted, we inform the customer of a conflicting legal requirement. We will notify the customer if we believe an instruction infringes applicable data-protection law.

People authorised to access customer personal data must be subject to confidentiality duties. We maintain technical and organisational measures appropriate to the agreed processing and risk. The agreed measures schedule must identify access control, credential management, transport protection, isolation, logging, patch responsibilities, backup scope and incident response; it must not list a certification or encryption mode without evidence.

4. Subprocessing and transfers

Only the agreed authorised subprocessors and purposes in the schedule are authorised at the start. Before adding or replacing a relevant subprocessor, we will give advance notice, normally at least 30 days, and a reasonable opportunity to object on data-protection grounds. We will work in good faith on an alternative; if a material justified objection cannot be resolved, the affected processing may be ended with an appropriate refund for the unused unprovided service.

We impose the required data-protection obligations on relevant subprocessors and remain responsible for their performance to the extent required by applicable law. Restricted international transfers require an applicable, properly implemented mechanism and any required assessment or supplementary measures. This addendum alone is not an executed set of Standard Contractual Clauses or a UK transfer addendum.

5. Assistance, incidents and accountability

Taking account of the nature of processing and information available, we reasonably assist with relevant individual-rights requests, security obligations, impact assessments and regulator consultations. We forward requests concerning customer-controlled data and do not independently respond in the customer's name unless instructed or legally required.

We notify the customer without undue delay after becoming aware of a personal-data breach affecting its processed data, with available information about scope, likely effects and remedial steps. We provide updates as facts develop. This does not start our notification clock only after a complete forensic investigation or guarantee that every incident will be fully described immediately.

We make available information reasonably needed to demonstrate the agreed processing obligations and permit required audits, including inspections under appropriate confidentiality and security arrangements. We may propose proportionate coordination to protect other tenants, without making required audit rights illusory. Any agreed assistance fee must be reasonable, disclosed and lawful and must not obstruct an urgent legal obligation.

6. End of processing and liability

At the customer's choice, we return or delete customer personal data after the service ends, subject to a lawful retention requirement. The schedule must define the export window, active-data deletion and restricted backup expiry. Data retained by law is isolated from ordinary processing and deleted when the requirement ends.

Each party is responsible for its legal duties and authorised acts. Contractual limits apply only to the extent consistent with mandatory data-protection law and do not remove a person's statutory rights or a regulator's powers. A required transfer mechanism prevails over a conflicting standard term. This addendum takes effect only with the completed schedules and the parties' valid adoption.

Back to policy index