Your privacy.
Your choices.

This policy describes personal data handling for Comments for Photos, also branded Comment Pro (Android package: com.comment.pro), provided by Rs Developers. Privacy contact: techrohitrs@gmail.com.

The app provides suggested comments, search and filters, copying, editing, sharing, Saved and Recent items, and optional notifications. It does not require an app account or an Instagram, Facebook or WhatsApp login. It does not access your social-media accounts or photo library to generate comments.

Features and services vary by app version. This policy describes the Comment Pro Flutter update and the services available in versions that include them. A description of an optional service does not mean it is enabled on every installation. Contact us if you need information about an older version.

Saved comment IDs, recent-copy history, preferences, introductory-screen status, reminder time and notification choices are stored in app storage on your device. Recent history is limited to the latest 50 entries in this update. We do not operate a cloud-sync service for these items.

Your selected age group and diagnostics choice are stored locally. We use them to control feature eligibility. We do not collect your date of birth or send the age-group selection as an Analytics event. If you change from an adult to a younger age group, ads and diagnostics are disabled locally. Remote notification cleanup can require internet and may be retried; Android notification settings can stop visible notifications while cleanup is pending.

Search queries and edits are processed locally in this update. Our application code does not send search queries, edited comment text, clipboard contents, or the text of your selected comments as Analytics event parameters. When you tap Copy, the selected text is written to the Android clipboard. Other apps and the operating system handle clipboard access under their own controls.

When you tap Share, the text you choose is passed to the Android sharing interface and the destination app you select. That recipient handles the text under its own privacy practices. We do not receive your destination-app messages or contacts.

Android device backup or device-transfer services may copy app preferences depending on your system settings. This is separate from an app-operated sync service.

Ad-enabled builds use Google AdMob Native ads. Google Mobile Ads may collect and share IP addresses (including inferred approximate location), app and ad interactions, technical diagnostics, and device or advertising identifiers for advertising, measurement and fraud prevention. This does not require the app to request GPS permission.

Consent and available ad processing depend on your location, choices and Google requirements. Ad-enabled versions use Google’s User Messaging Platform to determine when privacy messages and choices are required. Where available, use the app’s Ad privacy screen to review or change advertising choices. When a privacy-options form is required, you can reopen it there. Android also offers advertising-ID controls; their names and availability vary by device.

Non-personalized or limited ads do not necessarily involve zero data processing. Google may still process data necessary for permitted ad delivery, measurement and fraud prevention. Declining consent does not prevent access to locally stored comments.

For users who select the adult age group, this update requests non-personalized Native ads after the advertising privacy setup permits requests. Ads are disabled for the 13–17 group and while an age group has not been selected. Non-personalized ads can still use identifiers for frequency capping and reporting, and consent may still be required for storage or access. Google’s separate practices are described in its Privacy Policy and advertising information.

Where enabled, Google Analytics for Firebase records feature-use events such as copying a comment, adding a favorite, opening a feature or changing reminder settings. SDK-generated app-instance identifiers, device/app information and usage information may accompany events. We do not assign a personal user ID or send your email address as an Analytics event parameter.

Where enabled, Firebase Crashlytics processes crash reports, stack traces, diagnostic identifiers and device/app details to identify and fix failures. Firebase Remote Config can provide notification-invitation wording and processes installation information when fetching settings.

For people who select the 18-or-older age group, usage and crash diagnostics are optional and off by default. If you enable Share usage and crash diagnostics in Privacy settings, Analytics and Crashlytics collection is enabled. You can switch this off there later. Advertising choices and diagnostics are separate purposes. The public release uses locally bundled notification-invitation text and does not fetch Remote Config. Remote Config inspection is limited to internal test builds.

Read Firebase privacy information for service-specific processing. We will update this policy and the app’s disclosures and controls when data practices change, and obtain consent where required before enabling additional processing.

Daily reminders are optional local notifications scheduled on your device using your selected time and device timezone. They do not require sending the reminder time to a remote scheduling server. You can turn them off in the app or control notification permission in Android Settings.

Remote App Updates, when available and enabled by you, use Firebase Cloud Messaging. Google processes installation and messaging identifiers to deliver notifications. Turning App Updates off stops the app’s update-topic subscription; the operation may require an internet connection. Disabling Android notification permission stops visible notifications but is not a request to erase all service data.

Remote App Updates are available only after an adult explicitly enables them. An earlier internal-test subscription is not treated as permission for production updates. You can turn updates off from App Updates settings; remote subscription cleanup can require an internet connection. We do not display messaging installation identifiers in the released app.

If you contact us, we receive your email address and any information or attachments you choose to send. Please avoid sending passwords, private messages or unrelated personal information. We use support information to answer your request, investigate issues and handle privacy concerns.

