Legal
Privacy Policy
Status: pre-launch legal draft. It is blocked from production use until a qualified human/legal reviewer accepts the operator, contact, launch markets, retention, payment, analytics, and support behavior.
This page explains the privacy posture the website and apps are being built toward. It is not an accepted Privacy Policy, a customer contract, or a live privacy request channel.
Current Availability
VibeWall is not generally available. The public support, account-deletion, data-rights, and data-export pages are information routes only while legal review, verified request intake, and operational delivery remain pending. Visiting this page does not create a support case, export, deletion request, or account change.
Data Covered By This Draft
This draft covers account, device, app, wallpaper, purchase, support, and diagnostics information a future service may need. This list does not say that every category is collected in a production service.
- Account information can include sign-in identifiers, profile settings, account status, support contact details, and purchase access state.
- Device and app information can include platform, app version, display profile, wallpaper setup state, notification capability, and local settings needed to prepare device-ready outputs.
- Wallpaper information can include prompts, style choices, wallpaper set details, imported wallpaper metadata, generated wallpaper metadata, private library records, favorites, and device sync state.
- Purchase information can include product, checkout or app-store confirmation, purchase access status, refund or dispute state, and billing support context. VibeWall does not store full card numbers.
- Support and privacy information can include request category, account reference, platform, app version, verification state, and the details needed to handle deletion, export, billing, access, or security requests.
What VibeWall Avoids
VibeWall should not intentionally collect precise location, contacts, health information, biometric identifiers, government identifiers, raw payment cards, private files the user did not choose, raw service payloads, secrets, unbounded prompt histories, image bytes in account records, or unbounded logs.
Support forms should not receive passwords, recovery codes, raw payment data, private media files, service tokens, or unrelated personal information.
How A Future Service May Use Information
If the service opens, it may use information to create, import, save, apply, sync, and display wallpaper sets; authenticate users; register devices; prepare device-ready outputs; handle paid access; provide support; process data-rights requests; protect accounts; detect abuse; keep costly actions controlled; and meet legal, tax, security, accounting, fraud-prevention, and dispute obligations.
AI Generation And User Content
Before a generation service opens, the accepted policy must identify or classify the active service providers, processing locations, safeguards, and user choices. Users should not include sensitive personal information in prompts.
Wallpaper sets are private by default. Website waitlist and support forms do not collect raw prompts or private image files.
Website Analytics, Cookies, And Forms
Essential storage may keep navigation, consent state, accessibility choices, checkout safety, and support form state working. Optional analytics must respect consent and browser privacy opt-out signals. Analytics should avoid raw IP storage, private media content, prompt histories, support-message bodies, signed URLs, screenshots, session replay, payment payloads, secrets, or tokens.
Waitlist, contact, billing support, data rights, and marketing preferences forms must remain unavailable until their verification, delivery, consent, and response processes are accepted. A page must not present local validation as a submitted request.
Service Providers
VibeWall may use service providers for hosting, authentication, storage, generation, moderation, checkout, app-store purchase validation, analytics, email, notifications, customer support, fraud prevention, security, and operations. The final published policy must match the active services, countries of processing, and safeguards used at launch.
Retention And Deletion
VibeWall keeps personal information only as long as needed for service operation, legal obligations, security, fraud prevention, tax and accounting, support, dispute resolution, and policy enforcement.
An accepted deletion service must remove or disconnect eligible account-owned product data where it can safely do so. Some minimized commerce, receipt, tax, refund, chargeback, security, fraud-prevention, audit, abuse-prevention, legal, and dispute records may be retained where required or permitted. Final retention periods and criteria have not been accepted.
Data Rights And Choices
Depending on location and applicable law, a future service may need to provide access, correction, export, deletion, unpublishing, marketing controls, diagnostics controls, and regulator-contact options. The applicable rights, identity checks, response timing, and exceptions still require legal acceptance.
No privacy request channel is currently open. Before one opens, requests must use a verified in-app flow or verified privacy/support route before VibeWall discloses, changes, exports, or deletes account data.
Account Deletion
If accounts are available, users should be able to initiate deletion through an accepted in-app flow and a public web route where platform rules require it. The current web route is not a deletion-request channel. Before a deletion service opens, VibeWall must publish its verified fallback, retained-record exceptions, confirmation process, and purchase or subscription boundaries.
Data Export
The current web route does not accept data-export requests. A future verified route must limit eligible account, library, billing-summary, support, and settings data, and exclude secrets, internal risk notes, other users' data, raw service payloads, and data that cannot be disclosed.
Children
VibeWall is not intended for children under the age set by final legal review and launch-market requirements. VibeWall does not knowingly collect personal information from children under that age.
Security
VibeWall uses technical and organizational safeguards such as authentication, least-privilege access, encryption in transit, controlled purchase and generation state, audit logging, rate limits, abuse controls, and secret management. No system is perfectly secure.
Changes
VibeWall may update this policy. Material changes should be communicated in the app, website, or by email where appropriate.
Contact And Requests
Final support, privacy, and legal contact details are not accepted for publication. Do not treat a public route as a live support channel until it offers a verified request process and an explicit confirmation.