Privacy Policy

Effective date: October 22, 2026

IROIRO LLC ("us", "we", or "our") operates the https://iroi.ro website and related mobile applications (hereinafter referred to as the "Service").

This policy applies to all websites, applications, and services provided by IROIRO LLC.

This page informs you of our policies regarding the collection, use, and disclosure of personal data when you use our Service and the choices you have associated with that data. Our Privacy Policy for IROIRO LLC is managed with the help of Privacy Policies.

We use your data to provide and improve the Service. By using the Service, you agree to the collection and use of information in accordance with this policy. Unless otherwise defined in this Privacy Policy, the terms used in this Privacy Policy have the same meanings as in our Terms and Conditions.

Information Collection and Use

We collect several different types of information for various purposes to provide and improve our Service to you.

Types of Data Collected

Personal Data

While using our Service, we may ask you to provide us with certain personally identifiable information that can be used to contact or identify you ("Personal Data"). Depending on the specific Service used, personally identifiable information may include, but is not limited to:

Email address
First name and last name
Phone number
Address, State, Province, ZIP/Postal code, City
User-generated content (such as text, images, or other content you create within our applications)
Cookies and Usage Data

Not all Services collect all data types listed above. The specific data collected depends on the Service you use and the features you interact with.

Usage Data

We may also collect information on how the Service is accessed and used ("Usage Data"). This Usage Data may include information such as your computer's Internet Protocol address (e.g. IP address), browser type, browser version, the pages of our Service that you visit, the time and date of your visit, the time spent on those pages, unique device identifiers, and other diagnostic data.

Tracking & Cookies Data

We use cookies and similar tracking technologies to track the activity on our Service and hold certain information.

Cookies are files with small amounts of data which may include an anonymous unique identifier. Cookies are sent to your browser from a website and stored on your device. Tracking technologies also used are beacons, tags, and scripts to collect and track information and to improve and analyze our Service.

You can instruct your browser to refuse all cookies or to indicate when a cookie is being sent. However, if you do not accept cookies, you may not be able to use some portions of our Service. You can learn more about how to manage cookies in the Browser Cookies Guide.

Examples of Cookies we use:

Session Cookies: We use Session Cookies to operate our Service.
Preference Cookies: We use Preference Cookies to remember your preferences and various settings.
Security Cookies: We use Security Cookies for security purposes.
Advertising Cookies: On our ad-supported websites, Google AdSense and its partners set cookies (and read similar identifiers) to serve ads, to limit how often you see the same ad, and — unless you have opted out — to personalize the ads you are shown. See Google AdSense below, including how to turn personalization off.

Identifiers

Some of our applications may collect the following identifiers for advertising purposes:

User ID — A randomly generated identifier stored on your device, used by third-party advertising partners for ad delivery.
Device ID (IDFA) — Apple's Identifier for Advertisers, used by third-party advertising partners for personalized ad delivery.
Advertising ID (AAID) — Google's Advertising ID on Android devices, used by third-party advertising partners for personalized ad delivery. You can reset it, or opt out of personalized ads entirely, in your Android system settings.

On Apple devices, these identifiers are only shared with third-party advertising partners when you have authorized tracking via Apple's App Tracking Transparency (ATT) prompt. If you deny tracking, these identifiers are not shared. On Android, we honour the opt-out you set in your device's advertising settings.

Where required by law, we ask for your consent before any advertising identifier is used for personalized advertising. You can always withdraw it through your device's advertising settings, and applications that present a consent form also offer a way to reopen it.

Search Data

When you use search features within our applications, your search queries may be sent to third-party content and advertising providers to deliver results and relevant ads.

In-App Purchase and Subscription Data

We may log in-app purchase events (such as product identifier, plan type, and success or failure status) to our analytics services to understand conversion and improve the purchase experience. We do not collect or store your payment method or financial information — Apple handles all transactions via StoreKit, and Google handles them via Google Play Billing.

Some of our applications offer auto-renewing subscriptions. To know what you are entitled to, an application stores the product you purchased and when the current period runs out. That record is kept on your own device; your subscription is managed by, and can be cancelled through, the store you bought it from.

Advertising Data

