Privacy and measurement
Telemetry and website metrics
Sideverse records limited website usage on the server. These records are separate from the telemetry a compatible native client may send.
Website entry metrics
We count invitation opens, registrations, email verifications, member confirmations, Side setup and first actions. The aggregate table stores the date, event name and count, without account IDs, Side IDs, invitation tokens, IP addresses or precise location. A Side also records its first-action date so that action is counted once.
Public page views
Published pages have view counts. A page-view record contains the page ID, time, country code when available and referring host when available. It does not contain a visitor identifier, full referrer URL or IP address. These records support aggregate statistics for the page owner.
These measurement records are different from account and security records. Signed-in sessions can store an IP address, browser information and last activity. See the privacy policy for account data, map-provider requests and storage.
Native-client telemetry
Desktop and mobile downloads are not available yet. The current protocol implementation sends usage events by default in release builds; debug builds do not send them. It is not an opt-in setting in the current client.
The native event body contains event, version and channel. This registry stores accepted events with a country code when available and receipt dates. It does not store an IP address or a client identifier in the telemetry event record. This is not a claim that network infrastructure keeps no logs.
People running a compatible client should review that client’s telemetry settings and release documentation. In the current protocol implementation, setting TPSOCIAL_STATS_ENDPOINT to an empty value before starting the client disables its telemetry sender.