Visited

A private travel journal for iPhone.

Visited Privacy Policy

Last updated: October 22, 2026

Visited is provided by Gavin Galusha. Contact: gavingalusha2@gmail.com.

Information in Visited

Visited stores the countries, regions and cities you mark, visited/wishlist status, optional visit dates, update timestamps, notes and other associated metadata. Place names and geographic coordinates are drawn from the bundled place catalogue where available. Places are entered manually: this version does not request GPS, contacts, camera or photo access. No Visited account, email address or registration is required.

Local storage

Your history is saved in a persistent SQLite database in the app’s Documents directory, with transactional writes. It survives normal app closure, offline use, phone restart and power-off after a write has committed. If saving fails, the app displays an error; keep it open and resolve that error. Device loss, damage, storage failure, deleting the app or erasing the phone can lose unsynced data. iOS may include the database in device backups depending on your settings. We cannot read, manage or delete your device backups.

When upgrading from the old storage format, Visited migrates the original records and keeps the original local store for recovery until an explicit erase. Loading failures do not intentionally replace your history with an empty database.

Private iCloud synchronization

iCloud sync is off until you explicitly enable it in Data & Backup after reviewing the disclosure. On supported signed iOS builds, once enabled, Visited attempts to synchronize history using Apple’s CloudKit private database for the Apple Account already signed into the phone. No separate Visited login is created. Your records, notes and associated metadata are transmitted to Apple’s iCloud service to make them available on other devices using that same Apple Account. We do not upload your travel history to a developer-controlled server. This version has no analytics, advertising or tracking, and we do not sell your data.

History payloads use CloudKit’s encrypted record fields. Apple manages iCloud security, storage and availability under its applicable terms and privacy policy (https://www.apple.com/legal/privacy/). This is not a promise of protection against every device or account compromise. The app remembers an opaque CloudKit account identifier locally to pause sync if the Apple Account changes and avoid automatically mixing different accounts.

You can withdraw your sync choice by turning off iCloud sync in Data & Backup without losing local history. Turning it off stops subsequent automatic attempts; requests already submitted to Apple may finish; it does not delete existing iCloud copies. The app remains usable offline or without iCloud. Sync retries on app launch/foreground and periodically while open; this version does not promise background sync while closed. Data & Backup shows the actual attempt status and the last confirmed successful sync. Errors, quota limits and network failures can delay upload or restoration. Sync is not an independent historical backup: erasures and edits propagate. Concurrent edits may choose one current version; differing versions received on the phone are retained as recovery copies and included in exports.

Export, email and recovery

Data & Backup exports CSV and PDF reports, a versioned JSON backup with a corruption-detection checksum, or a passphrase-encrypted backup. Exports contain history, available coordinates, timestamps, notes, metadata and retained recovery information. Backup files also contain preferences and revision metadata. CSV/PDF are reports, not restore formats.

You choose Mail, Files, AirDrop or another destination using the native share sheet. No email is sent automatically or through our servers. Chosen providers and recipients handle their copies under their own policies; they may have different privacy protections. Only share with destinations you trust. Unencrypted reports and backups expose your travel history. The app removes temporary export files after sharing completes. Interrupted operations may leave temporary files for iOS to clean up; saved or emailed copies remain outside the app.

Encrypted backups use AES-256-GCM with a random salt, PBKDF2-HMAC-SHA256 (600,000 iterations), and your passphrase. The passphrase is not stored in the history database or sent to us. We cannot recover a lost passphrase. A plain backup checksum detects corruption; it does not prove who created the file.

Import validates supported formats and integrity before offering a merge. Existing places remain unchanged. Different imported versions are retained as recovery copies and can be explicitly restored. Imports do not automatically apply erase markers. Older backups may reintroduce previously erased data if you intentionally restore them.

Erase All My Data

Data & Backup → Erase All My Data asks for confirmation, then removes local history, notes, recovery copies and the retained legacy store, and resets display preferences. It requests removal of the applicable history from your private iCloud database. If the app has never connected to an iCloud account, erasure stays local and does not create a cloud copy. A minimal non-content erase marker and operational sync/account metadata (including your sync choice date and disclosure version) are retained to prevent stale devices from automatically restoring old history.

If iCloud is offline or unavailable, deletion stays pending. Keep the app installed, reconnect using the original Apple Account and retry until confirmed. Other devices must open Visited and synchronize to apply the erase. Old app versions that do not understand this protocol must be upgraded. The app cannot delete copies already saved to Files, emailed, held by recipients or retained in older device backups. Remove those separately through the relevant provider. Restoring an older device backup or deliberately importing an old export can restore erased information. If you delete the app before pending cloud deletion completes, the request cannot be guaranteed to finish.

Retention, choices and privacy requests

Local history and recovery copies stay until you remove them or erase all data. Connected iCloud history remains until erased; switching off sync alone does not erase it. Operational identifiers and erase markers remain as described above for safe synchronization. Apple controls any additional retention under its own service and backup policies. We do not hold a developer-server copy of your journal.

Use exports to access a complete copy of your history, place details to correct entries, and Erase All My Data to delete history. You can use local storage without consenting to iCloud. The app stores your latest sync choice and its date locally to remember that preference. For questions or applicable privacy-rights requests, contact gavingalusha2@gmail.com. Do not send sensitive journal contents or your passphrase. Because we do not hold your private database, we cannot remotely retrieve it or erase copies held on your devices, in private iCloud or by export recipients on your behalf. We will help explain the available controls. You may have additional rights, including contacting your relevant data protection authority, depending on where you live.

Children, future accounts and changes

Visited is a general audience app; we do not operate a service collecting children’s personal information. No optional Visited account is implemented in this version. If account-based synchronization is introduced later, data practices and controls will be updated before use. Updates to this policy will be published with a revised date. Material changes requiring a new choice will be presented before the new processing is enabled. Contacting support voluntarily shares the contents of your email with the support mailbox provider; use that channel only for information needed to answer your request.