Contact Dogday Lab & DogPath Support

Website feedback

Include “Dogday Lab” and the page address. Quote the short passage you are asking about, describe the problem and add a relevant source if you have one. For a broken tool, explain what you selected and what happened.

For an accessibility issue, describe the action you could not complete. Browser and device details can help, but share only information you are comfortable providing. You do not need to send personal training notes to report a website problem.

Open the publisher’s contact page

DogPath app support

Identify the app as DogPath and describe the feature involved. Device type, operating system version and the steps that led to the problem can help explain a technical issue. Never send a password, payment-card details or private access token.

Purchases and subscriptions are managed through the store and offer used for the purchase. Review the relevant Apple or Google account settings and the current app support information for the appropriate route. The training tools on this website do not have access to app accounts or purchase records.

About the DogPath app

Training and urgent concerns

This contact route is not an emergency veterinary service or a promise of an individual behavior consultation. For injury, pain, sudden changes or an urgent welfare concern, contact a veterinarian. For aggression, panic or bite risk, arrange qualified in-person or otherwise appropriate professional support.

The site can help you organize observations for that conversation. It cannot assess an emergency or replace a professional who can evaluate your dog and circumstances.

Give the next person a clear description to work with.

A useful support message explains one issue in a way that can be followed without access to your private household information. Begin with Dogday Lab or DogPath so the product is clear, then identify the page or feature involved. Keep the message focused on the action, the expected result and what actually happened.

For a website issue, describe a small repeatable sequence

If a tool result looks wrong, name the tool and the choices you entered using ordinary non-sensitive examples. Explain whether the output was missing, unclear or different from what the instructions described. If the problem involves a download, identify the file and the stage that failed: choosing it, saving it or opening the saved copy.

For an unclear guide, identify the heading or short passage and explain the decision you could not make from it. A source link or a concise description of the ambiguity can help. You do not need to provide a complete training log or an identifying photograph of your home to ask a question about the wording.

For app support, keep account secrets out of the explanation

Describe the DogPath feature and the actions leading to the issue. A general device description and software version can provide context when you choose to share them. A screenshot may help explain an interface problem, but review it first and remove unrelated private information. Never send a password, access token or payment-card number as a troubleshooting step.

The website tools cannot inspect an app account or retrieve information from a mobile device. For an app issue, describe the screen, the task and what happened using the current support route. Mentioning the product clearly helps distinguish a mobile app question from a browser note. Avoid sending private training records, passwords or device identifiers that are not needed to explain the issue.

Keep feedback and urgent care on the appropriate route

The publisher’s contact page can receive a website, accessibility or app-support question. Dogday Lab does not have a separate form on this page, and it does not offer an emergency response here. If the concern is urgent care or a safety issue involving a dog, seek appropriate professional help through the relevant direct route.

For ordinary feedback, a concise factual message is a useful starting point even when the cause is uncertain. State what you know and what remains unclear. There is no need to decide whether something is a software defect or an editorial mistake before reporting the observed problem, and this page does not promise a particular response time or resolution.