Privacy Policy

DidWeFeed is operated by Andreas Armanious, contactable at privacy@didwefeed.app.

Account data: Email address (for sign-in via email one-time code, Apple, or Google), display name and profile color you choose, and an optional profile photo. For Apple/Google sign-in, we collect the name and email address those providers return.

Beta signup data: When you join the founding beta on this website, we collect your email address, selected platform, language, landing page, broad device class, referrer category and campaign attribution parameters, plus any optional answer about who shares pet care with you. We use this information to send and operate the beta invitation, understand which signup sources work, and improve onboarding. We do not store the full referring URL in the signup funnel. Beta access does not automatically subscribe you to unrelated marketing.

Your content: Households you create or join (name, time zone) and household membership. Pets (name, details) and care tasks/reminders. Care log entries you record (e.g., 'fed', amounts, notes, symptoms) and their timestamps. Photos you choose to add: pet photos, photos on care entries, vet-visit attachments, and your optional profile photo.

Technical / diagnostic data: Crash reports and performance traces via Sentry. We set sendDefaultPii: false, so we do not attach your IP address or account identifiers to these reports, and we do not record session replays. We also collect standard server logs from our backend provider (Supabase) for security and reliability. The website uses Vercel Web Analytics and Speed Insights for aggregate page and performance measurement, and PostHog (EU cloud) to measure page views and the beta signup funnel. Unless you agree to more in the cookie banner, PostHog runs in cookieless mode: it sets no cookies and stores nothing on your device, creates no user profile, and counts visitors with a hash that changes daily and cannot be traced back to you. What changes if you agree is described under “Website analytics and cookies” below. If the page hits a technical error in your browser, an error report (error message, code location, page address, browser type) is sent as well so we can fix it. Form contents and email addresses are not sent to these analytics tools.

We do not collect advertising identifiers, run third-party ad tracking, sell your data, or use it for cross-app tracking. There is no in-app advertising.

The mobile app also uses Expo Observe (Expo / 650 Industries) to measure app launches, navigation and performance and diagnose errors. This includes app and operating-system versions, device model, language, performance measurements, and pseudonymous installation and session identifiers. These technical records help us find slow or failing app behavior. They are separate from the website analytics below and are not screen recordings. Providers also receive connection metadata, such as an IP address, when your device contacts their services.

Without your consent: The website sets no cookies. Two entries are kept in your browser’s local storage because the site needs them to behave the way you set it: the colour theme you picked (“theme”) and your answer to the cookie banner (“dwf-consent”), so we do not ask again on every page. Neither is used for analysis.

If you answer “Yes, that’s fine” in the cookie banner, PostHog additionally does the following:

• It sets a first-party cookie and local-storage entries (names starting with “ph_”) that hold a random visitor ID and are kept for up to one year. This lets us recognise a returning browser, for example to see whether a visit led to a beta signup on a later day.
• It records which elements you click, where the pointer moves and how far you scroll (click tracking and heatmaps).
• It records a replay of your visit to this website: the pages as they were shown and your movements on them. Everything typed into form fields is masked in your browser before anything is sent, so the email address you enter never reaches the recording.

We still create no user profile and do not link this data to your email address or your app account. It is processed by PostHog on servers in the EU. The legal basis is your consent (Art. 6(1)(a) GDPR, § 165(3) of the Austrian Telecommunications Act 2021).

Changing your mind: “Cookie settings” at the bottom of every page opens the banner again. If you answer “No, thanks” there, the cookie and the stored visitor ID are deleted right away and the website goes back to cookieless mode. PostHog keeps a single local-storage entry (“__ph_opt_in_out_…”) that notes nothing but your answer. Withdrawing consent does not affect the lawfulness of processing before the withdrawal. This section applies to the website only; the app uses none of it.

When you start a walk in the app, we access your device's precise location to draw the route on a map and measure distance, duration, and pace. This can continue while your screen is off or the app is backgrounded during an active walk, and stops when you finish it. The completed route and statistics are stored in our database solely to show that shared walk history to you and members of your household. You can delete a recorded walk at any time.

If you turn on Share live position for a walk, members of your household can see your current position, distance, duration, and pause status until you stop sharing or finish. This is off by default for every walk. The live feed does not include a route. Position messages pass through our backend and are retained temporarily by its realtime service.