Some of our applications display ads served by Google AdMob and its advertising partners. Google's use of the data it receives is described at policies.google.com/technologies/partner-sites. When ads are served, the following data may be shared with these providers:

Device information (hardware model, OS version, screen dimensions, language)
Network connection type
App version
User-Agent string

Ad creatives may contain tracking pixels from third-party advertisers.

Some of our websites are also ad-supported, and are served by Google AdSense. Web advertising does not use the mobile advertising identifiers described above — it uses cookies and your IP address instead. When an ad is served on one of our websites, the following may be shared with Google and its advertising partners: your IP address, your User-Agent string, the page you are viewing, general location derived from your IP address, and advertising cookies previously set in your browser. See Google AdSense below.

Diagnostic Data

Device model, OS version, and app version may be collected as part of customer support submissions and ad delivery operations.

Applications that include crash reporting also collect, when the application stops unexpectedly, the point in our code where it failed, the state of the device at that moment (model, OS version, app version, available memory and storage, whether the device was jailbroken), and a record of the screens visited beforehand. This is used to find and fix the fault. It is never used for advertising and it never contains the content you create in the application, but it does carry a per-installation identifier, so we report it as linked to you. See Crash Reporting below.

Use of Data

IROIRO LLC uses the collected data for various purposes:

To provide and maintain the Service
To notify you about changes to our Service
To allow you to participate in interactive features of our Service when you choose to do so
To provide customer care and support
To provide analysis or valuable information so that we can improve the Service
To monitor the usage of the Service
To detect, prevent, and address technical issues

Third-Party Advertising

Some of our applications are ad-supported. For ad-supported applications, data may be shared with third-party advertising partners for the purpose of delivering and personalizing ads. This includes search queries, device information, and (when tracking is authorized) your User ID and Device ID. See the "Identifiers" section above for details on how tracking authorization works.

On-Device Processing

Some of our applications perform on-device machine learning analysis (such as image recognition and text detection) to provide features like automatic tagging and content organization. All on-device analysis results are processed entirely on your device and are never transmitted to any external server.

iCloud Sync

Some of our applications sync your content and settings across your Apple devices using Apple's iCloud services (CloudKit and iCloud Key-Value Store). This data is stored in your private iCloud container, encrypted by Apple, and is not accessible to IROIRO LLC or any third party. iCloud sync features may be limited to certain subscription tiers.

Google Drive Backup

Some of our applications can back your content and settings up to your own Google Drive. This is optional: it happens only if you sign in with a Google account inside the application, and the only permission the application asks Google for is access to its own hidden application-data folder in your Drive. The backup is stored under your Google account, is subject to Google's privacy policy, and is not accessible to IROIRO LLC. Signing in tells Google which account is using the application; the application does not send your name, your email address, or your account identifier to us or to anyone else, and uses them only to show which account is signed in. You can end the backup by signing out inside the application, and delete the stored data from your Google Drive settings for connected applications.

Transfer of Data

Your information, including Personal Data, may be transferred to — and maintained on — computers located outside your state, province, country, or other governmental jurisdiction where the data protection laws may differ from those of your jurisdiction.

If you are located outside the United States and choose to provide information to us, please note that we transfer the data, including Personal Data, to the United States and process it there.

Your consent to this Privacy Policy followed by your submission of such information represents your agreement to that transfer.

IROIRO LLC will take all steps reasonably necessary to ensure that your data is treated securely and in accordance with this Privacy Policy, and no transfer of your Personal Data will take place to an organization or a country unless there are adequate controls in place including the security of your data and other personal information.

Disclosure of Data

Legal Requirements

IROIRO LLC may disclose your Personal Data in the good faith belief that such action is necessary to:

To comply with a legal obligation
To protect and defend the rights or property of IROIRO LLC
To prevent or investigate possible wrongdoing in connection with the Service
To protect the personal safety of users of the Service or the public
To protect against legal liability

Security of Data

The security of your data is important to us, but remember that no method of transmission over the Internet or method of electronic storage is 100% secure. While we strive to use commercially acceptable means to protect your Personal Data, we cannot guarantee its absolute security.

Deleting Your Data

Every application of ours that keeps anything about you on our servers has a control in its settings that deletes your data, labeled Delete Data.

What Delete Data erases, at once and for good:

The record our game server keeps for you in that application: the name shown beside your scores, your plays and the scores they earned on every leaderboard, your progress, streaks and collection, the push token that lets an alert reach you, and anything else stored with that record. See “Cloudflare Workers” below.
Your feedback conversations and the push token stored for replies. See “In-App Feedback” below.
Your progress on the device, and the copy of it in your Game Center or Google Play Games saved game, which is reset to blank.

What it keeps, and why:

Purchases. Apple and Google hold the record of what you bought, so a purchase can always be restored. A game that keeps the store’s transaction identifier with your record, so the purchase follows you to your other devices, erases that identifier with the rest of the record; restoring the purchase from the store adds it back.
The newsletter. If you signed up for the IROIRO Letter, your email address is on a separate list that Delete Data cannot reach. Leave it from the unsubscribe link in any email, or at iroi.ro/unsubscribe.
Analytics and crash reports. These are held by Google and expire on Google’s own retention schedule. They are stored against the per-installation identifiers described under “App Store Privacy Labels”, never against your game record, your name or your email address.

If you no longer have the application installed, contact us through our contact page. Your game record is stored against a random identifier rather than your name or email, so tell us the name shown beside your scores and roughly when you played, and we will erase the record that matches.

Service Providers

We may employ third-party companies and individuals to facilitate our Service ("Service Providers"), to provide the Service on our behalf, to perform Service-related services, or to assist us in analyzing how our Service is used.

These third parties have access to your Personal Data only to perform these tasks on our behalf and are obligated not to disclose or use it for any other purpose.

Analytics and Firebase Services

We may use third-party Service Providers to monitor and analyze the use of our Service.

Google Analytics: Google Analytics is a web analytics service offered by Google that tracks and reports website traffic. Google uses the data collected to track and monitor the use of our Service. This data is shared with other Google services. Google may use the collected data to contextualize and personalize the ads of its own advertising network.
Firebase: Our mobile applications may use Firebase, a platform provided by Google, for various services including:
- Firebase Analytics: To collect usage and behavior data to help us understand how users interact with our applications.
- Firebase In-App Messaging: To display targeted messages and announcements within our applications.
- Firebase Dynamic Links: To create links that provide a seamless user experience across platforms.
- Firebase Cloud Messaging: To send push notifications and messages to users.
- Firebase Crashlytics: To report crashes and errors so we can diagnose and fix them. See Crash Reporting below.

You can opt out of having made your activity on the Service available to Google Analytics by installing the Google Analytics opt-out browser add-on. The add-on prevents the Google Analytics JavaScript (ga.js, analytics.js, and dc.js) from sharing information with Google Analytics about visits activity.

For more information on the privacy practices of Google and Firebase, please visit the Google Privacy & Terms web page: https://policies.google.com/privacy?hl=en

Third-Party Advertising Providers

Some of our applications display advertisements from third-party providers. These providers may receive device information, search queries, and advertising identifiers (when tracking is authorized) for the purpose of delivering and measuring ads. Ad creatives served by these providers may load tracking pixels from additional third-party domains.

Where one of our websites is ad-supported, the advertising is served by Google AdSense. Google is a third-party vendor and uses cookies to serve ads based on your prior visits to our sites and to other sites on the internet.

Google's use of advertising cookies enables it and its partners to serve ads to you based on your visit to our sites and/or other sites on the internet.
You may opt out of personalized advertising by visiting Google Ads Settings. Opting out does not remove ads; it makes the ones you see non-personalized.
You can opt out of personalized advertising from many other vendors at www.aboutads.info/choices (United States), www.youronlinechoices.eu (Europe), or youradchoices.ca (Canada).
Where consent for advertising cookies is required by law, it is collected and recorded through Google’s consent management on our behalf, and you may change or withdraw it at any time from the same prompt or through the links above.

For details on how Google uses information from sites that use its services, see How Google uses information from sites or apps that use our services.

Apple CloudKit

Some of our applications use Apple's CloudKit service to sync content and metadata across your devices. Data synced via CloudKit is stored in your private iCloud container and is subject to Apple's privacy policy.

Google Drive

