The user cares about pet records but also wants privacy clarity.
Private journal
A private pet journal with clear data boundaries.
Keep a local-first pet journal for dog and cat behavior cues, saved check-ins, feedback, and privacy-aware exports.
Privacy-conscious pet owners who want behavior history without vague data claims.
Save local pet history while understanding when backend services are used.
Why this page exists
PawSignal stores journal data locally and uses backend services for selected analysis, purchase verification, credit protection, and coarse analytics.
01
Keep pet profiles and saved check-ins on device.
02
Send selected photo data only when requesting AI analysis.
03
Use privacy-aware export when reviewing data.
04
Contact support for backend deletion requests tied to anonymous app identity.
Code-backed proof
This page is backed by app and database behavior.
- Raw export strips local media paths.
- Analytics sanitizer blocks raw photos, prompts, questions, answers, transcripts, tokens, and diagnosis text.
- Legal pages describe local-first history and request-time backend use.
Decision logic
Privacy copy must be exact
The product can say local-first journal. It cannot say nothing ever uploads, because selected photo data uploads for AI analysis.
- Local profile and journal history.
- Request-time AI upload.
- Backend commerce and event protection.
Decision logic
Trust is the growth mechanism
Privacy-sensitive users convert only if the product explains the real path simply.
- What stays local.
- What is sent on request.
- What is excluded from analytics.
FAQ
Boundaries stay visible.
Is PawSignal cloud-only?
No. The journal is local-first, while selected analysis and backend commercial flows use backend services when needed.
Does analytics include raw pet photos?
The analytics sanitizer blocks image, photo, prompt, answer, transcript, token, and similar sensitive metadata keys.
Read the privacy-aware flow
Start with visible evidence, save the check-in, and keep the veterinary boundary clear.