Legal Documentation
How Third Eye Cyborg, LLC collects, uses, stores, and shares information across the Ascended Social platform — written in plain language so you can make informed choices.
This Privacy Policy explains how Third Eye Cyborg, LLC ("we", "us", "Ascended Social") collects, uses, stores, and shares information when you use the Ascended Social platform — including the website, web app, mobile app, in-game experiences, and related APIs.
Ascended Social is a spiritual social network. Because of that, the content people share with us is often more sensitive than what is shared on a typical social platform. We disclose those practices in plain language below so you can make informed choices before submitting content.
A copy may also be published via our compliance partner TermsHub at portal.termshub.io/ascended.social/privacy_policy. Until that copy includes the moderation and private-message disclosures below, this page is the current privacy notice.
Account & identity data. Email address, display name, avatar, authentication identifiers (managed via Clerk), and basic profile preferences.
Spiritual and personal content. Posts, comments, manifestations, intentions, ritual notes, tarot and I-Ching readings, divination history, oracle consultations, in-game choices in Sabs and The Cosmos, and the language you use to describe your spiritual life. This content can reveal religious or philosophical beliefs, so we treat it as sensitive and apply heightened obligations to it under GDPR Article 9 and equivalent laws.
Mood and intention tags. Mood is an optional tag that you pick from a fixed list to describe the tone of a post. It describes the post. It is not a health record or a medical or psychological assessment. Mood and intention tags are shown with the post to anyone who can see that post (public posts are visible to signed-in members). People can use them to search, and community moderators and our staff may see them when reviewing content. We don't use AI to choose, suggest or change your mood tag. We don't send mood or intention tags to our analytics provider (PostHog), and we don't share them through federation. If you use AI-assisted mode, the content of your posts may be processed by our AI moderation providers (such as OpenAI) to check it against our rules. In AI-assisted mode, if you add an intention to a public post, AI may also check whether it fits the post using your intention and the post's text (or a video's transcript). AI never writes or changes it. Those requests don't include your user ID. In Human Community mode, mood and intention tags aren't sent to AI providers. Community reviewers or staff review them instead. Tags are kept until you delete the post or your account.
Health information. We don't ask for or use information about your physical or mental health. If you choose to share health information in your own posts, it is treated as the content you chose to publish: it is visible to the people who can see that post, and it is subject to moderation like any other content. We don't use it to infer anything about your health.
Cosmos tool inputs and results. If you use an authenticated Cosmos tool, we may process the birth date, birth time, name, question, dream text, compatibility details, or place name needed by that tool. Place names are resolved through Roxy Location to obtain latitude, longitude, and an IANA timezone; users are not asked to provide raw coordinates. Cosmos history is opt-in: a result is saved only when you choose "Save result."
Ask Cosmos conversations and voice. Private chat messages are stored with the conversation so you can return to them, and a matched tool result is saved to Cosmos history only when you choose "Save result." Voice audio is sent for transcription and is not retained as a recording after the request; the transcript and response may become part of the conversation. Text sent for Speak playback is processed to generate private, uncached audio and is not used to name a conversation.
Before using Cosmos Tools, read the public preview and user guide. They explain the fourteen domains, server-side Roxy processing, opt-in history, deletion controls, and the limits of interpretive results.
Communications, chats, and messaging. Direct messages, group chats, and private network chat (text, images, audio, and video), including the report snapshot when someone in the conversation reports a message.
Social graph & engagement. Follows, sparks (likes), bookmarks, networks, whispers, and call/live session participation. Network project-board timesheets store who clocked in or out on a card, start and end times, optional notes, and which manager created or edited an entry.
Media uploads. Images, audio, and video files you upload. Public uploads may include moderation metadata from automated checks. Private Whisper and private-chat attachments are not sent to AI vendors.
Scheduled posts. If you schedule a post (a scheduled Flow), we store what will be published until it publishes: the text, tags, visibility, any mood or intention, the images you attached, the time and time zone you picked, and its status. We also store the country and region your request came from, so we can apply our geographic restrictions when it publishes. Time zone is used only to schedule and display. A scheduled post isn't shown to other users before it publishes. You can edit, cancel or delete it until it starts publishing. Delete removes a scheduled Flow and its media right away. Cancelled or failed scheduled Flows are deleted after 7 days. Once a scheduled Flow publishes, we delete the scheduled copy's content; the published post stays until you delete it. Backup copies are removed within our backup retention period.
Device & usage data. IP address, device and browser characteristics, referring URLs, country (via Cloudflare CF-IPCountry headers for jurisdiction routing), and basic telemetry about how you interact with the product.
Billing data. Subscription state, plan tier, and receipts processed through Polar and RevenueCat. We do not receive or store full payment-card numbers.
Compliance data. Privacy requests, consent choices, do-not-sell/share elections, jurisdiction signals, and audit-trail evidence required to demonstrate compliance.
We use the data above to: operate the platform; authenticate you; moderate content; recommend posts, books, and people; render avatars and game state; send transactional and (where you have opted in) marketing emails; bill subscriptions; investigate abuse; and meet our legal obligations.
In product Settings, users can choose an AI execution mode (auto, prefer_local, prefer_cloud, or local_only) to control how AI-assisted features are routed. In local_only mode, some generation features may be unavailable when local capability is not yet supported; the app surfaces clear guidance so users can switch modes if needed. On compatible Apple devices, local routing can use on-device Foundation Models where available. Public-content moderation remains active in all modes (including local_only). Private Whispers and private chats are never sent to AI; see section 3a.
Content moderation. Public content (posts, comments, public Whispers, public network chat, public Lives and calls) is moderated. If Use AI Features is on, it's checked by OpenAI's moderation API and Cloudflare, and flagged items may be analysed by an OpenAI model to help our moderators. If Use AI Features is off, or you choose Local Only, people review it instead. For now, images you post publicly and checks during public video calls and Lives may still use automated tools. Public Lives are recorded through Cloudflare Stream. Child-safety reports are reviewed by our staff and are never sent to AI. Scheduled posts are checked when they publish, not when you schedule them, using the AI or Human Community setting you have at that time. The optional AI intention check runs only while you're writing in the app, not when a scheduled post publishes.
You can upload your own sigil image if you own it or have the right to use it. Uploaded sigils are held for review before anyone else can see them. In Human Community mode, a person reviews them and they're never sent to AI providers. In AI-assisted mode, they're checked by the same automated image tools we use for post images (OpenAI's moderation API and Cloudflare) before review. Copyright complaints about uploaded sigils use our DMCA Policy and in-app copyright reporting.
Private messages. We don't review or run AI checks on the content of private Whispers or private network chats (text, images, audio or video), in either mode. An Ascended staff moderator sees a private message only if someone in the conversation reports it. The report includes the messages they select and up to 10 messages before and after for context. We use limited non-content signals, such as message volume, blocks and reports, to fight spam and abuse. If we find child sexual abuse material, we're legally required to report it to the National Center for Missing & Exploited Children (NCMEC) and preserve it. We may also disclose content when the law requires it or to protect someone from imminent harm.
Federation is planned, but it has no launch date and isn't available today, and plans can change. When federation launches, public content delivered to Ascended Social and private communication with Ascended Social-hosted users would remain subject to our rules and moderation; private exchanges solely among users of independent self-hosted services that never pass through Ascended Social may be outside our moderation, and those operators and users would be responsible for their own rules and legal compliance. Ascended Social does not currently send your content or account data to other servers through federation, and other servers cannot follow or receive your content through Ascended Social. Before any federation feature launches, we will update this Privacy Policy to explain what data would be shared, with whom, how deletion would work, and what choices you have, and we will notify you before the change takes effect. Private messages involving Ascended Social-hosted users aren't proactively reviewed or checked by AI; they're reviewed by Ascended staff only when someone in the conversation reports them, or where the law requires.
To power the Ascended Social recommendation engine and search, we generate vector embeddings — numerical representations — of posts and other public content. These embeddings capture the meaning of your content so we can suggest spiritually adjacent posts, books, and people.
When you delete a post, the corresponding embedding and indexed copy are removed from the recommendation and search stores in the same operation. When you delete your account, all embeddings tied to your content are removed as part of your account purge. See Delete your account for in-app steps, request-based deletion, and what we retain.
You can opt out of personalized recommendations at any time from the in-app Privacy Center; non-personalized fallback content is served instead.
We share the minimum data required with the following processors, each bound by a data-processing agreement:
Apps you connect. If you create an API key and give it to an app, script or AI assistant (including through our MCP server), that app can read or change your scheduled posts as the key's permissions allow, and it can publish posts as you. It handles that data under its own terms and privacy policy, not ours. You can revoke a key at any time in Settings → Developer.
We do not sell your personal information. We honor "Do Not Sell or Share My Personal Information" requests submitted through the Privacy Center.
We keep your data only as long as we need it. Default retention windows are:
Records subject to an active legal hold or open privacy request are exempt from automated deletion until that hold is lifted.
Depending on where you live (GDPR, UK GDPR, CCPA/CPRA, Colorado, Virginia, Connecticut, Utah, and similar regimes), you have the right to:
You can exercise any of these rights from the in-app Privacy Center or by emailing [email protected]. We respond within statutory deadlines (45 days for CCPA, 30 days for GDPR with a possible 60-day extension) and provide a public tracking ID for every request.
Third Eye Cyborg, LLC is established in the United States and is not established in the European Union. We have appointed a representative in the Union pursuant to Article 27 of the GDPR. We have also appointed representatives for the United Kingdom (Article 27 UK GDPR) and Switzerland (Article 14 FADP). EU, EEA, UK and Swiss users, supervisory authorities, and data subjects may contact the representative on any matter relating to the processing of personal data:
European Union — Article 27 GDPR
United Kingdom — Article 27 UK GDPR
Switzerland — Article 14 FADP
You may contact our EU representative in addition to, or instead of, contacting us directly at [email protected]. The same details appear on our Impressum and Data Processing Agreement. For EU Digital Services Act contacts, see our DSA Notices.
Ascended Social is intended for adults and users represent that they are at least 18 years old. The Service is not directed to children or anyone under 18, and age is currently collected as a representation rather than independently verified. If you believe a person under 18 has provided data or created an account, contact us and we will take appropriate action, including deletion where required. For child-safety reporting, see our Child Safety & CSAE Standards.
Our infrastructure is hosted in the United States. If you access the service from outside the United States, your data is transferred to and processed in the United States under appropriate safeguards (Standard Contractual Clauses where applicable).
We protect your data with encryption in transit, encryption at rest for databases and object storage, role-based access controls, automated abuse detection, and a documented incident response plan. No system is perfectly secure; if a breach affects you, we will notify you and the relevant authority as required by law.
Two-factor authentication (2FA/MFA): We offer optional TOTP-based two-factor authentication for all accounts. When enabled, you must enter a time-based one-time code from an authenticator app (such as Google Authenticator, Authy, or 1Password) in addition to your password at each login. You are solely responsible for keeping your authenticator device and backup codes safe. We strongly encourage all users to enable MFA in Settings → Security.
We will update this Privacy Policy when our practices change. The effective date at the top of the page shows the current version. Material changes are surfaced in the in-app Privacy Center and, for logged-in users, by email or in-product notice before they take effect.
Privacy questions: [email protected]. EU, EEA, UK and Swiss users may also contact our appointed representative, Prighter.