Privacy Policy

Effective: 3 November 2026. Version: privacy-2026-11-03.

This Privacy Policy describes how Viva Longer LLC, a California limited liability company doing business as Ashby Care (“we,” “us,” “our,” “Ashby”), collects, uses, and discloses information in connection with ashbycare.com, the Ashby Care staff and parent applications, and related services (collectively, the “Services”).

Please read this Privacy Policy carefully. If you do not agree, do not use the Services. Centers accept this notice, together with the Terms of Service and Data Processing Addendum, by clickwrap at organization signup. Section 15 explains how we tell Centers about a new version.

1. Who we are

Viva Longer LLC d/b/a Ashby Care 548 Market St PMB 649504 San Francisco, CA 94104-5401 United States

Privacy: privacy@ashbycare.com

We provide software to childcare programs in the United States, including licensed programs, programs preparing to open, and license-exempt programs. We are not a childcare provider, school district, or health plan.

2. Who this notice covers

This notice covers three audiences. The rules are not the same for each.

Website visitors. If you browse ashbycare.com without an account, we are the business that collects limited information about that visit (see Section 4). We are also the business for the sign-up measurement described in Section 4.

Center staff and owners. If you have an Ashby Care account for a childcare organization (the “Center”), we process your account information to run the Services. For child and family records the Center stores in the product, we act as the Center’s service provider / processor. The Center decides what to collect.

Parents and guardians. If a Center invited you, that Center is your vendor for your child’s program. We store records for the Center. We are not your childcare provider. Ask the Center to access, correct, or delete your family’s records, or to change a consent. We will assist the Center.

3. Our roles

State comprehensive privacy laws (including the California Consumer Privacy Act as amended by the CPRA, and similar state laws). For Customer Data the Center submits, the Center is the Business (or controller). Ashby is a Service Provider / Processor. We process that information only to provide the Services, on the Center’s documented instructions, and not for our own commercial purposes. Details are in the DPA.

COPPA (15 U.S.C. §§ 6501–6506; 16 C.F.R. Part 312). The Center operates the childcare program and is the primary operator vis-à-vis parents. Ashby provides software as a service provider to that Center. We still implement notice, verifiable parental consent in the product, a written retention policy, and security appropriate to children’s personal information. We do not claim that COPPA is inapplicable. We do not claim the school-authorization exception. We do not claim FERPA coverage. Typical licensed childcare is not a “school” for those purposes.

We never collect children’s data on our own initiative for advertising, sale, or training AI on children.

4. Information we collect

Information you or the Center provide

From website visitors who join the beta: the email address you type on ashbycare.com. We use it only to tell you when you can start. We do not sell it or use it for advertising.

From Center owners at school signup: if we ask them, answers to two optional questions: how you found Ashby, and whether your program is caring for children now, opening soon, or still planning. Each answer is chosen from a fixed list. We use the answers only in combined totals to understand which channels bring schools, and we never send them to Google, OpenAI, or any other advertising platform.

From guardians, because the Center invited them: name, email, phone, relationship to a child, consents, messages, and payment tokens if the Center uses in-product tuition payments (card numbers go to Stripe, not to us).

About children, because staff or guardians entered it: legal name, date of birth, room or group, attendance, authorized pickup, emergency contacts, allergies and care notes the Center needs, incident notes, immunization dates the Center stores, and photos or short videos if a guardian opted in.

From anyone who uses Hey Ashby: what they type in the chat and in its forms, and the reminders and preferences Ashby keeps for them. Section 9 explains what goes to Google, what is masked or held back, and how long Ashby keeps it.

Care notes and allergy information may be health-related. We process them only as the Center’s service provider so the Center can provide care. We do not operate a consumer health app for families.

Information we collect automatically

We may collect device and log information such as IP address, browser type, approximate general location derived from IP, pages viewed, and error events.

Google Analytics and Google Ads on ashbycare.com. On the public marketing site, Google Analytics and Google Ads measure page views and signup-button clicks so we can understand how our pages and ads perform. We use the advanced version of Google’s Consent Mode. Every consent type starts as denied, and ad personalization is always denied. Google Ads runs with Google’s restricted data processing turned on, which limits how Google may use this data.

