Your creations belong to you. Zero cross-user visibility.
Higgsfield Open is engineered with a strict local-first, zero-central-database architecture. Unlike conventional platforms that broadcast creations to public feeds, your video generations, prompt history, creator face locks, and API credentials never leave your browser session.
1. Zero Cross-User Visibility
Can other visitors see what you create? No. There is no shared gallery, explore page, or public community stream. User A's browser only sees User A's outputs. User B's browser only sees User B's outputs. No user can ever query, browse, or access another user's video runs.
2. No Central Server Database
Our web service does not operate any centralized SQL or NoSQL database (no PostgreSQL, MySQL, MongoDB, Prisma, or Supabase) storing your media or prompts. All generation logs and history cards exist exclusively in your device's browser sandbox via IndexedDB (openhiggsfield/kv).
3. HttpOnly Sealed Credentials
Your Higgsfield Key ID and Secret Key are never stored in plain browser localStorage. They are sealed inside an encrypted HttpOnly; Secure; SameSite=lax cookie. Client-side JavaScript, third-party browser extensions, and malicious scripts cannot access or export your keys.
4. Direct Device Downloads
Video media deliverables are provided directly via cryptographically unguessable UUID endpoints from Higgsfield's Edge CDN. You can download final MP4 video files directly to your device and clear local history with a single click at any time.
How Your Data Flows
An end-to-end audit of data transit between your machine and Higgsfield.
• IndexedDB History Store
• Sealed HttpOnly Cookie
• Local Video Player
• Zero Database Storage
• No Prompt Logging
• Path Traversal Guard
• US H100/A100 Clusters
• Seedance 2.5 Inference
• Signed Media Delivery
Architectural Comparison
Why local-first privacy is our defining product principle.
| Privacy & Security Property | Higgsfield Open | Conventional AI Video Platforms |
|---|---|---|
| Can other users see your generated videos? | 100% Private (No public feeds) | Often public in Discord / Community feeds |
| Central server database storing your prompts | None (Stateless architecture) | Permanent database logs on vendor servers |
| API Key Storage | HttpOnly, Secure, SameSite=lax cookie | Plaintext localStorage or cloud storage |
| Model Training on Your Brand Assets | Zero training on user uploads | Often trained on unless enterprise opt-out |
| Data Erasure Control | Instant 1-click local cache & cookie wipe | Multi-day account deletion ticket queues |
Frequently Asked Questions
Are the videos I generate visible to anyone else using the website?
No. All generation history, gallery cards, and video links are stored locally inside your personal browser via IndexedDB. There is no public user directory or shared feed. No other visitor or user can see your videos.
Where are my uploaded product images or creator selfies stored?
When you upload a product or selfie for Seedance 2.5 face-locking, it is stored with a random, unguessable cryptographic token and strictly sanitized against path traversal attacks. They are never published in any public library.
How are my API credentials safeguarded?
Your credentials are stored exclusively in an HttpOnly cookie that is inaccessible to browser JavaScript. They are never sent to third-party tracking services or written to disk.
Can I audit the source code?
Yes. Higgsfield Open is fully open source. You can inspect the entire repository, route handlers, and storage adapters on GitHub at princejain756/Higgsfield-Open.