This Privacy Policy explains how BeFam ("we", "our", "us") collects, uses, shares, protects and deletes information when you use the BeFam mobile app (iOS, Android), the web app at app.befam.app and the website befam.app (together, the "Service").
1. Who we are
The Service is operated by Dark Moto s. r. o., Tatranská 385/1, 059 21 Svit, Slovakia. Company ID (IČO): 50 750 496 · VAT ID: SK2120463092. Contact: info@befam.app. We are the controller of your personal data under the EU General Data Protection Regulation (GDPR) and the Slovak Act No. 18/2018 on Personal Data Protection.
2. What information we collect
- Account: email address, display name and nickname, role in the family (for example parent, child, grandparent), avatar or profile photo, app language, time zone. Passwords are stored only as salted hashes by our authentication provider; we never see them. With Sign in with Apple or Google we receive an account ID, your email and name, never your password.
- Family and household content: family name and members, tasks (title, notes, dates, times, place typed as text, category, who it is for), shopping lists, recipes and meal plans, notes (family or private), family chat and direct messages with photos, voice messages and videos, comments, praise, stars and rewards, birthdays and other important dates (with interests and gift notes you type), and members without an account (such as a baby or a pet).
- Children: a parent can add a child's name, year of birth, school or nursery, when they leave in the morning and how long the trip takes. This is visible to the family and used for reminders and the daily overview.
- Food diary: meals you log, calories and nutrients, and an optional daily calorie goal. A photo of a plate is sent for analysis and is not stored.
- Places you type: a task's place and the start and end of a commute, as text. BeFam does not use your device's location (GPS).
- Email addresses of people you invite, and emails you forward to your family's BeFam inbox address (if you use it).
- Technical data: push notification token (only if you allow notifications) and backend request logs (time, IP address, request) for security. We do not collect advertising identifiers and we do not read your contacts.
- Product analytics (mobile app only): see section 5.
- Website (befam.app): when you join the waitlist or newsletter, fill in the quiz or the contact form, we store your first name, email, optionally your country, your quiz answers or your message, to send the invitation and the newsletter and to reply. You can unsubscribe in every email. The website loads its fonts from Google Fonts, which receives your IP address; it sets no tracking or advertising cookies and keeps only your language choice in your browser.
3. Why we use it (legal basis)
- To provide the Service you signed up for: your account, family, tasks, lists, chat, reminders and the features you choose to use (Art. 6(1)(b) GDPR).
- Security, abuse prevention, fixing crashes and improving the app through product analytics, which you can switch off (legitimate interest, Art. 6(1)(f)).
- Push notifications, Google Calendar sync and the phone calendar, only when you turn them on (consent, Art. 6(1)(a); you can withdraw it at any time in the app or in your phone's settings).
- Billing and tax records when you buy BeFam Plus, and lawful requests (legal obligation, Art. 6(1)(c)).
We do not sell your data, we do not show ads, and we do not share data with advertising networks or data brokers.
4. AI features (Fam, dictation, photos)
- BeFam's AI features run on the Google Gemini API (Google LLC). What is sent to Google for one request: your messages, voice messages and photos to Fam; voice dictation of tasks and shopping items; photos of meals; recipe links, recipe photos and recipe ingredients; and the family context Fam needs to answer, such as first names and roles of members, tasks, events, shopping items, meal plans, important dates and children's details. The daily overview, weekly summary, birthday reminders and suggestions are written the same way from your family's data.
- We use the paid Gemini API. Under its terms Google does not use this content to train its models; it may keep it for a limited time to detect abuse.
- If Gemini cannot read a recipe link, the page text is sent to the Anthropic Claude API (Anthropic, PBC, USA) as a fallback, under terms that also exclude training.
- Voice messages in the family chat are not sent to any AI. Audio and photos sent to Fam are not stored by BeFam; we keep only the conversation text.
5. Product analytics (PostHog)
- The mobile app sends usage data to PostHog (PostHog Inc., EU servers): screens opened, a few actions (for example "task created", "family created", "paywall shown"), device model, operating system, app version, language, plan (Free or Plus), crash reports and a recording of how the app is used.
- In the recording all text, text fields and images are hidden, and the chat with Fam is hidden entirely.
- Events are linked to your BeFam account ID and family ID, never to your email or name, and never include your messages, tasks, photos or voice. PostHog receives your device's IP address with each request.
- We use it only to find where people get stuck and to fix crashes. You can switch it off any time: Settings → General → "Usage analytics". It is on by default; once it is off, nothing more is sent from that device and the recording stops. The web app and the website do not use PostHog.
6. Google user data (Google Sign-In and Google Calendar)
This section describes how BeFam accesses, uses, stores, shares and deletes data received from Google APIs.
6.1 What Google data we access
- Google Sign-In (scopes
openid,userinfo.email,userinfo.profile): your Google account ID, email address, name and profile picture, to create and sign in to your BeFam account. - Google Calendar (scope
https://www.googleapis.com/auth/calendar.events), only if you connect it in Settings → Calendar Sync: we create, update and delete calendar events that represent your BeFam tasks. Every event BeFam writes carries a private propertybefam_task_id. When we check for changes, Google returns the changed events to our server; we act only on events with that property and discard every other event at once. From BeFam's own events we use the date, start and end time, title and whether the event was deleted. - We receive an OAuth refresh token so that the sync keeps working when the app is closed, and the email of the connected Google account.
6.2 How we use Google data
- Your email and name identify your account and the family member the calendar belongs to.
- Calendar access is used only for the two-way sync you turned on: a BeFam task with a due date appears as an event in your Google Calendar, and when you move, rename or delete that event in Google Calendar, the matching task in BeFam is updated or removed.
- Events BeFam did not create are never stored, never shown in the app and never sent anywhere.
- We do not use Google user data for advertising, profiling, credit or lending decisions, and we do not use it to develop, improve or train AI or machine-learning models.
6.3 How we share Google data
- We do not sell, rent or transfer Google user data to anyone, including advertisers, data brokers or information resellers.
- Google user data is processed only by our infrastructure provider Supabase, Inc. (database and server functions in the EU, Ireland), on our instructions, to run the sync.
- Task titles synced with Google Calendar are visible to members of your own BeFam family, like any other task.
- The calendar sync never sends Google data to AI services. If you use Fam, it can read your BeFam tasks (which may include a title you edited in Google Calendar) to answer your request, as described in section 4.
- We may disclose data only if required by law.
6.4 How we protect Google data
- All traffic between the app, our servers and Google is encrypted in transit (TLS).
- OAuth tokens are stored in our EU database (Supabase, Ireland) on encrypted storage and are used only by our server-side sync functions. Row-Level Security restricts each token to the account that connected it; it is never visible to other users or family members.
- OAuth client secrets and API keys are kept as server secrets, never in the app. Access to production systems is limited to the people who operate the Service.
6.5 Retention and deletion of Google data
- The refresh token and the link between tasks and calendar events are kept only while Google Calendar is connected.
- When you disconnect in Settings → Calendar Sync, we revoke our access at Google and delete the token and the sync state from our database. Events already in your Google Calendar stay there as your own events.
- When you delete your BeFam account, we revoke the Google grant and delete the token immediately.
- You can also remove BeFam's access at any time at myaccount.google.com/permissions.
6.6 Limited Use
BeFam's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. The use of raw or derived user data received from Google Workspace APIs (including Google Calendar) will adhere to the Google User Data Policy, including the Limited Use requirements.
7. Calendar on your phone
If you turned on the phone calendar (offered in earlier versions under Settings → Calendar Sync) and allowed access, BeFam writes your tasks as events into the one calendar you picked. It is one-way: BeFam does not read your other events. Which calendar you chose and which task belongs to which event are stored only on your device.
8. Who processes data for us
We share data only with providers needed to run the Service, under data processing terms:
- Supabase, Inc.: sign-in, database, file storage and server functions (EU, Ireland).
- Google LLC: Gemini API for AI features (section 4), Google Sign-In and Google Calendar (section 6), Firebase Cloud Messaging for Android notifications.
- Anthropic, PBC: fallback for reading recipe links (USA).
- PostHog Inc.: product analytics and crash reports for the mobile app (EU servers).
- Expo (650 Industries, Inc.): delivers push notifications to Apple Push Notification service and Firebase (USA). A notification carries its text, for example a task title or the beginning of a chat message.
- Resend, Inc.: sends invitation and account emails (sign-up code, password reset) and receives emails forwarded to your family's BeFam inbox (USA).
- Cloudflare, Inc.: stores videos sent in the family chat.
- Vercel Inc.: hosts the web app and the website.
- Loops (Loops.so, Inc.): website waitlist and newsletter emails (USA). The website's form data is stored with Supabase in the EU (Frankfurt).
- Payments for BeFam Plus: Apple (App Store) and Google (Google Play) process in-app purchases, and RevenueCat, Inc. tells us whether a family has Plus (it receives your BeFam account ID and family ID, not your card). On the web, Stripe Payments Europe processes the payment and receives your email, the family name and IDs. We never see your card number.
Some of these providers are in the USA. Transfers outside the EU/EEA rely on the EU-US Data Privacy Framework where the provider is certified under it, otherwise on the European Commission's Standard Contractual Clauses.
9. Who in your family sees what
- Family content is visible to the members of that family; private notes only to their author and the people they are addressed to; direct messages only to the two people in them. This is enforced in the database (Row-Level Security).
- Photos, voice messages and profile pictures are stored at long, random web addresses that are not listed anywhere. Anyone who has such an address can open the file, so do not share it outside the family. Chat videos are stored privately and open only through short-lived links.
- Links you share outside the family (a note, "Family today") show only what you chose, can be switched off and can expire.
10. How long we keep data
- Your account and content: while your account exists.
- When you delete your account (Settings → Account → Delete account, or app.befam.app/delete-account), it is deleted immediately: your profile, messages, comments, praise, private notes, profile photo, push tokens, Google connection and your files in the chat. Tasks, lists, recipes and rewards you created in a family that still has other members are handed over to another member and stay with that family. If you were the last member, the whole family and its files are deleted, and a web subscription is cancelled. A subscription bought through Apple or Google must be cancelled in your App Store or Google Play account.
- Backend request logs are kept for a short time (days). Analytics data is kept by PostHog under our plan's retention period. Records kept by payment providers follow their legal obligations.
11. Your rights
Under the GDPR you have the right to access, rectification, erasure, restriction, objection, data portability and to withdraw consent at any time. Write to info@befam.app from the email of your account; we respond within 30 days. You can also lodge a complaint with the Office for Personal Data Protection of the Slovak Republic (dataprotection.gov.sk).
12. Children
BeFam is a family app and children may use it under parental supervision. A parent who adds a child profile or a child's details is responsible for managing that child's data within the family. The Service is not directed at children acting on their own. If a child has created an account without a parent, write to us and we will delete it.
13. Security
Traffic is encrypted in transit (TLS). The database limits every row to the family or person it belongs to. Server keys are never in the app. If a breach affects your personal data, we will notify you and the supervisory authority as the GDPR requires (Art. 33 and 34).
14. Changes
We will announce material changes in the app and by email at least 14 days before they take effect. The current version is always at befam.app/privacy.