• Before you choose, and after you choose Decline: Google receives limited signals without analytics or advertising cookies. They include the consent state, the event (a page view or a signup-button click), the public page address without its query string (pages outside a fixed list are reported as “/other”), and the network and browser information every web request carries, such as your IP address and user agent. We leave out ad-click identifiers, campaign labels, and the site you came from. We turn on Google’s ad-data redaction and turn off URL passthrough. Cookieless measurement still sends data to Google; it does not mean no data is collected.
• After you choose Accept: Google Analytics and Google Ads may also use first-party analytics and advertising cookies shared across ashbycare.com and its subdomains, including app.ashbycare.com. Events may also include Google ad-click identifiers (gclid, gbraid, wbraid), allowlisted campaign labels (utm_source, utm_medium, utm_campaign, utm_content, utm_id), and the domain of the site you came from, never its full address. When you accept, we resend the view of the page where you arrived, once, with those values, so the visit is credited to the right campaign.

We do not turn on enhanced conversions, Google signals, or ad personalization. We never send form contents. Other query parameters, URL fragments, and referrer paths are left out of our events.

Google Ads sign-up milestones from the Ashby app. When someone signs up to create a new school, Google Ads is told when each of four milestones happens: the sign-up form is shown, a new account is created, the email address is verified, and the school is created. The Ashby app (app.ashbycare.com) does not load the Google tag in its own pages. At a milestone, the app loads a separate page on ashbycare.com in an invisible frame and tells it only which milestone happened. That page, not the app, runs the Google tag and sends the milestone. It cannot read the app’s pages. Each milestone is sent at most once per page load of the app.

Google receives that page’s fixed ashbycare.com address and an empty referrer. Google may also learn that the page was opened inside app.ashbycare.com, but never the address of an app page, so it does not see which app screen or invitation link the sign-up came from. We do not send anything shown on screen, form values, names, email addresses, or account or school identifiers. Enhanced conversions, Google signals, and ad personalization stay off, and restricted data processing is on. Nothing is sent when the sign-up started from a family or staff invitation or a join link, and the account milestones are not sent when the new account already has a pending invitation, so parents and staff joining a school are not measured.

• Without consent: the cookie choice you made on ashbycare.com also applies in the app and on that page. If you declined, never chose, or your browser sends Global Privacy Control, Google receives the milestone without advertising cookies, together with the consent state and the network and browser information every web request carries, such as your IP address and user agent.
• With consent: Google Ads may also read and write its advertising cookies on ashbycare.com, so it can connect the milestone to an earlier ad click in the same browser. For a created school we also send a random one-time ID, so Google counts the school only once. That ID is not linked to the school or your account.

ChatGPT Ads (OpenAI). We measure ChatGPT ads only from our own server. Neither ashbycare.com nor the Ashby app loads an OpenAI script or pixel.

