Trust through specificity

The operating boundaries are part of the product.

These are the launch facts that shape what Warmly can do today. The linked public policies provide the full operational detail.

Operating facts

Trust starts with what the product does—and does not do.

Payments stay with Stripe

Warmly records the purchase state while Stripe processes payment details and confirmation.

Consent and channel control stay explicit

Optional measurement and messaging paths remain bounded by the choices and eligible delivery controls shown to the user.

Physical fulfillment remains human-led

Gift sourcing, substitutions, shipping evidence, and exceptions are operational work—not invisible automation.

Meet the Warmly team

Delivery

Cloud delivery is the default. Plans expose scheduled, attention, and delivery states instead of claiming invisible certainty. Premium assisted device sending remains user-operated.

Fulfillment

Physical gifts and gift cards are sourced through Human Operations. Substitutions, evidence, shipping, and exceptions remain manual operational work.

Money

Payments are USD-only. Pools fund one selected order or refund to original payment methods; they never create a wallet or cash balance.

Gift cards

The current public card option is a generic store gift card fulfilled manually in the United States. Retailer terms govern use, expiration, loss, and replacement.

Authority

Personal and Professional workspaces manage people. Company workspaces use employee rosters, departments, policies, approvals, budgets, and audit.

Advertising

Only the five eligible public ad landing pages can load configured Google measurement before a choice, with storage denied and ad-click data redacted; cookieless signals may be sent. Other eligible pages require matching consent, signed-in routes disable automatic page views and use a generic app location, and token or capability routes plus admin and operations routes never load the tag. Optional identifiers, analytics events, and Ads conversion events require the matching consent. Enhanced conversions and customer-data matching are off. Meta Pixel requires Advertising consent and measures public product landing visits and completed registrations on account entry, workspace home, or initial onboarding pages. Its standard metadata includes the page URL; see Privacy for details. It does not load on contact, order, payment, administrative, or token pages, and automatic events and advanced matching are off.