Privacy Policy

This policy explains how Aethera.TV collects, uses, and protects information across our video platform, dashboards, and community features. We keep this page updated to reflect new tools or regulations.

Last updated: August 28, 2026

Information we collect

  • Account details. When you sign up we store your username, email, encrypted password, date of birth, country, and any optional profile details you choose to share.
  • Engagement data. We log basic video analytics (impressions, watch time, retention milestones, device/traffic type) to power creator dashboards.
  • Audience analytics inputs. When you watch while signed in, we may use your country on file, date of birth, and optional gender setting to produce aggregated region, age, and gender audience reports for creators. We do not show those fields publicly on your profile.
  • Cookies and device signals. Essential cookies keep you signed in, secure payments, and prevent abuse. First-party campaign parameters, advertising click identifiers, and coarse device categories help us understand whether a visit led to account or VTT-world creation. Optional analytics cookies and third-party advertising measurement load only after consent.
  • Community content. Messages, uploads, and channel settings you submit are stored so we can deliver those to viewers and moderators.

Exchange buyer, license, and guardian records

Engineering draft candidate · No effective date · Not approved for production use

The proposed Exchange workflow would preserve the order or free claim, seller, beneficiary account, product and release, price and tax snapshot, access state, license and policy versions and hashes, AI disclosure snapshot, immediate-delivery consent, refund or dispute state, and necessary download or installation events. These records support delivery, prevent fraud, prove the terms presented, preserve acquired rights, and resolve support, refund, tax, security, and legal questions.

For an under-18 creator-membership beneficiary, the proposed guardian flow would also keep the adult guardian's protected contact reference, name and relationship, beneficiary account, exact transaction fingerprint, one-time token hash, expiry and approval timestamps, accepted versions, and hashed IP and user-agent evidence. One-time Exchange purchases for buyers under 18 remain unavailable. Aethera would not store payment-card details in the guardian record or put private guardian information into ordinary logs or payment-provider metadata.

Transaction, license, consent, guardian, refund, fraud, and rights records would follow the approved legal and transaction retention schedule and could remain during a chargeback, dispute, tax period, safety investigation, or legal hold. When deletion applies, Aethera would delete or de-identify data that is no longer required and preserve only the minimum pseudonymous evidence needed for those duties. Owner approval and qualified privacy review remain pending; this section does not authorize paid Exchange commerce.

Aethera Verify and creator-payment privacy

Test-mode disclosure version: 2026-07-12 · Not approved for live creator commerce

Aethera Verify uses Stripe Connect for creator identity, tax, payment, and payout setup. Sensitive legal identity documents and payout information are entered in a Stripe-provided secure flow and sent directly to Stripe. Aethera separately collects the protected seller-traceability fields required for a paid Exchange seller. Stripe acts as Aethera's connected-account and payment provider under Stripe's Privacy Policy.

What Aethera stores

  • The identifier that links your Aethera account to Stripe, test or live mode, country, business type, whether setup, payments, and payouts are ready, any remaining Stripe requests, and relevant dates.
  • Records showing which age, accuracy, Creator Agreement, Fee Schedule, privacy, and Commerce Policy disclosures you accepted, when you accepted them, and tamper-resistant evidence of that choice.
  • Limited references needed to connect creator products, prices, subscriptions, payments, fees, refunds, disputes, and account access without copying full Stripe records into Aethera.
  • For a paid Exchange seller, the protected traceability record can include legal and trading names, geographic address, telephone number, email address, trader or non-trader designation, applicable trade- register details, verification references and hashes, review decisions, audit history, retention state, and legal holds. Paid offers remain blocked until the exact required and public fields are approved for the seller's sales jurisdiction.
  • Account holds, the category of a payout failure, and relevant security or support history.

What Aethera does not store

Aethera does not store raw identity documents, selfies or biometric images, full Social Security or tax identification numbers, full dates of birth submitted to Stripe, full bank or routing numbers, payout-card credentials, beneficial-owner documents, or raw Stripe Account and webhook objects. Do not send those details to Aethera support.

Purposes, retention, and choices

We use the limited records above to control creator-payment access, prevent account and payment abuse, keep purchases and account access in sync, process refunds and disputes, meet recordkeeping obligations, provide support, and show which policies were accepted. Financial references, agreement evidence, security records, seller-traceability evidence, and legally required records may remain after onboarding or account closure for the period required by law, payment disputes, fraud prevention, and the approved retention schedule. The current seller-traceability candidate requires at least six months after the seller relationship ends, subject to longer lawful holds; no duration authorizes production until it is reviewed and approved. Other creator compliance status is deleted or de-identified when it is no longer needed.

