DomiFrame
Privacy
Privacy policy
Pictures sent to a DomiFrame are encrypted before they leave your device, so the server can't see them. There are no accounts, no ads, no analytics and no tracking, and nothing is sold. This page says exactly what is stored, where, and for how long. It covers the website (domiframe.art), the DomiFrame iPhone and iPad app, and the frames.
Your pictures are end-to-end encrypted
Every frame makes its own frame code and shows it on its screen. The code never goes to the server. When you send a photo, your phone or browser locks everything with that code before it leaves the device: the picture for the frame, its previews and thumbnail, the original photo (kept so it can be edited again), the edit settings, any caption or signature, your name if you add one, and folder names. The server stores only the locked (encrypted) data. The frame unlocks a picture with its code just before drawing it.
That means DomiFrame can't see, sort, scan or hand over your pictures or names, because it doesn't have the key. It also means a lost code can't be recovered by us.
What the server does store
- About each frame: its ID, the name it was given when it was set up, its screen size and how it hangs, and its settings (how often it changes picture and checks in, shuffle, quiet hours and their time zone, which folder it shows).
- About each picture: when it was sent, its place in the queue, which folder it's in, whether the frame has shown it, a day it should show on if one is set, and when it was removed. The picture and its names stay encrypted.
- From the frame when it checks in: the time, its battery voltage, its firmware version and screen size. Only the latest check-in is kept.
- If you turn on alerts in the iPhone app: a push token from Apple for your phone, kept with that frame so we can tell you when it's late or its battery is low. It's deleted when you turn alerts off, forget the frame, or the frame gets a new code.
- Keys: a one-way fingerprint (SHA-256 hash) of the frame's access token and of its device key, so the server can check them without storing them.
DomiFrame's own code doesn't record IP addresses, devices or browsing.
Who else is involved
- Netlify hosts the website and the server, and stores the data above. Like any web host, it handles your IP address and basic request details to deliver pages and may keep them in logs for a short time. See Netlify's privacy policy.
- Google Fonts: the website loads its typefaces from Google, so your browser contacts Google when you open a page. See Google's privacy policy. The app doesn't use Google Fonts.
- Art Institute of Chicago: in the app, Add Art shows public-domain paintings straight from the museum's image server, so the app contacts artic.edu when you open it. Nothing about you or your frames is sent. See the museum's privacy policy.
- Apple: if you turn on Sync codes with iCloud in the app, your frame codes are stored in iCloud Keychain, which Apple end-to-end encrypts so that not even Apple can read them. If you turn on alerts in the app, they're delivered by Apple's push notification service, which gets the alert's text (the frame's name and what's wrong) and your phone's push token. See Apple's privacy policy.
No other service receives anything.
What stays on your device
- Website: frame IDs and codes you've opened (so you don't have to type them again), the light or dark setting, your name for signing and a few editor choices, in your browser's storage. Clearing your site data removes them.
- App: frame codes in the iOS Keychain, on this device only unless you turn on Sync codes with iCloud in the app's Settings (then also in iCloud Keychain, end-to-end encrypted by Apple, so your other devices get your frames); the list of frames you've opened, your name for signing and a few editor choices in the app's own storage. Removing a frame in the app deletes its code, from iCloud too if it's synced. Deleting the app removes the rest, though iOS can keep Keychain items after an app is deleted: remove your frames in the app first to be sure.
- Photos and camera: the app uses the system photo picker, so it only sees the photos you choose. The camera is used only to scan an invite QR code; nothing it sees is saved or sent.
Who can see and change a frame's pictures
Anyone with the frame's code or invite link can send pictures to it, see its pictures and remove them. Only share it with people you trust. To shut everyone out, make a new frame code in the frame's Wi-Fi setup: the old code stops working, and the pictures and folders sealed with it are put away. They're still sealed, so nobody can open them, and they come back only if the old code is typed into the frame's Wi-Fi setup within 30 days. After that they're deleted.
How long things are kept
- Pictures stay until someone removes them. Removed pictures stay in Recently removed for 30 days, then they're deleted for good (or sooner, if someone deletes them from there).
- Making a new frame code puts that frame's pictures and folders away for 30 days, still sealed, then deletes them.
- If a frame is deleted, everything about it is deleted with it.
Children
DomiFrame isn't aimed at children under 13 and doesn't knowingly collect anything from them. It doesn't collect personal details from anyone.
Your choices
You can remove any picture, empty Recently removed, or make a new frame code at any time, without asking anyone. To have a whole frame deleted, open an issue at github.com/domchom/domiframe/issues with the frame's ID. Never post a frame code there: issues are public, and the ID is all that's needed.
Changes
If this policy changes, the new version will be posted here with a new date. A change that collects more will be explained here before it happens.
Contact
Questions about privacy: github.com/domchom/domiframe/issues.
Home · Privacy · Terms · Support · iPhone app