Privacy Policy

This Privacy Policy explains how Puffling, Inc. ("Puffling," "we," "us," "our") collects, uses, discloses, and retains information when you use our mobile application, website(s), online checkout, physical-product ordering features, and related services (collectively, the "Service").

By using the Service, you acknowledge the practices described in this Privacy Policy.

1) Who Puffling is for

Puffling is designed for parents/guardians and adult caregivers. The Service provides personalized play activities, stories, and rhymes for children.

Children should not use the Service to create accounts or provide information directly to us.

2) Summary of key points

• For the app and founding lists, we collect limited information about parents/guardians, such as first name and email.
• We collect structured information about children that parents/guardians choose to provide (child first name, birthdate, age range, interests, milestone selections).
• The Puffling app does not ask for phone numbers, photos, audio, or video.
• Puffling does not run ads or add advertising or retargeting SDKs to the Service.
• If you join a product founding list, we use your email address for the product previews, research invitations, and launch updates you requested.
• Website analytics uses a session identifier in session storage. We do not use a persistent cross-session advertising identifier.
• When physical-product ordering is available, we collect the contact, delivery, order, and fulfillment information needed to complete and support an order.
• Stripe provides the embedded shipping and payment components for website checkout. Payment card details entered in Stripe's payment fields go directly to Stripe; Puffling does not receive or store your full card number or card security code.
• We use third-party AI processing providers to generate content. We do not send a child's birthdate to those providers; we send an age range instead (e.g., "2-3 years old"). We require that those providers do not train on data we send them.
• We do not store prompts. We do store generated outputs so you can access and sync them across devices.
• You can delete a child profile or app account in-app. App profile data and order records follow different retention rules; deleting an app account does not automatically delete records we must keep for completed or attempted orders.

3) Information we collect

3.1 Information you provide (parents/guardians)

• Parent/guardian first name
• Email address
• Product research or founding-list preferences you choose
• Support/contact communications (if you email us)

3.2 Child profile information (provided by parent/guardian)

We collect child profile information only when a parent/guardian chooses to create or update a child profile, including:

• Child first name (text field)
• Child birthdate (used to derive an age range for personalization, e.g., "2-3 years old")
• Interests (short text fields; intended as simple terms like "trains")
• Developmental milestones (checkbox selections)

3.3 Generated content you save

Generated outputs (e.g., activities, stories, rhymes) that the Service creates and stores for you so you can revisit or sync them.

3.4 Device and service data

We collect information needed to operate the Service, such as:

• Device and app information (e.g., device type, OS version, app version)
• Operational logs (e.g., events needed to diagnose issues, prevent abuse, and keep the Service reliable)
• Website session data, such as pages viewed, interaction events, approximate screen size, campaign parameters, and a referrer origin and path with query parameters removed
• A randomly generated website session identifier stored in session storage and deleted by the browser when the session ends
• A salted hash of the network address and coarse country/region information used for security and aggregate traffic reporting; we do not store the raw network address in website analytics

We perform analytics and crash reporting using first-party tools and Apple platform APIs. We do not use third-party advertising or retargeting SDKs.

3.5 Payment information

App subscriptions. If you purchase a subscription via Apple In-App Purchase, Apple processes the transaction. We do not receive your full payment card information. We may receive purchase-related information needed to provide access (e.g., subscription status and renewal dates as provided by Apple).

Website orders. When physical-product ordering is available, Stripe provides the shipping and payment components embedded in our checkout. Stripe tokenizes sensitive payment details inside its hosted payment fields. Puffling does not receive or store your full card number or card security code. We receive and store transaction identifiers and status information from Stripe, such as a checkout-session identifier, payment-intent identifier, payment status, paid amount, tax, refunds, and disputes, as needed to operate and support the order.

3.6 Physical checkout, order, and fulfillment information

When website ordering is available and you begin or complete checkout, we and Stripe process information such as:

• Your email address, shipping recipient name, and delivery address
• The product, quantity, product-content version, price, shipping amount, discounts, tax, currency, and total
• The commerce-terms version presented and the time acceptance is recorded
• A random checkout request token, checkout reservation and expiration information, and Stripe transaction identifiers
• Order number, payment status, production status, promised ship-by date, fulfillment status, carrier, shipping service, tracking number, and relevant timestamps
• Return, refund, dispute, replacement, support, and product-safety communications associated with the order

The delivery address is entered in a Stripe component. When you ask us to save it during checkout, the address passes through Puffling's server so we can validate the delivery area and is then sent to Stripe for the checkout session. If payment completes, Puffling stores the delivery address in its order record for fulfillment and support.

3.7 Checkout sessions and private order links

Our checkout creates a random request token in browser session storage and in our order system so repeated requests can refer to the same short-lived checkout reservation. Stripe creates a separate checkout-session identifier. A checkout attempt can leave a reservation and transaction-status record even if the purchase does not complete.

