Privacy Policy: Reality Software Entertainment

Last updated: November 13, 2026

This Privacy Policy explains what personal information Reality Software Entertainment, LLC, an Ohio limited liability company (“Reality Software Entertainment”, “we”, “us”) collects, why we collect it, who we share it with, how long we keep it, and the choices you have. It covers realityse.com, your RealitySE account, Texas High School Football Dynasty, Snowball Dynasty, our mobile games and apps, and games we distribute through stores such as Steam and itch.io.

Ravensight, our analytics service for game studios, has its own Ravensight Privacy Policy (opens in new tab). It explains what Ravensight collects from the studios that use it and from players of the games those studios make.

The short version

Recipe Adapt, Dream Sift, Lunar Oracle and Uplift Echo

On Android, these apps can use Google sign-in to create an Android Google-linked app account for the selected app. When you sign in, we receive the Google account identifier, email address and display name Google provides. We keep purchase and subscription evidence supplied by Apple or Google to grant credits or access, prevent duplicate grants and address refunds or fraud.

Android Google-linked app account deletion. Each app provides a Delete Google app account control in Settings or Profile. You can also request deletion without the app by following the public account deletion instructions. Deletion applies to only the selected app and does not delete or change Apple-linked accounts, email accounts, or other RealitySE apps. We may retain limited purchase, security, fraud-prevention, tax, or legal records where required.

1. Information we collect

Your RealitySE account

Where a product offers RealitySE sign-in, one account can sign you in to those games and apps. Krikalia does not use this account system. For a RealitySE account we keep:

realityse.com

Texas High School Football Dynasty

Snowball Dynasty

Mobile games and apps

Krikalia

Krikalia does not require a RealitySE account. Your bookmarks, page information, tags, collections, notes, favorites, archive status, reminders, viewing times and link-health results are stored on your device. Plus can also save article text for offline reading. Krikalia has no advertising-network or analytics SDK and does not send your library to an AI service. It does show a Bjorlunda promotion. On Android, the promotion's wording and placement do not depend on the number or contents of saved bookmarks, including data synchronized from Google Drive. Tapping it opens that website with campaign parameters identifying Krikalia and the promotion you selected, not your library, bookmark count or account details. The website handles that visit under its own privacy practices.

Web requests. Previews, images, article downloads and Link Health contact the saved websites and image hosts, which receive the requested address and ordinary connection information such as your IP address. Opening a page uses your browser or a browser-provided tab and its cookies. Choosing an Internet Archive copy sends the selected page address to the Internet Archive.

Optional sync. iOS can sync through your private iCloud account. Android Google Drive sync is off until you connect it in Settings and authorize Google access. It reads and writes library records, including notes and synchronization history, in Krikalia's private Drive app-data storage. It requests no access to your other Drive files. Downloaded article bodies, cached page and image files, app preferences and Plus status are not uploaded by Drive sync. Image addresses stored in bookmarks are included. We operate no Krikalia sync server and do not receive your library on our servers. Android Drive and iOS iCloud are separate; JSON export/import can transfer a library between platforms. Local use and Plus do not require Drive sync.

Google account information. Sync records include your Drive account identifier, a random app-installation identifier, record identifiers, change versions and deletion records. The selected account identifier and, when available, email label are kept locally to identify the connection and prevent mixing accounts. Access tokens are held temporarily in app memory; Google manages the authorization. We use Google data only for the sync and recovery features you choose, in accordance with the Google API Services User Data Policy, including the applicable Limited Use requirements. We do not use that data for advertising or AI model training.

Android deletion and recovery. Disconnect stops sync on this device but keeps its library, account association, Drive data and Google's authorization. You can revoke authorization in your Google Account's connected-app settings. Deleting items or choosing Delete All Data propagates deletions when devices next sync, including after reconnecting. Previous content and deletion records can remain in local and Drive sync history; that history has no automatic expiry.

Delete Drive Sync History removes the current private Drive library data and history and disconnects this device. It keeps this device's library and account association, and leaves content-free reset markers in Drive so older devices cannot silently restore erased history. Other devices pause on detecting the reset; offline devices keep their local copies. This is not a remote wipe. Cleanup needs a successful connection; failures are reported and a request already in flight may need later cleanup. Rebuilding Drive from this device uploads its current library again. Replacing this device from Drive discards unsynced local edits. Export a backup before recovery. Removing hidden app data in Google Drive also causes connected devices to pause and require recovery.

