Effective date: 6 September 2026
Developer / publisher: Ja
Support/privacy email: dirja.project@gmail.com
Straight² is a sprint-racing game. Before the first race, an installation must connect once to claim a unique public Runner name. After that successful claim, Solo/local racing can work offline. Best-Time Challenges, private Live Multiplayer rooms and the Community Skin Store are optional online features. Straight² also includes banner advertising and optional rewarded advertising. It has no chat, direct messaging, social login or password-based user accounts.
App-private storage can contain settings, player/leaderboard name, selected country, local records/progression, replay/ghost data, runner skins, a random service identifier, whether the unique Runner name has been confirmed, accepted-terms version, blocks, cached/staged online data, Store metadata, pending progression claims, advertising/consent state supplied by the advertising SDK where applicable, and pending rewarded-ad verification state. Live-room codes are transient session data rather than a durable preference.
Accelerometer, gravity and gyroscope readings are used live for tilt steering. Raw sensor readings are not intentionally uploaded. Live Multiplayer sends compact derived race state such as distance, speed and lane offset.
No email, phone number, social account or password is required. Straight² creates a random installation/player identifier. Before the first race, that identifier is sent to the Straight² server with the Runner name requested by the player so the server can enforce first-come, first-served name uniqueness. Name matching is case-insensitive. The public Runner name may be shown with country, race results, ghosts, Store listings or live-room presence. Persistent ownership uses a keyed one-way hash of the installation/player identifier. If uploaded Straight² data is deleted through the in-game deletion flow, the associated server-side name reservation is also removed.
Creating/joining a room may process the random installation/player identifier, public Runner name, selected country, runner colour/appearance data (including the selected painted/custom skin payload when used), finish style, room code, host/participant role, lane, ready/loading/connection state, synchronized start timing, compact live race state and finish/DQ result.
Live-room state is held in server memory for the active session, is not intentionally written to the challenge SQLite history, and is removed when rooms expire or the live-room service restarts. A short reconnect grace period may temporarily retain a disconnected slot. “Private” means unlisted/code-based, not end-to-end encrypted from the Straight² relay; production traffic uses HTTPS/WSS encryption in transit and the relay processes messages to synchronize players.
The service may receive distance, valid PB finish/reaction time, country, app/protocol/ruleset information, a compact gameplay ghost and runner appearance. Other players can download visible challenge ghosts/appearances. Reports send the relevant entry identifier/reason.
Eligible races may send distance, difficulty, rank, reaction/finish time, DQ/validity state and a compact validation ghost. The server stores online progression wallet values and performs XP-to-coin exchange/purchase debit server-side; the client does not provide a trusted coin balance during purchase. The optional daily check-in stores a server UTC day key and claim timestamp for the installation and can add 100 XP once per server UTC day. Using the server day rather than the device clock prevents repeated rewards by changing the phone date/time.
The Store may process anonymous ownership identity, public Runner name, skin title, 1–8 coin price, painted-skin payload, preview, timestamps, purchase receipts, creator earnings, sales count and moderation reports. Visible listings expose listing metadata; the full skin is delivered to an owner/downloader. Coins/XP are virtual in-game values and are not redeemable for money.
Straight² uses Google AdMob / the Google Mobile Ads SDK to provide a banner ad in limited parts of the interface and optional rewarded ads that a player may choose to watch in exchange for an in-game coin. Straight² does not require a rewarded ad to play a race.
Google and its advertising partners may process information such as IP address, device and app information, advertising identifiers or similar device identifiers where available and permitted, ad interactions, diagnostics, approximate location inferred from network information, and consent/privacy choices. The exact data used can depend on device settings, region, consent status and the type of ad served.
Where required by applicable law, Straight² may present Google's consent/privacy messaging before requesting ads and may request non-personalized or otherwise restricted ads depending on the user's choices and applicable settings. Users may also be given a way in the app to revisit privacy choices when Google's SDK indicates that such an option is required.
More information about how Google uses data from apps that use its services is available at How Google uses information from sites or apps that use our services, and Google's privacy policy is available at Google Privacy Policy.
Rewarded-ad coins use server-side verification to reduce fraud. Before a rewarded ad is loaded, the Straight² server may create a short-lived random reward-session token. That token can be supplied to Google as rewarded-ad custom data. After a completed eligible ad, Google's server may send a signed verification callback to the Straight² server containing information such as the ad unit, reward amount/item, timestamp, transaction identifier, signature/key information and the short-lived custom session token. The Straight² server verifies the callback and credits the coin only when the reward session is valid. Duplicate transaction identifiers do not mint additional coins.
Straight² currently does not use Firebase Analytics, social-login SDKs or a separate third-party analytics SDK. Google AdMob is an advertising SDK and may perform measurement, fraud prevention, delivery and diagnostics related to advertising. The hosting provider also necessarily processes ordinary network information such as IP addresses and security logs for service delivery, reliability and abuse protection.
After a Runner name has been successfully claimed, Solo/local features can work offline. Pending PB/progression claims may retry later. Persistent name reservations, PB ghosts, Store records, progression wallet records, daily check-in records, rewarded-ad transaction records and moderation data are retained as needed for their features, fraud prevention and accounting consistency; backups may temporarily retain deleted persistent records until rotation. Live rooms use the shorter ephemeral retention described above. Short-lived rewarded-ad session tokens expire automatically.
Players can block locally and report leaderboard results/Store skins. In-game controls can disable syncing and request deletion of uploaded Straight² challenge/Store data. The deletion flow also removes the server-side unique-name reservation associated with that installation, allowing the name to be claimed again later. Active live-room state normally disappears when the room empties and is not part of the persistent account-deletion database. Advertising data controlled directly by Google is subject to Google's own retention, controls and privacy policy. Contact dirja.project@gmail.com for help.
Production traffic uses HTTPS/WSS with input validation, message/rate controls, host authorization and bounded room/message sizes. Unique-name claims and daily XP are enforced server-side. Rewarded-ad callbacks are cryptographically verified before server-authoritative coins are granted. No client game or internet service can guarantee absolute protection against every cheat or compromise. Online competition is casual rather than prize-bearing verified esports.
The publisher must select Google Play target age groups accurately and configure advertising and consent behavior to comply with the policies and laws that apply to the selected audience. Straight² has no chat/direct messaging but includes public Runner names, ghost sharing, private code-based multiplayer, advertising and moderated community skin listings.
This policy may change if the game, advertising setup or backend changes. For privacy, moderation or deletion questions contact dirja.project@gmail.com.