Account Deletion Terms & Condition

Last Updated:  o4th April 2024

Calorie Guard values the privacy and data protection rights of its users. This Data Deletion Policy outlines the terms and conditions regarding the deletion of user data upon request. By using the Calorie Guard app, you agree to these terms.

1. Information Collected:

a. Calorie Guard collects the following major types of information from users:

1. Email address

2. First name and last name (Full Name)

3. Phone number

4. Location

5. Body Composition (age, height, weight, physical activity level)

6.User interaction time (total time spend on the app daily by basis)

b. Third party data collection

1. Firebase SDK:  

Firebase SDK collects various types of data depending on the specific services and features you use in your app. Some common types of data collected through Firebase SDK include:

·       **Analytics Data**: Firebase Analytics collects user engagement data such as user interactions, screen views, events triggered, and user demographics (if enabled).

·       **Crash Reporting Data**: Firebase Crashlytics collects data related to app crashes and errors, including stack traces, device information, and user actions leading up to the crash.

·       **Performance Monitoring Data**: Firebase Performance Monitoring collects data related to app performance, including network requests, app startup time, and rendering issues.

·       **Cloud Firestore and Realtime Database Data**: If you use Firebase's database services (Firestore or Realtime Database), data related to user-generated content, user profiles, app settings, etc., can be collected.

·       **Authentication Data**: Firebase Authentication collects data related to user authentication and identity management, including user sign-ins, sign-ups, and authentication methods used.

·       **Cloud Messaging Data**: Firebase Cloud Messaging collects data related to push notifications sent to users, including delivery status, user interaction with notifications, and device tokens.

·       **Remote Config Data**: Firebase Remote Config collects data related to app configuration changes and experiments, including user segmentation data and experiment results.

2. Google Play Services SDK:

Google Play Services SDK collects various types of data to enhance user experience and provide services to developers. Some of the data collected through Google Play Services SDK include:

·       **Device Information:** Information about the user's device such as model, manufacturer, operating system version, hardware details, and unique device identifiers (e.g., IMEI, Android ID).

·       **Location Data:** Google Play Services collects location data through various methods such as GPS, Wi-Fi, and cell tower triangulation. This data is used for location-based services like maps, location-based ads, and other location-related features.

·       **Usage Data:** Information about how users interact with apps, including app usage statistics, crash reports, performance metrics, and user engagement data. This helps developers improve their apps and provides insights into user behavior.

·       **Google Account Information:** If the user is signed in with a Google Account, Google Play Services may collect information related to the account, such as email address, profile information, and account activity.

·       **Network Information:** Data related to network connections, such as Wi-Fi network details, cellular network information, IP address, and network status (e.g., online/offline).

·       **App Data:** Information about installed apps, updates, app permissions, and app-related data (e.g., storage usage, app settings).

·       **Analytics and Advertising Data:** Google Play Services may collect data for analytics purposes, such as user demographics, interests, and ad interactions. This data helps in targeting ads and measuring ad performance.

3. Glide:

Glide is a popular app-building platform that allows users to create mobile apps without writing code. The data collected through Glide depends on the specific functionalities and features integrated into the app. However, some common types of data that can be collected through Glide apps include:

·       **User Input**: This includes data entered by users through text fields, checkboxes, radio buttons, dropdown menus, etc. For example, user registration information, form submissions, survey responses, etc.

·       **Location Data**: If the app includes location-based services, it can collect GPS coordinates or location information based on user permissions.

·       **Media Uploads**: Users can upload images, videos, audio files, and other media through Glide apps. These files are stored in the app's database or linked cloud storage.

·       **Analytics**: Glide can collect analytics data such as app usage metrics, user interactions, screen views, session durations, and more to provide insights into app performance.

·       **User Authentication Data**: If the app includes user authentication features, data related to user accounts, login/logout activities, password resets, etc., can be collected.

·       **Third-Party Integrations**: Data from third-party services or APIs integrated into the app, such as social media platforms, payment gateways, databases, etc.

·       **Custom Data**: App creators can define custom data structures and collect any other type of data relevant to their app's functionality and purpose.

4. AI Client Generative AI:

                                             AI Client Generative AI is a broad term that can refer to various AI systems designed to generate data or content. The specific data collected through such systems depend on their purpose and design. Here are some examples of data that can be collected through AI Client Generative AI:

·       **Text Data**: This includes generated text such as articles, stories, product descriptions, chatbot responses, and more.

·       **Image Data**: Generative AI can create images, illustrations, artworks, and designs.

·       **Audio Data**: AI systems can generate music, voiceovers, sound effects, and speech.

·       **Video Data**: Some AI systems can generate video content, animations, and visual effects.

5. Reactive Streams:

Reactive Streams is a programming paradigm and specification that deals with asynchronous stream processing of data with non-blocking backpressure. The data collected through Reactive Streams

