The practical rules behind the service.

Service terms

Initial launch availability: when public checkout is enabled, paid Lite and Plus hosting will be available to eligible US-based customers, with initial capacity limited to 10 sites across LiteWP. Connect a domain you already own. Public free trials and new domain purchases are not available during this launch. Existing trial and domain services retain their accepted terms and obligations.

AWS contracting review. At this initial launch, we use existing AWS accounts and have not completed confirmation that their governing agreement covers LiteWP, Inc. Resolving this question, and making any necessary account or contractual changes, is our first post-launch task. This is an unresolved contractual matter, not a statement that AWS provides no data protections. This disclosure does not waive your rights, establish the missing confirmation, or excuse any provider arrangements required by applicable law.

LiteWP provides managed WordPress hosting on annual, per-site plans. Each plan has the storage, request, transfer, backup, email, and runtime limits shown on the pricing page. Customer plugin and theme installation is unavailable during this initial launch, as described below. There are no automatic overage charges. We may ask you to reduce sustained use that materially exceeds the published envelope, move the site to a suitable plan, or suspend the resource-intensive function after notice when practical.

You retain ownership of your content and domains. You give LiteWP the limited permission needed to store, process, back up, and deliver that content to operate the service. During this initial launch, LiteWP manages WordPress and the included Twenty Twenty-Five theme. You can edit pages and content, but customer installation or changes to plugins, themes or WordPress versions are unavailable. Arbitrary uploaded PHP and executable uploads are not supported on pooled hosting.

We use reasonable security, backup, and availability controls, but no internet service is failure-free. Customers remain responsible for lawful content, protecting their account and recovery methods, reviewing changes, and retaining exports needed for their own obligations. Authenticator-app MFA is optional for ordinary customer access but may be required before sensitive domain, recovery, export, or WordPress administration actions. We may make urgent changes needed to contain abuse or a security incident.

Plans renew annually until canceled. Canceling hosting renewal keeps the site online through the end of the paid term, then hosting stops. Cancellation does not delete the site or cancel a separately authorized domain renewal. See data retention and deletion for what happens to retained content.

30-day hosting trial

Where offered, each LiteWP account may use one 30-day trial on a LiteWP subdomain with the Lite plan’s resource limits. No payment card or subscription is required. The trial starts when WordPress is ready, not when you request the site. Deleting a trial site does not create another trial entitlement. Trials are subject to available capacity and the same acceptable-use rules as paid hosting.

To keep the same site and content, choose Lite or Plus and complete checkout. The first annual term is charged at checkout and renews annually until canceled. Custom domains require paid hosting; domain purchases and renewals are separately priced. Starting a trial does not authorize automatic payment.

If you do not upgrade, hosting pauses after 30 days. Your dashboard shows a further 14-day recovery deadline during which you may upgrade. After that deadline, the site is scheduled for deletion. We send reminders before trial expiry and before scheduled deletion. Protected backups and noncurrent media copies expire under their existing retention policies; deletion does not erase those copies immediately. Export anything you want to retain before the deadline.

Privacy notice

Who we are and whose information this covers

This notice explains how LiteWP, Inc. handles personal information for its own account administration, billing, support administration, security, and other stated operational purposes. When we process information in a customer’s hosted website on that customer’s behalf, the customer determines its use and the customer processing agreement applies. A website-data copy supplied for troubleshooting remains subject to that processing purpose; it does not become ours to reuse for unrelated purposes.

Public trials and new domain registrations are not offered during the initial launch. References to records of those services concern any previously provided services and their applicable retention periods.

Information we use and why

We use account and contact details, sign-in information and MFA status, billing references, site settings, support messages, operational logs, usage totals and security events to run LiteWP. You give us information when you create an account, contact support or order a service. Providers also return information needed to complete sign-in, payment and domain operations. We use this information to provide and secure hosting, process payments and domains, communicate with you, diagnose problems, prevent abuse and meet applicable legal obligations.

