tendie.space

tendie.space LLC

Privacy Policy

This policy describes how tendie.space LLC (“we”, “us”) collects and uses information for this website and for Clover Kart.

Who we are

tendie.space LLC is an independent game studio. This website (tendie.space) is our company site. Clover Kart is our game, operated at cloverkart.io and related domains (including cloverk.art and kart.tendie.space).

Privacy questions: [email protected].

This company website

tendie.space is a static informational site. It does not require an account, does not set advertising cookies, and does not load third-party analytics or advertising scripts. The hosting provider and our CDN or DNS provider may process standard request logs (such as IP address, user agent, and the page requested) to serve the site, keep it secure, and diagnose faults.

Clover Kart

When you play Clover Kart we process information needed to run the game. There is no password login. We do not run a mailing list, and we do not keep the text of in-game chat.

How we identify you

Progress is tied to a player key, not a password. If the browser can store data, we mint a guest token there and use it on later visits. If it cannot (private mode, some embedded game frames), we fall back to a short hash of the connecting IP address. The raw IP is not the stored key, is not sent to your browser as a player identifier, and is not sent to analytics as an event parameter.

Under that IP-hash fallback, people sharing the same public address — a household, school, or café — share one profile. If a durable account is later linked, progress follows that account instead.

What we store about play

On the server we keep a play profile. It may include:

Display names are chosen per session. The profile does not keep a current name, but each entry in the recent-session history records the name that visit used, so we can match a name seen in the arena or on Discord to the visit it belongs to.

Connection data

We use the connecting IP address at the edge for rate limiting, abuse prevention, and the hash described above. Our CDN provides a coarse country for the connection, which we may show on the kart unless you equip a flag cosmetic. Hosting, CDN, and DNS logs may include IP address, user agent, and the URL requested. Our game server's log records each connection's display name next to its connection details, for moderation and support.

Analytics

On first-party builds, Clover Kart uses Google Analytics (property G-E0QRCBBS08) to understand aggregate traffic and feature use. Analytics is keyed with the same pseudonymous player key. Events may describe which level is loaded and whether you are on a keyboard, a controller, or a touch device. We do not send a separate page-view hit, and we do not send raw IP addresses to Google as event parameters. Google may set its own cookies. Some storefront builds omit analytics.

Google’s processing is described in Google’s privacy policy.

Separately from Google Analytics, the game sends our own server a short report about once a minute over its existing connection. It carries counts of the same feature events (for example, how many times the Guide was opened) and performance figures such as frame rate and connection quality. Event counts are added into totals across all players and are not stored with your profile. Performance figures are visible to us next to your live connection so we can troubleshoot, go into the same kind of totals, and are not stored with your profile. The report also describes your device as your browser reports it: browser and operating system family, number of processor cores, approximate memory, graphics chip name, screen resolution, how long the game took to load, and the game’s quality settings. It also says how many seconds the screen spent upright and sideways, how often it was turned, and which kind of controls were in use; those figures go into totals across all players and into your recent-session history described above. Your recent-session history also records the browser and operating system family (for example “Safari” and “iOS”), so we can tell whether players on one kind of device leave early; nothing else from the device description is kept there. When you leave, we keep one record of the device description with the frame rate and screen figures your visit achieved, so we can choose sensible default quality settings. That record contains no player key, name, IP address, or country, is timestamped only to the hour, and is deleted after 90 days (routine backups may hold a copy for up to 14 days more). This report goes only to our servers, never to Google or any other third party. It is sent on every build, including storefront builds that omit Google Analytics.

Chat and Discord

In-game chat is shown to other players in the arena. On our own site, chat, the YouTube jukebox, and unfiltered display names are off until you tick “I’m 18+” on the start screen; without it, other players’ names reach you with flagged words masked. The tick is your own statement, not an age check: we do not ask for a date of birth or verify it. It is saved on your play profile so it carries over to your next visit, and unticking it turns those features off again. We do not retain message bodies. Server logs may record that a message was sent, its length, and the connection country.

