Privacy Policy
Last Updated & Effective: October 11, 2026
1. Data Controller & Privacy Commitment
At DaylyFlow ("DaylyFlow", "we", "our", or "us"), accessible via daylyflow.com, your privacy, confidentiality, and autonomy are our highest priorities. We designed DaylyFlow to help individuals organize daily routines, time-block schedules, and build positive habits — never to harvest, exploit, or sell personal information to third-party data brokers or advertisers.
Data Controller: Amit Mandal (Founder & Operator of DaylyFlow)
Address: India, Kolkata, West Bengal
Contact Email: [email protected] | [email protected]
We do not sell your data and share it only with the processors listed in this policy.
2. Information We Collect
We adhere strictly to the principle of data minimization. We only collect the information necessary to provide you with a functional, high-performance daily planning service:
- Account & Profile Credentials: When you register via email, Google Sign-In, or GitHub Sign-In, we store your verified email address, display name / public username, and optional avatar URL via Supabase Auth. We never receive or store your third-party account passwords.
- Planner & Schedule Data: Task titles, descriptions, designated time blocks, category tags, priority levels (Eisenhower matrix), and completion status that you create within the platform.
- Habit Tracking Logs: Custom habit titles, scheduled frequency, check-in timestamps, and consecutive streak statistics.
- Local UI & Aesthetic Preferences: Your preferred theme mode (Light, Dark), selected accent color palettes, and custom color wheel hex values stored directly in your browser.
- Technical Diagnostics & Server Logs: Edge request logs, browser user-agent, device category, IP address, and standard page response times collected by Cloudflare to ensure security, uptime, and protect against malicious automated attacks.
3. Legal Bases for Processing (GDPR & UK GDPR)
Under the General Data Protection Regulation (GDPR Article 6), we process your personal data under the following lawful bases:
- Contractual Necessity (Art. 6(1)(b)): Processing necessary to deliver DaylyFlow core services — managing your user account, rendering your timeline, storing habits, and syncing schedules.
- Legitimate Interests (Art. 6(1)(f)): Processing necessary to maintain system infrastructure, safeguard our service from malicious traffic or DDoS attacks, detect fraud, and provide technical support.
- Consent (Art. 6(1)(a)): For optional third-party cookies (Google Analytics 4). Analytics scripts load strictly if you explicitly click "Accept All" on our cookie consent banner.
- Legal Obligation (Art. 6(1)(c)): Retaining statutory purchase, tax, and invoice records required by applicable commercial and financial legislation.
4. Smart Planning Assistant & In-Browser Processing
DaylyFlow offers an optional smart planning assistant for daily schedule organization, Eisenhower matrix suggestions, and routine structuring. Unlike cloud AI platforms:
- 100% Client-Side Processing: The planning assistant runs entirely inside your web browser using client-side algorithms and sends nothing to any AI provider or external server. Zero prompt text, schedule data, or task titles are ever transmitted to external AI servers or cloud LLM APIs.
- No Cloud AI Sub-Processors: We do not send your data to OpenAI, Google Vertex AI, Anthropic, or any third-party AI provider. Your planning logic executes locally on your device.
- No Machine Learning Model Training: Because no data leaves your browser, your tasks, schedules, and habits are never logged by external AI vendors or used to train machine learning models.
- Tasks Saved to Account: When you use the planning assistant to schedule tasks, generate daily blocks, or create habits, the resulting tasks and habits are saved to your local browser storage and your account database just like tasks you create manually.
- User-Initiated Only: The planning assistant only runs when you explicitly submit a command to parse tasks or generate a daily plan.
- Human-in-the-Loop Control: All schedule proposals are suggestions that you can freely edit, adjust, reschedule, or discard at any time.
5. Google & GitHub Sign-In (Authentication Only)
DaylyFlow supports optional OAuth Sign-In via Google and GitHub for convenient, secure authentication. We enforce strict permission boundaries:
🔐 Authentication Boundaries & Data Access
- Sign-In Only: We use Google and GitHub OAuth exclusively to verify your identity and receive basic identity fields (email address, display name/username, and public avatar URL) via Supabase Auth.
- GitHub Sign-In: We receive only your verified email, username, and avatar URL. We do not request or possess access to repositories, organizations, private keys, or code.
- Google Sign-In: We request only basic profile identity. DaylyFlow does not request access to external calendars, Gmail, Google Drive, or any other private Google services.
- Session Security: Authentication tokens are securely handled by Supabase Auth with encrypted JSON Web Tokens (JWTs).
- Revoking Access: You can disconnect or revoke authentication permissions at any time directly through your Google Account Permissions or GitHub Authorized Applications.
6. Data Retention & Storage Lifecycle
We retain personal schedule data only for as long as necessary to provide your planning experience:
- Active Accounts: Your tasks, habits, and streak metrics are retained as long as your account remains open, enabling you to inspect historical completion trends and review your 365-day annual heatmap.
- Inactive Accounts: Inactive accounts are not automatically deleted based on periods of inactivity. Your account and stored planner items remain preserved until you choose to delete your account via self-service Settings or submit a deletion request.
- Server Diagnostics & Edge Logs: Cloudflare edge server access logs and infrastructure diagnostics are retained for up to 30 days for cybersecurity, DDoS mitigation, and system troubleshooting, after which they are permanently expunged.
- Client-Side Local Storage: Local theme preferences and offline cached tasks stored in your browser's
localStorageremain on your physical device until manually cleared in your browser settings or wiped via DaylyFlow Settings. - Automated Database Backups: Automated daily disaster recovery database backups provided by Supabase are retained on a rolling 7-day cycle. When you delete account data, it is expunged from live production databases immediately and completely wiped from backups as snapshots expire within 7 days.
- Statutory Financial Records: We retain only payment and transaction records strictly required by law (such as tax invoices, transaction receipts, and payment gateway logs) for statutory accounting and legal compliance.
7. International Data Transfers
DaylyFlow uses modern cloud infrastructure with servers located in the European Union, the United States, and edge networks distributed worldwide:
- Database and authentication services provided by Supabase are hosted in secure AWS data centers with strict encryption at rest and in transit.
- Global edge routing and CDN caching provided by Cloudflare ensure low-latency worldwide delivery.
- Payment processing for USD subscriptions is managed by Lemon Squeezy (United States), acting as Merchant of Record.
- Domestic INR payment processing and instant UPI transfers are managed by Razorpay Software Pvt. Ltd. (India), adhering strictly to RBI payment guidelines and data localization standards.
- When data is transferred outside the European Economic Area (EEA) or United Kingdom, transfers are safeguarded by Standard Contractual Clauses (SCCs) approved by the European Commission or equivalent adequacy decisions.
8. Local-First Architecture & Data Security
DaylyFlow is built with a local-first architectural approach. Your daily tasks and custom theme states are cached in your browser's client-side storage (localStorage). This guarantees near-instant page responsiveness and fast local task interaction.
For authenticated cloud sync, all data transmissions between your browser and our infrastructure are encrypted using TLS encryption with strict HTTPS enforcement. Database records in Supabase are governed by strict Row Level Security (RLS) policies, ensuring users can only read and write their own data.
All payment transactions for Pro subscriptions are handled by PCI-DSS Level 1 certified payment processors (Lemon Squeezy and Razorpay). DaylyFlow never stores or has access to full credit card numbers or banking secrets.
10. Third-Party Sub-Processors
We share data only with the following service providers strictly necessary to deliver DaylyFlow:
- Supabase Inc.: Database hosting and authentication.
- Cloudflare Inc.: Hosting and serverless functions (edge delivery, CDN, and SSL/TLS termination).
- Lemon Squeezy LLC: USD payments and global subscription management (Merchant of Record).
- Razorpay Software Pvt. Ltd.: INR payment processing (UPI, cards, netbanking).
- Google LLC: Sign-in only (optional OAuth authentication) and optional Google Analytics 4 (loaded strictly upon cookie consent).
- GitHub, Inc. (Microsoft Corporation): Sign-in only (optional OAuth authentication). Receives user ID, email address, public username, and avatar URL.
11. Account Deletion & Data Portability (Self-Service)
You maintain full sovereignty over your planner data. We provide immediate, frictionless self-service controls:
📥 Instant Data Export (JSON Only)
Download a complete machine-readable copy of your tasks, habits, and schedules anytime in JSON format from Settings > Data > Export Data. Available to all users (both Free and Pro). No waiting period, no lock-in.
🗑️ Immediate Self-Service Account Deletion
Permanently delete your account and all associated cloud data anytime in Settings > Danger Zone > Delete Account.
- Authenticated Deletion Endpoint: When initiated, our Cloudflare Pages Function endpoint (
/api/delete-account) verifies your active session JWT, verifies or cancels active subscriptions to prevent unexpected billing, then uses the Supabase service-role key to permanently delete your records fromuser_tasks,user_habits, andprofiles, and permanently deletes your authentication record fromauth.usersvia the Supabase Auth Admin API. - Statutory Record Retention: We retain only payment and transaction records strictly required by law for tax, accounting, and anti-fraud compliance.
- Client-Side Wipe & Sign Out: Upon successful deletion, your session is signed out, all local browser tokens, theme preferences, and cached task stores are wiped from
localStorageandsessionStorage, and you are returned to the home page. - GDPR & CCPA Rights: You also have the right to request manual verification of deletion or submit privacy inquiries by contacting [email protected].
12. Children's Privacy (COPPA & GDPR-K)
DaylyFlow is intended for general audiences, professionals, and students over the age of 13 (or 16 in certain European jurisdictions). We do not knowingly solicit or collect personal information from children under 13.
If we discover that a child under 13 has created an account without verified parental consent, we will promptly delete all associated information. If you believe a minor has registered an account, please notify us immediately at [email protected].
13. Privacy Contact & Inquiries
For questions, concerns, formal data requests, or GDPR/CCPA enforcement inquiries, please contact our Privacy Team:
DaylyFlow Privacy Support
Data Controller: Amit Mandal
Address: India, Kolkata, West Bengal
Privacy Inquiries: [email protected]
General Support: [email protected]