Yours, by design.
Jefield keeps your work on your device. When something leaves, it leaves sealed, and only because you signed in to sync it.
How it's built
Local-first
What you kept, every version and every project lives in your browser's storage. It opens without a network.
Sealed sync
When you sign in, everything is sealed with AES-GCM-256 on your device first. File names are keyed hashes, so the server can't tell what anything is.
Your library's key
Each library has its own key. With Google sign-in it's kept sealed under your account, so your own devices can open the same library.
Sign-in that asks for little
Google sign-in takes your account id, email, name and picture. No Drive, no Gmail, no other permission is asked.
On-device tools
Cutting out, removing and filling run on your device. The models download once; your pictures aren't sent anywhere.
No tracking
No analytics, no advertising identifiers, no error collectors. The site's host may keep ordinary access logs.
Never trained on
Jefield never sends your work to an AI, and never trains anything on it.
Nothing overwritten
Every save is a new version. Going back is a new version too.
Signing in, honestly
If you sign in with Google, your library's key is kept sealed on the server under your account and handed only to your own signed-in devices. That's how your phone and laptop open the same library. It also means the server's operator could open a signed-in account's library.
Report a vulnerability
Found a hole? Tell us first.
Email hello@mocmallen.com. Say what you found, how to reproduce it, and what it lets someone do. A person reads every report.
- We answer within three working days, and say what we will fix and when
- We fix what puts anyone's work or account at risk before anything else, and tell you when it ships
- We thank you by name on this page if you'd like, once it's fixed
- We won't take legal action against research that keeps to the rules below
Please don't
- Look at, change or delete other people's work, libraries or accounts: use your own, or two of your own
- Run load tests, denial of service, spam or social engineering against us or our providers
- Publish details before we've had a reasonable time to fix them (we suggest 90 days)
Machine-readable: /.well-known/security.txt. In scope: this website, the Jefield app at /app, its server functions under /api, and the Windows, Mac and Android apps.
Questions, answered
Can Jefield see my files?
Files that stay on your device, no. Synced copies are sealed with your library's key; with Google sign-in that key is kept sealed under your account so your devices can open it, and the operator could technically open it. Read the privacy page for exactly how.
Do the AI tools upload my pictures?
No. The models download once from public CDNs the first time you use them, and then run on your device.
How do I delete everything?
Erase a file or a project for good from its menu: it leaves this device, the cloud and your other devices. Sign out in Settings and Jefield first makes sure your work is in your account, then clears this browser's copy; anything that could not reach your account stays here, sealed to you. To delete the account record and its sealed copies, write to us from the contact page. Keep a copy first: Settings, Your library, Download a backup.
How do I report a vulnerability?
See Report a vulnerability below: what to send, what we promise, and what not to test.
Creative workspace
Make things that stay yours.
Your words open Jefield and wait there for you to keep. Making things from a prompt with AI is coming next.