Legal
Terms of Service, Privacy Policy & Cookie Policy
Terms of Service
Acceptance of Terms
By accessing or using Flux, you agree to be bound by these Terms of Service. If you do not agree to these terms, you must not use the platform.
User Conduct
- You agree to use Flux only for lawful purposes and in accordance with these terms.
- You must not engage in harassment, hate speech, spam, or any form of abusive behavior toward other users.
- You must not attempt to gain unauthorized access to other users' accounts, the platform's backend systems, or any restricted areas of the service.
- You must not distribute malware, phishing links, or any content that could harm other users or the platform's infrastructure.
- You must not scrape, crawl, or use automated means to extract data from Flux without explicit written permission.
Admin Control & Enforcement
Flux administrators reserve the right to deploy enforcement flags — including content restrictions, account suspensions, and permanent bans — against any account that violates these terms, compromises system integrity, or exploits WebSocket interfaces or other platform APIs. Enforcement actions are at the sole discretion of the platform administration and may be appealed through the Account Enforcement Appeals channel.
Content Ownership
You retain ownership of the content you create and share on Flux. By posting content, you grant Flux a non-exclusive, royalty-free license to display and distribute your content within the platform.
Service Availability
Flux is provided on an "as is" basis. We do not guarantee uninterrupted access and reserve the right to modify, suspend, or discontinue any part of the service at any time.
Account Termination
We reserve the right to terminate or suspend accounts that violate these terms. Upon termination, your right to use the platform ceases immediately. You may request account deletion at any time through your account settings.
Last updated: June 2026
Privacy Policy
Data Collection & Storage
Flux collects and stores only the information necessary to provide its core social communication services. User account data — including usernames, email addresses, and cryptographic password hashes — are stored in a secure relational database. All passwords are hashed using industry-standard one-way encryption; Flux never stores plaintext passwords.
Media Hosting
User-uploaded media — including profile avatars and banner images — are stored inside public Supabase storage buckets (uploads/avatars and uploads/banners). These files are accessible via public URLs to enable fast content delivery across the platform. Users should be aware that uploaded media is publicly accessible by design.
Real-Time Communication
Messages sent through Flux's real-time chat system are stored in our database to enable message history and cross-device synchronization. Message content is transmitted over encrypted WebSocket connections (WSS) and stored at rest in our database.
Account Deletion
When a user initiates account deletion, a cascading delete is triggered across all associated database tables. This includes the user's profile data, messages, media references, social connections, and notification records. This action is irreversible.
Third-Party Services
Flux uses Supabase as its backend infrastructure provider (database, authentication, and storage). User data processed through Supabase is handled in accordance with their privacy policy. Flux does not share user data with any additional third-party analytics, advertising, or tracking services.
Data Security
We implement appropriate technical and organizational measures to protect your personal data against unauthorized access, alteration, disclosure, or destruction. All data transmission between your browser and our servers is encrypted using TLS/SSL.
Last updated: June 2026
Cookies & Session Policy
Our Approach to Tracking
Flux does not use tracking cookies, advertisement modules, third-party analytics scripts, or any behavioral tracking technologies. Your activity on Flux is not monitored for advertising purposes.
Essential Session Storage
Flux relies strictly on essential browser storage to maintain your session state:
flux_token— A session token stored in your browser'slocalStorage. This token preserves your authenticated state across page reloads and browser sessions. It is a stateless JWT (JSON Web Token) used exclusively for identity verification with the Flux API.
How Sessions Work
When you log in to Flux, the server issues a signed JWT that is stored locally in your browser as the flux_token. Every subsequent API request includes this token in the Authorization header for stateless verification. The token has a configurable expiration period. When the token expires or you log out, the flux_token is removed from local storage and the session ends.
No Third-Party Cookies
Flux does not set any third-party cookies. The only data stored locally in your browser is the flux_token session key. No other cookies, local storage keys, or tracking mechanisms are employed.
Managing Your Session
You can end your session at any time by logging out of Flux, which removes the flux_token from your browser. You may also clear your browser's local storage manually through your browser settings.
Last updated: June 2026