Search, backups and caches. On supported Android devices, local device search is on by default. It indexes titles, summaries, site/host names, tags, creation times, bookmark identifiers and links back into Krikalia, but not notes or article bodies. Turning Device Search off in Settings clears that index. Android system backup or device transfer may separately copy the database and preferences, including downloaded articles, sync history, account information and cached Plus status, according to your device settings. HTTP/image caches are excluded from that backup. Restoring to a new installation requires reconnecting Drive. Delete All Data clears library items and downloaded articles, but not exported files, existing system backups, browser data or another device's offline copies. Temporary HTTP/image caches may remain until Android clears them or you clear the app's cache in Android Settings.

Plus purchases. Apple or Google handles this optional one-time purchase. Android verifies signed Play purchase information locally, acknowledges completed purchases to Google and saves an offline unlock status. It does not send receipts to a RealitySE purchase server or receive your card details. Store purchase records are separate from library data and are not erased by library deletion. Apple and Google purchases are separate.

For Krikalia, these controls supplement the general retention and account choices below. We cannot inspect or erase your private device or Drive library from a RealitySE server. Drive sync uses HTTPS; a website opened in your browser follows that website's security practices. Your Apple/Google cloud copies are stored under the provider's policies and account settings, rather than being limited to our United States server locations. For help, email support@realityse.com.

Just Lift: Be Fit

Your exercise library, training cycles, schedules, workout history, set weights and repetitions, durations and notes are stored on your device. Local workout tracking does not require a RealitySE account. A paired watch can receive workout information and send set changes and workout completion back to your phone. Exporting a JSON file creates a separate copy at the destination you choose.

Optional health permissions. With your permission, Just Lift can read your latest body weight from Apple Health or Android Health Connect and save workouts to that health store. Supported watch workouts can record heart rate and calories; Android requests separate permission to save those measurements to Health Connect. Health readings stay in this device, watch and health-store workflow. We do not automatically send them to our Smart service, include them in portable workout backups, or use them for advertising. Workout entries and set weights that you record in the library are included in library backups. You control health permissions and health-store records through Apple Health or Health Connect. Declining these permissions does not prevent local workout tracking.

Private platform backups. On iOS you can save a private iCloud backup. On Android you can separately authorize Google Drive to store a backup in Just Lift's private app-data folder, without granting access to your other Drive files. These copies contain your exercise library, workout history and notes, not your sign-in tokens or credit balance. Android replaces its previous snapshot and can back up once a day when you open the app if you enable that setting. This is a backup, not continuous synchronization between devices. Drive's account label and backup status are kept locally. These private copies go directly to Apple or Google, not our backup server. We use Google data only for the backup and restore features you choose, in accordance with the Google API Services User Data Policy, including applicable Limited Use requirements. Disconnecting stops future backup access but does not delete an existing cloud copy; manage that copy and authorization through your Apple or Google account controls.

Optional accounts and credits. RealitySE sign-in uses the provider identifier and the name and email supplied by Apple or Google to create or connect your shared RealitySE account. On Android, credits and paid operations can instead use a random guest identity without your name or email. We keep credit balances, operation records and store purchase identifiers to verify purchases, prevent duplicate grants and recover interrupted actions. Android has separate Backup Token and Smart Credit balances; its purchase and operation records identify which type of credit was used. Purchase verification sends the store's purchase information to RealitySE and the relevant store. Apple or Google handles payment; we do not receive your card details. Local workout tracking does not require buying credits.

Smart generation. When you choose to generate exercises, workouts or cycles, the preferences you submit, such as training goals, activity level, experience and injury or body-part selections, go to RealitySE and OpenAI to check and generate the result. Your health-store readings and full workout library are not automatically attached. Android shows a data-sharing notice and asks for agreement before your first generation. We retain operation records and generated results to recover interrupted requests. The current Smart service removes submitted input after a definitive result or failure; unresolved requests can retain it until recovery. OpenAI processes submitted information under its API service terms and retention settings. Do not include information you do not want processed.

Used Smart Credits. On Android, we do not offer discretionary change-of-mind refunds for Smart Credits already used for a successfully completed and delivered generation. This does not limit your statutory rights, Google Play's refund decisions, or remedies for services that are defective, unavailable or not as described. For help with a failed or interrupted generation, contact support@realityse.com.

Paid backup keys. Creating a paid backup sends your workout library, history and notes to RealitySE's cloud storage on Amazon Web Services. Anyone holding its recovery key can restore that copy, so keep the key private. This storage is separate from private iCloud and Google Drive backups. It is not end-to-end encrypted against RealitySE. Completed paid backups, generated results and active guest credit records have no automatic expiry in the current service.

Videos and service logs. Opening an exercise video loads its host or player, which receives ordinary connection information such as your IP address and the video requested. Android can display a YouTube player inside the app. That player may use cookies and show YouTube ads under Google's privacy policy. Opening a video in your browser also uses that browser's settings. RealitySE's services keep connection and security information such as IP address, user agent and request status, and generation usage and cost metrics. Local workout tracking itself does not send the full library to these services.

