Legal Document Changes

Initial public version of the Terms of Service.

Rewrites the cookies section to match what the Service actually does. States that we use no advertising or analytics cookies and no third-party analytics; lists the one sign-in cookie and the browser storage the app uses; and explains the new cookie-free website visit counts (what is stored, what is never stored, kept 13 months). Says plainly where an IP address does appear: a one-way hash kept briefly for abuse limits, and Google Cloud request logs kept 30 days. Removes the promise of a cookie banner, since no non-essential cookies are used. Also discloses the app's own product-usage records (sign-ins, clock-ins, exports and similar; identifiers and counts only, kept in our own database, not deleted on a schedule). Describes existing practice; no new data flow.

Adds Firebase Cloud Messaging (push notifications) to the subprocessor list and explains what is sent (generic notification text, with no client, family-member or caregiver names and no text typed by a user), that it is not covered by a business associate agreement, and how to turn notifications off. Describes more precisely what Google Maps Platform receives (typed address text sent from the browser; latitude/longitude pairs sent from our servers) and states that both services operate under Google's own terms. Also corrects the incident-response statement: it said HIPAA breach notification within 48 hours of Discovery, which is stricter than our contracts; it now says without unreasonable delay and no later than 60 days after Discovery, matching the Business Associate Agreement, the Master Services Agreement and our other privacy policy. Describes existing practice already disclosed in the BAA and DPA (v7, 2026-08-25); no new data flow.

Corrects the Google Maps Platform subprocessor row in the §8 table, which still read "Google Cloud BAA" after the BAA and DPA were corrected on this point 2026-08-25. Now states the integration is not covered by the Google Cloud BAA, matching those two documents. Also broadens the Purpose description, which described only EVV route display, to cover both actual data flows: server-side travel-time/mileage calculation using GPS coordinates only, and address autocomplete when staff enter a client's, employee's, or shift's street address — not only EVV — which sends that address text directly from the browser to Google, not through our servers, and can include a client's home address. This corrects the document to describe the existing integration accurately — no new subprocessor and no change to what data is shared or with whom.

Removes "Firebase Data Connect" from the Exhibit A Google Cloud Platform subprocessor row. Data Connect was decommissioned 2026-06-19; the application now talks to Cloud SQL directly via node-postgres and the Cloud SQL Connector, which the row already lists as "Cloud SQL." This corrects the document to describe existing infrastructure accurately — no new subprocessor, no change to what data is shared or with whom.

Restores the Plaid Inc. subprocessor row to the Exhibit A subprocessor table and scopes it explicitly to the Fiduciary Operations module. The underlying data practice is unchanged — Plaid is unavailable to home-care-only Customers, and even on the fiduciary module is invoked only where a Customer has enabled bank-account linking and an authorized user initiates the OAuth flow. This corrects the document to describe existing practice accurately rather than announcing a new practice.

Google API verification update: §6 names the exact Google Calendar OAuth scopes and adds disconnect/revoke language; §11 adds a Google Calendar token-retention line. Limited Use disclosure clarified.

Public-facing Privacy Policy displayed at /privacy.