Our AWS Cognito sign-in service handles account authentication. Google also processes sign-in information when you choose Google sign-in. That optional flow requests your Google identity, email and basic profile information; LiteWP uses the identity and verified email to sign you in. It does not give LiteWP access to your Gmail messages or Drive files. Password and optional authentication-factor handling are part of account security, not advertising.

For paid hosting, we send Stripe your account email or existing Stripe customer reference, selected plan and quantity, and identifiers linking checkout to your account, order and accepted terms. Stripe’s hosted checkout collects payment details and your billing address, including when you connect a domain you already own. We receive payment, subscription and reconciliation information needed to provide and administer the service.

Before hosting, we ask who the customer is, where they are based and whether you can act for them. For organizations, we ask about foreign ownership. For client sites, we ask who the client is, where they are based and whether you are authorized to use LiteWP for them. We ask about intended markets, relevant foreign organizations or data-transfer commitments, and data that needs additional protections. These answers help us assess availability, confirm authority and review uses we may not support. Describe data types, not real medical records or other people’s private information.

Account details are needed to set up hosting and payment information to buy paid hosting. You can browse public pages without an account. Choosing Google sign-in or accepting hosting terms does not authorize unrelated uses. If we rely on consent for an optional use, we explain it separately and how to withdraw consent. LiteWP does not sell personal information or use customer WordPress content for advertising.

Providers and processing locations

We use Amazon Web Services for hosting, databases, media storage, recovery, sign-in, operational records, global delivery and service email. Google Workspace provides our support mailbox; our retained AWS email and storage forwarding route also delivers there. New support mail is no longer forwarded to personal Gmail. Restricted Workspace Drive and Sheets records track privacy requests, outcomes and current restore restrictions, with private Calendar reminders. They contain limited identifiers, decisions and dates, not entire websites or exports.

Stripe handles payments. For previously provided domain services, registration contact details pass through AWS domain services to the applicable registrar and registry. Payment, registration and optional sign-in providers may also process information for their own purposes under their terms, separately from hosting on your instructions.

The dashboard’s software screen can load plugin images or theme previews from WordPress.org image services, disclosing ordinary network information such as an IP address and browser information. An included theme preview can load even though customer software installation is unavailable. Links to WordPress.org open its separate website. See WordPress.org’s privacy notice.

Our main regional hosting and separate-account recovery services are configured in Oregon, with some control and edge-service resources in Northern Virginia. Global edge locations deliver and cache websites. Workspace may process information in countries where Google or its providers have facilities, subject to the applicable agreement and location commitments. A US-first customer policy does not mean all information stays in the United States. AWS and Google publish their AWS and Workspace provider lists; which providers handle information depends on the services used.

Older support copies in personal Gmail and the AWS forwarding store, and authorized operator working copies, require separate handling. The Workspace migration did not erase them. Contact support about arrangements relevant to your service.

Browser storage and tracking preferences

The dashboard uses browser session storage for sign-in, security checks and carrying site setup choices between pages. After you select Continue, it can save eligibility answers in that tab to help you resume setup. The saved draft is valid for one hour; expired answers are removed when the draft is next read. It does not authorize hosting or bypass eligibility checks. Blocking or clearing storage can interrupt these flows.

Our public pages and dashboard do not change their functions in response to the browser’s Do Not Track setting. We do not use advertising trackers in those pages. This does not mean there are no browser identifiers, service logs or third-party requests. We use request and operational records to measure service usage and diagnose problems.

Other parties may collect information about activity over time and across different sites when you use their services in our payment or sign-in flows. For example, Stripe describes device/browser and transaction processing across services for fraud prevention and security; collection depends on the services and features used. See Stripe’s privacy notice. Software images, linked third-party sites and customer WordPress sites have their own handling. Do Not Track is distinct from legally recognized opt-out preference signals; this notice does not waive applicable opt-out rights or claim that a Global Privacy Control handler has been implemented.

Service decisions