After a completed order, we create a random private order-status link and send it to the order email address. Anyone who has that link may be able to view the order number, purchased items, charges, order and shipment status, and tracking information. The status page does not display the customer email or delivery address. Keep the link private and contact us if you believe it has been shared with someone who should not have it.

4) How we use information

We use information to:

Provide and operate the Service

• Create and manage accounts
• Create and manage child profiles
• Generate personalized content and features

Personalize outputs

• Use child profile attributes (age range, interests, milestones) to tailor activities, stories, and rhymes

Store and sync outputs

• Store generated outputs so you can access them later and sync across devices

Process and fulfill physical-product orders

• Create a short-lived checkout reservation and prevent duplicate checkout requests
• Validate the delivery area, provide order totals and shipping information, and calculate or record applicable tax
• Record the commerce-terms version accepted for an order and confirm payment through Stripe
• Prepare, fulfill, ship, track, support, refund, or otherwise administer an order
• Handle payment disputes, product-safety matters, recalls, replacements, and legal or accounting requirements

Maintain safety, security, and reliability

• Monitor for abuse, protect infrastructure, and diagnose bugs
• Prevent fraud and enforce our Terms of Service

Communicate with you

• Send service-related messages (e.g., account confirmations)
• Send transactional order receipts, shipping and tracking updates, support responses, and necessary product-safety notices
• Send marketing emails if you opt in or where permitted by law (you can unsubscribe at any time)
• Send product previews, research invitations, and launch updates when you join a founding list

Comply with legal obligations

• Respond to lawful requests and meet tax, accounting, consumer-protection, product-safety, and other regulatory requirements

5) AI processing and third-party model providers

5.1 What we send to AI processing providers

To generate content, we may share limited context with third-party AI processing providers, such as:

• Child first name
• Child interests
• Age range derived from birthdate (e.g., "2-3 years old"); we do not send the birthdate itself
• Selected milestone categories
• The type of content requested (e.g., activity, story, or rhyme)

5.2 Training restrictions

We contractually require that third-party AI processing providers do not train their models on the data we send them for Puffling's requests.

5.3 Prompt storage

We do not store prompts in our systems. Operational logs may capture limited metadata (such as timestamps and request types) needed for reliability and abuse prevention, but not the full content of prompts.

5.4 Output storage

We store generated outputs so you can access them later and sync them to your account.

6) How we disclose information

We do not sell your personal information.

We may disclose information in the following circumstances:

6.1 Service providers and processors

We disclose information to providers that help us operate the Service, subject to appropriate contractual and legal protections. Provider categories include:

• Hosting, database, infrastructure, security, and operational-support providers
• Apple for in-app subscription processing
• Stripe for website checkout, payment processing, fraud prevention, refunds and disputes, and, when enabled, tax calculation
• Transactional email providers for receipts, shipment notices, and other service messages
• Shipping carriers and fulfillment or shipping-label service providers for delivery and tracking
• AI processing providers for the limited purposes described in Section 5

Some providers act only on our instructions, while others process information under their own legal obligations or privacy terms for functions such as payment processing and fraud prevention.

6.2 Stripe checkout data

Stripe receives information entered in its checkout components, which can include card details, billing details, shipping information, email, order and transaction details, and information entered even if a checkout is not completed. Stripe may also collect browser, device, IP address, cookie, and interaction information directly through Stripe.js and Elements to provide its services and prevent fraud. Stripe's handling of information for its own purposes is described in the Stripe Privacy Policy.

6.3 Legal and safety

We may disclose information if we believe it is reasonably necessary to:

• Comply with law, regulation, legal process, or governmental request
• Protect the rights, property, or safety of Puffling, our users, children, or the public
• Investigate and prevent fraud or security issues

6.4 Business transfers

If Puffling is involved in a merger, acquisition, financing, reorganization, bankruptcy, or sale of assets, information may be transferred as part of that transaction, subject to appropriate confidentiality protections.

7) Data retention

We retain information for as long as your account is active or as reasonably needed for the purpose for which it was collected, to provide the Service, and to meet our legal obligations.

When you delete:

• A child profile: We delete the associated child profile information and related outputs tied to that profile.
• Your app account: We delete your app account information, child profiles, and stored outputs, subject to limited residual copies described below. App-account deletion does not automatically delete separate physical-order records.

Inactive accounts: If your account has been inactive for three (3) years, we may delete it after providing notice to the email address on file.

Founding lists and contact requests: We retain a founding-list email until you unsubscribe, ask us to delete it, or the applicable product research program ends. We generally retain contact-request records for no longer than 24 months after the last exchange unless a longer period is needed for security or legal obligations.

