Privacy Policy
1. Scope and responsible entity
This Privacy Policy (this “Policy”) describes how CodeBoss Tech LLC, a Texas limited liability company (“Riceball,” “we,” “us” or “our”), collects, uses, discloses and retains personal information in connection with the Riceball application, website and related services (collectively, the “Services”). “Personal information” means information that identifies, relates to or is reasonably capable of being associated with an individual, as further defined under applicable law.
This Policy applies to information obtained from you, from your device, from authentication and subscription providers, and through your use of the Services. Third-party sites that you visit through links in the Services are governed by their own privacy notices. This Policy describes processing practices; it does not, by itself, constitute consent to processing for which separate consent is required.
2. Categories and sources of personal information
| Category | Information processed | Source |
|---|---|---|
| Account identifiers | Apple sign-in identifier, internal Riceball account identifier, name and email address, including an Apple private relay address where selected. | You, Apple and account creation. |
| Profile information and inferences | Onboarding answers, interests, activities, preferences concerning other members, work or life context, adult-oriented event preferences, generated profile summaries and numerical representations used for matching (“embeddings”). | You and inferences generated from your responses. |
| Location information | A city or location you enter, or device coordinates provided with your permission; recorded location precision; derived city, region, country, search radius and supported event area. | You, your device and location resolution services. |
| Device and notification information | App installation identifier, push notification token, platform and notification permission status. | Your device. |
| Service activity | Events displayed, event responses, recommendations delivered, matches, introductions, and onboarding screens viewed and time spent. | Your interactions with the Services. |
| Communications | Messages sent through member conversations and associated safety review information. | You, other participants and safety processes. |
| Subscription information | Subscription status, plan, purchase records and account identifiers used to administer access, or an access code you redeem. Riceball does not receive your payment card information or billing address from App Store purchases. | Apple, RevenueCat and you. |
| Support information | Correspondence you send to support and our responses. | You and Riceball. |
| Technical and diagnostic information | Connection and request information, including IP addresses processed by hosting or network services, error reports, device or application context and operational logs. | Your interaction with the Services and infrastructure or error reporting providers. |
Device location may be precise when you authorize precise location access. Selecting or displaying a city does not necessarily mean that stored device coordinates have been reduced to city-level precision. We do not collect device location continuously in the background. You may enter a city instead of granting device location permission.
We do not request access to your contacts, photo library, calendar or health records. Information you voluntarily include in free-text answers, messages or support correspondence may contain sensitive information; please provide only information necessary for your intended use of the Services. We do not use advertising identifiers or track your activity across unrelated applications and websites for advertising.
3. Purposes of processing
We process personal information to:
- establish and authenticate accounts and administer subscriptions or access codes;
- resolve your location and supported event area, identify relevant events, generate profiles and recommendations, and avoid repeating prior recommendations;
- identify potentially compatible members, generate introductions and deliver member communications;
- deliver notifications concerning recommendations, introductions and messages where permitted by your device settings;
- review safety concerns, prevent misuse, investigate errors and maintain the security and operation of the Services;
- respond to support correspondence and privacy requests; and
- evaluate onboarding and matching performance, including through aggregate analysis, to improve the Services.
Automated systems, including AI models, process profile information and activity preferences to generate summaries, rankings and introductions. Their output may be incomplete or inaccurate. You may request correction of information used about you by contacting support.
4. Recipients and disclosures
We disclose information to the following categories of recipients for the purposes described below:
- Other members. Members to whom you are introduced receive your display name and an introduction derived from relevant aspects of your profiles. We do not display your email address, precise coordinates or complete onboarding responses to them. Messages you send are available to their recipients, who may retain copies outside the Services.
- Authentication, payment and notification providers. Apple supports sign-in, App Store purchases and iPhone notification delivery. RevenueCat receives your internal Riceball account identifier and processes associated purchase and entitlement information as necessary to administer subscriptions; our integration does not intentionally supply your name or email to RevenueCat. Expo relays push notifications to Apple and receives the device push token and notification payload necessary for delivery. These billing and notification identifiers are necessary to provide the respective services.
- AI processing providers. OpenRouter and the model providers to which it routes requests receive relevant profile text, preferences and event or matching context for profile generation, embeddings, ranking and introductions. Certain requests include your display name. Profile text may itself contain identifying information that you provided. We do not intentionally include your internal Riceball account identifier or email address as account fields in these requests or submit conversations between members to these models.
- Location services. Google receives location search text, such as a city, region or other location entered by you, when needed to resolve that location. Device location features may also use the operating system's location services under your device settings.
- Hosting, security and diagnostics providers. Hetzner hosts our application servers in Ashburn, Virginia, United States. Cloudflare provides network security and performance services. Sentry receives error reports and associated diagnostic context when error reporting is enabled. Our Sentry configuration disables default personal-information collection; this setting does not guarantee that error messages or diagnostic context contain no personal information.
- Website resource providers. Our website loads fonts from Google-hosted resources, which causes your browser to contact Google and transmit ordinary connection information.
We obtain public event listings from providers such as Ticketmaster, Fever and local publishers using event-area searches. These catalog fetches do not transmit member profiles or account information to event providers. When you follow an original listing, ticket or map link, the destination may receive information directly from your device, and its own privacy practices apply.
We may also disclose information where required by law or valid legal process, to protect members from harm, or in connection with a merger or sale of the business. Information transferred in a business transaction remains subject to the commitments in this Policy unless lawfully changed with any notice and consent required by law.
We do not sell personal information, have not sold personal information, and do not share personal information for cross-context behavioral advertising or use it for targeted advertising.
5. Retention and deletion
We retain account and associated service information while your account remains active. Event responses and delivered recommendations are retained to support the Services and avoid duplication. Operational logs are retained for security and debugging for a limited period.
Successful in-app account deletion removes your account and associated profile, location, device, response and conversation records from the application's active account database as part of that operation. Requests submitted through support are subject to verification, and we will complete deletion of personal information under our control within thirty (30) days, subject to any legally required retention. Backup copies are overwritten according to the applicable backup rotation and are not immediately erased by the in-app operation.
Account deletion does not itself cancel an Apple subscription or erase records independently maintained by Apple or other providers under their own legal obligations. It also cannot erase copies of communications retained independently by their recipients. Separate operational logs, support correspondence and provider-held records require treatment through the applicable retention or deletion process; in-app deletion should not be understood as instantaneous erasure from every system.
6. Permissions and privacy requests
You may grant or revoke location and notification permissions in your device settings. A manually entered city may be used without device location permission. Without a usable location, we cannot provide local recommendations; disabling notifications does not prevent you from viewing available recommendations in the application. Sign in with Apple's Hide My Email option allows you to supply a relay address.
You may request access to, correction of or deletion of your personal information by emailing [email protected]. You may also delete your account through the Account screen, accessible using the gear on Matches. We may require information reasonably necessary to verify your identity and authority before fulfilling a request. We will use verification information for that purpose and respond within applicable legal time limits.
Depending on your state of residence and whether the relevant law applies to Riceball, you may additionally have rights to obtain information about collection and disclosure, receive a portable copy of your information, use an authorized agent, appeal a denied request, or opt out of specified sales, advertising, profiling or uses of sensitive information. To submit an appeal, contact the same address and identify the request you wish to appeal. Applicable exceptions and verification requirements may limit particular requests. We will not unlawfully discriminate against you for exercising privacy rights.
We do not sell personal information or share it for cross-context behavioral advertising; consequently, we do not conduct those activities irrespective of an opt-out signal. Browser “Do Not Track” signals do not otherwise alter the processing described in this Policy. Applicable statutory rights concerning recognized opt-out preference signals remain unaffected.
7. Security and processing locations
We use HTTPS for transmission to our application servers, restrict server access and store application session tokens in hashed form. These measures do not guarantee absolute security. If we learn of a security breach affecting your personal information, we will notify you; legally required notices will be provided in accordance with applicable requirements.
Our application servers are located in the United States. Providers may process information in additional locations. This Policy does not represent that all providers retain information exclusively in the United States.
8. Individuals under eighteen
The Services are intended for individuals aged eighteen (18) and older. We do not knowingly collect personal information from individuals under eighteen. If you believe that such information has been provided to us, contact support so that we may investigate and delete it.
9. Changes to this Policy
We may revise this Policy and will identify the effective date of the revised version. For material changes, we will provide notice in the application before they take effect. Where applicable law requires consent to a change in processing, we will obtain that consent before undertaking the affected processing.
10. Contact
CodeBoss Tech LLC
[email protected]