Privacy Policy
Last updated October 28, 2026
This notice explains how Nectyl handles information on the website, including accounts, games, the chat workspace, and the early-access waiting list. Model access and payments are not open yet. The chat-data section describes what will happen when model requests are enabled.
Account information
For an email account, we keep your email address, account identifier and name, email-verification status, and account creation time. An account name can be supplied or derived from your email address. We use this information to create and manage your account.
Your password is used to verify sign-in and is stored as a hash with an individual salt. Readable passwords are not kept in the account database.
If you sign in with Google, we use the account identifier, email address, name, and email-verification information in Google’s sign-in response. This does not give Nectyl your Google password or access to Gmail or Google Drive.
Gmail addresses are guided to Google sign-in. Existing email/password accounts can still use their Nectyl password. Google and email/password accounts remain separate sign-in identities.
Authorized Nectyl administrators can view and export email-account details and waiting-list membership, including contact addresses, chosen update interests, sign-in method, two-factor status, and counts of retained game runs. They can end a member’s Nectyl sign-in sessions for account support. These administration screens do not expose passwords, authentication secrets, game-action contents, or chat messages.
Sign-in cookies and security
We use first-party cookies to keep you signed in, protect account requests, and complete verification. These cookies are encrypted and cannot be read by page scripts. Their lifetimes are:
- Sign-in session: up to one day.
- Account-request protection: up to ten minutes.
- Pending email sign-up verification: up to thirty minutes.
- Pending two-factor sign-in: up to five minutes.
If you enable two-factor authentication, we keep the chosen method and verification information needed to protect your account, including an encrypted authenticator secret where applicable and hashed recovery codes.
Email password-reset links work once and expire after fifteen minutes. We store a hash of the reset token, its expiry, and verification-attempt information. A successful password reset invalidates existing sign-in sessions. An account security record lets us keep those old sessions invalid.
Account security checks process request and sign-in signals, including IP addresses and email addresses, to limit abuse. The application stores keyed identifiers and attempt counts for these limits rather than raw IP addresses. Hosting providers may separately process network-request information.
Games and the waiting list
For signed-in games, we store the activity, challenge, submitted game actions, run times and duration, results, recent history, and personal bests. These records are private to your account.
Pi Memory sends and stores the typed draft of an unfinished account run, up to 60,000 characters, so you can return to it. The run can be restored for up to twenty-four hours after it starts. A completed result records the number of correct digits and the run duration. Expired raw runs, including drafts, are removed during later cleanup rather than immediately when restoration expires.
Guest runs and their session scores are temporary. The current website does not keep persistent guest results on your device or save them to an account.
Appearance preferences—color theme, motion, graphics quality, and reading size—are stored in your browser so they survive a reload. They contain no game results or account details. Clearing website storage resets these preferences.
If you choose to join the early-access waiting list, we store your account identifier, email address, sign-in provider, and joining time to record that request. You can optionally select Models, API, or Playground updates. We store those interests with your membership; you can change them or leave the list on the Early Access page.
You can also join with only an email address. We store the address, whether you asked for progress updates, when you joined and confirmed, and keyed hashes of the links in our emails (not the links themselves). We send one email to confirm the address and nothing else until access opens, plus progress updates only if you asked for them. Every email includes a link that deletes your address from the list.
If you apply to test the Chat beta, we store your email address, optional name, and your answers to the questionnaire, plus when you applied and whether you were selected. The email and answers are encrypted before they are stored, and only Nectyl administrators can read them. We use them only to choose testers and to contact you about the beta. To have your application deleted, write to contact@nectyl.com.
Chat and API data
The chat workspace keeps your drafts and conversation list in the memory of the current browser tab. They are not saved to browser storage or your account, and a reload or closing the tab removes them. Drafts are sent for processing only when you submit a message and model access is available.
Once model access is enabled, accepted chat requests are logged across the website and API. Submitted messages, the available generated reply, and request context are kept in encrypted request records. Request context can include the account identifier and sign-in provider for an account request, or the fact that an API access token was used, together with the request’s IP address and browser information. Access-token values and model-provider credentials are not included in those records.
Operational metadata is also recorded, including a request identifier, model identifier, request time, whether the reply was streamed, completion or error status, and duration. This metadata is stored separately from the encrypted conversation content. Requests that fail before acceptance, including requests while model access is unconfigured, do not create a conversation record through this service.
These request records have a thirty-day expiry measured from the start of the request. Expired records are removed during later request cleanup or configured scheduled cleanup. Expiry does not guarantee immediate removal of every copy, including separate provider records or backups.
Clearing a chat, reloading, or closing the tab removes the tab’s local conversation view; it does not erase server request records. Account deletion does not automatically erase these separate request records. You can contact us about a request to access or delete them, and we may need information that lets us identify the relevant records.
This first chat interface does not offer a Temporary Chat mode. The API also has no Temporary Chat option: logging remains part of an accepted model request. Separate sensitive-content screening and training-preference controls are not available yet. Nectyl’s chat service does not use these request records to train models.
When enabled, the configured model service receives the submitted conversation to generate a reply. Its own data handling may differ from Nectyl’s request-record expiry. We will update this notice with the model-service details before opening access.
Contacting us
If you contact us by email, the message includes your email address and the information you choose to send. We use messages we receive to handle and respond to the request. Email providers process messages as part of delivery.
While model access is unconfigured, model requests are declined before their message body is read by the model service. The chat workspace is available for preparing drafts. Checkout is not active, and the website does not collect payment-card details.
Service providers
Cloudflare provides website delivery and account-data storage. Google provides optional Google sign-in. Verification and security messages are sent from verify@nectyl.com through Resend or Cloudflare Email Sending, depending on the configured delivery service. Email delivery requires the recipient address and message contents.
These providers process information needed to deliver their services and may keep their own operational records. Their notices describe their processing and privacy controls:
Keeping and deleting information
We keep account information, saved results, and waiting-list details while your account exists to provide the features you choose. Recent game history is limited to fifty completed runs, alongside per-game personal-best records.
Temporary verification and security records expire and are removed during later cleanup. Older raw game-run records are also cleared during cleanup. Expiry is not a promise that every copy is erased immediately.
Deleting your account removes its email-account credentials, verification and two-factor records, waiting-list entry, and stored game records. A limited account-revocation record remains so old sign-in sessions cannot become valid again. Temporary abuse-prevention records are cleared through their normal cleanup process.
Account deletion does not delete your Google account or messages already delivered to inboxes. Support correspondence, provider logs, and backup copies, where they exist, may follow separate retention periods.
Your choices and requests
You can use guest activities without an account, manage two-factor authentication in your account menu, sign out, or delete your Nectyl account. You can block or clear cookies in your browser; account sign-in and verification may then stop working.
Download my records in Account settings provides a private JSON file with personal bests, the latest fifty completed game runs, unfinished-run summaries, and waiting-list membership and interests. Typed Pi drafts are excluded from that download.
For questions, account corrections, waiting-list removal, or requests to access or delete information, email contact@nectyl.com. We may ask you to verify account ownership before acting on a request. The rights available to you depend on applicable law.
Updates
This notice will be updated as the website’s features and data handling change. The date at the top identifies the latest version.