​

Data Privacy & Security

​

Our Privacy Commitment

​

Zero Data Collection

• Personal information or user profiles
• Project data or content
• Usage analytics or telemetry
• IP addresses or location data
• Browser fingerprints or device information
• Cookies for tracking purposes
• Any form of user behavior data

​

Local-Only Storage

​

How Your Data is Stored

• Browser-based: Data is stored locally on your device
• No cloud sync: Nothing is sent to external servers
• Per-browser storage: Each browser maintains its own data
• Automatic saves: Changes are saved to LocalStorage immediately
• Persistent sessions: Your data remains between browser sessions

​

What This Means for You

• Complete data privacy and security
• Works completely offline
• No account registration required
• No subscription or data sharing agreements
• Fast performance with no network latency

• Data is specific to the browser and device where it was created
• Clearing browser data will delete your projects
• Data doesn’t automatically sync across devices
• Browser storage limits apply (typically 5-10MB)

​

Data Ownership and Control

​

You Own Your Data

• Full access: All your data is always accessible to you
• No lock-in: Export your projects anytime in standard JSON format
• Complete control: Delete, modify, or export without restrictions
• No third parties: Your data is never shared with or accessible to anyone else
• Portability: Move your data freely between devices and browsers

​

Data Portability

{
  "project": "My Project",
  "timeline": {...},
  "tasks": [...],
  "team": [...]
}

• Contain all your project information
• Can be stored anywhere you choose
• Are importable back into Gantt Maker
• Can be version controlled or archived
• Are human-readable and can be edited

​

Security Best Practices

​

Protecting Your Project Data

​

Sensitive Project Data

• Use device encryption (FileVault, BitLocker, etc.)
• Store exported files in encrypted containers
• Don’t use shared or public computers for sensitive projects
• Consider using a dedicated browser profile for sensitive work
• Regularly clear LocalStorage on shared devices
• Use descriptive but non-sensitive project names

​

Data Backup Strategy

​

Why Backups Matter

• Can be cleared by browser cleaning tools
• May be deleted when uninstalling browsers
• Storage quota limits may be reached
• Browser crashes or corruption can cause data loss
• Switching devices means starting fresh without exports

​

Recommended Backup Approach

1. After major changes: Export when completing significant project updates
2. Regular schedule: Set a reminder to export weekly or monthly
3. Multiple versions: Keep different versions for project milestones
4. Organized storage: Use consistent naming conventions (e.g., project-name-2026-03-10.json)
5. Multiple locations: Store backups in at least two different locations

​

Export for Collaboration

1. Export your project as a JSON file
2. Share via your preferred method:
   • Email attachment
   • Shared drive (Google Drive, Dropbox, OneDrive)
   • File sharing service
   • Version control system (Git, if appropriate)
3. Team members import the file into their Gantt Maker
4. Exchange updated versions as needed
5. Use clear version naming to track changes

​

Browser Storage Considerations

​

Understanding LocalStorage Limits

• Typical limit: 5-10MB per domain
• Varies by browser: Chrome, Firefox, Safari have slightly different limits
• Shared quota: All data for the domain counts toward the limit
• No warning: Browsers may fail silently when limit is reached

​

Managing Storage Space

• Split into smaller project files by phase or team
• Archive completed projects (export and remove from LocalStorage)
• Keep only active projects in the browser
• Regularly clean up old or test projects

​

Data Persistence

• You explicitly clear browser data
• Browser storage is cleared by cleaning software
• Browser is uninstalled without exporting settings
• Storage quota is exceeded
• You manually delete the data

​

Transparency Commitment

• Open source: You can verify how data is handled by reviewing the code
• No hidden features: No analytics, tracking, or data collection code
• No external connections: The application doesn’t make network requests for data
• No accounts: No registration, login, or user tracking systems
• No monetization through data: Your data is never used for advertising or sold

​

Compliance and Standards

​

Privacy by Design

• Data minimization: We don’t collect data we don’t need (which is any data)
• Purpose limitation: No data is used for purposes beyond your project management
• Storage limitation: Data is only stored locally on your device
• Transparency: Clear information about how data is handled
• User control: You have complete control over your data

​

GDPR and Privacy Regulations

• No personal data processing: We don’t process or control your data
• No data transfers: Data never leaves your device
• No consent needed: Since we don’t collect data, no consent forms are required
• Right to deletion: Simply clear browser storage or delete exported files
• Right to export: Built-in export functionality provides data portability

​

Questions About Privacy?

• Review the application source code (available on GitHub)
• Check browser developer tools to see what’s stored in LocalStorage
• Use browser network monitoring to verify no external data transmission
• Examine exported JSON files to see exactly what data is stored