Privacy Policy

Effective date: October 23, 2026

1. Who we are and what this policy covers

LiveblogAI provides tools for media organizations and teams to manage, collaborate on and publish live coverage. In this policy, we use “LiveblogAI,” “we” and “us” to refer to the team operating the service. You can contact our team at support@liveblog.ai.

This policy covers our website, customer accounts, management application, support interactions and the technical operation of our hosted reader experiences. It explains both information we process for our own business purposes and information we process on a customer's instructions.

For account administration, customer communications, billing administration and our own service security and analytics, we determine the relevant purposes of processing. For personal information in content that a customer entrusts to us for hosting, collaboration and publication, we generally act on that customer's instructions under our Data Processing Addendum (DPA). Roles depend on the actual processing activity. A publisher's own privacy notice applies to its editorial choices and its website's independent data collection.

2. Information we process

Authentication is provided through Firebase Authentication. Depending on the method you choose, Google, GitHub or X may provide sign-in information. The information those providers process independently is governed by their own notices.

When you enter payment details into a payment provider's checkout, the provider processes those details under the applicable checkout arrangements. The checkout identifies the provider and seller involved. We use payment status and transaction information to administer the service; we do not ask you to send full payment-card details to support.

Organization administrators can access membership and activity information within their authorized scope. Content you publish may include author attribution. Leaving a team or closing an individual account does not automatically remove an organization's publications or the records needed to account for its activity.

Published content, including personal information within it, may be viewed, saved, copied, redistributed or indexed by third parties. Deletion from LiveblogAI does not guarantee removal of independent copies or search-engine records outside our control. We still carry out our own deletion obligations and provide reasonable assistance where required.

Links to external websites may take you to services governed by their own privacy notices. Their independent collection and use of information is subject to those notices. This does not remove our responsibility for information we disclose or transmit to them.

3. Cookies, browser storage and page analytics

We use authentication and browser storage to support sign-in, email-verification flows and preferences such as language, theme and the last selected workspace. Blocking necessary storage may prevent those features from working.

We use Google Analytics 4 (GA4) on our website and management application to understand page usage and improve the product. We do not use this analytics setup for advertising targeting or remarketing. Our analytics policy excludes customer content, names, email addresses and actual organization or liveblog identifiers from the information we intentionally send. Page information is filtered to avoid sending sensitive query parameters and identifiers.

Optional analytics is disabled until you choose to allow it. You may reject it and continue browsing our website or using all purchased application features. Accepting our Terms of Service does not constitute consent to optional analytics. Each person makes their own choice; an organization's choice does not replace its members' choices.

You can change your choice through the website's cookie settings or the application's personal privacy settings. Acceptance and rejection are remembered for six months, separately for the website and application; choices are not automatically synchronized across devices. Withdrawing consent stops future optional analytics under that choice but does not itself delete information already sent. Contact us to exercise applicable deletion rights.

GA4 may use first-party identifiers and browser or device information; page filtering does not make all analytics anonymous. Necessary billing, security and service-operation records are separate from optional page analytics.

4. Error reporting and embedded readers

We use Sentry for technical error reporting where enabled. Our website, management application and backend components use filtered reports containing technical information such as event time and identifier, service and operation category, deployment version, restricted failure classifications and application code locations. Reports are constructed to exclude customer content, account identity, request bodies, credentials and unrestricted error text. Code-location information may include approved source paths, function symbols, line and column numbers and source-map identifiers. Error reporting is separate from GA4 page analytics.

The hosted reader runtime has a narrower reporting scope. It reports selected failures in our own reader logic, using a fixed module and operation, restricted error type, fixed explanation, version/environment, event identifier/time and the location within our reader runtime. It does not intentionally include the host page's address, customer content, account identity, reading history or unrelated host-page errors. Its diagnostic requests omit cookies and referrer information. This does not mean that a network recipient cannot receive an IP address or other automatically transmitted network metadata.

Our reader diagnostics do not include session replay, performance tracing or an activity trail. Raw reader diagnostic reports are retained for 90 days. Access is limited to authorized technical troubleshooting personnel; operations and sales personnel do not receive access by default. Other operational logs and error-reporting projects follow the retention criteria in section 7; the reader's 90-day rule should not be understood as a claim about every technical record.

Our official reader is not used to add GA4 page tracking to a publisher's site. Loading the reader, images and updates nevertheless involves network requests. A publisher's website, custom theme or third-party content may carry out separate processing. Embedded YouTube, X, TikTok, Facebook content and external images or HTML can contact those providers when loaded. Privacy-enhanced embed options do not eliminate all third-party processing. Follow the publisher's notice and choices for those features.

5. How we use and protect information

We use information to provide the requested service, manage accounts and permissions, deliver content, administer billing, answer requests, maintain security, resolve faults and meet applicable legal obligations. Optional analytics and requested promotional updates are handled separately from essential service communications.

Where European or UK data-protection law requires a legal basis, the relevant basis may be performance of our contract with an individual, our legitimate interests in administering an organizational customer relationship and operating and securing the service, compliance with legal obligations, or consent for optional analytics and other processing that requires consent. We assess the applicable basis for the activity and do not treat acceptance of this policy as blanket consent. Processing of customer content on instructions is addressed by the customer's legal basis and our DPA obligations.

Staff may not browse non-public content merely because they have administrative access. Support access to that content requires customer authorization and is limited to what is necessary. Necessary access for security, abuse investigation or valid legal requirements may occur without prior authorization; we notify customers where permitted and appropriate. Access is restricted by responsibility, subject to confidentiality and recorded. We use reasonable technical and organizational safeguards, but no service can promise absolute security.

