Tabletally Privacy Policy

Who is responsible

Tabletally is published by an independent iOS developer (Apple Developer Team ID ZM8LF8494F). Questions and privacy requests:

Contact: captainlongevity@gmail.com

The records stored on your device

• Game titles and attributes, purchase information, shelf locations, cover photos, cached BoardGameGeek game facts, and imported collection CSV values.
• Player names, score-pad definitions and scores, play dates and durations, locations and notes, borrower names, loan dates, and locally calculated statistics.

These records and preferences are used to provide the app features you choose. Unconfirmed game, play, player, loan and score-pad editor fields are held in the current editor rather than saved as resumable setup drafts; closing the editor or process can discard them. The app separately keeps onboarding completion, purchase-entitlement caches and local rating milestones (first use, completed-play count and last request date) in UserDefaults. These settings are not included in collection or play CSV exports. Local calculations do not send the input records to a developer-operated service. There is no in-app account or developer-operated cross-device sync.

If the saved library cannot be opened, the updated App shows a storage-unavailable screen and blocks normal record creation and editing. It keeps the existing database files and pauses library seeding and app-side library-snapshot updates instead of treating a temporary empty store as your collection. Updated Siri and Shortcuts actions also stop when the persistent library is unavailable. Read failures are reported instead of being treated as an empty collection, and logging reports success only after a successful save. Existing widget snapshots may remain visible. Close and reopen the App and contact support before deleting or reinstalling it; the recovery screen is not a backup or a restoration guarantee. Older installed versions may behave differently until updated.

How Tabletally handles its main features

Core collection management, scorekeeping, logs and statistics work with your saved records and manual game entry.

Game data sources and earlier versions

This version does not include online game lookup or a lookup entry. Search and game-detail requests remain disabled because the required commercial authorization and API token have not been obtained. Existing cached facts remain local, and you can enter or edit details manually. Pro CSV import parses a file you select locally; CSV export remains available free.

Older installed versions can still attempt direct HTTPS requests to boardgamegeek.com until updated. Those requests include the typed game-name query or selected game ID, IP address and ordinary request metadata, and can be refused by the service. Player names, scores, play history, loans, collection CSVs and photos are not part of those lookup requests. Previously cached game information may remain on your device. The provider’s handling of earlier requests is described in BoardGameGeek’s Privacy Policy.

Optional permissions and system services

• Selected photos: The system photo picker gives the app the photos you choose for a record. Those copies stay in local app storage; the app does not browse or upload your entire photo library. Picking an item may cause the system Photos service to retrieve it from your own iCloud Photos account.
• A CSV you select: The Files picker grants access to the collection CSV you choose to import. Parsing is local; the app does not upload the CSV. Your file provider may retrieve the original under its own settings.

Permissions are requested in connection with the feature that needs them. You can refuse or revoke them in iOS Settings; features that need a refused permission may be unavailable. Selected photos and files are separate from granting unrestricted access to an entire library.

Widgets, shortcuts, and session displays

Widgets and shortcuts use locally stored or cached app data in this app’s shared container. The shared App Group snapshot can contain unplayed-game titles, active-loan game and borrower names, days lent, and a resumable session name. Widgets and shortcuts can expose this information outside the app. Cached displays can retain an earlier snapshot until the app refreshes it and the system reloads the display; use the system’s display settings for sensitive records. These displays do not create a developer-operated upload service.

Sharing, exports, and external links

Collection and play-history CSV exports and recap-card images are prepared locally and shared through the iOS Share Sheet. CSV import reads a file you select; it does not sign in to or download your BGG account. CSV exports are written to the app’s temporary directory before sharing. Temporary copies may remain until the system removes them; shared or saved copies are managed by the destination. These CSVs and recap images are not full backups and there is no full-database archive-import or recovery control.

Generating a file locally does not send it to us. When you choose a sharing destination, that app or provider can receive the selected content and apply its own privacy and retention rules. Opening a web link sends an ordinary request to the linked site. Review a report, photo, or screenshot before sharing information about yourself or others.

Apple purchases and diagnostics

Apple handles in-app payment and subscription billing. The app processes StoreKit product and transaction information to purchase, restore, and verify paid access. The updated paywall offers Yearly and one-time Lifetime access; historical Monthly transactions are still checked and recognized while valid. Trial eligibility is checked against the current Apple Account and is not persisted. We do not receive your payment-card details or billing address through the app. Apple may provide sales reports and, depending on your Apple settings, diagnostic information through its developer services.

Apple’s handling of purchases, device services, backups, and diagnostics is described in Apple’s privacy information.

Analytics, advertising, and tracking

We have not added advertising, behavioral analytics, or third-party crash-reporting SDKs to Tabletally. We do not sell your app records or use them for cross-app advertising tracking. This does not mean that Apple, an external site you open, or an optional data provider receives no connection information. Their exchanges are described above.

Retention, deletion, and device security

Deleting a game, player or score template removes that selected record after a successful save; deleting a game also removes its locally stored cover copy from that record. This is not a promise of immediate secure erasure from storage, caches or backups. Original system-library photos are unaffected. Play history, scoring sessions and loan records use separate identifiers and are not cascade-deleted; a retained record may lose a resolvable name or reference. Collection CSV import creates new game records for supported rows, rather than updating matching identifiers or skipping an existing collection item. Repeating an import may create duplicates. Collection and play CSV exports omit photos, complete scoring state and other records and do not provide full-database recovery.

Removing the App normally removes its local container, not independently kept original media, exported files, recipient copies or older backups. Manage those copies separately. Device-backup recovery requires a usable completed backup; the developer has no record archive to retrieve.

Use a device passcode and appropriate operating-system protections. Tabletally does not currently provide a biometric App Lock. Device protection does not hide exports or widget content from everyone who can access those destinations. Because we hold no remote record copy, we cannot recover a lost local record or delete a copy you sent to another provider.

If you contact support

Emailing captainlongevity@gmail.com voluntarily gives us your email address, message, and any attachments you send. We use that information to answer your request, investigate the issue, and meet applicable recordkeeping obligations. It is processed through email providers and kept as needed for those purposes; you may ask us to delete support correspondence, subject to any legal retention requirement. Please omit unnecessary private records.

This policy website

These static legal pages are hosted by Vercel. Loading a page makes a web request that can disclose your IP address, page URL, time, and browser or connection metadata to the host for delivery and security. We have added no advertising or analytics scripts to these pages.

Hosting information: Vercel’s Privacy Notice.

Children and privacy requests

Tabletally is not designed to solicit children’s personal information through accounts or a developer-operated journal service. If you believe a child has provided personal information to us through support, contact us. You can manage local records yourself and contact us about support correspondence or other data we actually hold. For information held by Apple or another provider, use that provider’s request process.

Policy changes and contact

We will update this page and its last-updated date if these practices change. Material changes to app data handling will be explained before or when the affected feature is introduced. Privacy questions: captainlongevity@gmail.com.

Optional sample records

In the updated app, Settings offers Add sample records with a confirmation. Samples are stored locally alongside ordinary records, can appear in totals, exports and widgets where those records are supported, and count toward applicable free limits. Adding samples does not erase existing records or grant paid access. Existing sample records from earlier versions remain until removed using the app’s applicable record controls.