Checkout and physical-order records: We retain checkout-reservation, transaction, order, delivery, refund, dispute, support, and product-safety records for as long as reasonably needed to complete and support the transaction; maintain tax and accounting records; prevent fraud; resolve refunds, chargebacks, or other disputes; address safety or recall obligations; enforce agreements; and comply with law. The applicable period depends on the record and the reason it is needed. An incomplete checkout may leave a reservation and transaction-status record even if no order is completed.

Website analytics: We retain identifiable session-level website analytics for up to 13 months, after which it is deleted or aggregated.

Backups and logs: Residual copies may remain temporarily in backups or logs for security, integrity, or disaster recovery purposes. Such copies are typically deleted or overwritten within 90 days in accordance with our normal backup lifecycle.

8) Your choices and rights

8.1 In-app controls

You can:

• Edit or delete a child profile in the app
• Delete your app account in the app, which deletes the app-account data described in Section 7

Physical orders do not require an app account, and deleting an app account does not automatically delete order records. Contact us to make a privacy request about order information; we may retain records where permitted or required for the purposes described in Section 7.

8.2 Marketing emails

You can opt out of marketing emails at any time by using the unsubscribe link in the email or by contacting us at hello@puffling.ai. Even if you opt out, we may still send important service-related messages.

8.3 Rights by region (including GDPR/UK GDPR and CPRA)

Depending on where you live, you may have the right to:

• Request access to your personal data
• Request correction of inaccurate data
• Request deletion of your data
• Request portability (a copy of your data in a commonly used, machine-readable format)
• Object to or request restriction of certain processing (GDPR/UK GDPR)
• Withdraw consent where we rely on consent (GDPR/UK GDPR)
• Request information about disclosures and processing (CPRA)

To exercise rights, email hello@puffling.ai. We may need to verify your identity and/or your authority as a parent/guardian before fulfilling a request.

8.4 California notice (CPRA)

• We do not sell personal information.
• We do not share personal information for cross-context behavioral advertising.
• We do not use or disclose "sensitive personal information" for purposes that require a "Limit the Use of Sensitive Personal Information" link under CPRA.

9) Children's privacy (COPPA)

9.1 We collect child information from parents/guardians

We do not knowingly collect personal information directly from children under 13. Child profile information is entered by a parent/guardian (or authorized caregiver). By creating a child profile, the parent/guardian represents that they have authority to provide this information.

9.2 Parental rights

A parent/guardian can:

• Review or change a child's profile information in-app
• Delete a child's profile in-app
• Delete the account in-app, which deletes associated child data

You can also contact us at hello@puffling.ai for assistance.

9.3 Data minimization and retention for children

We collect only what we need to provide personalization and store outputs for your use. We retain child profile information and outputs until you delete them (see Section 7).

10) International users and cross-border transfers

Puffling is based in the United States and may process information in the United States and other countries where our service providers operate.

If you are located in the European Economic Area (EEA), the United Kingdom, or Switzerland, we rely on appropriate safeguards for international transfers where required, such as Standard Contractual Clauses or other lawful mechanisms.

11) Legal bases for processing (GDPR/UK GDPR)

Where GDPR/UK GDPR applies, we process personal data on one or more of the following legal bases:

• Performance of a contract: To provide the Service you request
• Legitimate interests: To secure, maintain, and improve the Service; prevent abuse; and provide support (balanced against your rights)
• Consent: For certain marketing communications where required
• Legal obligation: To comply with applicable laws

12) Security

We implement reasonable administrative, technical, and physical safeguards designed to protect information from unauthorized access, use, or disclosure. These measures include encryption in transit, restricted file and system access, environment-specific credentials, and security reviews.

Private order-status pages use a random link token and are designed not to display the customer's email or delivery address. Because anyone with the link may be able to view order and tracking details, you should keep it confidential. If you believe a private order link has been exposed, contact us.

No security system is perfect, and we cannot guarantee absolute security. In the event of a data breach affecting your personal information, we will notify you and relevant authorities as required by applicable law.

13) Cookies and similar technologies (website)

The website uses session storage for a short-lived analytics session identifier and removes the legacy persistent visitor identifier if present. When checkout is available, we also use session storage for a random checkout request token that helps repeated requests refer to the same reservation. Session storage is cleared when the browser session ends.

Puffling does not use third-party advertising or retargeting cookies. Stripe's embedded checkout components may use cookies and similar technologies and collect browser, device, network, and interaction information for payment services and fraud prevention as described in Sections 3.5 and 6.2 and in Stripe's privacy materials.

14) Changes to this Privacy Policy

We may update this Privacy Policy from time to time. We will post the updated version and revise the Effective Date above. Your continued use of the Service after an update means you accept the revised Policy.

15) Contact us

For questions, requests, or complaints about privacy, contact:

Puffling, Inc.
251 Little Falls Drive
Wilmington, Delaware 19808
hello@puffling.ai