Privacy Policy

1. Introduction

This Privacy Policy explains what information LapLapLa processes, why it is needed, where it may be sent, and what choices are available to you. Most public content can be viewed without an account.

2. Customer Accounts and Authentication

You may use a LapLapLa customer account for features that require saved access, such as viewing digital products available to your account, managing product access, and returning to saved personalization. An account is not required for ordinary browsing of the public website.

Customer sign-in is provided through Supabase Auth. Depending on the option you choose, authentication may use Google OAuth or a one-time magic link sent to your email address. LapLapLa processes the account email, Supabase user identifier, authentication session, and required security tokens to sign you in and keep the account secure.

Restricted administrator access has a separate authorization flow. Being signed in as a customer does not by itself provide administrator access.

3. Product Access and Personalization

LapLapLa stores information about which digital products a customer account may access. This allows the service to show available products and protect customer-only creation and personalization tools.

When you use a personalization feature, LapLapLa may store the information you choose to enter, such as a display name or participant names, so you can return and edit the product later. You decide what to enter; LapLapLa does not require real names of children or other sensitive information for personalization.

4. Preorder and Early-Access Registration

You may provide an email address to register for the Sound Case #001 preorder. The purpose is to record the preorder, preserve eligibility for the special preorder price, and send a message when the product becomes available. The email is stored in a standardized form so it can later be matched reliably with the verified email of a LapLapLa customer account.

Preorder registration uses single opt-in: eligibility is recorded when you submit the form and expressly agree to receive the product-launch and preorder-price message. It does not automatically create a customer account, is not a purchase, and does not involve a payment. The preorder email is not used as consent for an indefinite general advertising newsletter.

5. Product Analytics

LapLapLa collects pseudonymous usage statistics. Events may include page views, sessions, language, device and viewport category, opening and completing content, use of maps and creative tools, project or export actions, external-link actions, and technical errors.

For analytics, LapLapLa creates a random visitor identifier and session identifier in localStorage. A session may be shared by tabs in the same browser profile and rotates after a period without tracked activity. These analytics identifiers are not intended to contain your name or email address. Preorder email addresses, normalized emails, email hashes, customer identifiers, and preorder record identifiers are not sent as analytics properties.

Raw analytics events are stored in Supabase and are normally deleted after approximately 15 days. Aggregate reports that do not contain individual visitor or session identifiers may be retained for longer.

6. Browser Storage and Local Materials

LapLapLa uses browser storage, including localStorage, sessionStorage, and IndexedDB, for language preferences, authentication sessions, analytics identifiers, application state, and locally created projects where applicable.

Drawings, local studio projects, selected files, and voice recordings may remain on the device using browser storage, data URLs, or temporary blob URLs. If a feature explicitly saves personalization to your account, that personalization is stored by LapLapLa as described above. Analytics may record that an action occurred, but not the contents of a drawing, recording, or local project file.

7. Search and External Media

Search queries may be sent to LapLapLa servers. Searches for images, GIFs, videos, or other media may also be sent to GIPHY, Pexels, Pixabay, Reddit, or Imgflip to return relevant results. Some queries may be stored briefly in a Supabase cache to improve performance.

YouTube provides embedded videos and may receive standard browser and playback request information under Google's policies. External services process information under their own terms and privacy policies.

8. Technical Data, Security, and Diagnostics

LapLapLa uses Sentry for error reports and performance diagnostics. Reports may include a stack trace, route or URL, browser type, runtime environment, and technical request context. Recognized sensitive fields such as authorization tokens, request bodies, cookies, and email addresses are filtered under the current monitoring configuration, but no filtering system can provide an absolute guarantee.

Vercel may create standard hosting and server logs, including request routes, timestamps, status codes, network information, and runtime diagnostics. An IP address may be processed to limit request frequency, prevent abuse, and protect the service. When distributed rate limiting is enabled, a hash of the IP address and request counters may be processed by Upstash for the relevant rate-limit window.

LapLapLa uses HTTPS and reasonable access controls, but no online service can guarantee complete security.

9. Service Providers

LapLapLa uses Supabase for authentication, customer and product-access data, saved personalization, preorder registrations, analytics, public content storage, and other database functions; Sentry for diagnostics; Vercel for hosting and server logs; and, when enabled, Upstash for distributed request limiting. Google provides identity authentication when you choose Google sign-in.

LapLapLa does not currently process payments through PayPal or another payment provider. Payment processing will be described in this policy if and when it becomes available.

10. Age Requirement

The main LapLapLa service is intended for users aged 16 and over and is not intended for users under 16.

11. Retention

Personal data is kept for as long as reasonably necessary for the purpose for which it was collected, to provide and secure the service, meet applicable obligations, and handle legal requests. Account, product-access, and personalization data may be retained while the account or related access remains active. A preorder registration may be retained until the related eligibility is used, expires, is withdrawn, or no longer needs to be administered.

12. Your Rights and Requests

You may contact juliamakhlinfiurst@gmail.com to request access to, correction of, or deletion of applicable personal data, or to withdraw the preorder communication consent. LapLapLa does not currently provide automated self-service account deletion. We may need to verify your identity and ask for enough information to locate the relevant account, preorder, personalization, or technical records.

Some aggregate information cannot be linked back to an individual and therefore cannot be individually accessed, corrected, or deleted. Requests are handled in accordance with applicable law.

13. Changes

This policy may be updated when the service or its data practices change. The current version is published on this page.