Privacy Policy

Information SETI Dex may process

• Account and access data: name, verified email, identity-provider identifiers, device-session information, membership, workspace, entitlement, and account-status information.
• User-maintained Logbook data: flight sectors, aircraft, airports, schedules and actual times, flight time, crew names, approaches, runways, remarks, role/duty classifications, simulator information, and local revision history.
• Documents and files: qualification/document metadata and files the user deliberately uploads, selects, or connects from an authorized workspace or storage provider.
• AFML Capture inputs: photos or files the user selects for the local AFML Capture workflow. The Founding Beta does not extract or upload those images automatically.
• Airport and personal reference data: airport searches, requested weather/NOTAM/AIP references, airline-entitled notices where applicable, and private notes the user chooses to save.
• Device-local data: the encrypted native Logbook Vault, drafts, preferences, offline snapshots, queues, and recovery state needed to keep selected workflows usable without a network connection.
• Security and diagnostics: request, authentication, integrity, error, device/app, network, and audit information reasonably necessary to secure, troubleshoot, and operate SETI Dex. Depending on the hosting layer, this can include technical information such as IP address and request timestamps.

Local-first Logbook

In the native iOS app, the working Logbook is stored in an encrypted, account-scoped vault on the device. Adding, editing, deleting, searching, and analyzing Logbook records is designed to operate against that local working copy. Ordinary Logbook edits are not automatically uploaded to a cloud database.

During migration or first setup, SETI Dex may import an existing authorized Logbook into the device vault. After that import, the local vault becomes the native app's working Logbook. User edits remain user-maintained Logbook data; SETI Dex does not represent those edits as airline, regulator, aircraft-record, or other operational authority.

Cloud backup and restore

Cloud backup is separate from the working Logbook. When the user chooses Back Up Now, SETI Dex may create an account/workspace-scoped recovery copy in the user's connected Google Drive. Backup files include an integrity checksum and are bound to the signed-in SETI account/workspace. Creating a backup does not make that file the live Logbook database.

Restore is also user initiated. SETI Dex verifies the selected backup's account/workspace scope and integrity before replacing the working Logbook on that device. A restore does not silently change another backup file or an unrelated external record source.

How information is collected

• Directly from the user when information is entered, photographed, selected, uploaded, edited, deleted, restored, or saved.
• From identity and storage services the user explicitly authorizes, such as Apple or Google sign-in and connected Google Drive features.
• From an existing authorized SETI workspace when the user performs an initial Logbook migration or requests a connected service.
• From live/reference providers when the user requests airport weather, NOTAM, AIP, or other configured reference information.
• Automatically from app/server security and diagnostic events needed to authenticate requests, prevent cross-account access, investigate failures, and protect service integrity.

Why information is used

• Authenticate the user and resolve the correct account, workspace, entitlements, and connected services.
• Let the user create, edit, delete, search, analyze, export, back up, and restore their own Logbook data.
• Provide flight-time summaries, analytics, document information, airport reference material, offline continuity, and recovery.
• Hold user-selected flight evidence locally and process reviewed OCR workflows only when the user explicitly initiates them.
• Protect data through account scoping, encrypted device storage, integrity checks, source boundaries, and access controls.
• Diagnose errors, prevent abuse, investigate security events, and maintain service reliability.

Connected services and service providers

SETI Dex may rely on third-party infrastructure only where needed for a selected feature—for example Apple or Google identity services, Google Drive when explicitly connected for backup/storage workflows, cloud hosting/database infrastructure for account and service functions, and error/diagnostic services. A connected provider is not permission to read unrelated user files or accounts.

SETI Dex does not authorize service providers to use pilot or account data for their own advertising or cross-service profiling. Providers that process SETI Dex user data are selected and configured to process data for the requested service under privacy and security protections intended to be consistent with this policy and applicable platform requirements.

Error diagnostics

The current native iOS build can use Sentry for error-only diagnostics when the production diagnostic DSN is enabled. SETI Dex configures this lane with default PII disabled, performance tracing disabled, screenshot attachment disabled, and privacy filtering that removes user, request, extra, email, token, aircraft-registration, flight-number, and other sensitive aviation/account details from diagnostic events where detected.

Diagnostic events are used to troubleshoot reliability and security problems, not for advertising or cross-app tracking. Browser cookie behavior is described separately in the Cookie & Tracking Notice.

