Privacy Policy

Last Updated: September 14, 2026

Marthen-Huddle is built on a minimum-necessary principle: the platform holds the small amount of resident information that daily operations genuinely require — a name on an appointment, a discharge on the movement board, a grievance being followed to closure — and no clinical information at all. This policy explains what we collect, why, who processes it, how long it is kept, and the rights you can exercise.

Section 1 — Introduction and Scope

Marthen-Huddle ("we," "us," or "our") operates marthen-huddle.com and the Marthen-Huddle application (together, the "Service"). This Privacy Policy explains how we handle information when a senior living or skilled nursing organization ("Customer") and its staff use the Service, and when a visitor uses our public website.

This policy covers our own practices. It does not govern how a Customer uses the Service internally, nor the privacy practices of any third-party product a Customer chooses to connect.

Section 2 — What the Service Is, and Is Not

The Service is designed to hold operational data plus a narrow, defined set of resident-identifying fields. Clinical information — diagnoses, medications, treatment, assessments — must never be entered into any field.

Marthen-Huddle is an operational coordination platform for daily huddles, department check-ins, issue and grievance follow-up, census and staffing visibility, front-desk appointment and movement boards, staff recognition, internal messaging, and operational reporting.

The Service is NOT:

  • •An Electronic Health Record (EHR/EMR) or clinical documentation system
  • •A medication, treatment, orders, or clinical decision-support system
  • •A billing, claims, or payroll system
  • •The Customer's official system of record for grievance files or regulatory reporting

Section 3 — Our Role: Controller and Processor

If you are a resident, family member, or employee of a facility that uses Marthen-Huddle and you want to access or delete information about you, contact that facility directly. As processor, we support their request rather than acting on it independently.

For account and website information — registration details, billing, support requests, marketing enquiries, and usage analytics — we act as the controller (a "business" under California law) and this policy describes our own practices.

For operational data entered into the Service by a Customer's staff, including any Limited Resident Information, we act as a processor and service provider on that Customer's behalf. The Customer decides what is entered, who may see it, and how long their organization keeps it. We process it only to provide, secure, and support the Service under the Customer's instructions — never for our own marketing, and never sold or shared for cross-context behavioral advertising.

Section 4 — Information We Collect

4.1 Account and Organization Information

When an organization and its users are set up we collect:

  • •Full name, work email address, and job title
  • •Organization and community name, address, timezone, care types, and unit or bed counts
  • •Role, community assignments, and department, which determine what a user may access
  • •Authentication credentials, stored only in hashed and salted form — we never see your password
  • •Billing and subscription details, processed by our payment provider; we do not store full card numbers

4.2 Usage, Device, and Audit Data

We automatically collect technical and access records, including:

  • •IP address, browser and version, device type, and operating system
  • •Pages and features used, and the date and time of access
  • •Authentication events and administrative actions — invitations, role changes, and record changes — recorded in an audit log for the Customer's own oversight

4.3 Customer Operational Data

Staff enter operational content such as huddle records, department check-ins with OK/flag/N-A states and follow-up dates, who spoke for each department, issues and their disposition history, notes, recognition, census and staffing figures, PPD, staff absences, expected visitors, and internal messages between colleagues.

4.4 Limited Resident Information

