Privacy Policy

DMO is a platform for teams and communities (“Studios”): daily checklists, a community feed, chat, courses, events, Team Hub pipelines, Run Mode, the Skill Matrix, bubble charts and member cards. It's operated by Daily Method (“we”, “us”) at https://dailymethod.app and its Studio subdomains.

This policy explains what personal information we handle, why, who we share it with, how long we keep it, and the choices and rights you have. It applies to the website, the apps and the public pages a Studio publishes on DMO.

There are two kinds of information here, and responsibility differs:

• Your account (name, email, password, time zone, profile photo) belongs to your DMO account, and we're responsible for it.
• What you do inside a Studio (posts, messages, checklists, sales and recruit entries, leads, course progress and so on) is held on behalf of that Studio. The Studio's owner decides how its Studio is run and is responsible for how they use its members' information; we process it for them under these terms. Questions about a Studio's own practices should go to its owner first. We'll help.

You give us:

• Account details: name, email address, password (stored only as a salted hash), time zone, and an optional profile photo.
• Studio profile: headline, bio and any profile fields a Studio asks for.
• Content: posts, comments, reactions, polls, chat messages, files, images, audio and video you upload, event RSVPs, course progress and quiz answers.
• Work records: daily, weekly, monthly and one-time checklist completions; Run Mode sales (date, institution, product, reference premium, points) and recruits; monthly goals; Skill Matrix ticks; bubble charts (including names, agent codes and photos of people in your organisation); Team Hub leads.
• Member card details you choose to show: phone and email.
• Payment details when you buy a Studio plan. Card details go directly to Stripe; we never see or store card numbers.
• Messages to us, for example support requests.

Information about other people you add. Leads, bubble chart entries and similar records can include other people's names and contact details. Only add people where you have a legitimate reason and, where required, their consent.

Visitors to a member card. If you leave your details on someone's card (name, and optionally phone and email), they go to that member as a lead in their Studio. You're contacted by that member, not by us.

Collected automatically:

• Technical data: IP address, browser and device information, and timestamps, used to keep the service secure, limit abuse and troubleshoot.
• Activity: when you were last active in a Studio, and an audit log of important actions (for example, changes to settings, access and payments).
• Cookies and similar storage; see section 9.

We don't use advertising trackers or sell analytics about you.

• To provide the service: show your checklists, feed, chats, courses, dashboards and reports; calculate points from the product rates a Studio sets; deliver notifications and emails you've opted into.
• To run Studios: let owners and admins manage members, access, goals and reports. Studio owners and admins can see members' activity within their Studio as the features describe (for example, team results, report pages and team dashboards).
• To process payments through Stripe on behalf of Studios, and to record the platform fee.
• To keep things secure: authentication, rate limiting, preventing spam on public forms, investigating misuse, and keeping audit logs.
• To support you and to tell you about important changes to the service or these documents.
• Optional AI features: if a Studio turns on DMO AI, the text needed for a request (for example a thread to summarise or a draft to improve) is sent to our AI provider to produce the result. It isn't used to train their models under our agreement with them.

Where the law requires a legal basis, we rely on performing our contract with you or the Studio, our legitimate interests in running a secure and useful service, your consent (for example, optional emails), and legal obligations.

• Studio owners and admins can manage their Studio's members and see Studio data that the features expose to them. Bubble charts are private to their owner; staff can view one only in a time-limited, read-only support view with a stated reason, and the chart's owner can see each such visit in Settings → Chart access log.
• Our staff (platform administrators) can access Studios to provide support, investigate abuse or meet legal obligations. These visits are recorded in the audit log.

We share personal information only as needed to run the service, with these kinds of providers acting on our instructions:

• Hosting and database: Railway (application servers and database).
• File storage: our servers or Cloudflare R2.
• Email delivery: Resend.
• Payments: Stripe, including Stripe Connect for Studios that sell plans. Stripe's own privacy policy applies to the payment information you give them.
• Optional services a deployment may use: Ably (live updates), Inngest (background jobs), Anthropic (DMO AI), Apple and Google (if you add your member card to a wallet).

Inside a Studio, what you post or share is visible to the people that feature is designed for (for example, members of a space, the people in a chat, or your Studio's admins). A member card and its public page are visible to anyone with the link.

We may disclose information if required by law, to protect people's safety, or as part of a merger or sale of the service (with notice to you). We don't sell personal information and we don't share it for cross-context behavioural advertising.

Our main servers and database are in the United States (California). Some providers process data in other countries. Where data leaves your country, we rely on the protections required by applicable law, such as contractual safeguards.

• Account data: for as long as your account is open.
• Studio data: for as long as the Studio exists, or until it's deleted by you, the Studio, or under section 10. Some features keep a history on purpose (for example, past checklist periods and logged sales), and past sales keep the rates they were logged with.
• Audit and security logs: for as long as reasonably needed for security, disputes and legal obligations.
• Payment records: as long as tax and accounting law requires.
• Backups: deleted data can remain in backups for a limited period before it's overwritten.

We use only what the service needs to work:

• Sign-in session cookie: keeps you signed in (required).
• Preference cookie (dmo_sidebar): remembers whether you collapsed the sidebar.
• Local storage: your light or dark theme, and which checklist headings you collapsed.

There are no advertising or third-party analytics cookies. You can clear cookies in your browser; you'll be signed out.

• Edit your profile (name, photo, headline, bio) from the profile menu or Settings.
• Download your data: Settings → Your data gives you everything a Studio holds about you, as a file.
• Delete your data in a Studio: Settings → Your data lets you erase your membership data in that Studio.
• Email preferences: unsubscribe from Studio newsletters with the link in each email or in Settings.
• Member card: switch it off or make a new link at any time; old QR codes stop working.

Depending on where you live (for example under Canada's PIPEDA, the GDPR or UK GDPR, or US state laws such as the CCPA), you may have rights to access, correct, delete or port your information, to object to or restrict some processing, and to withdraw consent. To use them, or to close your account, email privacy@dailymethod.app. We'll verify your request and respond within the time the law requires. For data a Studio controls, we may pass your request to its owner. You also have the right to complain to your data-protection authority.

We protect information with encrypted connections (HTTPS), hashed passwords, private file storage with short-lived links, and strict separation between Studios in our database (each Studio can only reach its own data). Access is limited to people who need it, and important actions are logged.

No system is perfectly secure. If we learn of a breach that affects your information, we'll notify you and the authorities as the law requires.

DMO isn't meant for anyone under 16, and we don't knowingly collect their information. If you think a child has given us information, contact us and we'll delete it.

We'll update this policy as the service changes. The effective date at the top shows the current version. For significant changes we'll tell you in the app or by email before they take effect.

Daily Method · privacy@dailymethod.app (privacy) · support@dailymethod.app (everything else).