Privacy Policy

1. Introduction

IMDAA Studio ("the Platform", "we", "us") is a scientific data processing application that converts IMDAA (Indian Monsoon Data Assimilation and Analysis) reanalysis archives into structured, research-ready CSV datasets. This Privacy Policy explains how we collect, use, store, and protect your information when you use the Platform.

2. Information We Collect

2.1 Account Information

When you create an account, we collect:

• Email address — used for authentication and account recovery
• Full name — used for personalization and membership records
• Phone number — required for membership verification via WhatsApp
• Research background — optional, used for membership review
• Research purpose — optional, used for membership review

2.2 Research Data

When you use the Platform to process data, we temporarily store:

• Uploaded ZIP archives — IMDAA reanalysis files you submit for processing
• Generated CSV outputs — processed and corrected datasets
• Processing metadata — job IDs, timestamps, file sizes, and processing status

2.3 Usage Data

We automatically collect minimal operational data:

• Job processing requests and their status (queued, processing, completed, failed)
• Storage quota usage per account
• Authentication timestamps (login/logout events)

3. How We Use Your Information

We use the information we collect to:

• Authenticate your identity and manage your account
• Process your IMDAA archive-to-CSV conversion requests
• Apply scientific correction modules (Temperature, Radiation, Vapor Pressure, etc.)
• Manage storage quotas and processing thread allocations
• Review and process membership applications
• Maintain system health, prevent abuse, and troubleshoot issues

4. Data Storage and Security

4.1 Storage Infrastructure

• Account data is stored in Firebase Realtime Database with encrypted connections
• Authentication is managed by Firebase Authentication with industry-standard protocols
• Research files are stored on the server filesystem within your account's isolated directory
• Job metadata is persisted locally on the server with per-user isolation

4.2 Security Measures

• All API routes are protected by Firebase token verification
• Dashboard routes require active authentication sessions
• File access is scoped to authenticated account ownership
• Admin operations require separate elevated authentication
• Membership verification uses HMAC-signed authorization codes

5. Data Retention

• Uploaded archives — retained until manually deleted by you or via workspace cleanup
• Processed CSV files — retained until manually deleted or account storage is purged
• Account profiles — retained for the lifetime of your account
• Job logs — retained as long as the associated files exist
• Membership records — retained for audit and renewal purposes

You can delete your processed files at any time from the Dashboard. Use the "Purge Studio Files" option in Settings to perform a full workspace cleanup.

6. Data Sharing

We do not sell, rent, or share your personal information or research data with any third parties. Your uploaded archives and generated outputs are never accessed by other users.

Exceptions:

• Firebase (Google) — authentication tokens and account metadata are processed by Firebase services under Google's privacy policies
• System administrators — admin users can view account metadata (name, email, membership status) for platform management purposes, but cannot access your research files

7. Your Rights

You have the right to:

• Access — view your profile, stored files, and processing history via the Dashboard
• Correct — update your profile information at any time from Settings
• Delete — remove your files and request account deletion
• Export — download all your processed CSV files at any time
• Withdraw consent — stop using the service and request data removal

8. Cookies and Local Storage

The Platform uses:

• localStorage — to persist your theme preference (light/dark mode) and Firebase authentication session
• Service Worker cache — for PWA offline shell functionality

We do not use third-party tracking cookies or analytics scripts.

9. Children's Privacy

IMDAA Studio is a scientific research tool intended for use by researchers, students, and professionals. We do not knowingly collect information from children under 13 years of age.

10. Changes to This Policy

We may update this Privacy Policy from time to time to reflect changes in our practices or applicable regulations. The "Last Updated" date at the top of this page indicates when the policy was most recently revised. Continued use of the Platform after changes constitutes acceptance of the revised policy.

11. Contact

If you have questions about this Privacy Policy or wish to exercise your data rights, please contact us at: