Alpha privacy notice · July 24, 2026

Private curiosity deserves clear rules.

This notice covers the SIUN founding-tester application and the private alpha. External testing will not begin unless the notice matches the implemented search path and the operating entity and dedicated privacy contact shown below are verified.

Application information

We collect the information you submit: name, email, device and iOS version, age range, current search sources, a recent decision example, expected weekly usage, consent confirmations, and referral source. We use it to select, contact, support, and learn from alpha testers.

Support information

If you open a support case, we store your contact email, category, message, consent confirmation, case status, and timestamps so the SIUN team can investigate and respond. Do not include search text, credentials, or sensitive personal information in a support report. When a failed search displays a random support reference, including it is optional and lets the team match the report to that technical event without revealing the query text. Support cases are available only through an authenticated administrative endpoint and are excluded from product measurement.

Alpha usage

The alpha records an installation-scoped random identifier, trust mode, a keyed digest and character count of each query, completion or failure status, latency, source counts, model and tool usage, and estimated cost. SIUN does not store raw query text in its analytics database. If you answer the one-tap comparison question, SIUN stores whether you preferred SIUN, your usual method, or rated them the same. After five completed searches, SIUN may ask how disappointed you would be if the product disappeared; it stores that answer and the number of completed searches at the time. Later alpha builds may add clearly disclosed measurements for evidence opened, saves, shares, and return usage.

Tester ID and return reconciliation

The app shows a shortened, pseudonymous Tester ID in its alpha information screen. Sharing it with the SIUN founder is optional. If you share it, the project team may link that code to your application and outreach record so completed-search days, comparison verdicts, and the optional retention answer can be reconciled with whether a founder-initiated contact was sent between searches. The outreach ledger stores only your application linkage, a bounded contact category, whether the contact affects return proof, and timestamps; it never stores message text. This is used to verify participation and unprompted return behavior. If you do not share the Tester ID, SIUN still works, but that activity is not counted as a qualified participant in the founder’s mission readout. The founder console does not expose raw query text, query digests, or the full installation identifier.

Search content

Search text is sent from SIUN’s server to the OpenAI API so its Responses API and web-search tool can retrieve and synthesize current sources. SIUN requests non-persistent response state by setting store: false. OpenAI may still retain API content for up to 30 days for abuse monitoring unless SIUN’s API organization is approved for Zero Data Retention. Pages reached through web search remain subject to their publishers’ own policies.

Do not submit sensitive personal information or medical, legal, financial, or safety-critical searches during the alpha.

Retention and access

Application and alpha records are limited to the SIUN project team and retained only as long as needed to operate and evaluate the alpha. We do not sell applicant or search information.

Your choices

Participation is optional. A tester may stop at any time and may ask for their application or associated alpha records to be deleted by replying to any SIUN invitation or opening a private support case. A dedicated privacy contact must be published on this page before external invitations begin.

Changes before launch

This is a pre-alpha notice. TestFlight invitations will not be sent unless the notice matches the product’s implemented data flow and the verified operating entity and contact information appear above.