What mdash reads, and what it does with it.
mdash is a private household dashboard. It reads the calendars and rings the people in a household connect, and shows them one shared view of the day. It is not advertising-supported, it runs no analytics, and there is no third party it sends your data to.
Everyone in a household signs in as themselves and connects their own accounts. Nobody connects an account on someone else’s behalf, and nobody can see another person’s data except through the household views described below.
Google Calendar data
With your permission mdash requests one scope, calendar.readonly, and no other.
- What is read. Event titles, times, locations, attendee counts and free/busy status, for the calendars you choose to connect.
- What is stored. A normalised copy of those events in mdash’s own database, so a screen can be drawn without calling Google on every view. Access and refresh tokens are stored encrypted.
- What is never done. mdash never writes to a calendar. It does not create, move, or delete events, and it does not read calendars you have not connected.
- Who sees it. Only members of your household, subject to the visibility each person sets for themselves.
Google user data is never sold, never used for advertising, never used to train a model, and never transferred to anyone except as required to operate mdash for you. Its use adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Oura data
If you connect a ring, mdash requests one of Oura’s eight scopes — daily, covering the sleep, activity and readiness summaries for a day. It does not request the continuous heart-rate series, which is the most sensitive thing a ring exposes, and it does not request your Oura email address. What a ring reports is visible to you; whether the rest of the household sees your recovery is a setting you control, and it is off until you turn it on.
Calendar feeds and recipes
A published ICS calendar is fetched by URL and needs no account. Recipes you import are fetched from the page you point at, and photographs you upload for import are stored in object storage owned by this deployment.
Sign-in
Signing in is a link sent to your email address. mdash stores that address, a session record, and nothing else about your identity. There is no password to reuse or leak. Signing in and connecting a calendar are separate decisions, and either can be undone without the other.
Disconnecting, and deletion
Disconnecting a calendar or a ring revokes the grant with the provider directly, not only in mdash — so the app stops appearing in your Google or Oura account permissions rather than lingering there with access you believe you removed. The stored data for that connection is deleted at the same time.
To delete your account and everything associated with it, ask the person who administers your household, or write to the address below. Removing a member from a household revokes their sessions server-side immediately.
Retention and security
Calendar events are retained only for the window the dashboard displays and are replaced on each sync; older rows are pruned automatically. OAuth tokens are encrypted at rest. Data is held in a managed Postgres database and served only over HTTPS.
Changes, and getting in touch
If this policy changes in a way that affects what is read or who can see it, the date at the top changes and the change is described here. Questions about any of the above go to alyssa.rae.fox@gmail.com.