Some of our applications use Google Drive to back your content up to your own Google account, through a hidden application-data folder that only that application can read. Data stored there is subject to Google's privacy policy. See “Google Drive Backup” above.

Cloudflare Workers

We use Cloudflare Workers to process certain Service-related operations, such as feedback submissions, newsletter sign-ups, and the online play in our games. Data sent to Cloudflare Workers is processed in accordance with Cloudflare's privacy policy.

A game with online play keeps a small record on our own server so that leaderboards, duels and cross-device play can work. It is stored against a random identifier the application creates the first time it goes online, never against your name or email: the initials you type and, only if you choose it, your gamer tag, both shown beside your scores; the words you play and the scores they earn, which other players can see on the leaderboards; your progress, your daily streak, the emoji you wear beside your name, your record against the people you duel, the push token that lets a duel alert reach you, and any names you have chosen to hide. Every one of these is erased when you choose Delete Data in that application’s settings.

A game that signs you in with Game Center or Google Play Games keeps its record against that account’s player identifier instead, with the name that account shows, which appears beside your scores. The record holds your runs and the scores they earned on the leaderboards, the inputs of a run while it stands in a leaderboard’s top 100 or is under review so others can watch it replayed, your progress and collection, the profile card you build, the store’s transaction identifier for a purchase you made, and, for each device you play on, an identifier the game creates there with the result of Apple’s App Attest or Google’s Play Integrity check that the game is genuine. Our server keeps no IP address. Every one of these is erased when you choose Delete Data in that game’s settings.

Rexy’s weekly fan ballot, Rexy Hype, adds each ballot you cast to that show’s total for the week. For that week our server also keeps a code derived from your installation, which changes every week and cannot be traced back to you, together with how many ballots it has used; it records nothing about which shows those ballots went to, and it is deleted a week after the week closes. For a Rexy+ member, the subscription proof Apple signs is checked and then discarded; a code derived from the purchase, kept the same way and deleted with the week, limits how many installations one subscription can vote from.

In-App Feedback

When you send feedback from inside one of our applications, your message and a short technical summary of your device (application version, device model, operating system version) are sent to our feedback service, where they become a support conversation and a ticket in that application's private issue tracker. You can read our replies in the application, and reply again while the conversation is open.

Feedback is identified only by a random, per-installation identifier generated on your device the first time you send something. It is not your name, your email address, or any account identifier, and we do not use it to build a profile of you. If you allow notifications, the application also registers a push token against that identifier so we can tell you when we have replied.

You can erase everything we hold for that identifier from within the application, using the data-deletion control in its settings.

The IROIRO Letter (optional newsletter)

Some of our applications offer an optional newsletter sign-up beside the feedback form. The checkbox is off by default and the email field only appears if you tick it — if you do not, no address is collected.

If you do provide an address, it is sent to a separate service, backed by a separate database from the feedback service described above. That database holds no feedback content and no feedback identifier, and the feedback service holds no email addresses, so the two cannot be joined. Feedback content is still reported as linked to you, because it is keyed to that per-installation identifier; what this separation guarantees is that it is never joined to your email address.

Your address is recorded as pending until you confirm it by clicking a link in a confirmation email we send you. We use it only to send you occasional news and updates about IROIRO and our applications. You can leave the list at any time from the unsubscribe link in any email we send, or at iroi.ro/unsubscribe. Deleting your data inside an application does not remove your address from the newsletter list, because the two systems are deliberately kept separate — use the unsubscribe link instead.

Crash Reporting

Some of our applications include crash reporting, provided by Firebase Crashlytics (Google). When an application stops unexpectedly, or hits an error it cannot recover from, it sends us a report so we can find the fault and fix it.

A report contains the point in our code where the failure happened, the state of the device at that moment — device model, operating system version, application version, available memory and storage, and whether the device has been jailbroken — and a record of the screens visited beforehand. It also carries an installation identifier generated on your device, so that repeated crashes from one installation can be recognised as the same problem.

What a crash report never contains: your name, your email address, your account, or any of the content you create in the application. We do not attach an account to crash reports, and we do not use them for advertising or to build a profile of you. We still report Crash Data as linked to you, because of the installation identifier described just above: Apple asks whether data is linked to your identity “via your account, device, or other details”, and an identifier that every report is stored against is a device-level identity even when no name or email is involved. Saying otherwise would understate what we hold.

