Privacy Policy

1. Who We Are

Yearbird is an open-source calendar visualization tool. The source code is publicly available at github.com/mjaverto/yearbird.

This Privacy Policy applies to the hosted version at yearbird.com and any self-hosted instances using the official codebase.

2. Information We Do NOT Collect

Yearbird is designed with privacy as a core principle. We do not:

• Collect, store, or transmit your calendar data to any server
• Use cookies for tracking or analytics
• Employ any third-party analytics services
• Store your Google account credentials
• Access your data in any way after you close the browser tab
• Sell, share, or monetize any user data (we have none to sell)

3. How Yearbird Works

Client-Side Architecture

Yearbird runs entirely in your web browser. When you sign in with Google:

• Your browser communicates directly with Google's servers
• Calendar data is fetched directly from Google to your browser
• All processing and rendering happens locally in your browser
• No calendar data passes through Yearbird's servers (we don't have any)

Google OAuth Authentication

We use Google Sign-In (OAuth 2.0) to authenticate you and access your calendar. This means:

• You authenticate directly with Google, not with us
• We request only calendar.readonly permission (read-only access)
• We cannot modify, delete, or create calendar events
• Your Google password is never shared with Yearbird

Google's authentication is subject to Google's Privacy Policy.

Google API Services User Data Policy Compliance

Yearbird's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Specifically, Yearbird:

• Only uses Google data for the stated purpose: Displaying your calendar events in a year-at-a-glance visualization
• Does not transfer data to third parties: Your calendar data never leaves your browser
• Does not use data for advertising: We have no ads, tracking, or monetization of your data
• Does not use data to train AI/ML models: Your data is only used for visualization
• Limits data access: We request only the minimum scope needed (calendar.readonly)

Local Storage

Yearbird stores minimal data in your browser's localStorage:

• OAuth tokens: Temporary access tokens from Google (automatically expire)
• User preferences: Display settings like hidden categories and view preferences

This data never leaves your browser and is cleared when you sign out or clear your browser data.

4. Third-Party Services

Yearbird interacts with the following third-party service:

• Google Calendar API: To fetch your calendar events. Subject to Google's Privacy Policy and Terms of Service.

We have no control over and assume no responsibility for the privacy practices of Google.

5. Data Security

Because we don't collect or store your data, there is no database to breach. Your calendar data exists only:

• On Google's servers (protected by Google's security)
• Temporarily in your browser's memory while using Yearbird

All communication with Google's API uses HTTPS encryption.

6. Children's Privacy

Yearbird is not intended for children under 13 years of age. We do not knowingly collect any information from children. If you are a parent and believe your child has used Yearbird, please note that we have no data to delete because we collect nothing.

7. Your Rights (GDPR, CCPA, and Similar Laws)

Privacy regulations like GDPR and CCPA give you rights over your personal data. Because Yearbird does not collect, store, or process your personal data on any servers:

• Right to Access: We have no data to provide
• Right to Deletion: We have no data to delete
• Right to Portability: We have no data to export
• Right to Object: We perform no processing to object to

To manage your Google data, visit your Google Account permissions to revoke Yearbird's access at any time.

8. Open Source Transparency

Yearbird is open source under the MIT License. You can:

• Inspect the complete source code at github.com/mjaverto/yearbird
• Verify our privacy claims by reviewing the code
• Self-host your own instance for complete control
• Contribute improvements or report issues

9. Changes to This Policy

We may update this Privacy Policy from time to time. Changes will be posted on this page with an updated revision date. Continued use of Yearbird after changes constitutes acceptance of the updated policy.

10. Contact

For privacy-related questions, you can:

• Open an issue on GitHub
• Review the source code to verify our practices