Your family’s details are not marketing data.

What this site handles

ThinkieInkies does not create customer accounts or receive card or bank details. Stripe processes website payments. Product pages let you browse and buy without a marketplace account.

Checkout collects the contact information, delivery address and personalization needed to prepare your selected order.

A product page may let you type a name for an on-screen preview. That text stays in the current browser session and is never included in analytics or checkout automatically.

Before an enabled Stripe checkout opens, the site stores a minimized order record needed for payment integrity and reconciliation. It contains an opaque order and attempt ID, provider, product slug and SKU, immutable per-line quantities/prices, option codes and non-personal required-field keys, catalog version, currency, item/shipping/tax/total amounts, payment and fulfillment states, and timestamps. The event ledger stores only provider event/object IDs, type, mode, timestamps and a one-way payload hash. It does not store names, email, phone, delivery address, card or bank data, personalization, IP address, browser identifier, raw provider payload or webhook signature.

For website orders, we also keep a separate protected fulfillment record after Stripe confirms payment. It contains the recipient’s name, email, phone, delivery address, and personalization entered at checkout. The store owner can view these details to make and deliver your order and respond to order questions. They are not sent to advertising tools. Card and bank details are not stored on this website. Contact the store with any question about your order data or a deletion request.

During an enabled Stripe shipping calculation, the name and US address entered in Stripe's embedded form pass transiently through the same-origin checkout endpoint so Stripe can retain them. The site sends USPS only the origin and destination ZIP codes, the approved package measurements and classification needed for a Ground Advantage price. It does not persist or log the name, address or raw ZIP. D1 keeps only the quoted service and amounts, expiry, one-way hashes of the parcel and line-item snapshots, and an HMAC tag that cannot be used to recover the ZIP. Stripe's signed webhook must match that record before the order is marked paid.

To prepare a physical paid order for shipping, an authorized owner can ask the site to retrieve the recipient name, email and delivery address from the matching Stripe Checkout Session. The site validates that session against the paid order and returns those details in a protected CSV together with every SKU, selected option identity and an exact measured parcel profile for that single variant or cart composition. The application does not write the recipient details or CSV to D1 or its logs. The owner temporarily downloads the CSV to a trusted device, uploads it to Pirate Ship to review rates and buy a label, and must delete the local file after use. Pirate Ship processes the uploaded data under its own privacy and data terms.

Query-bearing checkout success pages, cancellation pages and owner admin pages keep optional measurement tags inactive, so payment references and shipping-export credentials are not used for analytics or advertising measurement. After a Stripe order is confirmed paid in the ledger, the site can set a host-only HttpOnly receipt marker with a five-minute maximum lifetime and move the browser to a query-free confirmation page. That page rechecks the paid order before any conversion event is eligible, then the response clears the marker.

Why order records are kept

The minimized ledger is necessary to prevent duplicate charges, verify signed provider updates, keep a paid order from being changed by a later catalog edit, and support manual reconciliation. It is independent of the optional advertising choice. Records are kept for fulfillment, customer support, payment reconciliation and applicable legal requirements. Contact us to ask about or request deletion of your personal data; some records may need to be retained for legal obligations. Provider records follow their own policies.

Optional analytics and advertising tags

If you select Allow, this site may load configured analytics or advertising tags from Google, Meta, TikTok, Pinterest and Microsoft Advertising. They can receive page views, a non-personal product identifier, price, currency and standard browser or device information. If you allow tags and a Stripe payment passes both receipt checks, configured providers can also receive quantity, verified item/shipping/tax/total amounts and one-way transaction and event identifiers. The site does not send the internal order ID, Stripe references, names, email addresses, personalization text or free-form searches to these services.

When a configured server measurement connection is fully enabled, the query-free confirmation page can also send a server copy of the same verified Stripe purchase. It does this only after the browser confirms your current Allow choice with a signed, host-only HttpOnly consent cookie. The copy uses the same one-way event identifier as the browser event so providers can deduplicate it. Payment webhooks never trigger advertising sends, and a provider that is missing any required credential stays off.

For that consented server copy, configured providers can receive the standard network address and browser user-agent sent with the confirmation request, plus their own browser or advertising click identifiers when present. These transient values are forwarded only for the immediate provider request; the application does not save them, cookies, access tokens or provider request payloads in its D1 delivery record or application logs. That record contains only one-way event data, provider/status metadata, consent policy/time and the already-minimized internal order reference needed for bounded retry and deduplication. There is no background advertising sender.

Campaign parameters such as UTM values or advertising click IDs can be remembered in your browser after you allow analytics. Before that choice, they can be held only in the current page’s memory so your decision can be applied; they are not stored or sent to advertising vendors. Declining removes stored campaign attribution and prevents optional tags from loading. After a verified conversion is dispatched, the browser can retain up to 64 one-way event identifiers to prevent a refresh from counting the same payment twice; declining removes that deduplication record too.

Advertising providers and choices

After you choose Allow, configured providers may use cookies, pixels, web beacons or similar browser storage to measure visits and product actions, attribute advertising, build audiences and help show or limit relevant ads. ThinkieInkies controls the event fields intentionally sent by this site, while each provider separately handles standard browser, device and network data under its own policy.

• Meta: Privacy Policy and Ad preferences
• TikTok: TikTok for Business Privacy Policy
• Google: Privacy Policy and My Ad Center
• Pinterest: Privacy Policy
• Microsoft Advertising: Microsoft Privacy Statement and advertising settings

You can also use industry opt-out tools from YourAdChoices or the Network Advertising Initiative. These controls complement, rather than replace, the ThinkieInkies Privacy choices button below.

Your choices

The site stores your Allow or Decline selection so it can respect that choice on later visits. You can reopen the controls at any time. If you withdraw a previous Allow choice, the page reloads so already-loaded vendor scripts are cleared from the active page. Decline also blocks server purchase measurement immediately in that page and asks the site to expire its HttpOnly measurement-consent cookie; a network failure while making that request does not re-enable measurement.

External links and questions

Payment and sharing services have their own privacy terms. For a privacy question or an order placed on this website, use the store contact page. Do not include card or bank details in a message.

Last updated: August 27, 2026.