Privacy Policy

Daymatter is run from Poland by Marcin Kołodziej (sole proprietor), Polish tax ID (NIP) 6351851726, with a business address at Profilowa 4D, 43-175 Wyry, Poland, who is the controller of the personal data described in this policy.

For privacy questions, deletion requests, export requests, or corrections, email [email protected].

If you sign in with Google, Google gives Daymatter your Google account email address, name, and Google account identifier.

We use this data to create your Daymatter account, sign you in, and link Google sign-in to an existing account.

If you sign in with Apple, Apple gives Daymatter an Apple account identifier and the email address you choose to share, which is either your own address or a private relay address that Apple forwards to you. The first time you sign in, Apple also shares the name you choose to share.

We use this data to create your Daymatter account, sign you in, and link Sign in with Apple to an existing account with the same verified email address. Email we send to a private relay address reaches you through Apple.

We also store, encrypted, the refresh token Apple issues when you sign in. We use it only to revoke Daymatter’s access to your Apple ID when you delete your account. If you stop using Sign in with Apple for Daymatter in your Apple ID settings, Apple tells us, and we remove the Apple identifier and the token from your account.

Waitlist data collected during the closed beta is no longer used and is deleted. Copies of it may remain in our backups for a limited time.

When you create an account, Daymatter stores the information needed to provide the beta product.

• Account identity data such as name, email address, password hash, email verification state, and optional two-factor authentication data.
• A requested new email address while an email change is waiting for your confirmation.
• Timezone, language, and onboarding responses, including your onboarding goal.
• Activation and onboarding events such as your first opening of Today; older accounts may also hold a record that they once planned a Cycle or wrote a Retro; the plans and notes themselves are deleted.
• The calendar days on which your account was used, as dates only, without content or IP address. We use them to understand whether people come back after signing up.
• Your sign-up source: the UTM parameters of the link you arrived with, the host of the website that referred you, the page you landed on (without any token or other query string), whether you signed up on the web, the desktop app, or the mobile app, and the time of your first visit. Before you sign up this is kept only in your session record on our server (the one your session cookie points to), with no additional cookie, and it disappears when the session expires.
• Content you enter in the app: tasks, subtasks, routines, areas, agenda items (events), shopping lists, tags, and notes.
• Feedback you send with the in-app Feedback form: your message, its type and impact, the screen and page path you sent it from, and whether you are open to follow-up.
• For each mobile app sign-in, a device session with the platform, the app version, and when it was last used, so you can review and sign out devices in Settings.
• Session and security metadata needed to keep you signed in and protect the service, including the IP address and browser user agent stored with each browser session.

When you write to [email protected] or reply to one of our emails, we process your email address, the content of the correspondence, and the details you give in it, so that we can answer, help with your matter, and handle a complaint or a data request. We keep it until the matter is resolved and then for at most 12 months, unless we need it longer to establish, pursue, or defend legal claims.

If you ask on the Daymatter website to hear when an app that is not available yet is released, such as the desktop or mobile app, we store your email address, the apps you chose, the language of the page, and when you first and most recently gave your consent.

We use this data only to email you when an app you chose becomes available. We store it only with your consent, and you can withdraw that consent at any time with the unsubscribe link in every launch email, which works without signing in and deletes this data, or by emailing [email protected].

We keep this data until we have sent the launch email for every app you chose, or until you unsubscribe or ask us to delete it, whichever comes first. Each launch email removes the apps it announces from the data we keep.

We use the account data, Google sign-in data, and Sign in with Apple data described above to provide beta accounts, secure the service, debug errors, understand activation, whether people come back, and where sign-ups come from, and improve onboarding.

App launch notification data is used only as described in the App launch notifications section: to email you when an app you chose becomes available.

We do not sell personal data. We write to account holders only about access to Daymatter, announcements about changes to the service or these documents, and feedback about the beta.

You can let an AI assistant or another MCP client work with your Daymatter data. MCP access is off until you turn it on in Settings → Security, and you then create a credential for each client. A credential has the access you choose (read-only, read and write, or full access) and expires after 90 days unless you choose another lifetime of at most one year.

A client with a credential can read your planning content and, with write or full access, create, change, and delete it, as you can in the app. What the client and its AI provider do with the data they read is governed by their own terms and privacy policies, not by this policy, so connect only clients you trust.

You can revoke a credential in Settings → Security at any time. Turning MCP access off stops every credential from working, and deleting your account revokes them all. We store only a hash of each credential, with its name, access, expiry, and when it was last used. A revoked credential is deleted at once, and an expired one 30 days after it expired.

To secure the service and investigate misuse, we keep an audit record of MCP activity. It contains no planning content, only a pseudonymous account reference (a one-way hash of the account identifier), the credential’s identifier, the tool and operation, the result, and a duration range. We keep audit records for security monitoring for up to 90 days.

We process account data, sign-in data, planning content, feedback, and MCP credentials to provide the Daymatter service you sign up for, under Article 6(1)(b) GDPR (performance of a contract).

We process session and security metadata, MCP audit records, error diagnostics, aggregate analytics, and the days-of-use and sign-up source records on the basis of our legitimate interests in keeping the service secure, preventing abuse, fixing errors, understanding how the product is used, and learning whether the beta works for the people who join it, under Article 6(1)(f) GDPR. You can object to this processing by emailing [email protected].

