PRIVACY POLICY FOR CROPCARE AI

Last Updated: September 25, 2025
Version: 1.0.1+15

===============================================================================
YOUR PRIVACY IS IMPORTANT TO US
===============================================================================

This Privacy Policy explains how CropCare AI ("we," "our," or "us") collects, 
uses, and protects your information when you use our mobile application, web 
platform, and related services (collectively, the "Services"). CropCare AI 
operates across multiple platforms including mobile app (dev.hamez.cropcare), 
web platform (cropcare.hamez.dev), and backend API services.

1. INFORMATION WE COLLECT

1.1 PERSONAL INFORMATION
- Account information: Email address, encrypted password
- Profile data: Name, location/region (for pricing), preferences
- Contact information for customer support and communications
- OAuth2 authentication data (Google, Apple, GitHub) -> To be added 
- User-selected region for pricing tier determination (developed/underdeveloped)
- Organization membership and role information (for team features)

1.2 CROP AND IMAGE DATA
- Plant and crop photos you upload for AI analysis
- Analysis results, diagnoses, and treatment recommendations
- GPS location data (optional, if enabled) for environmental context
- Image metadata: timestamps, device information, photo quality metrics
- Analysis history and user-generated notes or tags
- Treatment effectiveness feedback and follow-up data

1.3 TECHNICAL AND DEVICE INFORMATION
- Device identifiers: Device model, operating system version, unique device ID
- App version, installation date, and usage statistics
- Network information: IP address, connection type (WiFi/cellular)
- Performance data: crash reports, error logs, loading times
- Screen resolution and device capabilities for optimal image processing

1.4 LOCATION INFORMATION
- GPS coordinates (optional, user-controlled) for regional pricing and country detection
- Country code detection for automatic regional pricing application
- Location data used for determining developed/underdeveloped region pricing tiers
- IP-based geolocation for fallback country detection when GPS is unavailable
- Location permissions managed through device settings with user consent required

1.5 SUBSCRIPTION AND BILLING DATA
- Subscription plan type (free, monthly premium, yearly premium)
- Subscription status, renewal dates, and billing cycle information
- Purchase receipts and transaction data from Google Play Store or Apple App Store
- Scan usage tracking: number of scans used per billing period
- Payment processing data (handled by app stores, not stored by CropCare)
- Regional pricing information and currency preferences

1.6 USAGE AND ANALYTICS DATA
- Feature usage patterns and user interaction data
- Analysis request frequency and timing patterns
- Success rates and confidence levels of AI analyses
- Search queries and filter preferences in analysis history
- Web platform usage: page views, session duration, feature engagement
- API usage statistics for enterprise customers

2. HOW WE COLLECT INFORMATION

2.1 DIRECT COLLECTION
- Account creation and profile setup information
- Images and data you upload for plant disease analysis
- Information provided through customer support interactions
- Preferences and settings configured within the application
- Feedback, ratings, and user-generated content
- Organization setup and team collaboration data

2.2 AUTOMATIC COLLECTION
- Mobile app usage through standard app analytics
- Web platform interaction through cookies and session tracking
- Device and technical information via standard mobile app APIs
- Performance metrics and error reporting for service improvement
- AI analysis results and confidence scores generated by our systems

2.3 THIRD-PARTY SOURCES
- GitHub Models API for AI plant disease detection processing
- Google Play Store and Apple App Store for subscription validation
- OAuth2 providers (Google, Apple) for secure authentication
- Payment processors (via app stores) for subscription management
- Content delivery networks for optimized service delivery

3. HOW WE USE YOUR INFORMATION

3.1 PRIMARY SERVICE PURPOSES
- Provide AI-powered plant disease detection via GitHub Models API
- Generate accurate treatment and care recommendations
- Manage subscription plans and billing (free tier, premium monthly/yearly)
- Maintain analysis history and personal plant health records
- Deliver regional pricing based on user location (developed/underdeveloped regions)
- Process and validate subscription purchases through app stores
- Auto-detect country code during signup for improved user experience
- Apply appropriate regional pricing tiers based on geographic location