Device-local and offline data

The native Logbook Vault is stored persistently in app document storage and protected with an encryption key kept in device-only secure storage. SETI Dex binds access to the active SETI device session/account so another signed-in account cannot simply open the prior user's vault. Signing out removes the active session and disposable caches but does not silently erase the user's Logbook Vault. The same account may need to sign in again to reactivate access to that local data.

Some airline-controlled material can have a shorter local retention rule than ordinary user Logbook data and may be removed or treated as unavailable after that rule expires.

Sharing, sale, advertising, and tracking

SETI Dex does not sell pilot records or account data. The current product does not use third-party advertising SDKs and does not use user data for cross-app advertising tracking. Information may be transmitted to a service provider, authorized storage provider, or connected system only when reasonably necessary to provide, secure, or troubleshoot the feature the user selected, or when disclosure is required by law.

Retention and deletion

User-maintained native Logbook data remains in the app's persistent local vault until it is changed, deleted, restored, or the app/device storage is removed. Signing out does not intentionally erase that vault. Cloud backup files remain in the user's connected Google Drive until the user removes them or another explicit retention action applies. Disposable caches, temporary AFML Capture state, diagnostics, security/audit records, and airline-controlled content can have different retention periods based on their purpose.

Files stored in a user-owned external service such as Google Drive remain subject to the user's ownership and that provider's controls; deleting a SETI Dex account does not automatically delete user-owned Drive backup files.

Deletion and revoking access

Users may edit or delete individual Logbook records directly in the native Logbook. Users can also use the available account-deletion flow or contact SETI Dex support about account/privacy requests. Account deletion and Logbook-data deletion are separate actions: deleting the SETI account does not silently delete user-owned Google Drive backups, and local device data may remain in app storage unless the user removes the app/device data or a dedicated local-data deletion action is used.

Before deleting an account, create a Google Drive backup if a portable recovery copy is needed. Once the account session is deleted, encrypted local-vault bytes that remain on the iPhone may no longer be unlockable in SETI Dex. The confirmation screen states this consequence before deletion.

Where an external service is connected, users may revoke that service's authorization through the applicable provider controls. Revocation can prevent future backup/restore access without deleting files already owned by the user in that provider.

Permissions

Camera and photo-library access are requested only when the user chooses a photo/AFML workflow that requires them. Denying an optional device permission does not authorize SETI Dex to bypass that choice. File selection and share-sheet actions are user initiated.

Your privacy choices

• Edit or delete your own native Logbook records directly in SETI Dex.
• Choose when to create a cloud backup and whether to restore one.
• Decline or later revoke optional camera/photo-library permissions through iOS settings.
• Disconnect or revoke authorized identity/storage access using available SETI Dex or provider controls.
• Review and export records through available SETI Dex record/export tools.
• Request account deletion through the signed-in Account surface or contact support for assistance.
• Ask a privacy, access, or deletion question at setisupport@gmail.com.

Security

SETI Dex uses account/workspace scoping, encrypted persistent storage for the native Logbook Vault, device secure-key storage, session-bound vault activation, connected-service authorization, and cloud-backup scope/checksum validation designed to reduce unauthorized access and accidental cross-account restore. No system can guarantee absolute security, so suspected security or privacy incidents should be reported promptly.

International processing

Cloud and connected-service providers may process information in countries other than the user's country. Where that occurs, SETI Dex relies on the provider's applicable contractual, organizational, and technical safeguards and limits processing to the service purpose described in this policy.

Children

SETI Dex is designed for pilots and aviation professionals and is not directed to children. SETI Dex does not knowingly seek to collect personal information from children through the product. If such information is believed to have been provided in error, contact support so it can be reviewed and handled appropriately.

Changes to this policy

This policy may be updated as SETI Dex features, providers, or legal obligations change. Material changes will be reflected by updating the effective date and public policy. App Store privacy disclosures should be updated when a release changes the app's data practices.

Current beta operator status

SETI Dex is currently distributed only through a limited internal TestFlight beta. The responsible legal owner/entity, final governing-law terms, and public commercial-distribution details must be finalized and published before any public paid release. This beta privacy notice does not itself authorize public commercial distribution.

Contact

Privacy, account, deletion, or security questions can be sent to setisupport@gmail.com. Current product support guidance is also available on the public Support page.