Privacy Policy
This Privacy Policy explains how Coffeebird Studio handles information when you use DailyDog, CycleBond, Push me!, or this website.
Last updated: September 9, 2026
Paul Rauch, operating as Coffeebird Studio in Austria, is responsible for the processing described here. This policy covers DailyDog, CycleBond, Push me!, and this website.
For questions or privacy requests, contact office@coffeebirdstudio.com.
You can use DailyDog without an account. Dog profiles and activities are saved on your iPhone. Creating an account or signing in enables cloud backup and synchronization. Joining a household makes shared records available to its members.
Location, Apple Health, camera, and notification permissions are controlled through iOS. You can change them in device settings; features that depend on a permission may then be unavailable.
DailyDog uses Google Firebase Authentication for email-and-password registration, sign-in, email verification, password resets, and account management. We process your email address, display name, account identifier, and household membership. Firebase processes authentication credentials and technical connection information, such as IP addresses and user-agent information, to operate and secure sign-in.
An account is optional for local use, but required for cloud synchronization, household sharing, and contributions to the community map. CycleBond and Push me! do not require a DailyDog account.
With location permission, DailyDog records precise coordinates and timestamps during a tracked walk, including in the background while tracking is active. Saved walks can include route geometry, duration, distance, step counts, the dogs involved, and the person who recorded the walk. These records can reveal places you visit and your routines.
Walks are stored locally and synchronized to your household when signed in. Household members can view shared routes. Stop a walk to end route recording; location may also be used when you request map or weather features. You can revoke location access in iOS settings.
DailyDog uses Cloud Firestore for account and household records, dog profiles, care entries, walks, places, person profiles, and dog health records. Cloud Storage for Firebase stores shared dog profile images and health attachments. Cloud Functions handle server-side operations such as sharing, community features, and deletion.
Optional records can include breed, birthday, weight, microchip details, vaccinations, medications, vet information, insurance details, notes, photos, and PDFs. Attachments may also contain personal information about you or others. Include only information you are entitled to share. Images are optimized before upload; PDFs are uploaded as selected.
DailyDog household sharing is an in-app feature. Household members can see and update shared dogs, photos, routes, care entries, and health records, including attachments. Member information includes display names, email addresses, roles, and identifiers; activities can show who recorded them. Joining or inviting someone therefore changes who can access household information.
Personal map favorites are separate: they synchronize across your own signed-in devices and are not shared with other household members. Signing out stops synchronization but keeps the current local data on that iPhone. Leaving a household does not recall copies already saved by others.
With your permission, DailyDog reads your daily step count and walking/running distance from Apple Health to display your activity on the iPhone. It does not write to Apple Health. These daily Health summaries are read locally; step counts recorded as part of an individual walk are included in the walk record and can synchronize with your household.
With motion permission, DailyDog also counts steps during recorded walks. Health access is optional and can be withdrawn in Apple Health or iOS settings. Health information is not used for advertising or marketing.
DailyDog uses Apple map and WeatherKit services to display maps and request weather for a location. Requests may transmit the requested location or map area and technical connection data to Apple.
Nearby public community places can be viewed without an account. Adding, confirming, or reporting a place requires sign-in. Place coordinates, categories, and submitted place details may be visible to other users. Public place documents exclude your account ID, email, and display name; a private contributor link and feedback records are kept for moderation and abuse prevention.
For nearby OpenStreetMap imports, DailyDog’s server sends Geoapify the center of an approximate map-area cell, rather than the device’s exact location. Community contributions are intended for public infrastructure, not private addresses or personal information.
Walk-goal, birthday, and health reminders are scheduled locally. Notification contents are not sent to Firebase, although health due dates are included in synchronized records. Widgets and Live Activities display app information on device surfaces that may be visible to someone using or viewing your device.
Photos selected for a walk-sharing image are processed locally and are not uploaded to DailyDog’s Firebase Storage for that export. The completed image goes to the sharing destination you choose. Original photo GPS metadata is not copied, but the image and route shape may still reveal a location. Copies shared outside DailyDog cannot be recalled through account deletion.
Apple processes App Store payments. DailyDog and Push me! use RevenueCat to manage purchases and subscription access. RevenueCat processes app-user identifiers, purchase and transaction information, and subscription status. DailyDog links its Firebase user identifier to RevenueCat when you sign in so access can be associated with your account; local users use a RevenueCat-generated identifier.
We do not receive full payment card details. Deleting an account does not cancel an Apple subscription. Manage subscriptions separately in your Apple account settings.
DailyDog uses Firebase App Check with Apple App Attest in production to help verify that requests come from the app. This involves app/device attestation information and security tokens. Cloud providers may process connection data and operational logs to deliver services, prevent abuse, and investigate failures.
Operational service logs and purchase records may be associated with account or technical identifiers; they should not be assumed to be anonymous. We do not sell or rent personal data or share it for advertising.
CycleBond stores cycle settings and app preferences such as cycle length, ranges, onboarding state, and display preferences on your device. Push me! stores workout plans, training progress, statistics, settings, and preferences locally. Device backups may include local app data if you enable them.
The DailyDog account, GPS, and household processing described above applies to DailyDog; it does not mean that these other apps upload their records to DailyDog’s cloud.
If you contact us, we process your email address, message, and any attachments to respond and resolve your request. Avoid sending passwords or unnecessary sensitive information.
Our website host may process IP addresses, browser information, access times, and requested pages to deliver and secure the website. The website loads fonts from Google Fonts, which means your browser contacts Google and sends connection information, including your IP address. The current website does not include an analytics or advertising script and does not itself set cookies through its page scripts.
Where the GDPR applies, we process information necessary to deliver requested account, backup, sharing, and subscription services on the basis of performing our contract with you (Article 6(1)(b)). Optional location and Health access rely on your permission and, where applicable, consent (Article 6(1)(a)); to the extent Health data is special-category personal data, explicit consent applies (Article 9(2)(a)). You can withdraw consent without affecting earlier lawful processing.
Security, abuse prevention, reliable service operation, and handling general inquiries serve our legitimate interests (Article 6(1)(f)). Processing required to comply with law or handle statutory rights requests is based on legal obligations (Article 6(1)(c)). We do not make decisions with legal or similarly significant effects solely through automated processing.
Recipients include authorized household members, destinations you choose when sharing, and providers needed to operate the services: Google/Firebase for authentication, cloud storage and processing, Apple for platform features and payments, RevenueCat for subscriptions, Geoapify for map-area place data, and our website and email providers.
Processing can occur outside Austria and the EEA. Firebase Authentication processes data in the United States; choosing a European database region does not make every Firebase service EU-only. Google describes its international-transfer arrangements, including the EU–US Data Privacy Framework and applicable processing terms, in its Firebase privacy documentation. Contact us for information about applicable safeguards.
Local records remain until removed or the app’s local storage is cleared. Removing the app or signing out does not delete your cloud account. Cloud records are retained to provide your account and household service until deleted, subject to shared-household handling below. Support information is retained while needed to resolve and follow up on a request or meet legal obligations; operational records are retained for security, troubleshooting, and provider recovery requirements.
In DailyDog, use More → Account & Backup → Delete Account, confirm your password, and review each household. Sole-member households are deleted with their records and photos. Shared households require a successor owner; other members keep shared dogs, photos, and places, while your linked person profiles and activities assigned to them are removed.
Once accepted, deletion continues on the server. The requesting iPhone’s local data and cache are cleared; other connected devices clear their copies when notified. Offline devices and exported copies cannot be erased immediately. Community contributor links, confirmations, and reports are removed; anonymized public infrastructure places may remain.
Completed deletion receipts expire after seven days for status checks and retries; Firestore removes expired records asynchronously. Minimal retired-profile markers prevent old devices from restoring removed activities. Provider backups and recovery copies may persist after active records are deleted. Firebase states that authentication information is removed from its live and backup systems within 180 days after user deletion is initiated.
Where applicable, you can request access, correction, erasure, restriction, or portability of your personal data, object to processing based on legitimate interests, and withdraw consent. Contact us at the email above; we may need to verify your identity. Some rights have exceptions, including where another person’s rights or legal retention duties are involved.
You can lodge a complaint with your local supervisory authority. In Austria, this is the Austrian Data Protection Authority (Datenschutzbehörde).
These apps are not directed at children under 13. If you believe a child has supplied personal information without appropriate authorization, please contact us.
We update this policy when our processing changes and show the revision date above. Where required, we will provide additional notice or request consent before new processing begins.