Data may be processed by Google and its service providers for the services described above, by an email provider when you contact us, and by an external app or website you deliberately open. We may disclose relevant information where legally required or to address fraud, security incidents or valid legal claims. We do not sell a customer-contact list. Advertising-related disclosures to Google are described separately above.

Providers may process information outside your country. Applicable provider terms and safeguards govern those transfers. A policy webpage may also generate hosting access logs or use the hosting platform’s technologies; these are distinct from app activity.

Local app preferences remain until removed or replaced through app actions or Android storage controls, subject to Android backup and restore. Removing a Saved item changes its local saved status. Recent history is overwritten as newer entries exceed its limit. Clearing app storage removes local app preferences and history and is irreversible; it does not erase data already processed by Google or another app.

For data already sent to Google services, service-specific retention applies. Google states that Crashlytics retains crash information and related identifiers for 90 days before removal begins. For Cloud Messaging and Remote Config, installation IDs can remain until a deletion request is made through the relevant API; subsequent removal from live and backup systems can take up to 180 days. These are not promises of immediate deletion when you switch notifications off.

For the Firebase-linked Analytics property, event-data retention is configured to 2 months and user-data retention to 14 months. Reset on new activity is enabled, so new activity can extend the retention of a user identifier. These settings do not impose the same expiry on standard aggregated reports. Advertising data is retained according to Google’s applicable policies and terms.

Support correspondence is retained for as long as needed to answer your enquiry, resolve related issues and meet applicable legal or security obligations. We consider whether a request remains open, whether follow-up is reasonably needed and whether a legal obligation requires continued retention. When these purposes no longer apply, we delete or anonymize information we control. Contact techrohitrs@gmail.com to request access, correction or deletion. We may need limited information to verify a request; do not send identity documents unless specifically necessary and requested.

Because the app has no user account and does not tie local activity to your email address, we may be unable to associate an email request with a particular installation. We will explain available steps and any legal or technical limits. Uninstalling the app does not itself instruct every service provider to erase historical data.

You can use local comment features without enabling reminders or remote updates. You can change notification choices and, when required and available, advertising choices using the app and Android settings. Withdrawal affects subsequent processing and does not automatically erase earlier records.

Depending on your location and the laws that apply, you may have rights to access information, correct it, request deletion, withdraw consent, object to or restrict processing, obtain a copy, or raise a privacy grievance. Send requests to the privacy contact above. Where applicable, you may also complain to the relevant data-protection authority. Requests are handled within the periods required by applicable law.

Where data-protection law requires a legal basis, we rely on consent for processing that requires it, including applicable advertising storage or access, and on legitimate interests where permitted for responding to support enquiries, protecting the app and investigating faults. We may also process information to meet legal obligations. You can contact us to ask which basis applies to a particular use, withdraw consent or object where applicable.

We rely on Android app isolation and service-provider security controls, including encrypted network transport for the Google services described above. No storage or transmission system is guaranteed completely secure.

The app is intended for people aged 13 and older, including users aged 13–17. It is not directed to children under 13. The app asks you to select an age group without requesting a date of birth. Users who select Under 13 cannot continue. For the 13–17 group, local comment features and local daily reminders are available, while advertising, usage/crash diagnostics and remote app updates are disabled. Selecting an adult age group does not automatically enable diagnostics or remote updates. Advertising privacy choices are requested separately where required. Age-of-consent and parental-permission requirements vary by country.

If you believe a child’s information has been processed inappropriately, contact us so we can investigate and take the steps required by applicable law.

We will update this policy when our data practices change, show the revision date, and provide additional notice or obtain a new choice when required. A privacy-policy update does not itself grant consent for a new processing purpose.

Rs Developers prohibits child sexual abuse and exploitation (CSAE), including grooming, sextortion, trafficking, sexual exploitation of minors and child sexual abuse material (CSAM). These standards apply to Comments for Photos / Comment Pro and associated support communications.

The app provides curated text suggestions. It does not provide user accounts, in-app chat, public user posts or a service for uploading photos or other media. We do not permit use of the app or our support channels to promote, request, distribute or facilitate CSAE or CSAM.

Use Report a concern in the app’s Privacy screen, or contact techrohitrs@gmail.com, our child safety and support contact. This reporting option is also available on the age-restriction screen. Describe the issue and identify the relevant comment if possible. Do not send or forward illegal imagery or unnecessary personal information. A parent or guardian can help a child report a concern.

We assess reports, remove or correct unsafe material within our control, and take appropriate steps to prevent further misuse. Where we become aware of CSAM, we address it within services we control and follow applicable legal reporting obligations, including reporting to the appropriate regional authority or reporting organisation where required. We cooperate with lawful child safety investigations. We do not promise immediate responses or emergency assistance through email.