A creator shipping address form should collect the recipient name, delivery address, a way to resolve delivery questions, and any product choice needed to prepare the package. Ask the creator to confirm that they want this shipment. Explain who will use their details and when you will remove them. Keep marketing choices, future gifts and posting commitments separate.
Treat the field list below as a starting point for an adult-creator seeding program. It is an operational recommendation, not a universal carrier specification or a complete privacy notice.
Choose the fields before choosing the form tool
Start with one question for every field: what will the fulfilment team do with this answer? If nobody can name an action, leave it out.
The UK Information Commissioner's Office describes data minimisation, purpose limitation and storage limitation as data protection principles. For a shipping form, that means designing around the shipment rather than collecting everything that might help a future campaign.
| Field | Suggested treatment | Reason |
|---|---|---|
| Creator reference | Carry over the invitation reference | Match the response without asking for follower counts or every profile again |
| Recipient name | Required | Identify the intended recipient; allow an approved receiving contact |
| Country or destination | Ask before address details | Select the appropriate address fields and supported destination |
| Delivery address | Required for dispatch | Collect address lines and the locality, region and postal fields needed for that destination |
| Apartment, suite or receiving company | Show where relevant | Let the recipient supply details that distinguish the delivery point |
| Delivery contact | Confirm one existing contact where possible | Resolve questions without collecting duplicate email addresses |
| Telephone number | Conditional | Add only after verifying a need for the selected shipping service; explain that need |
| Product or variant | Include only if there is a choice | Prepare the agreed item without another exchange |
| Delivery note | Optional and narrowly described | Ask for delivery instructions, not personal background |
| Shipment acceptance | A clear affirmative choice | Record that the creator wants this specific package |
Do not require a home address if the creator can supply another suitable receiving address. Verify that the chosen delivery arrangement supports it. Do not ask for identity documents, birth dates, tax identifiers or household details by default. If a particular shipment needs additional information, confirm the applicable requirement before adding a separate request.
Avoid a broad field called "Anything we should know?" It invites information the shipping team may never need. Use product choices where possible, and avoid collecting medical histories to decide which gift to send.
Address correction is a separate step. Use recipient confirmation before changing uncertain address details rather than silently rewriting the submitted answer.
Separate accepting a gift from the legal basis for processing
A creator saying "yes, send this package" gives you a clear operational instruction. Your privacy review still needs to identify the lawful basis for handling their data.
Under UK GDPR guidance, consent is one possible basis. The ICO's valid-consent guidance explains that another basis may suit fulfilment better. It also distinguishes express consent statements from consent inferred through actions. Ordinary address collection does not automatically require the special legal standard of explicit consent.
If your program relies on consent, use clear words describing the data use, an unselected choice, and a way to withdraw. A checkbox saying only "I have read the privacy policy" does not establish agreement to a specified use. Silence and preselected boxes do not establish valid consent either.
Keep these decisions separate:
- Accept this shipment and use the necessary details to arrange it.
- Keep an address available for later gifts, if your program offers that option and has reviewed the basis for doing so.
- Receive optional marketing messages through a named channel.
- Agree to content deliverables or usage rights through a separate agreement.
Do not make the gift depend on agreeing to unrelated marketing. Do not interpret a shipping phone number as permission to send promotional texts.
For a no-obligation gift, the form can state: "Accepting this gift does not require you to publish content." Only use that sentence when it matches the offer. If you need a post, settle that arrangement before collecting the shipping details. Address submission should not conceal a new commitment.
Put the data-use explanation beside the fields
The short explanation should identify the sender, describe the shipment purpose, name the relevant recipients or recipient categories, and explain retention. Link to the fuller privacy notice before the creator submits.
For UK GDPR-covered processing, the ICO's privacy information guidance also covers the lawful basis, applicable rights and complaint information. Retention information can specify a period or explain the criteria used to determine it. The ICO pages cited here carry notices that they are under review following the Data (Use and Access) Act. Have your privacy owner check the applicable rules before launch.
Give that owner concrete questions:
- Which legal entity collects the answers, and how can the creator contact it?
- Which form provider, warehouse, ecommerce system and carrier will receive each field?
- Does an agency need the full address, or only confirmation that shipping is underway?
- Where will answers appear beyond the form, including notifications, exports and support tickets?
- What event starts the retention period, and who runs deletion?
- Which records need separate retention, for what reason, and for how long?
- How can a creator correct details, cancel a pending shipment or exercise applicable privacy rights?
Modash's gifting-platform overview describes workflows where a submitted form creates an ecommerce order. That is a reason to inspect downstream records. Deleting the form response may leave an address in an order, export or fulfilment system.
Keep the address out of the campaign report
As an operational default, restrict full addresses to people arranging fulfilment and resolving delivery problems. Put shipment references and statuses in the shared campaign tracker. Colleagues evaluating content rarely need a creator's street address.
Use a retention schedule that distinguishes the working address list from records kept for a separate, documented purpose. Do not promise immediate deletion everywhere unless the form provider, warehouse and other recipients can support that promise. Name a person who owns removal from exports as well as the main system.
A shipment tracker with separate approval and delivery states lets the team follow progress without copying addresses into every report. Reconfirm the destination before another shipment instead of assuming the old address remains current.
Keep disclosure and content rights outside shipping consent
A voluntary post can still need a disclosure. In the United States, the FTC's influencer disclosure guidance says free products can create a material connection. Its guidance calls for disclosure when a creator mentions a gifted product, even if the brand did not request that mention. It also addresses posts from abroad that foreseeably affect US consumers.
Explain that distinction in the gifting invitation. Do not turn the disclosure reminder into a promise to post, and do not bundle advertising rights into the address form. If a creator later publishes something you want to use, ask separately for permission to reuse the post.
Before sending the form, submit a test response with fictional details. Follow it through every connected system. Remove fields nobody uses, confirm who can read the remaining answers, and assign the deletion task before inviting creators.