Just Lift account and data deletion

In Android Settings, choose Delete RealitySE Account to close the shared account. This affects other RealitySE products using that account, not just Just Lift. You can also request account or Just Lift data deletion by emailing support@realityse.com. Identify Just Lift and whether your request concerns an account, guest use or a backup. Use your account email where applicable; we may need to verify ownership. Do not send your password or sign-in token. Guest use has no account email, and older backup keys do not establish an account owner, so these requests need separate review.

Account closure and storage cleanup are separate steps. Cleanup for the current service removes associated Smart inputs and results, linked guest access and paid backup objects; it retains minimal purchase records that prevent a receipt being redeemed again. Cleanup is processed separately and can retry after failures, so closure does not mean every storage copy is immediately erased. Older backup-key copies are not automatically removed by account closure. Storage backups, previous versions and security records may remain under their separate retention controls. Contact us about those copies.

Reset Workout Data removes the local workout library. Signing out, disconnecting Drive or resetting the library does not delete server credit records, paid backups, exported files, private Apple/Google backups or health-store records. Manage those copies separately. Private Apple/Google storage follows the provider's policies and your account settings, rather than our server locations.

Saunavuoro

Saunavuoro records sauna, cold-plunge and meditation sessions. Your session types, dates, durations, temperatures, notes and saved mantras form your personal history. The iOS app uses Apple Health for workout history and keeps saved mantras and note edits on your device. The Android app keeps its history on your device; its timer and history do not require an account, purchase, location or cloud access. A paired Android watch sends completed sessions and recorded measurements to its companion phone. Apple Watch saves workouts through Apple Health.

Optional health data. With permission, supported watches record heart rate and calories. Apple Watch uses active calories; Wear OS reports total calories, including basal metabolism. Android can import and export Saunavuoro exercise records and their recorded heart-rate and total-calorie data through Health Connect. It filters imports to records originally written by Saunavuoro and does not import other apps' records. We use health data for your session history and the health-store, export and private-sync features you choose, not advertising or sale. Health measurements are not automatically sent to our mantra service. You can revoke permissions and manage health-store records in Apple Health or Health Connect.

Android export and private Drive sync. Exporting a portable file or choosing private Google Drive sync includes session history, recorded measurements, saved weather conditions, notes and saved mantras. It does not include sign-in credentials, purchase tokens or your server credit balance. Drive access is optional and limited to Saunavuoro's private app-data folder; it cannot read your other Drive files. Choosing Sync now merges snapshots from your Android installations, including deletion markers, and writes a snapshot for this installation. It does not transfer Apple Health or iCloud data. Your Drive account identifier and last-sync time are kept locally. These copies go directly to Google, not RealitySE's backup server. We use Google data only for these chosen features in accordance with the Google API Services User Data Policy, including applicable Limited Use requirements. Disconnecting stops future sync but does not delete existing cloud copies. Manage those copies and authorization through your Google account controls.

Accounts, credits and purchases. Optional Apple or Google sign-in connects your shared RealitySE account and its Saunavuoro credits. On Android, paid features can instead use a random guest identity without your name or email. Store purchase identifiers and tokens, credit balances and operation records go to RealitySE to verify purchases with the store, prevent duplicate grants, reconcile refunds and recover interrupted requests. Apple or Google processes payments; we do not receive your card details. Android guest credits may become inaccessible after uninstalling or resetting the app unless you first link them to a RealitySE account. Signing in does not upload your session history to RealitySE.

AI mantras. When you choose to generate a mantra, the feeling or text you submit goes to RealitySE and OpenAI for safety checks and generation. Your full history and health-store readings are not automatically attached. Android shows a data-sharing notice before generation. Its service removes submitted input after a definitive result or failure; unresolved operations can retain input while they recover. Generated results and operation records remain available for recovery. For iOS mantra requests, moderation logs can retain excerpts of flagged submissions. Do not submit information you do not want processed; OpenAI handles it under its API service terms and retention settings.

Reporting a mantra on Android. The in-app report action sends the selected mantra, your reason and any optional comment to RealitySE for safety review, associated with your account or guest identity. It does not automatically attach your original intention, session history or health readings, and uses no credits. Reports are available to our operators to investigate unsafe content and improve filtering. Report content is scheduled for deletion after 90 days; automatic cleanup and separate backup retention can delay removal of every copy. Account cleanup also removes reports associated with that account, including reports from linked guests.

