Português | English
Neenbo Privacy Policy
Last updated: July 13, 2026.
This Policy applies to Neenbo on Android and iOS, distributed through Google Play and the Apple App Store. It describes how Personal Data is collected, used, stored, shared and protected in the App, on the website and through Neenbo’s own APIs.
This Policy was prepared taking applicable data protection laws into account, including, where applicable, the LGPD, GDPR and CCPA. It does not replace the privacy policies, terms or controls of app stores, login providers, payment services or other Service Providers used by the App.
Last updated: July 13, 2026.
This Policy applies to Neenbo on Android and iOS, distributed through Google Play and the Apple App Store. It describes how Personal Data is collected, used, stored, shared and protected in the App, on the website and through Neenbo’s own APIs.
This Policy was prepared taking applicable data protection laws into account, including, where applicable, the LGPD, GDPR and CCPA. It does not replace the privacy policies, terms or controls of app stores, login providers, payment services or other Service Providers used by the App.
1 - Controller and contact
Neenbo is controlled by Vanderson Ruiz Cavalcante dos Santos, an individual developer.
For privacy requests, support, access, correction or account deletion, use in-app support or email support@neenbo.com or contato@neenbo.com. Neenbo may request additional information to verify your identity before responding to a request.
Neenbo is controlled by Vanderson Ruiz Cavalcante dos Santos, an individual developer.
For privacy requests, support, access, correction or account deletion, use in-app support or email support@neenbo.com or contato@neenbo.com. Neenbo may request additional information to verify your identity before responding to a request.
2 - Categories of data processed
Account and authentication data: internal user identifier, Firebase identifier, tokens and credentials required for authentication, language, session status and push notification tokens.
Profile data: display name, date of birth, calculated age, gender, search interests, bio, displayed city/location, photos, verification selfies, videos or other content that the User sends or publishes.
Approximate location data: city, country/region, IP-derived location and representative coordinates for a selected or identified city to show relevant people and calculate approximate distance. Neenbo does not collect precise GPS location in the current Android and iOS versions.
Communications and interactions: private messages, voice messages, images sent in conversations, groups, rooms, likes, matches, visits, favorites, blocks, reports, group requests and other interactions with product features.
Technical, diagnostic and security data: IP address, user agent, device or media identifiers used against abuse, advertising identifiers when actually processed by advertising on Android, usage data, technical events, crashes, logs and performance information.
Payments and subscriptions: product identifiers, Google Play purchase tokens, Apple JWS/receipts/transactions, status, validity, validation reason and information required to unlock or restore premium benefits. Neenbo does not receive or store full card details.
Account and authentication data: internal user identifier, Firebase identifier, tokens and credentials required for authentication, language, session status and push notification tokens.
Profile data: display name, date of birth, calculated age, gender, search interests, bio, displayed city/location, photos, verification selfies, videos or other content that the User sends or publishes.
Approximate location data: city, country/region, IP-derived location and representative coordinates for a selected or identified city to show relevant people and calculate approximate distance. Neenbo does not collect precise GPS location in the current Android and iOS versions.
Communications and interactions: private messages, voice messages, images sent in conversations, groups, rooms, likes, matches, visits, favorites, blocks, reports, group requests and other interactions with product features.
Technical, diagnostic and security data: IP address, user agent, device or media identifiers used against abuse, advertising identifiers when actually processed by advertising on Android, usage data, technical events, crashes, logs and performance information.
Payments and subscriptions: product identifiers, Google Play purchase tokens, Apple JWS/receipts/transactions, status, validity, validation reason and information required to unlock or restore premium benefits. Neenbo does not receive or store full card details.
3 - Purposes of processing
We use data to create and maintain the Account, authenticate the User, show relevant profiles and people, provide dating and social networking features, send and receive messages, enable content uploads, operate groups and rooms, handle reports and moderation, prevent fraud and abuse, provide support and maintain security and availability.
We also use data to validate subscriptions, unlock paid benefits, send push notifications, analyze usage and performance, fix crashes, record technical errors, improve stability and, where advertising is enabled, display, measure or limit ads according to the platform, consent choices and system controls.
Technical analytics and diagnostics do not necessarily mean individual monitoring for marketing. These tools are used prudently to understand App operation, stability and performance.
We use data to create and maintain the Account, authenticate the User, show relevant profiles and people, provide dating and social networking features, send and receive messages, enable content uploads, operate groups and rooms, handle reports and moderation, prevent fraud and abuse, provide support and maintain security and availability.
We also use data to validate subscriptions, unlock paid benefits, send push notifications, analyze usage and performance, fix crashes, record technical errors, improve stability and, where advertising is enabled, display, measure or limit ads according to the platform, consent choices and system controls.
Technical analytics and diagnostics do not necessarily mean individual monitoring for marketing. These tools are used prudently to understand App operation, stability and performance.
4 - Public, private and user-visible content
Not all information provided to Neenbo is public. Profile data such as display name, age, city, gender, bio, photos, videos and content published in public or semi-public areas may be visible to authorized users depending on the feature used.
Private messages, voice messages and one-to-one conversations are not publicly displayed. They may be processed and stored for delivery, synchronization, security, reports, moderation, support, legal compliance and Service operation. Neenbo does not provide end-to-end encryption for private messages.
The User is responsible for content they publish or send and must not make available third-party photos, videos, audio, personal data or content without permission. Illegal, abusive, exploitative, fraudulent content or content that violates third-party rights may result in removal, blocking, suspension, Account Deletion and reporting to authorities when required.
Not all information provided to Neenbo is public. Profile data such as display name, age, city, gender, bio, photos, videos and content published in public or semi-public areas may be visible to authorized users depending on the feature used.
Private messages, voice messages and one-to-one conversations are not publicly displayed. They may be processed and stored for delivery, synchronization, security, reports, moderation, support, legal compliance and Service operation. Neenbo does not provide end-to-end encryption for private messages.
The User is responsible for content they publish or send and must not make available third-party photos, videos, audio, personal data or content without permission. Illegal, abusive, exploitative, fraudulent content or content that violates third-party rights may result in removal, blocking, suspension, Account Deletion and reporting to authorities when required.
5 - Authentication
Neenbo uses Firebase Authentication and supports authentication with Google and Facebook. The iOS version also includes Sign in with Apple. Neenbo does not receive the password for the Google, Facebook or Apple account.
Google: the App receives credentials or ID tokens required to authenticate the User with Firebase Authentication and create a Neenbo session.
Facebook: login uses the access token for authentication through Firebase Authentication. On iOS, Facebook Login requests public_profile and uses the received token. Neenbo does not use the Facebook Graph API to retrieve additional personal data from the Facebook profile.
Apple, on iOS: the App uses Sign in with Apple credentials and Firebase Authentication; before Account Deletion for Apple users, the App may request a fresh Apple authorization to revoke the token as required by the platform.
Neenbo uses Firebase Authentication and supports authentication with Google and Facebook. The iOS version also includes Sign in with Apple. Neenbo does not receive the password for the Google, Facebook or Apple account.
Google: the App receives credentials or ID tokens required to authenticate the User with Firebase Authentication and create a Neenbo session.
Facebook: login uses the access token for authentication through Firebase Authentication. On iOS, Facebook Login requests public_profile and uses the received token. Neenbo does not use the Facebook Graph API to retrieve additional personal data from the Facebook profile.
Apple, on iOS: the App uses Sign in with Apple credentials and Firebase Authentication; before Account Deletion for Apple users, the App may request a fresh Apple authorization to revoke the token as required by the platform.
6 - Push notifications
Neenbo uses Firebase Cloud Messaging for tokens and notification delivery. On iOS, notifications also pass through the Apple Push Notification Service. The App may store notification tokens to notify the User about messages, matches, visits, groups and other relevant events.
Notifications depend on system permission and App settings. The User may deny, revoke or change notification permissions and preferences in device settings and in the App where available.
Neenbo uses Firebase Cloud Messaging for tokens and notification delivery. On iOS, notifications also pass through the Apple Push Notification Service. The App may store notification tokens to notify the User about messages, matches, visits, groups and other relevant events.
Notifications depend on system permission and App settings. The User may deny, revoke or change notification permissions and preferences in device settings and in the App where available.
7 - Photos, videos, audio and messages
Profile photos, conversation images, verification selfies, videos, text messages, voice messages and other submitted content may be stored on Neenbo servers and file infrastructure for display, delivery, verification, security and moderation.
The microphone is used to record voice messages when the User chooses that feature. The camera is used on iOS for verification selfies and may be used in equivalent flows depending on the platform. Photo or media selection depends on system pickers and User action.
Profile photos, conversation images, verification selfies, videos, text messages, voice messages and other submitted content may be stored on Neenbo servers and file infrastructure for display, delivery, verification, security and moderation.
The microphone is used to record voice messages when the User chooses that feature. The camera is used on iOS for verification selfies and may be used in equivalent flows depending on the platform. Photo or media selection depends on system pickers and User action.
8 - Payments and subscriptions
Android - Google Play Billing: purchases and subscriptions are processed by Google Play. Neenbo may receive purchase tokens, product identifiers and status information required to validate the subscription in Neenbo systems and unlock benefits. Full card details are not received by Neenbo.
iOS - Apple App Store and StoreKit 2: purchases and subscriptions are processed by Apple. Neenbo may receive JWS/receipts, transaction identifiers, product, validity and status information required to validate or restore benefits. Full card details are not received by Neenbo.
Each store applies its own privacy policy, terms, purchase history, refund, cancellation and subscription controls.
Android - Google Play Billing: purchases and subscriptions are processed by Google Play. Neenbo may receive purchase tokens, product identifiers and status information required to validate the subscription in Neenbo systems and unlock benefits. Full card details are not received by Neenbo.
iOS - Apple App Store and StoreKit 2: purchases and subscriptions are processed by Apple. Neenbo may receive JWS/receipts, transaction identifiers, product, validity and status information required to validate or restore benefits. Full card details are not received by Neenbo.
Each store applies its own privacy policy, terms, purchase history, refund, cancellation and subscription controls.
9 - Advertising
The Android version uses Google AdMob to display advertisements. When ads are enabled in a distributed version, Google Mobile Ads/AdMob may process advertising, measurement, frequency, performance data and the Android Advertising ID (AAID), according to consent choices, Google account settings and system controls.
IDFA is Apple’s advertising identifier on iOS; Advertising ID or AAID is Android’s advertising identifier. The current iOS version does not use Google Mobile Ads, App Tracking Transparency, NSUserTrackingUsageDescription or IDFA.
The User can limit ad personalization in platform controls. The availability of personalized or non-personalized advertising may vary by country, consent, age, device settings, App version and Service Provider policies.
The Android version uses Google AdMob to display advertisements. When ads are enabled in a distributed version, Google Mobile Ads/AdMob may process advertising, measurement, frequency, performance data and the Android Advertising ID (AAID), according to consent choices, Google account settings and system controls.
IDFA is Apple’s advertising identifier on iOS; Advertising ID or AAID is Android’s advertising identifier. The current iOS version does not use Google Mobile Ads, App Tracking Transparency, NSUserTrackingUsageDescription or IDFA.
The User can limit ad personalization in platform controls. The availability of personalized or non-personalized advertising may vary by country, consent, age, device settings, App version and Service Provider policies.
10 - Analytics, crashes and infrastructure
Android: the Android version uses Firebase Analytics, Firebase Crashlytics, Firebase Cloud Messaging, Firebase Realtime Database, Firebase Authentication, Google Play Billing, Facebook Login, Google Identity/Credential Manager, Google Play Integrity and Google AdMob.
iOS: the iOS version uses Firebase Authentication, Firebase Messaging, Firebase Realtime Database, Google Sign-In, Facebook Login, Sign in with Apple, StoreKit 2 and APNs. The current iOS version does not use Firebase Analytics, Firebase Crashlytics, Google Mobile Ads or IDFA.
Firebase Analytics, in the Android version, may process usage events, app opens, sessions, device information and aggregated metrics. Crashlytics, in the Android version, processes crash data, technical logs, app state, device and operating system information for diagnostics. Crashlytics is not used to collect IDFA or precise location.
Neenbo systems use proprietary APIs and services, media storage, Firebase Admin/Identity Toolkit, and notification delivery services to operate specific features.
Android: the Android version uses Firebase Analytics, Firebase Crashlytics, Firebase Cloud Messaging, Firebase Realtime Database, Firebase Authentication, Google Play Billing, Facebook Login, Google Identity/Credential Manager, Google Play Integrity and Google AdMob.
iOS: the iOS version uses Firebase Authentication, Firebase Messaging, Firebase Realtime Database, Google Sign-In, Facebook Login, Sign in with Apple, StoreKit 2 and APNs. The current iOS version does not use Firebase Analytics, Firebase Crashlytics, Google Mobile Ads or IDFA.
Firebase Analytics, in the Android version, may process usage events, app opens, sessions, device information and aggregated metrics. Crashlytics, in the Android version, processes crash data, technical logs, app state, device and operating system information for diagnostics. Crashlytics is not used to collect IDFA or precise location.
Neenbo systems use proprietary APIs and services, media storage, Firebase Admin/Identity Toolkit, and notification delivery services to operate specific features.
11 - Sharing and Service Providers
Data may be shared with Service Providers used for infrastructure and hosting, authentication, notifications, analytics, crash diagnostics, media storage, purchase processing and validation, Android advertising where enabled, support, security, fraud prevention, moderation and legal compliance.
Service Providers that process data on behalf of Neenbo must use the data only for the contracted services and apply protection compatible with this Policy and applicable law. We may also share data with public authorities, courts or third parties when required by law, a valid order, protection of rights, User safety or abuse investigations.
Neenbo does not sell Personal Data.
Data may be shared with Service Providers used for infrastructure and hosting, authentication, notifications, analytics, crash diagnostics, media storage, purchase processing and validation, Android advertising where enabled, support, security, fraud prevention, moderation and legal compliance.
Service Providers that process data on behalf of Neenbo must use the data only for the contracted services and apply protection compatible with this Policy and applicable law. We may also share data with public authorities, courts or third parties when required by law, a valid order, protection of rights, User safety or abuse investigations.
Neenbo does not sell Personal Data.
12 - Device permissions
Permissions depend on the platform, system version and feature used. The Android version requests Internet, notifications and microphone. The iOS version declares camera use for verification selfies and microphone use for voice messages, plus notifications through APNs/FCM.
The User can change camera, microphone, notification and photo or media access in device settings. The current Android and iOS versions do not request native location permission or generic storage permission.
Permissions depend on the platform, system version and feature used. The Android version requests Internet, notifications and microphone. The iOS version declares camera use for verification selfies and microphone use for voice messages, plus notifications through APNs/FCM.
The User can change camera, microphone, notification and photo or media access in device settings. The current Android and iOS versions do not request native location permission or generic storage permission.
13 - Retention, inactivity and Account Deletion
We retain data while the Account is active and for as long as needed to provide the Service, comply with legal obligations, resolve disputes, prevent fraud and abuse, maintain security, validate payments, operate backups and preserve technical records.
The User can delete the Account in the App by opening Profile, Settings and Delete Account. A public Account Deletion instructions page is also available at https://www.neenbo.com/delete. Requests may also be made through in-app support or by email. Uninstalling the App does not delete the Account or all data.
After deletion, the profile will no longer be available on Neenbo and the account will no longer operate as an active account. Some limited records may be retained for up to 6 months when necessary for security, fraud and abuse prevention, payments and subscriptions, disputes, reports, moderation, legal obligations, technical support, or backups. After this period, the remaining data will be deleted or anonymized, unless a longer retention period is required by law.
Requests related to remaining data after deletion may be sent through in-app support or the emails listed in this Policy. Handling may depend on identity verification and applicable legal or technical limitations.
We retain data while the Account is active and for as long as needed to provide the Service, comply with legal obligations, resolve disputes, prevent fraud and abuse, maintain security, validate payments, operate backups and preserve technical records.
The User can delete the Account in the App by opening Profile, Settings and Delete Account. A public Account Deletion instructions page is also available at https://www.neenbo.com/delete. Requests may also be made through in-app support or by email. Uninstalling the App does not delete the Account or all data.
After deletion, the profile will no longer be available on Neenbo and the account will no longer operate as an active account. Some limited records may be retained for up to 6 months when necessary for security, fraud and abuse prevention, payments and subscriptions, disputes, reports, moderation, legal obligations, technical support, or backups. After this period, the remaining data will be deleted or anonymized, unless a longer retention period is required by law.
Requests related to remaining data after deletion may be sent through in-app support or the emails listed in this Policy. Handling may depend on identity verification and applicable legal or technical limitations.
14 - User rights
Depending on applicable law, the User may request access, correction, deletion, copy, portability, withdrawal of consent, restriction, objection or review of certain data processing activities.
Some data can be corrected directly in the App, such as name, bio, gender, date of birth, photos, city, filters and preferences. Other requests must be sent to support. We may refuse, limit or delay requests when necessary to comply with law, protect third-party rights, prevent fraud, preserve security or verify identity.
Depending on applicable law, the User may request access, correction, deletion, copy, portability, withdrawal of consent, restriction, objection or review of certain data processing activities.
Some data can be corrected directly in the App, such as name, bio, gender, date of birth, photos, city, filters and preferences. Other requests must be sent to support. We may refuse, limit or delay requests when necessary to comply with law, protect third-party rights, prevent fraud, preserve security or verify identity.
15 - International transfers
Neenbo, its servers, app stores and Service Providers may operate or store data in Brazil, the United States and other countries. The laws of those countries may differ from the laws where the User resides.
Where an international transfer occurs, we use reasonable measures and appropriate contracts, controls or legal bases where applicable. Processing location is not determined simply by the location identified by the device.
Neenbo, its servers, app stores and Service Providers may operate or store data in Brazil, the United States and other countries. The laws of those countries may differ from the laws where the User resides.
Where an international transfer occurs, we use reasonable measures and appropriate contracts, controls or legal bases where applicable. Processing location is not determined simply by the location identified by the device.
16 - Security
Neenbo uses reasonable technical and organizational measures, such as authentication, tokens, access controls, technical monitoring, report review, security records, abuse blocking, purchase validation and platform resources to protect data.
No transmission or storage method is 100% secure. We do not promise absolute security. If the User identifies misuse, a security issue or unauthorized access, they should contact support immediately.
Neenbo uses reasonable technical and organizational measures, such as authentication, tokens, access controls, technical monitoring, report review, security records, abuse blocking, purchase validation and platform resources to protect data.
No transmission or storage method is 100% secure. We do not promise absolute security. If the User identifies misuse, a security issue or unauthorized access, they should contact support immediately.
17 - Minors
Neenbo is not intended for anyone under 18 years old. The Terms of Use and CSAE Policy indicate a minimum age of 18 to create an account and use the Service.
If we identify an account belonging to someone under the minimum age, we may block, suspend or delete the Account and remove associated data, while preserving records needed for safety, reporting, investigation or legal obligations. Suspected use by minors may be reported to support@neenbo.com.
Neenbo is not intended for anyone under 18 years old. The Terms of Use and CSAE Policy indicate a minimum age of 18 to create an account and use the Service.
If we identify an account belonging to someone under the minimum age, we may block, suspend or delete the Account and remove associated data, while preserving records needed for safety, reporting, investigation or legal obligations. Suspected use by minors may be reported to support@neenbo.com.
18 - Changes to this Policy
We may update this Policy to reflect changes in the App, platforms, Service Providers, legal requirements or security practices.
Material changes may be communicated by publishing the new version on this page, through an in-app notice, notification or another appropriate method. Use of Neenbo after the update will be subject to the new version, as permitted by applicable law.
We may update this Policy to reflect changes in the App, platforms, Service Providers, legal requirements or security practices.
Material changes may be communicated by publishing the new version on this page, through an in-app notice, notification or another appropriate method. Use of Neenbo after the update will be subject to the new version, as permitted by applicable law.