Bounty signup required fields due date and postcode

Which fields are starred on the Bounty join form?

The public join panel on Bounty’s packs page (checked 10 September 2026) is headed ‘Join Bounty in a few steps’ and stars:

A checkbox sits under the password: you may opt into Bounty emails that include baby-development updates and offers from Bounty and on behalf of its selected partners. Creating the account is treated as agreeing to the terms, privacy policy and cookie policy.

Why does the due date drive the weekly emails?

Bounty markets ‘week-by-week baby development emails’. The 20 May 2025 policy is blunt about the mechanism. It lists collection of due date and pregnancy status for the Bounty Club, directly from the individual, on the legal basis of consent. A later row says it processes due date and pregnancy status to target discounts, offers and pregnancy/child development information according to due date, and for research and statistical analysis of that targeting. Another row says name and contact details are used so information is aligned to your stage of pregnancy.

Without a due date the weekly series has no week number to hang on. That is why the field becomes required once you tick that you or your partner is pregnant. The join panel also offers ‘Remove pregnancy’, which clears that branch rather than inventing a date.

The same policy says Bounty keeps and processes information until the youngest child on the account turns five, then deletes the family record. A due date is not a one-week cookie; it starts a multi-year timeline.

Why is postcode a required field if the folder is not posted?

The prenatal folder is not posted to that postcode. Bounty’s pack FAQ says folders go to clinics and cannot be mailed to individuals. On the join form, postcode is still starred because the policy treats postal address as core contact data: service messages, some marketing by post if you agreed, and — on the app — examples such as a nearest hospital or vouchers that can be redeemed near you. Location on the app is a separate device permission you can refuse; the typed postcode is still part of the account.

The ICO-era field list quoted in *Underwood v Bounty* also included postcode on records collected in 2017–18. That is history. On the 2026 form it remains a live starred box.

How do you read the data-for-emails trade before you tap create?

1. 1
   Decide if you want the weekly series at all If you only want the 12-week clinic folder, you do not need this form. Ask the midwife. If you do want week-by-week emails, the due date is the field that schedules them.
2. 2
   Read the partner checkbox as a second product Development emails and ‘offers from Bounty and on behalf of its selected partners’ share one tick on the panel. The May 2025 policy says partner mail is sent by Bounty unless you have consented to a partner writing directly. Named partners live on Bounty’s own list, which changes; this page does not reprint it.
3. 3
   Treat optional Membership Clubs as other controllers The policy says clubs offered at registration are optional. If you join one, that club becomes a separate data controller and needs its own unsubscribe later.
4. 4
   Use My Profile if you already submitted The policy says you can edit details and communication preferences in My Profile, or use the unsubscribe link on any Bounty email. Due-date mistakes are an account edit, not a new pack claim.

In shortIn short: postcode and due date are starred because they power location-shaped contact and week-numbered emails, not because they unlock a posted folder. The folder still comes from a clinic. The form is the membership trade described in the 20 May 2025 policy.

What does the first panel not star, that the policy still mentions?

• Phone number — in the policy for recalls, some service calls and some marketing if you agreed; not a star on the first panel checked in September 2026.
• Full postal address beyond postcode — policy lists postal address; the first panel only forces postcode.
• Baby name, gender, baby date of birth — policy lists these after birth, including for popular-name articles.
• Number and ages of other children — policy lists them for personalisation.

Those extra fields can appear later in My Profile or after you add a child. They are not an excuse to skip reading the starred block on day one.

Who does Bounty say the form is not for?

The May 2025 policy says regulation means Bounty cannot offer its services to anyone under 16, or under 18 for JoyAtHomeShoot portrait services. A separate app notice says the app is not intended for users under 17, while parents may give information about their children. Date of birth on the join form is the age-validation field for that gate.