Privacy Policy

Daymatter is a small, invite-only beta. This policy explains what we collect, why we collect it, and how to contact us about your data.

Who runs Daymatter

Daymatter is operated from Poland. For privacy questions, deletion requests, export requests, or corrections, email [email protected].

Data we collect before an account

When you request closed beta access, we collect the information needed to review and manage that request.

  • Email address.
  • Waitlist profile selection.
  • Planning challenge text.
  • Submission source and submitted timestamp.
  • Manual review status, review notes, invited timestamp, invite expiration, invite acceptance timestamp, and accepted user reference.
  • Hashed IP address and hashed user-agent metadata for abuse prevention and operational safety.

Data we collect after account creation

If you accept an invite and 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.
  • Timezone and onboarding responses, including your onboarding goal.
  • Activation and onboarding events such as first Cycle Plan, first Today, and first Retro completion.
  • Planning content you enter in the app, including tasks, routines, projects, agenda items, subtasks, cycle plans, retros, and related notes.
  • Session and security metadata needed to keep you signed in and protect the service.

How we use data

We use this data to run the waitlist, manually review beta fit, send invites, provide beta accounts, secure the service, debug errors, understand aggregate activation, and improve onboarding.

We do not sell personal data. Closed beta contact is limited to Daymatter access, product updates, and feedback related to the beta.

Processors and service providers

Daymatter uses a small set of service providers to operate the product.

  • Railway for application hosting and infrastructure.
  • Resend for transactional email such as invites and account email.
  • Cloudflare for DNS, security, and traffic protection.
  • Sentry for error monitoring and diagnostics. Diagnostic events may include technical context needed to debug failures.
  • Plausible for aggregate analytics once enabled for public and product events.

Analytics boundary

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, waitlist submit success, invite page views, and signup completion.

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

Retention, deletion, and export

We keep waitlist data while reviewing beta waves and operating the invite-gated beta. 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 request deletion or export by emailing [email protected]. We may need to verify that the request comes from the relevant account or waitlist email address.

Your choices and rights

Depending on where you live, you may have rights to access, correct, delete, restrict, object to, or export personal data. Email [email protected] and we will handle the request through that contact path.

Security

Invite tokens are stored as non-reversible hashes. Waitlist IP addresses and user agents are stored as hashes for abuse prevention. We use reasonable technical and organizational safeguards for a small closed beta, but no internet service can guarantee perfect security.