Optional weather. With location permission, Saunavuoro uses your location to request outdoor conditions from Apple Weather. On Android, coordinates pass through RealitySE's weather service, which rounds them to two decimal places before requesting Apple's forecast. The weather service does not persist coordinates. Weather conditions can be saved with your session. Ordinary service connection and security logs, such as IP address, request status and user agent, are separate from your local history.

Saunavuoro retention and deletion

Android session history and saved mantras remain until you remove them or clear the app's storage. Removing a session in Saunavuoro leaves an existing Health Connect copy; separate per-session and all-Saunavuoro Health-copy deletion controls remove only this app's records and preserve local history. Exported files and private Drive snapshots are independent copies. Deletion markers are shared on a later successful sync and can remain in snapshots to prevent deleted items from reappearing. Disconnecting Drive, signing out or deleting local data does not erase server purchase records or those independent copies.

Android Settings offers Delete RealitySE account. This closes the shared account across connected RealitySE products, not just Saunavuoro, and clears local Saunavuoro history and saved mantras after successful closure. Existing Health Connect and Drive copies still require separate removal. Server cleanup removes associated Android generation inputs and results and linked guest access, while retaining minimal purchase-token hashes to prevent receipt replay. Cleanup can retry after a failure; account closure does not mean every copy is erased immediately. Active guest credit records and completed Android generation records have no automatic expiry in the current service. Security records and backups follow their separate retention controls.

You can also request Saunavuoro account or data deletion at support@realityse.com. Identify Saunavuoro and whether the request concerns an account, guest credits or another copy. We may need to verify ownership; never send your password, sign-in token or purchase token by email. Guest use has no account email and requires separate review. Private Apple and Google copies follow those providers' policies and your account controls, rather than our server storage locations.

Games on Steam, itch.io and other stores

When you buy or download one of our games from a store, the store handles your store account, payment and download under its own privacy policy. We receive only the sales and purchase information the store provides to game publishers.

When you contact us

If you email us, we keep your email address and our conversation so we can help you.

2. How we use your information

We do not use your personal information to show you targeted ads on our websites.

3. Who we share it with

We share personal information with companies that help us run our products, for that purpose:

Analytics and feedback from our own games also go to Ravensight, which is our own service.

We may also disclose information when the law requires it, to protect the rights, property or safety of our users, the public or us, or as part of a merger, acquisition or sale of all or part of our business, in which case your information would move to the new owner.

4. Cookies, browser storage and Do Not Track

We use these cookies:

We also keep a few small items in your browser's local storage: your answer to our cookie notice, your shopping cart, your Play page visitor ID, whether you closed a notice, game settings, and the random device ID our games use for Ravensight analytics.

We do not use advertising cookies on our websites.

The cookie notice on realityse.com. The notice records your choice in your browser. Analytics on realityse.com currently runs whether you choose Accept or Decline. To stop it, block cookies and site data for realityse.com in your browser settings, or use a content blocker.

Do Not Track. If your browser sends a Do Not Track signal, Texas High School Football Dynasty and Snowball Dynasty do not load their analytics in your browser. Some events are recorded by our servers when they happen, such as sign-ins, subscription changes and game milestones, and Do Not Track does not stop those. realityse.com does not currently respond to Do Not Track or Global Privacy Control signals.

5. How long we keep it

6. Your choices and rights

You can ask us to show you the personal information we have about you, correct it, give you a copy, or delete it. Email support@realityse.com from the address on your account or the address you used to contact us. We may ask you to confirm your identity before we act on a request, and we will not treat you differently for making one.

Depending on where you live, including California and other US states, the European Union and the United Kingdom, the law may give you these rights and others, such as the right to object to or limit how we use your information. You can exercise any of them by emailing us.

7. Children

Our games and websites are not directed at children under 13, and we do not knowingly collect personal information from them. You must be at least 13 to create a RealitySE account. If you believe a child under 13 has given us personal information, email support@realityse.com and we will delete it.

8. Security

Our own services use encrypted connections (HTTPS), store passwords only as one-way hashes, and keep sign-in cookies out of reach of page scripts. No method of storing or sending data is completely secure, so we cannot guarantee absolute security. Please use a password you do not use anywhere else.

9. Where your information is stored

We are based in the United States, and information on our servers is stored and processed in the United States. Information you send to those services from another country is transferred to the United States. Krikalia's private Apple and Google cloud copies, device backups and visits to external websites follow those providers' storage policies and your account settings; they are not limited to our server locations.

10. Changes to this policy

We will update this policy when our products or practices change, and change the date at the top. If we make a material change, we will notify you by posting the change on our websites or in this Privacy Policy.

11. Contact us

Questions, requests or complaints about privacy: email support@realityse.com. If a disability makes it hard to read this policy or to exercise your rights, email us and we will help you another way.