Memory Magazine Privacy Policy

Your work is stored on your device

Memory Magazine has no app account or developer-operated storage service. It stores pages, text, optimized imported images, image descriptions, masks, private notes, saved export recipes and unfinished work locally. Editing and rendering do not send this content to a developer server or external AI service. The app has no advertising or analytics service and no built-in cloud sync.

Recovery drafts can retain full typed text and selection, creation setup and owned images, or mask pixels, editing history and tool settings. A mask draft does not make another copy of the source photo. Unfinished Photos or Files selections may need to be selected again after relaunch. Recovery records remain until saved work is durably confirmed and cleanup completes, or you explicitly discard them. Failed cleanup can leave a record for retry.

Images you choose

You select still images through the system Photos or Files picker. The app creates optimized owned copies, normalizes orientation and removes source metadata from those image files. Originals remain unchanged in Photos or Files. Optimized imports are not a full-resolution photo archive.

A cloud photo or file provider may download your selection before import. That provider handles it under its own practices. Optional subject-mask assistance runs on your device and can be reviewed and refined manually. Crops and masks are compositing tools, not secure redaction.

Finished exports and private archives contain different information

Public PDF, PNG, JPEG and ZIP exports

Finished page files contain the selected visible artwork. ZIP packages contain ordered public page files, a manifest and any selected companions. Private notes, source metadata and source pixels hidden by the final crop or mask are excluded. Information you place visibly on a page remains visible. You may include the magazine title in PDF metadata. An optional text companion includes public text and authored image descriptions shown in its preview.

Editable backups: .memorymag

A private editable backup has broader contents: selected magazines, private notes, full optimized source photos including areas outside crops and masks, masks, page structure, saved export recipes and custom style presets. Earlier recipes may contain earlier text, notes and source revisions. Editable backups exclude unfinished creation and unapplied editor journals, purchase authority and old public-output files. Complete and save an edit before backing it up.

Restore validates a compatible backup and adds copies with fresh identities to Archive. It does not replace existing magazines or grant purchase access. These archives are not encrypted by Memory Magazine.

Raw recovery copies: .memoryrecovery

After a separate contents acknowledgment, Make recovery copy can preserve private notes, full uncropped owned sources, hidden content, saved and unfinished drafts, unsaved magazine details, existing output files, database files and recovery or staging bytes. Damaged, incomplete or unsupported records may be included. It excludes purchase authority, disposable thumbnails, previously completed backup and recovery archives, and original files outside the app.

Checking a recovery archive verifies byte integrity; it does not establish that the database or records are usable. A raw recovery copy is not a validated editable backup, does not repair the library and cannot be imported through Restore an editable backup. Compression is not encryption.

Creating a recovery archive keeps a local copy. Saving it elsewhere requires a separate action. Nothing is automatically sent to MubarakLab or another person.

Destinations you choose

Saving and sharing use system interfaces. A destination may be on the device, in iCloud Drive or with another file provider or app. A chosen cloud destination may upload the selected copy and handles it under its own practices. Memory Magazine does not automatically publish your magazines. Dismissing a share sheet does not establish that delivery occurred.

App Store purchases

Apple processes purchases. Memory Magazine uses verified StoreKit transaction information to determine Pro access. The app does not ask you for payment card details or an app account. Restore purchases checks access for the current App Store account; it does not restore magazine files. A backup cannot grant Pro.

Apple handles its services under Apple's privacy policy.

Keeping and deleting local content

Archive keeps a magazine on the device and frees an active library slot. Trash retains it until you explicitly delete it permanently; it has no automatic expiry. Thumbnail cleanup removes regenerable data rather than magazine sources.

Deleting a magazine does not automatically remove source material or earlier notes still referenced by saved export revisions or retained recovery drafts. Manage saved revisions in Settings → All export history, and retained drafts in Recovery & diagnostics. Current Undo and Redo history can also retain source revisions. Removing output files while keeping their recipe preserves the sources needed to render that revision again.

Completed private archives retain captured content separately. Editing or deleting the original magazine, revision or draft does not rewrite those archives. Deleting local work also does not remove files or archives you previously saved or shared elsewhere; manage those copies at their destinations.

Removing the app or losing the device may lose local work. Keep an accessible editable backup separately. A raw recovery copy is not a substitute for a restorable editable backup. Device-backup behavior depends on operating-system settings and is not an app sync service.

Diagnostics and support email

Recovery offers a preview of a redacted diagnostic summary with version, schema, counts and save state. That summary omits photos, magazine titles, captions, provider filenames and private notes. It is different from the broad private recovery archive described above. You choose whether to create and share diagnostics; the app does not upload them automatically.

If you email almahmeed.dev@gmail.com, MubarakLab receives your sender address, message and any attachments you choose to send. We use that correspondence to respond to your request. Email is also processed by the email providers involved in sending and receiving it; this contact address uses Gmail, subject to Google's privacy policy.

Only send personal photos, editable backups or raw recovery archives if you choose to disclose their contents and they are needed for your request. You can use the same contact address to ask about access to or deletion of support correspondence. Records may need to be retained where the law requires.

This website

These pages use plain HTML and CSS without advertising, analytics scripts, contact forms or cookies set by these pages. The site is hosted by GitHub Pages. GitHub may process technical request information, including IP addresses, for hosting, security and operation under GitHub's privacy statement.

Questions and changes

Contact almahmeed.dev@gmail.com with privacy questions or requests. We will update this page if these practices change; the date above identifies the current text.