AtelierRecords Privacy Policy

Effective date: 2026-05-22 · Last updated: 2026-11-04

Short version: AtelierRecords stores your fine art and decorative art collection records — pieces, provenance chains, acquisitions and disposals, appraisals, condition reports, beneficiary designations, insurance policies and itemized schedules, selected artwork photos and document-reference fields — on your iPhone only. Record processing runs on your device; records leave only through sharing or system backups you choose. We do not operate an app-record server and no analytics. Apple handles purchases and system services, including downloading selected iCloud photos when needed. Opening reference links, sharing records, visiting these pages and emailing support involve the chosen providers. Device backup depends on your Apple settings and successful completion; it is not an App-operated recovery service.

Who builds AtelierRecords

AtelierRecords is published by an independent iOS developer (Apple Developer Team ID ZM8LF8494F). For any privacy-related question, write to captainlongevity@gmail.com.

What never leaves the device

The app does not automatically send the following records to the developer for storage, advertising or analytics. User-selected exports, optional system services and support messages are handled as described in this policy:

We do not operate an app-record server. The app does not automatically send these fields to us; information you choose to include in a support message is an exception.

No third-party data sharing

AtelierRecords does not share any records with auction houses, art insurance carriers, due diligence databases (Art Loss Register, IFAR, German Lost Art Foundation, US Holocaust Memorial Museum, etc.), appraisal organizations, conservation organizations, government agencies, or research databases. There is no advertising SDK, no analytics SDK, and no marketing-data partnership in the app. If a future release ever introduces any such integration, it will be strictly opt-in, with a clear in-app notice before any record leaves your device.

What lives on the device

Archive records are stored locally using Apple's SwiftData framework. Apple device backups may include the local store and photo files depending on your settings and successful completion; they are not a developer-operated recovery service.

How records are processed

Several features process data locally on your device only:

Keeping your collection recoverable

AtelierRecords has no CloudKit synchronization, developer-hosted archive or full-archive JSON backup/restore feature. Apple device backup may include its local store according to your device settings. Verify that your backup has completed and that you can use the relevant Apple recovery process.

Every user can save a basic single-piece PDF with photos and a Markdown text copy. These are portable records, not a restorable database backup. The Markdown file does not embed photographs. Plus adds the professional collection reports. Copies saved to Files, Photos, email or another destination remain there until you manage them separately.

Subscription verification through Apple

AtelierRecords uses Apple StoreKit for a yearly subscription and a one-time non-consumable Lifetime purchase. Loading products, checking offer eligibility, purchasing, restoring and verifying access communicate with Apple. The app reads verified product and entitlement information, including expiration or revocation status where applicable, and keeps local access state. Apple processes payment; AtelierRecords does not receive your payment-card details or Apple Account password. Current and supported historical purchase access depend on verified transactions. See the AtelierRecords terms for the available plans and subscription handling.

Permissions requested

You can revoke any of these permissions at any time in iOS Settings > AtelierRecords.

Reference-only, not inference

AtelierRecords does not perform image recognition or AI-powered cataloging on your photos, does not auto-valuate any piece, does not make claims about whether a specific piece is looted art or whether a specific dealer or owner is culpable, does not generate legal opinions, does not query any due diligence database, and does not perform any artificial-intelligence analysis on your archive. Provenance gap flags (including the Nazi-era 1933-1945 flag) are rule-based computations on dates and ranges; they are reference-only and not a determination of provenance legitimacy, title, or restitution obligation.

Children

AtelierRecords is not directed to children under 13. The app has no child account or developer-operated record collection. Contact support if a child has sent personal information to us. The app's age rating reflects this.

Retention and deletion

Confirmed artwork deletion saves removal of the artwork and its linked ownership, transaction, appraisal, condition and beneficiary records before cleaning up their queued photo files. Separate insurance policies and scheduled-item records are not part of that cascade. A failed save keeps the editor open and restores the affected saved fields and relationships for retry. A local filename-only cleanup journal is prepared before the database change. After a successful save, cleanup checks saved references in a separate database context and removes only queued, unreferenced files. Files still referenced by other records or retained deletion snapshots are kept. Failed cleanup is retried during normal App startup and through Retry attachment cleanup; unreadable references or journal data postpone removal. This is not guaranteed immediate or secure erasure and does not scan unknown older files. If a discarded new file cannot be added to the journal, its name is retained only in memory for retry while the App stays open; interruption can leave an untracked draft file.

Removing an individual photo through the photo vault saves the changed record before attempting file removal; that separate path remains best effort and does not promise journal-based retry. There is no in-app trash or Recently Deleted recovery window. Original library images, exports and older device backups remain separate.

There is no in-app trash or Recently Deleted recovery window. PDF and Markdown exports cannot be imported to restore the collection or its original photos. Recovery from an Apple device backup depends on a usable completed copy and Apple's process; it is not guaranteed. Original system-library photos, exported files and older device backups remain separate and must be managed at their destinations. We cannot restore them.

International availability

The app is published in English and is primarily marketed in North America. The app does not route your archive through a developer-operated record server. Apple services, website hosting, support correspondence and sharing destinations may process information outside your region, as described in this policy.

Updates to this policy

If we ever change how the app handles data, we will update this policy and surface the change in the app before you can use the affected feature. The "Last updated" date at the top of this page reflects the most recent revision.

Local widgets and visible summaries

AtelierRecords's widget displays locally prepared summaries of app records. The app and its widget exchange the relevant summary and preferences through an on-device shared container; this is not a developer-operated record upload. Information displayed by a widget can be visible to people able to view the Home Screen or Lock Screen where it is placed. Use the widget and device display settings to control that visibility. Screenshots and independent copies remain separate from the records you later edit or delete.

Contact & Support

Privacy questions: captainlongevity@gmail.com

Older installed versions may use different save or cleanup ordering and may not offer these retry controls.

Checked local changes and retry

The updated acquisition/disposal, condition, provenance, beneficiary, due-diligence, appraisal, insurance-policy and scheduled-item forms now check both saves and deletions before closing. Failed operations retain the original affected graph and form input for retry, without globally rolling back unrelated pending changes. Editors apply fields changed in that form, preserving untouched stored precision, unknown values and parallel edits. Cancel discards only the local editor draft. Provenance gap-cache changes are committed with the provenance operation rather than through a second ignored save. Deleting an insurance policy cascades to its scheduled-item records. These subrecord controls do not erase independent artwork records, system originals, previously shared reports or document files merely referenced by an old record; the existing file-cleanup scope and retry triggers described elsewhere remain separate. Unconfirmed form drafts are held in memory and are not a full recovery archive.