No collection
Memory Atlas collects, transmits and sells no data. The application contains no advertising, no analytics and no automatic crash reporting. Its only network connection is the update check, described below. Oorun has no access to any of the information you enter.
Update check
At launch, then at most once a day, Memory Atlas downloads the list of published versions (an appcast.xml file) from GitHub (github.com, a service of GitHub, Inc.), then, if you agree to install a new version, its disk image. Like any Internet request, it gives GitHub your Mac’s IP address and a technical header (name and version of the app and of the Sparkle component). It sends no content of your repositories, no identifier of your Mac or of your account, and no system profile. GitHub processes this data under its own privacy statement (https://docs.github.com/site-policy/privacy-policies/github-general-privacy-statement); Oorun has no access to it.
An update is only installed with your consent, once its signature has been verified. You can turn off automatic checks in Settings › General: Memory Atlas then makes no connection at all, and Memory Atlas › Check for Updates… only checks when you choose it.
Where your data lives
- Your repositories (
.atlas) are saved where you choose. - Safety copies are saved on your Mac, in
~/Library/Application Support/Memory Atlas/Backups. - The application settings are saved in the macOS preferences of your account.
- Exports and transfer packages are written to the folders you choose. Memory Atlas sends them to no one, not even to Obscura Flow.
Linked files
When you link a file to a unit of description, Memory Atlas reads its technical metadata (name, size, type, dates) and keeps a bookmark to it. It never copies, moves or modifies the file. macOS may ask you to allow access to the Desktop, Documents or Downloads folders, or to external and network volumes.
Logs and diagnostic report
Memory Atlas writes technical logs to the macOS system log, on your Mac (visible in the Console app): repository openings, integrity checks, safety copies, exports, errors. They hold no content of your descriptions: only technical identifiers, counts, durations and error codes; file paths are masked. macOS deletes them itself over time.
Help › Export Diagnostic Report… saves these logs and the technical state of the open repository (identifier, integrity check, record counts) to a text file, where you choose. It holds no content of your descriptions. Memory Atlas sends it to no one: you read it and decide whether to pass it on.
Personal data in your descriptions
Archival descriptions often contain personal data (names, biographies, places, dates). You, or the organization on whose behalf you act, are their controller within the meaning of the GDPR: it is up to you to define their legal basis, retention period and conditions of access (ISAD(G) element 3.4.1). To erase a unit, move it to the trash, then choose “Delete Permanently…” or “Empty Trash…” (⇧⌘⌫): the unit and its description are removed from the repository, with no undo. Safety copies taken earlier still contain them until they are rotated out (Settings › Safety copies); delete them from the Finder if needed. File › Export › JSON… extracts your data as JSON.
Contact
For any question: see Oorun’s details in the legal notices.