Crash reporting is why those categories appear in our App Store privacy labels at all for our own account, rather than only for our advertising providers. It is collected for app functionality — keeping the applications working — and for understanding how often failures occur.

App Tracking Transparency

Some of our mobile applications participate in Apple's App Tracking Transparency (ATT) framework. Before any advertising identifiers are shared with third-party advertising partners, the application will request your permission via Apple's system prompt.

If you allow tracking: Your User ID and Device ID (IDFA) may be shared with advertising partners to enable personalized ad delivery.
If you deny tracking: No advertising identifiers are shared. You may still see ads, but they will not be personalized based on your identity.

You can change your tracking preference at any time in your device's Settings under Privacy & Security > Tracking.

App Store Privacy Labels

In accordance with Apple's App Store requirements, we disclose the following data practices for our iOS applications. The lists below are the combined practices across our applications; any individual application collects only what its own features require, and each app's App Store product page states its own answers.

Data Used to Track You — only in applications that ask for tracking permission through Apple's App Tracking Transparency prompt, and only when you grant it:

Device ID (IDFA)
User ID
Search History
Coarse Location
Product Interaction
Advertising Data

An application that does not present the tracking prompt collects nothing in this category. Such an application sends no advertising identifier and no persistent identifier to its ad provider, only an identifier that is regenerated every time the app launches, so the ads it shows are not personalised to you across sessions or across apps.

Data Linked to You:

Other User Content (things you deliberately send us from inside an application)
Gameplay Content (in a game with online play: your runs and scores, the replays of runs on the leaderboards, and your profile card, for app functionality)
User ID (a Google account sign-in used only to back your content up to your own Google Drive; in an application with friend sharing, the iCloud account identifier and the display name you choose, published in that application’s friend directory so someone can see who they are connecting to; or, in a game with online play, the random player identifier described under “Cloudflare Workers” with the initials and, if you choose it, the gamer tag shown beside your scores, or the Game Center or Google Play Games player identifier and name)
Purchase History (analytics; app functionality, where a game keeps the store’s transaction identifier so a purchase follows you to your other devices; and, in Rexy, the weekly purchase code described under “Cloudflare Workers” that limits how many installations one subscription can vote from)
Product Interaction (analytics; and app functionality, such as counting a Rexy Hype ballot against the week’s allowance)
Advertising Data (third-party advertising; and, in an application that measures Apple Ads campaigns, whether and through which campaign an Apple Ads ad brought the installation, as Apple’s attribution service reports it, for analytics and our own advertising)
Coarse Location (the general location that our advertising and analytics providers estimate from your IP address)
Email Address (optional newsletter sign-up, used for our own marketing)
Device ID (analytics; and, where an application can notify you, the push token your device registers so a reply or an episode countdown can reach it)
Customer Support (in-app feedback conversations)
Performance Data (analytics; and, in an application that shows ads, the performance data its advertising and consent libraries send together with the device identifier, used for our own and third-party advertising, analytics and app functionality)
Other Diagnostic Data (app functionality and analytics)
Crash Data (app functionality and analytics)
Other Data Types (push notification registration)

Data Not Linked to You: none. Every category above that we collect is stored against a persistent identifier, so we report all of it as linked.

Device ID appears in both lists above, and which one applies — if either does — depends on the application. As with everything in this section, these are the combined practices across our applications rather than a description of any one of them; each app’s App Store product page states its own answers.

In the tracking list, Device ID means the advertising identifier (IDFA/AAID), which is shared with advertising partners only in applications that ask through Apple’s App Tracking Transparency prompt, and only when you allow it. In the linked list it means something narrower. Where an application includes analytics and no advertising identifier is available to it, the analytics provider falls back to Apple’s Identifier for Vendors — a value that is the same across our own applications on one device and different on everyone else’s. So some of our applications collect an advertising identifier, some collect only this vendor identifier, and some collect neither.

Where a vendor identifier is collected, we use it to count how many people use a feature and to tell a returning person from a new one. It is not attached to your name, your email address or anything you create, it is never combined with data from other companies, and in an application without ads it is not shared with advertising partners. In an application that shows ads, the advertising library reads the vendor identifier itself and sends it to Google with its ad requests, as described under “Advertising Data” above. Deleting the last of our applications from a device clears it.