Some operational features necessarily identify a resident. The Service is designed to collect only the following: resident first name and last initial (or the Customer's internal non-clinical identifier); appointment date, time, category, provider or clinic, and transport logistics; admission, discharge, or transfer date and operational reason category; and, for grievances, the complainant's name and relationship together with how the concern was addressed and resolved.

Diagnoses, medications, treatment plans, dates of birth, Social Security or insurance numbers, medical record numbers, photographs, biometrics, and behavioral-health, substance-use, HIV, genetic, or reproductive-health information must never be entered. A Business Associate Agreement is available on request for Customers whose compliance program requires one.

4.5 Connected Third-Party Data

If a user connects their own Google Calendar or Microsoft Outlook account, we retrieve the calendar entries needed to display their schedule alongside the huddle. We request the narrowest permissions that make the feature work, hold access tokens securely, and stop retrieving data when the user disconnects.

4.6 Website, Demo, and Support Communications

If you request a demo, download a resource, or contact us, we collect the name, work email, organization, and message you provide, and retain the correspondence to respond and to keep a record of what was agreed.

Section 5 — How We Use Information

We do not sell personal information, and we do not share it for cross-context behavioral advertising. We do not use Customer operational data to train publicly available or third-party foundation models for the benefit of other customers, and we do not use it for our own marketing.

We use information to:

  • •Provide, operate, secure, and maintain the Service, and separate each organization's data from every other organization's
  • •Create and administer accounts, roles, community assignments, and invitations
  • •Deliver notifications, huddle reminders, representative confirmation requests, and reports and exports you request
  • •Process payments and send billing and administrative messages
  • •Generate AI-assisted summaries and operational insights from your own data, for review by your own staff
  • •Respond to support requests and investigate suspected misuse, security incidents, or breaches of our Terms
  • •Produce aggregated, de-identified statistics to improve the Service
  • •Comply with law and enforce our Terms of Service

Section 6 — Legal Bases for Processing

Where the EU or UK GDPR applies, we rely on the following bases:

  • •Performance of a contract — to provide the Service to a Customer and administer accounts and billing
  • •Legitimate interests — to secure the platform, prevent misuse, maintain audit records, and improve the Service in ways that do not override individual rights
  • •Consent — for optional marketing communications and for connecting an individual's own calendar account, each withdrawable at any time
  • •Legal obligation — to meet tax, accounting, and lawful-request requirements

Where we act as a processor for a Customer, that Customer is responsible for establishing the lawful basis for the operational data it enters.

Section 7 — How We Share Information

We share information only as described here, and never for third-party advertising.

7.1 Subprocessors and Service Providers

We use vetted vendors to run the Service, in these categories: cloud application hosting and database infrastructure; transactional email delivery; payment processing; AI model providers for insight generation; product analytics and error monitoring; and, where a user connects one, calendar providers. Each is bound by contract to protect the data, use it only to perform services for us, and delete or return it when engagement ends. A current list of subprocessors is available on request.

7.2 Within the Customer's Organization

Operational data is visible to that Customer's Authorized Users according to their role and community assignment. Owners, administrators, and regional leaders may have visibility across communities in their organization. Deciding who holds those roles is the Customer's responsibility, not ours.

7.3 Legal Requirements

We may disclose information where required by law, regulation, subpoena, court order, or governmental authority, or where necessary to protect our rights, investigate fraud, or protect the safety of any person. Where we lawfully may, we notify the affected Customer before disclosing their data.

7.4 Business Transfers

In a merger, acquisition, financing, or sale of assets, information may transfer as part of that transaction, subject to this policy. We will notify affected Customers before their data becomes subject to a materially different policy.

7.5 With Your Direction or Consent

We share information for any other purpose only at your direction or with your consent — including when you connect an integration or export a report to a recipient of your choosing.

Section 8 — International Transfers

The Service is operated from the United States, and information is stored and processed there. If you access the Service from outside the United States, you understand that your information will be transferred to and processed in the United States, where privacy laws may differ from those in your jurisdiction. Where required, we use appropriate safeguards such as the European Commission's Standard Contractual Clauses with our subprocessors.

Section 9 — Data Retention

Historical huddle records are intentionally durable: a correction is recorded as a new entry that supersedes the earlier one rather than overwriting it, so the record of what was reported on a given day stays intact for the Customer's own accountability purposes.

We keep information only as long as needed for the purpose it was collected, then delete or anonymize it.

  • •Account and organization records — for the life of the account, then deleted or anonymized within ninety (90) days of closure
  • •Operational data, including huddle records, check-ins, issues, and Limited Resident Information — for the subscription term, then deleted or anonymized within ninety (90) days of account closure unless the Customer requests an export first
  • •Internal messages — purged automatically on a rolling retention schedule
  • •Audit and security logs — retained longer than operational data to support investigations and compliance oversight
  • •Billing and tax records — retained as long as financial and tax law requires
  • •Website, demo, and support enquiries — retained while a business relationship is reasonably contemplated, then deleted on request
  • •Routine encrypted backups — aged out on their own retention cycle after deletion from live systems

Section 10 — Security

No method of transmission or storage is completely secure, and exports downloaded from the Service leave our controls. We cannot guarantee absolute security, and Customers are responsible for protecting downloaded files and for the credentials of their own staff.

We apply technical and organizational safeguards appropriate to the sensitivity of the data, including:

  • •Encryption of data in transit (TLS) and at rest
  • •Hashed and salted credential storage — passwords are never stored or visible in readable form
  • •Tenant isolation, so each organization's data is segregated, plus row-level authorization enforced on the server rather than in the browser
  • •Role-based access control tied to organization role and community assignment
  • •Server-side authorization on every read and write, and audit logging of administrative and access events
  • •Least-privilege internal access, restricted to personnel who need it to operate or support the Service
  • •Secure OAuth token handling for connected calendar accounts, with the narrowest workable permissions
  • •Ongoing security review, dependency patching, and monitoring

If we become aware of a security breach affecting personal information we hold, we will notify affected Customers without undue delay, and within the timeframes required by applicable law or by an executed Business Associate Agreement, with the facts known at the time and the steps we are taking.

Section 11 — Your Privacy Rights

Depending on where you live, you may have the right to:

  • •Know what personal information we hold about you, and how it is used and disclosed
  • •Access a copy of it, or receive it in a portable format
  • •Correct information that is inaccurate
  • •Delete it, subject to legal and contractual retention requirements
  • •Limit the use and disclosure of sensitive personal information
  • •Object to or restrict certain processing, and withdraw consent where processing relies on it
  • •Be free from discrimination for exercising any of these rights
  • •Appeal a refusal, or lodge a complaint with your data protection authority or state attorney general

California residents may designate an authorized agent to make a request on their behalf; we will verify the agent's authority and your identity before acting. We do not sell personal information or share it for cross-context behavioral advertising, so no "Do Not Sell or Share" mechanism is required. We respond to requests within the period required by law — generally forty-five (45) days, extendable once where permitted.

You may submit a request by email to info@marthenhuddle.com or through the contact form on our website. If your request concerns operational data held on behalf of a facility, we will refer you to that facility as the controller and support their handling of it.

Section 12 — Cookies and Analytics

We use cookies and similar technologies that are strictly necessary to keep you signed in, maintain session state, and remember your preferences such as your selected community. We also use limited product analytics and error monitoring to understand which features are used and to diagnose faults.

We do not use advertising or cross-site tracking cookies. You can block or delete cookies in your browser, though the Service may not function correctly without the necessary ones.

Section 13 — Automated Processing and AI

The Service uses AI-assisted processing to summarize huddle activity, highlight patterns across flags and issues, and draft operational insights from a Customer's own data. Outputs are suggestions for review by the Customer's staff.

No automated processing in the Service makes a decision that produces a legal or similarly significant effect on any individual — it does not decide anything about a resident's care, an employee's status, or a regulatory obligation. A person always remains in the loop, and a Customer may contact us to request human review of any output.

Section 14 — Children's Privacy

The Service is intended for use by healthcare and senior living professionals in the course of their work. We do not knowingly collect personal information from anyone under 18 as a user of the Service. If we learn that we have, we will delete it promptly.

Section 15 — Changes to This Policy

We may update this policy as the Service and the law evolve. We will revise the "Last Updated" date above and, for material changes affecting how we handle personal information, notify active Customers by email or in-app notification before the change takes effect. Continued use afterwards constitutes acceptance.

Section 16 — Contact Us

For privacy questions, a data subject or consumer request, a subprocessor list, a Data Processing Addendum, or a Business Associate Agreement, contact:

Marthen-Huddle

Email: info@marthenhuddle.com

Privacy requests: info@marthenhuddle.com

Website: marthen-huddle.com

This policy describes our practices for transparency and is not legal advice to you.

See your own huddle in it

A twenty-minute working session, not a sales pitch. We will walk through your current huddle and show you exactly what is falling through.