1. Introduction

Welcome to Sankalp Diary, a productivity and planning application developed by Cairo Infotech Private Limited ("we", "us", "our", or the "Developer").

We respect your privacy and are committed to explaining how information may be collected, processed, stored, used, disclosed, and deleted when you use our application.

Sankalp Diary is designed to help users organize tasks, manage goals, schedule reminders, maintain routines, use focus-related features, and review personal progress.

This Privacy Policy describes our current practices based on the features and services represented here. Actual data practices depend on the application's implemented code, permissions, configuration, and third-party software development kits.

Please read this policy carefully before using the application. Where applicable law requires additional notice or consent, that requirement remains applicable.

2. Scope and Applicability

This Privacy Policy applies to the Sankalp Diary Android application and related services operated by Cairo Infotech Private Limited, to the extent described in this policy.

It covers Google Sign-In, Firebase Authentication, productivity information, reminders, device permissions, technical operations, and any future payment or advertising services that are actually introduced.

This policy does not automatically describe the independent practices of third-party services or external websites. Those services may have their own privacy policies and terms.

If a feature described as future functionality has not yet been implemented, it should not be understood as currently available.

3. Information We May Process

The information involved depends on how you use the application, which features are enabled, and which permissions or third-party services are active.

3.1 Google Account and Authentication Information

When you use Google Sign-In, information may be processed to authenticate you and maintain the associated sign-in session.

Depending on the configuration, this may include:

• Your name or display name.
• Your Google account email address.
• Your profile image or its URL, if requested and used.
• A Firebase Authentication user identifier (UID).
• Authentication status and related technical information.

The actual information available to our application depends on the permissions requested, the information returned by Google, and the implemented sign-in flow.

3.2 Tasks, Goals, and Productivity Information

Depending on the features you use, you may enter information such as:

• Daily, weekly, and monthly goals.
• Task titles, descriptions, dates, and schedules.
• Task completion status and progress.
• Milestones, achievements, or streaks, if implemented.
• Personal notes or reasons for incomplete tasks, if available.
• Reminder preferences and routine schedules.
• Records used to calculate productivity reports.

This information may be used to provide the productivity features you request. The storage location and retention of each type of information depend on the actual implementation of the application.

Please avoid entering passwords, payment card details, government identification numbers, or other highly sensitive information into task descriptions or notes unless a feature explicitly requires and securely supports such information.

3.3 Reminders, Alarms, and Focus Preferences

If you use reminder, alarm, sleep routine, or focus features, the application may process schedules, reminder times, notification preferences, and related settings to provide those functions.

3.4 Technical and Diagnostic Information

Depending on the libraries and services actually integrated into the application, technical information may be processed for troubleshooting, security, and reliability. Examples may include application version, operating system information, crash diagnostics, and performance-related records.

This policy does not assert that every example above is collected. The actual data practices depend on the enabled services and their configurations.

4. Google Sign-In and Firebase Authentication

Sankalp Diary currently supports Google Sign-In through Firebase Authentication.

The application does not currently provide a separate email-and-password registration form. However, authentication through Google may create or maintain an authentication record or user identifier in Firebase Authentication.

Google Sign-In is used to verify your identity and support features that require an authenticated session. It does not, by itself, mean that every future account, subscription, payment, or profile-management feature is currently available.

4.1 Firebase Processing

Firebase Authentication may process authentication identifiers, account information, and technical data necessary to provide the authentication service. The exact processing depends on the implemented configuration and the applicable Firebase terms.

4.2 Google Privacy Information

Learn more about how Google handles information in its services by reviewing Google's Privacy Policy:

Google Privacy Policy

Information about Google Identity services is available at: Google Identity Documentation

Firebase Authentication documentation: Firebase Authentication

5. Local Storage and Online Processing

5.1 Information Stored on Your Device

Certain productivity records, reminders, preferences, and schedules may be stored locally on your device to provide application functionality.

Locally stored information may be removed if you clear the application's storage, uninstall the application, reset your device, or use a relevant deletion feature. Data that is not backed up may not be recoverable.

5.2 Information Processed Online

Google Sign-In and Firebase Authentication require online communication with the relevant service. Information necessary for authentication may therefore be processed by Firebase and Google.

The presence of Firebase Authentication does not necessarily mean that all tasks, goals, or personal notes are uploaded to a cloud database.

Any future cloud synchronization, backup, or online storage feature must be described according to its actual implementation before being represented as available to users.

6. Permissions, Notifications, and Focus Features

The application may request Android permissions necessary for features that are actually implemented. The specific permissions depend on the application version, Android version, and device configuration.

• Notifications: To display reminders and other notifications where supported.
• Exact alarms: If exact scheduling is needed for an implemented alarm feature and the applicable Android rules require authorization.
• Do Not Disturb access: If an implemented focus feature offers DND control and you explicitly grant the required system access.
• Network access: To communicate with Google Sign-In, Firebase, and other enabled online services.

Additional special permissions, such as usage access, should only be requested if an actual feature requires them and the request is appropriately explained.

