1. Who we are
CircleWorld CW is operated by the CircleWorld CW developer (“we”, “us” or “our”). This policy applies to the CircleWorld CW website at circleworldcw.com, its Android app and the account, social, messaging, creator, business and AI features you use.
This is the developer’s privacy notice, not a certification or a privacy guarantee issued by a hosting provider, Google or an app store. Different features process different information. Optional features and SDKs described below do not mean every visitor uses them.
2. Information we collect
- Account details: the email signup form collects username, email and password, with an optional referral association. Account records also include display name and preferences. If you use a supported external sign-in provider, authentication also involves that provider. Phone number and date of birth are not fields in the reviewed email signup form; contact or birth-date details can be supplied in other relevant features.
- Profile information: biography, profile and cover pictures, creator category, links, country, user-entered location, language, discovery preferences and optional self-selected age range. Dating processes date-of-birth and dating-profile details for its adult access check.
- Messages and communications: message text, attachments, conversation participants, timestamps, read/status information and related reports. Calls and livestreams process audio/video and connection information when used. Live sessions also store attendance identifiers, viewer counts, comments and gift activity for session analytics.
- Uploaded and user-generated content: photos, videos, music/audio, posts, stories, articles, comments, reactions, follows, friend requests, community activity, marketplace listings, business bookings and information you submit for moderation or verification.
- AI features: prompts, supplied files, conversation context, generated results and usage records. AI character conversations are labelled as AI, require your choice to begin, and are saved to your account.
- Payments and rewards: purchase and payment references, amounts, status, wallet and gift transactions, campaign submissions and fraud-review records. Bank or payout details are processed where a relevant feature requests them. Paystack handles the payment checkout; payment credentials you enter there are handled under its own privacy notice.
- Device, usage and technical information: browser/device information needed for sessions, language and preferences, service requests and error information. Hosting and connected services receive network information such as your IP address when contacted. First-party records include content engagement, visits, referral sources, campaign tags and a browser visitor identifier on supported traffic pages. Advertising SDK data is described in section 6.
Camera, microphone and file access are used by recording, upload, live and call features. Permission requests depend on your browser or installed app and device. You can revoke available permissions in your browser or operating-system settings; this may stop the related feature working.
3. How we use information
Information supports account creation and sign-in; profile and content display; messaging, calls and live sessions; discovery and community features; delivery of AI requests; payments, rewards and transaction reconciliation; creator and traffic reports; support; and the prevention and review of abuse, fraud and policy violations.
Preferences help determine visibility, who can contact you and which content you see. Reports, blocks and suspicious reward or payment activity support safety and moderation decisions. Financial and administrative history supports review and dispute handling. A recorded interaction or balance is not a promise of payment.
5. Service providers & external services
- Lovable Cloud: account authentication, application records, uploaded-file storage and server-side processing use the configured cloud services.
- Paystack: checkout, payment verification and relevant payment operations use Paystack. Review Paystack’s privacy notice.
- LiveKit: integrated call and livestream features use LiveKit when the service is configured. Participants’ media and connection information pass through the communications service. Integration alone does not establish that broadcasts or calls are recorded.
- Lovable AI and model services: AI requests are processed through configured AI services. AI character messages and context are sent through Lovable AI to OpenAI to generate a response. Other AI creation features process the input necessary for the requested generation. A request not to store provider conversations is not a guarantee that provider logs or other records are absent.
- Google: the Android app integrates Google AdMob and its consent tools. The website also loads fonts from Google Fonts, which receives the associated network request. Google sign-in, when available and chosen, involves Google’s authentication service. See Google’s privacy policy.
- Lovable-managed email: the app integrates Lovable email services for account and service notices. Delivery also involves your recipient email provider. Integration does not establish current sending status, the underlying delivery vendor or its retention settings.
- External media and links: opening official YouTube/Vimeo players or external websites contacts those services. Their own notices cover the information they receive.
Provider names do not imply that every integration is enabled in every country or app version. Exact processing locations, provider retention periods and contractual transfer arrangements have not been specified by the developer in this notice.
6. Advertising & Google AdMob
The Android wrapper includes the Google AdMob SDK and Google’s consent tools. Banner display is conditional on the app’s advertising configuration and whether Google’s consent result allows ad requests. The checked release configuration leaves production banner inventory disabled unless explicitly enabled. This notice does not assert that a particular installed release currently serves ads or has app-store approval.
When the SDK is initialized or ads are requested, Google and its advertising partners may process IP-derived approximate location, device and advertising identifiers, app/ad interactions and diagnostic information under Google’s SDK practices and the choices applicable to your device and region. Non-personalised or limited ads do not mean no data is processed. See how Google uses advertising information.
You can save app advertising choices on Privacy choices. On supported Android installations, that page also offers Google ad privacy options. Your operating system may offer controls for the advertising identifier. Private AI character conversation content is not used by that feature to target advertising.
7. Cookies & similar technologies
The app uses browser/device storage for authentication, consent choices, appearance and language preferences, referral attribution, notification settings and other feature preferences. Some interface preferences may use cookies. Supported offline features store saved content, drafts and queued actions on your device.
The Privacy choices page stores preferences for personalised advertising and analytics. It is not a universal switch for all operational records: transaction, safety, content-engagement and supported traffic records are also created by the features you use. This policy does not claim that declining analytics stops every usage record.
You can manage choices in the app and clear site data through your browser/device settings. Clearing local data may sign you out or remove local drafts and saved content; it does not delete the information held in your online account or by service providers. Shared devices can expose locally saved information to other device users.
8. Location information
Profile, business, event and dating features can process location, country or region information you choose to enter. Your language/region preferences may also be stored. Review a field’s visibility before including a precise address.
No device GPS collection was identified in the reviewed app code. This is not a promise that connected services process no location: hosting and advertising services receive IP addresses and may derive approximate location. Any future device-location collection needs to be disclosed alongside applicable device permission controls.
9. Storage & security
Account and feature records are stored in the configured cloud database, and uploads in cloud file storage. Some restricted media is delivered using expiring links after server-side access checks. Local copies may exist on your device, and providers process information for their own part of the service.
Implemented measures include authenticated sessions, server-side permission checks, database access rules, and confirmation/review checks for sensitive financial operations. These are safeguards, not a guarantee against loss, unauthorised access or disclosure. This policy does not make an unverified encryption-at-rest or end-to-end encryption claim; AI character chats are not end-to-end encrypted. Avoid sending passwords or other highly sensitive information in messages or AI prompts.
10. Retention & remaining records
Information remains in account, content, communication and transaction systems as those features operate. Some financial, audit and dispute histories are append-only; account removal is not a promise that those histories will be erased. Public copies, recipient copies and independent provider records may remain outside the developer’s immediate control.
Retention period: account and content information is retained while your account is active. Verified deletion requests are completed within 90 days: sign-in ends as soon as the deletion is applied, and information within our control is removed by that deadline. Some records may persist beyond that deadline where systems are append-only, held in backups, or retained by independent providers, as described above; requests made by email follow the same deadline for the records within the developer’s control.
11. Account deletion & data deletion requests
Self-service account deletion
- Open circleworldcw.com/delete-account, or choose Settings → Delete account.
- Sign in to the account you want removed. The information page is public, but deleting an account requires its signed-in session.
- The page checks for a positive wallet balance, pending earnings or an in-progress withdrawal. These conditions currently block self-service deletion. Payout controls are not open in the current member interface; if a financial blocker prevents deletion, contact the developer rather than expecting an available withdrawal button.
- If no blocker is shown, type DELETE and choose Delete my account permanently. On successful completion, the account sign-in is deleted and you are signed out. This action cannot be undone through this page.
What the current procedure does—and does not promise
The procedure explicitly removes your AI character conversation and usage records, requests removal/private status for your posts and removal status for your marketplace listings, then deletes the authentication account. Related database records can be deleted or lose the account reference according to their relationships. This is not verified as a complete purge of every photo/video file, message, comment, report, financial record, service log, backup or provider copy.
If you cannot sign in, or want specific data removed
Email circleworld26@gmail.com from your account email where possible. Use “CircleWorld CW account deletion” or “CircleWorld CW data request”, include your username, and identify the account or data you want removed. Explain if a wallet blocker or lost account access is involved. Do not send a password, full payment-card details or unnecessary identity documents.
This is a contact-based request, not an automatic deletion form. Account ownership and applicable retention needs must be checked before a request can be fulfilled. Verified deletion requests are completed within 90 days: sign-in ends as soon as the deletion is applied, and information within our control is removed by that deadline. Deleting an individual AI conversation from its chat page is also available without deleting your entire account.
12. Your privacy rights & choices
Depending on applicable law and your location, you may be entitled to request access, correction, a copy or portability of information, deletion, restriction, objection to certain processing, or withdrawal of consent where processing relies on consent. These rights may have exceptions, including relevant financial, legal, safety and third-party interests. You may also have a right to complain to your local data-protection authority.
Edit available profile fields in Settings, control visibility and discovery, block/report accounts and review Privacy choices. For requests that cannot be completed in the app, use the contact in section 16. There is no general self-service account-data export tool established in the current app; a request for a copy is handled through contact with the developer.
13. Children’s privacy
Dating is restricted to adults aged 18 or over using date-of-birth checks. Age restrictions on a particular feature do not establish that all account registration is age-verified. A self-selected discovery age range is not identity verification and is not inferred from a photograph.
Minimum age: CircleWorld CW is intended for users aged 18 or over. Account registration and all features, including dating, are subject to this 18-year minimum age. The app is not directed at children, and no claim is made that a universal identity-verification process checks every registrant’s age. If you believe a child under 18 is using the service or has submitted personal information, contact the developer with enough detail to identify the concern, without publicly sharing the child’s information.
14. International users
This public notice can be accessed without signing in wherever the website is accessible. Providers may process information outside your country. Your local rights and available features may differ. The developer has not supplied verified hosting countries or international-transfer arrangements; this notice does not assert a certification or a particular legal transfer mechanism.
15. Policy updates
The developer may revise this notice as features, SDKs or data practices change. Review the “Last updated” date above. Material changes should be explained through an appropriate app, website or account notice; the current app does not establish an automatic privacy-update email process.
16. Contact the CircleWorld CW developer
- App
- CircleWorld CW
- Developer
- CircleWorld CW developer
- Existing published privacy/support contact
- circleworld26@gmail.com
- Website
- https://circleworldcw.com
- Account deletion information
- https://circleworldcw.com/delete-account
No company address or registered legal entity is stated because verified details have not been supplied. The developer still needs to confirm provider processing/transfer details and a monitored privacy-request response process. The email above is the app’s existing published contact; its monitoring and response times are not independently verified.
4. Social visibility & sharing
Other users can see information you publish or share with them: public profiles and posts, comments, reactions, follow relationships where visible, community content, listings, live broadcasts and messages sent to conversation participants. Public creator and community pages can be viewed without an account and may be indexed by search engines.
Settings include profile visibility, discovery participation, contact permissions, following-list visibility and online/last-seen choices. These controls do not erase information already received, saved, downloaded or shared by someone else. A recipient may copy a message or take a screenshot.
Information is also shared with providers needed to run the feature, as described below. Relevant information may be provided in response to a valid legal requirement or for handling safety, fraud and disputes. No blanket promise is made that every uploaded file or record is accessible only to its uploader.