·       **Stream of Events:** Reactive Streams collect a stream of events or data items. These events could be sensor readings, user inputs, database records, or any other type of data that is produced over time.

·       **Backpressure Information:** Reactive Streams also collect information about backpressure, which refers to the mechanism used to handle situations where a downstream component is not able to process data as fast as it is being produced by an upstream component. Backpressure information helps in controlling the flow of data and avoiding overload or resource exhaustion.

·       **Error Handling Information:** Reactive Streams collect information about errors that may occur during stream processing. This includes exceptions, error codes, or any other type of error information that helps in diagnosing and handling issues within the stream processing pipeline.

·       **Completion Signals:** Reactive Streams also collect completion signals, which indicate the end of the stream or a particular stage of processing. This information is useful for determining when to perform cleanup tasks or when to initiate further processing based on the completion of a stream.

6. Gson: 

Gason is a Java library developed by Google that is used to convert Java objects to JSON (JavaScript Object Notation) and vice versa. When using Gson, various types of data can be collected and manipulated:

·       **Serialization**: Gson collects data from Java objects and converts them into JSON format. This includes collecting fields, methods, and annotations from Java classes to determine how to represent the data in JSON.

·       **Deserialization**: Gson collects JSON data and converts it into Java objects. This involves parsing the JSON structure and mapping its elements to corresponding fields in Java objects.

·       **Data Types**: Gson handles various data types such as primitive types (int, float, boolean, etc.), arrays, collections (List, Set, Map), custom objects, nested objects, and complex data structures.

·       **Annotations**: Gson can collect data from annotations such as `@SerializedName` to specify custom field names in JSON, `@Expose` to include or exclude fields during serialization/deserialization, and `@Since`/`@Until` to version control JSON output.

·       **Customization**: Gson allows customization through `TypeAdapter` and `JsonSerializer/JsonDeserializer` interfaces, enabling users to define custom serialization and deserialization logic for specific data types.

7. Integrity Play SDK: 

Integrity Play SDK is a tool used for monitoring and ensuring the integrity of digital assets, such as video content or gameplay in applications. The data collected through Integrity Play SDK typically includes:

·       **User Interactions:** This includes information about how users interact with the digital content, such as clicks, taps, swipes, and other actions within the application.

·       **Usage Patterns:** Data about how often and for how long users engage with the content can be collected, providing insights into user behavior and preferences.

·       **Performance Metrics:** The SDK may gather data related to the performance of the application, such as load times, latency, and responsiveness, to identify any issues affecting user experience.

·       **Device Information:** Information about the user's device, such as device type, operating system version, screen size, and hardware capabilities, may be collected for optimization and compatibility purposes.

·       **Security Events:** The SDK can track security-related events, such as unauthorized access attempts or suspicious activities, to enhance the overall security posture of the application.

·       **Content Integrity:** Integrity Play SDK specifically focuses on ensuring the integrity of digital assets, so it may collect data related to the authenticity, integrity, and verifiability of digital content, such as videos or game assets.

2. Data Deletion Process:

When a user submits the Account Deletion Form within the Calorie Guard app, the following information will be deleted:

1. First name and last name (Full Name)

2. Phone number

3. Location

4. Body Composition (age, height, weight, physical activity level)

5. Third party data collection

•   Firebase SDK

•   Google Play Services SDK

•  Glide

•  AI Client Generative AI

•   Reactive Stream

•   Gson

• Integrity Play SDK

3. Retained Data:

After the deletion process, Calorie Guard will retain the following information:

1. Email address

2. User interaction time (total time spend in the app on daily basis)

4. Prohibited Use of Retained Data:

The retained data (email address and in-app activity) will not be used for any purposes, including but not limited to marketing, analysis, or research activities. Calorie Guard ensures that this data will remain inactive and inaccessible for any activities.

5. User Responsibility:

Users are responsible for ensuring the accuracy and completeness of the data they provide. Calorie Guard is not liable for any inaccuracies or incompleteness in user-provided data.

6. Data Security:

Calorie Guard employs industry-standard security measures to protect user data from unauthorized access, disclosure, alteration, or destruction. However, no method of transmission over the internet or electronic storage is 100% secure, and Calorie Guard cannot guarantee absolute security.

7. Compliance with Laws:

Calorie Guard complies with applicable data protection laws and regulations, including but not limited to the General Data Protection Regulation (GDPR) and the California Consumer Privacy Act (CCPA).

8. Changes to the Policy

Calorie Guard reserves the right to modify or update this Data Deletion Policy at any time. Users will be notified of any changes through the app or other appropriate channels.

9. Contact Us:

If you have any questions or concerns about this Data Deletion Policy or the handling of your data, please contact us at calorieguard.in@gmail.com

10. Acceptance of Terms:

By using the Calorie Guard app and submitting the Account Deletion Form, you acknowledge that you have read, understood, and agreed to this Data Deletion Policy.