We process correspondence in order to answer your message: for account matters under Article 6(1)(b) GDPR, for other messages on the basis of our legitimate interests under Article 6(1)(f) GDPR, and for complaints and data requests to meet a legal obligation under Article 6(1)(c) GDPR.

We store app launch notification data only with your consent, under Article 6(1)(a) GDPR. You can withdraw it at any time, as described in the App launch notifications section, without affecting the processing before you withdrew it.

Where the law requires us to keep or disclose data, we do so to meet that legal obligation, under Article 6(1)(c) GDPR.

Providing data is voluntary, but without an email address and a password (or Google or Apple sign-in) you cannot create an account, and without an email address you cannot sign up for an app launch notification.

We do not make decisions about you based solely on automated processing, including profiling, that produce legal effects concerning you or similarly significantly affect you.

Daymatter uses a small set of service providers to operate the product. They process data on our behalf, while Apple and Google act as independent controllers, on their own terms, for sign-in and app distribution.

• Railway for application hosting and infrastructure.
• Resend for transactional email such as account verification and password reset messages, and for the one-time launch email about each app you asked to hear about.
• Cloudflare for DNS, security, traffic protection, and forwarding the email sent to [email protected].
• Google Workspace for the mailbox that receives the email sent to [email protected].
• Sentry for error monitoring and diagnostics on the server, on the web, and in the mobile app, with data stored in the EU region. Error reports may include technical context needed to fix them, such as the app version, the device platform, and the internal account ID.
• Plausible for cookieless, aggregate analytics of page views and product events on the website and in the mobile app.
• Discord for internal notifications to the Daymatter team when an account is created or feedback is sent. These notifications state only that it happened, with the sign-up method and time, and contain no name, email address, or feedback text.
• Apple for Sign in with Apple, its private email relay, and distributing the iOS app through TestFlight and the App Store.
• Google for Google sign-in.
• Expo for building the mobile app and delivering its updates. When the app checks for an update, Expo receives technical request data such as the IP address, the app version, the platform, and a random installation identifier.

Some of these providers, including Railway, Cloudflare, Google, Sentry, Resend, Discord, Apple, and Expo, may process personal data outside the European Economic Area, for example in the United States.

Where they do, the transfer relies on a safeguard the GDPR recognises, such as an adequacy decision of the European Commission (including the EU-U.S. Data Privacy Framework for providers certified under it) or the European Commission’s standard contractual clauses in the provider’s data processing terms. You can ask for more information about these safeguards at [email protected].

The website and web app use only cookies that are strictly necessary for the service you ask for: a session cookie that keeps you signed in, an XSRF security cookie that protects forms against cross-site request forgery, and, if you choose to stay signed in, a remember-me cookie. The other cookies only remember a choice you make: your language, your appearance setting, whether the sidebar is collapsed, and whether keyboard mode is on. The appearance setting and keyboard mode are also kept in the browser’s local storage (localStorage).

The session cookie points to a session record on our server that stores the IP address and browser user agent of the browser, also for visitors who are not signed in. The record is deleted after the session expires.

Daymatter uses no advertising or tracking cookies, and Plausible analytics works without cookies, so the site does not ask for cookie consent. The mobile app keeps its sign-in credentials in the device’s secure storage.

Database activation events are the product source of truth for Daymatter activation. Plausible is used only for aggregate public and product analytics such as landing page views.

Plausible is not used as the activation source of truth and is not used to evaluate individual planning content.

The days-of-use and sign-up source records described above are first-party records in the Daymatter database. They are not sent to Plausible.

When an account whose email address was never verified is deleted, we keep only an anonymous count per sign-up date and sign-up source. The count holds no email address, name, or account identifier.

An account whose email address is never verified is deleted automatically after 14 days. A requested email change that is not confirmed expires after 7 days.

The days-of-use and sign-up source records stay with your account and are deleted together with it.

We keep account and app data while your account exists or while needed to operate the beta, protect the service, comply with legal obligations, or resolve abuse and security issues.

You can delete your account yourself at any time: on the web in Settings → Profile → Delete account, and in the mobile app in More → Settings → Delete account. Deleting your account is permanent and covers all your content, and if you signed in with Apple it also revokes Daymatter’s access to your Apple ID. Copies of deleted data can remain in our hosting provider’s backups for a limited time, until they are overwritten in the normal cycle; we do not restore them for any other purpose.

You can request deletion or export by emailing [email protected]. We answer within 30 days, and an export is a copy of your account data and planning content in a machine-readable format. We may need to verify that the request comes from the relevant account email address.

Under the GDPR you have the right to access, correct, delete, restrict, object to, and export your personal data, and to withdraw a consent at any time. Email [email protected] and we will handle the request through that contact path.

You also have the right to lodge a complaint with a data protection supervisory authority: in Poland, the President of the Personal Data Protection Office (Prezes Urzędu Ochrony Danych Osobowych, UODO; ul. Stawki 2, 00-193 Warsaw, uodo.gov.pl), or the authority of the country where you live or work.

We apply appropriate technical and organizational measures, including encrypted connections (HTTPS), storing passwords and credentials only as hashes, and encrypting sensitive tokens. No internet service can guarantee perfect security, however.

We update this policy when Daymatter changes how it handles personal data. The effective date on this page shows when the current version took effect. We email you about material changes.