Use Settings or contact Loading support email to request access, correction, export, deletion, or other privacy rights that apply to Aethera-held data. Requests about identity or bank information held by Stripe may also need to be made through Stripe. Raw identity documents and payout credentials stay private and Aethera Verify does not create a public identity badge or endorsement. A paid seller may still use a public creator name, but it cannot replace the legally required seller disclosure. Depending on the approved jurisdiction, that public disclosure can include the reviewed legal or trading name, geographic address, trade-register details, and a legally sufficient contact method. Exact telephone, email, and address-redaction rules must be approved before that jurisdiction is enabled.

How we use your information

We rely on your data to run the service safely and responsibly:

  • Authenticate logins, protect account activity, and personalize dashboards.
  • Measure video performance so creators understand retention, funnels, subscriber growth, and audience mix.
  • Apply age checks, account recovery protections, and region-aware safety or moderation rules.
  • Process payments (subscriptions) when enabled.
  • Enforce community guidelines, investigate abuse, and respond to DMCA notifications.
  • Improve reliability through aggregate analytics and optional browser performance telemetry after cookie consent. Separately, privacy-minimized server crash and security diagnostics are essential operational records: they exclude user, session, seller, order, request-payload, and provider identifiers.

Creator analytics and profile fields

Creators can see aggregate audience analytics for their own videos. That includes region buckets when we have an edge country signal or a signed-in viewer country on file, age buckets for signed-in viewers with a date of birth on file, and gender buckets only for signed-in viewers who explicitly set the optional gender field.

These reports are aggregated. We do not expose a viewer-by-viewer list of demographic profile fields to creators, and the optional gender field is not displayed publicly on your account page.

Cookies & similar technologies

We categorize cookies as essential (authentication, CSRF, fraud prevention) and optional (analytics, browser performance monitoring, and Meta, Reddit, and OpenAI advertising measurement). Essential cookies are required for the site to function; optional cookies and the Meta, Reddit, and OpenAI Pixels are only loaded after you click "Accept all" on the cookie banner. Privacy-minimized server crash and security diagnostics do not depend on optional browser cookies. If your browser sends a Global Privacy Control signal, Aethera treats it as a choice to use essential cookies only. You can revoke optional consent by clearing Aethera site data in your browser and refreshing.

Advertising measurement

After you accept optional cookies, Aethera may use the Meta Pixel, Reddit Pixel, OpenAI Ads Pixel, and their Conversions APIs to measure landing-page visits, account registrations, demo-assisted signups, and first VTT-world creation. This helps us understand campaign performance and avoid relying only on browser-side tracking.

For registration and first-world events, Aethera may send Meta a one-way hash of the account email and internal account identifier, along with the request IP address, browser user agent, Meta browser and click identifiers (_fbp, _fbc, and fbclid when present), the page URL, event time, and a deduplication identifier. Aethera does not send Meta your password, date of birth, country, gender setting, session token, campaign name, maps, tokens, chat, or other VTT content.

For completed registration events, Aethera may send Reddit a one-way hash of the canonicalized account email and internal account identifier, along with the request IP address, browser user agent, Reddit browser and click identifiers (_rdt_uuid and rdt_cid when present), the page URL, event time, and a deduplication identifier. Aethera does not send Reddit your password, date of birth, country, gender setting, session token, campaign name, maps, tokens, chat, or other VTT content.

OpenAI Ads receives consent-gated landing-page events through its browser Pixel. For completed registration events, Aethera may also send OpenAI Ads a one-way hash of the normalized account email and internal account identifier, along with the request IP address, browser user agent, OpenAI browser and click identifiers (__obref and oppref when present), the page URL, event time, and a deduplication identifier. Aethera does not send OpenAI Ads your password, date of birth, country, gender setting, session token, campaign name, maps, tokens, chat, or other VTT content.

How we share information

We do not sell personal data. We share limited information with service providers strictly to deliver the platform:

  • Stripe and other disclosed payment providers for platform billing, creator onboarding, and payments.
  • Telemetry vendors for identifier-free essential server crash and security diagnostics, and—only after consent—for optional browser crash and performance telemetry.
  • Meta for optional advertising measurement, only after consent and as described above.
  • Reddit for optional advertising measurement, only after consent and as described above.
  • OpenAI Ads for optional advertising measurement, only after consent and as described above.
  • Law enforcement or legal entities when required to comply with the law.

Service providers handle information under their own published terms and Aethera's applicable agreements with them.

Your choices & rights

  • Sign in to access or update your profile in Settings or the creator dashboard.
  • Use Settings to export account data or request account deletion. Contact Loading support email if the self-service control is unavailable.
  • Control cookies via the consent banner or your browser settings. Essential cookies can only be disabled by not using the service.
  • Enable Global Privacy Control in a supported browser to keep optional tracking disabled.
  • Opt out of marketing emails using the unsubscribe link in marketing messages.

Contact us

Questions about privacy or data usage? Email Loading support email or use the contact options on the Support page.