xPulse
🇬🇧 EN
🇩🇪DE 🇬🇧EN
Pages
Contents

xpulse-web – Page Content & Texts

Status: v2.0.0 · Repo: xpulse-web Companion document: concept.md (structure & infrastructure) Updated April 2026

This document contains the editorial content for all pages on xpulse.one. Texts are written as raw content – no HTML, no formatting. Final markup is applied during implementation of the respective page.

Legal documents follow the inheritance model: Platform base always applies. Tool supplements apply additionally. Tool documents explicitly reference the platform base.

Platform Pages

`/` – Platform Landing

Tagline

P2P Chat. Private. Encrypted.

Intro

xPulse is a platform for privacy-conscious communication and tools. No account. No data storage. No compromises.

Feature Pills

CTA

→ Open Chat (chat.xpulse.one)

Guide · Security · Changelog

`/about/` – About xPulse

What is xPulse?

xPulse is a platform for private, decentralised communication tools. The goal: genuine digital privacy without compromise. No tracking, no data storage, no account.

Principles

Peer-to-peer instead of server. Data belongs to the user, not to us. Encryption is not a feature but a foundation. Less is more – no bloat, no hidden dependencies.

Currently Available Tools

xPulse Chat – P2P real-time communication directly between browsers.

Tool: Chat

`/tool/chat/` – Chat Tool Landing

What is xPulse Chat?

xPulse Chat is a web application for private real-time communication directly between two browsers – without a server, without an account, without data storage. Messages are end-to-end encrypted and leave your device exclusively as an encrypted data stream directly to your conversation partner.

CTA

→ Open Chat (chat.xpulse.one)

`/tool/chat/guide/` – Getting Started

How does pairing work?

To chat with someone, you need to "pair" once – that is, add each other as a contact. This works via a pairing code:

  1. One person opens "Add Peer" and generates a code.
  2. The code is transmitted (e.g. via messenger, phone, or in person).
  3. The other person enters the code – the connection is established.
  4. Afterwards both are saved as peers and can chat at any time, as long as both are online.

There is no account, no email address, no phone number. The pairing code is the only means of authentication.

What happens when a peer is offline?

xPulse Chat is a pure P2P application – there is no server that buffers messages. If your conversation partner is offline, no messages can be transmitted. Messages you send while the peer is offline are lost.

Install as PWA

xPulse Chat can be installed on your device like a native app.

After installation the app behaves like a normal app – without browser UI, with its own app icon.

FAQ

Where are my messages stored? Exclusively locally in your browser (localStorage). No server, no cloud. If you clear the browser storage, the messages are gone.

Do I need an account? No. No account, no registration, no email.

Does xPulse Chat work with the Tor Browser? No. Details at /tool/chat/security/.

Can I use xPulse Chat on multiple devices? Peers are stored locally. You would need to pair again on each device. Cross-device synchronisation is not supported.

`/tool/chat/security/` – Security & Anonymity

What xPulse Chat protects

All messages are transmitted end-to-end encrypted (ECDH P-256 for key exchange, AES-GCM 256 for encryption). No server stores message content. There is no account, no email address, no phone number. Server-side logs contain only anonymised IP addresses (last octet is set to 0).

Limits of anonymity

WebRTC – the technology behind xPulse Chat – determines so-called ICE candidates during connection setup: possible connection paths including your local network IP and public IP address. These are exchanged directly between the peers, not via our servers.

What this means in practice: your conversation partner potentially sees your IP address. This is not a bug, but a fundamental characteristic of P2P connections.

What you can do

VPN (recommended) If you use a VPN, the peer only sees the VPN IP, not your real one. This is the most pragmatic and effective measure.

Chrome / Edge – hide local IP Under chrome://flags/#enable-webrtc-hide-local-ips-with-mdns the local network IP can be hidden via mDNS. This only protects the LAN IP, not the public IP address.

Firefox – disable local ICE candidates Under about:config set the value media.peerconnection.ice.no_host to true. Disables local ICE candidates. The public IP remains visible unless a VPN is used.

TURN-only mode (planned) In a later version there will be an option to route exclusively via the TURN server. Then both sides only see the TURN server IP – at the cost of latency and bandwidth.

Why Tor does not work

Tor routes exclusively TCP traffic. WebRTC primarily uses UDP and is actively blocked by the Tor Browser, as it is a known deanonymisation risk. xPulse Chat is therefore not usable with the Tor Browser – this is not a limitation on our part, but a deliberate protective measure of the Tor Browser.

