52Weeks
Privacy Policy
How 52Weeks handles local planner data, analytics, optional backups, sharing, and third-party services.
- Effective date
- June 14, 2026
- Last updated
- June 14, 2026
1. Overview
52Weeks (“52Weeks,” “we,” “us,” or “our”) provides a local-first yearly planning application available at https://52weeks.lawson.dev. This Privacy Policy explains what information 52Weeks handles, how it is used, when it may leave your browser, and what choices you have.
2. Information We Collect or Process
By default, planner information you create in 52Weeks is stored locally in your browser using IndexedDB and localStorage. This may include event titles, descriptions or notes, start and end dates, event status, categories, category names, category colors, and planner preferences.
When you visit 52Weeks, standard technical information may be processed by your browser, hosting infrastructure, and analytics systems. This can include IP address, browser type, device type, operating system, referring page, pages visited, access time, and performance information.
In production, 52Weeks uses privacy-respecting analytics through a same-origin /visitors proxy to a self-hosted Umami analytics instance. Analytics events may include low-detail product usage, such as opening the planner, creating or deleting an entry, exporting or importing data, changing category filters, using sharing or backup features, enabling public holidays, or changing years.
We do not intentionally send planner titles, descriptions, full dates, share hashes, imported file contents, or user-created category names to analytics. The analytics script is configured to honor Do Not Track and exclude URL hashes.
3. Optional Google Drive Backup
If you choose to connect Google Drive backup, 52Weeks may process your Google account email address, temporary Google access tokens in your browser session, backup files stored in your Google Drive app data folder, backup metadata, and planner snapshots containing your entries, categories, and preferences.
Google Drive backup is optional. Your use of Google services is also governed by Google’s privacy terms and account settings.
4. Public Holidays and Share Links
If you enable public holidays, 52Weeks may use your browser locale to suggest a country and may request holiday data for selected country codes from a public holiday API. Country settings and holiday cache data may be stored locally in your browser.
If you use the sharing feature, 52Weeks can encode planner entries and categories into a share URL hash. URL hashes are generally not sent to our server by browsers, but anyone you share the link with can decode and view the included planner data.
5. How We Use Information
We use information to:
- Provide planner features and local browser storage.
- Let you export, import, share, back up, and restore planner data.
- Remember preferences such as theme, holiday, and backup settings.
- Understand aggregate product usage and improve the app.
- Maintain security, reliability, abuse prevention, and debugging.
- Comply with legal obligations.
We do not use planner titles, descriptions, or notes for advertising.
6. Legal Bases for Processing
For users in jurisdictions that require a legal basis, such as the European Economic Area or United Kingdom, we rely on one or more of the following legal bases: contract, consent, legitimate interests, and legal obligation.
7. How We Share Information
We may share or process information with service providers that help run 52Weeks, including Vercel for hosting, self-hosted Umami for analytics, Google Cloud, Google Identity Services, Google Drive APIs for optional backup, and a public holiday API for optional holiday data.
We may also disclose information if required by law, legal process, or to protect the rights, safety, and security of users, the public, or 52Weeks. We do not sell your planner data.
8. International Data Transfers
52Weeks and its service providers may process information in countries other than where you live. These countries may have different privacy laws.
9. Data Retention
Planner entries, categories, and preferences remain in your browser until you delete them, clear planner data, import replacement data, or clear browser storage. Exported files remain wherever you save them. Share links remain accessible to anyone who has the link unless the link is deleted or no longer shared.
Google Drive backups, if enabled, are stored in your Google Drive app data folder. The app currently keeps up to five backup files. Analytics and hosting logs are retained according to the configured retention settings of Umami and Vercel.
10. Your Choices and Rights
Depending on where you live, you may have rights to access, correct, delete, export, restrict, object to, or withdraw consent for certain processing of personal information. You may also have the right to opt out of certain sharing or analytics and to lodge a complaint with a data protection authority.
Because 52Weeks stores planner data locally by default, you can control much of your data directly in your browser by deleting planner data, clearing browser storage, deleting exports, or choosing not to share URLs.
Privacy requests may be sent to david@lawson.dev.
11. Cookies, Local Storage, and Tracking
52Weeks may use browser storage technologies including IndexedDB and localStorage to store planner data, remember preferences, cache holiday data, store migration or onboarding state, store backup settings, and support import, export, and app functionality.
You can control browser storage through your browser settings. Clearing browser storage may delete your planner data.
12. Security
We use reasonable measures to protect information, including local-first data storage by default, HTTPS, browser-based storage controls, limited analytics payloads, a same-origin analytics proxy, and optional Google Drive backup through Google APIs. No system is completely secure.
You are responsible for protecting access to your device, browser profile, exported files, Google account, and shared planner links.
13. Children’s Privacy
52Weeks is not intended for children under 13, and we do not knowingly collect personal information from children under 13. If you believe a child has provided personal information to us, contact us at david@lawson.dev.
14. Changes and Contact
We may update this Privacy Policy from time to time. If changes are material, we will provide notice by updating the effective date, posting a notice in the app, or using another reasonable method.
Questions or requests may be sent to david@lawson.dev.