You can manage available permissions through Android settings. Denying a permission may limit the feature that depends on it.

Android's Do Not Disturb behavior depends on the operating system, device manufacturer, user settings, and applicable exceptions. Sankalp Diary does not guarantee that every sound, notification, or activity from other applications can always be blocked.

7. How We Use Information

Information may be processed for the following purposes, where relevant to an enabled feature:

• To authenticate users through Google Sign-In.
• To operate and maintain application functionality.
• To organize tasks, goals, schedules, and reminders.
• To display progress and productivity reports.
• To maintain application reliability and security.
• To investigate technical errors and troubleshoot problems.
• To prevent abuse and unauthorized activity.
• To respond to user support and privacy requests.
• To comply with applicable legal obligations.

We aim to process information only for relevant purposes and in a manner consistent with applicable law and the actual operation of the application.

8. Information Sharing and Disclosure

We do not design Sankalp Diary for the sale of personal information. However, information may be processed by third parties when necessary to provide services, maintain security, or comply with applicable law.

8.1 Google and Firebase

Google and Firebase may process information needed to provide Google Sign-In and Firebase Authentication. Their processing is subject to the relevant service terms and privacy documentation.

8.2 Service Providers

If additional technical providers are integrated in the future, they may process information needed to provide their specific services, subject to applicable arrangements and legal requirements.

8.3 Legal Requirements and Protection

Information may be disclosed when required by law, in response to valid legal process, or where disclosure is reasonably necessary to protect rights, safety, security, or prevent unlawful activity, subject to applicable legal requirements.

8.4 No Unnecessary Sharing

We aim to limit disclosures to information relevant to the applicable purpose. The actual handling of information by third-party services is governed by their own terms and privacy practices.

9. Advertising and AdMob

We may introduce advertising in a future version of the application. If advertising is implemented, this policy and the relevant Google Play disclosures will be reviewed and updated to reflect the actual advertising SDK, data practices, consent requirements, and user choices.

If Google AdMob or another advertising service is integrated, the service may process information such as advertising identifiers, IP address, device or application information, ad impressions, interactions, fraud-prevention signals, or other technical data, depending on its configuration and applicable rules.

The actual information processed will depend on the SDK, consent status, regional requirements, and advertising settings in use at that time.

Google advertising information: Google Advertising Technologies

Where required, appropriate consent mechanisms and privacy choices must be implemented before relevant data processing takes place.

Future advertising features will be subject to applicable Google Play policies, advertising policies, and relevant privacy laws.

10. Future Payments, Razorpay, and Subscriptions

We may introduce paid plans in the future, including subscriptions that remove advertisements or provide additional application features.

Razorpay is being considered as a possible payment service provider. Any payment feature will be described according to the provider and payment method actually integrated when the feature becomes available.

10.1 Information That May Be Needed for Future Payments

If a payment feature is introduced, the information required may depend on the checkout flow, the payment provider, the selected payment method, and applicable legal requirements.

Depending on the implementation, this may include:

• Payment or transaction reference numbers.
• Selected plan or subscription details.
• Payment amount, currency, status, and timestamps.
• Contact information needed to complete or support a transaction.
• Subscription status, renewal information, or cancellation records, where applicable.
• Limited payment-related records needed for support, accounting, fraud prevention, or legal compliance.

This list describes possible future processing, not information currently collected for payments through Sankalp Diary.

10.2 Payment Security and Card Information

If Razorpay or another payment provider is integrated, payment information will be handled according to the actual checkout architecture and the provider's applicable security requirements and terms.

We will not claim that payment card details are collected or stored directly by the application unless the implemented payment flow actually does so. Sensitive payment credentials should not be entered into ordinary task descriptions, notes, or support messages.

10.3 Payment Provider Privacy Policy

If Razorpay is selected and integrated, users will be directed to the applicable official payment information and terms for the payment flow in use.

Razorpay website: https://razorpay.com/

Razorpay privacy information: https://razorpay.com/privacy/

The relevant provider's terms and privacy documentation should be verified again when the payment integration is implemented.

10.4 Subscriptions, Renewals, and Cancellations

If subscriptions are introduced, the applicable purchase flow will explain the plan price, duration, renewal terms, cancellation process, and refund conditions before purchase, as required by applicable law and platform policies.

Subscription management and cancellation procedures will depend on whether purchases are processed through Google Play Billing, Razorpay, or another supported payment arrangement.

This Privacy Policy does not itself establish a subscription, authorize a charge, or replace any separate payment terms, refund policy, or subscription agreement that may be required.

11. Data Retention

Information may be retained for as long as reasonably necessary to provide the relevant feature, maintain security, respond to requests, resolve disputes, or comply with applicable legal obligations.

• Local application data: May remain on your device until you delete it, clear application storage, uninstall the app, or another system process removes it.
• Authentication information: May be retained by Firebase according to the account state, service configuration, and applicable service rules.
• Technical records: May be retained by relevant services according to their settings and retention practices.
• Future payment records: If payments are introduced, relevant records may be retained for transaction support, accounting, fraud prevention, and legal compliance.