LiteWP checks eligibility answers, account and service records, capacity and hosting entitlement. Incomplete answers or a use needing review can hold a new site or purchase; we explain what needs attention before it proceeds. Entitlement checks can pause hosting when the entitlement ends. Contact support@litewp.com if you think a decision is wrong. Historical trial accounts remain subject to their accepted deadlines.

Requests and appeals

The dashboard provides site backups and site deletion where available; these site actions are not a whole-account export or account closure. For a whole-account access, correction, export, or deletion request, contact support@litewp.com. We handle those requests through support and explain any records that must be retained. See data retention and deletion for the different site deadlines and retained copies.

Depending on the law and processing involved, you may also have rights to know about processing, receive portable data, restrict or object to processing, opt out of sale, sharing, targeted advertising or certain profiling, and limit particular uses of sensitive information. Listing these rights does not mean we carry out each activity. Where we rely on consent, you can withdraw it without changing the lawfulness of earlier processing. We will not unlawfully discriminate against you for exercising privacy rights.

We may ask for information reasonably needed to confirm identity or understand the request. You may use an authorized agent where permitted; we may need to confirm their authority and your identity. Do not send passwords, authentication codes or full payment-card numbers. You do not need to purchase an account, identify internal records or download an export before requesting deletion.

We respond within the applicable legal time limit and explain any refusal or retained information, its reason and available complaint options. Where you have a right to appeal a refusal, email support@litewp.com and identify the decision. We review it and provide the outcome, reasons and available regulator complaint route within the applicable time limit. You may complain directly to the relevant authority where that right applies, without first contacting LiteWP. Internal housekeeping schedules do not extend your rights.

For information controlled by a website hosted on LiteWP, contact that website’s operator. We assist that customer with requests about hosted content. Requests about LiteWP’s own account records come to us.

Changes to this notice

The effective date appears above. We retain earlier versions. For material changes, we will explain them through an appropriate notice, such as email or an account notice, before they take effect where required. We obtain any separately required agreement or consent before the affected use. Updating this notice is not permission to use website data for a new purpose.

Data retention and deletion

Trial sites. The trial terms provide 30 days of hosting followed by a 14-day upgrade window. After that deadline, an unconverted trial site is scheduled for deletion. Starting a trial does not authorize payment.

Site deletion you request. A normal dashboard site deletion leaves the site recoverable for 30 days, as shown in the dashboard, before permanent removal is scheduled. Expired trials follow their separate deadline above. Deleting a site is not the same as closing your account or deleting a purchased domain.

Canceled paid sites. When paid hosting ends, content is not automatically purged on a fixed schedule. We retain it for recovery and customer-request handling until you request deletion or we schedule manual cleanup. If we schedule cleanup, we will email you at least 30 days before permanent deletion of the retained site content so you can export it, except where immediate action is legally required. This notice period applies only to cleanup we initiate after paid hosting ends. It does not extend trial deadlines or change deletion you request.

Backups and older media copies. Site backups follow the retention window shown for your plan on the pricing page. Scheduled infrastructure backups currently have retention periods of 35 days in the primary backup vault and 90 days in a separate backup account, measured from backup creation. Separate scheduled backups on the hosting servers have protection periods of 8 days for daily copies, 36 days for weekly copies and 366 days for monthly copies. A protection period prevents early removal; it is not an exact deletion deadline. Backup files can remain until their storage lifecycle rules remove them after protection ends. Older media versions have a retention period of 35 days after they are superseded. These are recovery-copy retention periods, not a promise of customer access to those copies or indefinite storage.

Other records. Deleting an active site or account record does not immediately erase historical backups or logs. Operational logs and billing, support, and domain records are retained for the service, dispute, abuse-handling, and legal purposes they support. Retention can depend on an outstanding payment, an open dispute or support case, or a legal preservation requirement. Contact support about records retained after account closure; we will explain the applicable retention period or criteria rather than promise immediate erasure of every copy.

Category-specific draft: the following periods are the proposed operating rules, not a claim that every removal is automated or that production account-wide deletion and every recovery route have been qualified. They remain subject to the publication review above.