Legal – Platform Base

`/privacy/` – Privacy Policy (Platform Base)

This privacy policy applies to the xPulse platform (xpulse.one) and all tools operated on it, unless a tool-specific privacy document adds something different.

Principle

xPulse is designed so that as little data as possible is generated. No user accounts are created, no email addresses are collected, no tracking is performed, no third-party services are integrated.

Website Access

When accessing xpulse.one, the web server logs technically necessary access data (IP address, timestamp, requested URL). This data is not linked to other data and not passed on to third parties. Legal basis: Art. 6 para. 1 lit. f GDPR.

Third Parties & Tracking

No tracking services, no analytics tools, no advertising, no external fonts or resources that transmit data to third parties.

Tool-specific Privacy Information

Supplementary privacy information may apply for individual tools. These are linked on the respective tool page and supplement – not replace – this platform base.

`/terms/` – Terms of Service (Platform Base)

These terms of service apply to the xPulse platform (xpulse.one) and all tools provided on it, unless tool-specific terms add something different.

Permitted Use

Prohibited Use

Availability

xPulse tools are provided without guarantee of availability. The service may be discontinued, restricted, or changed at any time without prior notice. There is no right to use the service.

Tool-specific Terms

Supplementary terms of service may apply for individual tools. These are linked on the respective tool page.

`/disclaimer/` – Disclaimer (Platform Base)

This disclaimer applies to the xPulse platform (xpulse.one) and all tools provided on it, unless a tool-specific document adds something different.

No Warranty

The content on xpulse.one has been created with care. No warranty is given for accuracy, completeness, or currency.

Beta Software

xPulse tools are in active development. No guarantee is given for freedom from errors, availability, or data consistency. Use is at your own risk.

Tool-specific Disclaimers

Supplementary disclaimers may apply for individual tools. These are linked on the respective tool page.

`/imprint/` – Imprint

Information in accordance with § 5 TMG

Name: [to be filled in via address service] Address: [to be filled in via address service] Contact: feedback@xpulse.one

Note: xPulse is a private, non-commercial project. No revenue is generated. It is operated without profit-making intent.

Legal – Tool: Chat

`/tool/chat/privacy/` – Privacy Policy (Chat Supplement)

This page supplements the platform privacy policy (xpulse.one/privacy/) for the specific operation of xPulse Chat. Both documents apply.

Message Content

Message content is never stored on our servers at any time. All messages are transmitted exclusively P2P and are end-to-end encrypted (ECDH P-256 + AES-GCM 256).

Local Data Storage

Peers, messages, and settings are stored exclusively in the browser's localStorage and do not leave the device. Optionally, this data can additionally be locally encrypted with AES-GCM.

Signaling Server Logs

The signaling server logs connection events (establishment and teardown) with anonymised IP addresses. The last octet is set to 0 (e.g. 192.168.1.0 instead of 192.168.1.42). In debug mode, full IPs may be logged. Legal basis: Art. 6 para. 1 lit. f GDPR.

TURN Server

The TURN server serves exclusively as a relay for connection establishment when a direct P2P connection is not possible. Message content is not stored.

IP Address & Anonymity

WebRTC exchanges IP addresses between peers during connection setup. Your IP address may be visible to your conversation partner. What measures you can take is described at xpulse.one/tool/chat/security/.

`/tool/chat/terms/` – Terms of Service (Chat Supplement)

This page supplements the platform terms of service (xpulse.one/terms/) for the specific operation of xPulse Chat. Both documents apply.

Permitted Use

Prohibited Use

`/tool/chat/disclaimer/` – Disclaimer (Chat Supplement)

This page supplements the platform disclaimer (xpulse.one/disclaimer/) for the specific operation of xPulse Chat. Both documents apply.

No Guarantee of Full Anonymity

Complete anonymity cannot be guaranteed. WebRTC exchanges IP addresses between peers during connection setup – your IP address may be visible to your conversation partner. What measures you can take is described at xpulse.one/tool/chat/security/. Browser configuration and network environment are the responsibility of the user.

Data Loss

Messages and peers are stored locally in the browser. When clearing browser storage, switching devices, or uninstalling the PWA, this data may be irretrievably lost.

Tor Browser

xPulse Chat is not compatible with the Tor Browser. The technical reason is described at xpulse.one/tool/chat/security/.

en/content.md 2026-04-24