Legal

Privacy Policy

Effective November 4, 2026

Draft. This document is being reviewed and is not yet in effect. The company details are still to be added.

1. Who is responsible

LiveHQ is responsible for the personal data described here (“we”). This policy covers the LiveHQ console, agent, edge and this website.

The apps you run with LiveHQ may process personal data of their own users. For that data, you decide what happens to it and we act only on your instructions, as your processor. We will sign a data-processing agreement with you on request at [email protected].

2. What we collect

Your account

Your name and email address, and your sign-in methods: a password (stored only as a hash), passkeys (we keep the public key), two-factor authentication and recovery codes. Also your workspaces, their members and invitations.

Sign-in and security

When you sign in we record the time, your IP address and your browser, so we can show you your sessions, detect misuse and investigate incidents.

The servers you connect

Each server’s name, its current public IP address, its operating system and agent versions, its health and update status, and usage metrics such as CPU, memory, disk and network.

Your apps and deployments

  • App and database names, addresses and custom domains.
  • The repositories you connect, and build and deployment logs.
  • Usage per app: bandwidth and request counts.
  • The names of your app variables. Their values are sealed in your browser to your server’s key, and nothing at LiveHQ can open them.

Traffic to your apps

Your visitors’ requests cross our edge on the way to your server. As with any content delivery network, encryption ends at the edge so it can route the request and check access. We don’t store the contents of requests or responses. The edge uses the visitor’s IP address in memory for rate limiting and passes it to your app. When request logging is on, it records the method, the path without any query values, the status and the timing, not the IP address. When your app’s firewall blocks, challenges or logs a request, we keep that request’s time, IP address, country, method, host, path without query values and browser for 24 hours, so you can see what was stopped and act on it.

People you share private apps with

The email addresses you invite and their access sessions, so the edge can let them in.

Backups you choose

If you schedule database backups, encrypted copies are stored off your server. We hold their keys so we can restore them for you.

Billing

Your plan, invoices and the identifiers of your Stripe customer and subscription. Stripe handles your card details; we never see your full card number.

When you contact us

What you send us, and our replies.

3. What we don't do

  • We don’t sell or rent personal data, and we don’t use it for advertising.
  • We can’t read your sealed app variables, from our database, our backups or our staff.
  • We can’t log into your server or run a shell on it; the agent accepts only exact, typed commands.
  • This website uses no analytics and sets no tracking cookies. The launch film loads from YouTube’s privacy-enhanced mode only when you press play.

4. Why we use it

  • To provide the Service you signed up for: to run your account, deploy and route your apps, bill you and support you. This is necessary to perform our contract with you.
  • To keep LiveHQ secure and working: to detect abuse and attacks, investigate incidents, and measure and improve reliability. This is our legitimate interest, and yours.
  • To meet legal obligations: for example tax records and lawful requests.
  • To tell you what matters: security notices, failed deployments, bandwidth alerts and changes to these documents. We don’t send marketing email without your consent.

5. Cookies

The console uses only cookies needed to keep you signed in and protect your session. Private apps use an access cookie on their own address so a visitor you invited stays signed in. When an app’s firewall asks a visitor for a browser check, a security cookie on that app’s address remembers the passed check for an hour. We don’t use advertising or analytics cookies.

6. Who helps us process it

These providers process data for us, under contract and only for the purposes below:

ProviderWhat forWhere
DigitalOceanLiveHQ's database (accounts, workspaces, servers, deployments)United States (New York)
Application hosting (to be named)LiveHQ's API and background workersTo be named
KoyebThe LiveHQ edge that carries your apps' trafficRegions where the edge runs
CloudflareDNS, certificates and delivery for app addresses; encrypted storage for database backups and short-lived diagnosticsGlobal network
StripePayments and invoicesUnited States and others
ResendAccount, security and notification emailsUnited States
GitHubRepositories you choose to connectUnited States

We will update this list before adding a provider that processes your personal data. We disclose data to others only when the law requires it, to protect people or the Service from harm, or as part of a merger or sale, where the new owner remains bound by this policy.

7. International transfers

LiveHQ’s database is in the United States, and our providers operate in several countries. When we transfer personal data from a country that restricts transfers, we rely on appropriate safeguards, such as the European Commission’s Standard Contractual Clauses.

8. How long we keep it

We keep data only as long as it is needed, and delete it automatically on this schedule:

DataKept
Account, workspaces, apps, databases and serversUntil you delete them or close your account; then within 30 days
Sign-in and security history (IP address, browser)30 days
Expired sessions, sign-in challenges and codes24 hours after they expire
Build and deployment logs, server and app metrics24 hours
Firewall statistics and blocked requests (visitor IP address, country, path, browser)24 hours
App logs you open in the consoleRead from your server on request; the result is kept 10 minutes
Bandwidth usage per app72 hours after its billing period ends, and at least 35 days
Finished deploymentsThe live release, its rollback target and the newest five per app; others 30 days
Servers you removeTheir reports at once; the server record after 30 days
Database backups you schedule (Pro)Under your backup schedule, until you delete them or the database
Billing recordsAs long as tax and accounting law requires

Data on your servers stays there and is under your control: LiveHQ doesn’t keep your apps’ files or databases, apart from the backups you choose.

9. Your rights

You can ask to access, correct, export or delete your personal data, and to restrict or object to how we use it. Write to [email protected] from your account’s email address. We answer within 30 days. To close your account, ask at the same address; we delete its data within 30 days, except what the law requires us to keep.

You can also complain to a data-protection authority, such as the one where you live.

10. Security

We protect data with encryption in transit and at rest, sealed app variables, least-privilege access and signed updates; the security page explains each layer. If a breach affects your personal data, we will tell you without undue delay.

11. Children

LiveHQ is not meant for anyone under 16, and we don’t knowingly collect their data.

12. Changes to this policy

We will post updates here with a new effective date, and tell you by email or in the console before a material change takes effect.

13. Contact

Privacy questions and requests: [email protected].