Ed Planner

Privacy Policy

Last updated: 24 April 2026

This policy covers both Student Planner (student.ed-planner.com) and Teacher Planner (teacher.ed-planner.com), which we refer to together as "Ed Planner". Ed Planner is operated by Marc Curran as a sole trader.

We've tried to write this in plain language. If anything is unclear, email help@ed-planner.com and we'll answer directly.

1. What data we collect

Only what's needed for the app to work:

• Account identity: your email address, display name and profile image, provided by your sign-in method (Google, Microsoft, Apple, or email + password).
• Planner content you create: subjects, classes, students you enter, periods, timetable entries, lessons, homework, exams, grades, notes, diary entries, preferences. This is the core of what the app does.
• Usage telemetry: anonymous page views and feature usage via Firebase Analytics, and crash/error reports via Sentry. Neither is tied to your planner content.
• Technical logs: IP address and user agent recorded briefly by Google Cloud for abuse prevention. We do not see or export these.

We do not collect: payment information, precise location, contacts, browsing history, or anything from devices other than the device you're using.

2. Why we collect it

• Identity → to recognise you across devices, so your data follows you.
• Planner content → to actually provide the service you're using.
• Usage telemetry → to understand which features are used and to catch bugs. Data is aggregated and never sold.
• Technical logs → to keep the service running and fend off abuse.

Under UK GDPR, our lawful basis is contract for everything needed to run the app (you can't use it without an account) and legitimate interest for telemetry and security logs.

3. Google account integrations

Ed Planner can optionally connect to Google services. You choose whether to enable each one; nothing is accessed without your consent.

• Google Calendar (read-only) — to show your meetings inline on the Teacher Planner dashboard.
• Google Classroom (read-only) — to import coursework into your homework list (Student Planner) or course + submission data (Teacher Planner).
• Gmail (read + modify, Teacher Planner only) — to list recent threads, open one, archive, delete to trash, and send replies. We never read attachments or full mailbox history.
• Google Drive (drive.file scope only) — to create a "Teacher Planner" or "Student Planner" folder and attach files you upload through the app. We cannot see any other file in your Drive.

What we do with this data: it's shown in the Ed Planner UI on your device. Calendar events and Classroom courses are fetched live and not copied to our database. Gmail thread IDs and Drive file IDs are stored alongside the relevant planner item so we can re-fetch the content on demand. We do not use any of this data to train AI models, build profiles, or share with anyone else.

Revoking access: you can disconnect Ed Planner at any time from your Google Account permissions page. Signing out of the app also clears the access token locally.

4. Where data is stored

All of your planner content is stored on Google Cloud Firestore, located in the European Union:

• Student Planner: multi-region eur3 (Belgium + Netherlands).
• Teacher Planner: single region europe-west2 (London).

Backups stay within the same region. Data does not leave the EU / UK for storage or routine processing. When you use Google integrations, Google itself may process that data according to its own policies; see Google's Privacy Policy.

Locally, Ed Planner also caches a copy of your data in your browser's localStorage and IndexedDB so the app works offline. Clearing site data removes that local cache.

5. Who we share data with

We use a small number of trusted processors to run the service:

• Google Cloud Platform / Firebase — hosting, authentication, database (Firestore). Data stored in the EU as above.
• Sentry — error and crash reports, EU region. Only stack traces and anonymised metadata; no planner content.

We do not sell your data. We do not share your data with advertisers. We do not use your planner content to train machine-learning models. We disclose data only if legally required (e.g. a valid UK court order) and will notify you unless prohibited from doing so.

6. How long we keep data

• Your planner content stays until you delete it or close your account.
• Clear all data in Settings wipes your content from our database within minutes.
• Closing your account wipes your content within 30 days.
• Anonymised analytics are kept for up to 14 months.
• Error reports are kept for 90 days.
• Security logs (IPs) are kept by Google Cloud for up to 30 days.

7. Your rights (UK GDPR / EU GDPR)

You have the right to:

• Access a copy of your data.
• Correct anything that's inaccurate.
• Delete your account and content ("right to erasure").
• Export your data in a common format.
• Object to processing based on legitimate interest.
• Withdraw consent for Google integrations at any time.
• Complain to the UK Information Commissioner's Office (ico.org.uk) or your local EU data protection authority if you feel we've mishandled your data.

To exercise any of these, email help@ed-planner.com. We'll respond within 30 days.

8. Children and school use

Ed Planner is intended for use by students aged 13 and over and by teaching staff. For users under 13, we require verifiable parental consent before an account is created (COPPA). Schools intending to deploy Ed Planner at scale should contact us at help@ed-planner.com so we can sign a data processing agreement before any student accounts are created.

If you believe a child under 13 has created an account without parental consent, please email us and we will delete the account within 7 days.

9. Security

• All traffic is encrypted in transit with TLS 1.3.
• Data is encrypted at rest by Google Cloud.
• Access to each user's data is enforced by Firestore Security Rules scoped to the signed-in user's UID — your data is unreadable by any other user of the service.
• We never store your password. Passwords are handled by Google's Firebase Auth using salted hashing (scrypt).
• Google OAuth tokens are kept in browser sessionStorage (cleared when you close the tab) and never sent to our server.

10. Changes to this policy

We'll update this page as the app evolves. Material changes will be flagged with a banner inside the app the next time you sign in, and the "Last updated" date above will change. Continued use after the update counts as acceptance; if you disagree, you can close your account from Settings.

11. Contact

Data controller: Marc Curran (sole trader), operating as Ed Planner.
Email: help@ed-planner.com