Privacy Policy
Last updated: September 6, 2026
LiveDreams is available at livedreams.ai and livedreams.net (together, the “Service”), operated by the same company under the same account, terms and privacy practices. Privacy is the product. This policy explains what we collect, why, and — just as importantly — what we never do. The short version: we collect the minimum needed to run the Service and prevent abuse, we never sell your data, we never sell referred users’ emails to partners, and we never use your prompts, uploads, or generations to train AI models. You have one account and one data set on both domains. Reference uploads are stored privately only while needed to run a generation (prompt-builder attachments, for the conversation) and are treated identically on livedreams.ai and livedreams.net. Cookies are set per domain: a visitor may see the age gate and cookie banner once on each address.
1. What we collect
- Account data. If you register: your email address and authentication credentials (passwords are stored only as secure hashes), or basic profile fields if you sign in with Google. Guest accounts are anonymous and hold no email until you link one.
- Content you create. Prompts and generation settings, media you upload (reference photos, first frames, videos), and the outputs generated for you (your library). Uploads and library items belong to the same account on both livedreams.ai and livedreams.net.
- Payment data. The pack you bought, its price, and the cryptocurrency transaction reference. We never see or store card numbers or bank details — we do not process card payments at all.
- Anti-abuse signals. IP address and device/browser fingerprint signals, collected at signup and generation time and used solely to prevent bonus farming, multi-accounting, and other abuse of the Service.
- Operational logs. Pages visited, actions taken, errors, and performance data needed to keep the Service running and secure.
- Product analytics. When Google Analytics 4 is enabled, we collect aggregated page views and events such as sign-up, login, generation start/result, choosing a credit pack, clicking the deposit / pay button, and completed purchases — never prompts, uploads, emails, or payment addresses. IP addresses sent to Google are anonymized. We enable Google signals so Google can show aggregated country, age, and gender for visitors and buyers when it has that data. We do not run Google Ads campaigns, remarketing lists, or sell audiences.
- Invite and partner tracking. If you arrive via an Invite (/r/) or Partners (/p/) link we store the last click (code, type, timestamp, optional click id and sub1–sub5) for 30 days, in a cookie and in local storage, so we can lock a new account at signup. After signup that lock lives on the account, not in the cookie.
- Partner program (if you apply). Traffic description, channel URLs, Telegram handle, application status, payout wallet (USDT TRC20 and/or USDC Polygon), commission and payout ledger (including on-chain transaction hashes), and any postback URL you set. Partners see aggregated stats and their own referred user ids hashed or truncated in the dashboard — not the referee's email, not prompts, not generations.
2. How we use it
- to provide the Service: authenticate you, run your generations, keep your library;
- to account for credits: purchases, spending, bonuses, and automatic refunds;
- to prevent fraud, bonus farming, and other abuse;
- to provide support and respond to requests;
- to run Invite friends and the partner program: attribute a signup to a last click, pay credit rewards, calculate commissions, send USDT/USDC, fire an S2S postback you asked for;
- to comply with law and enforce our Terms and Content Policy;
- to improve the Service using aggregated, non-identifying statistics, including which packs people click and who actually pays;
3. Zero-retention generation pipeline
Prompts and uploads are transmitted over encrypted connections to the AI inference infrastructure that produces your generation, are processed transiently, and are not retained there. On our side:
- uploaded reference files sit in private storage, are treated identically on livedreams.ai and livedreams.net, and are shared with the generation pipeline through short-lived signed links. We delete those files as soon as the generation that used them finishes (success or failure). Prompt-builder attachments stay for the conversation and are deleted within 24 hours or when you delete the chat;
- generated results stay in your library, visible only to you, until you delete them;
- deleting a generation removes it from active storage; residual copies in encrypted backups rotate out on a fixed schedule.
4. What we never do
- we never sell, rent, or trade your personal data;
- we never use your prompts, uploads, or generations to train AI models;
- we never run advertising trackers, remarketing pixels, or third-party ad cookies. We may use Google Analytics 4 for first-party product analytics as described in sections 1 and 9;
- we never share your content with other users — your library is private by default;
- we never sell, rent, or give partners a referred user's email, prompts, uploads, or generations. A partner sees that a lock exists and that a pack collected — not who the person is beyond an opaque id.
5. Who processes data for us
A small number of infrastructure providers process data on our behalf to run the Service: hosting and database, file storage, AI inference, crypto payment processing, Telegram (for Stars, where used), blockchain networks (Tron / Polygon) when we send a partner payout, and — when configured — Google Analytics 4 (Google Ireland Limited / Google LLC) for product analytics. A payout puts the destination wallet and amount on a public ledger; that is how crypto works, not a sale of your data. Each processor is bound by confidentiality obligations and by the privacy commitments described in this policy, and each receives only the data needed for its function. We do not name other providers publicly as a matter of operational security; details are available on request.
6. Retention and deletion
Account data is kept while your account is active. Uploaded reference files are deleted as soon as the generation that used them finishes. Prompt-builder attachments stay for the conversation and are deleted within 24 hours or when you delete the chat. Generated results stay in your library until you delete them, and are removed from active systems immediately when you do. You can delete the whole account and its media yourself from Account in the dashboard (type DELETE to confirm). Credit and transaction ledger entries are retained as required for accounting and legal purposes even after account deletion, but are dissociated from your identity where the law allows. To prevent abuse of the welcome-credit grant, we keep a one-way hash of the email and device signals used at signup — not the raw email, not your prompts or media. Signing up again with the same email does not grant new free credits. Partner application, commission, and payout records are kept as required for accounting even if you close the partner account; wallet addresses are used only to pay you.
7. Security
We use encryption in transit, hashed credentials, private-by-default storage, and least-privilege access controls. No system is perfectly secure; if a breach ever affects your data, we will notify you and the authorities as required by law.
8. Your rights
You may request a copy of your data, correct it, export it, or delete your account and its associated data at any time from Account in the dashboard, or by emailing [email protected]. We answer verified requests within 30 days. Depending on your jurisdiction you may have additional statutory rights (for example under GDPR or CCPA); we honor them regardless of where you live.
9. Cookies and local storage
We use what the Service needs to function: session/authentication tokens, a device cookie used only to prevent bonus farming, and interface preferences stored in your browser. The 18+ age gate is stored in local storage and is not cookie consent. The same cookies, used for the same purposes, are set separately on livedreams.ai and on livedreams.net. Consent is asked on each domain.
Invite and Partners last-click cookies (ld_invite, ld_partner, plus matching local storage) last 30 days from the last click. A short-lived cookie may carry the code across a Google/X sign-in hop (minutes, not days). These are not advertising cookies. They do not follow a user after the account exists: a later /p/ click does not rewrite a lock. You can clear them in the browser; if you already signed up, the account lock (if any) stays on the profile.
After you confirm you are 18+, we show a cookie choice. If you allow analytics, Google Analytics 4 sets first-party cookies used for measurement and Google signals (aggregated demographics such as country, age, and gender — not individual profiles we look up). We send Google Consent Mode v2 signals: analytics and the Google-signals flags are granted only if you allow them (outside the EEA they default on). You can reject analytics cookies; the Service still works. We do not run Google Ads campaigns or remarketing on livedreams.ai or livedreams.net.
10. Invite friends and Partners
If you use someone's Invite or Partner link, we attribute your new account to the last click in the 30 days before you register. After that the attribution sits on the account so we can grant Invite credits or pay the partner. We do not use that lock to sell your identity. Partners receive commissions in crypto to a wallet they give us; we do not share your email with them.
If you apply as a partner, the offer at /partners/terms explains payouts. This policy covers the personal data side: wallet, Telegram, traffic URLs, click ids, postbacks, and the ledger. You can ask us to close the partner account; we still keep payout records we need for accounting.
11. Children
The Service is strictly 18+. We do not knowingly collect data from anyone under 18. If we learn that a minor has used the Service, we delete the account and its data immediately.
12. International use
The Service is operated globally and your data may be processed in countries other than your own. Wherever it is processed, it receives the protections described in this policy.
13. Changes
We may update this policy from time to time; the current version with its revision date is always on this page. Material changes will be announced on the Service.
Privacy questions and requests: [email protected].