If you explicitly enable the optional home-radius feature, the app requests background-location permission so it can offer a departure prompt and recognize your return. The home-radius coordinates are kept on your device and are not stored in our database. You can disable the feature or revoke location permission in your device settings at any time. We never use location for advertising or cross-app tracking.

Maps and address search: Android maps use Google Maps and iOS maps use Apple Maps. Displaying a map sends requests for the area being viewed to the map provider. Google's Maps SDK also collects device and SDK metadata, IP addresses, SDK-specific identifiers, crash and diagnostic data, and map interactions such as panning or zooming to maintain and improve Google services. Address search and reverse geocoding use your operating system's geocoding service; the entered address or selected coordinates may be processed by its provider to return a result. Keeping the home radius out of our database does not mean map and address lookups stay entirely on your device. See Google's Maps SDK data disclosure and Apple's Maps privacy information.

To provide the service: authenticate you, operate the founding beta, send beta invitations, sync pet-care data across the members of your household in real time, and send care reminders.

To keep the app and website reliable and secure, prevent abuse, understand aggregate acquisition performance, and improve onboarding.

We do not use your pet-care content to train models or for marketing.

Data is stored with Supabase (hosted Postgres). Row-level security ensures only members of a household can read or write that household's pets, tasks, and care log.

Photos are kept in private Supabase Storage buckets. They are never publicly reachable; the app shows them to household members only through short-lived signed links. Your profile photo is visible to the members of the households you belong to.

Brevo stores beta contacts and processes beta invitations and transactional auth emails. A new-signup notification containing an obfuscated email address and platform may be sent to our private Discord workspace so the founder can monitor beta operations. The optional post-signup household answer is recorded only as an aggregate funnel event and is not linked to the submitted email.

Vercel hosts the website and processes aggregate web analytics, performance measurements, and standard security logs. PostHog processes website usage events, with your consent also click data and session recordings of the website, and technical server logs of the beta signup (status and error codes, never email addresses) on servers in the EU. When the shared signup rate limit is configured, Upstash stores a salted one-way hash of the client address in a short-lived counter for abuse prevention. Sentry processes app crash/performance diagnostics (no personally identifiable information attached).

Expo (650 Industries, USA) processes the mobile performance telemetry described above and relays push notifications to Apple and Google for delivery; see Notifications. Apple and Google process sign-in when you choose those methods. RevenueCat processes subscription/entitlement state (a pseudonymous user ID and purchase status; no payment details — payments are handled by Apple/Google).

Push notifications are sent by our server. Care reminders go out only while a task is still open, with a follow-up for medication; you also get a note when someone thanks you for an entry, and on your pet's birthday or gotcha day. A notification contains your pet's name, the task, and where relevant the name of the household member involved.

To deliver them we store your device's push token, its platform (iOS or Android) and your app language, linked to your account. Notifications are sent through Expo's push service (Expo / 650 Industries, USA) to Apple Push Notification service or Firebase Cloud Messaging (Google), which deliver them to your device. We keep a short log of which reminders were sent so none goes out twice; it is deleted after 14 days.

While you record a walk or another activity, we store that a session is in progress for that pet (no location) so the reminder for it stays quiet. It is removed when the session ends, and after one day at the latest.

Prompts from the optional home radius are created on your device. You can turn reminders off in the app under Settings → Notifications, mute a single task when you edit it, or block notifications in your device settings. Your push tokens are deleted with your account.

Export your data: Settings → Data & privacy → export a JSON copy of your account and household data.

Delete your account: Settings → Data & privacy → delete. This removes your account and profile photo and takes you out of your households; a household you were the last member of is deleted with its pets, care history, and photos (Apple requires in-app deletion). Alternatively, you can submit a deletion request via our Web Deletion Page.

You may request access, correction, or deletion by emailing privacy@didwefeed.app.

Depending on your region (e.g., EU/EEA, UK, California) you may have additional rights under GDPR/CCPA; we honour verified requests.

DidWeFeed is not directed to children under 13 and we do not knowingly collect their data.

We'll update this page and the 'last updated' date when this policy changes.

privacy@didwefeed.app