Your information in HomeFeud.

Who is responsible

Wecode AB is responsible for HomeFeud’s processing of personal information. Our organisation number is 556748-3861 and our address is Åsögatan 164, 116 32 Stockholm, Sweden. Contact support@homefeud.com about privacy, your account, or this policy.

Information we collect

• Account information. Apple or Google supplies an account identifier and available name and email address when you sign in. Google may also supply a profile-picture URL, which is stored with your authentication profile. We do not receive your Apple or Google password or access your photo library.
• Your household. We store your display name, optional partner label, household membership, language, timezone, week-start setting, custom activities, activity entries and notes, scores, results, and invitations. Shared information can come from you or your household partner.
• Notifications and app activity. We store notification preferences, device push tokens, delivery/read status, and timestamps for account and household actions. Update requests include the app version, operating system, and an installation identifier.
• Support and technical information. We process correspondence you send to support, records of administrative actions, and technical error information such as stack traces, release versions, and device/runtime details. Service providers also process connection information, including IP addresses, to receive requests.

Account information is needed to sign in; shared activity information is needed to provide household features. Partner labels, notes, and support messages are optional. Avoid putting sensitive information about yourself or others in notes or activity names.

Why we use it

We use account and household information to provide the service you request: sign-in, partner connections, invitations, shared activities, scores, history, and account support. The legal basis is performance of our contract with you.

Security records, error reporting, recovery, and basic counts of users, households, activities, and failed deliveries help us operate and protect HomeFeud. The basis is our legitimate interest in a secure, reliable service and understanding its use. This processing must be necessary and proportionate, taking your privacy rights into account. You can object as explained below. We also process information when necessary to meet a legal obligation, such as responding to a valid privacy request.

Optional push alerts are sent according to your choices and device permissions. You can turn them off. HomeFeud does not sell personal information, show advertisements, or use cross-app tracking for advertising. We do not make automated decisions that have legal or similarly significant effects on you; household scores are calculated from recorded activities.

Sharing with your partner

Your household partner can see shared activities, notes, and scores. An invitation link or code lets its holder view invitation information and request to join while the invitation remains valid. Share invitations only with the intended person. HomeFeud 3.0 uses link/code invitations and does not send invitation emails.

Disconnecting archives the shared household; it does not erase its history. Deleting your account has the separate effects described below. We cannot remove copies that another person has independently saved, such as screenshots.

Storage on your device

The website uses authentication cookies and browser storage for sign-in and temporary invitation state. The mobile apps use secure storage for authentication and cache household data for offline reading. Signing out clears HomeFeud’s private session and household cache. Uninstalling the app does not delete your server account.

Notifications and updates

Expo and Apple or Google deliver mobile notifications. A device push token lets us address notifications to your installation. Notification content may appear on your lock screen, depending on your device settings. Change preferences in HomeFeud or permissions in your operating system. Expo also provides app updates using technical information needed to deliver a compatible version.

Error reporting

When enabled, Sentry receives error and crash reports to help us fix failures. Reports contain technical details about the failure and the app/device environment. Our JavaScript error filter removes user details, request bodies, free-form messages, private notes, invitation secrets, and breadcrumbs. Server-side scrubbing is also configured. Native crash reports follow a separate path and may include crash identifiers, operating-system and device details, and native stack traces. These reports are not covered by the JavaScript filter, and we do not claim that all diagnostic reports are anonymous.

Session replay, screenshots, view hierarchies, profiling, performance tracing, and application log collection through Sentry are disabled. This does not mean our hosting providers receive no network or operational logs.

Service providers and support access

Convex supplies our database and authentication infrastructure; Vercel hosts the website; Apple and Google provide sign-in; Expo supplies updates and push delivery; and Sentry supplies error reporting. Support email is handled through Wecode’s mail services. Apple and Google also process information under their own policies when you use their accounts and platforms.

Administrative access is restricted. Routine support views limit access to private content; viewing sensitive notes requires a recorded reason and an audited support grant that expires after 15 minutes. Information may also be disclosed where legally required, subject to the applicable request and safeguards.

Where information is processed

Our production Convex database is in Ireland, website server rendering is configured in Dublin, and our Sentry projects use its EU region. Some providers and their subcontractors may process information outside the European Economic Area, including in the United States. An EU server region does not guarantee that all processing takes place in Europe.

Transfers outside the European Economic Area require a lawful transfer mechanism, such as an applicable adequacy decision or EU Standard Contractual Clauses with any necessary additional protections. Contact support to request information about the provider arrangements and safeguards relevant to your data.

Deleting your account

On the website, open Settings → Account → Delete account, type DELETE, and confirm. On iOS or Android, open Settings → Delete account and confirm the dialog. If you cannot sign in, use our account-deletion instructions or contact support.

Deletion ends access and replaces your display name with “Former partner”; your email and personal partner label are removed. Background cleanup removes linked sign-in profiles, authentication records, your activity notes (including copies in activity edit records), device tokens, and notifications. Cleanup is not instantaneous.

Some shared records remain, including activity names, dates, points, results, household relationships, and internal identifiers. Administrative records can also remain. These records are not necessarily anonymous: your former partner may recognize the history. Contact us if a retained activity name or other record contains personal information that you want removed. A deletion request does not delete your Apple or Google account.

How long information is kept

Account and household data are kept to provide your account and history, subject to deletion as described above. Archived household history does not currently expire automatically, including after both members leave. Contact support to request review or removal of personal information in retained history. Routine audit events, activity edit records, and expired support-access records become eligible for deletion after 90 days. An hourly job removes eligible records in batches. This does not delete household activities or score history.

Support correspondence is held in Wecode’s mailbox until it is manually deleted. Automatic expiry is not enabled, so messages are not automatically removed 12 months after closure. Contact support to request deletion of correspondence. We assess any need to retain information for an unresolved request or legal obligation when handling your request.

Production database backups are configured for seven-day retention. Deleted information may remain in a backup until it expires. Diagnostic and hosting logs have separate retention periods determined by the provider, service plan and account settings; the seven-day backup period does not apply to them. Contact support for information about a particular record or provider. We do not claim that account deletion immediately removes every copy from every provider.

Your rights

Depending on the applicable conditions, you can request access to your personal information, correction, erasure, restriction of processing, or a portable copy. You can object to processing based on legitimate interests. Where processing relies on consent, you can withdraw it without affecting earlier lawful processing.

Email support@homefeud.com to exercise these rights. We may need proportionate information to verify your identity. Never send your password, sign-in code, or private household notes. Requests are normally free and must be answered within one month; if a permitted extension is needed, we must explain it within that month.

You may complain to Sweden’s supervisory authority, the Swedish Authority for Privacy Protection (IMY), or another competent supervisory authority.

Age requirement

HomeFeud is intended for people aged 18 and over. If you believe someone under 18 has provided personal information through HomeFeud, contact support so we can investigate and handle the account and information appropriately.

Earlier versions and policy changes

This policy concerns HomeFeud 3.0. Previous accounts and household history are not imported into 3.0. This fresh start does not delete records held by the earlier service; contact support about those records. Material changes to this policy will be communicated through the service or another appropriate channel. The effective date above identifies this version of the policy.