1. Scope and necessary storage
Yuna uses browser storage for sign-in sessions and to keep the intended sign-in destination, selected onboarding company and chat/interface state. Local storage and session storage are relevant even when no conventional cookie is set.
Widget session data supports authorised access from verified websites. Its exact deployment-side storage and duration require an inventory. Clearing authentication storage can sign you out; clearing interface storage can reset choices.
2. Embedded services
Stripe checkout is embedded when a billing flow is opened. Stripe and its payment services may use their own storage for payment, fraud prevention and saved payment experiences. Google sign-in involves Google’s separate service and notice.
The preview footer itself does not load a payment form or payment-tracking script merely to show payment logos.
3. Optional tracking and consent
No optional analytics or advertising consent is introduced by this build. This source review is not a complete inventory of hosting-side analytics, external services or third-party cookies.
Browser settings can remove or restrict cookies and site storage, but necessary authentication/payment features may then stop working.
Requires approval / verification
Verify storage names, providers, purposes and durations across local preview, published hosting, Google sign-in, widget and Stripe checkout. Decide which are strictly necessary and whether consent controls are needed. Do not deploy optional non-essential tracking before any required consent.
4. Contact and review
Questions about storage and privacy: yuna@hoffstedts.se. This draft has no effective date and must be reconciled with the final technical inventory and Privacy Policy before launch.