3.2 PLATFORM AND FEATURE DELIVERY
- Authenticate users across mobile app and web platform
- Synchronize data between devices for premium users
- Enable team collaboration and organization features
- Provide Universal Link functionality (https://cropcare.hamez.dev/)
- Support deep linking between web and mobile platforms
- Deliver API services for enterprise customers

3.3 SERVICE IMPROVEMENT AND ANALYTICS
- Analyze usage patterns to improve AI model accuracy
- Monitor service performance and reliability
- Identify popular plant types and common disease patterns
- Optimize application performance and user experience
- Develop new features based on user behavior and feedback
- Enhance regional and local disease detection capabilities

3.4 COMMUNICATION AND SUPPORT
- Send subscription notifications and billing updates
- Provide customer support and technical assistance
- Notify users of scan limit approaches (free tier users)
- Deliver security updates and important service announcements
- Share educational content and treatment effectiveness tips
- Facilitate team communication for organizational accounts

3.5 COMPLIANCE AND SECURITY
- Prevent fraud and unauthorized subscription sharing
- Ensure compliance with app store policies and regional regulations
- Maintain data security and user account protection
- Validate subscription authenticity and prevent abuse
- Monitor for suspicious activity and policy violations

4. INFORMATION STORAGE AND SECURITY

4.1 LOCAL STORAGE (MOBILE APP)
- Analysis history stored locally using encrypted Hive database
- Images saved to app-specific device directories with restricted access
- Authentication tokens secured via Flutter Secure Storage with hardware-backed keystore
- User preferences and settings stored locally with encryption
- Offline analysis viewing capabilities through local data caching
- Data remains under user control with local deletion options

4.2 CLOUD INFRASTRUCTURE AND TRANSMISSION
- Secure HTTPS transmission to backend API
- Images processed through GitHub Models API with temporary processing only
- Web platform data hosted on secure cloud infrastructure with encryption at rest
- Database backups encrypted and stored with access controls
- API requests protected with OAuth2 authentication and rate limiting
- Cross-device synchronization for premium users with end-to-end encryption

4.3 THIRD-PARTY SERVICE SECURITY
- GitHub Models API: Temporary image processing with automatic deletion
- Google Play Store/Apple App Store: Subscription validation with secure tokens
- Payment processing: Handled entirely by app stores (no credit card data stored)
- OAuth2 providers: Secure authentication without password storage
- Content delivery networks: Encrypted transmission and secure endpoints

4.4 COMPREHENSIVE SECURITY MEASURES
- Industry-standard AES-256 encryption for data at rest
- TLS 1.3 encryption for all data transmission
- Regular security audits and vulnerability assessments
- Multi-factor authentication options for enhanced account security
- Automated threat detection and prevention systems
- GDPR and CCPA compliant data handling procedures
- Regular backup and disaster recovery protocols
- Secure development lifecycle and code review processes

5. DATA SHARING AND DISCLOSURE

5.1 WE DO NOT SELL YOUR PERSONAL DATA
- Your personal information, images, and analysis results are never sold to third parties
- Plant health data and treatment histories remain private and confidential
- Usage patterns may be anonymized and aggregated for service improvement only
- User consent is always required before any data sharing outside of essential operations

5.2 ESSENTIAL SERVICE SHARING
- GitHub Models API: Image processing for AI disease detection (temporary processing only)
- App stores (Google Play, Apple): Subscription validation and billing management
- Cloud service providers: Secure hosting and data processing infrastructure
- Authentication services: OAuth2 providers for secure login functionality
- Analytics services: Anonymized usage data for service optimization

5.3 LEGAL AND SAFETY DISCLOSURE
- Legal compliance: When required by law, court order, or regulatory authorities
- Safety protection: To prevent harm, protect rights, or ensure user safety
- Terms enforcement: To investigate violations of terms of service or fraud
- Business continuity: In case of merger, acquisition, or business transfer (with user notification)

5.4 ORGANIZATIONAL AND TEAM SHARING
- Team collaboration features: Data sharing within user-authorized organizations
- Premium organizational accounts: Controlled sharing based on role permissions
- API enterprise customers: Data sharing governed by specific enterprise agreements
- User-initiated sharing: Analysis results shared through user-controlled mechanisms

5.5 ANONYMIZED RESEARCH DATA
- Aggregated disease pattern analysis for agricultural research (no personal identification)
- Regional crop health trends for public health and agricultural planning
- AI model improvement using anonymized image and analysis data
- Academic partnerships for agricultural technology advancement (with ethical oversight)

6. YOUR PRIVACY RIGHTS

6.1 DATA ACCESS AND PORTABILITY
- View all stored analysis history through mobile app and web platform
- Export analysis data in machine-readable formats (JSON, CSV)
- Download complete account data including images and treatment history
- Access subscription and billing information through your account dashboard
- Review usage statistics and scan history for your account
- Request copies of any data we have collected about you

6.2 DATA CONTROL AND DELETION
- Delete individual analyses or clear complete analysis history
- Permanently delete account and all associated data
- Uninstall mobile app to remove all local data
- Clear authentication tokens and logout from all devices
- Cancel subscriptions directly through Google Play Store or Apple App Store
- Request deletion of any shared data with third parties (where technically feasible)

6.3 PRIVACY PREFERENCES AND SETTINGS
- Control camera, storage, and location permissions through device settings
- Manage location access for country code detection and regional pricing
- Grant or deny location permissions for automatic country code completion
- Manage notification preferences for billing and scan limit alerts
- Opt out of analytics and crash reporting (may limit support capabilities)
- Configure automatic data backup and synchronization settings
- Set analysis history retention periods and automatic cleanup
- Choose data sharing preferences for team and organizational features

6.4 REGIONAL PRIVACY RIGHTS
GDPR Rights (EU Users):
- Right to access: Request copies of your personal data
- Right to rectification: Correct inaccurate or incomplete data
- Right to erasure: Delete personal data under certain circumstances
- Right to restrict processing: Limit how we use your data
- Right to data portability: Transfer data to another service
- Right to object: Opt out of certain data processing activities
- Right to withdraw consent: Revoke previously given consent

CCPA Rights (California Users):
- Right to know: Information about data collection and sharing practices
- Right to delete: Request deletion of personal information
- Right to opt-out: Prevent sale of personal information (we don't sell data)
- Right to non-discrimination: No penalization for exercising privacy rights
- Right to correct: Request correction of inaccurate personal information

7. CHILDREN'S PRIVACY

7.1 AGE RESTRICTIONS AND REQUIREMENTS
- The Services are intended for users aged 16 and older
- We do not knowingly collect personal data from children under 16
- Users between 16-18 require parental consent for account creation
- Educational use by younger students requires institutional supervision and consent
- School and educational institution accounts must comply with COPPA and FERPA requirements

7.2 PARENTAL CONTROLS AND OVERSIGHT
- Parents can review and request deletion of their child's data
- Institutional accounts provide administrative oversight for student usage
- Educational features include enhanced privacy protections and limited data collection
- Parental notification requirements for any data processing of minors
- Special consent mechanisms for educational and agricultural training programs

7.3 EDUCATIONAL INSTITUTION COMPLIANCE
- Schools must obtain proper consent before student use
- Data processing agreements required for institutional deployment
- Enhanced data protection measures for educational environments
- Limited data retention periods for student accounts
- FERPA compliance for educational records and learning analytics

8. INTERNATIONAL DATA TRANSFERS

8.1 CROSS-BORDER PROCESSING AND COMPLIANCE
- Data may be processed in various countries to provide optimal service performance
- GitHub Models API processing occurs in Microsoft's global cloud infrastructure
- Backend services hosted in regions with strong data protection laws
- All transfers comply with applicable international privacy frameworks (GDPR Article 44-49)
- Standard contractual clauses and adequacy decisions ensure data protection across borders

8.2 REGIONAL DATA LOCALIZATION
- EU user data processed within the European Economic Area where possible
- Regional pricing and billing handled locally through app stores
- Analysis results cached locally on devices to minimize cross-border transfers
- Enterprise customers may request specific data residency arrangements
- Compliance with local data sovereignty requirements and regulations

8.3 SAFEGUARDS FOR INTERNATIONAL TRANSFERS
- Binding Corporate Rules (BCRs) for internal data transfers
- Data Processing Agreements with all third-party service providers
- Regular assessment of destination countries' privacy law adequacy
- Encryption and pseudonymization of data during international transmission
- User notification of any changes to data processing locations

9. DATA RETENTION

9.1 LOCAL DATA RETENTION POLICIES
- Mobile app analysis history: Retained until manually deleted by user
- Images and metadata: Stored locally until user removes them or app is uninstalled
- User preferences and settings: Persist between app sessions and updates
- Authentication tokens: Valid until user logs out or manually revoked
- Cached data: Automatically cleaned based on device storage availability

9.2 CLOUD AND BACKEND DATA RETENTION
- Account data: Retained while account remains active, deleted within 90 days of account closure
- Subscription information: Retained for tax and billing purposes as required by law (typically 7 years)
- Support communications: Retained for 2 years for quality assurance and issue resolution
- Anonymized usage analytics: Retained indefinitely for service improvement
- Security logs: Retained for 1 year for fraud prevention and security monitoring

9.3 THIRD-PARTY SERVICE RETENTION
- GitHub Models API: Images deleted immediately after processing completion
- App store data: Managed according to Google Play Store and Apple App Store policies
- OAuth providers: Token validity and refresh policies managed by respective providers
- Payment data: Handled entirely by app stores with their retention policies
- Analytics services: Anonymized data retained according to service provider policies

9.4 AUTOMATIC DELETION AND CLEANUP
- Inactive account deletion: Accounts inactive for 3 years may be automatically deleted
- Temporary data cleanup: Analysis processing data removed within 24 hours
- Error logs and crash reports: Retained for 90 days for troubleshooting purposes
- Email communications: Marketing emails retain engagement data for 2 years
- API access logs: Retained for 6 months for monitoring and security purposes

10. COOKIES AND TRACKING TECHNOLOGIES

10.1 WEB PLATFORM COOKIES (cropcare.hamez.dev)
- Essential cookies: Required for authentication, security, and basic functionality
- Analytics cookies: Google Analytics and similar services for usage optimization
- Preference cookies: Remember user settings, language choices, and dashboard configurations
- Security cookies: Fraud prevention, rate limiting, and suspicious activity detection
- Session cookies: Maintain login state and secure communications

10.2 MOBILE APP TRACKING
- Local storage: User preferences and settings stored in app-specific directories
- Analytics tracking: Anonymized usage patterns for feature optimization and bug detection
- Crash reporting: Automatic error collection for app stability improvement
- Performance monitoring: Load times, response rates, and user interaction metrics
- Authentication persistence: Secure token storage for seamless user experience

10.3 THIRD-PARTY TRACKING AND ANALYTICS
- GitHub Models API: No tracking cookies, temporary processing only
- App store analytics: Usage statistics provided by Google Play Store and Apple App Store
- OAuth providers: Authentication tracking managed by Google, Apple according to their policies
- Content delivery networks: Performance optimization tracking for faster service delivery
- Customer support systems: Interaction tracking for support quality and response time improvement

10.4 COOKIE MANAGEMENT AND USER CONTROL
- Web platform cookie preferences: Configurable through browser settings and our cookie banner
- Mobile app analytics: Opt-out available through app settings (may limit support capabilities)
- Third-party cookie control: Managed through respective service provider settings
- Tracking prevention: Compatible with browser privacy settings and tracking protection
- Cookie deletion: Regular cleanup and user-controlled cookie management options

11. THIRD-PARTY SERVICES

11.1 AI AND MACHINE LEARNING SERVICES
GitHub Models API:
- Purpose: AI-powered plant disease detection and analysis
- Data shared: Plant images (temporary processing only)
- Data retention: Images deleted immediately after analysis completion
- Privacy policy: Subject to Microsoft/GitHub Terms of Service and Privacy Policy
- Security: HTTPS encryption, no permanent storage of user images

11.2 AUTHENTICATION AND IDENTITY SERVICES
OAuth2 Providers (Google, Apple, GitHub):
- Purpose: Secure user authentication and account creation
- Data shared: Basic profile information (email, name), authentication tokens
- Data retention: Managed according to respective provider policies
- Privacy policies: Subject to Google, Apple, GitHub privacy policies

11.3 SUBSCRIPTION AND PAYMENT PLATFORMS
Google Play Store and Apple App Store:
- Purpose: Subscription management and payment processing
- Data shared: Purchase receipts, subscription status, billing information
- Data retention: Managed according to app store policies and local regulations
- Security: End-to-end encrypted payment processing, PCI DSS compliance
- User control: Subscription management through respective app store accounts

11.4 CLOUD INFRASTRUCTURE AND HOSTING
Backend Services and Web Platform:
- Purpose: User account management, data synchronization, API services
- Data shared: Account information, analysis history, subscription status
- Security: Industry-standard encryption, access controls, regular audits
- Compliance: GDPR, CCPA, and other regional privacy regulations
- Data residency: Configurable for enterprise customers and regulatory compliance

11.5 ANALYTICS AND PERFORMANCE MONITORING
Usage Analytics Services:
- Purpose: Service optimization, performance monitoring, user experience improvement
- Data shared: Anonymized usage patterns, performance metrics, crash reports
- Privacy protection: Data aggregation, anonymization, and pseudonymization
- User control: Opt-out capabilities available through app and web platform settings
- Compliance: Privacy-by-design principles and regulatory compliance standards

12. UPDATES TO THIS PRIVACY POLICY

12.1 POLICY MODIFICATION PROCEDURES
- We may update this Privacy Policy periodically to reflect changes in our practices
- Material changes will be notified through email and in-app notifications
- Updated policy will be posted on our web platform with revision date
- Continued use of Services after policy updates constitutes acceptance of new terms
- Users will have 30 days to review changes before they take effect

12.2 NOTIFICATION METHODS
- Email notifications to registered account holders
- In-app notifications and alerts for active users
- Website banner and prominent display of policy changes
- Push notifications for significant privacy-related updates
- Customer support communication for users with questions about changes

12.3 USER RESPONSE TO POLICY CHANGES
- Users may request clarification on policy changes through customer support
- Account deletion option available if users disagree with updated policies
- Data export capabilities provided before policy changes take effect
- Grandfathering of certain rights for existing users during transition periods
- Appeals process for users who believe changes affect their privacy rights

13. CONTACT INFORMATION AND DATA REQUESTS

13.1 PRIVACY OFFICER CONTACT INFORMATION
- Email: privacy@cropcare.hamez.dev
- Mailing Address: Kahawa, Kenya
- Phone: Available through customer support system
- Response Time: 7 business days for privacy inquiries
- Emergency Contact: security@cropcare.hamez.dev for urgent security matters

13.2 DATA SUBJECT REQUEST PROCEDURES
- Submit requests through privacy email or customer support system
- Identity verification required for all data requests
- Request processing time: 30 days maximum (may be extended with notification)
- Available request types: Access, correction, deletion, portability, restriction
- Appeal process available for denied or unsatisfactory responses

13.3 REGULATORY COMPLIANCE AND REPORTING
- Data Protection Officer (DPO) available for EU users
- GDPR Article 27 representative for European operations
- CCPA compliance officer for California residents
- Regular privacy impact assessments and compliance audits
- Breach notification procedures in compliance with applicable laws

14. EFFECTIVE DATE AND JURISDICTION

This Privacy Policy is effective as of September 25, 2025, and applies to all users of CropCare AI services worldwide. This policy is governed by applicable privacy laws in the jurisdictions where we operate, with specific attention to GDPR (European Union), CCPA (California), and other regional privacy regulations.

For region-specific privacy rights or questions, please contact our privacy team using the information provided above.

© 2025 CropCare AI. All rights reserved.