Privacy policy

Who is responsible for your information

Forward Digital Ltd owns and operates Unfaff and is the data controller responsible for personal information processed to run it. Our address appears at the end of this page. Use the contact details there for privacy questions or to exercise your rights.

Information you give us

Account information includes your email address, display name, sign-in provider and an optional profile image. We store group names, memberships and roles; the ideas, notes and photos you add; preferences chosen in a quiz; saved choices and quiz history.

If you enable push notifications, we store your notification preference and a device installation identifier and push token so we can deliver picked-idea notifications to your signed-in mobile devices.

We also receive the messages and attachments you send when you ask for help. Do not send passwords, verification codes or payment card details. You do not have to add an optional photo, but an email address and account details are needed to create and secure an account.

Information from other sources

A connected sign-in provider supplies information needed to authenticate you, such as an account identifier and email address. Other group members may add shared content or invite you to their group.

Payment providers and RevenueCat supply subscription identifiers, products, purchase status and expiry information so we can provide Plus and handle billing enquiries. Payment card details are handled by the payment provider; Unfaff does not store your full card number.

Why we use information

We use account, group, idea, quiz and subscription information to provide the service you request and fulfil our contract with you. This includes authenticating you, displaying shared content, choosing ideas, enabling paid benefits and sending essential account emails.

Optional picked-idea notifications are off until you enable them in Settings. You can turn them off there or through your device settings. Notifications contain the group name, the name of the person who picked and the idea title, which may appear on your lock screen.

We use technical and security records to protect accounts, prevent misuse, investigate errors and maintain a reliable service. Our proposed lawful basis is legitimate interests in securing and operating Unfaff, balanced against your rights. We use support correspondence to respond to your request, on the basis of our contract or legitimate interests in providing support.

We may retain information to comply with legal duties, including applicable accounting requirements, and use it to establish or defend legal claims. If we introduce optional marketing or tracking that requires consent, we will explain it and obtain that consent first. We do not sell personal information.

What your group can see

Group members see shared ideas, notes and photos, and the names and profile images shown within their group. Owners and admins can manage the group according to their role. Consider what you share, especially information about another person.

Content shared with a group can remain after its contributor leaves or deletes their account. Deleted accounts are shown as Deleted user. Removing the account attribution does not remove personal information someone wrote inside an idea or uploaded in a photo. Contact us if retained content identifies you and you need it reviewed.

Technical information and monitoring

Hosting and authentication services process network information such as IP addresses, request details, browser or device information and security logs. The app uses local storage or secure device storage for sign-in sessions and preferences. The marketing site uses a cookie when an editor opens a draft preview.

The current hosted development app uses PostHog for page or screen visits, clicks or touches, application lifecycle events and errors. Route identifiers and event properties are sanitised; input text and credentials are excluded from intended event capture. Session replay is disabled. Development monitoring is not enabled in the public marketing website or in mock mode.

Production analytics and any non-essential cookies or similar tracking must have their privacy basis and consent controls confirmed before launch. This draft does not claim that consent controls already exist.

Providers and other recipients

Our service providers include Supabase for authentication and database hosting, AWS S3 for uploaded photos, Vercel for website/API hosting, Resend for transactional email, RevenueCat for subscription administration, and Stripe or the relevant app store for payments. Storyblok hosts public journal content and its assets. PostHog processes the development monitoring described above.

These providers receive information needed for their service. Sign-in providers and payment providers may also process data under their own privacy policies. We may disclose information when legally required, to protect rights or investigate misuse, or as part of a business transfer with appropriate notice and protections.

Expo and Google Firebase Cloud Messaging deliver Android push notifications. They receive the push token and notification content needed to route messages to your device.

Where information is processed

The current development database and photo storage are in London, and the Storyblok and PostHog projects use EU regions. This does not mean every provider operation stays in the UK or EU. Providers may process information or provide support from other countries.

Before public launch, we must confirm the actual international transfers and applicable safeguards for each provider, such as an adequacy decision or approved contractual protections. You can request details and copies of applicable safeguards through our privacy contact.

How long we keep information

We keep account information while the account is active and shared content while the relevant group retains it. Account deletion removes the authentication account and personal profile, subject to shared-content behaviour described above. Media deletion is queued for background cleanup rather than guaranteed to happen immediately.

We remove a device registration when you sign out of that device or the push provider reports it is no longer registered. Account deletion removes notification preferences and device registrations. Notification delivery records are removed after seven days.

We decide how long to retain support correspondence, security records, subscription records and backups based on the purpose, legal requirements, dispute needs and the relevant provider's retention settings. Backups may retain deleted information until they expire. Final provider retention periods and a support-record schedule must be confirmed before public launch.

Your rights and choices

Depending on the circumstances, you can ask to access, correct or erase your personal information, restrict its use or receive a portable copy. You can update your profile and delete your account in account settings. We may need to verify your identity before acting on a request.

You have the right to object to processing based on legitimate interests. Contact our privacy inbox and explain which processing you object to. If we rely on consent, you can withdraw it without affecting earlier lawful processing.

You can complain to the UK Information Commissioner's Office at ico.org.uk/make-a-complaint or call 0303 123 1113. You can also contact your local data protection authority where applicable. We would welcome the chance to address your concern first.

Children, recommendations and changes

Unfaff is intended for adults aged 18 and over. Contact us if you believe a child has provided personal information so we can investigate.

The quiz matches your chosen preferences to your group's ideas. It does not make decisions with legal or similarly significant effects. We will update this dated policy when our data practices change and provide notice of material changes where appropriate.

Operator and contact details

Forward Digital Ltd

64 Nile Street, Shoreditch, London, N1 7SR

hello@unfaff.app