• When you click a ChatGPT ad, OpenAI adds an ad click reference (oppref) to the ashbycare.com link. Our site keeps it only in that browser tab and does not send it anywhere. If you choose Accept, or have already accepted, the site saves it in a first-party __oppref cookie on ashbycare.com for 30 days. If you choose Decline, the site deletes it.
• When a new school is created, and only if you accepted cookies, Ashby’s server sends OpenAI’s Conversions API one “registration completed” event. It contains a random event ID, the time, a fixed source address (https://app.ashbycare.com/measurement), and the __oppref click reference if one was saved. Because it is sent from our server, it does not carry your IP address or browser details. We send no name, email address (plain or hashed), phone number, school or account identifier, address, or child information, and we do not use OpenAI’s advanced matching. Every event is sent with OpenAI’s opt-out flag (opt_out) set, which marks it as not for ad personalization.
• Without consent, or when the sign-up started from an invitation or join link, no ChatGPT Ads event is sent.

Global Privacy Control. If your browser sends the Global Privacy Control (GPC) signal, ashbycare.com and the Ashby app on app.ashbycare.com treat it as Decline, even if you chose Accept before. Everything described above for Decline then applies: Google receives only limited signals without analytics or advertising cookies, the ChatGPT ad click reference is not saved, and no ChatGPT Ads event is sent.

Cookies and similar storage. These are the measurement cookies and browser storage we use:

Browsers can shorten these lifetimes. For example, Safari may limit cookies set by scripts, which includes every cookie above, to 7 days or less. Choosing Decline deletes the Google and ChatGPT Ads cookies above. Cookie settings at the bottom of marketing pages lets you change your choice at any time; the choice itself expires after six months. While your browser sends Global Privacy Control, your choice counts as Decline. Declining does not prevent sign-up or product use. The Ashby app also uses browser storage needed for sign-in, security, and preferences such as language; we do not use it for advertising.

Ashby’s own anonymous counts. Separately, Ashby counts page views and signup-button clicks for a fixed list of public pages, registration attempts and outcomes, and school-setup steps and errors. We may also count new visits, cookie-notice choices, and how many schools are created each week. These first-party counts work whatever your cookie choice, and they are not sent to Google or OpenAI.

• A count may include a traffic-source category and a device type. The traffic source is one of a fixed list, such as a Google ad, a ChatGPT ad, another paid ad, a search engine, an AI assistant, social media, email, a link on another website, direct, or unknown. The device type is phone, tablet, desktop, or unknown. A weekly count of created schools may also include the public ashbycare.com page where the visit started.
• If a count includes these categories, your browser works them out and passes on only the category names. A count carries only the event, a page name from our fixed list, and those category names. No identifiers, full page addresses, query strings, referrers, ad-click identifiers, or browser details such as the user agent are included in or stored with the counts.
• We store totals only: no individual browsing histories, unique visitors, per-person ad attribution, form contents, error messages, or account identifiers. The counts are never linked to a school or account, and they do not use cookies, fingerprinting, or tracking identifiers.
• We keep daily totals for up to 400 days and weekly totals indefinitely. Days and weeks follow Coordinated Universal Time (UTC). Older daily totals are removed when the next event is recorded.
• Our internal reports combine small breakdowns of sign-ups and schools (fewer than 3) by source or device, so a report does not point to one school or person.

Reloads and retries may count again. Ordinary infrastructure security logs are separate from these aggregate counts.

Ashby also counts, as one anonymous daily total, each time a newly created school opens the app for the first time, so we can check that sign-up measurement works. This count contains no school, account, cookie, browser identifier, URL, referrer, form value, or other personal data. It is not sent to Google or OpenAI, and it is collected whether or not you accept cookies because it is Ashby reliability telemetry, not advertising. Our server records in its logs only whether each ChatGPT Ads event was sent, skipped, or failed, with the response status, and may also keep these outcomes as an anonymous daily count, never the event’s contents. In the product, operational logs are used for security and reliability.

We do not put children’s names, photos, or other child-sensitive information into product analytics. Ashby’s own product analytics count when a Center reaches each setup step and when a person first opens an invitation, joins, visits, reads a message or pays. Each person appears only as a scrambled code that is different for every Center and cannot be turned back into a name or email. Screen recordings are described below. We do not send product analytics to any other company.

Screen recordings

To find the places where Ashby is hard to use, we record how people move through the Ashby app on the website. We record only:

• during a Center’s first 30 days, and
• on the sign-up pages.

What a recording contains. A recording shows where on the screen someone clicked, scrolled and typed, which Ashby screens they opened, and when something went wrong. Examples of something going wrong are an error, a click that did nothing, or a form that asked for a fix.

What we hide. Before anything leaves your browser, Ashby hides:

• every word on the screen, replaced with blank marks;
• everything you type;
• every photo, video and image.

The only words left readable are Ashby’s own fixed labels, such as menu names and button names. A recording never shows a child’s name, a family’s details, a message, a note, an amount, or any record. Ashby never records:

• sign-in and password screens;
• bank and payment screens;
• invitation links;
• the private forms inside Hey Ashby.

Who sees it. Only a small number of Ashby staff, to improve the product. Each time we watch a Center’s recording, it is written in that Center’s audit log. Recordings are kept in our own Google Cloud storage in the United States. They are never sent to an analytics or advertising company, never used for advertising, and never used to train AI.

How long we keep it. We delete recordings after 30 days.

How to turn it off.

• A Center’s owner can turn screen recordings off in School settings at any time.
• If your browser sends Global Privacy Control, Ashby does not record you.
• The iPhone and Android apps do not record screens.

Information from other sources

Authentication is provided by Firebase Authentication (Google). Payments may involve Stripe. Email delivery may involve Twilio SendGrid. Cloud hosting is Google Cloud. See subprocessors.

What we do not collect in the current product

We do not collect child biometrics for recognition (face templates, fingerprints, voiceprints), live camera streams of children, government-issued identification numbers or Social Security numbers, precise child geolocation, or children’s data for our own advertising or product analytics.

5. How we use information

We use information to:

• Operate the Center’s roster, attendance, ratios, licensing records, billing, and parent communication as the Center directs.
• Answer requests in Hey Ashby, as described in Section 9.
• Authenticate users and keep the Services secure.
• Provide customer support to the Center.
• Improve the product, using setup and activity counts and masked screen recordings that contain no child information, as described in Section 4.
• Measure how our website and ads lead to new schools, as described in Section 4.
• Comply with law, enforce our Terms, and protect the Services, our rights, and others.

We do not sell personal information. We do not “share” personal information for cross-context behavioral advertising as those terms are used in the CPRA. We do not use Customer Data to train AI models. We do not send children’s profiles, medical records, or photos to an AI provider.

6. Children’s privacy (COPPA)

The public marketing site is for adults shopping for software. The parent and staff apps are for adults. Children should not create accounts.

Almost every child record in the Services is a child under 13. Staff and guardians enter that information. Guardians see notice and give verifiable parental consent through signed electronic forms at invite, as described in Section 7.

We keep children’s personal information only as long as reasonably necessary for the purposes in this notice, and not indefinitely. See Section 11 (written retention policy, 16 C.F.R. § 312.10).

Parents may request access, correction, or deletion of their child’s personal information through the Center. We will assist the Center. Declining optional photo or extra-sharing consents still leaves a working parent account for required recordkeeping if enrollment consent is granted.

7. Consent

When a Center invites a guardian, the guardian sees three separate screens:

1. Enrollment / recordkeeping (required to use the child record in the app).
2. Photo and video (optional; off until the guardian says yes).
3. Sharing with non-integral third parties (optional).

Each grant is versioned. The Center is responsible for presenting notice and obtaining consent. We provide the screens and the audit trail. Revoking photos removes that child from photo features on the next request.

Hosting, authentication, Google’s AI for Hey Ashby, and (where used) payment processing are integral to providing the Services the Center asked us to run. They are named on the subprocessor list and are not a separate parent toggle.

8. Photos, video, and public pages

Photos of children are visible only to that child’s authorized guardians and relevant staff — not a public link. Public Center websites on Ashby Care must not include children’s personal information or images. Photo consent inside the logged-in parent experience is not consent to put a child on the public internet.

9. AI

Ashby has two AI features. Hey Ashby is part of Ashby for every Center. AI writing help is optional.

Hey Ashby

Hey Ashby is the chat in the Services (the “Chat”). A Center’s staff and the parents and guardians linked to its children can ask for things in their own words, such as “mark Mia absent today” or “who still owes for October?” It is part of the Services for every Center. No owner, staff member, or family needs to turn it on, and a Center does not choose it in a setting. Only Ashby can pause it. While it is paused, the apps say so and the regular screens keep working.

Ashby asks Google’s model to understand the request and to choose the next step among Ashby’s own tools. Ashby then shows an answer or a card. Each person sees only what their role in Ashby already lets them see. Ashby does not save or change a record, or send a message, until the person confirms a card. For a Center, Ashby processes Chat content as the Center’s service provider, under the DPA.

What we send Google. Each message, the earlier messages in the same conversation, and the facts from the Center’s records that a request needs are sent to Google in masked form. Ashby also sends its own instructions and descriptions of its tools. The facts are things such as dates, times, amounts, counts, statuses, the names of the Center, its locations, and its rooms, and titles staff wrote, such as event, announcement, closure, and rate names.

What we replace or hold back first. Before anything reaches Google, Ashby:

• replaces people’s names, phone numbers, email addresses, street addresses, dates of birth, and ID, case, card, and account numbers with placeholders, such as “[Child 1]” or “[phone 1]”;
• holds back the parts of a sentence about health, allergies, diet, medicine, injuries, custody, or incidents. When a child is staying home, Ashby sends that the child is absent and holds back why; and
• never sends photos, files, children’s profiles, or medical records. The Chat sends only the single masked facts a request needs, such as a room, an attendance status, or an amount owed.

Forms for private details. When Ashby needs a private detail, such as a phone number, an address, or an allergy, the Chat shows a form. What a person types in a form goes only to Ashby and is never sent to Google.

Limits. Masking is automatic. It can miss unusual wording, such as a name typed in lowercase, a name that is also an everyday word, or a health detail in words Ashby does not look for. So private details about children should go in the forms or the regular screens, not in the Chat. Centers should ask families to do the same. If Ashby cannot check a message safely, it stops and sends nothing. Names of public agencies and programs are not masked.

What Ashby keeps, and for how long. These stay inside Ashby, in Google Cloud in the United States:

• the masked conversation, until 24 hours after its last message;
• what a person typed that was held back, for 1 hour, so a form can be filled in for them;
• a card waiting to be confirmed, for 10 minutes;
• reminders and follow-ups a person asks Ashby to remember. Only that person sees them, and they may delete them at any time. Each one is deleted 90 days after the day it is for, or 90 days after it was saved or last changed if it has no day. A finished one is deleted 30 days after it is finished;
• notes a person asks Ashby to keep in mind, such as what they call a room. Only that person sees them, and they may delete them at any time. Each one is deleted one year after it was saved or last changed;
• which kinds of request a person confirms in the Chat, and at what time of day, such as checking children in each morning, so Ashby can suggest a likely next step. This is a kind of request and a count, never what was in it. Only that person sees it, they may delete it or turn it off at any time, and each kind is deleted 90 days after it was last used; and
• a person’s preferences, such as reply language, short replies, or the last child a parent looked at. They are kept until the person changes or deletes them.

All of them are deleted when the person leaves the Center.

Google’s processing and retention. Google LLC (Google Cloud) processes Chat requests on our behalf, as our processor and as a subprocessor for each Center. Ashby calls Google’s Gemini models through Vertex AI, in Ashby’s own Google Cloud project, at Google’s United States (us) location. Google does not use this content to train or fine-tune its models. Google may keep inputs and outputs in a short-term cache for up to 24 hours to answer faster, and may log prompts to detect abuse, as its Google Cloud terms allow. We do not turn on Google’s request logging, search grounding, or stored sessions. This is not Zero Data Retention. See Google’s Vertex AI data governance.

The Chat uses only Google’s Gemini models. Before the Chat uses another company’s model, such as Anthropic’s Claude, we will update this Policy and our subprocessor list and tell Centers first.

Setting up a new Center. A person creating a new Center can choose Set up with Ashby to do it in the Chat, or use the step-by-step forms, which use no AI. The same masking, forms, and limits apply. This Policy covers what they type in that chat.

AI writing help (optional)

AI writing help drafts text for staff, such as a daily note or an announcement. It is off unless the Center’s owner turns it on by separately accepting the Optional AI Terms and Privacy Notice. Those terms describe OpenAI’s processing and standard retention. Declining them, or turning AI writing help off later, does not block other Ashby features and does not affect the Chat.

If the Center uses AI writing help, we send OpenAI only the choices listed in the AI terms, such as activity types, a message purpose or announcement topic, and a tone. We never send a child’s name, profile, medical record, or photo. A person at the Center approves before a parent sees a draft.

Both features

Neither provider trains its models on this content. Optional extra sharing of child-linked content, if we ever offer it, is covered by the third-party consent screen.

10. Sharing and subprocessors

We disclose information to:

• Subprocessors that help us provide the Services (hosting, authentication, payments, email, Google’s AI for the Chat, and OpenAI for optional AI writing help), under contracts no less protective than the DPA for the data they receive. Current list: ashbycare.com/legal/subprocessors.
• Advertising measurement providers (Google and OpenAI), which receive only the limited website and sign-up measurement data described in Section 4. In that role, they receive no Customer Data.
• The Center and users the Center authorizes (staff with a role, guardians linked to a child).
• Professional advisors (legal, accounting, insurers) under confidentiality.
• A buyer or successor in a merger, acquisition, or asset sale, subject to this Policy and the DPA.
• Law enforcement or regulators when the law requires it, or to protect the Services, a child, or others from harm.

We do not sell children’s personal information.

11. Written retention policy

Children’s personal information is kept only as long as reasonably necessary for the purposes in this Policy, and not indefinitely.

Each record type has a clock. The clock is the longer of (a) what is reasonably necessary for that purpose under COPPA and (b) the Center’s state childcare licensing hold period for that record type. The product shows the Center its table. We do not apply one state’s licensing numbers to every Center. We do not delete a record before the applicable licensing floor. We do not keep child-sensitive data forever because a round number is convenient.

When a valid deletion request is made through the Center, or when the clock expires, we hard-delete from primary storage. Backups expire on a defined cycle. The Center can export a family’s data before deletion.

Consent records are kept long enough to prove what was agreed. Incident records may be kept longer where reasonably necessary to defend legal claims, but not shorter than the licensing floor.

Chat conversations, reminders, and preferences follow the shorter clocks in Section 9. A record a person confirms on a Chat card follows that record’s own clock.

Masked screen recordings (Section 4) are deleted 30 days after they are made.

12. Security

We use administrative, technical, and physical safeguards appropriate to the nature of the information, including encryption in transit and at rest for personal information, tenant isolation so one Center cannot query another Center’s records, role-based access, and audit of access to child-sensitive records. No method of transmission or storage is perfectly secure. We cannot guarantee absolute security.

We do not browse production child records as a casual practice. Access is limited to people who need it to operate or secure the Services.

13. Your choices and rights

Parents. Ask the Center to access, correct, or delete your family’s records, or to revoke a consent. We will assist the Center. We do not become another Center’s parent help desk for a different program’s records.

Center owners and staff. You may update account details in the product. An owner may export or delete the organization subject to the Terms and DPA. An owner can turn off screen recordings for the Center in School settings. Recordings already made are deleted after 30 days.

Website visitors. Use Cookie settings at the bottom of marketing pages to accept or decline measurement cookies at any time (see Section 4). You may also control cookies in your browser. Blocking cookies may affect site functions. We treat a Global Privacy Control signal from your browser as Decline on ashbycare.com and in the Ashby app (see Section 4). Like many sites, ashbycare.com is not designed to respond to browser “Do Not Track” signals. Learn more at allaboutdnt.com.

14. State privacy rights

If you are a consumer under a US state comprehensive privacy law (including California, Texas, Virginia, Colorado, Connecticut, and others that have similar statutes), you may have rights to know, access, correct, delete, or opt out of sale or sharing.

Customer Data (child, family, and staff records in a Center’s tenant): exercise those rights through the Center. The Center is the Business. We will not sell or share that information. Sensitive personal information (including children’s data and care notes) is used only to provide the Services.

Marketing-site visitors: we collect limited device and usage information as described above. If you join the beta, we also collect the email you submit. We do not sell either. We do not share them for cross-context behavioral advertising. These safeguards support that statement:

• We use Google’s and OpenAI’s advertising tools only to measure whether our own website and ads lead to new schools, not to target or personalize ads.
• Ad personalization is always off in the Google tag, and Google signals and enhanced conversions are off.
• Google Ads runs with Google’s restricted data processing turned on.
• ChatGPT Ads events are sent from our server with OpenAI’s opt-out flag, and only if you accepted cookies.
• You can choose Decline at any time, and we treat a Global Privacy Control signal as Decline on ashbycare.com and in the Ashby app.
• As advertising measurement providers, Google and OpenAI receive no Customer Data.

To request access or deletion of marketing-site information we hold as a business, email privacy@ashbycare.com. We will not discriminate against you for exercising a privacy right.

California notice at collection (site visitors). Categories: internet or other electronic network activity (pages viewed, signup-button clicks, sign-up milestones, IP address, device and browser type); identifiers (email, only if you join the beta; cookie identifiers and ad-click references, only if you choose Accept and your browser does not send Global Privacy Control). Purposes: operate and secure the site, understand aggregate use, measure our advertising, and email you when the beta opens. Retention: as reasonably necessary for those purposes, then deleted or de-identified. Sold or shared: no. Sensitive personal information collected on the marketing site: none intended.

Washington My Health My Data Act / similar health-privacy statutes. We do not offer a consumer health product. Allergies and care notes in a Center’s tenant are processed only as that Center’s service provider. Parents should send health-data requests to the Center.

15. Changes

If we make material changes to this Policy, we will publish a new version and update the effective date and version string at the top. We will tell Center owners about the change by email. Schools that sign up after we publish a new version accept it at signup. A change to the Center contract applies to an existing Center only as the Terms of Service allow. We will not treat continued browsing alone as acceptance of a material change to the Center contract.

16. Contact

Questions about this Policy: privacy@ashbycare.com

Viva Longer LLC, d/b/a Ashby Care 548 Market St PMB 649504 San Francisco, CA 94104-5401 United States

17. California consumer notice

If you are a California resident, in accordance with Cal. Civ. Code § 1789.3, you may report complaints to the Complaint Assistance Unit of the Division of Consumer Services of the California Department of Consumer Affairs, 1625 North Market Blvd., Suite N 112, Sacramento, CA 95834, or by telephone at (800) 952-5210.