Chrome extension privacy

Ancient Summons Collector privacy policy

This policy applies to the Runekist Ancient Summons Collector Chrome extension. The collector keeps captures on your device first and sends Ancient data to Runekist only when you choose completed captures for upload.

Start monitoring

Capture locally

Choose what to upload

This extension policy supplements the general Runekist privacy policy .

Controller and contact

Runekist is operated by Devops Plaza SL, which is the controller for personal data sent to Runekist through the extension. For privacy questions, requests, or support, use the existing support form. Contact support

Purpose and user control

The extension monitors Ancient Summons health and clan-ranking progress in the Total Battle game tab you select. It stores captures locally, lets you download a local JSON export, and lets you upload selected completed captures to a Runekist clan after an authorized Leader or Superior links that destination.

Data handled from Total Battle

While monitoring, the extension handles Ancient and event identifiers; Ancient level, health values, health samples, summon state, map coordinates, and timestamps; kingdom and clan identifiers; player identifiers, display names, ranks, scores, score changes, and ranking changes; the supported Total Battle origin and the identifier of the bound browser tab; and operational state, coverage evidence, errors, gaps, and bounded diagnostics needed to run the collector.

To repeat the read-only clan-ranking request, the extension stores a validated request template containing the Total Battle request URL, POST body, permitted non-sensitive headers, fetch options, referrer information, kingdom evidence, and capture time. Authorization, Cookie, Proxy-Authorization, and Set-Cookie headers are removed before storage.

Runekist connection data

Linking and connection management handle the Runekist account email label, clan label and clan slug; a local profile identifier and installation identifier; connection, authorization, expiry and revocation status; a temporary linking code and polling secret; the clan-scoped collector credential; and extension name, version, build commit, and decoder version metadata. The Runekist API also processes the client IP address for security and rate limiting. Reverse proxies and operational or security logs may process the IP address and request metadata.

Local storage and when collection begins

The extension uses chrome.storage.local for installation and profile state, collector credentials, connection state, runtime state, and sanitized ranking request templates. It uses IndexedDB for sessions, Ancient lifecycles, health samples, ranking checkpoints and changes, aggregate samples, the player directory, upload state, and a diagnostic ring buffer limited to 200 events per session.

Installing or linking the extension can create installation, connection, and credential state, but monitoring and capture persistence begin only after you press “Start monitoring” in a supported Total Battle tab. Captures remain on the device unless you export them or explicitly select completed captures for upload.

Local deletion, reset, unlinking, and uninstall

You can delete an individual completed Ancient locally. This removes its lifecycle, health and ranking records, and upload state; session-level aggregate samples, player-directory entries, and diagnostics remain until the session is reset. “Reset session” stops monitoring and deletes the current session and its session-level records, but it cannot delete JSON files you already downloaded.

Unlinking revokes the selected Runekist installation and removes that local connection profile and credential; it does not delete local captures or data already uploaded. Chrome's ordinary “Clear browsing data” action does not clear extension storage. Removing the extension clears its chrome.storage.local data, and Chrome removes the extension's local storage, including IndexedDB.

Transmission to Runekist

Link creation and polling, authorization checks, credential renewal, revocation, connection-status checks, and uploads are sent to runekist.com over HTTPS. Ancient data is uploaded only after an authorized destination is linked and you explicitly select one or more completed captures. A local JSON export is a separate download to your device; exporting does not send the file to Runekist.

The current upload schema includes:

submission format and schema version, submission identifier and creation time; extension name and version, build commit and decoder version; and the local session identifier, start time, and stop time;
binding evidence: kingdom identifier, Ancient and request kingdom identifiers, clan and current-player identifiers where available, roster player identifiers, and a roster hash;
for each selected Ancient: its identifier and idempotency key; level, base and total health and Tome of Knowledge metadata where available; summon counts; first-observed, defeated, and scheduled-end times; kingdom and map coordinates; ranking-coverage summaries; timestamped health percentages; score intervals with timing, health bounds, coverage and threshold evidence, clan score changes and source sequence; per-player identifier, SUID where available, score change, cumulative score and resulting rank; and aggregate totals. Display names and the sanitized ranking request template are not included in this upload schema.

Data the extension does not collect

The extension does not collect general browsing history or information from unrelated websites; Total Battle login credentials, cookies, or authorization headers; keystrokes, private chats, or personal communications; health, financial, or payment information; or GPS or precise device location. Runekist does process the client IP address when the extension calls its API, so the service does not claim that no location-related network information is handled.

Use, sharing, and processors

Runekist uses this data only to provide, maintain, report on, and secure Ancient collection and associated Runekist clan features. It does not sell the data or use it for advertising, unrelated profiling, creditworthiness, or lending. Uploaded clan data is available only within the authorized Runekist clan and to people or systems that need it to operate and secure the service.

Devops Plaza SL operates the application and PostgreSQL data store and may use infrastructure, encrypted off-host backup, monitoring, and logging providers where needed to run and secure Runekist. Those providers process data under their service terms and access controls. Runekist may also disclose data where law requires it, to establish or defend legal claims, or to investigate and prevent abuse or security incidents, consistently with the general privacy policy.

Retention

Local captures have no extension-imposed expiry and remain until you delete an Ancient, reset its current session, remove the extension, or Chrome evicts storage under exceptional storage pressure. Temporary linking sessions expire after 10 minutes and can be exchanged only once. Collector credentials expire 90 days after issue or last eligible renewal; active authorized use can renew that expiry on a bounded 24-hour cadence, and revocation invalidates the credential immediately. Runekist stores only digests of linking secrets and collector credentials, but the expired or revoked database records are not automatically deleted by the current implementation.

The current implementation does not define an automatic deletion date for uploaded Ancient data, submission records, installation records, or link-session records. They remain until removed through a valid deletion request or an applicable operational or legal deletion process. The API uses IP-based fixed rate-limit buckets of up to 10 minutes. A bucket is no longer consulted after its window, remains only in server memory, and disappears when application memory is cleared or the application restarts. Reverse-proxy, application, security-log, and backup retention is controlled by deployment policy rather than by the extension code. Deleted server data may remain in protected backups until those backups expire.

Security, deletion requests, and rights

Runekist uses HTTPS for extension API traffic. The collector credential and temporary polling secret are stored in chrome.storage.local without additional extension-level encryption; protect access to your Chrome profile. Runekist stores SHA-256 digests rather than the collector credential, polling secret, or linking code themselves. Authorization is clan-scoped, rechecked for uploads, rate limited, and revocable.

You can revoke an installation from the extension or Runekist account settings. Use the support form to request deletion of uploaded or other server-side data. People in the EU and EEA may request access, correction, deletion, restriction, portability, or objection, and may withdraw consent where applicable. Requests may be limited by security, legal-claim, accounting, and other legal retention duties, and you may complain to your competent data-protection authority.

Chrome Web Store Limited Use

Runekist’s use and transfer of information received from Google Chrome APIs complies with the Chrome Web Store User Data Policy, including the Limited Use requirements.

Independent community tool

Runekist is an independent community tool and is not affiliated with, endorsed by, or officially supported by Total Battle or its publisher.