Account information. We keep what is needed for your account and services. On account closure, we remove profile/contact details, memberships, display names and linked usage summaries no longer needed. A continuing payment, service or domain obligation does not justify keeping the entire profile. Trial identity/contact links no longer justified are included in a full account-erasure request; site deletion alone does not reset trial eligibility.

Site-use eligibility. We keep answers needed for an active site or order. After it closes, we remove unnecessary answers within 30 days, or sooner where required. Minimal review and restriction records follow the request-record rule below; unresolved payments, continuing restrictions and legal holds use only the information they need. Signup-only receipts are valid for one hour and then scheduled for expiry, not guaranteed physical erasure of every copy at that moment.

Support and temporary exports. Routine support correspondence is removed from the mailbox and other active copies we control within 12 months after resolution, including controllable trash and duplicates. You may request earlier deletion. Relevant dispute evidence follows its own purpose and period, not blanket retention of the conversation. Temporary export working copies are deleted within 30 days after fulfillment or closure, sooner when unnecessary. Undelivered copies are reviewed after seven days and at least every 30 days while delivery remains necessary. These periods do not extend request deadlines or control copies you download yourself.

Provider residuals. Removing active copies does not establish immediate erasure of provider recovery copies. Google’s processing terms describe up to 180 days for system deletion after deletion becomes irrecoverable through the service, with a separate termination sequence. This is not an observed deletion time or an extra allowance for LiteWP’s active mailbox, trash or downloads. Residual handling must be permitted for the information concerned and does not permit ordinary reuse.

Financial records. We normally keep invoices and supporting transaction records needed for accounting for five years after the end of the transaction’s calendar year. A longer applicable filing period or specific legal obligation can require longer retention. This does not require keeping website content or every account field. Test payments moving no real money are not customer revenue.

Agreement and purchase evidence. Necessary evidence of what you agreed to, paid for and received is kept while the affected contract is active and for up to six years after that term ends or is terminated, for contract claims. Relevant withdrawal, refund and correction evidence is included. A specific obligation or claim may require a different period; an unrelated renewal does not restart an older term’s period. Earlier deletion requests are assessed against the actual need for the records.

Unpaid checkout and delivery records. Unnecessary checkout evidence is removed 30 days after confirming that the order is unpaid and no payment, registration or service obligation remains pending; an expired checkout link alone is insufficient. Minimal delivery evidence follows the relevant record’s period. Detailed delivery diagnostics without a continuing purpose are removed within 90 days after delivery or final resolution of a delivery problem; some logs and queues expire sooner. Necessary evidence for a specific complaint is kept separately.

Request records and restore restrictions. A brief request/response record is kept for 12 months after resolution unless an applicable requirement needs a longer minimal record. For requests subject to the CCPA recordkeeping rule, we use 24 months after resolution. This does not require keeping the full conversation, identity documents or export. Minimal instructions needed to prevent erased data returning from recoverable copies remain until those copies are confirmed expired or removed; they have a separate purpose from the ordinary case record.

Continuing domains and specific holds. Necessary domain-management information remains while management or a related order continues. Afterward, only the necessary financial or contract evidence remains. Specific holds retain only necessary records, with review as the matter changes. When the reason ends, the original schedule applies rather than starting over.

Restricted recovery. A backup lock or internal preference is not a legal exception to deletion. Any delay must be permitted by applicable law and agreed instructions. The actual expiry/removal action and result must be tracked, not just the end of a protection period. Data covered by completed erasure is excluded from ordinary use; before restored data returns to service, current deletion/restriction instructions must be applied and checked. A restore route is not used for affected data unless these controls can be applied.

Operational schedules. Dashboard and domain service logs have 30-day retention, raw edge logs 14 days and regional analytics files 90 days. Hourly traffic counters expire after eight days; daily counters, ingestion receipts and application audit records use 400-day expiry, measured from processing, which can be later than the traffic. Monthly account-linked usage has no automatic expiry and follows the account-information rule above. Removal may occur after an expiry timestamp; backup copies follow their separate schedules. These are category-specific technical schedules, not blanket legal retention exceptions.