On first-party and Steam, a Discord bridge may copy display names, chat, and some game events (joins, leaves, wrecks, jukebox changes) to our Discord, and Discord messages may appear in the game. Discord’s own terms and privacy policy apply to information that reaches Discord. Some storefronts disable the bridge. If you join a community channel we link to, that service’s policy applies to what you provide there.

If you email us, we keep the correspondence long enough to respond and to handle the request.

YouTube jukebox

Players may queue YouTube links. We store the video identifier and fetch the public title from YouTube. Playback uses YouTube’s own player, which is subject to YouTube’s and Google’s policies. Video identifiers may also appear in Discord event lines when the bridge is on. Some storefronts disable the jukebox.

Match replays

To reconstruct a match we keep a command journal: the hashed player key, country, display name, inputs, and the garage or cosmetic choices that affect the simulation. Raw IP addresses, login tokens, analytics identifiers, and chat text are not written into that journal. Exported replays may include a player id, name, country, and simulation state. This is match reconstruction, not a chat log.

Shared clips

On first-party builds, the replay viewer can make a link to a short clip of your play, or post it to the #clips channel of our Discord. To do this the game uploads that replay’s data (the same simulation record described above, never a recording of your screen) and our server renders the video from it. A shared clip shows the display name you played under, its caption, and the game as recorded. Anyone with the link can watch it, and link previews on sites such as Discord, X, or Reddit may show it. The uploaded replay data is deleted once the video is made (or within a day if it cannot be). The video, its still image, and its page are deleted 90 days after they are made, or sooner if you ask us or the clip is reported and removed. Clips posted to Discord stay in that channel until removed there. Clip pages have a report link; reports keep the text you write and the reporting connection’s IP address until we review them.

Problem reports

The “Report a problem” button sends us what you type and, if you give one, where we can reply (an email address or Discord name, which the game remembers on your device for next time). With it goes what we need to find the problem: the last stretch of play from the game’s replay buffer (the simulation record described above, never a recording of your screen; it includes other players’ names and karts as your game saw them), a description of your device and browser (browser, operating system, graphics card, screen size, language, and time zone), your game settings, frame rate and connection figures, what the game was showing, and its recent error and console messages. Our server adds your connection’s IP address, country, and user agent, your display name and player id, and the state of the round. Nothing is sent until you press Send. We store the report on our server and post a summary (display name, country, reply address, the start of your message, and the technical figures) to a private staff channel on our Discord. We keep reports until we have looked into the problem they describe.

On your device

The game stores the guest token, settings, local scores, and tutorial flags in the browser. We do not set first-party advertising cookies. Google Analytics may set cookies when analytics is on.

High scores

Public boards show display name, score, and country.

How we use information

We do not sell personal information.

Sharing

We share information with the providers that host and deliver the services: hosting; Cloudflare for DNS, CDN, the country header described above, and storing and serving shared clips; Google Analytics when analytics is enabled; YouTube when the jukebox is on; and Discord when the Discord bridge is on, you post a clip there, or you send a problem report. We also share information when required by law. Hosting and Cloudflare process this information to perform their function for us. Google, YouTube, and Discord process information as described in their own policies when those features are enabled.

Retention

We keep play and account data for as long as needed to operate the game and our anti-abuse systems, then delete or de-identify it when it is no longer required, unless a longer period is required by law. Shared clips follow the 90-day rule above.

Children

Clover Kart is a general-audience online game and is not directed at children under 13. We do not knowingly collect personal information from children under 13. If you believe we have, contact [email protected] and we will delete it.

Your choices

You can play as a guest. You can control cookies and analytics through your browser settings: if your browser sends Do Not Track or Global Privacy Control, we do not load Google Analytics. The first-party usage and performance report described above is part of running the game and is sent regardless, since it never leaves our servers and is not kept with your profile. To request access, correction, or deletion of personal information we hold, email [email protected]. An IP-hash guest profile may be shared with others on the same public address, which limits what we can uniquely identify. We may need to verify the request and may retain information when we are required to (for example to combat abuse).

Changes

We may update this policy. The “Last updated” date at the bottom will change when we do. Continued use of the site or game after an update means you accept the revised policy.

Contact

tendie.space LLC
[email protected]
[email protected]
Contact page

Last updated: October 22, 2026