A plain-language rundown of what CFRAME stores, what it never touches, and what a couple of optional features send to outside services. Last updated October 2026.
There are no user accounts, no passwords, and no email addresses anywhere in this app. Uploading a frame or using one doesn't require signing up. The only password that exists is the site owner's admin login.
Your photo is edited entirely in your browser - positioning, zoom, rotation, filters, and the final composite are all drawn on a canvas on your device. Your photo is never sent to or stored on the server. When you download it or copy it to your clipboard, that image only ever exists on your own device.
The one thing the server does record is a plain usage count: each time you download or copy a finished image, the frame's "uses" number goes up by one. That's just an integer on the frame's row - it isn't tied to you, your photo, or your IP address.
When you upload a frame, this is stored on the server:
Nothing here identifies you personally unless you choose to put your real name in the creator name field (by signing in, or by typing it in yourself if the interface allows it). There's no IP address, device fingerprint, or analytics tag stored alongside any of this.
Signing in is entirely optional and only affects what name shows up as "Uploaded by ___" on a frame. When you sign in:
Because sign-in uses Google's and Facebook's own login buttons, your browser does talk directly to their servers during that step, and that exchange is covered by Google's privacy policy and Meta's privacy policy, not this one. If you'd rather not have that exchange happen at all, just skip sign-in and upload as Anonymous.
If you report a frame, we store the reason you selected, any details you typed in, which frame it was about, and when. We don't store your IP address - but to stop the report button from being abused to force-hide a frame (repeatedly reporting the same frame to trip the auto-hide threshold), we do keep a one-way, salted hash derived from your IP and that frame's ID. It can't be reversed back into your address, isn't linked to a name or account, and its only purpose is "has this visitor already reported this specific frame."
To stop upload spam and to slow down anyone trying to guess the admin password, both actions briefly log the same kind of one-way, salted hash described above (this time not tied to any specific frame). Each entry just says "this hash attempted this action at this time" and is automatically deleted after 24 hours - it isn't kept longer than that, and isn't used for anything besides catching too-many-attempts-too-fast.
The only cookie this site sets is a standard PHP session cookie, used to remember your display name (if signed in) and, on the admin page, whether you're logged in as the admin. It's a functional cookie, not a tracking or advertising one, and it goes away when your session ends.
Page text uses the Inter font, loaded from Google Fonts. Like any external resource, that means your browser makes a request to Google's font servers when a page loads, which exposes your IP address to Google the way any web request would. Google's privacy policy covers that request.
If you uploaded a frame, your manage link lets you delete it (and its image) at any time - go to your manage link and use "Delete this frame." If you've lost that link, or you'd like a report you filed removed, reach out to the site owner directly.
