Privacy Policy
Last updated: 22 November 2026
The short version: we process only what Eddyday needs to work, we keep the data of the app with Scaleway in France and the Netherlands, and we never sell it or use it for advertising. This website sets no cookies, runs no scripts and uses no tracking.
Who is responsible
The controller under the General Data Protection Regulation (GDPR) is:
Sven Wiegand
Im Grund 22
13591 Berlin
Germany
Email: hello@eddyday.com
See also the Legal Notice.
This website
When you open eddyday.com, the web server writes each request to a log: your IP address, the time, the page asked for, the answer, the referring page and the name of your browser. We need it to deliver the pages and to recognise faults and attacks (legitimate interest, Art. 6(1)(f) GDPR). The logs are deleted after 7 days.
The website sets no cookies, runs no scripts, and loads nothing from other servers: fonts, styles and pictures come from eddyday.com itself. There is no analytics.
The waitlist
To join the waitlist, you enter your email address on this website. Our server then sends you an email with a link to confirm it (double opt-in), so that nobody can put someone else’s address on the list. Until you confirm, we keep the address, the language of the page and the time of the sign-up. If you don’t confirm within 7 days, we delete it.
Once you confirm, we keep your address, its language and the times of sign-up and confirmation until Eddyday opens for you or until you remove it. We use it only to tell you when you can start using Eddyday; there is no newsletter. When you confirm, we get a short email with your address. Every later email contains a link to remove your address, and you can always write to us instead.
The legal basis is your consent (Art. 6(1)(a) GDPR), which you can withdraw at any time. The list is stored in our database in Paris, the emails are sent by Scaleway. The links in our emails are stored only as hashes, and to protect the form from abuse, our server counts sign-ups per IP address for one hour, in memory only.
If you write to hello@eddyday.com, we process your address and your message to answer you (Art. 6(1)(b) and (f) GDPR) and keep them as long as the conversation needs, at most until you ask us to delete them.
Our email provider is Fastmail Pty Ltd (Melbourne, Australia), whose servers we use in its EU region. Where Fastmail processes data outside the EU, the transfer is covered by the EU Standard Contractual Clauses in its data processing agreement.
Booking pages
With an Eddyday booking link, someone who uses Eddyday lets you choose a time for a meeting with them. To book, you enter your name and email address.
Our server passes them on to Microsoft only to create the event in the calendar of the person you book with; Microsoft Outlook then sends you the invitation from their mailbox. That person also gets a short email from Eddyday with your name. Eddyday does not store your name or address: they go neither into our database nor into a log. We keep only the time of the booking, without any data about you, until the meeting is over. Requests to the booking page are not logged by the web server.
The legal basis is the booking you ask for (Art. 6(1)(b) GDPR) and the interest of the person you book with in arranging the meeting (Art. 6(1)(f) GDPR). For the event in their calendar, Microsoft and the organisation of that person are responsible.
To protect the page from abuse, our server counts requests per IP address for one minute, in memory only.
The Eddyday app
Eddyday is in private beta: only people we have invited can sign in. We process their data to provide the app (Art. 6(1)(b) GDPR).
- Account: your email address, your name, language and time zone. You sign in with a six-digit code that we send by email; it is valid for 10 minutes and stored only as a hash. A sign-in session lasts 90 days from its last use and stores the IP address and browser or device it began from. To limit abuse, we count codes per email address (as a keyed hash, for one hour) and per IP address (in memory, for one minute).
- Your content: tasks, subtasks, projects, tags, goals, comments, links, attachments, plans and settings. The app stores them on your device and synchronises them with our server, so that they reach your other devices and survive the loss of one. Each change to a task is kept in its history.
- Links: when you add a link, Eddyday fetches the page once to show its title and icon: on the Mac directly from your device, in the web app through our server. The website you link to sees that request.
- Attachments are stored on our servers at Scaleway (Object Storage).
- Backups on your Mac: the Mac app keeps a daily copy of its database on your device, the newest 7. Signing out deletes them.
- Backups on our side: our database makes a daily backup that is kept for 7 days, and we keep a daily copy of the database for 30 days to restore from it after an error.
- Logs: our servers log technical events, with the IDs of accounts but without the content of tasks, mails or events. Logs are kept for 7 days, those of the database for up to 30 days.
- Updates: the Mac app asks our server for a newer version when it starts and every six hours, sending only its version and platform.
- Web app: the session is a cookie that only our server can read (90 days). Your data and attachments are kept in your browser’s storage for the app; signing out deletes them.
The app contains no tracking, no analytics and no crash reporting. You can export your data from the settings at any time (JSON and Markdown). The iPad and iPhone app is distributed through Apple’s TestFlight, for which Apple is responsible.
Microsoft 365
Only if you connect your Microsoft work account yourself, Eddyday accesses it through Microsoft Graph, for the areas you choose (Art. 6(1)(b) GDPR). The access tokens stay on our server only, encrypted, and never reach your devices.
- Calendar: Eddyday reads your events from yesterday to 14 days ahead (title, time, place, organiser, attendees, description) and shows them in the app; Microsoft tells our server when they change. Events that no longer come from Microsoft are deleted. Calendar rules and booking links write events into your calendar.
- Mail: when you turn a mail into a task with the Outlook add-in, Eddyday stores its text, sender, recipients and the names of its attachments with the task. Eddyday reads the mail and does not change it. If you remove the mail from the task or delete the task, the mail is deleted for good after 30 days; its subject remains as the title of the task.
- Teams: you can grant the permission, which we keep for planned features. Until then, Eddyday reads nothing beyond a check that the connection works.
When you disconnect an area, Eddyday deletes its events and the tokens; mails already attached to tasks stay with them. Disconnecting does not withdraw the permission at Microsoft; you can do that in your Microsoft account. Microsoft and your organisation are responsible for the data in Microsoft 365 itself.
AI assistants (MCP)
You can connect an AI assistant such as Claude to Eddyday over the Model Context Protocol. It gets access only after you agree on a page that names it, and only to the tasks, projects, tags, goals, comments, history and calendar events of your account. Mails attached to tasks and booking links stay out of reach.
We store the tokens of the assistant only as hashes; access lapses after 90 days without use, and you can disconnect it in the settings at any time, which takes effect at once. Changes made by an assistant show its name in the history. What the assistant does with the data is the responsibility of its provider and is governed by your agreement with them.
Processors and location
- Scaleway SAS (Paris, France): servers, database, file storage, sending of emails, logs, DNS. All data of the app is stored in Paris; the daily copy of the database in Amsterdam (Netherlands).
- Fastmail Pty Ltd (Melbourne, Australia): our email, see Email.
Microsoft and AI assistants receive data only when you connect them yourself; they act as services you use, not as our processors. We do not sell or share personal data for any other purpose.
How long we keep data
- Logs of this website and of our servers: 7 days; logs of the database: 30 days.
- Sign-in codes: 10 minutes; sign-in sessions: 90 days after their last use.
- Bookings: until the meeting is over, at least 24 hours; without your name or address.
- Waitlist: unconfirmed addresses for 7 days; confirmed ones until Eddyday opens for you or you remove them.
- Content of your account: as long as the account exists. Deleted tasks and comments are only marked as deleted so that they can be restored and synchronised; removed attachments are deleted for good after 30 days.
- Mails attached to tasks: as long as the task; removed ones for 30 days.
- Calendar events: as long as Microsoft delivers them, until you disconnect.
- Backups: 7 days for the database backup, 30 days for the daily copy, 7 days on your Mac.
To delete your account with all its data, write to us at hello@eddyday.com; we delete it within one month. Copies in backups disappear when the backups expire, after at most 30 days.
Your rights
You have the right to access your data (Art. 15 GDPR), to have it corrected (Art. 16) or deleted (Art. 17), to restrict its processing (Art. 18), to receive it in a portable format (Art. 20) and to object to processing based on legitimate interest (Art. 21). Where we process data with your consent, you can withdraw it at any time with effect for the future (Art. 7(3)). Write to hello@eddyday.com.
We do not make automated decisions about you, nor do we use profiling.
Complaints
You can complain to a data protection authority, for example to the one responsible for us: Berliner Beauftragte für Datenschutz und Informationsfreiheit, Alt-Moabit 59–61, 10555 Berlin, Germany, datenschutz-berlin.de.
Changes to this policy
When Eddyday starts processing data in a new way, we update this policy and the date at the top.
