thinkblox.PH
Let’s talk
All privacy policies

ANDROID MOBILE APP / PRIVACY POLICY

Radiant Circle (including Radiant Rush) Privacy Policy.

Radiant Circle is a Solana Mobile social app with daily rituals, profiles, Shared Sparks, private chat, AI-assisted conversation starters, the Radiant Rush game, and optional onchain features. These descriptions reflect the public project documentation and require confirmation against the deployed release.

Updated: 2026-10-18 · Developer: ThinkBlox PH · Operated by Juan Carlos Claridad

Android package: com.thinkblox.radiantrush

1. Scope and developer

This policy concerns Radiant Circle (including Radiant Rush), a product of ThinkBlox PH operated by Juan Carlos Claridad in the Philippines. It is distinct from the ThinkBlox PH website policy and from other products' policies.

2. Data accessed or handled

  • Account identity, profile information, interests, connections, messages, and game or activity progress used for social and application features.
  • Optional wallet public address and onchain transaction information for Solana Wallet Adapter and ORE functionality. The public repository describes wallet operations as non-custodial.
  • Device motion for the Shake to Discover interaction; review of permissions and motion processing is still required.

3. Data collected or stored

  • The public project documentation describes Firebase Authentication, Cloud Firestore, and backend functions for social identity, profile information, connections, private messaging, and feature state.
  • For AI conversation suggestions, a backend function uses shared profile-interest context to request an AI-generated starter. The documentation states that private chat history is not sent for this feature.
  • Specific identifiers, telemetry, crash reports, retention periods, and remaining SDK-transmitted data must be verified from the deployed Android package and backend configuration.

4. Purposes

  • To operate accounts, social discovery, Shared Sparks, connections, private chat, game features, and user-requested AI starter suggestions.
  • To support optional user-approved Solana transactions, onchain verification, and portfolio displays.
  • For application reliability and abuse prevention where implemented; exact logging and moderation processing require verification.

5. Sharing and recipients

  • Firebase/Google infrastructure processes account and application data for authenticated social features, according to the published architecture.
  • AI starter requests send shared-interest context to an AI service through a backend function; users decide whether to use the resulting suggestion.
  • User-authorized Solana transactions and related wallet addresses may become visible on the public blockchain and to the wallet provider. Public blockchain records generally cannot be erased by the app developer.
  • Recipients of diagnostics, device identifiers, or other SDK data are not yet fully audited.

6. External services

  • Google Firebase: Authentication, Firestore storage and Cloud Functions for the documented social and backend features. Provider privacy information
  • OpenAI API: Generates optional AI conversation starters using shared-interest context sent by the backend, per project documentation. Provider privacy information
  • Solana network and wallet providers: Process and publicly record wallet-approved transactions when a user chooses onchain functionality.

7. Device or browser permissions

  • Device motion supports Shake to Discover. Precise manifest permissions and runtime requests must be audited.
  • Optional wallet interactions require user approval in the connected wallet. Other device permissions must be verified in the production build.

8. Security

The public repository documents server-side AI keys, Firestore access rules, backend relationship checks, and user-approved wallet transactions. A full security review of the deployed app and services is still required.

9. Retention

The retention periods for account information, social relationships, messages, progress, analytics and backend logs have not yet been validated. Public Solana blockchain transactions may remain permanently visible.

10. Deletion and account controls

In-app Remove and Block functions control social relationships, but are not the same as account deletion. An actual account and associated-data deletion workflow must be verified and made available before Google Play submission.

Account deletion: The required in-app account-deletion path and dedicated external account-deletion resource have NOT been verified. Contact the developer for a privacy request in the meantime; contact email alone does not meet Google Play's account-deletion requirement.

11. Children and age-related privacy

Target ages, any applicable age restrictions, and protections for younger users of social and chat features must be verified before app-store publication.

12. International data handling

Firebase, AI service processing, wallet infrastructure and the Solana network may involve processing outside the Philippines. The specific processing arrangements require confirmation.

Policy updates

This notice may change after implementation reviews or product updates. The updated date will be revised when the disclosed practices change. Android app policies must agree with their current Google Play Data safety disclosures.

Contact for privacy inquiries

Developer: ThinkBlox PH · Juan Carlos Claridad · Philippines

Email: juanc.claridad@gmail.com

Include the product name and the nature of your request. Do not include passwords, recovery phrases or private keys.