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. 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', notes, symptoms) and their timestamps. 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; 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.

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 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.

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. 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. 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). 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).

The app schedules local care reminders on your device. You can disable these in the App under "Household" or in your OS settings at any time.

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 cascades you out of households (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.