Your privacy, thoughtfully handled.
This policy describes the application’s data flows. The business operator must supply its contact details and approve this policy before a public commercial launch.
Optional readership measurement, sharing and notifications
Audience measurement is off until you opt in using the control above the footer. With consent, browser-generated identifiers are transformed into server-side hashes to deduplicate session visits and measure returning readership, sharing interactions and referral visits. We do not record full referrer URLs, account pages or article query strings. Events are retained for 90 days. You can opt out at any time. Referral counts are observed consenting browser visitors, not verified people or sales. Web Push is separately opt-in and stores an endpoint, encryption keys, chosen topics, time zone and quiet hours; stop it on the Follow page or in browser settings. External share links open the selected service; clicking one does not prove a post was published.
Account and reading data
Netlify Identity manages production account credentials, signup, login and recovery. We store linked profile information, membership references, bookmarks and reading progress in PostgreSQL. Payment card details stay with Stripe; we do not store them.
Location and rescue research
City, town or ZIP search criteria and optional questions are sent to xAI for web-assisted research. Exact browser coordinates are requested only after you choose Find near me and approve browser permission. When configured, coordinates are sent to Geoapify solely to resolve a city; they are not sent to xAI or intentionally persisted in our search records. Search results are cached for one day, with expired cache records removed by background maintenance.
Providers and cookies
Authentication uses essential session cookies. Production deployments use Netlify Identity for accounts and may use Stripe, xAI, Resend, an object storage provider and the selected hosting and database operators. We do not add advertising trackers. Outbound websites apply their own policies. Embedded maps contact OpenStreetMap after loading.
Email preferences and retention
The Daily Bark requires explicit consent and email confirmation. Every newsletter must include an unsubscribe link. Security and billing records may need to be retained for operational or legal reasons; the business operator must adopt a jurisdiction-appropriate retention schedule. Do not send sensitive personal information in rescue questions.
Your requests
Use the contact page to request access, correction or account deletion. An operator contact address and applicable jurisdiction must be configured before launch. Service providers may process data internationally; the operator must confirm its applicable privacy obligations.