Privacy Policy

Astral Edge is responsible for the personal data described here. Contact: [email protected].

• Contract: account identification (email, Telegram identity, nickname) is needed to create/use accounts and login; payment details fulfil paid subscriptions. This includes supplied profile/preferences/community content, subscription/payment records and notifications you enable; browser push subscriptions are optional. On-chain transaction details and wallet addresses are public blockchain data.
• Contract: account-linked content activity (threads viewed, view counts, last-view time, reactions, comments) provides community features independently of Google consent.
• Legitimate interests: IP address, browser user agent and abusive-use signals secure the service and prevent abuse/fraud; account-linked content-activity statistics, account usage dates and first-party campaign source help understand service use.
• Consent: optional Google Analytics and Google Ads campaign measurement and ad personalization; we store your consent choice.

Hosting/CDN providers process service/request data; email delivery providers process email addresses/message contents; Telegram handles account/login/notification/payment interactions; browser push providers deliver enabled notifications. Google receives analytics/advertising measurement data only with consent. Payment transactions/wallet addresses are publicly visible on-chain. Community members see published nicknames, avatars, posts, comments and reactions.

Our providers may process personal data outside your country, including outside the European Economic Area; contact [email protected] for information about international processing and safeguards.

Account details and account-linked content activity (threads viewed, view counts, last-view time, reactions, comments): while the account exists; closure does not erase everything.

Login audits older than 12 months: weekly cleanup. Some security evidence: 180-day cleanup target, subject to scheduling/partition delays; suspicious-request/probe evidence ages from last activity; some inactive security activity counters: 30-day cleanup threshold.

Acknowledged notification delivery records: daily cleanup after 30 days, not all notifications. Payment-service log files: 60-day rotation policy, not payment-record expiry. Remembered-browser records: daily cleanup 30 days from being remembered. Login-code records: daily cleanup once expiry is more than one day old; code validity is not record deletion.

Other retention depends on account/service needs, security/abuse prevention, payment/legal obligations and dispute handling. Backups/provider copies may have separate retention. Cleanup schedules can delay removal.

Request rate/volume, automated site scanning, repeated failed sign-in code attempts and protected-area attempts can trigger automatic account/network restriction or blocking where protection is enabled, including ending sessions without prior human review. Restrictions can be temporary or permanent. To contest a restriction or request review, email [email protected].

• Subject to applicable law: request access, correction, deletion, objection, restriction or portability at [email protected]; withdraw consent at any time without affecting prior lawful processing; complain to a data protection authority. Consent changes: Cookie settings below.

Essential sign-in/session and remembered-browser cookies are necessary for authentication and do not require consent. Browser storage also holds privacy choices/service preferences.

Campaign attribution uses the ae_src cookie and local storage independently of Google consent, even after Reject: 30-day attribution window; cookie expiry; local-storage expiry checked when read. Attribution can attach to accounts at signup.

Google Analytics 4 measures public pages only: home, pricing, privacy; only after you press Accept, for visitors and for signed-in members on those pages. No Google Analytics measurement before choosing, after Reject, or elsewhere.

_ga and _ga_<id> hold a random identifier to tell new visitors from returning ones and count daily users. Measurement: page, reduced referrer, campaign/click information and login/plan/Telegram clicks. The site sends no account identifier to Google: no user ID, nickname, email or Telegram ID.

Google Ads can import these key events (login started, plan selected, Telegram joined) for campaign measurement; Accept also allows ad measurement and personalization.

Change or withdraw your choice at any time through the footer Cookie settings button when Google measurement is enabled; withdrawal stops Google measurement and removes Google Analytics cookies. Google's privacy policy.

Account usage dates (UTC): no IP addresses or pages; dates older than 400 days removed by daily cleanup, or if the account row is deleted.

The effective date is shown beside the notice heading.