We report that identifier, and the analytics attached to it, as linked to you. Apple asks whether data is linked to your identity “via your account, device, or other details”, and a persistent identifier that every event is stored against is a device-level identity even when no name or email is involved. Saying otherwise would understate what we hold. It remains not used for tracking, which is a separate question: tracking means combining this data with other companies’ data for advertising, or sharing it with a data broker, and we do neither.

Customer Support is reported as linked to you. A feedback conversation is keyed to a random per-installation identifier, and where you allow notifications the reply token is stored against that same identifier — a device-level identity we can read. What the separate storage does buy is narrower and real: feedback is held apart from the newsletter list, which is the only place we hold an email address collected in an application, so your support conversation is not joined to your email address. That is a different promise from “not linked”, and we would rather state the stronger obligation. See “In-App Feedback” and “The IROIRO Letter” above.

Crash Data and Other Diagnostic Data are both reported as linked to you, for the same reason. A crash report carries no account, no email address and none of the content you create, and our crash reporter’s own privacy manifest declares it not linked — but a supplier’s manifest describes that supplier, not us, and “carries no account” answers a narrower question than Apple asks. Both categories are stored against the same persistent per-installation identifier described above, which is a device-level identity, so both get the same answer. Performance Data follows the same rule. Where analytics do not collect it, the advertising and consent libraries still do, and they send it together with the device identifier the advertising library itself declares linked, so it is reported as linked to you even though each library’s own manifest says otherwise. Where a category is collected by more than one route, we report the answer that covers all of them. See “Crash Reporting” below.

Coarse Location is not a location permission: none of our applications asks for one, and none reads your device’s location. It is the general location that advertising and analytics providers estimate from the IP address of any connection, which Google discloses for both its advertising SDK and its analytics SDK. It is listed as linked to you because those providers attach it to the same identifiers described above.

Content that only syncs through your own iCloud account is not collected by us at all. Apple defines collecting as sending data off your device in a way that lets us reach it; records and photos that an application stores in your private iCloud database stay in storage only you can open, and we cannot read them. An application whose content never leaves your own account therefore declares nothing for it. That is why photos and videos appear nowhere in the lists above: the applications that hold them keep them on your device and in your own iCloud, and one of them makes no network connection at all. Other User Content is listed only for the narrower case where you deliberately send us something. Where an application offers a cloud backup you sign in to, the copy lives in your account there as well.

User ID, for the applications that offer a Google Drive backup, applies only once you sign in — it is the Google account you sign in with; in a game with online play it is the random player identifier and the name you show beside your scores. The backup itself is not collected by us: it is written to the hidden application folder inside your Drive, the only scope those applications request, which we cannot browse or read. See “Google Drive Backup” above. Other Data Types is the registration information the push-notification service sends with its token — device model, language, time zone, and operating-system and application versions — which its provider declares as not linked to you. We report it as linked to you, because the registration is made under the same persistent per-installation identifier described above.

Links to Other Sites

Our Service may contain links to other sites that are not operated by us. If you click on a third-party link, you will be directed to that third party's site. We strongly advise you to review the Privacy Policy of every site you visit.

We have no control over and assume no responsibility for the content, privacy policies, or practices of any third-party sites or services.

Children's Privacy

Our Service does not address anyone under the age of 13 ("Children").

We do not knowingly collect personally identifiable information from anyone under the age of 13. If you are a parent or guardian, and you are aware that your child has provided us with Personal Data, please contact us. If we become aware that we have collected Personal Data from children without verification of parental consent, we take steps to remove that information from our servers.

Changes to This Privacy Policy

We may update our Privacy Policy from time to time.

We will notify you of any changes by posting the new Privacy Policy on this page.

We will let you know via email and/or a prominent notice on our Service, prior to the change becoming effective and update the "effective date" at the top of this Privacy Policy. You are advised to review this Privacy Policy periodically for any changes. Changes to this Privacy Policy are effective when they are posted on this page.

Contact Us

If you have any questions about this Privacy Policy, please contact us by visiting this page on our website: https://iroi.ro/pages/contact.html