Data & privacy

Cliffline stores your driver name, account identifier, map drafts and published map snapshots. Your public driver name appears beside maps you publish. Your login email is not displayed in the community map list.

Driver profiles and challenges

Your display name, permanent handle, bio, avatar and published map list are visible to signed-in drivers. Do not put private information in your bio. Shared challenges preserve a separate map and vehicle snapshot. Editing or unpublishing the original does not remove this copy: revoke its challenge link from your profile. Accepted challenges and self-reported completion records are stored against your account; other players cannot browse your personal completion history.

Who can see your maps?

Drafts are available only to their author. Signed-in players with driver profiles can see and play published maps. Editing a published map does not update its playable version until you publish again. Unpublish removes the playable version while keeping your draft.

Community activity and feedback

For signed-in community play, we store per-map play counts, self-reported wins/losses and the latest run state/time against your account. Aggregate counts and recent active-player estimates are shown on map pages; individual play histories and account identifiers are not shown there. Ratings, difficulty votes and comments are linked to your public driver name. Ratings and discussion are separate. You can change your rating and edit or delete your own comments; replies keep their authorship. Map creators can hide comments without removing their ratings; abuse reports are stored for operator review.

Creators choose whether sharing tools allow JSON downloads and editable copies. Downloaded files and previously permitted copies cannot be recalled. Editable copies created through the game preserve source-map attribution. Imported maps saved to your account are private and can be removed from your account library. Unsaved imports and older device-only copies may remain in browser storage. Download restrictions are not encryption: playable map data is sent to your browser.

Sign-in and passwords

This hosted edition uses ChatGPT sign-in. The independent hosting edition uses Supabase for email/password accounts. The game does not store passwords in its map database. In the independent edition, session tokens use secure, HttpOnly cookies. Your sign-in provider handles account credentials and email verification.

Driving records and offline practice

Online driving sessions record reported distance, duration, vehicle and results. Aggregate driver levels and XP are visible to signed-in players. These are personal, client-reported records, not verified competitive scores. Offline practice does not upload distance or achievements, including after reconnection. Official completion markers remain local. The offline download stores public game assets and official maps, never account API responses.

On this device

Camera, sound, controls and graphics preferences stay in your browser. The editor keeps an unsaved draft buffer in the current tab. These do not replace the online Save draft action. Clearing browser storage removes local preferences and temporary buffers.

Service operation

The server limits repeated edits and sign-in attempts to reduce abuse. Temporary counters use hashed identifiers. Expired counters are cleaned as new requests arrive. Hosting and sign-in providers may retain their own operational logs under their policies.

Managing your data

Your public driver name is permanent once claimed. You can manage your account in Driver account and unpublish your maps in the editor. Signing out does not delete your saved maps. Deleting an identity-provider account and removing its saved game data are separate operations.