Terms of Use
Pre-release working terms · updated 5 October 2026
Important pre-release notice
These terms are a product-ready working draft for SETI Dex internal/founding-beta preparation. Final legal-entity details, governing law, consumer terms, and App Store subscription language must be reviewed and approved before public paid distribution.
1. Using SETI Dex
SETI Dex is a pilot record, logbook, analysis, document, and operational-reference application. You are responsible for the accuracy of information you enter, review, approve, import, or export and for maintaining any records required by your operator or regulator.
2. Aviation safety boundary
SETI Dex is not a certified EFB, dispatch system, navigation system, maintenance-release system, or substitute for operator manuals, authoritative NOTAM/AIP sources, air traffic services, regulators, or flight crew judgment. Weather, NOTAM, AIP, AI/OCR-derived information, and other operational references must be verified against the applicable authoritative source before operational use.
3. Your account and data
Keep your SETI account and device access secure. Your working Logbook may be stored locally on your device with explicit backup/recovery copies. You should keep appropriate independent backups of records you are required to preserve. Account, airline-entitlement, and workspace access are resolved by SETI-controlled authorization rather than by user-selected backend identifiers.
4. Subscriptions and purchases
SETI Dex may offer SETI Plus and SETI Pro subscriptions in 3, 6, and 12-month terms. App Store purchases, localized prices, renewals, cancellation, restoration, billing, and refunds are handled through Apple where the purchase was made through the App Store and remain subject to Apple’s applicable terms. Current beta purchase availability may be limited. See Billing, Subscriptions & Refunds. Nothing in these working terms is intended to remove consumer rights that cannot lawfully be waived.
5. Airline and restricted material
Some content is available only to users with an active airline entitlement. You must not attempt to bypass those restrictions, redistribute restricted operator material, or use another person’s account to obtain access.
6. Acceptable use
Do not misuse SETI Dex to gain unauthorized access, interfere with the service, distribute malware, defeat security controls, impersonate another user, or unlawfully collect or disclose another person’s information. Automated access is permitted only through interfaces SETI explicitly provides for that purpose.
7. User content and intellectual property
You retain responsibility for records, files, photos, notes, and other content you choose to enter or upload. Do not upload, redistribute, or publish material you do not have the right or authorization to use, including restricted airline or third-party content. SETI Dex branding, software, and product materials remain subject to the applicable ownership and licence rights.
8. Third-party services
Selected features can rely on Apple, Google, Google Drive, hosting/database providers, diagnostics providers, or aviation-reference providers. Those services can have their own terms and privacy controls. SETI Dex does not grant broader access to a connected account merely because one feature is authorized.
9. Availability and changes
Features may change as SETI Dex develops. Online services can be interrupted by maintenance, provider outages, connectivity, or third-party source availability. Local-first features are designed to reduce that dependency, but no software service can guarantee uninterrupted availability.
10. Privacy
How SETI Dex handles personal information is described in the Privacy Policy. Browser storage and tracking are described in the Cookie & Tracking Notice. Store and product behavior must match the published notices and the actual shipping application.
11. Support and account actions
For product support, privacy questions, or account requests, use the support channels published inside SETI Dex or on the SETI Dex Support page. Account deletion and provider-revocation flows must follow the safeguards shown in the application and may require identity verification or resolution of shared-resource responsibilities.