Our standard Terms do not guarantee the confidentiality of uploaded content, including unpublished drafts. That contractual disclaimer does not change the access restrictions, processing limits or safeguards described in this policy, authorize public disclosure of private content, or remove obligations under applicable data-protection law or an expressly agreed DPA.

The service described here does not provide built-in AI content processing or model training. We do not use customer content to train AI models. Customers may choose and authorize their own third-party agents through the integrations we make available, including MCP and Skills where offered. Information transferred to a customer's agent or its providers is subject to that customer's choices and those providers' arrangements. Revoking an integration prevents future authorized access but does not retrieve external copies or reverse completed actions.

6. Recipients and international processing

We disclose information to providers only as needed for their assigned purposes, subject to the arrangements appropriate to their role. Our service-provider categories include:

The deployment-specific provider register, including relevant entities, processing locations and customer-content subprocessors, forms part of our DPA arrangements. Providers processing information for their own legally defined purposes may have separate responsibilities and notices; not every provider in this table is a subprocessor for every activity.

We may disclose necessary information in response to binding legal requirements, to protect the service and people from abuse, or to handle a legal claim, subject to applicable law. We do not obtain a right to sell customer content or use it for independent advertising merely by hosting it. Using a customer's name, logo or content in our marketing requires separate permission.

Information may be processed outside your country. We do not promise storage or processing exclusively in any particular country. Where required, transfers are subject to a valid mechanism, such as an applicable adequacy decision or appropriate contractual safeguards, together with any required supplementary measures. Contact support@liveblog.ai for information about applicable safeguards.

7. Retention, archiving and deletion

Customer content remains stored while the relevant subscription is active, subject to valid deletion requests and lawful restrictions. Ordinary soft deletion is recoverable and is not permanent erasure. Liveblogs use archiving and unarchiving; soft-deleted posts and related records follow their own visibility rules. Existing references to soft-deleted structured records may remain readable. We do not describe archiving or soft deletion as complete removal from all systems.

After a paid service period ends without renewal, we normally retain content for read-only access and export for up to two years, calculated from the end of the last applicable paid period. Editing, new publication and real-time features stop. This is a conditional retention arrangement: significant service changes may require an earlier end, in which case we give at least 30 days' notice and an opportunity to export. We also notify the organization owner 30 days before ordinary expiry. If our fault prevents export during the available window, we provide a reasonable extension rather than clearing the affected content before the problem is resolved. Detailed refund and restart rules appear in the Terms.

A successful new paid subscription during retention returns remaining data to active-subscription retention. A later cancellation starts a new retention period from the latest applicable unrefunded paid period's end. Payment does not automatically unarchive or restore soft-deleted content, and it cannot restore permanently cleared data. Soft-deleted data follows the same organizational retention arrangement rather than a separate 30- or 90-day deletion timer.

To request permanent deletion, contact support@liveblog.ai. We verify authority and scope, explain the effects and provide an export opportunity where appropriate. An organization owner can request earlier permanent deletion without waiting for retention to expire. An individual's account deletion does not automatically delete an organization's reporting; we assess individual privacy requests separately.

Permanent deletion ends normal service access to the affected content. Residual backup copies and records that must be kept for legal purposes follow separate restricted retention arrangements; deletion is not a promise that every copy disappears simultaneously. Backups are not a promise that permanently cleared content can be recovered for a customer.

For account, inquiry, billing, audit and security records, we retain information only as needed for the relevant service or relationship, applicable legal obligations, security investigations and the establishment or defense of legal claims. We consider the purpose, sensitivity, applicable requirements and whether less identifiable information would suffice. Raw reader diagnostics have the specific 90-day period described above.

8. Your choices and rights

Depending on applicable law, you may have rights to access, correct, delete or obtain a portable copy of personal information; restrict or object to processing; withdraw consent; and complain to a relevant data-protection authority or pursue other available remedies. You may object to processing based on legitimate interests where that right applies. Withdrawing consent does not affect the lawfulness of earlier processing. You may ask us to stop requested promotional updates without stopping necessary account or service notices.

Contact support@liveblog.ai. This is our primary contact point, not a reason to reject a valid request submitted another way. We use account or registered-email information where suitable to verify identity and ask for additional information only where necessary. We do not routinely require government identification.

We respond without undue delay and within applicable deadlines. Where an extension is permitted, we explain the reason and expected timing. Requests are normally free; we charge or refuse only where applicable law permits it and explain our decision and available complaint routes. A right to deletion is not an unconditional right to remove another organization's journalism or information lawfully retained for a different purpose.

For information a publisher controls, we ordinarily direct or forward the request to that publisher and assist it, while meeting our own obligations. We protect other people's information when responding and disclose only what the requester is entitled to receive.

9. Security incidents and changes to this policy

If we become aware of a security incident affecting customer data, we notify affected customers without undue delay, through their designated security contact or otherwise the organization owner. We provide known facts first, then updates as investigation continues, and take reasonable containment and remediation measures. We assist customers with their obligations and meet our own legal and contractual notice requirements.

For material changes affecting customer rights, we provide at least 30 days' advance email notice and an application notice explaining the changes and effective date. Minor wording corrections or clarifications may be recorded with an updated date and change record without individual emails. We explain new purposes or expanded collection before beginning them and obtain fresh consent where required. A policy update does not itself authorize a new use of customer content or replace required consent.

10. Contact

LiveblogAI team: support@liveblog.ai