This page clarifies the privacy and data-handling boundaries of Pet Health Journal. Our primary goal is long-term accumulation of pet-care records: helping you continuously organize body weight, vaccination, deworming, clinic visits, symptoms, medication, and lab information for family collaboration and review. Content here is general guidance; it is not medical advice and does not replace professional diagnosis or treatment.
1. Data scope: centered on pet-care records, not excessive collection
Core data is centered on pet profiles and health events, with emphasis on records that are reviewable, searchable, and comparable. In practical logging, prioritize pet status, timeline, and handling steps, and avoid personal-sensitive information unrelated to health management (for example full home address, national ID numbers, bank-card information). This lowers privacy risk while keeping records focused and useful.
For clinic-related records, preserving hospital name, diagnostic conclusion, treatment plan, and follow-up advice is usually sufficient. If contact references are needed, role labels (for example “Family member A” or “Primary clinician”) are generally enough for review.
2. Account and data isolation: one person, one account, lower mixed-entry risk
After login, records are bound to and displayed within the account. To avoid confusion in multi-pet households about who wrote what and for which pet, we recommend not sharing one account among multiple people. A better pattern is one primary account maintaining standard templates, with family members logging under unified conventions, and consistency achieved through summaries or fixed fields.
If multi-person collaboration is unavoidable, align units and keywords first: weight in kg, dosing in mg/tablet, and titles in the “event + outcome” format. Unified wording is itself part of privacy protection because it reduces the need to add excessive explanatory personal details in free text.
3. Public pages vs private records: presentation layer and record layer are separated
Official pages (`/official/*`) and public brief pages (`/seo/*`) host publicly searchable explanatory content such as announcements, FAQs, guides, and topics. This layer is for information discovery and reading, not for your private health records. Day-to-day pet records are maintained mainly in the post-login business-data layer for long-term tracking and review, not for public display.
You can think of this as a two-layer model: public pages explain what to do, while the record layer captures what you actually did. This separation preserves searchability while reducing exposure of personalized data in public contexts.
4. Logs and operations: for stability and troubleshooting, not individual profiling
Necessary technical logs may be generated during operation for fault diagnosis, interface stability analysis, and security auditing. Log governance follows the minimum-usable principle: retain only information required to locate and resolve issues, not to build individual user profiles. You can further reduce potential exposure on the logging side by avoiding sensitive fields in business-text entries.
5. Practical usage recommendations: low-risk, review-friendly recording style
- Record only facts and conclusions related to pet health; avoid unrelated sensitive information.
- Use unified fields and units to reduce leakage and misreading caused by free-form variation.
- For clinic notes, prioritize timestamp, chief concern, handling, and follow-up; skip private details.
- Run periodic weekly/monthly reviews to retain executable actions instead of accumulating redundant prose.
6. Additional note on data management
If record content needs adjustment (for example correction, de-identification, or clarification), revise the source entry as early as possible to avoid misunderstandings from multiple inconsistent versions. For content no longer needed over the long term, periodic cleanup is recommended so only data that is truly valuable for review remains. In practice, a minimization-plus-structure habit is usually more effective than late-stage remediation.