Cancellation and refunds

You can cancel hosting renewal from the Stripe customer portal at any time. Cancellation takes effect at the end of the paid annual term unless a refund is required by law or separately approved by support. Duplicate charges and billing errors will be corrected.

Free trials are not available during this initial launch. We do not offer an additional blanket money-back guarantee. Contact support about a paid service we cannot provide so we can resolve the issue or arrange an appropriate refund. We review other hosting refund requests case by case. Nothing in this policy limits any refund or other rights you have under applicable law.

Domain registration, renewal, redemption, and transfer charges are generally non-refundable once the registry action has completed, because it cannot ordinarily be reversed. If a domain order cannot be completed, contact support. Support will check the payment and registrar outcome, then cancel an uncaptured authorization where applicable, arrange a refund of the domain portion or an alternative you agree to. Refunds and replacement domains require operator review; they are not promised as an automatic response to an error. Please do not purchase the domain again while support is checking the order.

Hosting and domain charges are handled separately. Canceling hosting never transfers or deletes your domain and does not change an automatic domain renewal you have authorized.

Acceptable use

Do not use LiteWP for malware, phishing, credential theft, spam, illegal content, intellectual-property infringement, harassment, exploitation, unauthorized security testing, denial-of-service activity, evasion of platform limits, or attacks on LiteWP, another customer, or a third party. Do not attempt to cross tenant boundaries, access host credentials, or upload executable server code outside the reviewed catalog.

We may throttle or suspend harmful activity immediately when needed to protect people or systems. When risk permits, we will identify the issue and provide a way to correct or appeal it. Good-faith security reports should be sent to security@litewp.com and must avoid accessing other customers’ data.

Managed-domain terms

When you ask LiteWP to register or renew a domain, the dashboard shows the live registrar charge plus $1 per domain-year for managed DNS before payment. Registration uses the contact details you provide, privacy protection where supported, and the exact term you approve. Availability and pricing are not guaranteed until the registrar accepts the request.

Hosting renews through your annual subscription. Domain renewals are charged separately to your saved payment method when automatic renewal is enabled. Customers are responsible for current registration contact information and verification messages. Registry rules, eligibility requirements, transfer locks, expiration, redemption fees, and transfer timing vary by suffix and can override ordinary service timing.

Where combined checkout is offered, your initial hosting and one-year domain registration are paid in one checkout. You authorize us to use the individual name, email address, telephone number, and billing address entered in Stripe Checkout as the domain's registration contacts. Please use accurate registrant details and respond to registrar verification emails. Contact support before paying if the registration must be in an organization's name or needs different contact details.

Automatic renewal agreement. Automatic domain renewal is enabled for new combined orders and disclosed before checkout. When automatic renewal is on, accepting the checkout terms authorizes annual off-session charges to your saved payment method for the then-current domain renewal price plus $1 for managed DNS. We email the amount and intended charge date at least seven days before charging, normally charging 35 days before expiry. A changed amount requires a new notice period. You can turn off automatic renewal in LiteWP Billing before the charge date; turning it off does not reverse a payment already completed or processing. Hosting cancellation or site deletion does not cancel this separate domain-renewal authorization. Existing registrations are not enrolled automatically, and saved orders with automatic renewal off keep that preference.

A failed or declined payment does not renew the domain. We may retry the same payment up to three times and ask you to complete payment in Stripe if your bank requires authentication. Late payments, registrar failures, and incomplete contact details may require support review. If auto-renew is off, turn it on in advance or contact support for manual renewal before expiry. Keep your account email and payment details current; a domain that is not renewed can expire and be lost.

LiteWP keeps a purchased domain parked and separate from website deletion. You may request transfer unlock and an authorization code when the registry supports self-service export; some suffixes require operator or registrar support. Domain secrets are displayed only through a recent-MFA flow and are not retained in browser-visible logs. Failure to renew can result in expiration and eventual loss of the domain.