Privacy Policy
Effective November 14, 2026 · Last updated November 17, 2026
Work4WiFi LLC, doing business as FaLaLaLaLumin ("we," "us," or "our"), provides the service at falalalalumin.snodevelopment.com and its downloadable processing companion. This policy explains how we handle personal information. Work4WiFi LLC is responsible for its service-related processing. Identity, AI and payment providers may also act independently under their own policies.
1. Information we process
- Accounts and sign-in: name, email, account identifiers, verification status and settings. Email sign-in stores a salted one-way password hash, hashed session and email-link tokens, session dates and browser information. Authentication rate limits use hashed identifiers; hosting services may separately receive IP addresses. If you choose Google sign-in, we receive your verified email address and basic profile from Google, not your Google password. Resend delivers verification and recovery emails.
- Your content: recordings, lyrics, xLights layouts, model and group names, images, videos, prompts, creative directions, project settings and edits. Layouts and file names may reveal information about your property, household or computer.
- Results and operations: musical analysis, words and timing, singer assignments, generated songs and visuals, sequences, packages, previews, job status, usage, errors and diagnostics.
- Connections: encrypted Google, OpenAI, Anthropic or xAI API keys if you connect them, provider and connection identifiers, key suffix and connection dates. Your full key is not shown in connection-status responses.
- Billing and support: plan, subscription and transaction references, status, usage balances, support messages and information needed to investigate requests. Stripe handles payment credentials; our app does not collect or store full card numbers.
2. Information that stays on your device
A house photo selected as a preview background currently uses a browser-local file reference and is not uploaded by that control. Uploading the same image as artwork creates a separate uploaded copy. A video added through Link a local video is not uploaded or included in the package or browser preview: its path and placement are saved and exported so xLights can read your original file. Local paths can contain your computer user name or folder names.
Browser local storage keeps account-scoped recovery drafts containing project settings, layouts, lyrics and creative directions. Original recordings and layout files are also kept separately in account-scoped private browser storage to recover your selected files after a refresh. Supplied-media binaries, house photos and API keys are not embedded in recovery drafts. Temporary browser file URLs support playback. Files you download, local-companion files and your own backups remain under your control.
3. Purposes and legal bases
We use information to provide and secure accounts; verify email and restore access; save projects; analyze and sequence your display; process selected AI requests; reuse compatible saved media and timings; deliver previews and downloads; account for usage; manage subscriptions; support you; investigate errors and abuse; and comply with law. Where a legal basis is required, we rely on performing our agreement with you, legitimate interests in operating and protecting the service, legal obligations, or consent where required. You may stop optional AI requests and disconnect your provider key.
Your uploaded images and videos do not consume AI image or video generation credits. Normal show-processing usage may apply. Automatic selection can use file names, descriptions, lyrics and musical context. Avoid including unnecessary sensitive information.
4. AI content and providers
Eligible plans include AI capacity. Song generation uses Google, and cloud lyric transcription uses OpenAI. With your own keys, you can use Google, OpenAI or xAI (Grok) for supported visual features and Anthropic (Claude) for creative planning. Depending on the operation, we send relevant prompts, lyrics, a compressed recording, creative instructions, descriptions of compatible display targets and musical analysis. Requests use your selected provider connection or the plan-funded connection shown in the application. Running a locally hosted speech or music-analysis model does not, solely because of that model's publisher, submit the recording to that publisher.
Google's handling varies by product, tier and settings. Free-tier inputs and output may be used to improve its products and reviewed by humans. Some background requests use stored interactions so results can be recovered. Published Google policies describe retention of certain interactions and abuse-monitoring content for up to 55 days, with different or shorter periods for some tiers and settings. We do not promise zero retention or confidential handling under a free tier. Review Google's API terms, interaction-storage documentation and usage policies before submitting sensitive material.
Other providers apply their own API retention and abuse-monitoring policies, which can vary by endpoint, settings and contract. Review OpenAI data controls, Anthropic retention information and xAI’s privacy policy. We do not promise zero provider retention. Deleting your account or disconnecting a key does not revoke it at the provider or erase independent provider history. Use the provider's controls and contact us if you need help identifying a request we submitted. AI output is not guaranteed to be original, exclusive, accurate or legally protectable.
5. Hosting and other recipients
We use ChatGPT Sites and Cloudflare to host the service, process shows and store account records and files. Uploaded and generated files are held in private cloud storage with access controls. Resend handles verification and recovery email delivery. Google processes your sign-in when you choose that option. Google Fonts receives network/browser information when your browser requests our typography. Our email provider handles support correspondence.
Stripe handles checkout and transaction information under its Privacy Policy. Live checkout processes real payments. Account billing records may include Lifetime ownership, one-time hosted-processing purchases, expiration dates and refund/reversal references. These records do not include full payment-card details. Eligible live transactions use Stripe Managed Payments as merchant of record. Checkout identifies the seller and applicable terms before payment. Stripe handles transaction tax, payment support and legally required remedies under its applicable terms.
We may disclose information to providers acting for us, professional advisers, authorities when legally required, parties needed to investigate fraud or protect rights and safety, or a business successor subject to applicable safeguards and notice requirements. We do not sell personal information or share it for cross-context behavioral advertising. Uploads are not sent to advertising providers.
6. Cookies, advertising and analytics
Email sign-in uses a secure, HTTP-only session cookie with a current 14-day lifetime, subject to earlier sign-out, revocation, password reset or deletion. The optional sign-in provider may use its own cookies. Draft recovery uses browser storage. Selected media may also be copied into this browser’s private file storage so processing does not depend on continued access to the original local file. These copies use browser storage and may remain until removed or site data is cleared. Account deletion attempts to clear this account’s browser copies on the device making the request; other devices require their own cleanup. Clearing this site's browser data can sign you out and remove drafts.
We count first-party page views in our Cloudflare database without requiring analytics cookies. These totals use a calendar date, standard page name and broad referral source. Short-lived random identifiers prevent duplicate counts and expire after 24 hours of analytics activity; they are not persistent visitor identifiers. Known automated clients and our staff accounts and browsing requests signaling Do Not Track or Global Privacy Control are excluded. Counts are approximate and can miss blocked scripts.
With your optional analytics consent, we set first-party cookies for a random browser identifier (up to 90 days), a session identifier (30 minutes of tracked inactivity), and your consent preference (up to 180 days). We store hashed identifiers, session dates, landing and visited pages, broad referral sources, coarse device categories, selected UTM source/medium/campaign labels and product interactions. When signed in, observed sessions and events can be linked to your account to understand registration and show-creation journeys. This is not fingerprinting and does not identify the same person across devices. We do not collect recordings, layouts, media contents, API keys, full referring URLs or IP addresses in analytics. You can decline or change consent using Analytics preferences in the footer. Withdrawing consent attempts to remove that browser’s optional analytics history and clears its identifiers; if privacy signals or blockers prevent the request, historical records follow the retention rules below. Account deletion also removes its account-linked event/session records and attempts to disable optional analytics on that device.
Raw product events and inactive session/hashed-browser records are cleaned after 90 days when analytics activity runs. Aggregate page counts retain up to 90 UTC calendar days. We also use account, processing and billing records to operate the service and produce reports, separately from optional browser analytics. Payment information used for account reports is retained for up to 180 days and updated periodically. Transaction identifiers and anonymized financial records may remain after an account link is removed. Storage-usage reports use file information rather than reading your file contents. Advertising scripts and third-party behavioral-analytics trackers remain disabled. Hosting/security logs have their separate retention rules.
When you submit feedback or rate a show, we store your comments, optional rating, category, subject, submission dates and account link for support review. Show-related feedback can include its job reference, processing state, workflow, application/engine version, plan and an error code. These references do not automatically attach your song, layout, videos, keys or other private files. Optional screenshots/text files require your explicit attachment confirmation, are kept in private cloud storage and are limited to two files and 10 MB per submission, with a 100 MB saved-attachment safeguard per account. Feedback, ratings, replies and attachment metadata are included in account data exports; operators’ internal notes are not. Feedback and attachments have no fixed automatic expiration; they are removed from active storage when the account is deleted or a support team member deletes the report. The backup limitations below apply.
If you allow follow-up, a support team member may respond to your account email using our email delivery provider, Resend, or an email draft. The email provider receives the address and reply contents needed to deliver the response. Acceptance by that provider does not guarantee delivery. Internal support notes are not sent as part of a reply. Replies and their submission status remain with the report until deletion.
7. Retention and deletion
Saved work is retained so you can return to projects and reuse content. There is currently no fixed automatic expiry in the application for saved account content, completed shows, failed-job history or completed uploads abandoned before processing. These are our active-storage rules, rather than a promise that all historical copies disappear immediately:
- Projects and show files: account-linked settings, originals, lyrics, supplied media, generated assets, sequences and previews remain until removed through the relevant controls or account deletion, or another lawful reason for removal. Project deletion removes its dedicated originals. Removing a show from history can hide that version while preserving files reused by other work. Account deletion uses those account-linked records to remove their files from active storage. This covers linked project originals, job inputs, transcripts, generated media, sequences and previews. It does not guarantee removal of every file or historical copy.
- Failed and abandoned work: some uploaded inputs and partial outputs remain with processing records until account deletion. Supported failure and cancellation paths delete known supplied-media inputs. Completed uploads that are no longer linked to account records can remain after account deletion; such files may require manual review and removal. Completed uploads currently have no fixed automatic expiry. Incomplete uploads are canceled after seven days; this does not delete completed files. Copies held in earlier hosting storage may follow different retention rules. Contact us for investigation and cleanup of residual content.
- Processing computers: managed job folders are removed when processing finishes. Startup/periodic worker cleanup checks for interrupted job folders older than 24 hours and recording caches with files older than 30 days. These checks require worker activity and do not guarantee erasure at an exact hour. Container shutdown can also discard temporary files. The local companion's files and caches remain on your computer until you remove them.
- Keys: saved provider credentials remain encrypted while connected and are removed from active connection storage when disconnected or account deletion completes. Provider-side copies and requests have separate lifecycles.
- Authentication and security: email verification/reset links expire after 30 minutes; sessions after 14 days. Expired database records can remain until replacement, session cleanup or account deletion. Expiry is not the same as erasure. Hosting logs follow provider retention; we cannot provide a fixed retention period for those logs. Some queue history, hashed security identifiers, incident records and a disabled-account identifier can remain for reliability, abuse prevention or legal purposes without a fixed automatic expiry.
- Financial records: account deletion removes app account-linked subscription and usage records. Stripe's independent transaction, tax, dispute and legal records are not erased by that action. Limited payment-event identifiers and payment-review or compliance records may remain as needed for legal or legitimate business purposes. Retention depends on the record and applicable obligations, not a single universal period.
- Device copies: the account-deletion flow attempts to clear the account's recovery draft on the device used for deletion. It cannot erase other devices, local companion caches, downloaded packages or your own backups. Clear site storage on each other device.
- Backups: deleting data from active storage does not establish that historical recovery copies have been erased. We retain encrypted backup copies and copies from earlier hosting for recovery. These copies currently have no fixed automatic expiration and are not individually erased when an account is deleted from active storage. Backups are made manually; recurring backups are not guaranteed. Recovery history, earlier hosting copies and hosting logs may have different retention periods. We do not promise a specific expiry date for historical copies. Contact us for review and cleanup of retained copies; a recovery must reapply later deletion decisions before reopening access.
Backup coverage is limited, and recovery of lost, deleted or corrupted content is not guaranteed. We do not promise recovery within a particular time. You should retain your original recordings, layouts and media, and download and keep copies of completed sequences and show packages. Nothing in this statement limits rights or obligations that cannot be excluded under applicable law.
Cancel subscription renewal before deleting the account. Running work must stop; the app may require you to confirm deletion again. Starting a request alone does not complete it. A disabled account record retains a pseudonymous identifier to prevent automatic re-creation through trusted sign-in. Older files no longer linked to account records, residual processing files and third-party records may need separate investigation. Contact us for a deletion review if you believe content remains. We may preserve information required by law, a legal hold, fraud prevention or a legitimate dispute, while limiting its use accordingly.
8. Your choices and rights
Account settings lets you review usage, revoke email sessions, disconnect a provider key, export account metadata and initiate deletion. The JSON export includes account/project, job, usage and connection metadata; binary audio, layouts, artwork and packages are not embedded, and your full key is not disclosed. Download files separately before deleting the account.
Depending on your location, you may have rights to access, correct, delete, restrict or object to processing, obtain portable data, withdraw consent, or appeal a privacy decision. Email support@snodevelopment.com with your request and account email. We verify identity where necessary and request only reasonably needed information. We respond within applicable legal periods and explain lawful refusals or extensions. You may complain to your local data-protection authority. We do not discriminate for exercising applicable privacy rights, though some features necessarily require processing your content.
9. International handling and security
We are based in Tennessee, United States. Hosting, identity, email, payment and AI providers may process data in the United States and other countries where they operate. We do not guarantee country-specific residency. Applicable transfer safeguards apply where required. We use access controls, secure transport, salted password hashing and encryption for stored provider keys. No system guarantees absolute security. Protect your account, device and keys and contact us promptly about suspected unauthorized access.
10. Adults and changes
Minors may use the service only with the consent and supervision of a parent or legal guardian, subject to applicable law. We do not knowingly collect personal information from a child where a specific form of parental consent is legally required unless that consent has been obtained. If you believe a child has provided information without the required consent, contact us so we can investigate and take appropriate action. We may update this policy as the service changes, revise the effective date and provide additional notice of material changes where required.
Contact us
Work4WiFi LLC, doing business as FaLaLaLaLumin5101 Compass Way
Christiana, TN 37037, United States
support@snodevelopment.com