In short
- Photos are edited on your device and aren’t stored when you ask Mary.
- Sign-in goes through Apple or Google. Mariframe never sees a password.
- Every request is checked against your account, over encrypted connections.
- Found a problem? Write to security@mariframe.app.
01How your account is protected
Sign-in: you sign in with Apple or Google, so Mariframe never handles a password. The server checks each identity token with Apple or Google before accepting it.
Device token: the app registers your device with a random token kept in the device’s Keychain. The server stores only a hash of it, so a database copy can’t be used to sign in.
Account-only access: every request is checked against the account it comes from, and no one else’s data can be read through it.
Encryption: the app and this website talk to the server over HTTPS only. The database encrypts stored data.
02Your photos
Editing happens on your device. When you ask Mary, a smaller copy without its location is sent for that one edit and isn’t stored by Mariframe.
Mary’s AI providers get only what the task needs and can’t see other accounts. Your photos are never used to train models.
03Complete deletion
Delete account in the app removes your account, your sign-ins, your devices and your AI edit records from the server straight away. Deleted data can’t be restored.
04Reporting a security problem
Write to security@mariframe.app with what you found and how to reproduce it. We’ll reply promptly, keep you posted while we fix it, and credit you by name if you like.
Please don’t access other people’s data, run load or denial-of-service tests, or use social engineering. Our contact details are also at /.well-known/security.txt.