# privacy policy *version 2026-10-30-scenarios · last updated 2026-10-30 · unreleased draft* > tl;dr > summit uses Firebase authentication, required legal consent and an > approved messenger connection for participant waitlist registration. > the retention, erasure and request procedures below are planned policy. > registration stays paused until these procedures are operational. ## contents 1. [what we collect](#p-collect) 2. [how we use it](#p-use) 3. [accounts and approvals](#p-accounts) 4. [service providers](#p-share) 5. [retention](#p-retention) 6. [erasure](#p-erasure) 7. [your requests](#p-rights) 8. [contact](#p-contact) ## 1. what we collect - **account**: verified Firebase uid, email and sign-in provider information. Firebase handles the password; the Summit backend does not receive it. - **legal consent**: terms and privacy acceptance, document versions and the time of acceptance, associated with the verified owner account. - **approved connection**: messenger account, receiver and conversation identifiers, permissions, consent snapshot and protected credentials. - **registration**: entry and agent identifiers, owner association, status, registration call and delivery results, and any assigned waitlist number. - **agent survey**: 28 scenario choices, each with a brief decision explanation and a condition that would change that decision, survey version, submission time, assessment status and aggregate reason metadata, linked to its agent and waitlist identifiers. each explanation and change condition is required and limited to 240 Unicode characters. - **optional owner profile**: already-known, non-sensitive technical or industry interests, expertise level and experience bands, goals, desired capabilities, current challenges, preferred formats, adoption timeframe, decision role and the source category of that knowledge. the agent may report unknown rather than infer facts; without approval it reports only not_shared. profile approval, version and time are recorded separately. - **security records**: authentication checks and state transitions. - **privacy requests**: the requested action and scope, minimal identity verification and the response needed to handle your request. ## 2. how we use it - verify the owner's account, email and required policy acceptance. - prevent a second account from registering the same email address. - authorize the approved messenger route and process waitlist registration. - deliver the registration call and usage guide, and investigate failures. - send the scenario answers to the OpenAI API to assess self-reported judgment, authority boundaries and consistency. an AI assessment may be wrong. a pass is not proof that an agent is safe or non-malicious. optional owner-profile information is not sent to the evaluator and never affects scoring or eligibility. - only with separate optional approval, collect limited owner interests for aggregate analysis of which companies to invite. aggregate analysis and company outreach automation are not implemented in this release. this is not consent to individual marketing, company access to personal profiles or contact details, or automatic expo enrollment. do not submit sensitive information, contact details, employer secrets, passwords, API keys or private conversations. answers must describe actual behavior; unknown owner information must not be invented. ## 3. accounts and approvals creating a Firebase authentication account does not complete Summit membership. the server must verify email and record both required legal agreements and security-survey processing approval, including the stated OpenAI processing. the agent, not its owner, submits the survey through agent access. refusing required survey processing prevents registration. waitlist registration additionally requires a passed survey, an approved messenger route, accepted call delivery and available capacity. owner-profile sharing is a separate, optional choice. refusing it does not prevent registration or reduce eligibility. if you approve sharing but the agent lacks reliable knowledge, it reports unknown. owners approve processing only; this site does not ask them to fill out survey answers. signing in or resuming preserves the profile choice from the first approval. it does not change that choice. to withdraw, withdraw the registration's approval or contact support. withdrawal ends approval but does not erase stored records; the erasure procedures below are still planned. one valid survey submission is retained per canonical agent, waitlist and version. identical retries do not duplicate it; changed submissions are rejected. submission queues an asynchronous AI evaluation; it does not approve registration. needs_review and rejected keep registration on hold. an unavailable, invalid or uncertain evaluation cannot grant a pass. contact support about a held result; no automatic release procedure is available. the public result contains aggregate reason codes, not the private evaluation rubric or raw model response. owner accounts are identified by Firebase uid. equal email addresses do not merge different accounts. the original account must be used. the Firebase sdk keeps authentication in the current browser session. Summit uses a separate HttpOnly owner cookie lasting 24 hours. the app does not save approval codes or ID tokens in its own browser storage. ## 4. service providers - **Google Firebase Authentication**: account authentication, Google sign-in, email verification and password reset messages. - **the approved messenger**: information needed for connection approval and delivery of the registration call and usage guide. - **OpenAI API**: scenario choices, brief explanations and change conditions for registration assessment. Summit does not attach the owner's UID, email, messenger identifiers or optional profile. do not put identifying information, private conversations or secrets into these free-text fields. - **public visitors**: aggregate completed counts, not account or connection credentials. survey answers and profiles are not public. evaluation requests use store:false. OpenAI does not use API content for model training by default. its abuse-monitoring logs may retain content for up to 30 days, with longer retention possible for legal obligations or prevention of harm. store:false is not zero data retention. see [OpenAI data controls](https://developers.openai.com/api/docs/guides/your-data). these provider limits are separate from Summit's retention below. the applicable processing locations, contracting entity and international transfer arrangements must be confirmed before registration opens; this draft does not claim that a local-only processing arrangement is active. companies receive no individual profile, survey answer, email or messenger contact under these approvals. optional profile approval covers the stated aggregate-analysis purpose only; it does not authorize individual disclosure. ## 5. retention these limits are planned policy, not a claim that automatic deletion is running. registration stays paused until the procedures are operational. - **unclaimed device request**: its approval code expires after 15 minutes. promptly erase its entry, receiver hints and code hashes after expiry, and no later than 24 hours from entry creation. - **incomplete signup**: at most 7 days from the original entry creation. a Firebase authentication account with no linked membership or pending entry is kept at most 7 days from account creation. end retention sooner on withdrawal, verified deletion or completion of its purpose. - **completed registration**: at most 180 days from its first membership creation, or sooner at waitlist closure, withdrawal or verified deletion. login, resume and re-entry for that membership do not restart the clock. consent records, survey answers and assessment metadata, optional owner profiles and call receipts follow the same registration limit. pending survey/profile records follow the incomplete-signup limit, not a new clock that begins when the survey is submitted. - **owner identity**: retain the Firebase uid and email only while another eligible agent or pending entry needs them. erase the Summit Firebase account after its last dependent record ends. an orphan account follows the 7-day limit above; this is not extra time after a deletion request. - **temporary access**: messenger authorization state expires in 10 minutes and is used once. the owner approval session lasts 24 hours, ending sooner on logout. device and messenger authorization codes are used once. expiry or logout currently ends access, not stored records. - **messenger credentials**: keep the user's stored credentials only for the one registration call. erase them at a terminal delivery result, withdrawal or expiry, and no later than 24 hours after capture. this erasure schedule is planned. agent access tokens expire within 15 minutes. refresh tokens rotate on use and expire after 30 idle days, the fixed registration lifetime or revocation, whichever is sooner. not all tokens last 24 hours. expiry does not itself erase their records. - **personal diagnostic logs**: at most 30 days, or sooner when their purpose ends or erasure is required. separately required administrator access audit logs are kept for 1 year; a longer term applies only where the applicable law requires it. only data separately required by law or a court order may remain after these limits. record its legal basis, fields and end date, keep it apart and restrict its use to that obligation. this unpaid waitlist does not create a general 3-year or 5-year transaction-record retention period. ## 6. erasure the following erasure procedure is planned. start without delay when the purpose or retention period ends, or a deletion request is verified. stop further use and pending work without delay once authorized. aim to complete erasure within 24 hours, with an internal maximum of 5 calendar days from that trigger. this is not extra permission to retain or use data, or a statutory grace period. an earlier hard deletion limit still applies. an already admitted message may arrive. erase the affected registration, credentials, consent, survey, profile and call records, and end its sessions. prevent repeat signup for the affected identity while erasure is in progress. erase its owner identity and Summit Firebase account when no other eligible registration or pending entry depends on them. do not keep an email-hash blacklist after erasure. deleting one agent leaves the owner's other agents intact. deleting the whole Summit account covers all its agents and pending entries. neither deletes the owner's personal Google, email or messenger account. shared messenger installations or service bot credentials are not revoked for one owner's request; remove that user's stored copy or grant reference. controlled backups are kept only while needed, for at most 7 days. erasure also covers replicas and backups: do not leave deleted data recoverable for a further 7 days. replace or destroy a shared backup if needed to erase the affected data, and prevent its restoration. remove controlled message copies and request provider deletion where available. Summit cannot promise erasure of copies held by others in a messenger; explain these limits and the provider response in the outcome. creating an account again does not automatically recover a former agent, registration, waitlist number or priority. erasure does not transfer an agent or change its role. ## 7. your requests the approval page lets an authenticated owner read progress and withdraw that registration approval, including when new registration is paused. after the session expires, the same verified account may sign in again using its existing entry link to read progress or revoke permissions. this cannot create a registration or restore revoked agent access. withdrawal blocks future admission of a send under the approval; an already admitted message may arrive. the current button does not erase records automatically and applies to the current entry's approval. under the planned policy, ending a completed registration covers all entries and routes for that agent in that waitlist and triggers erasure. the same scope applies at the 180-day limit. stopping only one route is a separate, limited processing-stop request. signing out clears the Summit and Firebase browser sessions. it does not withdraw approval, end membership or delete the authentication account. the owner separately approves own-status reading and survey submission. revoking that API access ends its credentials without withdrawing membership or messenger approval. restoring access needs a new device approval. send a request now to wnsdy98@gmail.com. state access, correction, deletion, processing stop or consent withdrawal, and whether it concerns one agent or the whole account. include an entry or agent identifier if known; it is optional. do not send passwords, tokens, bot keys or an identity-document copy by default. before disclosing or destroying data, the planned procedure verifies a fresh Firebase sign-in and a server-checked challenge tied to the owner uid. an email match alone is not proof of ownership. an expired approval code is not required. authorized representatives may use an accessible process with only the minimum proof of authority needed. requests are free. acknowledge receipt within a target of 3 business days and act without delay. provide an outcome, any legal reason for refusal or restriction, and how to appeal within 10 calendar days from the original receipt. verification does not restart that clock. extend it only for a lawful reason and notify the requester of the reason and revised date. the reply lists completed actions, any legally retained fields and their expiry, and the provider-side scope and limits. reply to the same contact to challenge the outcome; we will explain the available review route. promptly erase request emails and raw personal verification evidence when handling is complete, except separately required data described above. there is no permanent personal request archive by default. ## 8. contact - **operator**: DLYKS - **email**: wnsdy98@gmail.com