Retention periods may vary by information type and service provider. Some records may need to be retained for a legally required period even after a deletion request, where permitted or required by law.

12. Data Deletion and Authentication Requests

You may contact us to request information about your personal data or to request deletion, correction, or other action where available under applicable law.

Email: admin@cairoinfotech.com

Suggested email subject: Sankalp Diary - Privacy or Data Deletion Request

Please describe the request and, where necessary, provide the email address associated with Google Sign-In so that we can identify the relevant authentication record.

Do not send your password, one-time password (OTP), payment card security code, or other secret authentication credentials in your request.

We may request limited additional information when reasonably necessary to verify the request and protect the account against unauthorized deletion.

12.1 Local Data

Locally stored information may be managed using the deletion controls actually available in the application or the device's Android application settings. Removing local data does not automatically remove information held by an online service.

12.2 Firebase Authentication

Authentication-related deletion requests will be reviewed according to the actual Firebase implementation and applicable legal requirements. Deleting an authentication record may not automatically remove separate records held in other systems.

If account creation and account deletion functionality is introduced or required under applicable Google Play rules, the relevant in-app and external deletion mechanisms must be implemented and kept operational. This policy does not claim that a deletion feature exists unless it is actually available.

12.3 Future Payment Records

If payment services are introduced, deleting an application profile may not automatically delete transaction records maintained by a payment provider or records that must be retained for legal, tax, fraud-prevention, or accounting purposes.

13. Data Security

We aim to use reasonable technical and organizational safeguards to protect information against unauthorized access, misuse, alteration, or loss.

Security depends on the actual application design, authentication configuration, device security, network communications, third-party services, and operational practices.

No method of electronic storage or internet transmission can be guaranteed to be completely secure. We therefore cannot guarantee absolute security under every possible circumstance.

Users should protect their devices and Google accounts, use appropriate screen-lock protections, keep their software updated, and avoid sharing authentication credentials with others.

14. Children and Teenagers

We recognize the importance of protecting the privacy of children and teenagers who may use Sankalp Diary.

The application's target audience, data practices, advertising configuration, and available features must comply with applicable laws and Google Play requirements for the declared age groups.

Where applicable law or platform rules require parental consent, age-appropriate safeguards, restrictions on advertising, or additional disclosures, those requirements must be followed.

If you believe that personal information relating to a child has been processed inappropriately, please contact us at admin@cairoinfotech.com . We will review the request in accordance with applicable law and our actual technical capabilities.

15. Your Privacy Rights and Choices

Depending on your location and applicable law, you may have rights concerning your personal information, including the right to:

• Request information about the personal data processed about you.
• Request correction of inaccurate or incomplete information.
• Request deletion of information in applicable circumstances.
• Withdraw consent where processing is based on consent.
• Object to or restrict certain processing where applicable.
• Submit a privacy complaint through an available lawful process.

These rights depend on applicable law, the nature of the information, and the role of the relevant service provider. Some information may be retained where legally required or where a lawful exception applies.

To submit a request, contact admin@cairoinfotech.com .

15.1 Device and Account Choices

You can manage supported Android permissions through your device settings. Google account settings may also provide controls for your Google account and associated services.

Any future advertising or subscription feature must provide the user choices required by applicable laws and platform policies.

16. International Data Processing

Some service providers may operate infrastructure in multiple countries. If an enabled service processes or transfers information internationally, that processing will be subject to the provider's arrangements and applicable legal requirements.

Where required, appropriate safeguards for international transfers must be applied.

17. Third-Party Websites and Services

The application or its related website may contain links to third-party websites, documentation, or services. These third parties may operate independently and maintain their own privacy policies and terms.

We encourage users to review the relevant policies before using an external service. A link to a third-party website does not, by itself, mean that we control that website's data practices.

18. Changes to This Privacy Policy

We may update this Privacy Policy when the application changes, new services are integrated, legal requirements change, or additional disclosures become necessary.

The "Last Updated" date at the top of this page will be revised when the policy is materially updated.

Where a change requires additional notice or consent, the relevant notice or consent will be provided as required by applicable law.

Users should review this page periodically to remain informed about our privacy practices.

19. Legal Compliance and Privacy Complaints

This Privacy Policy is intended to be interpreted consistently with applicable Indian law and any other privacy or data-protection requirements that apply to the relevant processing.

Nothing in this policy is intended to exclude rights or obligations that cannot lawfully be excluded or limited.

If you have a privacy question, concern, or complaint, please contact us using the details provided below. Where applicable law requires additional grievance contact information or a designated officer, those details must be published and kept up to date.

20. Contact Us

For questions about this Privacy Policy, Google Sign-In, personal information, data deletion requests, or privacy concerns, please contact the Developer.

21. Official Privacy and Developer Resources

The following resources may help users understand the privacy practices of the third-party services referenced in this policy:

• Google Privacy Policy
• Firebase Authentication Documentation
• Google Play Console Help
• Google AdMob Help Center
• Razorpay Official Website
• Razorpay Privacy Information

Third-party resources and URLs may change. Please verify the applicable official documents when integrating or enabling a related service.