CRASQ One 1.0 Stable 19102026 — PRIVACY POLICY
Document version: 1.0-web-20102026 • 20 October 2026
1. Controller and contact The controller is Szymon Szulik, operating under WAROS Team / SZYSZU. Website: https://crasq.com. Controller and support contact: support@crasq.com.
2. Local data The app stores settings, sessions, diagnostic evidence, the telemetry queue and repair backups on your computer. Full logs, saves and screenshots are not automatically uploaded. Local files are not covered by the private-message encryption below. Uninstallation preserves LocalAppData/CRASQ; you may remove it yourself after making any necessary backup.
3. Account and social features Accounts are optional; core local diagnostics work without them. We process email, unique nick, random ID, avatar, badges, roles, salted password hashes, hashed session tokens and device information. Published content can show your nick, avatar, role and up to three selected owned badges. Registration badges use Polish time; the PRO badge requires an active entitlement. Public chat, NEWS, comments and reactions are visible to their respective audiences. Do not publish confidential data there.
4. Private messages and groups The API supplies private messages to authorized active conversation members. An admin role alone does not grant access to another person's conversation. Metadata includes participant/conversation identifiers, group titles, dates, membership and read state. Since API 2.12.6, the server encrypts new message bodies with AES-256-GCM before storing them in D1. Keys are kept separately as server secrets. Missing or invalid keys block content handling; they do not enable plaintext writes. Old messages require migration. Complete history encryption can only be confirmed after migration; older backups may still contain plaintext. This is server-side encryption, not end-to-end encryption. The server decrypts messages for authorized recipients; an operator with the database and key can technically decrypt them. The admin panel and SZYSZOK integration expose counts and security status, not conversation bodies. Your data export contains your own decrypted sent messages and must be stored safely.
5. Optional telemetry and diagnosis Telemetry is disabled by default; accepting the EULA does not enable it. Separate consent in Settings enables pseudonymous data: random installation/session IDs, app version, game, session duration/outcome, issue fingerprint, mod configuration, hardware classes and aggregated performance readings. The diagnostic schema does not request serial numbers, MAC addresses or Windows user names. Text filters aim to remove private paths and identifiers; they do not replace reviewing manually submitted text or images. Withdrawing consent in Settings stops telemetry transmission without disabling local diagnostics. Smart may record an apparently clean exit without prompting. This is not a verified repair or Trusted Good. Short or conflicting endings need a player response. Reading API rules does not mean AI model training. Private messages and support submissions are not automatically used for model training.
6. Support and cooperation Forms send your name/nick, reply email, product, category, subject, description and optional version or link. A report may include one JPG/PNG/WebP screenshot up to 512 KiB. Cloudflare and Resend deliver submissions to support@crasq.com. Reply-To is the submitter's address. Full logs are not automatically attached. Correspondence is kept for case handling; the retention target is up to 24 months after closure, with manual deletion.
7. Purposes and legal bases Account, messaging and requested support data are used to provide your selected service (GDPR Article 6(1)(b)). Diagnostic telemetry relies on consent (a). Account protection, abuse prevention and legal claims rely on the controller's legitimate interests (f). Legal obligations may require processing under (c). Data are not sold or used for behavioural advertising. Required data are necessary for the relevant feature; local use remains available.
8. Providers and transfers Cloudflare provides website/API/database infrastructure. Resend sends automatic emails; the configured mailbox provider handles correspondence. Providers may process request data and keep separate logs. Processing may involve countries outside the EEA. Actual contracts, locations and transfer safeguards must be confirmed against the operator's configuration before public launch; contact support@crasq.com for information. External installer hosting receives download request data.
9. Retention and deletion Public chat messages older than 24 hours are removed on the next chat request. Private messages older than 180 days are excluded from API reads; physical cleanup requires a configured Worker schedule. That schedule also removes selected diagnostic data older than 12 months. Cleanup code exists, but production scheduling and backups require separate verification. Accounts remain until deletion or action under security rules. Account deletion removes related content and relationships according to the API; limited operation and security logs may remain for the periods described below. Email codes last 10 minutes; sessions last up to 30 days or until revoked. The new scheduled cleanup removes expired or consumed codes and expired or revoked sessions after one additional day, rate-limit records two days after their last update, account activity and specified administrative/security logs after 12 months, and daily aggregate statistics after 25 months. Access expires independently of physical record deletion. Cleanup requires deployment and an active Cron trigger; this source package does not confirm the live server configuration. The local queue and verdict files are retained for up to 30 days. Database and mailbox backups have separate retention depending on operator configuration.
10. Statistics and SZYSZOK Aggregated page-view and download-redirect counts contain no account ID, email or persistent visitor identifier. Page-view reporting respects DNT/GPC. Redirects do not prove completed downloads; views are not unique visitors. Security may use pseudonymous IP-based rate limits; providers keep separate logs. SZYSZOK is the operator's private tool and receives authorized metadata, not private conversation bodies.
11. Rights and security You may request access, correction, deletion, restriction and portability where applicable, withdraw consent or object to legitimate-interest processing. Withdrawal does not affect prior lawful processing. Contact support@crasq.com. You may complain to Poland's data protection authority (President of UODO). The account panel supports export and deletion. We do not make decisions with legal effects based solely on automated profiling. Passwords and tokens are hashed, network communication uses HTTPS and access requires authentication and authorization. No mechanism eliminates every risk. Do not include passwords or keys in support reports.
12. PRO and updates PRO sales are disabled. Keys and access are for testing; the provisional 30 November 2026 launch depends on readiness and is not a commitment to sell. Sales terms and payment-provider information will be published before sales begin. The installer can be downloaded from the website or through the configured signed-update feature, with separate installation confirmation. The signed updater needs separate deployment/testing; a download SHA-256 checksum is not a publisher signature.
13. Browser storage and form protection The website stores language preference in localStorage (crasq-language). Account device management also stores a random browser ID in localStorage (crasq-web-device); it is not used in page-view counters. Clearing browser storage may create a new device ID on the next login. Login uses the necessary crasq_session cookie (HttpOnly, Secure, SameSite=Lax); logout revokes the session. Aggregate counters do not require advertising cookies. Forms use a spam trap, rate limits and input validation. If Turnstile is enabled for registration, Cloudflare processes technical browser/request data for verification; confirmed production settings may require additional information.
14. Update checks With Cloud enabled, the app checks the public Stable channel after startup and at most once every six hours after a successful check; failures are retried no earlier than after 30 minutes. Automatic checks are deferred during an active game session. Manual checks run on request in Updates. Requests expose necessary connection information, including the IP visible to infrastructure, and, when signed in, the session token used to verify access. Checking does not download or run the installer.