Privacy policy

Who operates Again Soon

Brandon Beals is the individual developer and operator of Again Soon and againsoon.app. For support or a privacy question, contact [email protected].

This policy covers the Again Soon app and this website. Apple and any file or email services you choose also handle information under their own terms and privacy practices.

Your library is stored on your device by default

Again Soon stores the items and entries you create on your device. These can include names, descriptions, dates, notes, selected photos, colors, goals and targets, archived status, saved places, and reminder preferences. Entries preserve their recorded time precision and time zone when known. The app uses these records to calculate elapsed time, show history and charts, and provide reminders you choose.

There is no separate Again Soon account, advertising SDK, or developer analytics SDK. Ordinary logging does not send your library to a developer server. Device backups, exports, Apple services, and optional iCloud sync have the separate behavior described below.

Permissions, app appearance, authentication sessions, purchase-access state, and global notification and celebration choices are stored locally. The app also keeps device-local engagement dates and review-request attempt information to limit when it asks Apple to display a rating prompt. It does not use your item names, notes, goals, or sentiment to select that prompt, and these counters are not uploaded to developer analytics.

Photos are selected by you

Again Soon uses Apple’s photo picker for the photo you choose. It does not scan your entire photo library. Newly selected photos are resized and re-encoded, removing their original metadata. Photos in imported backups retain their existing bytes and may contain metadata. Apple’s picker may retrieve a selected photo from iCloud Photos according to your Apple settings.

Places and notifications require your choices

A saved place can contain a name, address, coordinates, radius, and prompt setting. Saving a place is separate from enabling location monitoring. Place search and maps use Apple MapKit and can send requests to Apple.

If you enable an eligible arrival prompt and grant the required location and notification permissions, iOS can monitor the selected region. Again Soon does not store a continuous route history. An arrival prompt asks you to open the app and review an activity; it never creates an entry automatically.

You can choose manual review reminders, learned review prompts, and milestone notifications separately. Notification text does not disclose private item details. Turn off a prompt in the app or change its permissions in iOS Settings. Manual logging remains available when permissions are denied. Canceling an unsaved item does not save its draft place or register its region.

Private items conceal identifying details in the app

Private-item controls hide names, photos, notes, locations, and goals until device-owner authentication succeeds. Again Soon receives an authentication result from Apple, rather than your face template or passcode. Revealed details are concealed again when you lock the app or leave it.

Private entries’ calendar dates and generic analytics counts, rates, and timing remain visible while locked. Private items are excluded from widgets. Notification previews remain generic.

This control protects visibility inside the app. Private records remain in the underlying library and can be included in an authenticated export or optional iCloud sync. Local files use iOS file protection; Again Soon does not add a separate encrypted vault or database encryption layer.

Exports and device backups create separate copies

Export creates a readable JSON backup in a destination you choose. Private items and their history and places are excluded by default. Including them requires your explicit choice, device authentication, and confirmation. Again Soon does not separately encrypt the exported file.

The file provider, destination, or recipient you choose handles that copy under its own practices. Device backups can also retain app data according to your iOS and Apple settings. Restore validates a selected file, shows a preview, and asks before replacing your library. A backup that excluded private items cannot restore them. A supported Onceward import is a deliberate file import and does not access or change the other app’s storage.

Optional iCloud sync transfers your complete library

iCloud sync starts off. Enabling and continuing it require your explicit opt-in and verified Again Soon Plus access. The app uses your Apple account’s private CloudKit database and has no separate developer-hosted sync server.

Enabling sync transfers the complete library, including private items, names, dates, notes, photos, archived records, goals, saved place coordinates, reminder settings, and goal-feedback metadata. Record identifiers, change versions, and retained deletion records are used to merge changes. Device authentication does not exclude private items from this transfer.

Global app appearance and notification choices, OS permissions, and authentication sessions stay on the device. The app stores a local hash of the Apple account scope to help avoid mixing accounts. Changing Apple accounts requires confirmation before syncing the local library with that account.

Again Soon does not add its own end-to-end encryption layer to CloudKit payloads. Apple’s iCloud account, storage, and security practices apply. Turning sync off stops new transfers and keeps local data and existing cloud records. Sync pauses when Plus ends or its access cannot be verified. The retention limits below also apply.

Apple handles purchases and platform services

StoreKit contacts Apple to load subscription offers, process purchases, verify transactions, and restore access. Apple handles payment details; Again Soon has no payment-card form. The app uses transaction results to determine Plus access.

Photos, maps, CloudKit, device backups, and Apple’s native rating prompt involve Apple’s services and your settings. TestFlight users can send beta feedback and diagnostics that Apple makes available to the developer. This is separate from an app analytics SDK. See Apple’s privacy information.

Deleting records does not remove every copy

Archiving keeps an item’s history. Deleting an item or entry removes it from the current library. A previous validated local snapshot is kept for recovery until it is replaced, so it can contain removed records. Local sync bookkeeping can also retain earlier field values. Plus ending does not delete your records.

When sync has been enabled, deletions are represented by retained synchronization records rather than a physical purge of the cloud record. Earlier fields can remain so that stale device changes do not bring deleted entries back into the active library. The app has no in-app control that purges all retained cloud data. Turning off sync or uninstalling the app does not erase existing iCloud records, exports, device backups, or copies you shared.

Manage exported files and device backups through the destinations and Apple settings that hold them. Contact [email protected] with questions about retained information. Do not assume that deleting an entry, canceling Plus, or uninstalling removes it from every copy.

Website hosting and security cookies

This website serves static HTML, CSS, and images. Its code sets no cookies, uses no browser storage, and includes no analytics, advertising, tracking pixels, external fonts, account system, mailing-list form, or automatic support upload.

DigitalOcean hosts the website. Serving a page involves ordinary request information, such as an IP address, browser request headers, the requested resource, and request timing. The hosting service can process this information for delivery, operation, and security, including operational logs according to the hosting configuration. This is separate from app library data; the website does not receive your library.

The current hosting edge uses Cloudflare and can set a __cf_bm security cookie to help identify automated traffic. This is separate from website audience analytics. Read Cloudflare’s cookie information for its purpose and handling.

Opening an external link sends a request to that destination. Opening the email link uses the email app and provider you choose. Their own practices apply.

Support correspondence and privacy requests

If you email support or send TestFlight feedback, the developer receives the content you submit, such as your email address, message, and attachments. This information is used to respond, investigate the issue, and handle related follow-up. Correspondence may be retained for those purposes. There is no automatic personal-library upload.

Share only what is needed and redact private details in screenshots. Do not send passwords or verification codes. A full backup can contain sensitive personal records, including photos and places.

Contact [email protected] to ask about access, correction, deletion, or other privacy requests concerning information you have sent. Your applicable privacy rights depend on local law and the information involved. The developer does not automatically receive or have a server-side copy of your on-device library.

Changes to this policy will be posted here with an updated date. Changes to optional features do not remove the need for the choices and permissions described in this policy.